rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

Bug #1788997 reported by a on 2018-08-25
96
This bug affects 18 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned
Bionic
Medium
Unassigned

Bug Description

=== SRU Justification ===
[Impact]
Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36.

[Fix]
The commit that causes the regression works in mainline, so there are
some functional dependencies are not in 4.15.

Finding those dependencies can be hard since I don't have the hardware
to test with, also pulling new commits may cause new regression. So the
safest way to deal with this bug is to simply revert the regression
commit.

[Test]
User confirmed reverting the commit can fix the issue.

[Regression Potential]
Low. Realtek 8723be works without this commit.

=== Original Bug Report ===
When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK.

Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works.

The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: al 1234 F.... pulseaudio
 /dev/snd/controlC0: al 1234 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-05-27 (89 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Hewlett-Packard HP Notebook
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-33-generic N/A
 linux-backports-modules-4.15.0-33-generic N/A
 linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-33-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/01/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.02
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8137
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 99.02
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: Hewlett-Packard

Paul White (paulw2u) on 2018-08-25
affects: ubuntu → linux (Ubuntu)

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1788997

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
a (rqcv1762) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected bionic
description: updated
a (rqcv1762) wrote : CRDA.txt

apport information

a (rqcv1762) wrote : CurrentDmesg.txt

apport information

a (rqcv1762) wrote : IwConfig.txt

apport information

a (rqcv1762) wrote : Lspci.txt

apport information

a (rqcv1762) wrote : Lsusb.txt

apport information

a (rqcv1762) wrote : ProcCpuinfo.txt

apport information

apport information

a (rqcv1762) wrote : ProcEnviron.txt

apport information

apport information

a (rqcv1762) wrote : ProcModules.txt

apport information

a (rqcv1762) wrote : PulseList.txt

apport information

a (rqcv1762) wrote : RfKill.txt

apport information

a (rqcv1762) wrote : UdevDb.txt

apport information

a (rqcv1762) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
a (rqcv1762) wrote :

The above diagnosis was performed having started the computer with 4.15.0-33.36 amd64; as a result there was no network connection. To obtain network connection for submitting the data, a Gigaset USB Adapter 108 has been plugged in prior to running apport-collect 1788997.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
status: Incomplete → Triaged
Changed in linux (Ubuntu Bionic):
importance: Undecided → Medium
status: New → Triaged
Rene (gxrcr981) wrote :

I have hp-15-ac167nf with wireless chip rtl8723be and ubuntu xenial 16.04 LTS and HWE.

I got same issue: module rtl8723be option ant_sel=2 is not working anymore from kernel 4.15.0-33.

As a workaround I boot previous kernel 4.15.0-32 (from grub menu).
On same PC, I tried ubuntu bionic 18.04, and symptoms are exactly the same.

Heribert Heckhoff (hheckhoff) wrote :

Same story here with HP 17-y009ng, 16.04 worked like a charm, with ant_sel=2 ( after having had a hard time to find out that this option was a must).

Kernel 4.15.0.32 worked as well after upgrade to 18.04-1.

No more wifi signal after update to kernel 4.1.5.0-33. Tried all other module options but had no success.

Currently booting with kernel 4.15.0-32 ....

Changed in linux (Ubuntu):
status: Triaged → In Progress
Changed in linux (Ubuntu Bionic):
status: Triaged → In Progress
Changed in linux (Ubuntu):
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Bionic):
assignee: nobody → Joseph Salisbury (jsalisbury)
Joseph Salisbury (jsalisbury) wrote :

I built a test kernel with a revert of commit af8a41cccf8f469165c6debc8fe07c5fd2ca501a. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997

Can you test this kernel and see if it resolves this bug?

Note about installing test kernels:
* If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages.
* If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

a (rqcv1762) wrote :

Thx! With the test kernel from http://kernel.ubuntu.com/~jsalisbury/lp1788997 according to #21 wifi of the laptop HP 1S-af023ngof works again. So reverting commit af8a41cccf8f469165c6debc8fe07c5fd2ca501a seems to fix the bug.

Rene (gxrcr981) wrote :

Hello,
I have difficulties trying your test kernel.
maybe because I use signed kernel with secure boot ?

In the instruction you talk about
linux-image and linux-image-extra .deb packages
linux-image-extra is not in folder.
image is unsigned, and do not install.

So I installed headers, modules, modules-extra.
rtl8723be do not load anymore (because not signed).

Could you confirm test procedure for 16.04 LT HWE with uefi secureboot ?
Thank you in advance.

Heribert Heckhoff (hheckhoff) wrote :

A new kernel update 4.15.0.34 has been provided recently. This kernel doesn't work with / support rtl8723be either. It seems the fix has not been committed so far.

18.4.1 typically keeps two kernels, unless you modify /etc/kernel/postinst.d/apt-auto-removal, so to keep more kernels. Hence users that installed the latest kernel update will have not more kernel installed that supports rtl8723be !!

The changes, that were applied in 4.15.0.33, have completely broken all system with rtl8223be meanwhile, unless you've made changes to the system how it handles kernel updates.

So I think there is evidence to provide a kernel update including the fixes to support rtl8723be immediately.

- Heribert

Joseph Salisbury (jsalisbury) wrote :

I'll ping upstream and the author of the patch that was reverted. However, before doing so, we should test the latest mainline kernel to see if the bug is already fixed upstream.

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3

Heribert Heckhoff (hheckhoff) wrote :

I've tested with the kernel as recommended and suggest in #25. Wifi with rtl8723b3 works again (like a charm). However, ant_sel must be set to 1 (ant_sel=1) as opposed to kernel 4.15.0-32, which required ant_sel to be set to 2 (ant_sel=2). (e.g sudo modprobe rtl8723be ant_sel=1 vs. sudo modprobe rtl8723be ant_sel=2).

Heribert Heckhoff (hheckhoff) wrote :

I don't know how to add a tag to or mark this bug track. :-;

tags: added: kernel-fixed-upstream
Changed in linux (Ubuntu Bionic):
status: In Progress → Confirmed
Heribert Heckhoff (hheckhoff) wrote :

found how to set the tag and marked status as confirmed.

Joseph Salisbury (jsalisbury) wrote :

We can perform a "Reverse" bisect to identify the commit that fixes this bug in v4.19. We first need to identify the last bad kernel version and the first good kernel version.

Can you test the following kernels:
v4.16 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/
v4.17 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17/
v4.18 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18/
v4.19-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc1/

You don't have to test every kernel, just up until the first kernel that does not have the bug.

Thanks in advance!

Changed in linux (Ubuntu Bionic):
status: Confirmed → In Progress
Heribert Heckhoff (hheckhoff) wrote :

4.16 does not work at all.
4.17 and 4.18 work just fine.
Haven't tested 4.19-rc1 though anymore, as suggested.

Joseph Salisbury (jsalisbury) wrote :

We next need to identify which 4.17 release candidate introduced the fix. Can you next test the following kernels:

v4.17-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc1
v4.17-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc4
v4.17-rc7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7

Like before, you don't have to test every kernel, just up until the first kernel that does not have the bug.

Thanks in advance!

Heribert Heckhoff (hheckhoff) wrote :

v4.17-rc4 just works fine.
v4.17-rc1 doesn't work at all (yields no , or a very, very weak signal).

I do not know Linux kernel process, but i would like to know if and when this fix will appear by defautl into Ubuntu doing a sudo apt upgrade ?
Thanks and sorry for such basic question.

Joseph Salisbury (jsalisbury) wrote :

@Stephane Potier, once we identify the fix, I will SRU it to the Ubuntu kernel. At that point, the fix will be applied for the following round of updates.

Heribert Heckhoff (hheckhoff) wrote :

neither rc2 or rc3 work at all...very low signal ...

Joseph Salisbury (jsalisbury) wrote :

Just to confirm, v4.17-rc4 works? I'll start a "Reverse" bisect between v4.17-rc3 and v4.17-rc4.

Joseph Salisbury (jsalisbury) wrote :

I think this commit should fix the bug:
af8a41cccf8f rtlwifi: cleanup 8723be ant_sel definition

However, this commit was added to Bionic in 4.15.0-33, which I believe you already tested. Can you test -proposed or newer than -33 to see if this bug is fixed? If not, there is only one other rtl commit in v4.17-rc4.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Thank you in advance!

royden (ryts) wrote :

" Can you test -proposed or newer than -33 to see if this bug is fixed?"

Tested with 4.15.0-36 and -24 which was distributed a few days back - same problem as originally reported, with either ant_sel 1 or 2.

royden (ryts) wrote :

I meant to type "-34" and of course it was -36 that was released recently.

Joseph Salisbury (jsalisbury) wrote :

I started a "Reverse" kernel bisect between v4.17-rc3 final and v4.17-rc4. The kernel bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
2e171ffcdf62a90ea7a0192728f81c1ac288de50

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

Heribert Heckhoff (hheckhoff) wrote :

The bug is fixed with this kernel (http://kernel.ubuntu.com/~jsalisbury/lp1788997), as long as you select antenna 1 (i.e. modprobe rtl8723be ant_sel=1).

Joseph Salisbury (jsalisbury) wrote :

Does this workaround also work with the current 4.15.0-36 kernel available in updates: modprobe rtl8723be ant_sel=1

Are does it only work with the test kernel I posed in comment #41?

Heribert Heckhoff (hheckhoff) wrote :

I have never seen kernel 4.15.0-36 ... was this ever released ?

royden (ryts) wrote :

@jsalisbury: ant_sel=1 with 4.15.0-36 kernel gives no improvement, both ant_sel 1 & 2 yield a poor signal.

So, I believe http://kernel.ubuntu.com/~jsalisbury/lp1788997 has the problem fixed, but only with ant_sel=1.

Joseph Salisbury (jsalisbury) wrote :

Thanks for the feedback. The kernel posted in comment #41 was the first of a series needed for the reverse bisect. There will be about 7 in total.

I built the next test kernel, up to the following commit:
e002434e88882d8f8205619b5b8f1d8e373a2724

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

Heribert Heckhoff (hheckhoff) wrote :

The Kernel (4.17.0-041700rc2-generic_4.17.0-041700rc2.201810101258_amd64) posted in comment #46 just works great with ant_sel=1 . Signal level is as good as with 4.15.0-32-generic.

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, up to the following commit:
e8e9608116593a54915a6ca8e343210e3aa6bce3

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

Heribert Heckhoff (hheckhoff) wrote :

The Kernel (4.17.0-041700rc2-generic_4.17.0-041700rc2.201810111939) posted in comment #48 just works great with ant_sel=1 . Signal level is as good as with 4.15.0-32-generic.

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, up to the following commit:
cc2180a5880d0fd8491182cdc65e8df9696a7c9e

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

Heribert Heckhoff (hheckhoff) wrote :

Kernel as of comment #50 (4.17.0-041700rc2-generic_4.17.0-041700rc2.201810121135) doesn't work. Very weak signal for both ant_sel=1 or ant_sel2.

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, up to the following commit:
1da9a586a2ed78d0b5fab4c0cc0473b873e48346

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

royden (ryts) wrote :

"The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997"

linux-headers-4.17.0-041700rc2-generic_4.17.0-041700rc2.201810151529_amd64

This kernel has wifi working just fine, ant_sel=1.

Heribert Heckhoff (hheckhoff) wrote :

comment #53 confirmed .

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, up to the following commit:
6a9a27d5397fc6c52f90c09ddab91e65053584aa

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

royden (ryts) wrote :

"I built the next test kernel, up to the following commit:
6a9a27d5397fc6c52f90c09ddab91e65053584aa

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997"

From #55, this kernel has poor wifi reception, both ant_sel=1 and 2.

dekl (dekl) wrote :

HP Pavilion Notebook (V0Z66EA#ACB)
Ubuntu 18.04.1
4.15.0-32-generic -- rtl8723be works fine with ant_sel=2
4.15.0-38-generic -- rtl8723be very weak signal with ant_sel=0 and with ant_sel=1 and doesn't work at all with ant_sel=2

dekl (dekl) wrote :

I also have tried Ubuntu 18.10 -- rtl8723be worked fine out-of-the-box, even without any ant_sel explicitly given.

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.

dekl (dekl) wrote :

Do you mean
linux-image-4.18.0-8-generic/bionic-proposed 4.18.0-8.9~18.04.1 amd64 ?

Joseph Salisbury (jsalisbury) wrote :

It would be the 4.15 based Bionic proposed kernel, which is at version: 4.15.0-38.41

Bionic proposed now has the following commit:
c4748a936d6c rtlwifi: cleanup 8723be ant_sel definition

That would rule out that commit as being the fix. If the bug still happens with proposed, we can continue the reverse bisect with has about 2-3 more kernels to test.

royden (ryts) wrote :

Tested bionic-proposed kernel 4.15.0-38.41.

There now is no difference between ant_sel=0,1,or 2 BUT compared to 4.15.0-32 ant_sel=2, the reception is 70% as opposed to 100%.

Go figure :-)

dekl (dekl) wrote :

Sorry, but it seems the kernels 4.15.0-38 in bionic-updates and in bionic-proposed are the same. I have tested it already (#57), the bug is in place. I would be happy to help test other kernels.

Rene (gxrcr981) wrote :

I tested last proposed kernel 4.15.0-39, but the issue is still there, no signal with either no ant_sel, ant_sel=0, ant_sel=1 or ant_sel=2.
In my environment the last working kernel is 4.15.0-32 with ant_sel=2.

Rene (gxrcr981) wrote :

I also tested last kernel from mainline (following #25 & #26 ,just for confirmation...)
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19
modinfo rtl8723be says:
filename: /lib/modules/4.19.0-041900-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723be/rtl8723be.ko
firmware: rtlwifi/rtl8723befw_36.bin
firmware: rtlwifi/rtl8723befw.bin
srcversion: CF0CBB2F4446A615D0ABCBE

similarily with comment #58 wifi works out of the box (no ant_sel)
it works also fine with ant_sel=0 (supposed to be equivalent)
it works also fine with ant_sel=1
does not work with ant_sel=2
like for comment #53, the working ant_sel changed compared to reference kernel 4.15.0-32

Heribert Heckhoff (hheckhoff) wrote :

I can confirm comment #65 :-)

fidel (akism89) wrote :

Works on 4.15.0-36 but not on 4.15.0-38...

spi (spi-gmxpro) wrote :

Still doesn't work in 4.15.0-42 either.

Changed in linux (Ubuntu Bionic):
status: In Progress → Confirmed
Changed in linux (Ubuntu):
status: In Progress → Confirmed
Changed in linux (Ubuntu Bionic):
assignee: Joseph Salisbury (jsalisbury) → nobody
Changed in linux (Ubuntu):
assignee: Joseph Salisbury (jsalisbury) → nobody
jack lemon (mb0087) wrote :

This problem still exists for me on debian testing with 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1

Only if I put my laptop directly next to a device emitting a wifi network I am able to connect. Few meters away it already becomes unusable. ant_sel=1 makes it worse. ant_sel=2 not better.

Detailed information here:
http://forums.debian.net/viewtopic.php?f=5&t=140368&p=691244#p691244

Kai-Heng Feng (kaihengfeng) wrote :

Does reverting the simple commit help? If it helps then we should simply revert it.

The other route is to back port the functional changes this commit depends on, ranges from v4.15 to v4.17.

Heribert Heckhoff (hheckhoff) wrote :

well...this bug has been unresolved for more than 6 month meanwhile, which is pretty hard for me to understand. I think it is common understanding that the Linux community is fixing bugs more or less instantaneously, as opposed to Microsoft Windows. Reverting a code change is a no brainer, which leave the question why this bug is not fixed with a kernel update. Quite a few contributers, as well as myself, have tested kernels that fix the bug, let alone, that no "official" fix has been released meanwhile. This is pretty much frustrating.

I can as well not agree that breaking a functionality completely can be considered as "medium impact"..

I mean we started out with kernel 4.15 and we're at 4.20 / 5.0 meanwhile ...

Kai-Heng Feng (kaihengfeng) wrote :

AFAIU, mainline kernel works, but with different ant_sel value.
On currently Ubuntu kernel, it doesn't work at all, correct?

Heribert Heckhoff (hheckhoff) wrote :

well, I have not seen any "officially released" kernel beyond 4.15.0-32, that works .

royden (ryts) wrote :

I guess folk like myself who upgraded to Cosmic and 4.18 have a working wifi with ant_sel=1. Bionic has the problem, ironically given that it is LTS.

BTW, I suspect there are other issues with the rtl8723be under 4.18 - my connection stalls after a while, until modprobe -r && modprobe then all is well again

Kai-Heng Feng (kaihengfeng) wrote :

So for Bionic, the commit should be reverted.

Please test this kernel:
https://people.canonical.com/~khfeng/lp1788997/

jack lemon (mb0087) wrote :

For me ant_sel=0 "zero!" was the magic key. Took me a week of messing around until I realized one cannot only select 1 or 2 but also 0. Try out with these:

sudo modprobe -r rtl8723be
sudo modprobe rtl8723be ant_sel=0
iwlist scan | egrep -i 'ssid|quality'
sudo modprobe -r rtl8723be
sudo modprobe rtl8723be ant_sel=1
iwlist scan | egrep -i 'ssid|quality'
sudo modprobe -r rtl8723be
sudo modprobe rtl8723be ant_sel=2
iwlist scan | egrep -i 'ssid|quality'

http://forums.debian.net/viewtopic.php?f=5&t=140368&p=691244#p691244

Heribert Heckhoff (hheckhoff) wrote :

 kernel 4.15.0-46 works as good as -4.15.0-32, i.e. with the same setting (ant_sel=2 only)

Heribert Heckhoff (hheckhoff) wrote :

hmm, well...I'm not sure what happened...

the kernel created of the packages from https://people.canonical.com/~khfeng/lp1788997/ (post #75) just works great.

However, I run an update as well later this day and that included (supposingly) the very same packages. However the kernel generated from those packages does not work at all. Strange, as both kernel packages have the very same version number ...

The generated kernel files do as well differ ( first column as of #75, second column as of update )

initrd.img-4.15.0-46-generic /boot/initrd.img-4.15.0-46-generic differ: byte 5, line 1
System.map-4.15.0-46-generic /boot/System.map-4.15.0-46-generic differ: byte 11352, line 334
vmlinuz-4.15.0-46-generic /boot/vmlinuz-4.15.0-46-generic differ: byte 159, line 4

I guess it's normal that initrd.img differ, as there seems to be a time stamp at the beginning of the image ....

uname reveals for the kernel as of post #75 reveals:

Linux heri-hp-pc 4.15.0-46-generic #49 SMP Fri Mar 8 13:21:42 CST 2019 x86_64 x86_64 x86_64 GNU/Linux

uname for the kernel after the update reveals:

Linux heri-hp-pc 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

pretty weird :-(

Kai-Heng Feng (kaihengfeng) wrote :

Sorry, I didn't bump the version number of the test kernel I built. I'll send a patch to revert the patch.

description: updated
Heribert Heckhoff (hheckhoff) wrote :

hmm, well, I had the test kernel as of #75 installed , which was overridden by a regular update today...and guess what, that kernel , as already mentioned in #78, does NOT work. So manual intervention is required to revert to the test kernel again. This is NOT very handy :-((

The expectation is that BIONIC should continue to fully support RTL8723b, which it doesn't meanwhile for more than 7 (in words SEVEN) month.

Kai-Heng Feng (kaihengfeng) wrote :

It'll be included in next kernel release.

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

Other bug subscribers