Bug#227114: 20040108 fails on ia64
Package: installation-reports
Version: 20040108-ia64
Severity: grave
Justification: renders package unusable
Debian-installer-version: http://people.debian.org/~manty/testing/netinst/ia64/20040108/sarge-ia64-netinst.iso
uname -a: 2.4.20-ia64 #1 Mon Jan 5 07:53:11 GMT 2004 ia64
Date: Fri, 09 Jan 2004 13:50:04 -0700
Method: USB Keychain and IDE CDROM
Machine: hp rx2600
Processor: 2x Itanium2
Memory: 6GB
Root Device: SCSI sda
Root Size/partition table: GPT 100MB fat16 (not mounted), ~30G ext3 (/), ~2G swap
Output of lspci: Not available
Base System Installation Checklist:
Initial boot worked: [E] - failed to autoboot. manually running bootloader worked
Configure network HW: [O]
Config network: [O]
Detect CD: [O]
Load installer modules: [E] - failed to load from USB mass storage, worked fine from CD
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [E] - Never got there, couldn't get a kernel installed
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
I was hoping to do an install off of a USB keychain. I'm using a
256MB keychain, partitioned as GPT with a 100MB fat16 partition, and the
rest ext3. I copied the contents of the el-torito image into the fat16
partition and the rest of the CD into the ext3 partition. The system
failed to autoboot when I selected USB for install (the directory and
filename layouts are incorrect for autoboot). I then went to an EFI
Shell and booted manually by typing elilo (I'm using a VGA console for
install). Install went fine till it started looking for a CD. I got it
to look for the install media elsewhere, but it got an error that the
usb-storage module wasn't available.
I gave up on the USB keychain and popped in a CD. In the processes of
installing the base system, I got some unaligned access errors on the
console. These were mainly from main-menu and anna. Really ought to
fix these, use prctl to turn them off or maybe just turn down the dmesg
level to make them not go to the console. I got the base system
installed and selected the install kernel option. It presented a list
of 4 available kernels. Selecting any of them immediately brought me
back to the main menu w/ the "install kernel" option highlighted. I
checked the /target drive, and no kernel was installed. I tried this
several times before I gave up.
I have some concerns about using devfs for the install. I'm told
that after install you will not end up with a devfs system, but I
couldn't get that far to verify. It's confusing to be presented with
SCSI devices as host/bus/target/lun when you're really just expecting
sda. I'm aware of all the naming problems with sdX, but using a
deprecated interface doesn't seem like the way to work around it. My 2
cents. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
Reply to: