Debian-installer-version:
http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20041227/sarge-i386-businesscard.iso
uname -a: <The result of running uname -a on a shell prompt>
Date: 20041228
Method: cdrom boot
Machine: HP Proliant ML110
Processor: PentiumIV 3.0Ghz
Memory: 1Gb (2x512Mb memory modules)
Root Device: SATA on Promise PDC20621 (2 160Gb disks in raid1)
Root Size/partition table: <Feel free to paste the full partition
table, with notes on which partitions are mounted where.>
Output of lspci and lspci -n:
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O]
Configure network HW: [ ]
Config network: [ ]
Detect CD: [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Create file systems: [ ]
Mount partitions: [ ]
Install base system: [ ]
Install boot loader: [ ]
Reboot: [ ]
Comments/Problems:
Whenever the installer is started (linux, linux26, expert26, expert) and
the CD-ROM is detected, the installer tries to load the sd_mod module
and hang forever (at least, for more than 5 minutes.)
"hang" means that the computer is blocked at 92% and control-alt-del
doesn't work.
This computer host a SATA promise controller and a tekram DC-395UW SCSI
controller with a tape connected to it.
If the SCSI controller is removed, the installation proceed correctly.
If the SATA controller is removed, then the installation process keep
going until it cannot find any hard disk.
So, I think that maybe the problem reside in the SCSI driver that
require a disk on its chain, while I only have a tape there.
Bye,
Giuseppe
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Summary: d-i does not correctly handle Promise FastTrak SATA SX4.
I removed all other PCI cards and I still cannot correctly install Sarge
since whenever sd_mod is loaded the computer freeze.
A second -- and different -- problem is about the SCSI controller I
already mentioned. It seems that it cannot correctly handle tape drives
like the HP DAT72i.
I then added an IDE drive to the internal PATA controller and installed
debian locally. When debian starts the module sata_sx is loaded but the
sd_mod isn't and the controller is correctly detected and all scsi0-3
chain are defined. Then, when I load sd_mod, the computer start giving
SCSI errors and then freeze.
I recompiled kernel 2.6.10 putting all SCSI and SATA stuff builtin (as
opposed to modules) and removed all IDE drivers. The new kernel boots
and recognize correctly all disks. The operating system then boot.
Bye,
Giuseppe
P.S. lspci is now available and attached.
> A second -- and different -- problem is about the SCSI controller I
> already mentioned. It seems that it cannot correctly handle tape drives
> like the HP DAT72i.
Please file a seperate bugreport for it.
> I then added an IDE drive to the internal PATA controller and installed
> debian locally. When debian starts the module sata_sx is loaded but the
> sd_mod isn't and the controller is correctly detected and all scsi0-3
> chain are defined. Then, when I load sd_mod, the computer start giving
> SCSI errors and then freeze.
>
> I recompiled kernel 2.6.10 putting all SCSI and SATA stuff builtin (as
> opposed to modules) and removed all IDE drivers. The new kernel boots
> and recognize correctly all disks. The operating system then boot.
>
> Bye,
> Giuseppe
>
> P.S. lspci is now available and attached.
> 0000:00:00.0 Host bridge: Intel Corp. 82875P Memory Controller Hub (rev 02)
> 0000:00:1c.0 PCI bridge: Intel Corp. 6300ESB 64-bit PCI-X Bridge (rev 02)
> 0000:00:1d.0 USB Controller: Intel Corp. 6300ESB USB Universal Host Controller (rev 02)
> 0000:00:1d.1 USB Controller: Intel Corp. 6300ESB USB Universal Host Controller (rev 02)
> 0000:00:1d.4 System peripheral: Intel Corp. 6300ESB Watchdog Timer (rev 02)
> 0000:00:1d.5 PIC: Intel Corp. 6300ESB I/O Advanced Programmable Interrupt Controller (rev 02)
> 0000:00:1d.7 USB Controller: Intel Corp. 6300ESB USB2 Enhanced Host Controller (rev 02)
> 0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 0a)
> 0000:00:1f.0 ISA bridge: Intel Corp. 6300ESB LPC Interface Controller (rev 02)
> 0000:00:1f.1 IDE interface: Intel Corp. 6300ESB PATA Storage Controller (rev 02)
> 0000:00:1f.3 SMBus: Intel Corp. 6300ESB SMBus Controller (rev 02)
> 0000:04:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
> 0000:04:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705_2 Gigabit Ethernet (rev 03)
> 0000:04:05.0 SCSI storage controller: Tekram Technology Co.,Ltd. TRM-S1040 (rev 01)
> 0000:04:06.0 RAID bus controller: Promise Technology, Inc. PDC20621 [SATA150 SX4] 4 Channel IDE RAID Controller (rev 01)
Provide also the output of `lspci -n`
or even better:
( lspci ; lspci -n ) | sort
Cheers
Geert Stappers
Here it is.
Bye,
Giuseppe
I made some further tests and also had some email exchange with Promise
support and I got finally a clue about the problem: sd_mod need to be
loaded before sata_sx. This is a know problem even for the original
driver (shipped only for redhat and suse.)
So the solution might be to include in /etc/modprobe.conf something
like:
install sata_sx "/sbin/modprobe sd_mod; /sbin/modprobe ‐‐ignore‐install
sata_sx"
or in /etc/modules.conf, this similar command:
pre-install sata_sx modprobe sd_mod
This change should of course be done even on the /target file system.
Does anyonw know if this is possible using the modprobe command included
in d-i (is it from busybox?)
Thanks,
Giuseppe
> I made some further tests and also had some email exchange with Promise
> support and I got finally a clue about the problem: sd_mod need to be
> loaded before sata_sx. This is a know problem even for the original
> driver (shipped only for redhat and suse.)
I. Hate. The. Kernel. :-(
> So the solution might be to include in /etc/modprobe.conf something
> like:
> install sata_sx "/sbin/modprobe sd_mod; /sbin/modprobe ‐‐ignore‐install
> sata_sx"
I don't think that will affect the order the modules are loaded by the
installed system's initrd will it?
> Does anyonw know if this is possible using the modprobe command included
> in d-i (is it from busybox?)
It depends on the kernel version, 2.6 uses the module-init-tools one.
I think we can work around it easily in d-i by adding a hack to
load_module() in hw-detect. Fixing it in initrd-tools could be harder.
--
see shy jo