Hi,
I have a laptop hp pavilion dv6110ca with bcm4311 wireless card. Three weeks ago it stopped working. I guess it’s dead because it doesn’t show up neither in windows nor in linux. It was the second time so I decided to buy d-link dwa-140 usb wireless adapter.
I’ve read the thread Getting Your Wireless to Work and did everything according to that threat. In YaST => Hardware => Hardware Information I see my usb wireless adapter and Kernel Driver is rt2870. When I checked /var/log/boot.msg I didn’t find any line with the word “firmware”, but I found these lines:
rt2870sta: module is from the staging directory, the quality is unknown, you have been warned.
usbcore: registered new interface driver rt2870
Error: Driver ‘rt2870’ is already registered, aborting…
usbcore: error -17 registering interface driver rt2870
Can that be a problem that I can’t get my wireless adapter connected?
I can see a lot of Access Points in my vicinity, but I can’t connect to any of them (some of them are open).
Thanks
benoix wrote:
> Hi,
> I have a laptop hp pavilion dv6110ca with bcm4311 wireless card. Three
> weeks ago it stopped working. I guess it’s dead because it doesn’t show
> up neither in windows nor in linux. It was the second time so I decided
> to buy d-link dwa-140 usb wireless adapter.
> I’ve read the thread Getting Your Wireless to Work and did everything
> according to that threat. In YaST => Hardware => Hardware Information I
> see my usb wireless adapter and Kernel Driver is rt2870. When I checked
> /var/log/boot.msg I didn’t find any line with the word “firmware”, but I
> found these lines:
>
>> rt2870sta: module is from the staging directory, the quality is unknown,
>> you have been warned.
>> usbcore: registered new interface driver rt2870
>> Error: Driver ‘rt2870’ is already registered, aborting…
>> usbcore: error -17 registering interface driver rt2870
>
> Can that be a problem that I can’t get my wireless adapter connected?
> I can see a lot of Access Points in my vicinity, but I can’t connect to
> any of them (some of them are open).
> Thanks
There were a number of HP laptops with problems in the BIOS that
caused overheating of the motherboard and failure of the PCI-E
interface. I had one of them, which was replaced by HP. I don’t know
how long the warranty situation existed, but you should check with HP
support giving model and serial number.
You made an unlucky choice of a USB stick. Any driver that comes from
staging is a vendor written driver. No Linux developer will devote
much time to sorting out that kind of problem.
To show you how bad such drivers are, error -17 means that the driver
is trying to create a file that already exists! That error is
certainly killing your device. If you are lucky, ndiswrapper with the
Windows driver might work.
Thanks. I’ll try ndiswrapper.
It is a second time that my wireless card gives me problems. First time I sent my laptop to hp and they changed wireless card to another one. It worked during one year and now I got the same problem, so I decided to buy usb adapter.
About error -17 can it be the reason that I have bcm4311 driver installed? May be some kind of interference? I’m a newbie so sorry for that kind of question. May be I need to reinstall old bcm4311 driver?
benoix wrote:
> Thanks. I’ll try ndiswrapper.
> It is a second time that my wireless card gives me problems. First time
> I sent my laptop to hp and they changed wireless card to another one. It
> worked during one year and now I got the same problem, so I decided to
> buy usb adapter.
> About error -17 can it be the reason that I have bcm4311 driver
> installed? May be some kind of interference? I’m a newbie so sorry for
> that kind of question. May be I need to reinstall old bcm4311 driver?
It has nothing to do with the BCM4311. It is a crappy, vendor-written
driver.
I found at the Ralink Technology: Home this:
Firmware RT2870USB(RT2870/RT2770)
Should I try to install it or disregard this firmware and try to install ndiswrapper?
Thanks
EEEEH have you tried clicking the boot button? i once had the same problom and i tried it, my computer started and i was able to play ping-pong, it was 1 of the happiest days of my life
I bought myself this Wi-Fi adapter and I don’t know from where to start to make it work in OpenSUSE.
On this link: rt2870sta - Debian Wiki it’s said that the driver is included in the kernel from the version 2.6.29-rc1
Because I think the OpenSUSE 11.2 is using the Kernel version 2.6.31, shouldn’t this device being recognized by OpenSUSE ?
I can get only the recognition of the device as a hardware device, but it’s not present in the Network Manager.
I’m using KDE 4 with OpenSUSE 11.2, 32 bit.
And here are my results for various commands:
Linux:/home/robert # lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 045e:006a Microsoft Corp. Wireless Optical Mouse (IntelliPoint)
Bus 001 Device 003: ID 07d1:3c0a D-Link System
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Linux:/home/robert # dmesg | less
....
2.416118] usb 1-2: new full speed USB device using uhci_hcd and address 3
2.587693] EXT4-fs (sda2): barriers enabled
2.594715] usb 1-2: New USB device found, idVendor=07d1, idProduct=3c0a
2.594721] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2.594727] usb 1-2: Product: 11n Adapter
2.594730] usb 1-2: Manufacturer: Ralink
2.594734] usb 1-2: SerialNumber: 1.0
2.595011] usb 1-2: configuration #1 chosen from 1 choice
....
Linux:/home/robert # dmesg | grep firmware
22.618869] platform microcode: firmware: requesting intel-ucode/0f-02-04
Linux:/home/robert # iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
Linux:/home/robert # su -c ifconfig
eth0 Link encap:Ethernet HWaddr 00:04:23:0C:31:65
UP BROADCAST 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 lg file transmission:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:76 errors:0 dropped:0 overruns:0 frame:0
TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:4728 (4.6 Kb) TX bytes:4728 (4.6 Kb)
On 04/18/2010 12:16 PM, robertgf wrote:
>
> Hi,
>
> I bought myself this Wi-Fi adapter and I don’t know from where to start
> to make it work in OpenSUSE.
>
> On this link: ‘rt2870sta - Debian Wiki’
> (http://wiki.debian.org/rt2870sta) it’s said that the driver is included
> in the kernel from the version 2.6.29-rc1
>
> Because I think the OpenSUSE 11.2 is using the Kernel version 2.6.31,
> shouldn’t this device being recognized by OpenSUSE ?
>
> I can get only the recognition of the device as a hardware device, but
> it’s not present in the Network Manager.
>
> I’m using KDE 4 with OpenSUSE 11.2, 32 bit.
>
> And here are my results for various commands:
>
>
> Code:
> --------------------
> Linux:/home/robert # lsusb
> Bus 001 Device 003: ID 07d1:3c0a D-Link System
The correct driver for the device is rt2800usb.ko, and it is in 11.2. It
seems as if the driver is not loaded. Please go to
So, after a long search I finally get this USB adaptor to work. Sadly, I managed to find the right procedure only for Ubuntu.
The problem is that I have the hardware version no.2 of this device (ID 07d1:3c0a D-Link System). The first version seems to work fine with no additional drivers.
On 05/29/2010 01:06 PM, robertgf wrote:
>
> So, after a long search I finally get this USB adaptor to work. Sadly, I
> managed to find the right procedure only for Ubuntu.
>
> The problem is that I have the hardware version no.2 of this device (ID
> 07d1:3c0a D-Link System). The first version seems to work fine with no
> additional drivers.
>
> For those interested, the best information for me was here: ‘dwa-140 -
> Documentation Ubuntu Francophone’
> (http://doc.ubuntu-fr.org/dwa-140#d-link_dwa-140_b2)
>
> Well, the site is in French but the file -Driver dwa 140 B2- is
> universal (in fact I think it’s a script).
>
> Maybe someone with a strong Linux background can adapt this for
> OpenSUSE, too.
Drivers do not usually depend on the distro - only the kernel.
There is a serious problem with that procedure. One should never mess
with the license that is provided in the original driver. That is like
messing with someone else’s copyright.
Well I tried to follow the instructions from the driver readme of d-link.
But didn’t succeed.
At least I activated the networkmanager and what a surprise :
It worked !!
I don’t know why but it’s running like hell.
Well my conclusion is: Linux is not for Dummy User.
On 06/14/2010 04:26 AM, frank 41BS wrote:
>
> Well I tried to follow the instructions from the driver readme of
> d-link.
> But didn’t succeed.
> At least I activated the networkmanager and what a surprise :
>
> It worked !!
>
> I don’t know why but it’s running like hell.
>
> Well my conclusion is: Linux is not for Dummy User.
That is unfortunately true, but look at the reason. Vendors for Winblows
either start with a limited range of hardware and test like crazy (the
box builders), or they test their device on a lot of different kinds of
boxes. These situations make it a lot more likely that your Novice User
(a more politically correct term) will be able to have the system just
run. At least it will start until the kernel bugs cause a BSOD or the
malware gets them.
With any Linux, the probability that any developer has run your hardware
is quite small in most cases, thus the system has had very little formal
testing. When you add the complication of using a vendor-written driver
that has never been seen by even the least-qualified Linux developer, is
it any wonder there are troubles? As an example, the first Realtek
driver that I tried for the DWA-130 worked like a champ on a 32-bit
system, but generated a kernel panic when used on a 64-bit system. After
I fixed most of the problems and sent a patch to Realtek, I got back a
beta version that does work for 64 bits. I have their permission to
rework it and include it in the staging directory of the kernel where
the standards are lower. You should hope that someone will do that for
the DWA-140. Then the device will work “out of the box”.
Hallo,
I´m a newbie and have the same problem with dwa 140, receiving error 17.
But I´ve read, that the rt2870 needs not only drivers but also firmware.
The question was asked but not answered. Ralink provides the firmware for linux.
My problem is: will I still be able to use the dwa 140 with windows xp, if I install linux firmware? If not I´ll just cut my losses.
On 06/18/2010 03:46 PM, mgzhr wrote:
>
> Hallo,
> I´m a newbie and have the same problem with dwa 140, receiving error
> 17.
> But I´ve read, that the rt2870 needs not only drivers but also
> firmware.
> The question was asked but not answered. Ralink provides the firmware
> for linux.
> My problem is: will I still be able to use the dwa 140 with windows xp,
> if I install linux firmware? If not I´ll just cut my losses.
Firmware is the code that gets loaded into the CPU on the device.
Before you read the rest of my posting, what do you think is the answer
to your question? If it has to be reloaded EVERY time, will it persist
across reboots?
Now for the answer “No”.
Why doesn’t Winblows need firmware? The answer is that it does - it just
has a massive data statement inside the driver for the info to be pushed
into the device. Why doesn’t Linux do it the same way? In fact, some
drivers do. It just depends on the copyright that the vendor puts on
those files.