| 2006-03-28 20:23:13 |
Konstantinos Togias |
bug |
|
|
added bug |
| 2006-03-28 20:24:51 |
Konstantinos Togias |
bug |
|
|
added attachment 'lshw.txt' (The output of lshw) |
| 2006-03-28 20:25:41 |
Konstantinos Togias |
bug |
|
|
added attachment 'lsusb.txt' (The output of lsusb -vv) |
| 2006-03-28 20:26:36 |
Konstantinos Togias |
bug |
|
|
added attachment 'lsmod.txt' (The output of lsmod) |
| 2006-03-28 20:31:49 |
Konstantinos Togias |
bug |
|
|
added attachment 'dmesg.txt' (Output of dmesg relative to rtl8187) |
| 2006-03-28 20:33:34 |
Konstantinos Togias |
bug |
|
|
added attachment 'iwconfig_wlan0.txt' (Outpout of iwconfig wlan0) |
| 2006-03-28 20:37:06 |
Konstantinos Togias |
bug |
|
|
added attachment 'iwlist_wlan0_scan_run_after_running_dhclient.txt' (iwlist wlan0 scan output) |
| 2006-03-28 20:38:07 |
Konstantinos Togias |
bug |
|
|
added attachment 'dhclient_wlan0.txt' (dhclient wlan0 output) |
| 2006-03-28 20:38:48 |
Konstantinos Togias |
bug |
|
|
added attachment 'ifconfig.txt' (ifconfig output) |
| 2006-04-22 09:01:56 |
Sitsofe Wheeler |
description |
I tried Netgear WG111v2 Wireless USB Adapter with Dapper Flight 5 (kernel 2.6.15-18-386).
When I plug WG111v2 into a usb port, r8187 module is loaded. I can see wlan0 interface with iwconfig wlan0. But the led on the adapter does not light.
Then I run iwlist wlan0 scan and get:
wlan0 Failed to read scan data : Operation not permitted
If I then run dhclient wlan0, dhclient fails to contact my dhcp server, but just after that iwlist wlan0 scan command manages to scan and detect my Access Point. It reports Signal level:0.
After that running dhclient fails to obtain an ip and even if i give a static ip the adapter fails to transmit any data. The same happens when configuring wlan0 through network-admin gui.
The specific adapter is not detected at all under breezy but works flawlessly with ndiswrapper under breezy.
I attach below the output of lshw, lsusb, lsmod, iwconfig, iwlist, dhclient and ifconfig.
Note: the original reporter indicated the bug was in package 'nic-usb-modules-2.6.15-18-386-di'; however, that package was not published in Ubuntu. |
I tried Netgear WG111v2 Wireless USB Adapter with Dapper Flight 5 (kernel 2.6.15-18-386).
When I plug WG111v2 into a usb port, r8187 module is loaded. I can see wlan0 interface with iwconfig wlan0. But the led on the adapter does not light.
Then I run iwlist wlan0 scan and get:
wlan0 Failed to read scan data : Operation not permitted
If I then run dhclient wlan0, dhclient fails to contact my dhcp server, but just after that iwlist wlan0 scan command manages to scan and detect my Access Point. It reports Signal level:0.
After that running dhclient fails to obtain an ip and even if i give a static ip the adapter fails to transmit any data. The same happens when configuring wlan0 through network-admin gui.
The specific adapter is not detected at all under breezy but works flawlessly with ndiswrapper under breezy.
I attach below the output of lshw, lsusb, lsmod, iwconfig, iwlist, dhclient and ifconfig.
Note: the original reporter indicated the bug was in package 'nic-usb-modules-2.6.15-18-386-di'; however, that package was not published in Ubuntu. |
|
| 2006-04-22 09:01:56 |
Sitsofe Wheeler |
title |
Netgear WG111v2 Wireless USB Adapter recognized but not functioning |
[r8187] Netgear WG111v2 Wireless USB Adapter recognized but not functioning |
|
| 2006-11-02 01:32:17 |
Andrew Ash |
None: status |
Unconfirmed |
Needs Info |
|
| 2006-11-02 01:32:17 |
Andrew Ash |
None: statusexplanation |
|
|
|
| 2007-03-29 05:48:35 |
Andrew Ash |
linux-source-2.6.15: assignee |
|
ash211 |
|
| 2007-03-29 05:48:35 |
Andrew Ash |
linux-source-2.6.15: statusexplanation |
|
Can you still confirm this on Feisty Beta or newer? |
|
| 2007-04-10 00:45:18 |
Andrew Ash |
linux-source-2.6.20: status |
Needs Info |
Fix Released |
|
| 2007-04-10 00:45:18 |
Andrew Ash |
linux-source-2.6.20: assignee |
ash211 |
|
|
| 2007-04-10 00:45:18 |
Andrew Ash |
linux-source-2.6.20: statusexplanation |
Can you still confirm this on Feisty Beta or newer? |
I'm closing this bug based on Elektranox's statements. If it's still a problem for you, Konstantinos, please let us know and we'll keep working on it.
Thanks |
|
