User avatar
Posts: 1098
Joined: Mon Oct 19, 2015 6:21 am
Location: Finland

DM9601 Ethernet HUB's

Sun Jan 03, 2016 3:51 pm

I got one of these Ethernet HUB's. They do not work well with Raspberry Pi's.


Posts: 22019
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: DM9601 Ethernet HUB's

Sun Jan 03, 2016 4:04 pm

karrika wrote:I got one of these Ethernet HUB's. They do not work well with Raspberry Pi's.
Yes that has been documented several times such as




Retired disgracefully..... an uncomplicated life !

Rather than negativity think outside the box !

Posts: 1509
Joined: Mon Nov 28, 2011 10:08 am

Re: DM9601 Ethernet HUB's

Sun Feb 14, 2016 8:02 am

Patches were added yesterday to the dwc_otg driver which means it's now robust against the quirks of the upstream DM9601 driver. Available now via rpi-update if you need it.

Posts: 1
Joined: Sat Mar 19, 2016 9:02 am

Re: DM9601 Ethernet HUB's

Sat Mar 19, 2016 9:04 am

You can find a quick tutorial on how to apply the patch for this issue

Would be nice to have the driver fixed though.

Posts: 351
Joined: Thu Mar 28, 2013 9:19 am
Location: Nottingham, UK

Re: DM9601 Ethernet HUB's

Thu Mar 24, 2016 3:44 pm

I have three of these, if they are the same, having what looks like a power adaptor connection on the opposite side to the USB ports.
They seem to work OK on Jessie 4.1.19-v7+, with one drawback.
They all report the same MAC address, 00:e0:4c:53:44:58, which is problematic if you have more than one on the same network.

For a partial fix for this, I added a pre-up script into /etc/network/if-pre-up.d to iterate through the eth? devices, and on finding a "broken" adaptor, assign a new address to it (which is actually derived from the Pi serial number, like the smsc interface does.

It's not "that" robust, since it only works for the device connected at boot time, and only works for one device on the Pi, but it solved the problem of having multiple Pi zero/DM9601 connected devices on my LAN.

The nuts and bolts of it are simple. Run ifconfig ethX (where X is 0,1, etc). If that succeeds, the adapter exists, so run ifconfig again, and use grep and sed to extract the HWaddr part. Check it against the bad MAC.
If it is the bad MAC, then generate a new mac (again by judicious use of grep/sed on /proc/cpuinfo and the serial number line), and then assign it a new hardware address.

Since ifconfig is now deprecated, I should really work out how to set the new hw address using ip, since all the other stuff is possible....
Steve S
No, I can't think of anything funny that won't offend someone if they want it to...

Return to “Troubleshooting”