raygun

Group: Members
Posts: 1
Joined: Feb. 2007 |
 |
Posted: Feb. 03 2007,22:11 |
 |
Quote (roberts @ Jan. 22 2007,12:33) | I suspect that you have DSL v3.2. The new module b44.o is likely causing this problem. Hopefully you have DSL v3.1 or prior. Solution: copy /lib/modules/2.4.26/kernel/drivers/net/b44.o and then perform a depmod -a then modprobe 8139too then a netcardconfig should get you going. |
I was having the same problem as some of the posters here; my ethernet card was spotted and worked fine from the 3.2 Live CD (and from a 3.1 install), but when I installed 3.2 and booted up, the card wasn't even recognized.
I used the 3.1 Live CD to follow the quoted instructions posted by roberts, and now I am able to access the network with no problems in 3.2.
I have an older Gateway computer with a Celeron 331Mhz processor (sorry, I don't know the ethernet card vendor)
|