Trouble with usb wifi adapter

Stuff that plugs in via USB, FireWire, eSATA, PS/2, etc.

Trouble with usb wifi adapter

Postby Sragonal » 04 Dec 2009, 01:23

Hello FreeBSD people,

I've got an old pc here where I put FreeBSD 8.0 on, the problem is that I can't get the wifi adapter to work. The adapter is a "Siemens Gigaset USB Adapter 108" . I've checked the hardware notes and the device should work with the 'uath' driver.

It's a fresh install, and I've compiled a whole new kernel for that device. I made sure that all dependencies where met.

When I connect the device this shows up: "ugen0.2 <Atheros Communications Inc> at usbus0". But it doesn't show up in /dev as uath0. The program 'uathload' for loading the right firmware in the device seems to work fine though.

I'm quite a newbie concerning FreeBSD. I hope someone could help me with this problem, I would really appreciate that. :)
Sragonal
Junior Member
 
Posts: 8
Joined: 04 Dec 2009, 01:00
Location: The Netherlands

Postby aragon » 04 Dec 2009, 03:17

When it's plugged in, paste us the output of this:

Code: Select all
usbconfig -u 0 -a 2 dump_device_desc


The above assumes it comes up as ugen0.2.
aragon
Giant Locked
 
Posts: 2031
Joined: 16 Nov 2008, 17:04
Location: Cape Town, South Africa

Postby Sragonal » 04 Dec 2009, 10:54

The output of usbconfig -u 0 -a 2 dump_device_desc:

Code: Select all
gen0.2 <AR5523 Atheros Communications Inc> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

bLength = 0x0012
bDescriptorTyupe = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x00ff
bDeviceSubClass = 0x0000
bDeviceProtocol = 0x0000
bMaxPacketSize0 = ox0040
idVendor = 0x129b
idProduct = 0x160c
bcdDevice = 0x0001
iManufacturer = 0x0001 <Atheros Communications Inc>
iProduct = 0x002 <AR5523>
iSerialNumber = 0x0003 <1.0>
bNumConfigurations = 0x0001


Thanks for replying :)
Sragonal
Junior Member
 
Posts: 8
Joined: 04 Dec 2009, 01:00
Location: The Netherlands

Postby aragon » 04 Dec 2009, 19:18

Unfortunately that card is not supported at this time, but it might be possible/easy to add support because the AR5523 controller is supported. Do you know how to patch source code and recompile your kernel?
aragon
Giant Locked
 
Posts: 2031
Joined: 16 Nov 2008, 17:04
Location: Cape Town, South Africa

Postby Sragonal » 05 Dec 2009, 02:52

I know basic C. And as mentioned in my first post, I have recompiled a kernel with the instructions from the handbook.

Maybe you could give me some more instructions to get my wifi adapter working?

I have no experience patching source code though. :/
Sragonal
Junior Member
 
Posts: 8
Joined: 04 Dec 2009, 01:00
Location: The Netherlands

Postby aragon » 05 Dec 2009, 05:16

Great. Download the attached patch. Apply it as follows:

Code: Select all
cd /usr/src
patch </path/to/siemens.txt


It should apply cleanly on 8.0 source. After patching, recompile your kernel and hold thumbs.

(it says CYBERTAN in the source because that vendor was already defined for 0x129b)
Attachments

[The extension txt has been deactivated and can no longer be displayed.]

aragon
Giant Locked
 
Posts: 2031
Joined: 16 Nov 2008, 17:04
Location: Cape Town, South Africa

Postby Sragonal » 05 Dec 2009, 06:31

OK, I have executed the commands in your post. And after that I've executed "make buildkernel KERNELCONF=HOMESERVER", this is my custom kernel, at the moment it is compiling. When it is done I will execute "make installkernel KERNELCONF=HOMESERVER".

I am not really understanding what is happening in the 'siemens.txt' file tough. Maybe you could explain what is happening, or link me to a web address where I could learn more about patch files. What does a line like: "@@ -1120,6 +1120,7 @@" mean? Did you write this file yourself?

I'm holding thumbs right now. ;)

I really appreciate the work you have put into this.:)
Sragonal
Junior Member
 
Posts: 8
Joined: 04 Dec 2009, 01:00
Location: The Netherlands

Postby aragon » 05 Dec 2009, 06:57

The patch file is created with [man=1]diff[/man]. I found this guide. Take a look at [man=1]patch[/man] too.

Hope it works.
aragon
Giant Locked
 
Posts: 2031
Joined: 16 Nov 2008, 17:04
Location: Cape Town, South Africa

Postby Sragonal » 05 Dec 2009, 10:25

Now there seems to be happening more with the device while booting. But in the end it turns out that there is still no uath0 in /dev.

dmesg with some irrelevant stuff filtered out:
Code: Select all
ugen0.3: <Atheros Communications Inc> at usbus0
uath0: <Atheros Communications Inc AR5523, rev 2.00/0.01, addr 3> on usbus0
Root mount waiting for: usbus0
uath0: timeout waiting for reply to cmd 0x1 (1)
uath0: could not initialize adapter
device_attach: uath0 attach returned 35
uath0: <Atheros Communications Inc AR5523, rev 2.00/0.01, addr 3> on usbus0
uath0: timeout waiting for reply to cmd 0x1 (1)
uath0: could not initialize adapter
device_attach: uath0 attach returned 35
Sragonal
Junior Member
 
Posts: 8
Joined: 04 Dec 2009, 01:00
Location: The Netherlands

Postby aragon » 05 Dec 2009, 10:30

Ack. That's a pity. Unfortunately it's not an easy fix then, at least not for me. Since you know some C, you might be able to add support in [file]src/sys/dev/usb/wlan/if_uath.c[/file]
aragon
Giant Locked
 
Posts: 2031
Joined: 16 Nov 2008, 17:04
Location: Cape Town, South Africa

Postby Sragonal » 05 Dec 2009, 10:40

Haha, alright. Back to the days when if you wanted something with your pc, you will have to write the code yourself.:e

Thanks for your help anyway. :)
Sragonal
Junior Member
 
Posts: 8
Joined: 04 Dec 2009, 01:00
Location: The Netherlands

Postby aragon » 05 Dec 2009, 10:44

Sragonal wrote:Haha, alright. Back to the days when if you wanted something with your pc, you will have to write the code yourself.:e

Something like that. :P

Actually there is more you could still try. The mailing lists are a good source of help too.

Or you could try another card. My Cisco/Linksys WUSB54G works great with [man=4]rum[/man].
aragon
Giant Locked
 
Posts: 2031
Joined: 16 Nov 2008, 17:04
Location: Cape Town, South Africa

Postby Sragonal » 05 Dec 2009, 14:13

Strange that the hardware notes say that the device I'm using is supported. While in practice it doesn't seem to work. :/
Sragonal
Junior Member
 
Posts: 8
Joined: 04 Dec 2009, 01:00
Location: The Netherlands

Postby aragon » 05 Dec 2009, 14:17

Yup. Usually a patch like mine works fine. Not so lucky this time.

Something else you can try is [man=4]ndis[/man].
aragon
Giant Locked
 
Posts: 2031
Joined: 16 Nov 2008, 17:04
Location: Cape Town, South Africa

Postby Sragonal » 08 Dec 2009, 14:44

I'll try that, I hope it works. What troubles me is that the uath driver changed the firmware. I've been searching a bit on the net but I couldn't find it.

I will just try it and see how it works out.
Sragonal
Junior Member
 
Posts: 8
Joined: 04 Dec 2009, 01:00
Location: The Netherlands


Return to Peripheral Hardware

Who is online

Users browsing this forum: No registered users and 0 guests