so i have 2 network adapters in my laptop, one that doesn't work, and one (usb) that does. every time im connected to a wifi connection with the usb adapter, it runs fine. however whenever the adapter that does not work picks up the wifi signal stronger then the usb adapter dose, it drops the usb adapter and attempts to connect with the first one. i'm currently using ubuntu 15.10, and have been using ubuntu for about 3 months now. iv tried googling this, but got almost nothing other then a bunch of people saying that ubuntu needs a hardware manager. anyone have any suggestions of how to if not disable the other adapter, just turn the wifi detection off on it without killing my wifi entirely.
Why don't you just remove the non working adapter from networkmanager? I mean.. if it does not know the network its not going to connect. and the connection with your USB adapter should not be dropped
sorry kind of new to ubuntu still, the non functioning adapter is unfortunately the built in one. i really cant remove it. also every time it drops it goes to reconnect and brings up the wifi sign in page. with the other adapter selected. according to the wifi drop down the other adapter is picking up the wifi stronger then the working one. then once i deselect it and tell it to use the usb adapter it will connect until the cycle repeats.
Disable the dead NIC in the BIOS if you can, if not, you can shut it off from the terminal.
Find out which NIC is the dead one with
$ iwconfig
Then turn it off with
$ sudo ip link set 'NIC' down
1 Like
Ok, I assume that the interface that is built in is recognised as wlan0. So if you edit the /etc/network/interfaces with superuser rights. To do that open a terminal and type:
gksu gedit /etc/network/interfacesto the end of the file add:
iface wlan0 inet manualThat will set wlan0 to be manually configured, and thus network-manager wont use it.
Than after saving the file issue
sudo service network-manager restartAfter that the deffective nic should be ignored and not cause trouble.
1 Like
well this was what was in the interface file... i cant make heads or tails of it.
interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
After you edit it it should look like that:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
iface wlan0 inet manualGiven that the broken card is wlan0, but its my best bet as its the internal one.
ok, so after undoing what i just did... yeah its seeing the USB adapter as wlan0. looking at lspci and lsusb, iv noticed that even though its built in its running through the usb and not the pci. also its apparently a combo Bluetooth and wifi adapter. but yes attempt one has failed.
Many internal components are atatched to the USB bus.. trackpad for excample often are.
Ok, soooo the internal card... is recognised as wlan0? and the external adapter as wlan1?
Which did you try now? my suggestion or the one from Baz?
ok, so i did what @Baz told me to do and iwconfig. found the name and added that as manual in the interface. and by the way why the hell is it named "wlx6045bdd1b354"... ok so problem seems fixed for now ill let you know in about 2 or so hours how stable the connection is!
name of what and where? ^^ indeed a wired name
that is the name of the broken adapter!!!! yeah...
Ok, its the name on lsusb? or is that what its named as interface given by ifconfig? - you confuse me XD
iwconfig.
wired ^^ but you have to use that name instead of wlan0 than. Whats the name of the external dapter?
the external adapter was and still is wlan0. which is why it was not working before when i set wlan0 to manual. it killed the working adapter. it wasn't until i set wlx6045bdd1b354 to manual that it stopped the broken adapter.
1 Like
Sorry, I assumed the internal was wlan0 as it usually is... during setup normally the internal is present and thus given the first interface. my bad
its all good! everything seems to be working so far. i'm stress testing it at school to see how long the connection holds.
It should by now. The change to the config makes it so that the network-manager does not use the interface, and thus it wont look for wireless networks and can't connect.
sweet! hey thanks for the help with this, and patience!
1 Like