- it detected the NIC happily,
- prior to the DHCP said it needed the b44 module loaded, good,
- then DHCP failed and when I tried to redetect the hardware b44 was no longer in the list.
I have a wireless onboard NIC on this machine too (it's an Intel Centrino-based laptop) - could this be causing problems? How does a user ensure the appropriate NIC is used for install?
Thanks, Rua HM.
Rua Haszard Morris wrote:
From: Adam Aube <[EMAIL PROTECTED]> Rua Haszard Morris wrote:
> >> I have a BroadCom 4400 NIC that is not being detected, leading to > >> DHCP failing, leading to no additional .debs being available... > > tg3 module contains support for BroadCom net cards
Aha - I just tried doing that - there doesn't seem to be an option "load additional driver modules" (or anything like it) in the sarge installer. Should there be?Cheers - I am guessing that now I simply need to "load additional driver modules" and select tg3 early in the installation.. correct?
Yes - assuming the Sarge installer doesn't find it for you.
I couldn't get to the list of modules that I'm used to seeing in the qoody installer; it tries to autodetect first. When I manually chose it "Detect hardware" again, after the DHCP failed, i was able to choose from a 'list' of modules - but only the one it had detected apparently ("Linux floppy") (which is funny because the machine has no floppy!).
Should I be emailing this to debian-boot as well? I think so... (conesquently there's a little summary above)
Thanks for the help so far, I'm not giving up ! (But I am about to install Knoppix in the meantime)
Cheers, Rua HM.
-- Rua Haszard Morris Software Engineer & Research Assistant MARCS Auditory Laboratories University of Western Sydney http://marcs.uws.edu.au
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
