Bug#299055: Installation report for Dell PowerEdge 1850
Package: installation-reports
Hi,
INSTALL REPORT
Debian-installer-version: Debian Installer RC2 disc1 for i386, from
<http://www.debian.org/devel/debian-installer/>
uname -a: Linux fw 2.4.27-2-686-smp #1 SMP Thu Jan 20 11:02:39 JST 2005 i686 GNU/Linux
Date: 2005/02/28
Method: I installed Debian with the bootable CD set. I did not use any network
connection until the base system was installed. Then I setuped a
classical ADSL connection via PPPoE and updated my Sarge system.
Machine: PowerEdge 1850
Processor: Intel(R) Xeon(TM) CPU 2.80GHz (this machine is SMP capable, but was
bought wis a single CPU)
Memory: 1 GB
Root Device: /dev/mapper/vg0-root, this is an ext3 filesystem created on
a LVM LV named root, in the LVM VG named vg0 of format LVM2 with
PV /dev/sda2
/dev/sda is a RAID 1 array provided by module megaraid2
Root Size/partition table: here's the output of fdisk -l /dev/sda:
Disk /dev/sda: 73.2 GB, 73274490880 bytes
255 heads, 63 sectors/track, 8908 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 31 248976 83 Linux
/dev/sda2 32 8908 71304502+ 8e Linux LVM
Here's the output of mount -l -t ext3:
/dev/mapper/vg0-root on / type ext3 (rw,errors=remount-ro)
/dev/sda1 on /boot type ext3 (rw)
/dev/mapper/vg0-home on /home type ext3 (rw)
/dev/mapper/vg0-srv on /srv type ext3 (rw)
/dev/mapper/vg0-usr on /usr type ext3 (rw)
/dev/mapper/vg0-var on /var type ext3 (rw)
/dev/mapper/vg0-var--log on /var/log type ext3 (rw)
Output of lspci and lspci -n:
Here's the output of lspci:
0000:00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 09)
0000:00:02.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A0 (rev 09)
0000:00:04.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port B0 (rev 09)
0000:00:05.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port B1 (rev 09)
0000:00:06.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port C0 (rev 09)
0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02)
0000:01:00.0 PCI bridge: Intel Corp. 80332 [Dobson] I/O processor (rev 06)
0000:01:00.2 PCI bridge: Intel Corp. 80332 [Dobson] I/O processor (rev 06)
0000:02:0c.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
0000:02:0c.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
0000:02:0e.0 RAID bus controller: Dell PowerEdge Expandable RAID controller 4 (rev 06)
0000:03:0b.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
0000:03:0b.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
0000:05:00.0 PCI bridge: Intel Corp. PCI Bridge Hub A (rev 09)
0000:05:00.2 PCI bridge: Intel Corp. PCI Bridge Hub B (rev 09)
0000:06:07.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05)
0000:07:08.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05)
0000:09:0d.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]
And here's the output of lspci -n:
0000:00:00.0 0600: 8086:3590 (rev 09)
0000:00:02.0 0604: 8086:3595 (rev 09)
0000:00:04.0 0604: 8086:3597 (rev 09)
0000:00:05.0 0604: 8086:3598 (rev 09)
0000:00:06.0 0604: 8086:3599 (rev 09)
0000:00:1d.0 0c03: 8086:24d2 (rev 02)
0000:00:1d.1 0c03: 8086:24d4 (rev 02)
0000:00:1d.2 0c03: 8086:24d7 (rev 02)
0000:00:1d.7 0c03: 8086:24dd (rev 02)
0000:00:1e.0 0604: 8086:244e (rev c2)
0000:00:1f.0 0601: 8086:24d0 (rev 02)
0000:00:1f.1 0101: 8086:24db (rev 02)
0000:01:00.0 0604: 8086:0330 (rev 06)
0000:01:00.2 0604: 8086:0332 (rev 06)
0000:02:0c.0 0200: 8086:1010 (rev 01)
0000:02:0c.1 0200: 8086:1010 (rev 01)
0000:02:0e.0 0104: 1028:0013 (rev 06)
0000:03:0b.0 0200: 8086:1010 (rev 01)
0000:03:0b.1 0200: 8086:1010 (rev 01)
0000:05:00.0 0604: 8086:0329 (rev 09)
0000:05:00.2 0604: 8086:032a (rev 09)
0000:06:07.0 0200: 8086:1076 (rev 05)
0000:07:08.0 0200: 8086:1076 (rev 05)
0000:09:0d.0 0300: 1002:5159
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O]
Configure network HW: [E]
Config network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O]
Reboot: [O]
Comments/Problems:
I saw two main problems, one major problem with the megaraid2 loading, and a
minor one when detecting network hardware.
(First 2.6 attempts:)
Confident in D-I, I first tried a linux26 setup, and then an expert26 setup
since no disk was found (no sda in dmesg). Inserting module "megaraid" from
tty2 didn't help, either because it doesn't work on 2.6 or because the module
to use in 2.6 is also called "megaraid2".
(Going back to 2.4:)
I was told by a coworker that the RAID driver wasn't expected to work in 2.6,
so I immediately tried an "expert" install. The steps "detect network
hardware" and "detect hardware" both offered to load megaraid2 to support my
RAID controller. This permitted to go on with the installation, until the
choice of kernel.
This is where I would like to report the first thing I consider a bug:
megaraid2 is not a network driver, but was loaded during the "detect network
hardware phase".
The setup went fine for LVM etc, until I had to choose a kernel to boot on.
I tried with the 686 kernel, the 686 SMP kernel, and the 386 kernel because
I thought SMP support might interfere with my megaraid2 module (see below).
I must add I couldn't tell what "speakup" is for a kernel flavor, maybe this
would need some documentation or help?
(First boot always failed:)
Finally, I noticed the boot couldn't work because initrd was loading megaraid
instead of megaraid2. I went through all the d-i screens I could think of,
but missed the way to add a custom module to the initrd image. So I manually
mounted all my partitions, edited /etc/mkinitrd/modules, and added "megaraid2".
I reinstalled another kernel image (somehow my mkinitrd command lines did not
produce useful images), and the new kernel+initrd booted fine.
As you saw above, I know run 2.4.27 686 SMP, and everything else is fine.
My bugs are:
1/ megaraid2 missing from initrd (important)
2/ megaraid2 inserted by network hardware detection phase (minor)
3/ better description for the choice of a kernel (it's surprizing that d-i RC2
runs 2.4.27-1 and offers only -2 to install), ie. what's "speakup" (wishlist)
Bug #282109 is about the same hardware, and I bet the submitter hit the
exact same problem, as would probably other megaraid2 users do.
Thanks for Debian Installer.
Regards,
--
Loïc Minier <lool@dooz.org>
"Neutral President: I have no strong feelings one way or the other."
Reply to: