The only thing I can suggest is to keep an eye on your dmesg while connecting dongles and testing things out; the debug information that appears there can appear a bit cryptic at times but it will help you get to the bottom of what's actually going on. I'd try doing a few tests with the docking station/hub first just by having an xterm window open, doing a dmesg to get your baseline (find out what the last point in the log was before you connect anything), plug in the dock, check dmesg again for any erronious messages (usually things that say "error", "failed", "insufficient", "unknown", etc). Then try connecting the power adapter and check dmesg again; my bet would be that you'll see some kind of error message appear when you connect the adapter...

As for the dongles, which ones are you trying to use?

-Rob

It was the one in this post: http://www.internettablettalk.com/fo...2&postcount=80

Oh no... I wish I'd noticed that post! Those definately don't work... I got one a few months back that was branded as an N-Gear product, but exactly the same thing... blue transparent plastic, round-sh shaped plastic box that it came in... yea, it's a piece of junk. In my experiments I needed a powered USB hub to even get it recognized... then it turns out that the manufacturer ID is actually invalid, so the only way to get the driver to actually recognize it is to modify the original kernel driver source code and add in the manufacturer and unit ID's to the list that's there... and after all of that, the stupid thing still only worked about 50% of the time... it would cut in and out, do randomly odd things... in general I came to the conclusion that instead of paying 10 bucks for a piece of... I'd just pay 30 and get a proper Linksys one. Well worth it in my mind. Not sure what that other poster was talking about, and maybe they've legitimately fixed the chip ID problem, but this is yet another one of those "you get what you pay for" scenarios as far as I'm concerned.

Check your dmesg outputs though and see... perhaps it's not the same problems that I ran into... but it does sound awfully familiar...

-Rob

Wow, great. Maybe the poster was a shill for the product. Eh, live and learn.

updated to diablo 36-5 and still doesnt work. if i run usbethup i get the wired connection but i cant go on the internet with it

after unplugging everything and running the usbethdowb script im getting a popup window every 30 secs that says "current internet connection will be ended. disconnect?" as if i were trying to disconnect my wireless connection. D: help

I just tried on a different adapter, the SMC EZ Connect USB model 2202USB/ETH... it fails with the following error:

line 53: udhcpc: not found

Oh and dog-- I get the same "connection will be ended" popup all the time now, regardless of connection type. It also doesn't matter how much charge is in the device.

i have an SMC 2208USB/ETH

man i'm getting killed by this pop up D: after rebooting device these guys are coming at me two at a time.

That's what happens when i use the usbethdown script. >_>

Since i don't know how to end the script i renamed usbethdown.sh to usbethdown.sh1. I hope this stops the pop ups. so far i think it's successful

Okay I fixed the script error that was causing that continuous "disconnect" message to pop up, so just remove your current USB LAN package and re-install, should take care of it. Under normal circumstances it was not a problem, but when the tablet and USB devices get into a fight with each other then they keep toggling on/off which causes the disconnect message to continously come up; I've put some lock files in place so that it should only appear once, but it may not be perfect since I can't reproduce the problems you guys are having (lack of the hardware you're using), but hopefully it will take care of at least that little annoyance.
I've also updated the paths for udhcpc so that it should work when you call the scripts manually.

Give it another go guys and let me know.

Thanks,
-Rob

Thanks Rob. But where is the download location? FYI, various download links for both the driver deb and the dbus scripts in wiki and posts present differing versions... and I don't see an updated version of the scripts on any of them.

Sorry, download for the latest version (0.4.6) is here:
http://www.electronicproductonline.c....4.6_armel.deb

I've updated all the wiki entries to make sure they reflect this verison, if you see one somewhere else that needs to be changed let me know.