Bug#240179: bug reports
Package: installation-reports
Debian-installer-version: sarge-i386-netinst.iso 25.03.2004
uname -a:
Date: 25.03.2004
Method: Booted from the cd. Didn't get to the network installation part,
see below why.
Machine: Targa XP10 Laptop
Processor: AMD 2500+
Memory: 512 MB DDR
Root Device: internal IDE /dev/hda
Root Size/partition table: 40 GB
Output of lspci:
Base System Installation Checklist:
Initial boot worked: [O]
Configure network HW: [E]
Config network: [ ]
Detect CD: [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Create file systems: [ ]
Mount partitions: [ ]
Install base system: [ ]
Install boot loader: [ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
Okay, this is complicated. As I use a laptop, there is no floppy. And
this is where the story starts. Booting from the CD was no problem, but
then hw detection was started and everything went okay until it came to
"ide-floppy". Installer said smth like "skipping unavailable module
'ide-floppy' " and kept hanging there.
So I booted in expert mode. well, I got it to load my network drivers
(via rhine) and then I had to do "hardware install" again...guess what,
yes, ide-floppy failed again - The syste, was just showing that messaga
and did nothing. I rebooted again and again, trying to catch a debug
output on console (what I didn't manage) and looking into
/lib/modules/... I found out there is no ide-floppy.o...well, I did
touch ide-floppy.o before I started hw detection, didn't help. I did cp
ide-cd.o ide-floppy.o -- didn't help.
Each time the system was hanging and I got more and more frustrated.
maybe this isn't a ide-floppy.o problem. maybe the installer waits for
insmod / modprobe to exit with status 0, but smth goes wrong, and we
hang.
Ah yes, sometimes it was also complaining about ide-probe-mod, that it
couldn't be loaded also.
Well, I hope this helps, if you wish a lspci output, please send me a
mail, then I will try to get one.
Thanks! Tobias
Reply to: