maemo.org - Talk - Usb NIC problem

maemo.org - Talk (https://talk.maemo.org/index.php)

- Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)

- - Usb NIC problem (https://talk.maemo.org/showthread.php?t=66667)

Hi,

I bought cheap no-name card on auction and I'm trying to make it work with N900 using h-e-n full speed hostmode. Card seems to be reconized but no interface is created.

Here is dmesg output:

Code:

[15315.749542] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2

[15321.371368] usb usb1: usb resume

[15321.390014] hub 1-0:1.0: hub_resume

[15321.390075] hub 1-0:1.0: port 1: status 0101 change 0001

[15321.499511] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[15321.499572] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s

[15321.624511] usb 1-1: new full speed USB device using musb_hdrc and address 75

[15321.772918] usb 1-1: ep0 maxpacket = 8

[15321.773895] usb 1-1: default language 0x0409

[15321.775848] usb 1-1: uevent

[15321.776062] usb 1-1: usb_probe_device

[15321.776123] usb 1-1: configuration #1 chosen from 1 choice

[15321.779876] usb 1-1: adding 1-1:1.0 (config #1, interface 0)

[15321.780212] usb 1-1:1.0: uevent

[15321.781951] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '075'

[15321.782623] usb 1-1: New USB device found, idVendor=0fe6, idProduct=8101

[15321.782653] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=3

[15321.782714] usb 1-1: Product: USB Network Controller

[15321.782745] usb 1-1: SerialNumber:

[15321.782775] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[15321.782867] hub 1-0:1.0: port 1 enable change, status 00000103

Nokia-N900:~# ifconfig

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:32 errors:0 dropped:0 overruns:0 frame:0

TX packets:32 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:1390 (1.3 KiB) TX bytes:1390 (1.3 KiB)



phonet0 Link encap:UNSPEC HWaddr 15-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00

UP POINTOPOINT RUNNING NOARP MTU:4000 Metric:1

RX packets:3435 errors:0 dropped:0 overruns:0 frame:0

TX packets:126 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:100

RX bytes:123284 (120.3 KiB) TX bytes:1978 (1.9 KiB)



Nokia-N900:~#

I tryed to plug card in my ubuntu machine and seems work fine:

Code:

[124331.852181] usb 2-2: new full speed USB device using uhci_hcd and

address 4

[124332.039608] usb 2-2: configuration #1 chosen from 1 choice

[124332.076971] eth1: register 'dm9601' at usb-0000:00:1d.0-2, Davicom

DM9601 USB Ethernet, 00:10:14:02:21:7d

[124332.431275] eth1: link down

[124332.446918] ADDRCONF(NETDEV_UP): eth1: link is not ready

korek@misio:~$ ifconfig



eth1      Link encap:Ethernet  HWaddr 00:10:14:02:21:7d

         UP BROADCAST MULTICAST  MTU:1500  Metric:1

         RX packets:0 errors:0 dropped:0 overruns:0 frame:0

         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

         collisions:0 txqueuelen:1000

         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Can some one help me to make it work?

Re: Usb NIC problem

Off-hand, I'd say the driver is missing from the kernel: even the power kernel doesn't have EVERYTHING compiled in it as it would eat too much memory and slow things down. If Titan or someone else can confirm it, this means you'll just have to compile your own kernel, assuming this driver will compile on ARM. You may also be able to get away with just compiling a module by itself in Scratchbox, Easy Debian, or (sounds hardest) cross-compiling openly in your Ubuntu box.

Mike

Re: Usb NIC problem

It was my first guess to. But this line makes me wonder:

Code:

[15321.781951] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '075'

Do you know what this thing mean?

Re: Usb NIC problem

Can some one tell me how to find what kind of driver is my ubuntu using for that network card,
I would try to compile module then.

Re: Usb NIC problem

Try using lsmod?

Re: Usb NIC problem

Quote:

Originally Posted by hardkorek (Post 893799)

Can some one tell me how to find what kind of driver is my ubuntu using for that network card,
I would try to compile module then.

you need dm9601.ko driver for Davicom . i tried compile for but i get error ( unknown symbol ) when insmod the module.
need more attention for that. when i will have some time i will try again. curiously on same setup i compiled pl2303.ko driver with success.

Re: Usb NIC problem

Quote:

Originally Posted by kureyon (Post 893933)

Try using lsmod?

How to check it if it would be compiled in to kernel? I'm just courious.

Quote:

Damn, if you have a probems with it i'll fail as well. I'm noob in driver stuff.
If you would successfully compile it can you post step by step instruction.

I'll try tommorow anyway.

Re: Usb NIC problem

When I tried out h-e-n with my Belkin USB ethernet adapter I found that I needed a cable plugged in and linked *before* applying vbus and enumerating:

http://talk.maemo.org/showthread.php...941#post883941

Re: Usb NIC problem

connect the device (lan cable too), start h-e-n, high speed, vbus boost on, enumerate.
open terminal, and as root : udhcpc

Re: Usb NIC problem

@hardkorek here is your driver. i modprobe-it but not tested because i don't have davicom device

Re: Usb NIC problem

Great, thank you. I'll test it right now.

Update:

I tested it. I was also able to insert module but i have following errors:

Highspeed

Code:

[ 1193.618743] usbcore: registered new interface driver dm9601

[ 1218.436950] kb_lock (GPIO 113) is now closed

[ 1218.617126] kb_lock (GPIO 113) is now open

[ 1230.236175] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2

[ 1237.265350] Forced hostmode error: no device attached

[ 1237.265441] usb usb1: usb resume

[ 1237.288513] hub 1-0:1.0: hub_resume

[ 1237.288574] hub 1-0:1.0: port 1: status 0101 change 0001

[ 1237.397735] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[ 1237.397796] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s

[ 1237.522705] usb 1-1: new high speed USB device using musb_hdrc and address 2

[ 1237.647796] usb 1-1: device descriptor read/64, error -71

[ 1237.882171] usb 1-1: device descriptor read/64, error -71

[ 1238.116577] usb 1-1: new high speed USB device using musb_hdrc and address 3

[ 1238.241546] usb 1-1: device descriptor read/64, error -71

[ 1238.475982] usb 1-1: device descriptor read/64, error -71

[ 1238.710296] usb 1-1: new high speed USB device using musb_hdrc and address 4

[ 1239.132110] usb 1-1: device not accepting address 4, error -71

[ 1239.257354] usb 1-1: new high speed USB device using musb_hdrc and address 5

[ 1239.679077] usb 1-1: device not accepting address 5, error -71

[ 1239.679199] hub 1-0:1.0: unable to enumerate USB device on port 1

[ 1239.679260] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 1239.679321] hub 1-0:1.0: port 1 enable change, status 00000501

Full speed:

Code:

[ 2134.070220] WARNING: at /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/musb/musb_host.c:128 musb_h_tx_flush_fifo+0x94/0xcc()

[ 2134.070281] Could not flush host TX0 fifo: csr: 000a

[ 2134.070281] Modules linked in: dm9601 usbnet vfat fat sd_mod scsi_mod iphb rfcomm panic_info_buff sco l2cap ext3 omaplfb jbd pvrsrvkm bridgedriver ipv6 g_file_storage uinput board_rx51_camera et8ek8 omap_previewer_hack omap34xxcam_mod isp_mod iovmm videobuf_dma_sg videobuf_core omap3_iommu iommu2 iommu dspbridge mmc_block ssi_mcsaab_imp phonet cmt_speech omap_hsmmc wl12xx smc91x mii omap_ssi omap_wdt hci_h4p mmc_core nokia_av mac80211 tsc2005 crc7 bluetooth fmtx_si4713 ad5820 rtc_twl4030 lis302dl videodev v4l1_compat compat_ioctl32 leds_twl4030_vibra leds_lp5523 adp1653 smia_sensor twl4030_wdt tsl2563 led_class rtc_core smiaregs v4l2_int_device joydev cifs

[ 2134.070861] [<c0030470>] (dump_stack+0x0/0x14) from [<c0057444>] (warn_slowpath+0x64/0x80)

[ 2134.070953] [<c00573e0>] (warn_slowpath+0x0/0x80) from [<c01e9a60>] (musb_h_tx_flush_fifo+0x94/0xcc)

[ 2134.071044]  r3:00000000 r2:c0349b67

[ 2134.071075]  r6:d80ab100 r5:0000000a r4:0000000a

[ 2134.071105] [<c01e99cc>] (musb_h_tx_flush_fifo+0x0/0xcc) from [<c01ea930>] (musb_cleanup_urb+0xc0/0x10c)

[ 2134.071197] [<c01ea870>] (musb_cleanup_urb+0x0/0x10c) from [<c01eb134>] (musb_urb_dequeue+0x1dc/0x248)

[ 2134.071258] [<c01eaf58>] (musb_urb_dequeue+0x0/0x248) from [<c01cec9c>] (unlink1+0x108/0x114)

[ 2134.071319] [<c01ceb94>] (unlink1+0x0/0x114) from [<c01cfc38>] (usb_hcd_unlink_urb+0x9c/0xf8)

[ 2134.071411] [<c01cfb9c>] (usb_hcd_unlink_urb+0x0/0xf8) from [<c01d0af4>] (usb_kill_urb+0x84/0x14c)

[ 2134.071472]  r7:cdf44900 r6:cdf44900 r5:cf0a6000 r4:00000000

[ 2134.071533] [<c01d0a70>] (usb_kill_urb+0x0/0x14c) from [<c01d1d78>] (usb_start_wait_urb+0x80/0x120)

[ 2134.071594]  r6:00001388 r5:cf0a7e50 r4:00000000

[ 2134.071655] [<c01d1cf8>] (usb_start_wait_urb+0x0/0x120) from [<c01d1ff8>] (usb_control_msg+0xc4/0xe8)

[ 2134.071716] [<c01d1f34>] (usb_control_msg+0x0/0xe8) from [<c01cacec>] (hub_port_init+0x3d8/0x634)

[ 2134.071807] [<c01ca914>] (hub_port_init+0x0/0x634) from [<c01cc3e4>] (hub_events+0x86c/0xe64)

[ 2134.071868] [<c01cbb78>] (hub_events+0x0/0xe64) from [<c01ce034>] (hub_thread+0x30/0x19c)

[ 2134.071929] [<c01ce004>] (hub_thread+0x0/0x19c) from [<c006da90>] (kthread+0x54/0x80)

[ 2134.071990]  r6:00000000 r5:c01ce004 r4:00000000

[ 2134.072052] [<c006da3c>] (kthread+0x0/0x80) from [<c005a950>] (do_exit+0x0/0x7bc)

[ 2134.072113]  r5:00000000 r4:00000000

[ 2134.072143] ---[ end trace 605768102227b096 ]---

[ 2134.082702] usb 1-1: khubd timed out on ep0out len=0/0

[ 2136.764282] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2

[ 2136.944580] usb 1-1: device not accepting address 4, error -71

[ 2136.944671] hub 1-0:1.0: unable to enumerate USB device on port 1

[ 2136.944732] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 2136.944763] hub 1-0:1.0: port 1 enable change, status 00000501

[ 2137.157714] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 2137.157775] hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s

[ 2137.311767] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101

[ 2137.436859] usb 1-1: new full speed USB device using musb_hdrc and address 5

[ 2137.585235] usb 1-1: ep0 maxpacket = 8

[ 2137.586242] usb 1-1: default language 0x0409

[ 2137.588104] usb 1-1: uevent

[ 2137.588287] usb 1-1: usb_probe_device

[ 2137.588348] usb 1-1: configuration #1 chosen from 1 choice

[ 2137.594024] usb 1-1: adding 1-1:1.0 (config #1, interface 0)

[ 2137.594390] usb 1-1:1.0: uevent

[ 2137.596038] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '005'

[ 2137.596740] usb 1-1: New USB device found, idVendor=0fe6, idProduct=8101

[ 2137.596771] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=3

[ 2137.596801] usb 1-1: Product: USB Network Controller

[ 2137.596832] usb 1-1: SerialNumber: 

[ 2137.596893] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 2137.596954] hub 1-0:1.0: port 1 enable change, status 00000103

udhcpc in both cases:

Code:

Nokia-N900:~# udhcpc 

udhcpc (v0.9.9-pre) started

SIOCGIFINDEX failed!: No such device

Re: Usb NIC problem

according datasheet davicom dm9601 is full speed device
start with davicom adapter plugged to n900

try
echo -1 >/sys/module/usbcore/parameters/autosuspend
or
echo 2 >/sys/module/usbcore/parameters/autosuspend

Re: Usb NIC problem

Code:

[10468.066375] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2

[10469.498474] usb usb1: usb resume

[10469.515258] hub 1-0:1.0: hub_resume

[10469.515350] hub 1-0:1.0: port 1: status 0101 change 0001

[10469.624938] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[10469.624969] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s

[10469.750305] usb 1-1: new full speed USB device using musb_hdrc and address 26

[10474.749877] usb 1-1: khubd timed out on ep0in len=0/64

[10479.749694] usb 1-1: khubd timed out on ep0in len=0/64

[10484.749755] usb 1-1: khubd timed out on ep0in len=0/64

[10484.874694] usb 1-1: device descriptor read/64, error -110

[10489.984100] usb 1-1: khubd timed out on ep0in len=0/64

Nokia-N900:~# cat /sys/module/usbcore/parameters/autosuspend

-1

-----------------------------------------------------------

Nokia-N900:/dev# ls | grep usb

usbdev1.1_ep00

usbdev1.1_ep81

usbmon0

usbmon1

-----------------------------------------------------------

Nokia-N900:/dev# ls /sys/class/net

lo        phonet0   wlan0     wmaster0

-----------------------------------------------------------

Nokia-N900:/dev# ifconfig

lo        Link encap:Local Loopback  

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:3755 errors:0 dropped:0 overruns:0 frame:0

          TX packets:3755 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0 

          RX bytes:220825 (215.6 KiB)  TX bytes:220825 (215.6 KiB)



phonet0   Link encap:UNSPEC  HWaddr 15-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  

          UP POINTOPOINT RUNNING NOARP  MTU:4000  Metric:1

          RX packets:7226 errors:0 dropped:0 overruns:0 frame:0

          TX packets:881 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:100 

          RX bytes:526868 (514.5 KiB)  TX bytes:42504 (41.5 KiB)



wlan0     Link encap:Ethernet  HWaddr 34:7E:39:4A:47:F2  

          inet addr:192.168.1.102  Bcast:192.168.1.255  Mask:255.255.255.0

          inet6 addr: fe80::367e:39ff:fe4a:47f2/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:9953 errors:0 dropped:0 overruns:0 frame:0

          TX packets:7796 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:9743450 (9.2 MiB)  TX bytes:903025 (881.8 KiB)



wmaster0  Link encap:UNSPEC  HWaddr 00-1F-DF-57-C9-2E-00-00-00-00-00-00-00-00-00-00  

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

It's still not creating interface.

Re: Usb NIC problem

I have a davicom, and it's basically useless and unstable even when you use it with a PC.

Re: Usb NIC problem

Hi,

fyi:

i have a apple usb ethernet adapter... anyway i have the same problem... i asked in another thread for help with a displaylink driver which is usb as well... sadly i cannot get it to work. So you're not alone... :-(

Code:

[92365.538391] usb 1-1.4: New USB device found, idVendor=05ac, idProduct=1402

[92365.538421] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[92365.538452] usb 1-1.4: Product: Apple USB Ethernet Adapter

[92365.538452] usb 1-1.4: Manufacturer: Apple Inc.      

[92365.538452] usb 1-1.4: SerialNumber: 024D35

[92494.863952] hub 1-1:1.0: state 7 ports 4 chg 0000 evt 0004

[92494.874938] hub 1-1:1.0: port 2, status 0101, change 0001, 12 Mb/s

[92495.031433] hub 1-1:1.0: debounce: port 2: total 100ms stable 100ms status 0x101

[92495.117370] usb 1-1.2: new high speed USB device using musb_hdrc and address 28

[92495.228637] usb 1-1.2: default language 0x0409

[92495.231414] usb 1-1.2: uevent

[92495.231628] usb 1-1.2: usb_probe_device

[92495.231658] usb 1-1.2: configuration #1 chosen from 1 choice

[92495.237030] usb 1-1.2: adding 1-1.2:1.0 (config #1, interface 0)

[92495.237365] usb 1-1.2:1.0: uevent

[92495.238647] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '028'

i think it will be required to compile an own kernel... :-(

It looks like nobody really cares about arm when writing modules/drivers... t've seen this problem often now...

Re: Usb NIC problem

anyway i continue to work on it and keep you updated...

Re: Usb NIC problem

Has anyone gotten this device to work?
I have also posted here http://talk.maemo.org/showpost.php?p...&postcount=268
I have a davicom chipped Crystal Blue super cheap USB wired ethernet adapter that I can almost get working on my N900. I have in the past installed some scripts to try to get this working but the USB port was broken so I wasn't able to get anything working.
Now with a new USB port I have read/write on flash drives, I can use USB keyboards, I also can get the Crystal Blue ethernet adapter to light up and an interface called WIRED appears in my Internet connections options and automatically attempts to give my programs Internet access unsuccessfully.
The driver seems to be available for the Davicom, but none loads and then obviously no interface appears in ifconfig.
I am having trouble finding definite info other than the os2008 stuff which obviously will not work with a N900.
I run /usr/sbin/usbEthUp.sh and it says that /lib/modules/2.6.28.10-power47/usb2net/modlist is not present
Is there a USB ethernet adapters faq like they did for os2008 that I am missing?
I know the davicom chip is flaky but this adapter successfully connects when used with my laptop.
tried sudo modprobe usbnet, no love at all.
I am sure I am missing something stupid and this is a few keystrokes away for someone who actually knows what is going on.
I also looked at http://talk.maemo.org/showthread.php?p=1002480 and didn't see anything useful, again perhaps overlooking the obvious.

Re: Usb NIC problem

Don't quote me on that cause this is pure guess working, but may:

Quote:

I run /usr/sbin/usbEthUp.sh and it says that /lib/modules/2.6.28.10-power47/usb2net/modlist

...mean that module is missing from kernel and You must ask pali to include it in next kernel release? You're using kp47, right?

Re: Usb NIC problem

Quote:

Originally Posted by Estel (Post 1038082)

Don't quote me on that cause this is pure guess working, but may:

...mean that module is missing from kernel and You must ask pali to include it in next kernel release? You're using kp47, right?

Probably right although I had thought that the compiled module was floating around here on talk at some point, it was a few months that I couldn't hack because of a broken USB but now that I am back I can't find them if they were the right ones anyways.
Forgive my ignorance is Pali the powerkernel maintainer?
thanks

Re: Usb NIC problem

Ya, it's Pali, but for best results I recommend You to ask for that in kp47 thread:
http://talk.maemo.org/showthread.php?t=71879

Many skilled people read this thread, so You got higher chances that someone will mention useful things.

Re: Usb NIC problem

Just to stick it in this thread too, Pali has the Davidcom driver in line for the KP48 kernel, but I think it also depends on the scripts from N810, cant say for sure, since a few months of broken USB separated getting the starting and finishing this project, I have forgotten what steps I have taken.

Re: Usb NIC problem

Any updates regarding the driver for the davicom?

I just bought (in total noobiness ;)) such an adapter and was not successful getting it working.
Then researched a bit and found this thread. Also with the driver from blue_led no chance (usbnet.ko is automatically loaded). Ah, yes: I am running KP47.

Maybe blue_led did compile his driver against some source from freeware linux sites like the attached:
dm9601.c

I have also attached the original files from davicom.co.tw:
dm9601-Linux2.6_1.tar

Maybe it is enough to compile these sources for ARM?
As I do not know how to do it (neither on the N900 nor on a -not present- x86 linux), I would like to ask blue_led or another knowledgeable person to compile the driver for Maemo again from the tarball. Or maybe point me to some instructions....

Thanks

--edit
Another (not likely) thought came to my mind:
maybe the power consumption of this adapter is more than our N900 can deliver (300mA)? Could not find this param in spec (http://www.davicom.com.tw/page1.aspx?no=236843).

Re: Usb NIC problem

Just a reminder!
Anybody out there?

Or do I have to go bankrupt (have spent 5.37€ for nothing ;))?

Re: Usb NIC problem

OK, step by step.
I found now the driver included in KP48 lights up the device: my laptop detects a network. After struggling with usbnet, dm9601 and ifup and so on, I detected to use g_ether, but have to disable g_file_storage before. Using ifdown before ifup will help to get the right settings on N900 and I have the interface up and can ping it locally.

But I can not ping betwenn the laptop and N900! No firewall, no routing problem. The adaptor is working flawlessly (<10MBit) under Windows ....
What is still missing ? I have no clue. :(