Yes I think it's possible. Mount it, chroot (e.g. systemd-nspawn) into
the system and install the kernel packages.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822363
Title:
Booting h
So it's specific to AMD systems.
Does this only happened to EHCI (USB 2.0) ports? Does this happen when
it's connected to xHCI (USB 3.0)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/178
Can someone test #24? If the issue is still there then we need to raise
the issue to upstream.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838133
Title:
realtek r8822be kernel module
Public bug reported:
Release: Ubuntu 16.04.6 LTS (xenial)
Upgrading dkms from 2.2.0.3-2ubuntu11.6 to 2.2.0.3-2ubuntu11.7 (the
"fix" for https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827697)
breaks installation of custom kernels again, as it undoes the fixes done
for bug https://bugs.launch
I just tested 5.0.0-23-lowlatency kernel with the mouse plugged into a
USB3 port, and everything seems to be okay. So it does seem to be USB2
specific (I dont have any USB1 ports to test it on, sorry)
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
What is the kernel module wl for? where is it in the /lib/modules/'uname
-r'/?
cd /lib/modules/`uname -r`
find . -iname wl.ko
Kernel modules: iwlwifi, wl
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
Hi Kai-Heng~
I tried the steps mentioned in #24 to build a kernel with the latest
wireless-drivers-next modules. However, I'm getting the following error
at the last step:
$ INSTALL_MOD_STRIP=1 modules_install && sudo make install
modules_install: command not found
Is there anything else I need
I don't have the NFC chip.
With kernel 5.2.x, it happens always after hibernation, sometimes after
suspension, rarely after reboot. I'm occasionally able to restore it by
unloading/reloading the i2c_hid kernel module.
With kernel 4.19.61, the issue occurs sporadically, and I can always
solve it b
Yes it's `sudo make INSTALL_MOD_STRIP=1 modules_install && sudo make
install`.
The command gets cut halfway in the comment.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838133
Title:
Is it a clickpad?
https://wayland.freedesktop.org/libinput/doc/1.13.4/clickpad-softbuttons.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1831831
Title:
Touchpad does not respond Id
Hi Kai-Heng~
Thanks for the help. Now the 5.3.0-rc1+ kernel with wireless-drivers-
next builds properly. I rebooted into the new kernel (selected from GRUB
menu) and I can verify that wireless does not work.
I have attached a tarball containing the output of dmesg, journalctl
-b0, and lsmod on ma
rtw88 isn't in lsmod. Please unblacklist rtw88 and related modules,
reboot, and rerun instruction in comment #24.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838133
Title:
realtek r8
Public bug reported:
On an 18.04 amd64 system dm-verity reports:
device-mapper: table: 253:20: verity: Invalid number of feature args
device-mapper: ioctl: error adding target to table
when trying to use "veritysetup" to create a previously formatted verity
device that uses FEC. Without FEC it s
** Description changed:
On an 18.04 amd64 system dm-verity reports:
device-mapper: table: 253:20: verity: Invalid number of feature args
device-mapper: ioctl: error adding target to table
when trying to use "veritysetup" to create a previously formatted verity
device that uses FEC.
** Summary changed:
- dm-verity: Invalid number of feature args
+ "dm-verity: Invalid number of feature arg" with FEC due to "#
CONFIG_DM_VERITY_FEC is not set"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
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 1838844
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
It's very familiar to Bug #1788807.
I'm on 19.04.
How can I help to solve it?
1) $lsb_release -rd
Description:Ubuntu 19.04
Release:19.04
2) $ apt-cache policy bluez
bluez:
Установлен: 5.50-0ubuntu2
Кандидат: 5.50-0ubuntu2
Таблица версий:
*** 5.50-0ubunt
*** This bug is a duplicate of bug 1837783 ***
https://bugs.launchpad.net/bugs/1837783
** This bug has been marked a duplicate of bug 1837783
Snapping or workspace settings are broken >:]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Public bug reported:
Couldn't log into after upgrading to kernel 5.0.0-23. Loging prompt was
unresponsive.
The kernel version was: linux-image-5.0.0-23-generic. I had to downgrade back
to "4.18.0-25.26" to get back into the machine. further details in attached
file.
** Affects: 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 1838851
and then change the status of the bug to 'Confirmed'.
If, due to the nature
apport information
** Tags added: apport-collected bionic
** Description changed:
Couldn't log into after upgrading to kernel 5.0.0-23. Loging prompt was
unresponsive.
The kernel version was: linux-image-5.0.0-23-generic. I had to downgrade back
to "4.18.0-25.26" to get back into th
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1838851/+attachment/5280667/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838851
Ti
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1838851/+attachment/5280669/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/18
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1838851/+attachment/5280678/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1838851/+attachment/5280668/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1838851/+attachment/5280674/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1838851/+attachment/5280671/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838851
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1838851/+attachment/5280670/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838851
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1838851/+attachment/5280672/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1838851/+attachment/5280677/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838851
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1838851/+attachment/5280676/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1838851/+attachment/5280673/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1838851/+attachment/5280675/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Grepping the syslog for "colord" shows lots of EDID errors.
Aug 3 10:35:09 mypc dbus-daemon[961]: [system] Activating via systemd: service
name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.57'
(uid=121 pid=1389 comm="/usr/lib/gnome-settings-daemon/gsd-color "
label="un
Hi Kai-Heng,
I checked my /etc/modprobe.d/blacklist.conf file, however, rtwpci and
rtw88 are not blacklisted. I am not sure why both these kernel modules
are not loaded when booting with kernel 5.3.0-rc1+...
Should I try building 5.3.0-rc1+ with different options?
Jun
--
You received this bug
Edit .config and manually enable rtw88:
CONFIG_RTW88=m
CONFIG_RTW88_CORE=m
CONFIG_RTW88_PCI=m
CONFIG_RTW88_8822BE=y
CONFIG_RTW88_8822CE=y
CONFIG_RTW88_DEBUG=y
CONFIG_RTW88_DEBUGFS=y
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
This bug was fixed in the package dkms - 2.3-3ubuntu9.5
---
dkms (2.3-3ubuntu9.5) bionic; urgency=medium
* Fixup previous upload: find_module doesn't exist yet, and there's bad
boolean logic in the check if we've already dealt with obsoleted modules.
(LP: #1838245)
-- Math
Sorry, my fault. Today I saw in GNOME-Tweaks that the setting for
Mouseclick-Emulation was 'Finger' instead of 'Area' (I have a German Version,
sorry for not knowing the correct English Words in the menues). Finally I can
say, that the Touchpad works perfect in Ubuntu 18.04 LTS by running
$ sudo
You have been subscribed to a public bug:
1) lsb_release -rd
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
2) apt-cache policy zfsutils-linux
zfsutils-linux:
Installed: 0.8.1-1ubuntu5
Candidate: 0.8.1-1ubuntu5
Version table:
*** 0.8.1-1ubuntu5 500
500
** Package changed: zfsutils (Ubuntu) => zfs-linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1835697
Title:
Upgrade to zfsutils-linux 0.8.1-1ubuntu5 fails on Ubuntu 19.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Hello Kai-Heng,
I edited the .config file in wireless-drivers-next and manually added
the RTW88 drivers you mentioned above and then rebuilt the 5.3.0-rc1+
kernel.
After rebooting into the new kernel, I noticed that rtw88 and rtwpci
kernel modules are now loaded but wifi is still not working... I
43 matches
Mail list logo
