Howto Configure A Usb Ethernet Adaptor

[trichmon]

Tried that, same result.  Does it need some sort of usbnet module?  or is that all supposed to be handled by the pegasus module?

Todd

[Meanie]

I did put the pegasus.o file in the same place on my tosa as you listed.  Below is the dmesg output that talks about this device.  It seems to see it and says the driver is loaded.  I dont get anything with ifconfig -a .


dmesg output:

hub.c: USB new device connect on bus1/1, assigned device number 4
usb.c: USB device 4 (vend/prod 0x846/0x1040) is not claimed by any active driver.
usb.c: registered new driver acm
acm.c: v0.21:USB Abstract Control Model driver for USB modems and ISDN adapters
pegasus.c: v0.4.22 (2001/12/07):Pegasus/Pegasus II USB Ethernet driver
usb.c: registered new driver pegasus


Here is the output of lsmod as well

Module                  Size  Used by    Tainted: P
pegasus                11048   0  (unused)
acm                     5708   0  (unused)
pxa_bi                 21788   0  (unused)
net_fd                 25000   1
usbdcore               34456   0  [pxa_bi net_fd]
mousedev                4496   1
usbdmonitor             5216   0
sharp_mmcsd_m          31492   2
usb_ohci_tc6393        24492   0
usbcore                51984   1  [pegasus acm usb_ohci_tc6393]
#                                                               

Todd
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125485\"][{POST_SNAPBACK}][/a][/div]

Hmm.... well, the drive loads OK, but doesn't actually locate the hardware. Did you try to rmmod the acm module (not sure why it loaded that) before modprobing the pegasus module? Maybe it is blocking it?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125514\"][{POST_SNAPBACK}][/a][/div]

actually, the driver loaded and if you do a

ifconfig -a

you will see eth0 with no IP address assigned to it so that's why it does not show when you do just ifconfig

all you need to do now is to either get dhcp to assign an IP (if you have a working dhcp server) or assign an IP manually

ifconfig eth0 192.168.1.201
you might also need to set some routes and setup resolv.conf, .etc...
all this can be automated using the hotplug mechanism, ie hotplug detects usb thingy being inserted, then loads the required moduile, then configures eth0., etc...

[trichmon]

Thats sort of the problem.  When i ifconfig -a I dont get an eth0 (i only see the lo device).  

Todd

[karlto]

Tried that, same result.  Does it need some sort of usbnet module?  or is that all supposed to be handled by the pegasus module?

Todd
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125515\"][{POST_SNAPBACK}][/a][/div]

Same dmesg? My SL6000 shows the same USB modules loaded with the client USB networking (i.e. via the cradle) running, with the exception of acm and pegasus of course. It appears that net_fd is the device (not host) networking.

I have just noticed something with your earlier posts too - you got the same pegasus message before trying the uploaded module as after (and afterward it loaded acm instead!). Maybe the pegasus driver was already there somewhere (perhaps compiled into the kernel rather than a module), and/or you still aren't using the uploaded one?

May as well try the other modules - attached usbnet.o and CDCEther.o

[trichmon]

your right.  If i modprobe up the pegasus mod you compiled i and when its not running i get the same dmesg.  Also the same with your two new modules.

[Meanie]

your right.  If i modprobe up the pegasus mod you compiled i and when its not running i get the same dmesg.  Also the same with your two new modules.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125528\"][{POST_SNAPBACK}][/a][/div]

you definately need the pegasus module, but I noticed a *tainted* status in the previous posts. this means the module was not compiled with the correct kernel parameters.

[desertrat]

dmesg output:

hub.c: USB new device connect on bus1/1, assigned device number 4
usb.c: USB device 4 (vend/prod 0x846/0x1040) is not claimed by any active driver.
usb.c: registered new driver acm
acm.c: v0.21:USB Abstract Control Model driver for USB modems and ISDN adapters
pegasus.c: v0.4.22 (2001/12/07):Pegasus/Pegasus II USB Ethernet driver
usb.c: registered new driver pegasus

Stabbing in the dark:

I notice that in my /lib/modules/2.4.20/modules.usbmap your vend/prod 0x846/0x1040 is listed as using the module usbnet. In contrast both my usb ethernet adaptors are listed correctly as using pegasus and rtl8150 respectively. Maybe that's the problem?

-- cheers

[trichmon]

my modules.usbmap file does not list those values under vend/prod.  So i added a line with those values, and rmmod the acm.  I have to admit that Im not sure how or why but the modules.usbmap file is regenerated when i reboot the Z.  I have done it twice to be sure.  

Todd

[karlto]

my modules.usbmap file does not list those values under vend/prod.  So i added a line with those values, and rmmod the acm.  I have to admit that Im not sure how or why but the modules.usbmap file is regenerated when i reboot the Z.  I have done it twice to be sure. 

Todd
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125592\"][{POST_SNAPBACK}][/a][/div]

Unfortunately that's sorta jumping the gun - setting this up automates loading the correct driver, but you'll probably want to find one that works first! Maybe you have something compiled into the kernel that is overriding the modules, as the pegasus module doesn't appear to be being used at all (even though it loads). Any depmod errors? usbnet and CDCEther are most likely no use - worth a try, but pegasus is what we want.

The dmesg output without loading pegasus as a module:
- connects the device
- claims that there is no driver loaded for the device
- disconnects the device
- loads a pegasus driver from somewhere
- connects the device again
- claims that there is no driver loaded for the device
==> so the pegasus driver is in nowhere-land!

The dmesg output with the module installed:
- connects the device
- loads a modem driver
- loads the pegasus module driver by manual modprobe
==> but the device still doesn't seem to be under the control of any driver...!

The only other snippet of info I see is that you have driver version 0.4.22, whereas desertrat has v0.4.32. Hardly major though when you consider the tosa kernel is 2.4.18 against the later 2.4.20.

@Meanie: I couldn't see any tainted flags in the posts here; can you elaborate, and how would I fix it?

[trichmon]

Here is a dmesg with the CDCETher, usbnet, and pegasus modules loaded.  Im not sure what is needed so I captured the whole thing.


Thanks
Todd

[karlto]

Here is a dmesg with the CDCETher, usbnet, and pegasus modules loaded.  Im not sure what is needed so I captured the whole thing.


Thanks
Todd
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

I have just done a bit of googling, and I think we're barking up the wrong tree.

Judging by the numbers in your dmesg, you have a Netgear FA120. This needs the ax8817x.o driver, which was introduced in the 2.4.21 kernel. The rtl driver isn't in the tosa kernel either.

I will see if I can find a backported patch for 2.4.18...

[Edit]

There is an RTL driver on this forum! See [a href=\"https://www.oesf.org/forums/index.php?showtopic=10214&st=0&p=89505&#entry89505]this post[/url]. Should work fine for the huf11

The same thread claims to have a backported ax8817 driver somewhere, but also says the USB stack needs backporting as well to compile it! That makes sense because it is a USB 2.0 device. Looking like you might have to abandon the netgear NIC unless an upgraded kernel is available...

[trichmon]

dont mind getting rid of the netgear or ordering a nic that will work.  I grabbed the driver for the huf11 off the other forum and after i insmod it and plug in the nic i get and eth0! Three strange issues the ifconfig lists a starnge mac address for the nic (moslty 00) and the light on the nic does not come on (which it did you before when i plugged it in).  Dhcpcd does not pcikup an address.  Im going to reflash and try again since i have mucked around with my Z so much trying to get the netgear working.


Thanks
Todd

[karlto]

dont mind getting rid of the netgear or ordering a nic that will work.  I grabbed the driver for the huf11 off the other forum and after i insmod it and plug in the nic i get and eth0! Three strange issues the ifconfig lists a starnge mac address for the nic (moslty 00) and the light on the nic does not come on (which it did you before when i plugged it in).  Dhcpcd does not pcikup an address.  Im going to reflash and try again since i have mucked around with my Z so much trying to get the netgear working.


Thanks
Todd
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125715\"][{POST_SNAPBACK}][/a][/div]

Cool - sounds like that's gotten to the bottom of it. I think the MAC address is set by the driver in some instances (because there isn't actually a proper NIC). I imagine with a little bit of fiddling around you'll have it working soon.

[xjqian]

i have the same problem as trichmon encountered. The adpator ed under sharp rom. i didn't find usbnet driver, so I suspect that's the culprit. The previously posted usbnet.ipk was corrupted. Anybody can post usbnet.o (for Tosa) for me?