Author Topic: *experimental* wireless usb support package  (Read 300137 times)

March 27, 2009, 06:03:32 AM
Read 300137 times

Zorander

  • Newbie

  • Offline
  • *

  • 36
Here's a first attempt at a wireless usb network support package.

wireless-mod.app.bin (0.0.1)

It attempts to load the usb network driver for the following chipsets:
  • Zydas 1201 (11b)
  • Zydas 1211/1211b
  • RaLink 2870
  • RaLink rt73
  • Atheros Otus

The normal net.config options apply (dhcp/static IP).  The drivers should default to searching for the best open wireless point.

You can try adding specific configuration into net.config such as:

  iwconfig $MDEV essid MyHomeNetwork

No idea if wpa_supplicant works. (it's probably tied to the Otus driver explicitly)

This app.bin may work on older ext3-boot firmwares, as well as WDLXTV firmware releases. (UNTESTED)


March 27, 2009, 12:08:09 PM
Reply #1

waterlooscp

  • Newbie

  • Offline
  • *

  • 10
Hello Zorander,

If I use encryption i have to put like this?

wconfig $MDEV essid MyHomeNetwork key xxxx-xxxx-x

Sorry but I'm Linux newbie.

Thanks for the package.

Regards

waterlooscp

March 27, 2009, 01:09:04 PM
Reply #2

b-rad.cc

  • Hero Member

  • Offline
  • *****

  • 833
  • Personal Text
    FW Hacker
    • B-RAD
I have a rt2500 wireless adapter to play with. I compiled the kernel modules a while ago, so I'll see about getting WDLXTV compatible with this package very soon.

March 27, 2009, 05:52:50 PM
Reply #3

Zorander

  • Newbie

  • Offline
  • *

  • 36
wireless-mod experimental support package 0.0.2

Uploaded here

This version (attempts to) fix the /etc/mdev.conf for all the funky device names that they like to use.

Here's the list of network device names:
arusb_lnx uses ath0
rt2870sta uses ra0
rt73 uses rausb0
zd1201 uses wlan0
and, not to be outdone, zd1211b uses eth1 (or eth0)

I even threw in usb0 in case any of the regular usb network devices uses it (I think one or two of the usb-usb cables use usb0 as a device name)

b-rad.cc:  You need to update the /etc/mdev.conf in your distro to this:
Code: [Select]
# /etc/mdev.conf
eth[01] 0:0 755 *(/etc/hotplug/net.agent)
sd[a-z].* 0:0 755 @(/etc/hotplug/disk.agent)
sr[0-9] 0:0 0 *(/etc/hotplug/cd.agent)
#
# wireless drivers like to use strange device names
usb0    0:0 755 *(/etc/hotplug/net.agent)
ra0     0:0 755 *(/etc/hotplug/net.agent)
rausb0  0:0 755 *(/etc/hotplug/net.agent)
ath0    0:0 755 *(/etc/hotplug/net.agent)
vlan0   0:0 755 *(/etc/hotplug/net.agent)
(this is required since WDLXTV is perma-flashed, including the /etc directory where mdev resides, and therefore read only)

March 27, 2009, 09:47:40 PM
Reply #4

shadow

  • Newbie

  • Offline
  • *

  • 33
1st, thanks for the rt73 port on wdtv!!

I have a D-link DWA-110 wireless adapter (rt73 chipset), and installed the 8.7.2 and wireless-mod 0.0.2.

Apparently the kernel module does not detect the device, as follows:

 - Messages.txt during boot:
wdtv user.notice root:  [07d1:3c07] 1-1( 2.00,480m) 802.11 bg WLAN
(...)
wdtv user.info kernel: usbcore: registered new driver rt73
no further mention of rt73 nor WLAN

 - lsusb -v shows:
Displaying detected USB devices...
 [07d1:3c07] 1-1( 2.00,480m) 802.11 bg WLAN
 [0781:5203] 1-2( 2.00,480m) Flash Memory/200524446007F5F2E8BA
 [0000:0000] usb1( 2.00,480m) TangoX USB 2.0/tangox-ehci-hcd
 [0000:0000] usb2( 1.10,12m) USB Host Controller/TANGOX OHCI

The ifconfig and /proc/net/dev shows only the "lo" interface.
iwconfig shows no interfaces.

Tried to force load of rt73 on net.config, or others things...  but none worked.

If I unplug the wireless dongle and plug it again, the message.txt shows only:
wdtv user.info kernel: usb 1-1: USB disconnect, address 2
wdtv user.info kernel: usb 1-1: new high speed USB device using tangox-ehci-hcd and address 4

Any Ideas?

March 28, 2009, 12:03:47 AM
Reply #5

rezmus

  • Sr. Member

  • Offline
  • ****

  • 418
my rt73 based edimax EW-7318USg works ok with wireless-mod 0.0.1, no more messages in messages.txt then loading rt73.ko, interface was down by default (0.0.2 should fix it), had to up by ifconfig rausb0 up and manualy set ip (ifconfig rausb0 ip) coz dhcp didn't work (0.0.2 should fix it too). then just used iwconfig to set ap and wep key (iwconfig rausb0 essid ap key "s:asciikey" and it works ok. also tried wpa-psk with wpa_supplicant.

March 28, 2009, 01:19:41 AM
Reply #6

rezmus

  • Sr. Member

  • Offline
  • ****

  • 418
with 0.0.2 i got rausb0 up on reboot, but i can;t get iwconfig to work during boot setting ap/key in net.config, after boot when i run iwconfig from console it works ok, i get ip with dhcp.

March 28, 2009, 01:26:42 AM
Reply #7

FUZZI

  • Newbie

  • Offline
  • *

  • 1
are there any good tutorials for total noobs how to install a custom firmware on the wd? I've got a RaLink 2870 usb adapter and it would be really great if this is going to work.

March 28, 2009, 01:41:38 AM
Reply #8

Hades666

  • Newbie

  • Offline
  • *

  • 35
are there any good tutorials for total noobs how to install a custom firmware on the wd? I've got a RaLink 2870 usb adapter and it would be really great if this is going to work.

Totally agree, a step-by-step guide will be very useful...
I find some guides for wired conections, but with wireless configuration im totally lost...

thanks

March 28, 2009, 03:23:56 AM
Reply #9

rezmus

  • Sr. Member

  • Offline
  • ****

  • 418
zorander: i looked on /etc/hotplug/net.agent and i think iwconfig fails on boot because it is executed before you up the interface, is it right or i'm wrong? maybe we should wake up interface before dhcp so if there will be iwconfig in the middle it should work.

edit: my mistake, rausb0 should be up before iwconfig, so still i don't know why it doesn't work from /boot/net.config while it works from console after boot.
« Last Edit: March 28, 2009, 03:29:28 AM by rezmus »

March 28, 2009, 03:30:32 AM
Reply #10

Zorander

  • Newbie

  • Offline
  • *

  • 36
rezmus: you're right.

Just add "ifconfig $MDEV up" to the net.config before the iwconfig lines should do for now.

March 28, 2009, 04:52:30 AM
Reply #11

rezmus

  • Sr. Member

  • Offline
  • ****

  • 418
hehe so i was right after all, now it works like a charm :)

March 28, 2009, 07:28:20 AM
Reply #12

shadow

  • Newbie

  • Offline
  • *

  • 33
Zorander,

Concerning about the D-Link DWA-110 issues;

After some test and research, apparently for D-LINK DEVICES (vendor: 07d1) this port used for RT73 driver supports only the product: 3c03 ("DWL-G122 802.11g Adapter [ralink rt73]")"

The DWA-110 (07d1:3c07) is compatible with the rt73 driver, but in order to work with this port of RT73, its "usb product id" must be added to the rtmp_def.h of the RT73 files before compiling.
(just add {USB_DEVICE(0x07d1,0x3c07)},\ in rtmp_def.h )

Thats why the dongle gets detected on the lsusb, but the interfaces do not show up (the driver does not recognizes it as a valid/supported D-Link device).
wdtv user.notice root:  [07d1:3c07] 1-2( 2.00,480m) 802.11 bg WLAN

If it's possible, can you include this is some next release?
I would appreciate a lot!!!

Thanks for all this work!
Shadow

March 28, 2009, 08:01:14 AM
Reply #13

3dxr

  • Global Moderator
  • Sr. Member

  • Offline
  • *****

  • 411
Hi all I want ask people who have functional Wireless Dongle do some performance test

and share results and send me a private message to post where was this information published

I am not able check so many threads and update WIKI
I need your support now when is main discussion splitted to more forums and threads

I near future I will add to WIKI WIRELESS ADAPTERS TABLE


Regards

3dxr

March 28, 2009, 11:14:34 AM
Reply #14

rezmus

  • Sr. Member

  • Offline
  • ****

  • 418
zorander check this link:

http://cateee.net/lkddb/web-lkddb/RT73USB.html

here u can find much more vids/pids for RT73 then in sources i've sent u if u consider to recompile the driver.