Problems to get Embedded Linux to network.

[btb]

that seems feasible - it threw up some 'new' errors after I copied in the new files - some of the code was not recognised. I will try your link.

The code in the link I posted appears to be a patch, so I will try and add that manually to both the new and original asix.c


I think I may have to try and source the old style adapter.

You mention you have sucessfully installed a wireless apapter. If I can source the same model, could you assist with what you learnt in getting it to work ?

thanks
btb

[ag]

You mention you have sucessfully installed a wireless apapter. If I can source the same model, could you assist with what you learnt in getting it to work ?

thanks
btb

Hi btb,

Happy to help where I can. My wireless adapter is shown here http://www.ihrschutz24.de/Multimedia/Zubehoer-149/Hyundai-Wireless-LAN-USB-Adapter--HW01.html?refID=16&IhrSchutz24, but I think any USB wLAN stick 802.11G type AB-11102 with Realtek chipset rtl8187 should work as an equivalent.

I can also provide assistance for a USB LAN adapter with dm9601 driver like this one http://de.shopping.com/bigtec-usb-ethernet/eEmilBe1jtN4eJqYbxKnMQ==/info

I dont use the WLAN adapter for the ElektorBoard very much anymore, because it increases the power consumption from less than 1 watt to over 7 watts. That's why I generally use the LAN adapter, which increased the power consumption unmeasureably.

Regards,
Ag'

[btb]

Ag

fix it ! (well, I get eth0 now, and the adapter leds light up)

basically, the new style e100 adapter has an ax88772 chip set, but there was not an asix.c function at:

static const struct usb_device_idproducts

[] =

that matched 88772 with ID 2001,0x1a02


so I ammended the code for E 100 B1 Alternative to read :

// DLink DUB-E100 H/W Ver B1 AlternateUSB_DEVICE (0x2001, 0x1a02),.driver_info = (unsigned long) &ax88772_info,

(it was originally 2001,0x3c05)

make modules and install


i set the static IP address as per the text and can ping myself........
however it now randomly reports the following error:

eth0: asix_rx_fixup() Bad Header Length
eth0: asix_rx_fixup() Bad RX Length 32860


a new problem to solve !

btb

[ag]

Hi btb,

I'm glad I do not own that adapter, and I begin to wonder why Elektor seems to promote it. It seems to riddled with problems.

Good luck

Ag

[btb]

Ag
some sucess
earlier, the board appeared to ping itself but ifconfig -a showed (ie)
Tx pkts =0, Rx errors = 20
pinging from my PC showed "host unreacable"

also the board terminal reported the header length errors as described earlier

using the info in this link: https://lkml.org/lkml/2011/7/26/507

I edited my asix.c code to read:

while (skb->len > 0) {if ((short)(header & 0x07ff) !=    ~((short)((header & 0x07ff) >> 16))) {deverr(dev,"asix_rx_fixup() Bad Header Length");}/* get the packet length */size = (u16) (header & 0x000007ff);

make modules and install

now I can get the board to ping itself with ifconfig -a then reporting Tx 20, Rx 20 , err=0

also I can now ping the board from my PC. I can also get to the server test page "hello world" as per Pt 5 page 27 fig 13.

However, each time I refresh the browser page, the board terminal reports :
eth0: asix_rx_fixup() Bad Header Length.

the board terminal slowly logs random copies of this error too
So, there is still something wrong but not as critical.

I have yet to try your idea about kernel versions - still worth a shot. Any other ideas on this are welcome.

I am hopeful my net connection will hold up and allow me to continue with Pt5 & 6 as is, meatime i will order the other recomended adapters.

thanks
btb

[jima]

Hi All,
I picked up a cheap USB to ethernet adaptor from New Egg. Like you, mine didn't work. I recognized that the adaptor's vendor and product id was missing from the asix.c file as well as my adaptor having an asix ax88772b chip. I googled it and driverscollection.com had version 4.1.0 driver for version 2.6.38 kernel. I renamed all the asix files to .old and copied the new files to the directory. linux-2.6.33-lpc313x/drivers/net/usb. I redid everything exactly as in the article and it all worked. It created the new asix files as necessary. I did notice different driver versions for different kernel versions. Hoe this helps,

Jim

[jeroentje]

Hi all,

First: Thank you btb, because of your post I got my card to work in 10 minutes

I bought a level-1 USB adapter which identifies itself as an asix board but that last digit is different!

So I changed that in asix.c , make modules and only copied the asix module via an usb stick to the board. reload and viola, it sees my board.

For the error message during refresh of webpages -> I removed the lines completely:

//if ((short)(header & 0x07ff) !=
// ~((short)((header & 0x07ff) >> 16))) {
//deverr(dev,"asix_rx_fixup() Bad Header Length");
//}

And that removes the annoying lines on the console. Ok not perfect but as long as you dont connect your board directly onto the internet ... who is going to send you bad header lengths?

Cheers,

Jeroen'

[hala2013]

Thank you

[ashodgson]

I had the same problem with and onboard dm9601 and was about to go out buy and another external device but decided to investigate what was happening.

My first step was to blacklist the module so I could manually install it to diagnose the issue. I added
blacklist dm9601
to /etc/modprobe.d/blacklist.conf

and the rebooted. I was expecting the networking to disappear but instead it used the standard linux network usb driver and it worked perfectly.

Hope this helps others

Andrew