How can I install this driver in Ubuntu?

tntcoder · 6 Dec 2009 at 23:48

Can you post the output of 'ifconfig'

You can also confirm the module is loaded with 'sudo lsmod | grep dm9601'

slylittlefox · 7 Dec 2009 at 00:05

tntcoder said:
Can you post the output of 'ifconfig'

You can also confirm the module is loaded with 'sudo lsmod | grep dm9601'

Do what he says and post the results.

Also, jump the gun and do a

Code:

sudo dhclient eth0

after unplugging the USB network dongle and plugging it back in again.

dirtydog · 7 Dec 2009 at 06:44

growse · 7 Dec 2009 at 08:32

Can you post an 'ifconfig -a' as well? That'll list nics that aren't configured as well.

Throw in an 'lsusb' just to check that the kernel's picking the usb device up.

dirtydog · 7 Dec 2009 at 09:12

All the USB stuff I have plugged in is listed there correctly, including apparently the USB network adapter.

.walls · 7 Dec 2009 at 09:52

slylittlefox said:
Do what he says and post the results.

Also, jump the gun and do a

Code:

sudo dhclient eth0

after unplugging the USB network dongle and plugging it back in again.

You'll need an "ifconfig eth0 up" before doing that.

dirtydog · 7 Dec 2009 at 10:42

.walls said:
You'll need an "ifconfig eth0 up" before doing that.

Tried this, it gives the same error as above:

Code:

eth0: ERROR while getting interface flags: No such device

Outcast · 7 Dec 2009 at 11:33

I'll bet it's something as simple as right clicking the net connection icon and selecting Eth1 (EthZERO) is onboard.

dirtydog · 7 Dec 2009 at 14:37

Net connection icon, do you mean this?

growse · 7 Dec 2009 at 16:02

dirtydog said:
*img*

All the USB stuff I have plugged in is listed there correctly, including apparently the USB network adapter.

This is a fairly big pointer that the module's not loading properly, or the kernel's not recognising it as a NIC. It's pointless doing any commands involving the mythical eth0, if eth0 doesn't exist.

Unfortunately, I'm out of ideas as to figuring out what's going wrong when the module gets loaded. Perhaps there's some debug output somewhere, or somehow?

dirtydog · 7 Dec 2009 at 16:14

Pass. From the thread at the Ubuntu forums it seems this device really ought to work out of the box, all that should be required is to plug it in.

.walls · 7 Dec 2009 at 17:53

growse said:
This is a fairly big pointer that the module's not loading properly, or the kernel's not recognising it as a NIC. It's pointless doing any commands involving the mythical eth0, if eth0 doesn't exist.

Unfortunately, I'm out of ideas as to figuring out what's going wrong when the module gets loaded. Perhaps there's some debug output somewhere, or somehow?

Seconded - although, I was merely pointing out that before assigning the nic to dhcp, you need to bring it up first. I was actually expecting the nic to have an odd device name similar to the way that atheros do (ath0 anyone?), hence the suggestion of what's in dmesg.

lsusb is quite clearly showing that the device is recognised - but without even some kind of log output, any suggestions we make are as useful as a fart in a hurricane!

dirtydog · 7 Dec 2009 at 18:01

Is there anything else I should do at this point or is everyone flummoxed?

enragedchip · 7 Dec 2009 at 21:37

It would seem that the assumption so far has been that your connection will be eth0, it could be eth1 etc

do a

Code:

dmesg | grep eth

that will show all eth devices the kernel sees

then do as previously mentioned with ifconfig and dhclient

dirtydog · 8 Dec 2009 at 06:46

I did dmesg | grep eth and nothing happened, there was no report or anything, it just went straight back to the next command prompt. I take it this means the kernel is not seeing any ethernet devices then.

memyselfandi · 8 Dec 2009 at 08:26

I'd suggest the following:

Make sure the kernel module is loaded

modprobe dm9601

Check that it is loaded

lsmod | grep -i dm9601

Then re-plug the USB device and post here the last 30 or lines from the output of

dmesg

That should hopefully give some indication on what is going on

dirtydog · 8 Dec 2009 at 09:34

Okay did all that

then removed and reinserted the device, this is the latter output of dmesg...

.walls · 8 Dec 2009 at 09:45

Ok, so it's registering the device and picking the right module.... but it's not being recognised as an ethernet card.... which means that the driver isn't right for this device... which kind of sucks.

I've had similar issues in the past with a wireless card which didn't work on a specific kernel version. Your choices: try a different kernel version (booting from a livecd is the easiest), use ndiswrapper, erm... get a different card*

* Not really a solution, I know...

dirtydog · 8 Dec 2009 at 09:53

I do have a PCI ethernet card which I suspect will be detected and will work without issues, but the reason I don't use it is because I need to keep the PCI slot free because of my graphics card. And my onboard ethernet is dead!

I may elect to buy another motherboard as the best solution to this problem

.walls · 8 Dec 2009 at 10:26

dirtydog said:
I do have a PCI ethernet card which I suspect will be detected and will work without issues, but the reason I don't use it is because I need to keep the PCI slot free because of my graphics card. And my onboard ethernet is dead!

I may elect to buy another motherboard as the best solution to this problem

Possibly a bit overkill - like I said, try a different kernel or two before committing money!