Package: installation-reports Severity: normal Debian-installer-version: today's hppa netboot daily build Method: Netbooted, installed from my local sarge mirror. Machine: hppa a500 (I think, it's not mine) Processor: dual 550 mhz PA8600 Memory: 1994 mb Root Device: /dev/sda5 Root Size/partition table: Device Boot Start End Blocks Id System /dev/sda1 1 4 32098+ f0 Linux/PA-RISC boot /dev/sda2 5 20 128520 83 Linux /dev/sda3 21 8924 71521380 5 Extended /dev/sda5 * 21 54 273073+ 83 Linux /dev/sda6 55 662 4883728+ 83 Linux /dev/sda7 663 1027 2931831 83 Linux /dev/sda8 1028 1789 6120733+ 82 Linux swap /dev/sda9 1790 1838 393561 83 Linux /dev/sda10 1839 8924 56918263+ 83 Linux Output of (lspci ; lspci -n) |sort -n: 0000:00:00.0 0200: 1011:0019 (rev 41) 0000:00:00.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 41) 0000:00:01.0 0100: 1000:000b (rev 07) 0000:00:01.0 SCSI storage controller: LSI Logic / Symbios Logic 53C896/897 (rev 07) 0000:00:01.1 0100: 1000:000b (rev 07) 0000:00:01.1 SCSI storage controller: LSI Logic / Symbios Logic 53C896/897 (rev 07) 0000:00:02.0 0100: 1000:000f (rev 14) 0000:00:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 14) 0000:00:02.1 0100: 1000:000f (rev 14) 0000:00:02.1 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 14) 0000:00:04.0 0700: 103c:1048 (rev 02) 0000:00:04.0 Serial controller: Hewlett-Packard Company Diva Serial [GSP] Multiport UART (rev 02) 0000:00:05.0 0700: 103c:1048 (rev 02) 0000:00:05.0 Serial controller: Hewlett-Packard Company Diva Serial [GSP] Multiport UART (rev 02) 0000:10:00.0 0200: 12ae:0001 (rev 01) 0000:10:00.0 Ethernet controller: Alteon Networks Inc. AceNIC Gigabit Ethernet (rev 01) 0000:20:00.0 0200: 12ae:0001 (rev 01) 0000:20:00.0 Ethernet controller: Alteon Networks Inc. AceNIC Gigabit Ethernet (rev 01) 0000:30:02.0 0100: 1000:0021 (rev 01) 0000:30:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 66MHz Ultra3 SCSI Adapter (rev 01) Note that this system has 3 ethernet cards. The two Alteon's are in pci slots, the other one is built in. Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked: [O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems: [O] Mount partitions: [O] Install base system: [O] Install boot loader: [O] Reboot: [E] Comments/Problems: This was my first hppa install. Most of the install (the entire first stage) was performed noninteractively using my preseeding and digress framework. The first stage install went fine, although out of several dozen I've done today in teaking digress to work with hppa, I did experience one that hung the machine during partman disk formatting to the point that linux stopped responding to pings. And of course partman is slow on hppa with the 2.4 kernel. Anyway, problems began in second stage boot. I'm using the network console, and got some alerts. A truncated version of the first one, which happended before linux booted at all: ************* SYSTEM ALERT ************** ALERT LEVEL: 6 = Boot possible, pending failure - action required REASON FOR ALERT SOURCE: 8 = I/O SOURCE DETAIL: 6 = disk SOURCE ID: 0 I accepted this alert, and it went on to boot linux. So what does this alert mean, anyone know? Any way to disable it? Then I got a second alert: Detecting hardware: de4x5 acenic sym53c8xx_2 Roading de4x5 module. ... REASON FOR ALERT SOURCE: 0 = unknown, no source stated SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF Here it hung. Apparently de4x5 is not happy with this hardware. This was kernel 2.4.27-64-smp BTW. I reset the machine and discover didn't load de4x5 this time since it hung before, and the system came up to base-config ok, and the network even worked. eth0: Digital DS21143 Tulip rev 65 at 0x80, 00:30:6E:1C:90:2E, IRQ 128. eth0: Setting half-duplex based on MII#1 link partner capability of 0021. So the tulip driver is compiled in, is used, and presumaly gets pissed off when de4x5 tries to take over the same card. :-/ The other two ethernet cards did not come up, since discover wants to load the acenic module for them, and this module does not exist with the 2.4.27 hppa kernel. I notice that de4x5 is not included in the d-i udebs at all, which is probaly why my first stage install succeeded. Perhaps it should be dropped from the hppa kernel entirely, if all it does is conflict with tulip and crash boots.. For some reason it wanted to configure console-data in the second stage. Not sure why, though I've seen this on sparc and s390 too. The rest of the install went ok. -- see shy jo
Attachment:
signature.asc
Description: Digital signature