Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

wlan connection issues

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
User avatar
ozgta
Posts: 465
Joined: 2009-05-25 02:32
Location: Nth Qld

wlan connection issues

#1 Post by ozgta »

Hi,
Running Stretch testing with xfce4
New installation.
During installation I chose to run the download using wlan. Wlan was recognized by the Debian installer and all went well.
After the installation I tried to connect via wlan however this fails.

Using realtek rtl8187B usb stick which has in the past been faultless and needs no configuration (this was used during the install)
$ lsusb recognizes the usb stick

Network manager recognizes the network SSID and I can enter the password however no connection.

iwconfig

Code: Select all

root@db64:/# iwconfig
enp2s0    no wireless extensions.

wlx00027298befc  IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

          
lo        no wireless extensions.

root@db64:/# 

00027298befc in the above is the Realtek usb device

All network packages were installed with the original installation so i do not believe I am missing any packages.

Any advice on how to fix this would be greatly appreciated.


User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: wlan connection issues

#3 Post by stevepusser »

There's been posts here about the 4.9 Stretch kernel breaking Realtek wifi devices because their USB ID numbers have been added to another kernel driver. What driver shows as being used for that device now with

Code: Select all

lsusb -t
MX Linux packager and developer

User avatar
ozgta
Posts: 465
Joined: 2009-05-25 02:32
Location: Nth Qld

Re: wlan connection issues

#4 Post by ozgta »

@ marcetm,
Thanks I'll look at the topics.
I did try to sort this myself for two days and searched topics here...must have used the wrong search terms :)


@stevepusser, thanks for the reply.
I guess this means something to you....
lsusb -t

Code: Select all

   nigel@db64:~$ lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
        |__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 6: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
        |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtl8187, 480M
nigel@db64:~$ 

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: wlan connection issues

#5 Post by stevepusser »

Sure, the one it's trying to use is rtl8187

Code: Select all

Driver=rtl8187
That gives us something to start with.
MX Linux packager and developer

User avatar
ozgta
Posts: 465
Joined: 2009-05-25 02:32
Location: Nth Qld

Re: wlan connection issues

#6 Post by ozgta »

Thanks stevepusser... a start is always good :)
Away from my computer for a few hours. I will get back to you.

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: wlan connection issues

#7 Post by stevepusser »

OK, if you plug in the stick and then run "dmesg" as root in the terminal, do you see anything there at the end about the device?
MX Linux packager and developer

User avatar
ozgta
Posts: 465
Joined: 2009-05-25 02:32
Location: Nth Qld

Re: wlan connection issues

#8 Post by ozgta »

@stevepusser

This is a the end of the 'dmesg' command

Code: Select all

  9.152784] rtl8187: Customer ID is 0x00
[    9.153647] rtl8187: wireless switch is on
[    9.153671] usbcore: registered new interface driver rtl8187
[   10.469028] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[   11.275550] Adding 4009980k swap on /dev/sda3.  Priority:-1 extents:1 across:4009980k FS
[   12.046031] rtl8187 2-1.6:1.0 wlx00027298befc: renamed from wlan0
[   13.899938] systemd[1]: apt-daily.timer: Adding 11h 5min 39.696443s random time.
[   13.957571] systemd[1]: apt-daily.timer: Adding 1h 20min 27.427405s random time.
[   16.384110] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[   16.414260] r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168e-3.fw
[   16.534187] r8169 0000:02:00.0 enp2s0: link down
[   16.534236] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[   16.555151] IPv6: ADDRCONF(NETDEV_UP): wlx00027298befc: link is not ready
[   20.393440] IPv6: ADDRCONF(NETDEV_UP): wlx00027298befc: link is not ready
[   24.329461] IPv6: ADDRCONF(NETDEV_UP): wlx00027298befc: link is not ready
[   25.620697] IPv6: ADDRCONF(NETDEV_UP): wlx00027298befc: link is not ready
root@db64:/home/nigel# 
Hope this helps....

User avatar
ozgta
Posts: 465
Joined: 2009-05-25 02:32
Location: Nth Qld

Re: wlan connection issues

#9 Post by ozgta »

I can see the line...
[ 12.046031] rtl8187 2-1.6:1.0 wlx00027298befc: renamed from wlan0
not sure if it is the problem...looking into it

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: wlan connection issues

#10 Post by stevepusser »

Is the 4.8 kernel still available in Stretch? The 4.9 seems to causing this issue.
MX Linux packager and developer

User avatar
ozgta
Posts: 465
Joined: 2009-05-25 02:32
Location: Nth Qld

Re: wlan connection issues

#11 Post by ozgta »

I have looked into the 4.8 kernel being available for stretch and from what my limited understanding tells me is....I'm not sure...I'm a bit out of my depth here :)

Bulkley
Posts: 6383
Joined: 2006-02-11 18:35
Has thanked: 2 times
Been thanked: 39 times

Re: wlan connection issues

#12 Post by Bulkley »

Does this look familiar? [SOLVED] WiFi package compile error after LXDE upgrade to kernel 4.9 Read this all the way through. It is a driver issue, not a kernel problem. The fix involves forcing the kernel to load a driver module at boot.

User avatar
ozgta
Posts: 465
Joined: 2009-05-25 02:32
Location: Nth Qld

Re: wlan connection issues

#13 Post by ozgta »

@ bulkley,
Thanks for the link, unfortunately in this instance it does not work.
I have been using the realtek 8187B for many years now on many Debian installs and it has proven to be faultless with no need for configuration.

lsusb recognizes the device.
The device recognizes the SSID
For me with my limited understanding this should be enough.....

I shall persevere....

User avatar
alekz
Posts: 68
Joined: 2008-11-06 20:21

Re: wlan connection issues

#14 Post by alekz »

Same issue here with Stretch + Realtek 8187, here goes my outputs.

Code: Select all

uname -a
Linux debian 4.9.0-3-amd64 #1 SMP Debian 4.9.25-1 (2017-05-02) x86_64 GNU/Linux
Output for dmesg:

Code: Select all

[    1.515779] usb 2-2: New USB device found, idVendor=0bda, idProduct=8187
[    1.515781] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.515782] usb 2-2: Product: RTL8187_Wireless
[    1.515783] usb 2-2: Manufacturer: Manufacturer_Realtek_RTL8187_
[    1.515784] usb 2-2: SerialNumber: 000F1065113B
[   11.487047] rtl8187: Customer ID is 0x00
[   11.487369] rtl8187: wireless switch is on
[   11.487391] usbcore: registered new interface driver rtl8187
[   12.860421] rtl8187 2-2:1.0 wlx000f1065113b: renamed from wlan0
[   31.955360] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[   89.984385] wlx000f1065113b: authenticate with c8:b3:73:3e:25:d3
[   90.257065] wlx000f1065113b: send auth to c8:b3:73:3e:25:d3 (try 1/3)
[   90.258770] wlx000f1065113b: authenticated
[   95.261539] wlx000f1065113b: aborting authentication with c8:b3:73:3e:25:d3 by local choice (Reason: 3=DEAUTH_LEAVING)
[   97.540347] wlx000f1065113b: authenticate with c8:b3:73:3e:25:d3
[   97.805293] wlx000f1065113b: send auth to c8:b3:73:3e:25:d3 (try 1/3)
[   97.807409] wlx000f1065113b: authenticated
[  102.808071] wlx000f1065113b: aborting authentication with c8:b3:73:3e:25:d3 by local choice (Reason: 3=DEAUTH_LEAVING)
[  105.484754] wlx000f1065113b: authenticate with c8:b3:73:3e:25:d3
[  105.745444] wlx000f1065113b: send auth to c8:b3:73:3e:25:d3 (try 1/3)
[  105.751611] wlx000f1065113b: authenticated
[  110.748324] wlx000f1065113b: aborting authentication with c8:b3:73:3e:25:d3 by local choice (Reason: 3=DEAUTH_LEAVING)
[  113.010862] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[  115.117259] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[  659.023492] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[  669.671665] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[  671.583986] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[  676.860092] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[  676.882168] wlx000f1065113b: authenticate with c8:b3:73:3e:25:d3
[  677.016733] wlx000f1065113b: send auth to c8:b3:73:3e:25:d3 (try 1/3)
[  677.018220] wlx000f1065113b: authenticated
[  682.022063] wlx000f1065113b: aborting authentication with c8:b3:73:3e:25:d3 by local choice (Reason: 3=DEAUTH_LEAVING)
[  695.632528] wlx000f1065113b: authenticate with c8:b3:73:3e:25:d3
[  695.905095] wlx000f1065113b: send auth to c8:b3:73:3e:25:d3 (try 1/3)
[  695.909528] wlx000f1065113b: authenticated
[  700.910301] wlx000f1065113b: aborting authentication with c8:b3:73:3e:25:d3 by local choice (Reason: 3=DEAUTH_LEAVING)
[  702.027810] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[  703.944948] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[  710.977396] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[  710.992532] wlx000f1065113b: authenticate with 34:b3:54:22:33:c4
[  711.126014] wlx000f1065113b: send auth to 34:b3:54:22:33:c4 (try 1/3)
[  711.127526] wlx000f1065113b: 34:b3:54:22:33:c4 denied authentication (status 13)
[  727.878608] wlx000f1065113b: authenticate with 34:b3:54:22:33:c4
[  728.150213] wlx000f1065113b: send auth to 34:b3:54:22:33:c4 (try 1/3)
[  728.151982] wlx000f1065113b: 34:b3:54:22:33:c4 denied authentication (status 13)
[  736.029060] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[  738.006135] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[  852.895280] perf: interrupt took too long (2541 > 2500), lowering kernel.perf_event_max_sample_rate to 78500
[ 1082.962441] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[ 1123.172094] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[ 1124.936163] wlx000f1065113b: authenticate with 34:b3:54:22:33:c4
[ 1125.212879] wlx000f1065113b: send auth to 34:b3:54:22:33:c4 (try 1/3)
[ 1125.214343] wlx000f1065113b: 34:b3:54:22:33:c4 denied authentication (status 13)
[ 1140.707955] perf: interrupt took too long (3285 > 3176), lowering kernel.perf_event_max_sample_rate to 60750
[ 1141.997162] wlx000f1065113b: authenticate with 34:b3:54:22:33:c4
[ 1142.273525] wlx000f1065113b: send auth to 34:b3:54:22:33:c4 (try 1/3)
[ 1142.275244] wlx000f1065113b: 34:b3:54:22:33:c4 denied authentication (status 13)
[ 1148.043870] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[ 1149.957599] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[ 1393.398604] perf: interrupt took too long (4228 > 4106), lowering kernel.perf_event_max_sample_rate to 47250
[ 1494.966855] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[ 1812.105948] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[ 2073.295661] r8169 0000:07:00.0 enp7s0: link down
[ 2083.167248] wlp6s0: deauthenticating from 34:b3:54:22:33:c4 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 2083.183845] IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
[ 2087.468141] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[ 2089.212333] wlx000f1065113b: authenticate with 34:b3:54:22:33:c4
[ 2089.488831] wlx000f1065113b: send auth to 34:b3:54:22:33:c4 (try 1/3)
[ 2089.491693] wlx000f1065113b: 34:b3:54:22:33:c4 denied authentication (status 13)
[ 2106.237287] wlx000f1065113b: authenticate with 34:b3:54:22:33:c4
[ 2106.513877] wlx000f1065113b: send auth to 34:b3:54:22:33:c4 (try 1/3)
[ 2106.515877] wlx000f1065113b: 34:b3:54:22:33:c4 denied authentication (status 13)
[ 2113.086567] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[ 2114.997507] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[ 2429.092649] IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
[ 2460.010161] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
[ 2603.351932] perf: interrupt took too long (5341 > 5285), lowering kernel.perf_event_max_sample_rate to 37250
[ 2744.109523] IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
[ 2777.062023] IPv6: ADDRCONF(NETDEV_UP): wlx000f1065113b: link is not ready
For lsusb:

Code: Select all

Bus 002 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
For lsusb -t

Code: Select all

    |__ Port 2: Dev 2, If 0, Class=(Defined at Interface level), Driver=rtl8187, 480M
When 'lspci -k' is performed, I can't see the Realtek Wireless Card:

Code: Select all

lspci -k
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
	Subsystem: Dell Broadwell-U Host Bridge -OPI
	Kernel driver in use: bdw_uncore
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)
	Subsystem: Dell HD Graphics 5500
	Kernel driver in use: i915
	Kernel modules: i915
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
	Subsystem: Dell Broadwell-U Audio Controller
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
	Subsystem: Dell Wildcat Point-LP USB xHCI Controller
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
	Subsystem: Dell Wildcat Point-LP MEI Controller
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
	Subsystem: Dell Wildcat Point-LP High Definition Audio Controller
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03)
	Subsystem: Dell Wildcat Point-LP USB EHCI Controller
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
	Subsystem: Dell Wildcat Point-LP LPC Controller
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
	Subsystem: Dell Wildcat Point-LP SATA Controller [AHCI Mode]
	Kernel driver in use: ahci
	Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
	Subsystem: Dell Wildcat Point-LP SMBus Controller
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
06:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
	Subsystem: Intel Corporation Dual Band Wireless AC 3160
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 07)
	Subsystem: Dell RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
	Kernel driver in use: r8169
	Kernel modules: r8169
.
For lshw -c network:

Code: Select all

  *-network
       description: Wireless interface
       physical id: 2
       bus info: usb@2:2
       logical name: wlx000f1065113b
       serial: ce:ce:67:f7:35:aa
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=rtl8187 driverversion=4.9.0-3-amd64 firmware=N/A link=no multicast=yes wireless=IEEE 802.11
For iwconfig:

Code: Select all

wlx000f1065113b  IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

Any idea, or we just have to wait for the bug to be solved?
Running: Testing
RSA Key ID (4096): 514F180C

User avatar
ozgta
Posts: 465
Joined: 2009-05-25 02:32
Location: Nth Qld

Re: wlan connection issues

#15 Post by ozgta »

@ alekz
Well I am clueless and hoping for a bug fix......

marcetm
Posts: 135
Joined: 2015-08-02 21:30

Re: wlan connection issues

#16 Post by marcetm »

Hi alekz

In my case the best solution was to put this line in /etc/modprobe.d/rtl8192ce.conf:

Code: Select all

options rtl8192ce ips=0 fwlps=0
You may want to give it a try. Also you should take a look at:

https://wiki.debian.org/rtl819x

if you haven't done it yet.

User avatar
ozgta
Posts: 465
Joined: 2009-05-25 02:32
Location: Nth Qld

Re: wlan connection issues

#17 Post by ozgta »

Thanks marcetm, I am currently overseas and will follow up on your post when I return home.

skunkworks
Posts: 5
Joined: 2017-07-06 18:46

Re: wlan connection issues

#18 Post by skunkworks »

None of this worked for me. What did work was from this bug report

https://bugs.debian.org/cgi-bin/bugrepo ... =842422#40

add

[device]
wifi.scan-rand-mac-address=no

to

/etc/NetworkManager/NetworkManager.conf

lcvette
Posts: 2
Joined: 2018-04-15 05:33

Re: wlan connection issues

#19 Post by lcvette »

skunkworks wrote:None of this worked for me. What did work was from this bug report

https://bugs.debian.org/cgi-bin/bugrepo ... =842422#40

add

[device]
wifi.scan-rand-mac-address=no

to

/etc/NetworkManager/NetworkManager.conf
i tried putting this in but it came back telling me file not found.. any thoughts?

Post Reply