Bug#296738: IBM NetVista fails to identify cdrom with module piix
Package: installation-reports
Debian-installer-version: 20050203 daily build
uname -a: Linux (none) 2.4.27-2-386 #1 Thu Jan 20 10:55:08 JST 2005 i686 unknown
Date: Thu, 24 Feb 2005 13:53:49 +0200
Method: cdrom
Machine: IBM Netvista
Processor: P4, 2.4G
Memory: 1GB
Root Device: IDE, /dev/hda
Root Size/partition table: Nothing special. 30GB disk all in /:
/dev/hda1 * 1 3497 28089621 83 Linux
/dev/hda2 3498 3649 1220940 5 Extended
/dev/hda5 3498 3649 1220908+ 82 Linux swap
Output of lspci and lspci -n:
0000:00:00.0 0600: 8086:2560 (rev 01)
0000:00:02.0 0300: 8086:2562 (rev 01)
0000:00:1d.0 0c03: 8086:24c2 (rev 01)
0000:00:1d.1 0c03: 8086:24c4 (rev 01)
0000:00:1d.2 0c03: 8086:24c7 (rev 01)
0000:00:1d.7 0c03: 8086:24cd (rev 01)
0000:00:1e.0 0604: 8086:244e (rev 81)
0000:00:1f.0 0601: 8086:24c0 (rev 01)
0000:00:1f.1 0101: 8086:24cb (rev 01)
0000:00:1f.3 0c05: 8086:24c3 (rev 01)
0000:00:1f.5 0401: 8086:24c5 (rev 01)
0000:02:08.0 0200: 8086:1039 (rev 81)
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [E]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Create file systems: [ ]
Mount partitions: [ ]
Install base system: [ ]
Install boot loader: [ ]
Reboot: [ ]
Comments/Problems:
Workaround: start the installation in expert mode. disable loading the
module 'piix' when probing for modules to detect the CD. Strangely
enough the module appeared on the list of modules for the network
adapter.
piix still got into the initrd and thus the CD was not accessible after
the boot and thus the CD was not accessible in the installed system.
Luckily for me I did not need the installer at the second boot stage.
The problem seems to also exist in the daily build of 20050223. Both
in kernel 2.4 and in kernel 2.6 of both builds.
--
Tzafrir Cohen icq#16849755 +972-50-7952406
tzafrir.cohen@xorcom.com http://www.xorcom.com
Reply to: