Has anyone been able to get this driver to work in ad-hoc mode?
I have an edimax ew7117u and have managed (I think) to get the driver to work - I can scan available networks etc.
The problem is the network I am trying to set up is ad-hoc between two of this wlan sticks. They can see each other but can't connect.
If anyone has managed to get ad-hoc to work any help would be greatly appreciated.
Cheers, Andy.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Im afraid adhoc mode is not available by now.
This drivers is based on a old version of linux-wlan-ng driver, that at that moment didnt support adhoc mode very well ...
So The way we have to get a proper adhoc supoort, is to convert this driver into a patch against the original wlan-ng driver, so we can use the latest wlan-ng that has adhoc mode and mucho more things.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-12-07
Thanks for your reply andres.
Is this happening at the moment? I mean are you (or is someone) in the process of converting this driver into a patch as you mention?
Thanks for your help by the way. Good job on getting any driver to work with this chipset at all!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, i dont expect the driver to be fully merged into the official wlan-ng driver, until some redisign is made in th driver. And i dont fell capable of doing that, as at this momnet, my knowledge of linux module programming, USB and 802.11 internals is not that good.
But dont panic, there's some hope left :-)
I recently upgraded my box kernel to 2.6.0 and guess what? Zydas driver doesnt support kernel 2.6.0 as it is based on wlan-ng 0.2 driver, and linux 2.6 suport was added into a 2.1pre version, so im trying to convert Zydas1201 driver into a patch againt the last version of wlan-ng.
And that path applied to wlna-ng should work with linux 2.4, 2.4 and hoppefully it MAY provide adhoc mode.
Stay tunned, this week im working on it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-01-08
Hello,
I got a driver from a vendor in denmark for the Zydas 1201 chipset. It is a more recent version than the one for the sweex. I have tested this driver with a TopCom USB wireless stick under Linux. I have tested it in ad-hoc mode (without encryption) and it works perfect. The pdf document shipped with the driver also spoke about supporting ad-hoc and infrastructure mode and wep encryption. I haven't tested infrastructure mode but i suppose this will work too.
I don't know where i can put this driver on the net , so if somebody could contact me how to do this on the sourceforge page.
Greetings
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-01-08
What vendor is it? Maybe they have put the driver up on their website?
If not you could always put it on sourceforge as you say - I think you could either e-mail the source to andres in this project or register a new project and put the source up that way (but that might be a bit over the top :-) )
Regards, Andy
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As i said i tryed to merge the current driver with wlan-ng driver... but it turned out to be much more hard that i expected.
So we are not going to get adhoc and linux 2.6 support so soon :-(
Anyway i talinkg with Wim Valcke to see if he can send us the driver he have, and publish it here, lets see what happens.
Greetings
Andrs
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-01-17
Hi all,
I've found a driver at http://www.delitek.com/usb.tgz, this is version zdsta-1.0.4 and has working ad-hoc support :) Some additional description can be found at http://www.delitek.com/non-cgi/usr/5/5_17.txt, but unfortunately this one is in chinese (as I don't understand that, I don't know what exactly is written there, but all important parts are in the package in file zydas1201.doc )
Still this is just for 2.4.x kernels :(( but if that is what you are running this is just for you.. I'll try to do something with it, but no warranty..
ad-hoc mode tested (against windows machine..) and works great, infrastructure should work...
oh, and don't forget to turn on wireless support in the kernel to have /proc/net/wireless statistics :)
So, enjoy :))
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did I diff wrong or the only thing 1.0.3 lacked was as registering the ad-hoc hooks ?
Anyway, seems to work with ad-hoc+wep on the Zaapa usb stick (0x0ace/0x1201).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sweet, sweet :-)
now we have 2 adhoc working drivers: The delitek(chinesse) driver and another one provided by Wim
Thanx guys :-)
Im analysing them, comparing with wlan-ng, and applying some patches to support more zydas1201 devices, and i publish them Monday or Tuesday.
Stand by.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-01-19
I'm now working happily with the edimax 7117 in adhoc mode + WEP using the delitek driver.
Thanks people for putting these drivers up.
Cheers, Andy.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-02-01
Running fedora core 1 here (kernel 2.4.22-1.2115.nptl)
Edimax 7117U
i don't get "USB device no accepting..." error, so i assume i don't need to compile the modified kernel.
Also, I can see the the led blinking from orange to green, so i guess the usb part is ok, but...
None of the wlanctl-ng commands work! I always get "operation not supported"
when i used iwconfig (just testing) i would get "operation not supported" and "Bad address" errors
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-02-05
Hello,
Sorry for delay in replying but you know.. things to do!
Which driver are you using? I'm using the delitek one (the url is posted in this thread).
Lets assume that your usb system is okay for now. If you are using one of the modified drivers that are capable of adhoc (like the delitek) then maybe you could post any errors or messages from your syslog that refer to the wlan stick when you plug it in.
You should see something like my /var/log/messages here:
Feb 5 21:01:18 badass kernel: hub.c: new USB device 00:07.2-2, assigned address
2
Feb 5 21:01:18 badass kernel: dev->name wlan0
Feb 5 21:01:18 badass kernel: p80211knetdev_open !!!
Feb 5 21:01:18 badass kernel: USB Download Boot code success
Feb 5 21:01:18 badass kernel: ident: nic h/w: id=0x00 0.0.0
Feb 5 21:01:18 badass kernel: ident: pri f/w: id=0x00 0.0.0
Feb 5 21:01:18 badass kernel: MFI:SUP:role=0x00:id=0x00:var=0x00:b/t=0/0
Feb 5 21:01:18 badass kernel: CFI:SUP:role=0x00:id=0x00:var=0x00:b/t=0/2
Feb 5 21:01:18 badass kernel: PRI:SUP:role=0x00:id=0x00:var=0x00:b/t=0/0
Feb 5 21:01:18 badass kernel: AP:SUP:role=0x00:id=0x00:var=0x00:b/t=0/0
Feb 5 21:01:18 badass kernel: PRI-CFI:ACT:role=0x00:id=0x00:var=0x00:b/t=0/0
Feb 5 21:01:18 badass kernel: STA-CFI:ACT:role=0x00:id=0x00:var=0x00:b/t=0/0
Feb 5 21:01:18 badass kernel: STA-MFI:ACT:role=0x00:id=0x00:var=0x00:b/t=0/0
Feb 5 21:01:18 badass kernel: Prism2 card SN: \x00\x00\x00\x00\x00\x00\x00\x00\
x00\x00\x00\x00
Feb 5 21:01:18 badass kernel: linkstatus=DISCONNECTED (unhandled)
Don't worry too much about the wlanctl-ng commands - the only ones you need are in the shell scripts scan.sh and setup.sh. Those should be enough to connect in adhoc mode with WEP and all! I have never used iwconfig.
Oh - one problem I had (with mandrake) was that there was a module already loaded called prism2_usb tucked away somewhere under /lib/modules somewhere. I had to delete it because it was loaded in preference. Maybe fedora does the same thing (it's red hat rebranded isn't it?).
Anyway post any error messages you get when you plug in. Or try having the stick plugged in on boot.
Good luck, Andy.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-02-06
i deleted the prism2_usb.o just in case... then i compiled the drivers from delitek this is what i got:
Feb 6 05:00:21 hcsousa kernel: hub.c: new USB device 00:02.0-1, assigned address 2
Feb 6 05:00:21 hcsousa kernel: usb.c: USB device not responding, giving up (error=-110)
Feb 6 05:00:22 hcsousa kernel: hub.c: Cannot enable port 1 of hub 1, disabling port.
Feb 6 05:00:22 hcsousa kernel: hub.c: Maybe the USB cable is bad?
Feb 6 05:00:22 hcsousa kernel: hub.c: new USB device 00:02.0-1, assigned address 3
Feb 6 05:00:22 hcsousa kernel: usb.c: USB device 3 (vend/prod 0xace/0x1201) is not claimed by any active driver.
Feb 6 05:00:25 hcsousa insmod: /lib/modules/2.4.22-1.2115.nptl/net/p80211.o: unresolved symbol register_netdevice
Feb 6 05:00:25 hcsousa insmod: /lib/modules/2.4.22-1.2115.nptl/net/p80211.o: unresolved symbol eth_type_trans
Feb 6 05:00:25 hcsousa insmod: /lib/modules/2.4.22-1.2115.nptl/net/p80211.o: unresolved symbol __wake_up
Feb 6 05:00:25 hcsousa insmod: /lib/modules/2.4.22-1.2115.nptl/net/p80211.o: unresolved symbol __kfree_skb
and a lot more of similar errors
Then i compiled the one in the linux-lc100020 page
what i got was
Feb 6 05:02:52 hcsousa kernel: init_module: prism2_usb.o: 0.2.0 Loaded
Feb 6 05:02:52 hcsousa kernel: init_module: dev_info is: prism2_usb
Feb 6 05:02:52 hcsousa kernel: usb.c: registered new driver prism2_usb
Feb 6 05:02:52 hcsousa kernel: dev->name wlan0
Feb 6 05:02:52 hcsousa kernel: ip_tables: (C) 2000-2002 Netfilter core team
Feb 6 05:02:52 hcsousa kernel: USB Download Boot code success
Feb 6 05:02:52 hcsousa kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
Feb 6 05:02:52 hcsousa kernel: printing eip:
Feb 6 05:02:52 hcsousa kernel: ce977bdc
Feb 6 05:02:52 hcsousa kernel: *pde = 00000000
Feb 6 05:02:52 hcsousa kernel: Oops: 0000
Feb 6 05:02:52 hcsousa kernel: prism2_usb p80211 trident ac97_codec pcigame gameport soundcore ide-cd cdrom powernow-k7 nls_iso8859-1 nls_cp437 vfat fat parport_pc lp parport autofs ds yent
Feb 6 05:02:52 hcsousa kernel: CPU: 0
Feb 6 05:02:52 hcsousa kernel: EIP: 0060:[<ce977bdc>] Not tainted
Feb 6 05:02:52 hcsousa kernel: EFLAGS: 00010246
Feb 6 05:02:52 hcsousa kernel:
Feb 6 05:02:52 hcsousa kernel: EIP is at prism2sta_probe_usb [prism2_usb] 0x7c (2.4.22-1.2115.nptl)
wlan0 Link encap:Ethernet HWaddr 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)
Hardware address 000000000000??
I had noticed that this adapter does not respect the 802.11b standart (this adapter is capable of MAC address spoofing, just like ethernet card)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-02-07
Your first attempt (with the delitek) looks more promising. The second was causing a kernel oops.
The usb device not responding is probably the same error as mentioned with the driver info: USB not accepting new address = xxx.
Try editing your usb.c and hub.c as described in the docs. This will hopefully ensure that the usb subsystem accepts the device and fires up the prism2_usb module.
By the looks of it you may need to remove the old p80211.o as well.
> Hardware address 000000000000??
> I had noticed that this adapter does not respect the 802.11b standart (this adapter is capable of MAC address spoofing, just like ethernet card)
The hardware address of all zeros is just because the driver hadn't loaded. You only need to set up the networking aspect (ifconfig etc..) when you know that the driver has correctly loaded.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-02-14
i compiled a new kernel and it worked, thanks.
Is there a patch for 2.6.x kernels or they don't need it?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Has anyone been able to get this driver to work in ad-hoc mode?
I have an edimax ew7117u and have managed (I think) to get the driver to work - I can scan available networks etc.
The problem is the network I am trying to set up is ad-hoc between two of this wlan sticks. They can see each other but can't connect.
If anyone has managed to get ad-hoc to work any help would be greatly appreciated.
Cheers, Andy.
Im afraid adhoc mode is not available by now.
This drivers is based on a old version of linux-wlan-ng driver, that at that moment didnt support adhoc mode very well ...
So The way we have to get a proper adhoc supoort, is to convert this driver into a patch against the original wlan-ng driver, so we can use the latest wlan-ng that has adhoc mode and mucho more things.
Thanks for your reply andres.
Is this happening at the moment? I mean are you (or is someone) in the process of converting this driver into a patch as you mention?
Thanks for your help by the way. Good job on getting any driver to work with this chipset at all!
Well, i dont expect the driver to be fully merged into the official wlan-ng driver, until some redisign is made in th driver. And i dont fell capable of doing that, as at this momnet, my knowledge of linux module programming, USB and 802.11 internals is not that good.
But dont panic, there's some hope left :-)
I recently upgraded my box kernel to 2.6.0 and guess what? Zydas driver doesnt support kernel 2.6.0 as it is based on wlan-ng 0.2 driver, and linux 2.6 suport was added into a 2.1pre version, so im trying to convert Zydas1201 driver into a patch againt the last version of wlan-ng.
And that path applied to wlna-ng should work with linux 2.4, 2.4 and hoppefully it MAY provide adhoc mode.
Stay tunned, this week im working on it.
Hello,
I got a driver from a vendor in denmark for the Zydas 1201 chipset. It is a more recent version than the one for the sweex. I have tested this driver with a TopCom USB wireless stick under Linux. I have tested it in ad-hoc mode (without encryption) and it works perfect. The pdf document shipped with the driver also spoke about supporting ad-hoc and infrastructure mode and wep encryption. I haven't tested infrastructure mode but i suppose this will work too.
I don't know where i can put this driver on the net , so if somebody could contact me how to do this on the sourceforge page.
Greetings
What vendor is it? Maybe they have put the driver up on their website?
If not you could always put it on sourceforge as you say - I think you could either e-mail the source to andres in this project or register a new project and put the source up that way (but that might be a bit over the top :-) )
Regards, Andy
Hi all again.
As i said i tryed to merge the current driver with wlan-ng driver... but it turned out to be much more hard that i expected.
So we are not going to get adhoc and linux 2.6 support so soon :-(
Anyway i talinkg with Wim Valcke to see if he can send us the driver he have, and publish it here, lets see what happens.
Greetings
Andrs
Hi all,
I've found a driver at http://www.delitek.com/usb.tgz, this is version zdsta-1.0.4 and has working ad-hoc support :) Some additional description can be found at http://www.delitek.com/non-cgi/usr/5/5_17.txt, but unfortunately this one is in chinese (as I don't understand that, I don't know what exactly is written there, but all important parts are in the package in file zydas1201.doc )
Still this is just for 2.4.x kernels :(( but if that is what you are running this is just for you.. I'll try to do something with it, but no warranty..
ad-hoc mode tested (against windows machine..) and works great, infrastructure should work...
oh, and don't forget to turn on wireless support in the kernel to have /proc/net/wireless statistics :)
So, enjoy :))
Did I diff wrong or the only thing 1.0.3 lacked was as registering the ad-hoc hooks ?
Anyway, seems to work with ad-hoc+wep on the Zaapa usb stick (0x0ace/0x1201).
Sweet, sweet :-)
now we have 2 adhoc working drivers: The delitek(chinesse) driver and another one provided by Wim
Thanx guys :-)
Im analysing them, comparing with wlan-ng, and applying some patches to support more zydas1201 devices, and i publish them Monday or Tuesday.
Stand by.
I'm now working happily with the edimax 7117 in adhoc mode + WEP using the delitek driver.
Thanks people for putting these drivers up.
Cheers, Andy.
Running fedora core 1 here (kernel 2.4.22-1.2115.nptl)
Edimax 7117U
i don't get "USB device no accepting..." error, so i assume i don't need to compile the modified kernel.
Also, I can see the the led blinking from orange to green, so i guess the usb part is ok, but...
None of the wlanctl-ng commands work! I always get "operation not supported"
when i used iwconfig (just testing) i would get "operation not supported" and "Bad address" errors
Hello,
Sorry for delay in replying but you know.. things to do!
Which driver are you using? I'm using the delitek one (the url is posted in this thread).
Lets assume that your usb system is okay for now. If you are using one of the modified drivers that are capable of adhoc (like the delitek) then maybe you could post any errors or messages from your syslog that refer to the wlan stick when you plug it in.
You should see something like my /var/log/messages here:
Feb 5 21:01:18 badass kernel: hub.c: new USB device 00:07.2-2, assigned address
2
Feb 5 21:01:18 badass kernel: dev->name wlan0
Feb 5 21:01:18 badass kernel: p80211knetdev_open !!!
Feb 5 21:01:18 badass kernel: USB Download Boot code success
Feb 5 21:01:18 badass kernel: ident: nic h/w: id=0x00 0.0.0
Feb 5 21:01:18 badass kernel: ident: pri f/w: id=0x00 0.0.0
Feb 5 21:01:18 badass kernel: MFI:SUP:role=0x00:id=0x00:var=0x00:b/t=0/0
Feb 5 21:01:18 badass kernel: CFI:SUP:role=0x00:id=0x00:var=0x00:b/t=0/2
Feb 5 21:01:18 badass kernel: PRI:SUP:role=0x00:id=0x00:var=0x00:b/t=0/0
Feb 5 21:01:18 badass kernel: AP:SUP:role=0x00:id=0x00:var=0x00:b/t=0/0
Feb 5 21:01:18 badass kernel: PRI-CFI:ACT:role=0x00:id=0x00:var=0x00:b/t=0/0
Feb 5 21:01:18 badass kernel: STA-CFI:ACT:role=0x00:id=0x00:var=0x00:b/t=0/0
Feb 5 21:01:18 badass kernel: STA-MFI:ACT:role=0x00:id=0x00:var=0x00:b/t=0/0
Feb 5 21:01:18 badass kernel: Prism2 card SN: \x00\x00\x00\x00\x00\x00\x00\x00\
x00\x00\x00\x00
Feb 5 21:01:18 badass kernel: linkstatus=DISCONNECTED (unhandled)
Don't worry too much about the wlanctl-ng commands - the only ones you need are in the shell scripts scan.sh and setup.sh. Those should be enough to connect in adhoc mode with WEP and all! I have never used iwconfig.
Oh - one problem I had (with mandrake) was that there was a module already loaded called prism2_usb tucked away somewhere under /lib/modules somewhere. I had to delete it because it was loaded in preference. Maybe fedora does the same thing (it's red hat rebranded isn't it?).
Anyway post any error messages you get when you plug in. Or try having the stick plugged in on boot.
Good luck, Andy.
i deleted the prism2_usb.o just in case... then i compiled the drivers from delitek this is what i got:
Feb 6 05:00:21 hcsousa kernel: hub.c: new USB device 00:02.0-1, assigned address 2
Feb 6 05:00:21 hcsousa kernel: usb.c: USB device not responding, giving up (error=-110)
Feb 6 05:00:22 hcsousa kernel: hub.c: Cannot enable port 1 of hub 1, disabling port.
Feb 6 05:00:22 hcsousa kernel: hub.c: Maybe the USB cable is bad?
Feb 6 05:00:22 hcsousa kernel: hub.c: new USB device 00:02.0-1, assigned address 3
Feb 6 05:00:22 hcsousa kernel: usb.c: USB device 3 (vend/prod 0xace/0x1201) is not claimed by any active driver.
Feb 6 05:00:25 hcsousa insmod: /lib/modules/2.4.22-1.2115.nptl/net/p80211.o: unresolved symbol register_netdevice
Feb 6 05:00:25 hcsousa insmod: /lib/modules/2.4.22-1.2115.nptl/net/p80211.o: unresolved symbol eth_type_trans
Feb 6 05:00:25 hcsousa insmod: /lib/modules/2.4.22-1.2115.nptl/net/p80211.o: unresolved symbol __wake_up
Feb 6 05:00:25 hcsousa insmod: /lib/modules/2.4.22-1.2115.nptl/net/p80211.o: unresolved symbol __kfree_skb
and a lot more of similar errors
Then i compiled the one in the linux-lc100020 page
what i got was
Feb 6 05:02:52 hcsousa kernel: init_module: prism2_usb.o: 0.2.0 Loaded
Feb 6 05:02:52 hcsousa kernel: init_module: dev_info is: prism2_usb
Feb 6 05:02:52 hcsousa kernel: usb.c: registered new driver prism2_usb
Feb 6 05:02:52 hcsousa kernel: dev->name wlan0
Feb 6 05:02:52 hcsousa kernel: ip_tables: (C) 2000-2002 Netfilter core team
Feb 6 05:02:52 hcsousa kernel: USB Download Boot code success
Feb 6 05:02:52 hcsousa kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
Feb 6 05:02:52 hcsousa kernel: printing eip:
Feb 6 05:02:52 hcsousa kernel: ce977bdc
Feb 6 05:02:52 hcsousa kernel: *pde = 00000000
Feb 6 05:02:52 hcsousa kernel: Oops: 0000
Feb 6 05:02:52 hcsousa kernel: prism2_usb p80211 trident ac97_codec pcigame gameport soundcore ide-cd cdrom powernow-k7 nls_iso8859-1 nls_cp437 vfat fat parport_pc lp parport autofs ds yent
Feb 6 05:02:52 hcsousa kernel: CPU: 0
Feb 6 05:02:52 hcsousa kernel: EIP: 0060:[<ce977bdc>] Not tainted
Feb 6 05:02:52 hcsousa kernel: EFLAGS: 00010246
Feb 6 05:02:52 hcsousa kernel:
Feb 6 05:02:52 hcsousa kernel: EIP is at prism2sta_probe_usb [prism2_usb] 0x7c (2.4.22-1.2115.nptl)
Feb 6 05:02:52 hcsousa kernel: eax: 00000000 ebx: 00000000 ecx: 00000000 edx: 00000000
Feb 6 05:02:52 hcsousa kernel: esi: cd3ce400 edi: c1888000 ebp: 00000000 esp: c2a35e54
Feb 6 05:02:52 hcsousa kernel: ds: 0068 es: 0068 ss: 0068
Feb 6 05:02:52 hcsousa kernel: Process modprobe (pid: 3610, stackpage=c2a35000)
Feb 6 05:02:52 hcsousa kernel: Stack: c1888000 00000000 00005adc 35da9000 0002245a cd6848c0 ce988940 ce884cc0
Feb 6 05:02:52 hcsousa kernel: c5b362c0 00000001 ce85fe89 cd0d8800 00000000 00000000 00000000 cd0d8824
Feb 6 05:02:52 hcsousa kernel: ce988920 00000000 ce871c40 00000000 cd0d8800 00000002 ce976000 ce85fa8c
Feb 6 05:02:52 hcsousa kernel: Call Trace: [<ce988940>] prism2_usb_driver [prism2_usb] 0x20 (0xc2a35e6c)
Feb 6 05:02:52 hcsousa kernel: [<ce884cc0>] hid_driver [hid] 0x20 (0xc2a35e70)
Feb 6 05:02:52 hcsousa kernel: [<ce85fe89>] usb_find_interface_driver [usbcore] 0x1e9 (0xc2a35e7c)
Feb 6 05:02:52 hcsousa kernel: [<ce988920>] prism2_usb_driver [prism2_usb] 0x0 (0xc2a35e94)
Feb 6 05:02:52 hcsousa kernel: [<ce871c40>] usb_driver_list [usbcore] 0x0 (0xc2a35e9c)
Feb 6 05:02:52 hcsousa kernel: [<ce85fa8c>] usb_check_support [usbcore] 0x4c (0xc2a35eb0)
Feb 6 05:02:52 hcsousa kernel: [<ce85faa5>] usb_check_support [usbcore] 0x65 (0xc2a35ec4)
Feb 6 05:02:52 hcsousa kernel: [<ce871c48>] usb_bus_list [usbcore] 0x0 (0xc2a35ed0)
Feb 6 05:02:52 hcsousa kernel: [<ce85f153>] usb_scan_devices_Rca4f6301 [usbcore] 0x33 (0xc2a35ed8)
Feb 6 05:02:52 hcsousa kernel: [<ce988920>] prism2_usb_driver [prism2_usb] 0x0 (0xc2a35ee0)
Feb 6 05:02:52 hcsousa kernel: [<ce85f0fc>] usb_register_R8e1281a5 [usbcore] 0x7c (0xc2a35ee4)
Feb 6 05:02:52 hcsousa kernel: [<ce86af00>] .rodata.str1.32 [usbcore] 0x0 (0xc2a35ee8)
Feb 6 05:02:52 hcsousa kernel: [<ce982ab4>] .rodata.str1.1 [prism2_usb] 0x14 (0xc2a35eec)
Feb 6 05:02:52 hcsousa kernel: [<ce977f6b>] init_module [prism2_usb] 0x4b (0xc2a35f04)
Feb 6 05:02:52 hcsousa kernel: [<ce988920>] prism2_usb_driver [prism2_usb] 0x0 (0xc2a35f08)
Feb 6 05:02:52 hcsousa kernel: [<ce982c47>] .rodata.str1.1 [prism2_usb] 0x1a7 (0xc2a35f0c)
Feb 6 05:02:52 hcsousa kernel: [<ce982ab4>] .rodata.str1.1 [prism2_usb] 0x14 (0xc2a35f10)
Feb 6 05:02:52 hcsousa kernel: [<c011e697>] sys_init_module [kernel] 0x567 (0xc2a35f14)
Feb 6 05:02:52 hcsousa kernel: [<ce986708>] .kmodtab [prism2_usb] 0x0 (0xc2a35f24)
Feb 6 05:02:52 hcsousa kernel: [<ce976060>] prism2sta_open [prism2_usb] 0x0 (0xc2a35f2c)
Feb 6 05:02:52 hcsousa kernel: [<ce976060>] prism2sta_open [prism2_usb] 0x0 (0xc2a35f58)
Feb 6 05:02:52 hcsousa kernel: [<c01099df>] system_call [kernel] 0x33 (0xc2a35fc0)
Feb 6 05:02:52 hcsousa kernel:
Feb 6 05:02:52 hcsousa kernel:
Feb 6 05:02:52 hcsousa kernel: Code: 8b 1c d0 0f b6 43 04 39 c1 7d 4d 31 c0 89 44 24 14 8b 54 24
(sorry if i pasted to much useless info)
typing iwconfig and ifconfig, i can see that there is a wlan0 interface but,
result of iwconfig
wlan0 IEEE 802.11-b Mode:Auto Access Point: 00:00:00:00:00:00
Encryption key:off
result of ifconfig
wlan0 Link encap:Ethernet HWaddr 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)
Hardware address 000000000000??
I had noticed that this adapter does not respect the 802.11b standart (this adapter is capable of MAC address spoofing, just like ethernet card)
Your first attempt (with the delitek) looks more promising. The second was causing a kernel oops.
The usb device not responding is probably the same error as mentioned with the driver info: USB not accepting new address = xxx.
Try editing your usb.c and hub.c as described in the docs. This will hopefully ensure that the usb subsystem accepts the device and fires up the prism2_usb module.
By the looks of it you may need to remove the old p80211.o as well.
> Hardware address 000000000000??
> I had noticed that this adapter does not respect the 802.11b standart (this adapter is capable of MAC address spoofing, just like ethernet card)
The hardware address of all zeros is just because the driver hadn't loaded. You only need to set up the networking aspect (ifconfig etc..) when you know that the driver has correctly loaded.
i compiled a new kernel and it worked, thanks.
Is there a patch for 2.6.x kernels or they don't need it?