Bug#230279: Installer report for HP Omnibook 6000
Package: installation-reports
Debian-installer-version: 2004-01-02, ftp://ftp.r-net.sk/pub/linux/debian/dists/sarge/main/installer-i386/current/images/netboot-initrd.gz
uname -a: <The result of running uname -a on a shell prompt>
Date: 2004-01-28, 17:00 CET
Method: network, via PXE from a local machine running Debian Woody
Machine: HP Omnibook 6000
Processor: Intel Pentium III-M 1133 Mhz
Memory: 256MB
Root Device: IDE 30GB
Root Size/partition table:
part1 nfts 8 GB (not mounted)
part2 reiserfs 20 GB (/)
part3 swap 0.8 GB
Output of lspci:
Base System Installation Checklist:
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [ ]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [E]
Install boot loader: [ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
Problems
During hardware detection the installer complained about not being able
to load ide-disk. The disk was however dectected correctly.
deboostrap failed on the base system install. It appears to be because
of some dependency (possibly circular) involving gnutls. I'd paste the
original output from apt here, but my second try at running deboostrap
hosed the list of installed packages, so I don't have it no more.
Also in the deboostrap log was something like "sleep: command not
found". Strange since /target/bin/sleep exists.
Is there a way to convice the installer that deboostrap was successful
and continue with the next step? If there is, I couldn't find it.
Attempting to select "install kernel" just retried the deboostrap again.
(And hosed the list of installed packages, as mentioned above).
Network hardware detection found both eth0 (Intersil PRISM wireless) and
eth1 (Intel eepro100). The network configuration screen is confusing, it
didn't say which interface was which card, had to try DHCP on both until
I figured out that eth1 was the eepro100.
Disk partitioning is confusing. Once you create the partitions you get a
screen that lets you create filesystems. It's not at all obvious here
whether the filesystem names it prints are what it's going to create or
what is already on the disk or in fact if the disk partitioning was
successful.
Example:
I had two NTFS partitions originally. Deleted one of them and kept
part1. Thus part2 which was to be reiserfs got created at the start of
the old (now deleted) NTFS partition. However the partition selector
when creating filesystems was trying to be "smart" and (presumably)
examining the start of the new partition, where it still found NTFS.
This confused the hell out of me since it looked like the fdisk hadn't
done anything.
After re-reading it a few times, checking with the command line fdisk
and dmesg that the change had *really* been made, I realised what was
going on and went and created the new filesystem anyway.
Reply to: