I already had that version installed, before you made the changes you mentioned today. ???

Yea sorry uninstall it and just re-install again. I made two code changes in one script to fix the multiple "disconnect disconnect!" dialog problem and I didn't bother to change the version number because I would have had to have gone through and updated all the links again and I didn't want to do that until I knew for sure that we'd fixed things...

Ok, uninstalled and reinstalled, and the behavior certainly changed... at first just not for the better.

With my Targus hub, the connection to WIRED is still made automatically, but the internet connection does not work off the bat (cannot load web pages).

With the Targus hub and the 2 dongles, executing /usr/sbin/usbEthUp.sh results in:

udhcpc (v0.9.9-pre) started
socket failed: Operation not permitted

But of course, entering "sudo gainroot" and then rerunning the script was successful on the Targus hub.

So far the connection manager isn't so chatty-- I only see the disconnect dialog when I unplug the cat6 cable, as expected.

Thanks!

Okay that's a step in the right direction.

If you want to make the usbEthUp launch automatically for your targus/any other device, you just need to add an entry to the Udev rules. You can usually find the vendor and product ID values listed in your dmesg output, then it's simply a matter of adding a new rule to /etc/udev/rules.d/z98_usbEth.rules.

For example, the two entries right now read:

#UDEV rules to bring up and shutdown Eth0 interface when USB network adapter is connected/removed
SUBSYSTEMS=="usb", ATTRS{idProduct}=="8150", ACTION=="add", RUN+="/usr/sbin/usbEthUp.sh"

SUBSYSTEMS=="usb", ACTION=="remove", RUN+="/usr/sbin/usbEthDown.sh"


As you can see, it runs usbEthUp.sh anytime a usb device with a product ID of 8150 is attached. If you check your dmesg look for a section that talks about device and product (i.e. with my USB100M it says "device v0bda p8150 is not supported") like this:


usb 1-1: new full speed USB device using musb_hdrc and address 9
[13538.375000] usb 1-1: ep0 maxpacket = 8
[13538.375000] usb 1-1: default language 0x0409
[13538.390625] usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=3
[13538.390625] usb 1-1: Product: Linksys USB LAN Adapter
[13538.390625] usb 1-1: Manufacturer: Linksys
[13538.390625] usb 1-1: SerialNumber: 2603
[13538.390625] usb 1-1: device v0bda p8150 is not supported
[13538.390625] usb 1-1: uevent
[13538.390625] usb 1-1: usb_probe_device

The "p8150" is what you're after; p means productID, and 8150 is the 4 digit string. Your targus should have a similiar line in the output, but it'll have different device v (vendor) and p (productID) values. Take the 4 digit number after the p, and add it to your udev rules entry. So if the number was say 5555, then you would simply add this to the end of the existing z98_usbEth.rules:


SUBSYSTEMS=="usb", ATTRS{idProduct}=="5555", ACTION=="add", RUN+="/usr/sbin/usbEthUp.sh"

Then next time you connect the targus it will automatically launch the usbEthUp script for you as root.

Thanks,
-Rob

Well I managed to get some tests in with that other old cheapie USB adapter that I had kicking around, and I'm not sure what's changed but Diablo has definately made a signficant difference to making it work. With the latest USB LAN installed I simply connected it to my OTG swivel, the cat.5e cable and then plugged the whole shebang into the N800 and did a quick dmesg check and sure enough all of the errors and problems that I'd seen on Chinook were gone! I grabbed the product ID as described in my previous post, added it to the udev rules and disconnected/reconnected the OTG adapter and everything just worked. What's even more interesting is that the one I have here although visually identical identifies itself as an ADM8511 Pegasus II chipset, so not even the RTL one and it still seems to work fine. It took a little bit to get an IP (about 10-20 seconds after plugging it in I noticed my SIP connection came up), but after that worked just fine. I tried it for about 20 minutes and no drops or other odd behaviour.

Definitely something to do with Diablo updates though as I tried it on my other N800 that's still running Chinook and it went back to the original haphazzard buggy behaviour I had reported before! So there's hope yet... One thing I did notice is that it draws more power than the USB100M though... on this Pegasus dmesg told me there was 15mA power budget left, and with the USB100M I know there's usually more than that... but that's not a big concern as if you're going to have a LAN cable plugged in, you're probably going to have a charger connected as well. My charger's not here at the moment but I'll try to check that later this evening to make sure connecting it doesn't disrupt anything (hasn't done in the past for me...).

Thanks,
-Rob

Unfortunately dmesg does not appear to provide sufficient granularity for the Targus hub; it identifies that a usb hub of some sort is attached, and it has several ports, but does not go into enough detail. :/

FYI, the Targus hub has 2 regular usb ports, 2 high-powered usb ports, 1 vga port, 1 com port, 1 ethernet port, 1 earphone jack and one microphone jack.

EDIT: just tested the cheap blue dongles, results are--

-dmesg reports dongle as Davicom DM9601 USB Ethernet
-out of 4 dongles purchased, 2 are able to reliably achieve a connection and enable internet browsing

It looks like the other 2 "want" to connect, but their inability points toward the flakiness ascribed earlier to these cheap devices. They're technically capable, but apparently the "QC PASSED" sticker is just for show.

Also, I'm not sure what happened, but now the SMC dongle works! So I have 4 working devices. In fact the SMC outperforms the others (I'm not surprised).

EDIT 2: I think I'll tack on a list of tested devices to the wiki article. Seems to me the format should be something like:

-Device name/model
-chipset
-functionality (works well, doesn't work, partially works, etc)
-unique aspects

EDIT 3: three devices added to end of wiki article

Edit: WRT the Targus hub:
You should see a hub (or two) with several devices connected to its ports; is it bombing with some problem from the first hub, before it can look at the downstream ports?

It's not bombing at all now.

But regardless, I can't see any meaningful ethernet info, nor do I know how to drill down into it...

Good news! I managed to get the Targus hub info using dmesg (not sure why it worked better this time) and also dug out vendor/product info for the 3 devices I've tested.

Updated wiki article at http://www.internettablettalk.com/wi...de_and_OS_2008

Also, I have bid on 2 more cheap dongles to test. If the ebay price stays low I'll go ahead and buy them, test and provide further data.

Update: I won a Netgear EA101C USB Wired Ethernet Adapter for 99 cents plus $4.80 in shipping.

Hey, this is very nice!

I saw this thread this morning and went out and picked up an adapter (Trendnet TU-ET100C). It's Pegasus-based, so after a bit of dmesg digging and adding a UDEV rule for product 8511 as described above, it's working like a charm via dhcp.

Now for the $16 question (that's what the adapter cost): What do I have to change to get it to use a static IP? Necessary for my usage pattern for it to always have the same IP, but I can't set up dhcp to always assign that IP.