Re: BT Voyager 1010 (or Linksys WUSB11)
Jonathan Melhuish wrote:
Wa-hey! Looks like I got it working! :-)
May 10 22:36:55 laptop kernel: hub.c: new USB device 00:07.2-1, assigned
address 23
May 10 22:36:55 laptop kernel: at76c503.c: $Id: at76c503.c,v 1.35
2003/07/30 06:31:51 jal2 Exp $ compiled May 9 2004 16:15:33
May 10 22:36:55 laptop kernel: at76c503.c: firmware version 0.90.0 #44
(fcs_len 4)
May 10 22:36:55 laptop kernel: at76c503.c: device's MAC
00:90:99:45:19:51, regulatory domain MKK1 (Japan) (id 65)
May 10 22:36:55 laptop kernel: at76c503.c: registered wlan0
It was actually the at76c503-i3861 driver that it uses. It seems to
vary; both of them seem to be listed for Linksys WUSB11! There's a big
table of Amtel devices here: http://at76c503a.berlios.de/devices.html
Anyway, once I found that out, it was just a matter of adding the
appropriate USB vendor/product ID to the driver. Here's the diff:
--- at76c503-i3861.c~ 2003-11-30 01:05:35.0 +
+++ at76c503-i3861.c2004-05-10 22:31:20.0 +0100
@@ -72,6 +72,9 @@
#define VENDOR_ID_DYNALINK0x069a
#define PRODUCT_ID_DYNALINK_WLL013_I 0x0320 /* Dynalink/Askey WLL013
(intersil) */
+#define VENDOR_ID_BT0x069a
+#define PRODUCT_ID_BT_VOYAGER_1010 0x0821 /* BT Voyager 1010 */
+
#define VENDOR_ID_SMC 0x0d5c
#define PRODUCT_ID_SMC2662W_V10xa001 /* EZ connect 11Mpbs
Wireless USB Adapter SMC2662W (v1) */
@@ -101,6 +104,7 @@
{ USB_DEVICE(VENDOR_ID_HP, PRODUCT_ID_HP_HN210W ) },
{ USB_DEVICE(VENDOR_ID_M4Y750, PRODUCT_ID_M4Y750) },
{ USB_DEVICE(VENDOR_ID_DYNALINK, PRODUCT_ID_DYNALINK_WLL013_I ) },
+ { USB_DEVICE(VENDOR_ID_BT, PRODUCT_ID_BT_VOYAGER_1010 ) },
{ USB_DEVICE(VENDOR_ID_SMC, PRODUCT_ID_SMC2662W_V1 ) },
{ USB_DEVICE(VENDOR_ID_BENQ, PRODUCT_ID_BENQ_AWL_300 ) },
{ USB_DEVICE(VENDOR_ID_ADDTRON, PRODUCT_ID_ADDTRON_AWU120) },
I'll send it to the Amtel driver guys, so that hopefully it'll be plug
and play in future.
Wow, my first real contribution to the open source community! 8-)
Good Show!
Ron
--
bumper sticker
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BT Voyager 1010 (or Linksys WUSB11)
Ron wrote:
Jonathan Melhuish wrote:
There must surely be a table that translates these numeric codes into
the right driver to load - anyone got any idea where it is?
Yeah, I got an idea where it is. It is in the driver. Look at
at76c503-rfmd.c of your berlios source directory. Your vendor 0x69a is
there as dyna link, but your product 0x821 is not. At least this is the
case in my version from back in December. I got a chuckle earlier, but
this is your chance to modify that puppy and reconfigure. I'd just follow
the convention that exists in the file for WUSB11.
Wa-hey! Looks like I got it working! :-)
May 10 22:36:55 laptop kernel: hub.c: new USB device 00:07.2-1, assigned
address 23
May 10 22:36:55 laptop kernel: at76c503.c: $Id: at76c503.c,v 1.35
2003/07/30 06:31:51 jal2 Exp $ compiled May 9 2004 16:15:33
May 10 22:36:55 laptop kernel: at76c503.c: firmware version 0.90.0 #44
(fcs_len 4)
May 10 22:36:55 laptop kernel: at76c503.c: device's MAC
00:90:99:45:19:51, regulatory domain MKK1 (Japan) (id 65)
May 10 22:36:55 laptop kernel: at76c503.c: registered wlan0
It was actually the at76c503-i3861 driver that it uses. It seems to
vary; both of them seem to be listed for Linksys WUSB11! There's a big
table of Amtel devices here: http://at76c503a.berlios.de/devices.html
Anyway, once I found that out, it was just a matter of adding the
appropriate USB vendor/product ID to the driver. Here's the diff:
--- at76c503-i3861.c~ 2003-11-30 01:05:35.0 +
+++ at76c503-i3861.c2004-05-10 22:31:20.0 +0100
@@ -72,6 +72,9 @@
#define VENDOR_ID_DYNALINK0x069a
#define PRODUCT_ID_DYNALINK_WLL013_I 0x0320 /* Dynalink/Askey WLL013
(intersil) */
+#define VENDOR_ID_BT0x069a
+#define PRODUCT_ID_BT_VOYAGER_1010 0x0821 /* BT Voyager 1010 */
+
#define VENDOR_ID_SMC 0x0d5c
#define PRODUCT_ID_SMC2662W_V10xa001 /* EZ connect 11Mpbs
Wireless USB Adapter SMC2662W (v1) */
@@ -101,6 +104,7 @@
{ USB_DEVICE(VENDOR_ID_HP, PRODUCT_ID_HP_HN210W ) },
{ USB_DEVICE(VENDOR_ID_M4Y750, PRODUCT_ID_M4Y750) },
{ USB_DEVICE(VENDOR_ID_DYNALINK, PRODUCT_ID_DYNALINK_WLL013_I ) },
+ { USB_DEVICE(VENDOR_ID_BT, PRODUCT_ID_BT_VOYAGER_1010 ) },
{ USB_DEVICE(VENDOR_ID_SMC, PRODUCT_ID_SMC2662W_V1 ) },
{ USB_DEVICE(VENDOR_ID_BENQ, PRODUCT_ID_BENQ_AWL_300 ) },
{ USB_DEVICE(VENDOR_ID_ADDTRON, PRODUCT_ID_ADDTRON_AWU120) },
I'll send it to the Amtel driver guys, so that hopefully it'll be plug
and play in future.
Wow, my first real contribution to the open source community! 8-)
Cheers,
Jon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BT Voyager 1010 (or Linksys WUSB11)
Ron wrote:
Jonathan Melhuish wrote:
Jonathan Melhuish wrote:
There must surely be a table that translates these numeric codes into
the right driver to load - anyone got any idea where it is?
Yeah, I got an idea where it is. It is in the driver. Look at
at76c503-rfmd.c of your berlios source directory. Your vendor 0x69a is
there as dyna link, but your product 0x821 is not. At least this is the
case in my version from back in December.
Hmm, I tried to modify it properly so that I can send my changes back
to the authors. Here's the diff:
#define VENDOR_ID_BT 0x69a
#define PRODUCT_ID_BT_VOYAGER_10100x821
113a114
{ USB_DEVICE(VENDOR_ID_BT, PRODUCT_ID_BT_VOYAGER_1010 ) },
I did a make, make install, but still the message in the system log is
the same (not claimed by any active driver). I tried typing modprobe
-v at76c503-rfmd again but to no avail.
Just as an aside, how do I get the proper diff output with filenames and
line numbers and stuff, so that you can use patch?
I got a chuckle earlier, but
this is your chance to modify that puppy and reconfigure. I'd just follow
the convention that exists in the file for WUSB11.
Bleh, don't listen to them! Linux isn't what it is today /just/ because
of the hardcore coders, ya know - it's people like you who test, hack,
document and support these things that really makes Linux into a quality
product. :-)
Cheers,
Jon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BT Voyager 1010 (or Linksys WUSB11)
Kevin Murphy wrote: Yargh, this is too hardcore for me; I didn't manage to get this working in a couple hours today. I'm going to try this all over again more carefully and then take it to the atmel driver list. Yup, I think I'll follow you there. Ron's suggestion looks promising so if I can get that working, I'll send you (and the authors of the drivers) a patch. If he draws a blank, I'll go on over to the Amtel driver list. My kernel is actually 2.6.3-1-386. I successfully compiled the latest Berlios atmel driver from cvs and installed it; the modules seem to be loaded fine when I plug in the linksys wusb11. From the Amtel driver readme: Reqirements: - Kernel 2.4.x. I am developing the driver on 2.4.20, but it reportedly also works on 2.4.19, 2.4.18 and 2.4.16. I am not sure about 2.5.x. So feel free to try it with kernel 2.6, but don't cry if it breaks! ;-) Cheers, Jon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BT Voyager 1010 (or Linksys WUSB11)
On Mon, May 10, 2004 at 09:08:47AM +0100, Jonathan Melhuish wrote:
Hmm, I tried to modify it properly so that I can send my changes back
to the authors. Here's the diff:
#define VENDOR_ID_BT 0x69a
#define PRODUCT_ID_BT_VOYAGER_10100x821
113a114
{ USB_DEVICE(VENDOR_ID_BT, PRODUCT_ID_BT_VOYAGER_1010 ) },
I did a make, make install, but still the message in the system log is
the same (not claimed by any active driver). I tried typing modprobe
-v at76c503-rfmd again but to no avail.
Just as an aside, how do I get the proper diff output with filenames and
line numbers and stuff, so that you can use patch?
Use 'diff -u'.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
BT Voyager 1010 (or Linksys WUSB11)
Has anybody succeeded in getting either of the above devices (apparently they use the same chipset) to work under Debian? I've just spent an hour or so trying to get the Amtel driver to compile, but have got no-where :-( My (brief) notes are here, if anybody can spot my mistake: http://www.orangejon.com/wiki/tiki-index.php?page=BtVoyager Can anybody point me in the direction of some tried and tested instructions? TIA, Jon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BT Voyager 1010 (or Linksys WUSB11)
Has anybody succeeded in getting either of the above devices (apparently they use the same chipset) to work under Debian? I'm going to be trying this out tomorrow (I have a Linksys WUSB11). I _have_ succeeded in compiling the Atmel driver at BerliOS (v 0.11, http://download.berlios.de/at76c503a/at76c503-0.11.tar.gz) for the 2.4.25-1-i386 kernel, but I have not tried it yet. I did 'sudo apt-get install kernel-build-2.4.25-1' to install the kernel headers, then untarred the driver source, and it built without errors, not that this means much ;-) Kevin Murphy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BT Voyager 1010 (or Linksys WUSB11)
Kevin Murphy wrote: Has anybody succeeded in getting either of the above devices (apparently they use the same chipset) to work under Debian? I'm going to be trying this out tomorrow (I have a Linksys WUSB11). I _have_ succeeded in compiling the Atmel driver at BerliOS (v 0.11, http://download.berlios.de/at76c503a/at76c503-0.11.tar.gz) for the 2.4.25-1-i386 kernel, but I have not tried it yet. I did 'sudo apt-get install kernel-build-2.4.25-1' to install the kernel headers, then untarred the driver source, and it built without errors, not that this means much ;-) Kevin Murphy I have set up the belkin version under both SuSE 2.4.20 and Debian 2.4.18. I highly recommend the Berlios version of the driver. My iwconfig package did not support some changes so I modified the at76c503a.c source and reconfigured. Changes were essid, essid length, and channel if I remember correctly. On another machine with the ohci board the whole thing crashed the machine during boot (gave up after a few tries and went pci). The berlios was better than the version that shipped with SuSE. I don't remeber if Debian had a version. Either way the Berlios was the way to go. Good Luck Ron -- bumper sticker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
