Package: installation-reports Debian-installer-version: sarge netinst daily of 20040812 uname -a: Linux buddha 2.4.26-1-generic #1 Tue Aug 3 22:46:34 CEST 2004 alpha GNU/Linux Date: Fri Aug 13 15:59:17 CDT 2004 Method: Booted from SRM onto the netinst CD.
Machine: AlphaServer 2100 4x275
Processor: 2 x Alpha EV45 275mhz
Memory: 512MB
Root Device: HW RAID5 on DAC960 controller, /dev/rd/c0d0
Root Size/partition table: (a=aboot, b=/boot, c=/, d=swap)
5 partitions:
# start end size fstype [fsize bsize cpg]
a: 1* 1* 0* ext2
b: 1* 39* 38* ext2
c: 39* 14075* 14035* ext2
d: 14075* 14319* 244* swap
Output of lspci:
PCI devices found:
Bus 0, device 0, function 0:
Ethernet controller: Digital Equipment Corporation DECchip 21040
[Tulip] (rev 35).
IRQ 32.
Master Capable. Latency=32.
I/O at 0x9400 [0x947f].
Non-prefetchable 32 bit memory at 0x1109000 [0x110907f].
Bus 0, device 1, function 0:
SCSI storage controller: LSI Logic / Symbios Logic 53c810 (rev 2).
IRQ 33.
Master Capable. Latency=32.
I/O at 0x9000 [0x90ff].
Non-prefetchable 32 bit memory at 0x1108000 [0x11080ff].
Bus 0, device 2, function 0:
Non-VGA unclassified device: Intel Corp. 82375EB (rev 4).
Master Capable. Latency=32.
Bus 0, device 6, function 0:
RAID bus controller: Mylex Corporation DAC960P (rev 2).
IRQ 34.
Master Capable. Latency=32. Min Gnt=4.
I/O at 0x9480 [0x94ff].
Non-prefetchable 32 bit memory at 0x110a000 [0x110a07f].
Base System Installation Checklist:
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: [E]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
Well things are getting far better than they used to be. With the daily
from 20040812, I was able to get all the way to the installation of the
bootloader (aboot, since this is on an Alpha), which gave me this
message:
An installation step failed. You can try to run the failing item
again from the menu, or skip it and choose something else. The
failing step is: Install aboot on a hard disk
I noticed that it appeared to be trying to install aboot to
"/dev/rd/c0d0p". If I remember swriteboot's usage, it should perhaps be
using /dev/rd/c0d0. Otherwise, it needs a partition number after the p.
Syslog tells me,
Jul 7 22:08:05 main-menu[258]: DEBUG: Menu item 'aboot-installer' selected
Jul 7 22:08:05 main-menu[258]: DEBUG: configure aboot-installer, status: 2
Jul 7 22:08:05 main-menu[258]: DEBUG: configure chroot, status: 0
Jul 7 22:08:18 aboot-installer: info: Installing aboot on '/dev/rd/c0d0p'
Jul 7 22:08:18 main-menu[258]: (process:5501): open disk device: No such file or
directory
Jul 7 22:08:18 main-menu[258]: WARNING **: Configuring 'aboot-installer' failed with
error code 1
Jul 7 22:08:18 main-menu[258]: WARNING **: Menu item 'aboot-installer' failed.
I chroot'd into /target and manually did an swriteboot / abootconf
invocation:
cd /boot
swriteboot -f1 /dev/rd/c0d0 bootlx
abootconf /dev/rd/c0d0 3
but then noticed that my /etc/aboot.conf wasn't going to be much help
(not sure if this would have been corrected had the aboot installation
completed, or not). It was:
0:3/vmlinux.gz ro root=/dev/sda2
1:3/vmlinux.old.gz ro root=/dev/sda2
2:3/vmlinux.new.gz ro root=/dev/sda2
3:3/vmlinux ro root=/dev/sda2
I continued the installation without the boot loader, rebooted, and
from SRM loaded up aboot in interactive mode. From there, I did:
aboot> p 2
aboot> i /initrd.img-2.4.26-1-generic
aboot> b 2/vmlinuz-2.4.26-1-generic ro root=/dev/rd/c0d0p3 console=ttyS0
This got me booted up and into my shiny new Sarge installation and a run
of base-config.
--
Nathan Poznick <[EMAIL PROTECTED]>
I won't mention any names, because I don't want to get sun4's into
trouble... :-) -- Larry Wall
signature.asc
Description: Digital signature
