Bug#564095: Installation Report - LENNY on HP OmniBook 5700
Boot method: Network install via GRUB boot of HD-Media
Machine: HP OmniBook-5700CT
Processor: Pentium MMX 166 MHz
Memory: 128Mb for install, 32Mb for operation. ( Yes, 32 Meg )
Partitions: <df -Tl will do; the raw partition table is preferred>
$ fdisk -l
Disk /dev/hda: 1358 MB, 1358991360 bytes
255 heads, 63 sectors/track, 165 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000f1b
Device Boot Start End Blocks Id System
/dev/hda1 1 97 779121 83 Linux
/dev/hda2 98 106 72292+ 82 Linux swap / Solaris
/dev/hda3 107 165 473917+ 83 Linux
$ df -Tl
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/hda1 ext3 766848 579448 148444 80% /
/dev/shm tmpfs 14612 0 14612 0% /lib/init/rw
udev tmpfs 10240 552 9688 6% /dev
/dev/shm tmpfs 14612 20 14592 1% /dev/shm
/dev/hda3 ext3 458925 22615 412615 6% /home
Output of lspci -knn (or lspci -nn):
[ Didja know: The 'lspci' function does not appear to exist in a base
install. :-( ]
$ lspci -nn
00:00.0 Host bridge : OPTi Inc. 82C557 [Viper-M] [1045:c557] (rev 14)
00:01.0 ISA bridge : OPTi Inc. 82C558 [Viper-M ISA+IDE]
[1045:c558] (rev 02)
00:02.0 VGA compatible controller : Chips and Technologies F65554
[102c:00e4] (rev c2)
00:03.0 CardBus bridge : Texas Instruments PCI1131 [104c:ac15]
00:03.1 CardBus bridge : Texas Instruments PCI1131 [104c:ac15]
00:14.0 IDE interface : OPTi Inc. 82C621 [Viper-M/N+] [1045:c621]
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [E]
Detect network card: [E]
Configure network: [O]
Detect CD: [ ]
Load installer modules: [E]
Detect hard drives: [O]
Partition hard drives: [E]
Install base system: [O]
Clock/timezone setup: [O]
User/password setup: [O]
Install tasks: [O]
Install boot loader: [O]
Overall install: [E]
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
Initial boot went into "Low Memory" mode, but after the initial
questions were answered, hung at the "Detecting Network Cards" stage
with "0%" completion.
Restarted after installing additional memory to provide 128Mb.
Install again hung at the "Detecting Network Cards" stage with "0%"
completion. Network card was an "SMC 8034TX-56K [PN:99-012014-000]"
multifunction Ethernet/TelephoneModem unit.
pccardctl ident Socket 1:
product info: "PCMCIAs", "Fast Ethernet+56K ComboCard", "", ""
manfid: 0x0143, 0xc0ab
function: 0 (multifunction)
(Why is 'cardctl' now called 'pccardctl' ??)
Again restarted the install after replacing the network card with an
"SMC8041TX V.2" card.
The install proceeded to the Disk Partitioning step, at which point I
hit a wall, as a network install using hd-media does not seem to like
doing a repartition and sizing operation on the disk it is installing
from. My work around was to kill the install, do a manual
repartitioning, sizing, and formatting of the disk using a 'tomsrtbt'
LOAF utility disk. (http://www.toms.net/rb/) I recopied the
installation hd-media to hda3, and restarted the installation process
using a GRUB loader disk.
From this point onward, a 'base system' installation proceeded normally
with the exception of skipping the partitioning and reformatting steps.
I used the previously prepared partitions, manually assigning hda1 to
root ("/") and hda3 to "/home". After the installation was completed,
the boot and hd-media files on hda3 were deleted.
After completing the installation, I found that there was a significant
delay in reboots. Setting edd=off fixed somewhat, but I'm still stuck
with delays at the 30 second mark:
[ 23.039338] EXT3-fs: mounted filesystem with ordered data mode.
[ 30.958299] udevd version 125 started
[ 45.775753] input: PC Speaker as /class/input/input1
[ 50.380868] Yenta: CardBus bridge found at 0000:00:03.0 [0000:0000]
And a significant 2.5 minute delay at the 70 second mark:
[ 67.553521] pcmcia: registering new device pcmcia1.1
[ 68.341328] udev: renamed network interface eth0 to eth1
[ 222.856521] Adding 72284k swap...
It is also interesting to note that after the Base System install,
subsequent reboots using the original networking card (which hung during
the initial install) are automagically discovered and configured during
the boot process.
Further details available upon request...