[Kernel-packages] [Bug 2046714] [NEW] Boot failed, /dev/mapper/ubuntu--vg-ubuntu--lv does not exist.
Public bug reported:
I have installed Ubuntu Server on My VisionFive v2, the Kernel version is
6.5.0-14-generic, I notice the new Kernel linux-image-starfive(= 6.5.0.1005.7)
was released and I upgrade it, and then VisionFive v2 crashes while it boots.
the initramfs message:
ALERT! /dev/mapper/ubuntu--vg-ubuntu--lv does not exist. Dropping to a shell!
Hope it could be fixed soon. Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-starfive 6.5.0.1005.7
ProcVersionSignature: Ubuntu 6.5.0-14.14.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic riscv64
ApportVersion: 2.27.0-0ubuntu5
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Dec 18 07:00:45 2023
InstallationDate: Installed on 2023-09-19 (90 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release riscv64
(20231011)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=tmux-256color
SourcePackage: linux-meta-starfive
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: linux-meta-starfive (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug mantic riscv64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-starfive in Ubuntu.
https://bugs.launchpad.net/bugs/2046714
Title:
Boot failed, /dev/mapper/ubuntu--vg-ubuntu--lv does not exist.
Status in linux-meta-starfive package in Ubuntu:
New
Bug description:
I have installed Ubuntu Server on My VisionFive v2, the Kernel version is
6.5.0-14-generic, I notice the new Kernel linux-image-starfive(= 6.5.0.1005.7)
was released and I upgrade it, and then VisionFive v2 crashes while it boots.
the initramfs message:
ALERT! /dev/mapper/ubuntu--vg-ubuntu--lv does not exist. Dropping to a
shell!
Hope it could be fixed soon. Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-starfive 6.5.0.1005.7
ProcVersionSignature: Ubuntu 6.5.0-14.14.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic riscv64
ApportVersion: 2.27.0-0ubuntu5
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Dec 18 07:00:45 2023
InstallationDate: Installed on 2023-09-19 (90 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release riscv64
(20231011)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=tmux-256color
SourcePackage: linux-meta-starfive
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-starfive/+bug/2046714/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046105] Re: Sound: Add rtl quirk of M90-Gen5
** Tags removed: verification-needed-jammy-linux-oem-6.1 verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.1 verification-done-jammy-linux-oem-6.5 ** Changed in: hwe-next Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046105 Title: Sound: Add rtl quirk of M90-Gen5 Status in HWE Next: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] When plugin the headset jack, only speaker is identified. [Fix] Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work. [Test] Vendor tested on hardware, headset mic works fine. [Where problems could occur] It may break audio. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046131] Re: drm/amd: Disable PSR-SU to fix the brightness issue
** Tags removed: verification-needed-jammy-linux-oem-6.1
verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.1
verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2046131
Title:
drm/amd: Disable PSR-SU to fix the brightness issue
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Bug description:
[Impact]
Sometimes the brightness isn't changed on gnome menu.
[Fix]
The TCON is random hung by PSR-SU.
Add a workaround to disable PSR-SU until the real fix.
[Test]
Tested on hardware, the brightness is changed as expected.
[Where problems could occur]
It may break AMD display.
Note: This commit is replaced by commit: cd2e31a9ab93d13c4
("drm/amd/display: Set minimum requirement for using PSR-SU on
Phoenix") in v6.5, but new commit failed to fix the original issue,
disable PSR-SU again by this commit.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046131/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046217] Re: Some machines can't pass the pm-graph test
>From the log in pstore the issue was caused by iwlwifi. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046217 Title: Some machines can't pass the pm-graph test Status in linux-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 package in Ubuntu: In Progress Status in linux-hwe-6.5 source package in Jammy: New Status in linux-signed-hwe-6.5 source package in Jammy: New Bug description: During the jammy-hwe migration test, I found some machines failed to run the pm-graph. test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604) One of machine when I rerun it locally, it passed, but others are still failed. Following are the machines failed to run pm-graph. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201702-25401/ https://certification.canonical.com/hardware/202002-27718/ https://certification.canonical.com/hardware/201711-25989/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Tue Dec 12 02:48:24 2023 InstallationDate: Installed on 2023-02-22 (293 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2046217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046681] Re: jammy-oem-6.5: one more pannel needs to disable psr2
** Description changed: - tracking + BugLink: https://bugs.launchpad.net/bugs/2046681 + + [Impact] + The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly + + [Fix] + There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. + + [Test case] + + booting with the patched kernel, If the pannel's edid is in the qurik + list, the PSR2 will be disabled (checking + /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not + in the quirk list, the graphic driver will work as before. + + [Where problems could occur] + It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046681 Title: jammy-oem-6.5: one more pannel needs to disable psr2 Status in HWE Next: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
ODM verify passed on Orchid Bay MLK2 FHD panel. So verification done forlinux-oem-6.5 ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046681] [NEW] jammy-oem-6.5: one more pannel needs to disable psr2
Public bug reported: tracking ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: originate-from-2045640 ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-6.5 (Ubuntu) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Tags added: originate-from-2045640 ** Also affects: hwe-next Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046681 Title: jammy-oem-6.5: one more pannel needs to disable psr2 Status in HWE Next: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: tracking To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
6.5.13 > "Test amd64/build failed (rc=2, on=amd64, time=0:07:36,
log=amd64/log)".
@superm1
In 6.6.6 this issue seems fixed FYI.
--
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/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085]
Unfortunately, I think the issue is still not resolved. The touchpad still disconnects for me on a fully updated Fedora 39 with Gnome 45.2. -- 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: Applying
[Kernel-packages] [Bug 1834085]
I tested it. The trackpad worked for more than an hour without the same disconnections every 10 minutes that we had before. But an hour later it disconnected and could not restore the connection. Only restarting bluetooth helped. This happened several times. The problem has not yet been resolved. Fedora 39. -- 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev:
[Kernel-packages] [Bug 2046660] [NEW] Jammy update: v6.1.65 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.65 upstream stable release from git://git.kernel.org/ Linux 6.1.65 io_uring: fix off-by one bvec index USB: dwc3: qcom: fix wakeup after probe deferral USB: dwc3: qcom: fix software node leak on probe errors usb: dwc3: set the dma max_seg_size usb: dwc3: Fix default mode initialization USB: dwc2: write HCINT with INTMASK applied usb: typec: tcpm: Skip hard reset when in error recovery USB: serial: option: don't claim interface 4 for ZTE MF290 USB: serial: option: fix FM101R-GL defines USB: serial: option: add Fibocom L7xx modules usb: cdnsp: Fix deadlock issue during using NCM gadget bcache: fixup lock c->root error bcache: fixup init dirty data errors bcache: prevent potential division by zero error bcache: check return value from btree_node_alloc_replacement() dm-delay: fix a race between delay_presuspend and delay_bio hv_netvsc: Mark VF as slave before exposing it to user-mode hv_netvsc: Fix race of register_netdevice_notifier and VF register hv_netvsc: fix race of netvsc and VF register_netdevice USB: serial: option: add Luat Air72*U series products s390/dasd: protect device queue against concurrent access io_uring/fs: consider link->flags when getting path for LINKAT bcache: fixup multi-threaded bch_sectors_dirty_init() wake-up race md: fix bi_status reporting in md_end_clone_io bcache: replace a mistaken IS_ERR() by IS_ERR_OR_NULL() in btree_gc_coalesce() swiotlb-xen: provide the "max_mapping_size" method ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CVA arm64: dts: imx8mn-var-som: add 20ms delay to ethernet regulator enable NFSD: Fix checksum mismatches in the duplicate reply cache NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update() ext4: make sure allocate pending entry not fail ext4: fix slab-use-after-free in ext4_es_insert_extent() ext4: using nofail preallocation in ext4_es_insert_extent() ext4: using nofail preallocation in ext4_es_insert_delayed_block() ext4: using nofail preallocation in ext4_es_remove_extent() ext4: use pre-allocated es in __es_remove_extent() ext4: use pre-allocated es in __es_insert_extent() ext4: factor out __es_alloc_extent() and __es_free_extent() ext4: add a new helper to check if es must be kept media: qcom: camss: Fix genpd cleanup media: qcom: camss: Fix V4L2 async notifier error path media: qcom: Initialise V4L2 async notifier later media: camss: Convert to platform remove callback returning void media: camss: Split power domain management MIPS: KVM: Fix a build warning about variable set but not used cifs: fix leak of iface for primary channel cifs: account for primary channel in the interface list cifs: distribute channels across interfaces based on speed cifs: print last update time for interface list smb3: allow dumping session and tcon id to improve stats analysis and debugging cifs: minor cleanup of some headers lockdep: Fix block chain corruption USB: dwc3: qcom: fix ACPI platform device leak USB: dwc3: qcom: fix resource leaks on probe deferral nvmet: nul-terminate the NQNs passed in the connect command i40e: Fix adding unsupported cloud filters i40e: use ERR_PTR error print in i40e messages arm64: mm: Fix "rodata=on" when CONFIG_RODATA_FULL_DEFAULT_ENABLED=y mm,kfence: decouple kfence from page granularity mapping judgement afs: Fix file locking on R/O volumes to operate in local mode afs: Return ENOENT if no cell DNS record can be found net: axienet: Fix check for partial TX checksum amd-xgbe: propagate the correct speed and duplex status amd-xgbe: handle the corner-case during tx completion amd-xgbe: handle corner-case during sfp hotplug octeontx2-pf: Fix ntuple rule creation to direct packet to VF with higher Rx queue than its PF arm/xen: fix xen_vcpu_info allocation alignment net/smc: avoid data corruption caused by decline net: usb: ax88179_178a: fix failed operations during ax88179_reset ipv4: Correct/silence an endian warning in __ip_do_redirect HID: fix HID device resource race between HID core and debugging support drm/rockchip: vop: Fix color for RGB888/BGR888 format on VOP full drm/i915: do not clean GT table on error path ata: pata_isapnp: Add missing error check for devm_ioport_map() octeontx2-pf: Fix memory leak during interface down wireguard: use DEV_STATS_INC() drm/panel: simple: Fix Innolux G101ICE-L01 timings drm/panel: simple: Fix Innolux G101ICE-L01 bus flags drm/panel: auo,b101uan08.3: Fine tune the panel power sequence drm/panel: boe-tv101wum-nl6: Fine tune the panel power sequence afs: Make error on cell
Re: [Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot
On Fri, Dec 15, 2023 at 3:55 PM Sam Tannous <2043...@bugs.launchpad.net> wrote: > > You're correct. It can fail for other reasons. I don't think we could check > the errno, could we? It would be 1, "Operation not permitted". The exit code is not documented in the manpage, and it appears to exit 1 with other failure types: root@dannf-kdump-chroot:~# unshare -U true unshare: unshare failed: No space left on device root@dannf-kdump-chroot:~# echo $? 1 I also suspect this is not the only situation that could return -EPERM. > If not, I think we can live with the last suggestion. ACK. As you can see above, I've uploaded that change to noble, and will begin the SRU process back to jammy. -dann -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2043059 Title: Installation errors out when installing in a chroot Status in kdump-tools package in Ubuntu: Fix Released Status in linux-nvidia package in Ubuntu: Invalid Bug description: Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.15.0-1040-nvidia ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.15.0-1040-nvidia cryptsetup: WARNING: Couldn't determine root device W: Couldn't identify type of root file system for fsck hook cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-5.15.0-1040-nvidia mkinitramfs: failed to determine device for / mkinitramfs: workaround is MODULES=most, check: grep -r MODULES /var/lib/kdump/initramfs-tools Error please report bug on initramfs-tools Include the output of 'mount' and 'cat /proc/mounts' update-initramfs: failed for /var/lib/kdump/initrd.img-5.15.0-1040-nvidia with 1. run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1 dpkg: error processing package linux-image-5.15.0-1040-nvidia (--configure): installed linux-image-5.15.0-1040-nvidia package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-5.15.0-1040-nvidia E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2043059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046657] [NEW] mmc: sdhci-of-dwcmshc: Replace sauce patches with upstream commits
Public bug reported: SRU Justification: [Impact] The msdhci-of-dwcmshc driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. [Test Case] * Boot BF3 platform, verify no new errors [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2046657 Title: mmc: sdhci-of-dwcmshc: Replace sauce patches with upstream commits Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The msdhci-of-dwcmshc driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. [Test Case] * Boot BF3 platform, verify no new errors [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2046657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046656] [NEW] Jammy update: v6.1.64 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.64 upstream stable release from git://git.kernel.org/ Linux 6.1.64 RISC-V: drop error print from riscv_hartid_to_cpuid() cxl/port: Fix NULL pointer access in devm_cxl_add_port() mmc: sdhci-pci-gli: GL9755: Mask the replay timer timeout of AER Input: xpad - add VID for Turtle Beach controllers tracing: Have trace_event_file have ref counters powerpc/powernv: Fix fortify source warnings in opal-prd.c drm/amd/display: Change the DMCUB mailbox memory location from FB to inbox drm/amd/display: Enable fast plane updates on DCN3.2 and above drm/amd/display: fix a NULL pointer dereference in amdgpu_dm_i2c_xfer() drm/amdgpu: lower CS errors to debug severity drm/amdgpu: fix error handling in amdgpu_bo_list_get() drm/amdgpu: don't use ATRM for external devices drm/amdgpu: don't use pci_is_thunderbolt_attached() drm/amdgpu/smu13: drop compute workload workaround drm/amd/pm: Fix error of MACO flag setting code drm/i915: Fix potential spectre vulnerability drm/i915: Bump GLK CDCLK frequency when driving multiple pipes drm/amd/pm: Handle non-terminated overdrive commands. ext4: properly sync file size update after O_SYNC direct IO ext4: add missed brelse in update_backups ext4: remove gdb backup copy for meta bg in setup_new_flex_group_blocks ext4: correct the start block of counting reserved clusters ext4: correct return value of ext4_convert_meta_bg ext4: mark buffer new if it is unwritten to avoid stale data exposure ext4: correct offset of gdb backup in non meta_bg group to update_backups ext4: apply umask if ACL support is disabled Revert "net: r8169: Disable multicast filter for RTL8168H and RTL8107E" media: qcom: camss: Fix csid-gen2 for test pattern generator media: qcom: camss: Fix invalid clock enable bit disjunction media: qcom: camss: Fix missing vfe_lite clocks check media: qcom: camss: Fix VFE-480 vfe_disable_output() media: qcom: camss: Fix VFE-17x vfe_disable_output() media: qcom: camss: Fix vfe_get() error jump media: qcom: camss: Fix pm_domain_on sequence in probe mmc: sdhci-pci-gli: GL9750: Mask the replay timer timeout of AER r8169: add handling DASH when DASH is disabled r8169: fix network lost after resume on DASH systems mptcp: fix setsockopt(IP_TOS) subflow locking mptcp: add validity check for sending RM_ADDR mptcp: deal with large GSO size mm: kmem: drop __GFP_NOFAIL when allocating objcg vectors mm: fix for negative counter: nr_file_hugepages mmc: sdhci-pci-gli: A workaround to allow GL9750 to enter ASPM L1.2 riscv: kprobes: allow writing to x0 riscv: correct pt_level name via pgtable_l5/4_enabled riscv: mm: Update the comment of CONFIG_PAGE_OFFSET LoongArch: Mark __percpu functions as always inline nfsd: fix file memleak on client_opens_release dm-verity: don't use blocking calls from tasklets drm/mediatek/dp: fix memory leak on ->get_edid callback error path drm/mediatek/dp: fix memory leak on ->get_edid callback audio detection media: ccs: Correctly initialise try compose rectangle media: venus: hfi: add checks to handle capabilities from firmware media: venus: hfi: fix the check to handle session buffer requirement media: venus: hfi_parser: Add check to keep the number of codecs within range media: sharp: fix sharp encoding media: lirc: drop trailing space from scancode transmit f2fs: avoid format-overflow warning f2fs: do not return EFSCORRUPTED, but try to run online repair i2c: i801: fix potential race in i801_block_transaction_byte_by_byte net: phylink: initialize carrier state at creation net: dsa: lan9303: consequently nested-lock physical MDIO net: ethtool: Fix documentation of ethtool_sprintf() s390/ap: fix AP bus crash on early config change callback invocation i2c: designware: Disable TX_EMPTY irq while waiting for block length byte sbsa_gwdt: Calculate timeout with 64-bit math lsm: fix default return value for inode_getsecctx lsm: fix default return value for vm_enough_memory Revert "i2c: pxa: move to generic GPIO recovery" Revert ncsi: Propagate carrier gain/loss events to the NCSI controller cxl/region: Fix x1 root-decoder granularity calculations tools/testing/cxl: Define a fixed volatile configuration to parse cxl/mem: Move devm_cxl_add_endpoint() from cxl_core to cxl_mem cxl: Unify debug messages when calling devm_cxl_add_port() i3c: master: svc: fix random hot join failure since timeout error i3c: master: svc: add NACK check after start byte sent cxl/region: Do not try to cleanup after cxl_region_setup_targets() fails cxl/region: Move region-position validation to a helper
[Kernel-packages] [Bug 2046085] Re: Problem with driver for Realtek 8852be Wi-Fi pci card
Hi, I contacted manufacturer and they have told me that most likely wifi module is broken. They sent me a replacement and it works out of the box now. So I think this bug can be closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2046085 Title: Problem with driver for Realtek 8852be Wi-Fi pci card Status in linux-firmware package in Ubuntu: Incomplete Bug description: I am not sure that this shall come into Ubuntu bug tracker, but correct me if I am wrong. I have a fan-less media pc that has PCI WI-FI adapter rtl8852be. I know this chipset has support in HWE Ubuntu kernel but for some reason, firmware for it still not being recognized. First I tried to make it work with 6.2 generic HWE kernel and the only strings I have in dmesg: [ 15.034783] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 15.061504] rtw89_8852be :03:00.0: no suitable firmware found [ 15.061543] rtw89_8852be :03:00.0: failed to recognize firmware [ 15.061557] rtw89_8852be :03:00.0: failed to setup chip information [ 15.075283] rtw89_8852be: probe of :03:00.0 failed with error -2 Then I tried to use linux-image-6.5.0-1009-oem kernel and get a little bit more info: [ 16.501540] rtw89_8852be :03:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin [ 16.503083] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 16.567443] rtw89_8852be :03:00.0: xtal si not ready(R): offset=41 [ 16.567470] rtw89_8852be :03:00.0: no suitable firmware found [ 16.567494] rtw89_8852be :03:00.0: failed to recognize firmware [ 16.567509] rtw89_8852be :03:00.0: failed to setup chip information [ 16.572860] rtw89_8852be: probe of :03:00.0 failed with error -2 I suspect my PCI WIFI card has different subvendor ID and subdevice ID compare to the popular ones: Lenovo laptops have 8852be has PCI 10ec:b852:17aa:4853 HP laptops have 8852be has PCI 10ec:b852:103c:88e3 Mine is: PCI 10ec:b852:10ec:b852 Any suggestions are welcomed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.23 ProcVersionSignature: Ubuntu 6.5.0-1009.10-oem 6.5.3 Uname: Linux 6.5.0-1009-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sun Dec 10 21:46:40 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.4 InstallationDate: Installed on 2023-09-15 (86 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b85b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 006: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SDZ X133 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1009-oem root=UUID=cd870d97-e484-43d5-aafa-2ba1ec68a7a8 ro cpufreq.default_governor=powersave RelatedPackageVersions: linux-restricted-modules-6.5.0-1009-oem N/A linux-backports-modules-6.5.0-1009-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2023 dmi.bios.release: 1.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: PC_STICK_8G_D8R2 dmi.board.asset.tag: Default string dmi.board.name: X133 dmi.board.vendor: SDZ dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: SDZ dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrPC_STICK_8G_D8R2:bd05/12/2023:br1.20:svnSDZ:pnX133:pvrDefaultstring:rvnSDZ:rnX133:rvrDefaultstring:cvnSDZ:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Notebook dmi.product.name: X133 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: SDZ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2046085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
