disable onboard wireless adapter

English Network/Internet
1

Hello everyone,

A computer i use at the moment has an onboard wireless adapter. Anyway, i have some weird problem and, although it shows i am connected to the internet, there is no data transfer, i.e i cant really use a browser and etc…
Ok, as i had a wireless pci adapter, i tried it and now it works. The problem is, knetworkmanager (opensuse 12.2 32 bits with kde 4.8) insists in asking the root password, then asking the kdewallet password, and the password of my connection. If i close it once, after some minutes it will ask again, and again, and that would be so the whole time.

Maybe you guys know how to blacklist this device, or a way to, as the topic name says, disable this onboard wireless adapter.
I read a thread in other forums, talking about bounding this MAC adress of your device to the connections MAC adress, so it wouldnt connect to any other MAC adress. i did that and it stills the same.

simultaneously, i tried, as other forum described, creating a blacklist file in /etc/modprobe.d/
and i did it too, and the content of the blacklist file is the following:
blacklist r8712u

still, no changes.

I would like to proceed correctly. Could anyone help me?

It is a medion desktop computer, found in Germany and maybe somewhere else.

this is the output of the iwconfig, if it is at least important:


tun0      no wireless extensions.

wlan0     unassociated  Nickname:"rtl_wifi"
          Mode:Managed  Access Point: Not-Associated   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

eth0      no wireless extensions.

wlan1     IEEE 802.11bg  ESSID:"FRITZ!Box Fon WLAN 7170"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:24:FE:AD:18:42   
          Bit Rate=54 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=42/70  Signal level=-68 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:13  Invalid misc:79   Missed beacon:0

Thanks in advance and kind regards.

Wilker

2

Most of the time, these onboard devices can be switched off in the BIOS. Did you try that?

3

Can you post the output of :


/sbin/lspci -nnk

This will be more useful I believe. You might also try rfkill to disable the radio of that particular card but I’m not sure if it has that granularity.

4

Sorry, forgot to tell that. I actually did that with the Bios long ago, but apparently didnt work. I tested under the °Integrated Peripherals" menu, and disabled the “on-board LAN controller”. It apparently worked for a while and then not anymore, then i ended up enabling it again. Anyway, i just did it again, and so far i havent received any ask to connect using the onboard device. Let me see if knetworkmanager will ask it again…

here is the output of /sbin/lspci -nnk

00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e30] (rev 03)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
        Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller [0300]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
        Kernel driver in use: i915
00:02.1 Display controller [0380]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e33] (rev 03)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 01)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
        Kernel driver in use: snd_hda_intel
00:1d.0 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 01)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
        Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] (rev 01)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
        Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] (rev 01)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
        Kernel driver in use: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] (rev 01)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
        Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] (rev 01)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
        Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
        Kernel driver in use: ata_piix
00:1f.2 IDE interface [0101]: Intel Corporation N10/ICH7 Family SATA Controller [IDE mode] [8086:27c0] (rev 01)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
        Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation N10/ICH 7 Family SMBus Controller [8086:27da] (rev 01)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7633]
        Kernel driver in use: i801_smbus
01:01.0 Network controller [0280]: Ralink corp. RT2561/RT61 802.11g PCI [1814:0301]
        Subsystem: Linksys WMP54G v4.1 [1737:0055]                                                                                          
        Kernel driver in use: rt61pci

Thank you both for the quick answer =)

5

Reread your post. There’s a couple of things outside the issue of the onboard card:

Somewhere somehow, you set connections to be “system connections” otherwise the root password would not be required.
The onboard card is working, something is wrong in the configuration of it.
Also, some connections using the onboard must be in the list of prefered networks And, you have an issue with kwallet.

What you can do. Get rid of the present connections. Establish a new one, but as soon as the config window opens, set the IP of your router as the gateway address, use 8.8.8.8 and 8.8.4.4 as DNS servers. In KDE’s network settings, set proxy to none if you’re not using a proxy.

6

Hi,

you mean i should remove the pci adapter and try to use the config you wrote only with the onboard device?
(i tried configuring as you wrote, with both devices inside, and somehow i couldnt reconnect, and knetworkmanager had a red shield with a white X over it then. until i deleted this connection, restarted and stablished a new one giving only the password and leting everything as it was, i couldnt return to the forum, i.e i had no internet connection.)

listen, this is my girlfriends computer. she (always used windows) said she had no problems with internet at the beginning, then she simply couldnt connect, so she tried using such usb adapters, and it would work so bad and after a while disconnect. (all that with windows 7)

so i came and installed opensuse, dual booting with her windows 7. with my pci adapter, internet works for both.
why it didnt work in windows anymore, dont know, and maybe it doesnt interest much, as she may have this pci adapter i put in, and network is actually working (in windows for example, it is never asked to connect using another device. it connects directly due to the pci adapter and so it is). in my opensuse, network works TOO, but kwallet annoys from time to time, as the onboard wants to connect too. (if i allow it to connect, something weird happens and i simply cant access anything. knetworkmanager shows as both connected, the pci and the onboard)
sprry for detailing too much, i just think it could somehow help, knowing a little the history.

7

On 10/11/2012 09:36 AM, wilker91 wrote:
>
> Knurpht;2495210 Wrote:
>> Reread your post. There’s a couple of things outside the issue of the
>> onboard card:
>>
>> Somewhere somehow, you set connections to be “system connections”
>> otherwise the root password would not be required.
>> The onboard card is working, something is wrong in the configuration of
>> it.
>> Also, some connections using the onboard must be in the list of
>> prefered networks And, you have an issue with kwallet.
>>
>> What you can do. Get rid of the present connections. Establish a new
>> one, but as soon as the config window opens, set the IP of your router
>> as the gateway address, use 8.8.8.8 and 8.8.4.4 as DNS servers. In KDE’s
>> network settings, set proxy to none if you’re not using a proxy.
>
> Hi,
>
> you mean i should remove the pci adapter and try to use the config you
> wrote only with the onboard device?
> (i tried configuring as you wrote, with both devices inside, and
> somehow i couldnt reconnect, and knetworkmanager had a red shield with a
> white X over it then. until i deleted this connection, restarted and
> stablished a new one giving only the password and leting everything as
> it was, i couldnt return to the forum, i.e i had no internet
> connection.)
>
> listen, this is my girlfriends computer. she (always used windows) said
> she had no problems with internet at the beginning, then she simply
> couldnt connect, so she tried using such usb adapters, and it would work
> so bad and after a while disconnect. (all that with windows 7)
>
> so i came and installed opensuse, dual booting with her windows 7. with
> my pci adapter, internet works for both.
> why it didnt work in windows anymore, dont know, and maybe it doesnt
> interest much, as she may have this pci adapter i put in, and network is
> actually working (in windows for example, it is never asked to connect
> using another device. it connects directly due to the pci adapter and so
> it is). in my opensuse, network works TOO, but kwallet annoys from time
> to time, as the onboard wants to connect too. (if i allow it to connect,
> something weird happens and i simply cant access anything.
> knetworkmanager shows as both connected, the pci and the onboard)
> sprry for detailing too much, i just think it could somehow help,
> knowing a little the history.

If you add a line that says “blacklist rt61pci” to
/etc/modprobe.d/50-blacklist.conf, the driver for the internal card will never
be loaded.

8

thank you, lwfinger, what you wrote disabled the onboard wireless adapter.
i was creating a wrong blacklist file. (/etc/modprobe.d/blacklist)
just a detail: rt61pci is actually the PCI adapter, the internal is r8712u

9

On 10/12/2012 12:16 AM, wilker91 wrote:
>
> lwfinger;2495239 Wrote:
>> On 10/11/2012 09:36 AM, wilker91 wrote:
>>>
>>> Knurpht;2495210 Wrote:
>>>> Reread your post. There’s a couple of things outside the issue of
>> the
>>>> onboard card:
>>>>
>>>> Somewhere somehow, you set connections to be “system connections”
>>>> otherwise the root password would not be required.
>>>> The onboard card is working, something is wrong in the configuration
>> of
>>>> it.
>>>> Also, some connections using the onboard must be in the list of
>>>> prefered networks And, you have an issue with kwallet.
>>>>
>>>> What you can do. Get rid of the present connections. Establish a new
>>>> one, but as soon as the config window opens, set the IP of your
>> router
>>>> as the gateway address, use 8.8.8.8 and 8.8.4.4 as DNS servers. In
>> KDE’s
>>>> network settings, set proxy to none if you’re not using a proxy.
>>>
>>> Hi,
>>>
>>> you mean i should remove the pci adapter and try to use the config
>> you
>>> wrote only with the onboard device?
>>> (i tried configuring as you wrote, with both devices inside, and
>>> somehow i couldnt reconnect, and knetworkmanager had a red shield
>> with a
>>> white X over it then. until i deleted this connection, restarted and
>>> stablished a new one giving only the password and leting everything
>> as
>>> it was, i couldnt return to the forum, i.e i had no internet
>>> connection.)
>>>
>>> listen, this is my girlfriends computer. she (always used windows)
>> said
>>> she had no problems with internet at the beginning, then she simply
>>> couldnt connect, so she tried using such usb adapters, and it would
>> work
>>> so bad and after a while disconnect. (all that with windows 7)
>>>
>>> so i came and installed opensuse, dual booting with her windows 7.
>> with
>>> my pci adapter, internet works for both.
>>> why it didnt work in windows anymore, dont know, and maybe it doesnt
>>> interest much, as she may have this pci adapter i put in, and network
>> is
>>> actually working (in windows for example, it is never asked to
>> connect
>>> using another device. it connects directly due to the pci adapter and
>> so
>>> it is). in my opensuse, network works TOO, but kwallet annoys from
>> time
>>> to time, as the onboard wants to connect too. (if i allow it to
>> connect,
>>> something weird happens and i simply cant access anything.
>>> knetworkmanager shows as both connected, the pci and the onboard)
>>> sprry for detailing too much, i just think it could somehow help,
>>> knowing a little the history.
>>
>> If you add a line that says “blacklist rt61pci” to
>> /etc/modprobe.d/50-blacklist.conf, the driver for the internal card
>> will never
>> be loaded.
>
> thank you, lwfinger, what you wrote disabled the onboard wireless
> adapter.
> i was creating a wrong blacklist file. (/etc/modprobe.d/blacklist)
> just a detail: rt61pci is actually the PCI adapter, the internal is
> r8712u

Interesting. The PCI adapter is external, but the USB one is internal.