The Elektor Forum will close. See also this link. From Friday March 1st it is no longer possible to log in to the forum. However, the content of the forum will remain visible until the end of March. As of April 1st the forum will definitely go off the air.

Problems to get Embedded Linux to network.

The topic on number crunching

Postby ag » Sun Feb 03, 2013 12:00 am

Hi matias-t,

In your first post, the id was listed as 1a02. Your latest post however, shows 1A02. Linux is generlly case-sensitive, so I suspect that you still have a problem with unmatched id. Not sure why your id has changed from 1a02 to 1A02.

Just to be very sure on this, please check that the id displayed in usb 1-1 agrees with your asix.c / asix.ko file also in regard to case-sensitive.

Regards,
Ag
Ag
ag
 
Posts: 533
Joined: Thu Jan 02, 2014 10:37 am

Postby matias-t » Sun Feb 03, 2013 12:00 am

Hi Ag,

Rather strange. Why there was a bia A. Now, when I removed the adapter and switch back:

root@gnublin:/media#
root@gnublin:/media# usb 1-1: USB disconnect, address 8

root@gnublin:/media# usb 1-1: new high speed USB device using lpc-ehci and address 9
usb 1-1: New USB device found, idVendor=2001, idProduct=1a02
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: DUB-E100
usb 1-1: Manufacturer: D-Link
usb 1-1: SerialNumber: D7545D

root@gnublin:/media#

matias-t
matias-t
 
Posts: 9
Joined: Thu Jan 02, 2014 10:43 am

Postby ag » Sun Feb 03, 2013 12:00 am

Hi matias-t,

Indeed, strange. But I know too little about linux to understand that. If you are sure that your asix.c file is correctly edited, compiled and transferred, then I am at a loss for any further suggestions.

Sorry.

Regards,
Ag
Ag
ag
 
Posts: 533
Joined: Thu Jan 02, 2014 10:37 am

Postby matias-t » Mon Feb 04, 2013 12:00 am

Perhaps the problems are the best school, but also frustrating ... Is your D-Link the same model, which is in Benedikt's article or newer black model?

Regards
matias-t
matias-t
 
Posts: 9
Joined: Thu Jan 02, 2014 10:43 am

Postby ag » Mon Feb 04, 2013 12:00 am

Hi matias-t,

I don't have a D-Link adapter, only a DM9601 (Davidcom). I did however find someone having the same problem with the DUB E-100 in ther german language forum. Apparantly, there is another file which contains the asix product id which also needs to be edited:

drivers/net/usb/asix.mod.c

If you have not already done so, please change
MODULE_ALIAS("usb:v2001p1A00d*dc*dsc*dp*ic*isc*ip*");
into
MODULE_ALIAS("usb:v2001p1A02d*dc*dsc*dp*ic*isc*ip*");

Then again recompile and transfer to SD card. Hopefully that will then do the trick. The above was not necessary for my DM9601 adapter. Credit for this go to joef.

Regards,
Ag
Ag
ag
 
Posts: 533
Joined: Thu Jan 02, 2014 10:37 am

Postby matias-t » Mon Feb 04, 2013 12:00 am

Hi, Ag,

Thank you for your advices! I put it all new from the beginning, and I tried your the most recent guidelines too, but nework do not work.
I think that I need to read the articles Benedict, and then try again.

I do not give up, but maybe I must take a litle break

best regards,
matias-t
matias-t
 
Posts: 9
Joined: Thu Jan 02, 2014 10:43 am

Postby ag » Mon Feb 04, 2013 12:00 am

Hi matias-t,

Sorry that it didn't help As an alternative, I can recommend the DM9601 which I am using. You can get it from Amazon.com for about 10 € inlcluding freight (http://www.amazon.de/gp/product/B005BY7HSS/ref=oh_details_o00_s00_i00), and I would be able to provide first hand experience support

Regards,
Ag
Ag
ag
 
Posts: 533
Joined: Thu Jan 02, 2014 10:37 am

Postby matias-t » Wed Feb 06, 2013 12:00 am

Hi Ag,

thanks for your tip

regards,
matias-t
matias-t
 
Posts: 9
Joined: Thu Jan 02, 2014 10:43 am

Postby btb » Tue Mar 05, 2013 12:00 am

I have the same adapter and the same problem. I've tried everything posted already, to no avail.

I founfd this:
http://www.zeroshell.org/forum/viewtopic.php?p=11473&sid=87f8c9851b3ec6321c6b452071c276b7

On the basis of this, I replaced the asix.c in the toolchain with the version on the adapter product CD (much larger file). I also tried copying over the other 3 files asix.h, axusbnet.c & h into the toolchain.
each time I tried
make clean
make modules_install INSTALL_MOD_PATH=/

root@gnublin:~# modprobe asix
eth%d: read AX_CMD_READ_NODE_ID failed: -110
eth%d: Binding device failed: -110
asix: probe of 1-1:1.0 failed with error -110
usbcore: registered new interface driver asix

subsequent modprobe asix report nothing !



root@gnublin:~# modinfo asix
filename: /lib/modules/2.6.33/kernel/drivers/net/usb/asix.ko
........
alias: usb:v2001p1A02d*dc*dsc*dp*ic*isc*ip*
........

So it is still looking for 1A02, not 1a02, despite editing the .c entries

Im stuck now, cannot progress to the rest of the cousre without a net connection. Any ideas?'
btb
 
Posts: 4
Joined: Thu Jan 02, 2014 10:43 am

Postby ag » Tue Mar 05, 2013 12:00 am

Hi btb,

This is just a shot in the dark, as I don't have the subject adapter to do any testing. Also, I have not been moving about in the linux world very long yet. But... I remember when I had analogous problems with my DM9601, it was recommended to get a version of the driver file (in this case asix.c) which was "as close as possible to your kernel level". I would guess that the files you copied from the CD are probably somewhat newer in regard to supported kernel, so you might be having kernel compatability problems with those files. I would suggest that you get 2.6.33 files (for example, here: http://www.filewatcher.com/m/asix.c.39233-0.html), and then check and if necessary edit to match your adapter id.

Again, just a shot in the dark.

Regards,
Ag
Ag
ag
 
Posts: 533
Joined: Thu Jan 02, 2014 10:37 am

PreviousNext

Return to Microcontrollers & Embedded

Who is online

Users browsing this forum: No registered users and 2 guests