Fraser Campbell wrote: > I do still have syslog output in /var/log/debian-installer/syslog, here's the part > that I think might be relevant: > Oct 16 03:44:08 (none) user.notice hw-detect: Trying to load module 'pcnet32' > Oct 16 03:44:08 (none) user.notice hw-detect: Could not locate driver 'pcnet32' for 'Advanced Micro Devices [AMD] 79c970 [PCnet LANCE]'. > Oct 16 03:44:08 (none) user.debug frontend: --> FSET hw-detect/not_included seen false > Oct 16 03:44:08 (none) user.debug frontend: <-- 0 false > Oct 16 03:44:08 (none) user.debug frontend: --> SUBST hw-detect/not_included CARDNAME Advanced Micro Devices [AMD] 79c970 [PCnet LANCE] > Oct 16 03:44:08 (none) user.debug frontend: Adding [CARDNAME] -> [Advanced Micro Devices [AMD] 79c970 [PCnet LANCE]] > Oct 16 03:44:08 (none) user.debug frontend: <-- 0 > Oct 16 03:44:08 (none) user.debug frontend: --> SUBST hw-detect/not_included MODULE pcnet32 > Oct 16 03:44:08 (none) user.debug frontend: Adding [MODULE] -> [pcnet32] > Oct 16 03:44:08 (none) user.debug frontend: <-- 0 > Oct 16 03:44:08 (none) user.debug frontend: --> INPUT low hw-detect/not_included > Oct 16 03:44:08 (none) user.debug frontend: <-- 30 question skipped So the problem is it doesn't display the message as your debconf priority is too high. Probably the one time you saw it repeated failures had pushed the priority down to low. If it had not found any interfaces, there would have been an error displayed about that, but since it did find one, you probably saw no message at all. I see how that could be confusing, you wouldn't know which ethernet interfaces was being used unless you paid careful attention when it was detecting the hardware. But we don't want to bother users with only one card that is detected properly. Tricky. > > > When first trying to partition harddrive nothing seemed to be happening, > > > pressing enter moved the screen up a line but didn't wake anything up. > > > After 2-3 minutes I pressed CTRL-C. I had done the full hardware > > > detection prior to trying this and had confirmed that the disk was > > > detected ... at least /proc/ide/hda/ existed. After cancelling the first > > > try I immediately went back in to partitioning my disk was listed as > > > available. > > > > I have filed a bug report on this. The syslog would probably be useful > > here too. It would be good to know if you can reproduce it. It would > > I can reproduce it, I did at least two installs and had the same behaviour on each. > > > also be good if you could try a daily build with hw-detect 0.46 on it, > > this has some fixes for IDE drives, though it might not apply to yours. > > Are there prebuilt floppies I can use for that? I tried building the installer myself > but it seemed to want to install some udebs that conflicted with packages on my > host system. If you can point me to a download location for these images I'll give > them a try. That is in the archive now so it should be picked up by the next daily build. If you look at the stats.txt file in the daily build directory, you can find the entry for the floppy image, and it will include the version of hw-detect in there, just to be sure. -- see shy jo
Attachment:
signature.asc
Description: Digital signature