Started to have a go with NetGear MA101

[philb]

Hi,

I'm not really looking for help here unless you can tell me where I'm going wrong without having to do any work yourself. Otherwise I will get there in the end, I always do, but I'm just writing this to remind me what I did.

Anyway, I'm trying to get my MA101 Rev B. to work with Knoppix, so just now I downloaded Oliver Kurth's driver source from http://freshmeat.net/projects/at76c503/ onto my hard disk (using Windows).

Then I booted Knoppix from the CD, and made a new driectory /ramdisk/home/knoppix/atmel and copied the .tar.gz file there from the hard disk and untarred it.

Then I did make which worked fine. Make install didn't work because /lib is on the CD. Therefore I installed the modules using insmod which seemed to work :

knoppix@ttyp0[atmel]$ su
root@ttyp0[atmel]# insmod usbdfu.o
root@ttyp0[atmel]# insmod at76c503.o
root@ttyp0[atmel]# insmod at76c503-rfmd.o
root@ttyp0[atmel]# lsmod
Module Size Used by Not tainted
at76c503-rfmd 39328 0 (unused)
at76c503 48992 0 [at76c503-rfmd]
usbdfu 7572 0 [at76c503-rfmd]

However, running dmesg, things didn't look so good :

bdfu.c: USB Device Fimware Upgrade (DFU) handler v0.10
usb.c: registered new driver usbdfu
at76c503.c: Generic Atmel at76c503/at76c505 routines v0.10
at76c503-rfmd.c: Atmel at76c503 (RFMD) Wireless LAN Driver v0.10
usb.c: registered new driver at76c503-rfmd
usb-uhci.c: interrupt, status 2, frame# 1564
at76c503.c: getting firmware failed with -75, or version is 0
at76c503.c: this probably means that the ext. fw was not loaded correctly
unregister_netdevice: device eth%d/d5d1f800 never was registered
at76c503.c: at76c503_new_device returned NULL

The system knows that the MA101 adapter is there because when I cat /proc/bus/usb/devices, part of the ot put is this :

S: Product=USB UHCI Root Hub
S: SerialNumber=c400
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=fe(app. ) Sub=01 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0864 ProdID=4102 Rev= 1.00
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
E: Ad=85(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

0864 4102 is the right Vendor ID / Product ID. Oh well, too tired to do any more right now, perhaps I'll have another go next weekend,

Cheers,

Phil

[garyng]

do you need to update the source for the device ID as mentioned on the website ? The system's knows the device ID means nothing as it is still up to the driver to decide if it likes that ID. Even if you don't load the driver, "cat /proc/bus/usb/devices", would still show you the same information. I notice that it said driver:none meaning no driver is associated with that device.

[philb]

Hi, yes I appreciate what you're saying, but I just did cat /proc/bus/usb/devices just to check that the USB system driver found the device as if not then the device driver wouldn't stand much of a chance. I juxt checked the driver souces and it does support the ID. I'm just looking through the source now to see where the dmesg error messages come from,

Cheers,

Phil