rtl8723be cannot connect to wifi since Kernel version 4.15.0-33-generic

Bug #1796576 reported by Alessio "Spinus" Moscatello
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Starting from Kernel version linux-image-4.15.0-33-generic I cannot connect anymore to wifi network. The problem occurs also with linux-image-4.15.0-34-generic.
Kernel version linux-headers-4.15.0-32-generic is working fine.

My current configuration for rtl8723be is
/etc/modprobe.d/rtlbtcoex.conf:
options rtl8723be ant_sel=2 ips=0

I'm using these parameters with for rtl8723be module in order to get the correct gain for Wifi antenna.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-modules-extra-4.15.0-34-generic 4.15.0-34.37
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alessio 1778 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 7 19:16:55 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=9d050d63-7a5d-443b-9210-3f51da9bf26f
InstallationDate: Installed on 2017-02-20 (593 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:b008 Realtek Semiconductor Corp.
 Bus 001 Device 003: ID 1bcf:2c87 Sunplus Innovation Technology Inc.
 Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Notebook
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=6c5ccef4-fabc-435b-a40b-c3d11c52cbfe ro quiet splash pci=noaer vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-34-generic N/A
 linux-backports-modules-4.15.0-34-generic N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-08-21 (46 days ago)
dmi.bios.date: 12/12/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.25
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8216
dmi.board.vendor: HP
dmi.board.version: 83.14
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.25:bd12/12/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.14:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

Revision history for this message
Alessio "Spinus" Moscatello (spinus) wrote :
Revision history for this message
Alessio "Spinus" Moscatello (spinus) wrote :

Attaching dmesg output

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Thank you in advance!

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-bisect
Revision history for this message
Alessio "Spinus" Moscatello (spinus) wrote :

Hello,
sorry for the delay, I've tested kernel 4.15.0-38-generic, but the problem is not solved.
Wifi seems, connect, but I cannot ping my domestic router...it seems that there are some problem sending packet on the Wifi connection, rather than establishing the connection with the Wifi router...
Is there any other test I can perform?

eno1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
        ether c8:d3:ff:dd:dd:31 txqueuelen 1000 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 0 bytes 0 (0.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
        inet 127.0.0.1 netmask 255.0.0.0
        inet6 ::1 prefixlen 128 scopeid 0x10<host>
        loop txqueuelen 1000 (Loopback locale)
        RX packets 799 bytes 49878 (49.8 KB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 799 bytes 49878 (49.8 KB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Dhclient is not working...I've set a static ip, but interface is not working...
wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.0.110 netmask 255.255.255.0 broadcast 192.168.0.255
        inet6 fe80::1383:e55e:d490:37a7 prefixlen 64 scopeid 0x20<link>
        ether 58:00:e3:ae:66:3b txqueuelen 1000 (Ethernet)
        RX packets 7 bytes 610 (610.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 71 bytes 12872 (12.8 KB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlo1 IEEE 802.11 ESSID:"Linux"
          Mode:Managed Frequency:2.462 GHz Access Point: DC:EF:09:51:23:49
          Bit Rate=150 Mb/s Tx-Power=20 dBm
          Retry short limit:7 RTS thr=2347 B Fragment thr:off
          Power Management:on
          Link Quality=46/70 Signal level=-64 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:24 Missed beacon:0

Regards,
Alessio

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Alessio "Spinus" Moscatello (spinus) wrote :

Hello,
just a quick update: using Kernel version 4.15.0-39-generic I was able to connect to wifi, but after switching on and off some times the Wifi...so the problem is partially solved, but there is still something not working fine.

BR,
Alessio

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.