traveler
January 27th, 2005, 12:18 PM
Hi Community,
now after searching the web I could not find a successfull solution to my problem:
I've istalled Ubuntu Warty successfully on my Laptop (Thinkpad x20). After installation, where several updates were installed from the web (?) I booted into the GUI. Unfortunally I have no working Network now.
I suspect Kernel 2.6.8 to not support the 3com card in the Notebook. Why? Well, when I issue
lsmod I can see, that the 3c59x is loaded but not used. Another "hint" for the Kernel was, that after rebooting during system loadup I get a handfull of messages stating:
localhost kernel: eth0: command 0x5800 did not complete! Status=0xffff
Now I know that the Laptop is supportet by the complete Kernel 2.2.x and 2.4.x series since I use Slackware on that Laptop too.
Now my question is: is there anyone who could tell me how to get close to the problem? Or better: solve it :)
Take care
-traveler (from freezing cold Germany *shivvvver*)
http://lists.debian.org/debian-user/2004/09/msg03615.html
Seems to be a known (reported), but yet unsolved problem...
now after searching the web I could not find a successfull solution to my problem:
I've istalled Ubuntu Warty successfully on my Laptop (Thinkpad x20). After installation, where several updates were installed from the web (?) I booted into the GUI. Unfortunally I have no working Network now.
I suspect Kernel 2.6.8 to not support the 3com card in the Notebook. Why? Well, when I issue
lsmod I can see, that the 3c59x is loaded but not used. Another "hint" for the Kernel was, that after rebooting during system loadup I get a handfull of messages stating:
localhost kernel: eth0: command 0x5800 did not complete! Status=0xffff
Now I know that the Laptop is supportet by the complete Kernel 2.2.x and 2.4.x series since I use Slackware on that Laptop too.
Now my question is: is there anyone who could tell me how to get close to the problem? Or better: solve it :)
Take care
-traveler (from freezing cold Germany *shivvvver*)
http://lists.debian.org/debian-user/2004/09/msg03615.html
Seems to be a known (reported), but yet unsolved problem...