[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

d-i install report, hppa



INSTALL REPORT

Debian-installer-version: cvs-head, 20040118, built locally
uname -a:
Date: Sun, 18 Jan 2004 19:28:45 +0000
Method: netboot of lifimage (netboot-image.img), installing from local
	unstable mirror.

Machine: B180L, Merlin L2+ 180 (9000/778/B180L)
Processor: PA7300LC (PCX-L2)
Memory: 256MB
Root Device: SCSI

Root Size/partition table:
  Disk /dev/sda: 4294 MB, 4294816768 bytes
  133 heads, 62 sectors/track, 1017 cylinders
  Units = cylinders of 8246 * 512 = 4221952 bytes
  
     Device Boot      Start         End      Blocks   Id  System
  /dev/sda1               1           8       32953   f0  Linux/PA-RISC boot
  /dev/sda2               9         245      977151   83  Linux
  /dev/sda3             246         306      251503   82  Linux swap

Output of lspci:
  richard@debian:~$ lspci 
  00:13.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 04)
  00:14.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 30)
  richard@debian:~$ lspci -n
  00:13.0 Class 0100: 1000:000f (rev 04)
  00:14.0 Class 0200: 1011:0019 (rev 30)
  richard@debian:~$ 


Base System Installation Checklist:

Initial boot worked:    [E]
Configure network HW:   [O]
Config network:         [O]
Detect CD:              [ ]
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]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

Initial boot fails due to a SEGV in frontend; this appears to be because
of a bug in glibc, triggered by libm being reduced to what is effectively
an empty library.  Bug #228375 filed.  I hacked mklibs to include a symbol
from libm, so I could build a working image.  text frontend worked ok.

Kernel hung on reboot when discover tried to load de4x5.o; the kernel
has the tulip driver compiled in to handle the network i/f.  I renamed
the module and tried again.  This time it rebooted ok, and base-config
ran ok.

Richard



Reply to: