d4cnobby


Group: Members
Posts: 6
Joined: Mar. 2004 |
 |
Posted: Aug. 05 2004,14:05 |
 |
Hi, I have tried three versions of DSL on a couple or HP-Compaq d530 PC's (basic 2 Gig Celeron corporate workhorse) without success in the NIC detection department.
The card in question is a 10/100/1000 Mbit/sec embedded (I believe) ethernet device made by BroadCom and designated as a BCM5782 (57xx series).
A Google search widely indicated that the "tg3" driver would be an appropriate driver. This was confirmed by my usage of the 0.2.14 "System Rescue CD" [http://www.sysresccd.org/] on one of these boxes.
That is to say, the "tg3" driver on that utility distro loaded without a hitch, but the same driver on DSL versions 0.5.2 , 0.7.1 and 0.7.3 baulked and didn't load at all :-(
An attempt at "forcing' the issue with "insmod -f tg3" , resulted in complaints about "no suitable device" being found or suchlike ...
- should the driver source be checked and then the driver be recompiled ? - any ideas ?
Peter (not quite so happy about this one)
|