** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806472
Title:
RTL8822BE WiFi Disabled in Kernel 4.18.0-12
To manage notifications about this bug go to:
This bug was fixed in the package linux - 4.18.0-16.17
---
linux (4.18.0-16.17) cosmic; urgency=medium
* linux: 4.18.0-16.17 -proposed tracker (LP: #1814749)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CVE-2018-16880
- vhost: fix OOB in
This bug was fixed in the package linux - 4.15.0-46.49
---
linux (4.15.0-46.49) bionic; urgency=medium
* linux: 4.15.0-46.49 -proposed tracker (LP: #1814726)
* mprotect fails on ext4 with dax (LP: #1799237)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
*
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806472
Title:
RTL8822BE WiFi Disabled in Kernel 4.18.0-12
To
This looks like it works on 4.15.0-46-generic #49 now. Wifi seems to be
working while booted in secure mode.
modinfo attached showing it as signed with ver PKCS#7 / md4
lappy5k:~$ uname -a
Linux lappy5k 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
Didn't test this on a full install but enabled the 4.18.0-16 signed
kernel through the cosmic-proposed repository on a Bionic install. Works
fine! mokutil reports secure-boot enabled and release shows as 4.18.0-16
:)
It should be noted that just installing this kernel itself did not fix
the
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag
This bug was fixed in the package linux - 4.19.0-12.13
---
linux (4.19.0-12.13) disco; urgency=medium
* linux: 4.19.0-12.13 -proposed tracker (LP: #1813664)
* kernel oops in bcache module (LP: #1793901)
- SAUCE: bcache: never writeback a discard operation
* Disco update:
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu Cosmic)
Status: New => Triaged
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Cosmic)
Importance: Undecided => Medium
--
You received
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: Kai-Heng Feng (kaihengfeng)
Status: Confirmed
Hey,
This kernel seems to be working fine on a fresh install of KDE Neon
(based on Bionic). I had to roll back due to other reasons, but
installing this kernel has fixed it for me here. If you require any logs
let me know.
Short of reinstalling to 18.10 I haven't got a way to test it on there,
The drivers in staging won't get loaded when lockdown is enabled to
provide safety. There's a list to override behavior though.
The r8822be in its current form defaults to enable debugfs, which can be less
secure as it exposes and extra interface to userspace. But we are not sure if
the driver
So, the driver was previously unsigned, then signed and included in the
original Ubuntu kernel for 18.10, then subsequently unsigned during an
update somewhere along the way?
That doesn't make sense to me - would have to try and find upstream to work out
what has happened.
Larry Finger suggests
Installed 18.04 LTS with kernel 4.15 - was required to disabled secure
boot mode to get the r8822be wifi module working. Seems unsigned here as
well.
lappy5k:~$ sudo uname -a
Linux lappy5k 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
modinfo,
Hey,
Still seems to be an issue with Kernel v4.18.0-13 too. Tried to modprobe
r8822be module and received the same "operation not permitted" error as
before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ ===SRU Justification===
+ [Impact]
+ Realtek 8822be doesn't work under kernel lockdown.
+
+ [Fix]
+ Add r8822be.ko to signature-inclusion, so it can be signed and be loaded
+ when lockdown is enabled.
+
+ [Test]
+ Since I can't signed the kernel so it's not tested.
+
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806472
Title:
RTL8822BE WiFi Disabled in Kernel 4.18.0-12
To
Thanks for your testing.
This means staging drivers don't work when kernel lockdown is enabled.
I'll discuss with kernel team members how to sort this out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yep, disabling Secure Boot seems to allow the driver to load no problem.
Attached is dmesg output of this boot sequence with Secure Boot disabled.
** Attachment added: "dmesg output secureboot disabled"
Ok, can you test if disabling secure boot in BIOS helps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806472
Title:
RTL8822BE WiFi Disabled in Kernel 4.18.0-12
To manage notifications about this
Hi, not sure what the hotkey was supposed to do if anything, I don't
have any dmesg entries after executing it and there's no change in the
status of the r8822be module when I attempt a modprobe afterwards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Please try the hotkey "Alt+PrintScreen+x", then reload rtl8822be?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806472
Title:
RTL8822BE WiFi Disabled in Kernel 4.18.0-12
To manage notifications
24 matches
Mail list logo
