ia64 install report
INSTALL REPORT
Debian-installer-version:
<http://gluck.debian.org/cdimage/testing/netinst/ia64/daily/sarge-ia64-businesscard.iso>
Dated 07-Nov-2003 16:17
uname -a:
Linux (none) 2.4.20-ia64 #1 Tue Oct 14 04:24:27 MDT 2003 ia64 unknown
Date: Sat, 8 Nov 2003 11:40:08 +0000
Method: cdrom boot, businesscard iso
Machine: ia64 bigsur (i2000 proto)
Processor: 2 off itanium-I @ 667MHz
Memory: 1GB
Root Device: SCSI
Root Size/partition table: 2GB, /dev/sdb4, with /dev/sdb1 as efi boot
partition.
Output of lspci:
Base System Installation Checklist:
Initial boot worked: [O]
Configure network HW: [E] had to manually modprobe eepro100
Config network: [O] (dhcp)
Detect CD: [O]
Choose a mirror: [O]
Load installer modules: [O] loaded from CD
Detect hard drives: [O]
Partition hard drives: [ ] parted ran ok, but I used existing partitions
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install the kernel: [O]
Install boot loader: [O]
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
Manually modprobing eepro100 is because ia64 doesn't have e100.o atm,
and discover-data got changed to specify e100 recently. Bug 219513
filed, new kernel expected soon.
Had to boot with TERM_UTF8=no to avoid issue where bterm dies with
SIGILL. Not yet investigated or filed bug. hadn't seen that before as
I'd been testing netboot, which doesn't use bterm.
'Detect hardware' seemed to cause main-menu to die, ps showed a
main-menu in state Z, one in state S, and no menu displayed. Killed the
frontend that was running and got main-menu redisplayed with 'Partition
a harddrive' highlighted. Hadn't seen that with my local built
netboots. Not investigated yet.
Installed sid, because debootstrap is broken for sarge on ia64
(libreadlin4), bug 219655 filed.
Would have liked to use a local mirror, but fix for that is not in this
build.
When "Downloading packages" the dialog box often (but not for all pkgs)
says "Validating %s".
On reboot, console has lots of non-implemented syscall warnings as a
result of the new glibc - bug 219512.
So, still limping along a bit, unfortunately.
Richard
Reply to: