[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown
Kernel with the patch included: https://people.canonical.com/~khfeng/lp1912935/ -- 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/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1913812] Re: snd_fireworks module fails to load
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc5/amd64/ -- 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/1913812 Title: snd_fireworks module fails to load Status in linux package in Ubuntu: Confirmed Bug description: dmesg contains these two lines: [8.593334] snd_fireworks fw1.0: EFW transaction timed out [8.594276] snd_fireworks fw1.0: Sound card registration failed: -5 And ALSA therefore does not see my echo audiofire 12. The device continues to work fine as a backend for jackdbus2 using the FFADO kernel modules. The snd_fireworks did work fine with this device in ubuntustudio 20.04 but also fails in ubuntustudio 20.10 (which I don't use) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-modules-5.8.0-36-lowlatency 5.8.0-36.40+21.04.1 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-36-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu56 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jan 29 13:14:58 2021 Dependencies: InstallationDate: Installed on 2021-01-29 (0 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210128) IwConfig: lono wireless extensions. enp5s0no wireless extensions. Lsusb: Bus 002 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdb3 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-lowlatency N/A linux-backports-modules-5.8.0-36-lowlatency N/A linux-firmware 1.194 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/16/2013:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913812/+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 1908286] Re: Asus G732LWS | ALC294 | Speakers don't work on 20.04 or 20.10
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc5/amd64/ -- 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/1908286 Title: Asus G732LWS | ALC294 | Speakers don't work on 20.04 or 20.10 Status in linux package in Ubuntu: Confirmed Bug description: Asus G732LWS-DS76 Realtek ALC294 (Intel HDA Audio) Xubuntu 20.04 with kernel 5.4.0-58-generic No sound from speakers even though it shows in pavucontrol. For some reason the sound gets redirected to the internal mic (when I play music there is no sound from speakers, but when I open Audacity and start recording it records a song playing). I tried: alc294-sound-patch.fw from https://bugzilla.kernel.org/show_bug.cgi?id=206589 No effect "options snd-hda-intel model=asus-zenbook" in /etc/modprobe.d/alsa-base.conf Speakers start working, but it is impossible to control the volume, they're eithher ON (100%) or OFF (Muted) I tried different kernels and sidtributions to localize the problem: Doesn't work Xubuntu 20.04 | 5.4.0-58-generic Xubuntu 20.04 | 5.4.0-54-generic Xubuntu 20.04 | 5.4.0-48-generic Xubuntu 20.10 | 5.8.0-25-generic Fedora 33 | 5.8.15-301.fc33.x86_64 Manjaro 20.2 | 5.9.11-3-MANJARO WORKS Xubuntu 20.04 | 5.4.0-42-generic It appears that it is a kernel problem and something broke between 5.4.0-42-generic and 5.4.0-48-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kotek 5812 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Dec 15 09:25:13 2020 InstallationDate: Installed on 2020-10-01 (75 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ROG Strix G732LWS_G732LWS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=8d8cfa7f-5e24-4952-b6ae-4ae35ca9563d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G732LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G732LWS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG732LWS.310:bd07/14/2020:svnASUSTeKCOMPUTERINC.:pnROGStrixG732LWS_G732LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG732LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G732LWS_G732LWS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908286/+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 1910211] Re: Fix the video can't output through WD19TB connected with TGL platform during cold-boot
** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid -- 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/1910211 Title: Fix the video can't output through WD19TB connected with TGL platform during cold-boot Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] After Apply the patches from https://www.spinics.net/lists/intel-gfx/msg248700.html, the TGL platform would have the failure rate(1/20) on outputting the video through WD19TB. [Fix] The patch is provided by Imre(https://gitlab.freedesktop.org/drm/intel/-/issues/2801#note_740352). If there's no lttpr in the link chain, the DRM driver wouldn't configure the transparent mode again. [Test Case] 1. Connected the WD19TB with the TGL platform and connected the external monitor on WD19TB with HDMI/Displayport. 2. Don't plug the external monitor on the TGL platform, so there's only one monitor on WD19TB. 3. Cold boot the TGL platform. 4. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] As per Imre's comment, this may be caused by the dock. In the future if the WD19TB's firmware is updated, we may encounter the same issue again. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1910211/+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 1913933] Re: System freeze while dbus-daemon execution
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc5/amd64/ -- 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/1913933 Title: System freeze while dbus-daemon execution Status in linux package in Ubuntu: Confirmed Bug description: I regularly get my system frozen while using. It does not occur on any user interaction I do periodically, so I checked the log files last time it happened: These are the last 3 kernel log entries before the freeze: Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 audit(1612017269.344:43): apparmor="DENIED" operation="open" profile="snap.standard-notes.standard-notes" name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 label="snap.standard-notes.standard-notes" Jan 30 15:34:29 ubuntu kernel: [24749.903525] exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ So I think this is related to the dbus-daemon. If you need any more information, please let me know so I can provide them. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dbus 1.12.20-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Jan 31 09:22:49 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/bash SourcePackage: dbus UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chshr 2241 F pulseaudio /dev/snd/controlC0: chshr 2241 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52 MachineType: Micro-Star International Co., Ltd MS-7A34 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: groovy Uname: Linux 5.8.0-41-generic x86_64
[Kernel-packages] [Bug 1914020] Re: Fix no video output when boot up system with type-c port
verified on 5.10-oem-1013 ** Tags added: verification-done-focal -- 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/1914020 Title: Fix no video output when boot up system with type-c port Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] Connect a WD19SC/WD19TB/typeC2hdmi converter on the machine type-c port, video can't output to the external monitor. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/patch/msgid/2020110401.4165574-1-imre.d...@intel.com). Correct the typo during output setup. Fix a typo that led to some MST short pulse event handling issue (the short pulse event was handled for both encoder instances, each having its own state). [Test Case] 1. Connected the WD19SC/WD19TB/typeC2hdmi converter with the TGL platform's Type-C port and connected the external monitor on WD19SC/WD19TB/type-c2hdmi with HDMI/Displayport. 2. Cold boot the TGL platform. 3. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] Just correct the typo and have low regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914020/+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 1913372] Re: Fix the video can't output through WD19TB connected on TGL's Type-C port during cold-boot
verified on 5.10-oem-1013. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1913372 Title: Fix the video can't output through WD19TB connected on TGL's Type-C port during cold-boot Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] WD19TB would report the number of lane(2-lane) and it works well on Type-C port of TGL platform. Change the LTTPR mode to non-transparent mode, WD19TB would report the larger number of lane(4-lane). It's over the type-c port's bandwidth. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/series/86267/). Calculate the PBN divider value based on the rate and lane count link parameters that the driver uses for all other computation. [Test Case] 1. Connected the WD19TB with the TGL platform's Type-C port and connected the external monitor on WD19TB with HDMI/Displayport. 2. Cold boot the TGL platform. 3. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] It's more reasonable to calculate the PBN divider based on the source's rate and lane count, not the mst's capability. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1913372/+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 1887294] Re: [nvidia] Display freeze and kernel crash on GeForce GTX 1060 6GB
** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1887294 Title: [nvidia] Display freeze and kernel crash on GeForce GTX 1060 6GB Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Bug description: The display is completely frozen, and no signal is output to the monitors. There is also no signal when switching to a console (Ctr- Alt-F1). I have normal access via SSH. It happens about once in 14 days. Only happens when turning the display off or on (about once in 15 screen power cycles). nvidia-smi still works (via SSH; without any options) DISPLAY=:1 xset dpms force on hangs indefinitely. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Jul 12 17:47:58 2020 DistUpgraded: 2020-05-17 13:48:43,365 DEBUG entry '# deb [arch=amd64] https://repo.skype.com/deb stable main # disabled on upgrade to focal' was disabled (unknown mirror) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) v4l2loopback, 0.12.3, 5.4.0-39-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85ae] InstallationDate: Installed on 2016-07-27 (1445 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-17 (56 days ago) dmi.bios.date: 04/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8C WS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd04/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8CWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jul 7 22:02:38 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1887294/+subscriptions -- Mailing
[Kernel-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
*** This bug is a duplicate of bug 1914007 *** https://bugs.launchpad.net/bugs/1914007 ** This bug has been marked a duplicate of bug 1914007 RT3290 Bluetooth not finding any device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit:
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
** Changed in: pulseaudio (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1913682] Re: Fix no screen show on display after S3 on CML-R
** Changed in: linux (Ubuntu Focal) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Focal) Assignee: koba (kobako) => (unassigned) ** Changed in: linux (Ubuntu Groovy) Assignee: koba (kobako) => (unassigned) -- 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/1913682 Title: Fix no screen show on display after S3 on CML-R Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in linux-oem-5.10 source package in Groovy: New Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] On CML-R, after S3, No screen show on all three connector(3*DP). [Fix] The patch is got from https://patchwork.freedesktop.org/patch/416162/. For Legacy S3 suspend/resume GEN9 BC needs to enable and setup TGP PCH. [Test Case] 1. Connected the monitor on one of 3*DP on CML-R. 2. Suspend the machine. 3. Check the monitor can output something. [Where problems could occur] Just Enable the hpd detection in IRQ installer and during suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1913682/+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 1872908] Re: bcmwl kernel module does not build with kernel version 5.6 or 5.8
** Changed in: bcmwl (Ubuntu Focal) Milestone: None => ubuntu-20.04.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1872908 Title: bcmwl kernel module does not build with kernel version 5.6 or 5.8 Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Focal: Fix Released Bug description: After kernel update to 5.6.0-1007-oem wifi stopped working. Turned out dkms is unable to build the bcmwl module. The make log shows: ubuntu@ubuntu-inspiron-5482:~$ cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64) ons 15 apr 2020 09:19:05 CEST make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem' CFG80211 API is prefered for this kernel version Using CFG80211 API AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_reg_map’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ^~~ | ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: warning: returning ‘int’ from a function with return type ‘void *’ makes pointer from integer without a cast [-Wint-conversion] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ~^~~~ In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_set_auth_type’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5: warning: this statement may fall through [-Wimplicit-fallthrough=] 52 | if (wl_dbg_level & WL_DBG_DBG) { \ | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3: note: in expansion of macro ‘WL_DBG’ 816 | WL_DBG(("network eap\n")); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2: note: here 817 | default: | ^~~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_attach’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { |^~~ |ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18: warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_pci_probe’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 780 | if ((val & 0xff00) != 0) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 782 | bar1_size = pci_resource_len(pdev, 2); | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2), | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_reg_proc_entry’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58: error: passing argument 4 of ‘proc_create_data’ from incompatible pointer type [-Werror=incompatible-pointer-types] 3376 | if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, _fops, wl)) == NULL) { | ^~~~ |
[Kernel-packages] [Bug 1913853] Re: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- 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/1913853 Title: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging Status in linux package in Ubuntu: Fix Committed Bug description: Hi there, I've updated kernel on my Ubuntu 16.04 from 4.4.0-201-generic to 4.4.0.202-generic today and it broke my system. Basic commands, such as pidof, lsof, ps fax (ps -a works) hang indefinitely and not even root issued kill -KILL will terminate them. Only thing that helps is to kill the shell that started such commands. I had to reboot back to 4.4.0-201, however during shutdown various stop jobs hanged as well and after more than 25 minutes I had to go for hard reboot. My current—NOT BROKEN—kernel has signature (cat /proc/version_signature): Ubuntu 4.4.0-201.233-generic 4.4.247 I am attaching the lspci-vnvn.log, also created with the non-broken kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913853/+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 1914146] Re: package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- 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/1914146 Title: package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: New Bug description: none ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.6 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 1 18:51:48 2021 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-09 (54 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1914146/+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 1914146] [NEW] package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit statu
Public bug reported: none ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.6 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 1 18:51:48 2021 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-09 (54 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1914146 Title: package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: New Bug description: none ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.6 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 1 18:51:48 2021 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-09 (54 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1914146/+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 1914143] Missing required logs.
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 1914143 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 -- 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/1914143 Title: vmxnet3: update to latest ToT Status in linux package in Ubuntu: Incomplete Bug description: This request is to port vmxnet3 patches to Ubuntu ongoing kernel release. Below is the commit: vmxnet3: Remove buf_info from device accessible structures https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=de1da8bcf40564a2adada2d5d5426e05355f66e8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914143/+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 1914143] [NEW] vmxnet3: update to latest ToT
Public bug reported: This request is to port vmxnet3 patches to Ubuntu ongoing kernel release. Below is the commit: vmxnet3: Remove buf_info from device accessible structures https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=de1da8bcf40564a2adada2d5d5426e05355f66e8 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1914143 Title: vmxnet3: update to latest ToT Status in linux package in Ubuntu: New Bug description: This request is to port vmxnet3 patches to Ubuntu ongoing kernel release. Below is the commit: vmxnet3: Remove buf_info from device accessible structures https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=de1da8bcf40564a2adada2d5d5426e05355f66e8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914143/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
+1 same for me -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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 1913944] Re: broadcom wireless adapter disappears after reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1913944 Title: broadcom wireless adapter disappears after reboot Status in bcmwl package in Ubuntu: Confirmed Bug description: Used Updater to install additional drivers for my Broadcom wireless. It worked at first but when I booted up the next day the wifi icon was gone as if I had to wifi adapter at all. my specs: lspci -nn -d 14e4: 04:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01) This Below is what happens when I tried a fix that was suggested: sudo apt install bcmwl-kernel-source [sudo] password for anansi: Reading package lists... Done Building dependency tree Reading state information... Done bcmwl-kernel-source is already the newest version (6.30.223.271+bdcom-0ubuntu5). The following packages were automatically installed and are no longer required: libfprint-2-tod1 libllvm10 Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Removing old bcmwl-6.30.223.271+bdcom DKMS files... -- Deleting module version: 6.30.223.271+bdcom completely from the DKMS tree. -- Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-41-generic Building for architecture x86_64 Building initial module for 5.8.0-41-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-so urce.0.crash' Error! Bad return status for module build on kernel: 5.8.0-41-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more informati on. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess retur ned error exit status 10 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) Heeelp! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 08:27:11 2021 InstallationDate: Installed on 2021-01-27 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1913944/+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 1872908] Update Released
The verification of the Stable Release Update for bcmwl has completed successfully and the package is now being 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 regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1872908 Title: bcmwl kernel module does not build with kernel version 5.6 or 5.8 Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Focal: Fix Released Bug description: After kernel update to 5.6.0-1007-oem wifi stopped working. Turned out dkms is unable to build the bcmwl module. The make log shows: ubuntu@ubuntu-inspiron-5482:~$ cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64) ons 15 apr 2020 09:19:05 CEST make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem' CFG80211 API is prefered for this kernel version Using CFG80211 API AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_reg_map’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ^~~ | ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: warning: returning ‘int’ from a function with return type ‘void *’ makes pointer from integer without a cast [-Wint-conversion] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ~^~~~ In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_set_auth_type’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5: warning: this statement may fall through [-Wimplicit-fallthrough=] 52 | if (wl_dbg_level & WL_DBG_DBG) { \ | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3: note: in expansion of macro ‘WL_DBG’ 816 | WL_DBG(("network eap\n")); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2: note: here 817 | default: | ^~~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_attach’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { |^~~ |ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18: warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_pci_probe’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 780 | if ((val & 0xff00) != 0) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 782 | bar1_size = pci_resource_len(pdev, 2); | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2), | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_reg_proc_entry’:
[Kernel-packages] [Bug 1872908] Re: bcmwl kernel module does not build with kernel version 5.6 or 5.8
This bug was fixed in the package bcmwl - 6.30.223.271+bdcom- 0ubuntu7~20.04.1 --- bcmwl (6.30.223.271+bdcom-0ubuntu7~20.04.1) focal; urgency=medium * debian/dkms.conf.in, debian/patches/0028-add-support-for-linux-5.6.patch (LP: #1872908): - Add support for Linux 5.6. -- Alberto Milone Mon, 04 May 2020 13:23:19 +0200 ** Changed in: bcmwl (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1872908 Title: bcmwl kernel module does not build with kernel version 5.6 or 5.8 Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Focal: Fix Released Bug description: After kernel update to 5.6.0-1007-oem wifi stopped working. Turned out dkms is unable to build the bcmwl module. The make log shows: ubuntu@ubuntu-inspiron-5482:~$ cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64) ons 15 apr 2020 09:19:05 CEST make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem' CFG80211 API is prefered for this kernel version Using CFG80211 API AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_reg_map’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ^~~ | ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: warning: returning ‘int’ from a function with return type ‘void *’ makes pointer from integer without a cast [-Wint-conversion] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ~^~~~ In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_set_auth_type’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5: warning: this statement may fall through [-Wimplicit-fallthrough=] 52 | if (wl_dbg_level & WL_DBG_DBG) { \ | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3: note: in expansion of macro ‘WL_DBG’ 816 | WL_DBG(("network eap\n")); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2: note: here 817 | default: | ^~~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_attach’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { |^~~ |ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18: warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_pci_probe’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 780 | if ((val & 0xff00) != 0) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 782 | bar1_size = pci_resource_len(pdev, 2); | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2), | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_reg_proc_entry’:
[Kernel-packages] [Bug 1887294] Re: [nvidia] Display freeze and kernel crash on GeForce GTX 1060 6GB
It's been 21 days without a crash. I think this problem is solved for me. I may have updated system files since the last reboot, so I try to put the version of the running code: $ cat /sys/module/nvidia/version 450.102.04 $ uname -a Linux blackhole 5.4.0-60-generic #67-Ubuntu SMP Tue Jan 5 18:31:36 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thanks to the people who have fixed it! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1887294 Title: [nvidia] Display freeze and kernel crash on GeForce GTX 1060 6GB Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: The display is completely frozen, and no signal is output to the monitors. There is also no signal when switching to a console (Ctr- Alt-F1). I have normal access via SSH. It happens about once in 14 days. Only happens when turning the display off or on (about once in 15 screen power cycles). nvidia-smi still works (via SSH; without any options) DISPLAY=:1 xset dpms force on hangs indefinitely. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Jul 12 17:47:58 2020 DistUpgraded: 2020-05-17 13:48:43,365 DEBUG entry '# deb [arch=amd64] https://repo.skype.com/deb stable main # disabled on upgrade to focal' was disabled (unknown mirror) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) v4l2loopback, 0.12.3, 5.4.0-39-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85ae] InstallationDate: Installed on 2016-07-27 (1445 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-17 (56 days ago) dmi.bios.date: 04/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8C WS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd04/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8CWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jul 7 22:02:38 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs:
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Aksahat: The kernel 5.8.0-42 is not yet in proposed, on Ubuntu 20.04. For now only on Ubuntu 20.10. The alternative, until it is included in Ubuntu 20.04.2 is this: sudo apt install linux-oem-20.04 This way, the OEM 5.6 kernel is installed, which is fix. Then you have to uninstall the hwe kernel: sudo apt remove --purge --install-recommends linux-generic-hwe-20.04 To list installed kernels: sudo dpkg --list | grep linux-image and: sudo dpkg --list | grep linux-headers Clear all 5.8 kernels with: sudo apt-get --purge remove linux-xxx That or wait for it to be fixed in ubuntu 20.04 with kernel 5.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1894778 Title: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [SRU Justification] [Impact] When booting with a certain platforms with boot disk attached to SATA bus behind Intel VMD controller, disk probing may fail with following error messages left in dmesg: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [Fix] Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X vectors") currently in vanilla kernel tree for v5.11. [Test Case] Check dmesg/lsblk for disk probe. For pci MSI address, check lspci output: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee0 Data: When it fails, the address is fee0. And with a patched kernel: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee01000 Data: [Where problems could occur] An unpatched kernel will not be able to probe SATA controllers moved behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks attached on it completely unusable. With this change, kernel would then be able to probe them but may also suffer from issues that only occur under such configuration. However, the worst case is to move away sata disks from VMD bus as they are currently without this fix, so the risk here should be justified. == Previous SRU == [SRU Justification] [Impact] When booting with a certain platforms with boot disk attached to SATA bus behind Intel VMD controller, disk probing may fail with following error messages left in dmesg: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [Fix] Proposed kernel patch https://patchwork.kernel.org/patch/11758345/ [Test Case] Check dmesg/lsblk for disk probe. For pci MSI address, check lspci output: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee0 Data: When it fails, the address is fee0. And with a patched kernel: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee01000 Data: [Regression Potential] Low. For previous NVMe based platforms, this patch brings no effective change for NVMe devices because they will still stay in fast-interrupt list. == Original Bug Description == When booting with root filesystem on sata disks under Intel VMD mode, following errors printed in dmesg and no disk is found, nor booting into it: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 16.659284] ata1.00: qc timeout (cmd 0xec) [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 48.147294] ata1.00: qc timeout (cmd 0xec) [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) $ lspci ... 1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
** No longer affects: coreutils (Ubuntu Groovy) ** No longer affects: coreutils (Ubuntu Focal) ** No longer affects: coreutils (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/1894329 Title: ZFS revert from grub menu not working. Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Bug description: [Impact] * Users can’t revert to previous snapshots when enabling the hw enablement stack kernel on focal or using any more recent version. * The option is available on grub and will let you with a broken system, partially cloned. [Test Case] * Boot on a system, using ZFS and ZSys. * In grub, select "History" entry * Select one of the "Revert" option: the system should boot after being reverted with an older version. [Where problems could occur] * The code is in the initramfs, where the generated id suffix for all our ZFS datasets was empty due to new coreutils/kernels. * We replace dd with another way (more robust and simple) for generating this ID. - @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the dataset without a proper suffix. Replacing the function with: uid() { grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 } fixes the problem. Ubuntu version is: Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 zfs-initramfs version is: 0.8.4-1ubuntu11 With regards, Usarin Heininga ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 4 20:23:44 2020 InstallationDate: Installed on 2020-09-02 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+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 1912935] Re: battery drain while notebook off / shutdown
@kaihengfeng I tested the mainline kernel 5.11, version rc5 has the same battery drain. How can I test the patch, or is it integrated in rc5? -- 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/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1914052] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 I have this error to install the wi-fi drive. is blocking me. help me please -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1914052 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-41-generic Date: Mon Feb 1 10:09:25 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-02-01 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1914052/+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 1872908] Re: bcmwl kernel module does not build with kernel version 5.6 or 5.8
Installing the new package: -- Подготовка за разпакетиране на bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7~20.04.1_amd64.deb ... Removing all DKMS Modules Done. Разпакетиране на bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7~20.04.1) над (6.30.223.271+bdcom-0ubuntu7) ... Инсталиране на bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7~20.04.1) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-41-generic Building for architecture x86_64 Building initial module for 5.8.0-41-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-41-generic/updates/dkms/ depmod... DKMS: install completed. update-initramfs: deferring update (trigger activated) Обработка на тригерите за initramfs-tools (0.136ubuntu6.3) ... update-initramfs: Generating /boot/initrd.img-5.8.0-41-generic -- Everything works. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1872908 Title: bcmwl kernel module does not build with kernel version 5.6 or 5.8 Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Focal: Fix Committed Bug description: After kernel update to 5.6.0-1007-oem wifi stopped working. Turned out dkms is unable to build the bcmwl module. The make log shows: ubuntu@ubuntu-inspiron-5482:~$ cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64) ons 15 apr 2020 09:19:05 CEST make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem' CFG80211 API is prefered for this kernel version Using CFG80211 API AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_reg_map’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ^~~ | ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: warning: returning ‘int’ from a function with return type ‘void *’ makes pointer from integer without a cast [-Wint-conversion] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ~^~~~ In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_set_auth_type’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5: warning: this statement may fall through [-Wimplicit-fallthrough=] 52 | if (wl_dbg_level & WL_DBG_DBG) { \ | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3: note: in expansion of macro ‘WL_DBG’ 816 | WL_DBG(("network eap\n")); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2: note: here 817 | default: | ^~~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_attach’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { |^~~ |ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18: warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_pci_probe’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 780 | if ((val
[Kernel-packages] [Bug 1913950] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1827100 *** https://bugs.launchpad.net/bugs/1827100 ** This bug has been marked a duplicate of bug 1827100 bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux 5.1.0-1.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1913950 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: guanhe@guanhe-Lenovo-G510:~/Downloads$ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.3_amd64.deb cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-41-generic (x86_64) 2021年 01月 31日 星期日 23:09:12 CST make: Entering directory '/usr/src/linux-headers-5.8.0-41-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_dev_ioctl’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9: error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? [-Werror=implicit-function-declaration] 462 | set_fs(get_ds()); | ^~ | get_fs /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9: error: incompatible type for argument 1 of ‘set_fs’ 462 | set_fs(get_ds()); ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-41-generic Date: Sun Jan 31 23:09:15 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.3:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9: error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-12-14 (48 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.3 Python3Details: /usr/local/bin/python3.9, Python 3.9.1, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1913950/+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 1872908] Re: bcmwl kernel module does not build with kernel version 5.6 or 5.8
** Summary changed: - bcmwl kernel module does not build with 5.6.0 kernel or later + bcmwl kernel module does not build with kernel version 5.6 or 5.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1872908 Title: bcmwl kernel module does not build with kernel version 5.6 or 5.8 Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Focal: Fix Committed Bug description: After kernel update to 5.6.0-1007-oem wifi stopped working. Turned out dkms is unable to build the bcmwl module. The make log shows: ubuntu@ubuntu-inspiron-5482:~$ cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64) ons 15 apr 2020 09:19:05 CEST make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem' CFG80211 API is prefered for this kernel version Using CFG80211 API AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_reg_map’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ^~~ | ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: warning: returning ‘int’ from a function with return type ‘void *’ makes pointer from integer without a cast [-Wint-conversion] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ~^~~~ In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_set_auth_type’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5: warning: this statement may fall through [-Wimplicit-fallthrough=] 52 | if (wl_dbg_level & WL_DBG_DBG) { \ | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3: note: in expansion of macro ‘WL_DBG’ 816 | WL_DBG(("network eap\n")); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2: note: here 817 | default: | ^~~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_attach’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { |^~~ |ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18: warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_pci_probe’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 780 | if ((val & 0xff00) != 0) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 782 | bar1_size = pci_resource_len(pdev, 2); | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2), | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_reg_proc_entry’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58: error: passing argument 4 of ‘proc_create_data’ from incompatible pointer type [-Werror=incompatible-pointer-types] 3376 | if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, _fops, wl)) == NULL) { |
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Hi richmbx, I am currently working this, and currently doing testing to make sure it has integrated with Focal correctly. I expect it to begin the SRU process in the next day or so. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded Status in cloud-images: Confirmed Status in grub2 package in Ubuntu: Won't Fix Status in linux-azure package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Triaged Status in grub2 source package in Focal: Confirmed Status in linux-azure source package in Focal: Invalid Status in livecd-rootfs source package in Focal: Confirmed Bug description: A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu 20.04 by “do-release-upgrade –d”. Then the latest Ubuntu v5.6 kernel was installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a reboot was performed, a panic with the v5.6 kernel occured because the rootfs can not be found. It turns out by default, initramfs does not get loaded: /boot/grub/grub.cfg: menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-3d2737e8- b95a-42bf-bac1-bb6fb4cda87f' { … if [ "${initrdfail}" = 1 ]; then linux /boot/vmlinuz-5.6.0-050600-generic root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled unknown_nmi_panic initrd/boot/initrd.img-5.6.0-050600-generic else linux /boot/vmlinuz-5.6.0-050600-generic root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled unknown_nmi_panic panic=-1 #Dexuan: here the initrd line is missing! fi initrdfail } As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit the “fail to mount rootfs” panic and the kernel will automatically reboot…. Also, the “initrdfail” here marks initrdfail=1, so when the kernel boots for the 2nd time, the kernel should successfully boot up. Next, when the kernel boots for the 3rd time, it panics again since the userspace program resets initrdfail to 0, and next time when the kernel boots, it can boot up successfully -- this “panic/success/panic/success” pattern repeats forever… The linux-azure kernels are not affected since they have the vmbus driver and storage drivers built-in (i.e. “=y”): /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m The v5.6 kernel uses =m rather than =y, so is affected here. It looks the setting may be intentional, but we should not assume a customer kernel must have the necessary vmbus/storage drivers built-in. This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 19.04 as well?) on Azure. We installed a Ubuntu 20.04 VM from the .iso file from http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub issue. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1870189/+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 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Just as a follow-up on this topic. now running Linux ZBook15G6 5.8.0-41-generic #46-Ubuntu SMP Mon Jan 18 16:48:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and things are a bit better. I have everything working fine (mic + sound + thunderbolt dock), but I have to boot the laptop unplugged to the AC adapter. When doing so, everything works fine. If I boot the laptop with the AC adaptor hooked (and of course power supply), then mic in ok, but I then have no sound. This seems strange to me, but this is the actually observed / repeatable behaviour. -- 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/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+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 1878045] Re: doing dist-upgrade got error related do Broadcom
** Changed in: bcmwl (Ubuntu Focal) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Focal: Invalid Status in bcmwl source package in Groovy: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+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 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Aksahat: Here are the instructions to activate proposed: https://wiki.ubuntu.com/Testing/EnableProposed Either way, the new kernel should be on regular Ubuntu 20.10 updates, and also 20.04 with HWE kernel, in the next few days or weeks. I still hope that it reaches the launch of Ubuntu 20.04.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1894778 Title: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [SRU Justification] [Impact] When booting with a certain platforms with boot disk attached to SATA bus behind Intel VMD controller, disk probing may fail with following error messages left in dmesg: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [Fix] Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X vectors") currently in vanilla kernel tree for v5.11. [Test Case] Check dmesg/lsblk for disk probe. For pci MSI address, check lspci output: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee0 Data: When it fails, the address is fee0. And with a patched kernel: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee01000 Data: [Where problems could occur] An unpatched kernel will not be able to probe SATA controllers moved behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks attached on it completely unusable. With this change, kernel would then be able to probe them but may also suffer from issues that only occur under such configuration. However, the worst case is to move away sata disks from VMD bus as they are currently without this fix, so the risk here should be justified. == Previous SRU == [SRU Justification] [Impact] When booting with a certain platforms with boot disk attached to SATA bus behind Intel VMD controller, disk probing may fail with following error messages left in dmesg: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [Fix] Proposed kernel patch https://patchwork.kernel.org/patch/11758345/ [Test Case] Check dmesg/lsblk for disk probe. For pci MSI address, check lspci output: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee0 Data: When it fails, the address is fee0. And with a patched kernel: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee01000 Data: [Regression Potential] Low. For previous NVMe based platforms, this patch brings no effective change for NVMe devices because they will still stay in fast-interrupt list. == Original Bug Description == When booting with root filesystem on sata disks under Intel VMD mode, following errors printed in dmesg and no disk is found, nor booting into it: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 16.659284] ata1.00: qc timeout (cmd 0xec) [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 48.147294] ata1.00: qc timeout (cmd 0xec) [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) $ lspci ... 1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1894778/+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 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel or later
Hello Vincent, or anyone else affected, Accepted bcmwl into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.271 +bdcom-0ubuntu7~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: bcmwl (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1872908 Title: bcmwl kernel module does not build with 5.6.0 kernel or later Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Focal: Fix Committed Bug description: After kernel update to 5.6.0-1007-oem wifi stopped working. Turned out dkms is unable to build the bcmwl module. The make log shows: ubuntu@ubuntu-inspiron-5482:~$ cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64) ons 15 apr 2020 09:19:05 CEST make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem' CFG80211 API is prefered for this kernel version Using CFG80211 API AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_reg_map’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ^~~ | ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: warning: returning ‘int’ from a function with return type ‘void *’ makes pointer from integer without a cast [-Wint-conversion] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ~^~~~ In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_set_auth_type’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5: warning: this statement may fall through [-Wimplicit-fallthrough=] 52 | if (wl_dbg_level & WL_DBG_DBG) { \ | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3: note: in expansion of macro ‘WL_DBG’ 816 | WL_DBG(("network eap\n")); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2: note: here 817 | default: | ^~~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_attach’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { |^~~ |ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18: warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { |
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
** Changed in: bcmwl (Ubuntu Focal) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Patch added: "debdiff for Focal" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+attachment/5458878/+files/bcmwl_6.30.223.271+bdcom-0ubuntu7~20.04.1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Focal: In Progress Status in bcmwl source package in Groovy: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+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 1878045] Re: doing dist-upgrade got error related do Broadcom
** Also affects: bcmwl (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: bcmwl (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: bcmwl (Ubuntu Groovy) Status: New => Fix Released ** Changed in: bcmwl (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Focal: In Progress Status in bcmwl source package in Groovy: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+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 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel or later
** Changed in: bcmwl (Ubuntu Focal) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1872908 Title: bcmwl kernel module does not build with 5.6.0 kernel or later Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Focal: Triaged Bug description: After kernel update to 5.6.0-1007-oem wifi stopped working. Turned out dkms is unable to build the bcmwl module. The make log shows: ubuntu@ubuntu-inspiron-5482:~$ cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64) ons 15 apr 2020 09:19:05 CEST make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem' CFG80211 API is prefered for this kernel version Using CFG80211 API AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_reg_map’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ^~~ | ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: warning: returning ‘int’ from a function with return type ‘void *’ makes pointer from integer without a cast [-Wint-conversion] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ~^~~~ In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_set_auth_type’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5: warning: this statement may fall through [-Wimplicit-fallthrough=] 52 | if (wl_dbg_level & WL_DBG_DBG) { \ | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3: note: in expansion of macro ‘WL_DBG’ 816 | WL_DBG(("network eap\n")); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2: note: here 817 | default: | ^~~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_attach’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { |^~~ |ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18: warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_pci_probe’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 780 | if ((val & 0xff00) != 0) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 782 | bar1_size = pci_resource_len(pdev, 2); | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2), | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_reg_proc_entry’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58: error: passing argument 4 of ‘proc_create_data’ from incompatible pointer type [-Werror=incompatible-pointer-types] 3376 | if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, _fops, wl)) == NULL) { | ^~~~ |
[Kernel-packages] [Bug 1902355] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1902355 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: on a fresh install which happened with no wifi connection so no updates during install once installed I defined a good wifi connection then ran apt-get update && apt-get upgrade I get this error on next reboot ProblemType: Package DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-26-generic Date: Sat Oct 31 07:54:08 2020 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu7:./include/linux/log2.h:24:1: error: stray ‘\1’ in program InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageVersion: 6.30.223.271+bdcom-0ubuntu7 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: linux-image-5.8.0-26-generic linux-base RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1902355/+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 1910607] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: el subproceso instalado paquete bcmwl-kernel-source script post-installation devo
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1910607 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: el subproceso instalado paquete bcmwl-kernel-source script post-installation devolvió el código de salida de error 10 Status in bcmwl package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: linux-image-5.8.0-34-generic:amd64: Purge linux-modules-5.8.0-34-generic:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 7 17:25:31 2021 ErrorMessage: el subproceso instalado paquete bcmwl-kernel-source script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2020-11-20 (48 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: el subproceso instalado paquete bcmwl-kernel-source script post-installation devolvió el código de salida de error 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910607/+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 1905211] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed focal fossa in kernel v5.9
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1905211 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed focal fossa in kernel v5.9 Status in bcmwl package in Ubuntu: New Bug description: Impact The DKMS package won't work with new kernel v5.9 on focal fossa. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 Uname: Linux 5.9.0-050900-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.12 AptOrdering: bcmwl-kernel-source:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 17:23:01 2020 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-11-16 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1905211/+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 1914052] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1914052 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-41-generic Date: Mon Feb 1 10:09:25 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-02-01 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1914052/+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 1914102] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: artful -- 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/1914102 Title: 3 newest kernel do not boot (black screen) Status in linux package in Ubuntu: Confirmed Bug description: Hello, I'm running Kbuntu 18.04.5 LTS and currently have the following kernels installed which all just show a black screen when booting (occasionally a single _ is displayed): linux-image-4.15.0-132-generic linux-image-4.15.0-130-generic linux-image-4.15.0-129-generic I had the issue first with the newer two kernels and the 129 did work. I uninstalled some older kernels to free space on /boot and reinstalled the newest kernel. I also installed some other, hopefully unrelated, packages around php + mariadb. Now 129 is also not working any more (same behavior). The recovery modes do work. linux-image-4.13.0-36-generic is working. I do have a full disk encryption active. I also wrote here and got the advice to report a bug: https://answers.launchpad.net/ubuntu/+question/695293 Thank you in advance for any help! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-132-generic 4.15.0-132.136 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sdennler 2695 F pulseaudio /dev/snd/controlC0: sdennler 2695 F pulseaudio CurrentDesktop: KDE Date: Mon Feb 1 18:35:20 2021 HibernationDevice: RESUME=UUID=8e2585bb-f721-4eee-9030-5ef469cfdef0 InstallationDate: Installed on 2018-02-09 (1087 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2) MachineType: HP HP EliteBook 840 G3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/vgkubuntu-root ro kopt=root=/dev/mapper/vgkubuntu-root RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (887 days ago) dmi.bios.date: 03/22/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.05 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.61 dmi.chassis.asset.tag: 5CG6231YK9 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.05:bd03/22/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.61:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914102/+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 1909369] Re: linux-headers-5.10.3-051003-generic is not supported
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1909369 Title: linux-headers-5.10.3-051003-generic is not supported Status in bcmwl package in Ubuntu: Confirmed Bug description: > $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 > $ sudo apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installé : (aucun) Candidat : 6.30.223.271+bdcom-0ubuntu5 Table de version : 6.30.223.271+bdcom-0ubuntu5 500 500 http://fr.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages Hello, I tried to install a wireless network adapter broadcom BCM4360, i nned to install the package bcmwl-kernel-source but when i try to install it i have the following error : "ERROR (dkms apport): kernel package linux-headers-5.10.3-051003-generic is not supported Error! Bad return status for module build on kernel: 5.10.3-051003-generic (x86_64) " ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source (not installed) Uname: Linux 5.10.3-051003-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 26 21:16:07 2020 InstallationDate: Installed on 2020-01-05 (356 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1909369/+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 1914102] [NEW] 3 newest kernel do not boot (black screen)
Public bug reported: Hello, I'm running Kbuntu 18.04.5 LTS and currently have the following kernels installed which all just show a black screen when booting (occasionally a single _ is displayed): linux-image-4.15.0-132-generic linux-image-4.15.0-130-generic linux-image-4.15.0-129-generic I had the issue first with the newer two kernels and the 129 did work. I uninstalled some older kernels to free space on /boot and reinstalled the newest kernel. I also installed some other, hopefully unrelated, packages around php + mariadb. Now 129 is also not working any more (same behavior). The recovery modes do work. linux-image-4.13.0-36-generic is working. I do have a full disk encryption active. I also wrote here and got the advice to report a bug: https://answers.launchpad.net/ubuntu/+question/695293 Thank you in advance for any help! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-132-generic 4.15.0-132.136 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sdennler 2695 F pulseaudio /dev/snd/controlC0: sdennler 2695 F pulseaudio CurrentDesktop: KDE Date: Mon Feb 1 18:35:20 2021 HibernationDevice: RESUME=UUID=8e2585bb-f721-4eee-9030-5ef469cfdef0 InstallationDate: Installed on 2018-02-09 (1087 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2) MachineType: HP HP EliteBook 840 G3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/vgkubuntu-root ro kopt=root=/dev/mapper/vgkubuntu-root RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (887 days ago) dmi.bios.date: 03/22/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.05 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.61 dmi.chassis.asset.tag: 5CG6231YK9 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.05:bd03/22/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.61:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G3 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-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/1914102 Title: 3 newest kernel do not boot (black screen) Status in linux package in Ubuntu: New Bug description: Hello, I'm running Kbuntu 18.04.5 LTS and currently have the following kernels installed which all just show a black screen when booting (occasionally a single _ is displayed): linux-image-4.15.0-132-generic linux-image-4.15.0-130-generic linux-image-4.15.0-129-generic I had the issue first with the newer two kernels and the 129 did work. I uninstalled some older kernels to free space on /boot and reinstalled the newest kernel. I also installed some other, hopefully unrelated, packages around php + mariadb. Now 129 is also not working any more (same behavior). The recovery modes do work. linux-image-4.13.0-36-generic is working. I do have a full disk encryption active. I also wrote here and got the advice to report a bug: https://answers.launchpad.net/ubuntu/+question/695293 Thank you in advance for any help! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-132-generic 4.15.0-132.136 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sdennler 2695 F pulseaudio /dev/snd/controlC0: sdennler 2695 F pulseaudio CurrentDesktop: KDE Date: Mon Feb 1 18:35:20 2021 HibernationDevice: RESUME=UUID=8e2585bb-f721-4eee-9030-5ef469cfdef0 InstallationDate: Installed on 2018-02-09 (1087 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2) MachineType: HP HP EliteBook 840 G3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/vgkubuntu-root ro kopt=root=/dev/mapper/vgkubuntu-root RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (887 days ago) dmi.bios.date: 03/22/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.05 dmi.board.name: 8079
[Kernel-packages] [Bug 1913890] Missing required logs.
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 1913890 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 ** Tags added: groovy -- 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/1913890 Title: My device is ASUS ViviBook x507. I installed Ubuntu 20.04 LTS. I have a fingerprint sensor that worked with windows 10. Ubuntu can't even recognise it . It wont even show up in lsusb, lspci or lshw. Status in linux package in Ubuntu: Incomplete Bug description: (base) akash@Akash-Asus:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (base) akash@Akash-Asus:~$ ^C (base) akash@Akash-Asus:~$ fprintd-enroll list_devices failed: No devices available (base) akash@Akash-Asus:~$ ^C (base) akash@Akash-Asus:~$ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) 00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO UART Controller #0 (rev 21) 00:1e.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO SPI Controller #0 (rev 21) 00:1e.6 SD Host controller: Intel Corporation Sunrise Point-LP Secure Digital IO Controller (rev 21) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce MX130] (rev a2) 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) (base) akash@Akash-Asus:~$ lshw WARNING: you should run this program as super-user. akash-asus description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 8GiB *-cpu product: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 1132MHz capacity: 3400MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d cpufreq *-pci description: Host bridge product: Xeon E3-1200 v6/7th Gen
[Kernel-packages] [Bug 1910920] Re: no soundcard present with linux-image-5.8.0-37-generic
Same issue exists in 5.8.0-41-generic. Same fix, install linux-modules- extra-5.8.0-41-generic. I am using KDE Neon 20.04. During earlier attempts to debug the issue I removed the .config/pulse directory and permitted it to be rebuilt. Combined with the additional library and a reboot, it remade the config for the sound devices. -- 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/1910920 Title: no soundcard present with linux-image-5.8.0-37-generic Status in linux package in Ubuntu: Confirmed Bug description: With linux-image-5.8.0-34-generic, all on-board soundcards work flawlessly. After update of kernel to linux-image-5.8.0-37-generic durign this week no soundcards are detected. I am happy to provide more information. But I will not sent automatic apport reports because it includes private local data. !!DMI Information !!--- Manufacturer: LENOVO Product Name: 20BUS23M00 Product Version: ThinkPad T450 Firmware Version: JBET54WW (1.19 ) Board Vendor: LENOVO Board Name:20BUS23M00 !!Kernel Information !!-- Kernel release:5.8.0-34-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.8.0-34-generic Library version:1.2.3.2 Utilities version: 1.2.3 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xe123 irq 51 1 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe1234000 irq 52 !!PCI Soundcards installed in the system !!-- 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09) Subsystem: Lenovo Broadwell-U Audio Controller [17aa:5034] 00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03) Subsystem: Lenovo Wildcat Point-LP High Definition Audio Controller [17aa:5034] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920/+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 1913890] Re: My device is ASUS ViviBook x507. I installed Ubuntu 20.04 LTS. I have a fingerprint sensor that worked with windows 10. Ubuntu can't even recognise it . It wont eve
** Package changed: ubuntu => linux (Ubuntu) -- 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/1913890 Title: My device is ASUS ViviBook x507. I installed Ubuntu 20.04 LTS. I have a fingerprint sensor that worked with windows 10. Ubuntu can't even recognise it . It wont even show up in lsusb, lspci or lshw. Status in linux package in Ubuntu: New Bug description: (base) akash@Akash-Asus:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (base) akash@Akash-Asus:~$ ^C (base) akash@Akash-Asus:~$ fprintd-enroll list_devices failed: No devices available (base) akash@Akash-Asus:~$ ^C (base) akash@Akash-Asus:~$ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) 00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO UART Controller #0 (rev 21) 00:1e.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO SPI Controller #0 (rev 21) 00:1e.6 SD Host controller: Intel Corporation Sunrise Point-LP Secure Digital IO Controller (rev 21) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce MX130] (rev a2) 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) (base) akash@Akash-Asus:~$ lshw WARNING: you should run this program as super-user. akash-asus description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 8GiB *-cpu product: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 1132MHz capacity: 3400MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d cpufreq *-pci description: Host bridge product: Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 08 width: 32 bits clock: 33MHz configuration: driver=skl_uncore resources: irq:0 *-display description: VGA compatible controller product: UHD Graphics 620 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 07 width: 64 bits
[Kernel-packages] [Bug 1913890] [NEW] My device is ASUS ViviBook x507. I installed Ubuntu 20.04 LTS. I have a fingerprint sensor that worked with windows 10. Ubuntu can't even recognise it . It wont e
You have been subscribed to a public bug: (base) akash@Akash-Asus:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (base) akash@Akash-Asus:~$ ^C (base) akash@Akash-Asus:~$ fprintd-enroll list_devices failed: No devices available (base) akash@Akash-Asus:~$ ^C (base) akash@Akash-Asus:~$ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) 00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO UART Controller #0 (rev 21) 00:1e.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO SPI Controller #0 (rev 21) 00:1e.6 SD Host controller: Intel Corporation Sunrise Point-LP Secure Digital IO Controller (rev 21) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce MX130] (rev a2) 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) (base) akash@Akash-Asus:~$ lshw WARNING: you should run this program as super-user. akash-asus description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 8GiB *-cpu product: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 1132MHz capacity: 3400MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d cpufreq *-pci description: Host bridge product: Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 08 width: 32 bits clock: 33MHz configuration: driver=skl_uncore resources: irq:0 *-display description: VGA compatible controller product: UHD Graphics 620 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 07 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:130 memory:ed00-edff memory:c000-cfff ioport:f000(size=64) memory:c-d *-generic:0 description: Signal processing controller product: Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem vendor: Intel Corporation physical id: 4 bus info: pci@:00:04.0 version: 08 width: 64
[Kernel-packages] [Bug 1900665] Re: Switch to the upstream dwc driver on arm64
** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => Won't Fix ** Description changed: We currently use the dwc_otg driver from raspberrypi on 5.4 and 5.8 armhf and arm64 kernels. That driver supports FIQ interrupt handling (presumable for better performance) but lacks the maintenance and bug fixing of the vanilla upstream dwc driver. Turns out that FIQ handling is disabled in the dwc_otg driver on arm64 so it makes little sense to use that driver on arm64. + + In fact, upstream raspberrypi recommends to use the dwc2 driver on + arm64. ** Summary changed: - Switch to the upstream dwc driver on arm64 + Use the upstream dwc2 driver on arm64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1900665 Title: Use the upstream dwc2 driver on arm64 Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: Won't Fix Status in linux-raspi source package in Groovy: Won't Fix Status in linux-raspi source package in Hirsute: New Bug description: We currently use the dwc_otg driver from raspberrypi on 5.4 and 5.8 armhf and arm64 kernels. That driver supports FIQ interrupt handling (presumable for better performance) but lacks the maintenance and bug fixing of the vanilla upstream dwc driver. Turns out that FIQ handling is disabled in the dwc_otg driver on arm64 so it makes little sense to use that driver on arm64. In fact, upstream raspberrypi recommends to use the dwc2 driver on arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1900665/+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 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series
The link of Nvidia SRU testing result is following, no regression was found. https://docs.google.com/spreadsheets/d/1-efzhthwiePkABHBgVGw8qBQwr8v0wznSEWcA52pjzs/edit#gid=1694297374 -- 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/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Introduce the new NVIDIA 460-server series and update the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460-server == * Initial release: - Added support for the following GPUs: NVIDIA A40 NVIDIA RTX A6000 - Added support for CUDA 11.2. == 460 == * New upstream release: - Added support for the following GPUs: GeForce RTX 3080 Laptop GPU GeForce RTX 3070 Laptop GPU GeForce RTX 3060 Laptop GPU GeForce GT 1010 - Updated the NVIDIA driver to restore functionality of some features, including runtime power management, hotplugging audio-capable display devices, and S0ix-based system suspend, with recent kernels such as Linux 5.10. - Fixed a bug that caused bindless texture samplers to be incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS limit. - Fixed a bug that could cause the GPU to hang when attempting to perform link training on an HDMI 2.1 Fixed Rate Link (FRL) display, while the display is powered off. - Fixed a bug that could intermittently cause NvFBC applications to fail with the error message "Unable to send exported fds". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+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 1913859] Re: RT3290 Bluetooth not finding any device
** This bug is no longer a duplicate of bug 1914007 RT3290 Bluetooth not finding any device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED" operation="connect"
[Kernel-packages] [Bug 1899508] Re: alsa/hda/realtek - The front Mic on a HP machine doesn't work
** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1899508 Title: alsa/hda/realtek - The front Mic on a HP machine doesn't work Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Won't Fix Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: This fix is only for oem-5.6 kernel, other kernels will merge this patch with stable update. Our oem project needs this patch to be merged ASAP. [Impact] When using a HP machine, after plugging the headset at front jack, there is no any input device shows. [Fix] The codec of the HP ZCentrol is alc671 and it needs to override the pin configuration to enable the headset mic. This patch is going to be merged by upstream, now backport it to oem-5.6 kernel. [Test Case] Boot the system, plug a headset and check the gnome-control-center, the Mic is active in the UI, and record the sound, it could record the sound. [Regression Potential] Low, this patch is to add a platform specific quirk to override pin configuration and already tested in this HP machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1899508/+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 1907298] Missing required logs.
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 1907298 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 -- 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/1907298 Title: glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8 Status in GLibC: Unknown Status in glibc package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/ppc64el/g/glibc/20201208_192946_04f11@/log.gz -- FAIL: misc/tst-sigcontext-get_pc original exit status 1 info: address in signal handler: 0x737faa11db44 info: call stack entry 0: 0x737faa311f58 info: call stack entry 1: 0x737faa3404c4 info: call stack entry 2: 0x0 info: call stack entry 3: 0x737faa312144 info: call stack entry 4: 0x737faa312870 info: call stack entry 5: 0x737faa313264 info: call stack entry 6: 0x737faa311c40 info: call stack entry 7: 0x737faa0f9e5c info: call stack entry 8: 0x737faa0fa040 error: ../sysdeps/unix/sysv/linux/tst-sigcontext-get_pc.c:60: not true: found error: 1 test failures -- To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1907298/+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 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Hello, I recently install in my new laptop with `1TB HDD + 256GB SSD`. I am facing same problem.I will like to fix this using this patch or some another method. Please help me out in applying this patch and checking if this will work for me. P.s. I am working on ubuntu 20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1894778 Title: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [SRU Justification] [Impact] When booting with a certain platforms with boot disk attached to SATA bus behind Intel VMD controller, disk probing may fail with following error messages left in dmesg: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [Fix] Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X vectors") currently in vanilla kernel tree for v5.11. [Test Case] Check dmesg/lsblk for disk probe. For pci MSI address, check lspci output: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee0 Data: When it fails, the address is fee0. And with a patched kernel: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee01000 Data: [Where problems could occur] An unpatched kernel will not be able to probe SATA controllers moved behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks attached on it completely unusable. With this change, kernel would then be able to probe them but may also suffer from issues that only occur under such configuration. However, the worst case is to move away sata disks from VMD bus as they are currently without this fix, so the risk here should be justified. == Previous SRU == [SRU Justification] [Impact] When booting with a certain platforms with boot disk attached to SATA bus behind Intel VMD controller, disk probing may fail with following error messages left in dmesg: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [Fix] Proposed kernel patch https://patchwork.kernel.org/patch/11758345/ [Test Case] Check dmesg/lsblk for disk probe. For pci MSI address, check lspci output: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee0 Data: When it fails, the address is fee0. And with a patched kernel: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee01000 Data: [Regression Potential] Low. For previous NVMe based platforms, this patch brings no effective change for NVMe devices because they will still stay in fast-interrupt list. == Original Bug Description == When booting with root filesystem on sata disks under Intel VMD mode, following errors printed in dmesg and no disk is found, nor booting into it: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 16.659284] ata1.00: qc timeout (cmd 0xec) [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 48.147294] ata1.00: qc timeout (cmd 0xec) [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) $ lspci ... 1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1894778/+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 1907298] Re: glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8
It seems there may be a kernel-side fix: https://lists.ozlabs.org/pipermail/linuxppc-dev/2021-January/223199.html I've committed XFAIL-ing the test for now, to be landed in Hirsute this/next week. ** Changed in: glibc (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1907298 Title: glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8 Status in GLibC: Unknown Status in glibc package in Ubuntu: Fix Committed Status in linux package in Ubuntu: New Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/ppc64el/g/glibc/20201208_192946_04f11@/log.gz -- FAIL: misc/tst-sigcontext-get_pc original exit status 1 info: address in signal handler: 0x737faa11db44 info: call stack entry 0: 0x737faa311f58 info: call stack entry 1: 0x737faa3404c4 info: call stack entry 2: 0x0 info: call stack entry 3: 0x737faa312144 info: call stack entry 4: 0x737faa312870 info: call stack entry 5: 0x737faa313264 info: call stack entry 6: 0x737faa311c40 info: call stack entry 7: 0x737faa0f9e5c info: call stack entry 8: 0x737faa0fa040 error: ../sysdeps/unix/sysv/linux/tst-sigcontext-get_pc.c:60: not true: found error: 1 test failures -- To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1907298/+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 1895132] Re: s390x broken with unknown syscall number on kernels < 5.8
I facing a whole load of odd issues in recent Hirsute LXD containers on s390x. Only s390x, only Hirsute - The guests didn't complete systemd initialization, some processes hang around, journal didn't start ... ddstreet was so kind to recognize this on IRC and gave me a hint to this bug. I was fomerly trying all kind of LXD versions, all behaved the same in regard to this issue. Since it was mentioned to be introduced in 5.4.0-43.47 I was downgrading the kernel from 5.4.0-65 to 5.4.0-26. And e voila - my world was colorful and happy again. So year, I seem to be affected by this and I must say it is a pretty heavy hitting as well as hard to debug issue. +1 for a fast resolution ... -- 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/1895132 Title: s390x broken with unknown syscall number on kernels < 5.8 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: On kernels prior to 5.8 when a task is in traced state (due to audit, ptrace, or seccomp) s390x and a syscall is issued that the kernel doesn't know about s390x will not return ENOSYS in r2 but instead will return the syscall number. This breaks userspace all over the place. The following program compiled on s390x will output 500 instead of -ENOSYS: root@test:~# cat test.c #define _GNU_SOURCE #include #include #include #include #include #include #include #include #include #include #include #include #include static inline int dummy_inline_asm(void) { register long r1 asm("r1") = 500; register long r2 asm("r2") = -1; register long r3 asm("r3") = -1; register long r4 asm("r4") = -1; register long r5 asm("r5") = -1; register long __res_r2 asm("r2"); asm volatile( "svc 0\n\t" : "=d"(__res_r2) : "d"(r1), "0"(r2), "d"(r3), "d"(r4), "d"(r5) : "memory"); return (int) __res_r2; } static inline int dummy_syscall(void) { return syscall(500, -1, -1, -1, -1); } int main(int argc, char *argv[]) { printf("Uhm: %d\n", dummy_inline_asm()); printf("Uhm: %d\n", dummy_syscall()); exit(EXIT_SUCCESS); } This breaks LXD on s390x currently completely as well as strace. Fix: Backport commit cd29fa798001075a554b978df3a64e6656c25794 Author: Sven Schnelle Date: Fri Mar 6 13:18:31 2020 +0100 s390/ptrace: return -ENOSYS when invalid syscall is supplied The current code returns the syscall number which an invalid syscall number is supplied and tracing is enabled. This makes the strace testsuite fail. Signed-off-by: Sven Schnelle Signed-off-by: Vasily Gorbik which got released with 5.8. The commit missed to Cc stable and although I've asked Sven to include it in stable I'm not sure when or if it will show up there. Regression Potential: Limited to s390x. Test Case: The reproducer given above needs to output -ENOSYS instead of 500. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1895132/+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 1913853] Re: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging
Thanks Kleber, I see now that this is what happens when you check a checkbox (Pre-released updates) and five years later don't even remember it. :-) -- 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/1913853 Title: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging Status in linux package in Ubuntu: Confirmed Bug description: Hi there, I've updated kernel on my Ubuntu 16.04 from 4.4.0-201-generic to 4.4.0.202-generic today and it broke my system. Basic commands, such as pidof, lsof, ps fax (ps -a works) hang indefinitely and not even root issued kill -KILL will terminate them. Only thing that helps is to kill the shell that started such commands. I had to reboot back to 4.4.0-201, however during shutdown various stop jobs hanged as well and after more than 25 minutes I had to go for hard reboot. My current—NOT BROKEN—kernel has signature (cat /proc/version_signature): Ubuntu 4.4.0-201.233-generic 4.4.247 I am attaching the lspci-vnvn.log, also created with the non-broken kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913853/+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 1914052] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1914052 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-41-generic Date: Mon Feb 1 10:09:25 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-02-01 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1914052/+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 1914052] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
Public bug reported: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-41-generic Date: Mon Feb 1 10:09:25 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-02-01 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1914052 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-41-generic Date: Mon Feb 1 10:09:25 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-02-01 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1914052/+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 1913442] Re: [Ubuntu 20.04] Problem leading IUCV service down (on s390x)
A kernel test build (binary-debs) from s390x can be found here: https://people.canonical.com/~fheimes/lp1913442/ Cross-arch. builds (for amd64, arm64, ppc64el and amd64) can be found in this PPA: https://launchpad.net/~fheimes/+archive/ubuntu/lp1913442 -- 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/1913442 Title: [Ubuntu 20.04] Problem leading IUCV service down (on s390x) Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Triaged Bug description: When I deployed a Ubuntu20.04 instance with kernel version of 5.4.0-58-generic under z/VM, I saw below messages from kernel and the iucvserv program malfunctioned. Hence it caused some devices like network device configuration failure and deployment failure. Dec 14 22:02:26 ub2004img iucvserv: Receive OPNCLD4 0.0.0.1 pwd sent from IUCV client. Dec 14 22:02:26 ub2004img iucvserv: /etc/iucv_authorized_userid exists, check authorization. Dec 14 22:02:26 ub2004img iucvserv: senduserid=OPNCLD4, authuserid=OPNCLD4, len=7 Dec 14 22:02:26 ub2004img iucvserv: Current version is 0.0.0.1, upgraded version is 0.0.0.1 Dec 14 22:02:26 ub2004img iucvserv: Will execute the linux command pwd 2>&1; echo iucvcmdrc=$? sent from IUCV client. Dec 14 22:02:26 ub2004img iucvserv: result length=14, send message length=14,#012 /#012iucvcmdrc=0 Dec 14 22:02:26 ub2004img kernel: [63084.184649] [ cut here ] Dec 14 22:02:26 ub2004img kernel: [63084.184654] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'dma-kmalloc-1k' (offset 0, size 20)! Dec 14 22:02:26 ub2004img kernel: [63084.184680] WARNING: CPU: 1 PID: 697 at mm/usercopy.c:75 usercopy_warn+0xa0/0xd0 Dec 14 22:02:26 ub2004img kernel: [63084.184681] Modules linked in: tcp_diag udp_diag raw_diag inet_diag unix_diag xt_CT iptable_raw ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_conntrack nf_conntrack nf_defr ag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter af_iucv nls_utf8 isofs dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmur vfio_ccw vfio_mdev mdev s390_trng vfio_iommu_type1 vfio sch_fq_codel drm drm _panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common dasd_fba_mod dasd_mod qeth_l2 qeth qdio ccwgroup Dec 14 22:02:26 ub2004img kernel: [63084.184718] CPU: 1 PID: 697 Comm: iucvserv Not tainted 5.4.0-58-generic #64-Ubuntu Dec 14 22:02:26 ub2004img kernel: [63084.184718] Hardware name: IBM 8561 LT1 400 (z/VM 7.1.0) Dec 14 22:02:26 ub2004img kernel: [63084.184719] Krnl PSW : 0704c0018000 b3c37a60 (usercopy_warn+0xa0/0xd0) Dec 14 22:02:26 ub2004img kernel: [63084.184721]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 Dec 14 22:02:26 ub2004img kernel: [63084.184722] Krnl GPRS: 0004 0006 0081 0007 Dec 14 22:02:26 ub2004img kernel: [63084.184722]0007 f2ecb400 b43fdc6a 03e00014 Dec 14 22:02:26 ub2004img kernel: [63084.184723] 0014 b43f01f0 Dec 14 22:02:26 ub2004img kernel: [63084.184723]aae13300 e9332a00 b3c37a5c 03e000987a10 Dec 14 22:02:26 ub2004img kernel: [63084.184728] Krnl Code: b3c37a50: c020003e310f larl%r2,b43fdc6e Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a56: c0e5ffedbe85 brasl %r14,b39ef760 Dec 14 22:02:26 ub2004img kernel: [63084.184728] #b3c37a5c: a7f40001 brc 15,b3c37a5e Dec 14 22:02:26 ub2004img kernel: [63084.184728] >b3c37a60: eb6ff0c4 lmg %r6,%r15,192(%r15) Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a66: 07fe bcr 15,%r14 Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a68: 47000700 bc 0,1792 Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a6c: c020003e30fa larl%r2,b43fdc60 Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a72: a7f4ffd4 brc 15,b3c37a1a Dec 14 22:02:26 ub2004img kernel: [63084.184735] Call Trace: Dec 14 22:02:26 ub2004img kernel: [63084.184736] ([] usercopy_warn+0x9c/0xd0) Dec 14 22:02:26 ub2004img kernel: [63084.184740] [ ] __check_heap_object+0xd8/0x150 Dec 14 22:02:26
[Kernel-packages] [Bug 1913933] Re: System freeze while dbus-daemon execution
** Description changed: I regularly get my system frozen while using. It does not occur on any user interaction I do periodically, so I checked the log files last time it happened: These are the last 3 kernel log entries before the freeze: Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 audit(1612017269.344:43): apparmor="DENIED" operation="open" profile="snap.standard-notes.standard-notes" name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 label="snap.standard-notes.standard-notes" Jan 30 15:34:29 ubuntu kernel: [24749.903525] exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ So I think this is related to the dbus-daemon. If you need any more information, please let me know so I can provide them. - ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dbus 1.12.20-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Jan 31 09:22:49 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/bash SourcePackage: dbus UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago) - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: chris 2241 F pulseaudio - /dev/snd/controlC0: chris 2241 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: chshr 2241 F pulseaudio + /dev/snd/controlC0: chshr 2241 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52 MachineType: Micro-Star International Co., Ltd MS-7A34 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/usr/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/usr/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 RelatedPackageVersions: - linux-restricted-modules-5.8.0-41-generic N/A - linux-backports-modules-5.8.0-41-generic N/A - linux-firmware1.190.3 + linux-restricted-modules-5.8.0-41-generic N/A + linux-backports-modules-5.8.0-41-generic N/A + linux-firmware1.190.3 RfKill: - 0: phy0: Wireless LAN - Soft blocked:
[Kernel-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
This bug is Invalid for Ubuntu. If you would like to track the problem that is in Ubuntu then please use bug 1189721. ** Package changed: bluez (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1914007 Title: RT3290 Bluetooth not finding any device Status in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: type=1400
[Kernel-packages] [Bug 1914020] Re: Fix no video output when boot up system with type-c port
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1914020 Title: Fix no video output when boot up system with type-c port Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] Connect a WD19SC/WD19TB/typeC2hdmi converter on the machine type-c port, video can't output to the external monitor. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/patch/msgid/2020110401.4165574-1-imre.d...@intel.com). Correct the typo during output setup. Fix a typo that led to some MST short pulse event handling issue (the short pulse event was handled for both encoder instances, each having its own state). [Test Case] 1. Connected the WD19SC/WD19TB/typeC2hdmi converter with the TGL platform's Type-C port and connected the external monitor on WD19SC/WD19TB/type-c2hdmi with HDMI/Displayport. 2. Cold boot the TGL platform. 3. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] Just correct the typo and have low regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914020/+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 1914007] Re: RT3290 Bluetooth not finding any device
** Changed in: bluez (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: New Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1102
[Kernel-packages] [Bug 1914033] [NEW] linux-raspi: Bump max number of CPUs
Public bug reported: NR_CPUS=4 is not very forward looking so bump it to match upstream raspberrypi and the Ubuntu generic kernel. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1914033 Title: linux-raspi: Bump max number of CPUs Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Hirsute: New Bug description: NR_CPUS=4 is not very forward looking so bump it to match upstream raspberrypi and the Ubuntu generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914033/+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 1900663] Re: Re-enable memory cgroups
** Changed in: linux-raspi (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-raspi (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => Won't Fix ** Changed in: linux-raspi (Ubuntu Groovy) Status: Won't Fix => Confirmed ** Changed in: linux-raspi (Ubuntu Focal) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1900663 Title: Re-enable memory cgroups Status in linux-raspi package in Ubuntu: In Progress Status in linux-raspi source package in Focal: Confirmed Status in linux-raspi source package in Groovy: Confirmed Status in linux-raspi source package in Hirsute: In Progress Bug description: Currently, the 5.4 and 5.8 raspi kernels disable the memory cgroup by default to conserve memory [1]. This is a legacy custom modification, that is no longer needed, since the memory cgroup code has been rewritten to no longer requires large amounts of memory [2]. So the custom patch can be dropped. The patch is also the reason why the LXC ADT test fails. [1] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/focal/commit/?id=64e543b88ea2a013e1d8e014e7c92c53df1322ed [2] https://github.com/torvalds/linux/commit/1306a85aed3ec3db98945aafb7dfbe5648a1203c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1900663/+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 1913853] Re: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging
Hello Marcel and everyone else affected, Thank you for reporting this issue. Xenial kernel 4.4.0-202 is still in -proposed therefore it's expected to be unstable. We are investigating the issues with this kernel version and will publish an update as soon as possible. In the meantime please downgrade to version -201 to have an usable system again. -- 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/1913853 Title: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging Status in linux package in Ubuntu: Confirmed Bug description: Hi there, I've updated kernel on my Ubuntu 16.04 from 4.4.0-201-generic to 4.4.0.202-generic today and it broke my system. Basic commands, such as pidof, lsof, ps fax (ps -a works) hang indefinitely and not even root issued kill -KILL will terminate them. Only thing that helps is to kill the shell that started such commands. I had to reboot back to 4.4.0-201, however during shutdown various stop jobs hanged as well and after more than 25 minutes I had to go for hard reboot. My current—NOT BROKEN—kernel has signature (cat /proc/version_signature): Ubuntu 4.4.0-201.233-generic 4.4.247 I am attaching the lspci-vnvn.log, also created with the non-broken kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913853/+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 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
Hello @firepiper, I add this PPA to get appropriate kernel. https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa $ sudo add-apt-repository ppa:canonical-kernel-team/ppa $ sudo apt-get update $ sudo apt install linux-headers-oem-20.04b $ sudo apt install linux-image-oem-20.04b Please try it out again. I use fwupdmgr to update my system firmware, maybe you can also try it out. -- 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/1879633 Title: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux-firmware source package in Groovy: Won't Fix Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [SRU Justification: oem-5.6] [Impact] Qualcomm QCA6390 series not recognized due to the lack of ath11k and all its prerequisite drivers. $ lspci :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101] Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] [Fix] Tag ath11k-qca6390-bringup-202011301608 from ath tree (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git) marks first stable milestone on the platform/device under development since v5.6-rc1. Most of the commits under this tag, ~350 commits, have been in vanilla kernel v5.10-rc4 except those starting from commit 065c9528cc50 ("ath11k: add 64bit check before reading msi high addr"). While ath11k depends on MHI bus, qrtr and qmi helpers, changes falling in these components are also pulled. Besides, tx encapsulation https://lore.kernel.org/linux-wireless/20200908123702.88454-1-...@nbd.name/ and a couple more inclusive of 6 GHz capability, BSS Color were also pulled to satisfy API changes in mac80211/cfg80211. [Test Case] 1. Install firmwares & boot from patched kernel, 2. ath11k should be now up and running. Check with `sudo dmesg | grep ath11k` While this is going to bring massive changes to the kernel, as well as shared wireless stack that is not only used by ath11k but also many others, prebuilt kernel/firmware packages were deployed on platforms with and without ath11k for regression tests, and so far the results are positive. [Where problems could occur] ath11k and its relying parts have never been enabled in oem-5.6, so changes to them should have little effect on most platforms. For platforms equip QCA6390, this will be the first time they're probed and enabled, and as the driver is still under polishing, there can be regressions, performance lost, power consumption increase at this moment. Changes to wireless stack could also be an issue as this introduces interface changes to the API, so maybe DKMS packages in the wild will be affected. == SRU for U/OEM-5.10 == [SRU Justification: U/OEM-5.10] [Impact] Qualcomm QCA6390 series not recognized due to the lack of ath11k driver. $ lspci :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101] Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] [Fix] 25 additional fixes in ath tree (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git), tag ath11k-qca6390-bringup-202011301608 to resolve issues on TGL platforms, and firmware updates from mainline are required. [Test Case] 1. Install firmwares & boot from patched kernel, 2. ath11k should be now up and running. Check with `sudo dmesg | grep ath11k` [Where problems could occur] There has been a lot patches landed in kernel since 5.7 devel cycle. The last bits here has merge base with mainline at v5.10-rc4, and since then only patches for ath11k itself has been committed. == Original Bug Description == Qualcomm QCA6390 series not recognized due to the lack of ath11k driver. :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101] Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] Depending on bug 1891632 to fix Wi-Fi dead after resumed from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1842 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs
[Kernel-packages] [Bug 1914020] Re: Fix no video output when boot up system with type-c port
** Description changed: [Impact] - Connect a type-c2hdmi converter on the machine type-c port, video can't output to the external monitor. + Connect a WD19SC/WD19TB/typeC2hdmi converter on the machine type-c port, video can't output to the external monitor. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/patch/msgid/2020110401.4165574-1-imre.d...@intel.com). Correct the typo during output setup. Fix a typo that led to some MST short pulse event handling issue (the short pulse event was handled for both encoder instances, each having its own state). - [Test Case] - 1. Connected the WD19SC/WD19TB/type-c2hdmi converter with the TGL platform's Type-C port and + 1. Connected the WD19SC/WD19TB/typeC2hdmi converter with the TGL platform's Type-C port and connected the external monitor on WD19SC/WD19TB/type-c2hdmi with HDMI/Displayport. 2. Cold boot the TGL platform. 3. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] Just correct the typo and have low regression risk. -- 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/1914020 Title: Fix no video output when boot up system with type-c port Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] Connect a WD19SC/WD19TB/typeC2hdmi converter on the machine type-c port, video can't output to the external monitor. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/patch/msgid/2020110401.4165574-1-imre.d...@intel.com). Correct the typo during output setup. Fix a typo that led to some MST short pulse event handling issue (the short pulse event was handled for both encoder instances, each having its own state). [Test Case] 1. Connected the WD19SC/WD19TB/typeC2hdmi converter with the TGL platform's Type-C port and connected the external monitor on WD19SC/WD19TB/type-c2hdmi with HDMI/Displayport. 2. Cold boot the TGL platform. 3. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] Just correct the typo and have low regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914020/+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 1914007] Re: RT3290 Bluetooth not finding any device
Yes, you have a different problem caused by a driver that is not supported or provided by Ubuntu. That makes this bug Invalid for the 'Ubuntu' task. My only suggestions are: 1. Subscribe to bug 1189721. 2. Try replacing the wireless card in the laptop with a different card, ideally made by Intel. Because it looks like RT3290 might never be supported in Linux. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create"
[Kernel-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
*** This bug is a duplicate of bug 1914007 *** https://bugs.launchpad.net/bugs/1914007 ** Changed in: bluez (Ubuntu) Status: In Progress => Invalid ** This bug has been marked a duplicate of bug 1914007 RT3290 Bluetooth not finding any device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
[Kernel-packages] [Bug 1914020] Re: Fix no video output when boot up system with type-c port
** Tags added: oem-priority originate-from-1913553 ouagadougou ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- 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/1914020 Title: Fix no video output when boot up system with type-c port Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] Connect a WD19SC/WD19TB/typeC2hdmi converter on the machine type-c port, video can't output to the external monitor. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/patch/msgid/2020110401.4165574-1-imre.d...@intel.com). Correct the typo during output setup. Fix a typo that led to some MST short pulse event handling issue (the short pulse event was handled for both encoder instances, each having its own state). [Test Case] 1. Connected the WD19SC/WD19TB/typeC2hdmi converter with the TGL platform's Type-C port and connected the external monitor on WD19SC/WD19TB/type-c2hdmi with HDMI/Displayport. 2. Cold boot the TGL platform. 3. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] Just correct the typo and have low regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914020/+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 1902864] Re: aws: update patch to batch hibernate and resume IO requests
** Changed in: linux-aws (Ubuntu Groovy) Assignee: (unassigned) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1902864 Title: aws: update patch to batch hibernate and resume IO requests Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Focal: New Status in linux-aws source package in Groovy: Fix Released Bug description: [Impact] During hibernation and resume the kernel is submitting an individual IO request for each page of data. In the aws kernel we are using a custom SAUCE patch to batch IO requests together in order to achieve better performance. Recently a patch designed to achieve the same goal has been applied upstream. This patch has been acknowledged by Amazon and it has shown a performance improvement. Moreover, this patch looks much cleaner compared to the custom patch that we are using and it's upstream, so it makes sense to drop the previous patch and apply this new one. [Test case] Hibernate + resume and measure the time required to perform these operations. Performance result reported by Amazon: One hibernate and resume cycle for 16GB RAM out of 32GB in use takes around 21 minutes before the change, and 1 minutes after the change on a system with limited storage IOPS. [Fix] Apply the following upstream commit: 55c4478a8f0ecedc0c1a0c9379380249985c372a ("PM: hibernate: Batch hibernate and resume IO requests") Drop the custom aws SAUCE patch: 11c3fa3b29722124f5c9122671983614383686db ("UBUNTU: SAUCE: [aws] PM / hibernate: Speed up hibernation by batching requests") [Regression potential] Upstream patch that allows to drop a custom patch that is doing the same thing. The only potential regression would be a performance drop, but according to Amazon's tests and our tests, we didn't notice any performance regression. Any other kind of regression would be considered as upstream regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1902864/+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 1914020] [NEW] Fix no video output when boot up system with type-c port
Public bug reported: [Impact] Connect a type-c2hdmi converter on the machine type-c port, video can't output to the external monitor. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/patch/msgid/2020110401.4165574-1-imre.d...@intel.com). Correct the typo during output setup. Fix a typo that led to some MST short pulse event handling issue (the short pulse event was handled for both encoder instances, each having its own state). [Test Case] 1. Connected the WD19SC/WD19TB/type-c2hdmi converter with the TGL platform's Type-C port and connected the external monitor on WD19SC/WD19TB/type-c2hdmi with HDMI/Displayport. 2. Cold boot the TGL platform. 3. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] Just correct the typo and have low regression risk. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1913553 ouagadougou ** Description changed: - [impact] + [Impact] + Connect a type-c2hdmi converter on the machine type-c port, video can't output to the external monitor. + + [Fix] + The patch is provided by Imre(https://patchwork.freedesktop.org/patch/msgid/2020110401.4165574-1-imre.d...@intel.com). + + Correct the typo during output setup. + Fix a typo that led to some MST short pulse event handling issue (the + short pulse event was handled for both encoder instances, each having + its own state). + + + [Test Case] + 1. Connected the WD19SC/WD19TB/type-c2hdmi converter with the TGL platform's Type-C port and + connected the external monitor on WD19SC/WD19TB/type-c2hdmi with HDMI/Displayport. + 2. Cold boot the TGL platform. + 3. Check the monitor can be blinked and the video can output to the monitor. + + [Where problems could occur] + Just correct the typo and have low regression risk. -- 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/1914020 Title: Fix no video output when boot up system with type-c port Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] Connect a type-c2hdmi converter on the machine type-c port, video can't output to the external monitor. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/patch/msgid/2020110401.4165574-1-imre.d...@intel.com). Correct the typo during output setup. Fix a typo that led to some MST short pulse event handling issue (the short pulse event was handled for both encoder instances, each having its own state). [Test Case] 1. Connected the WD19SC/WD19TB/type-c2hdmi converter with the TGL platform's Type-C port and connected the external monitor on WD19SC/WD19TB/type-c2hdmi with HDMI/Displayport. 2. Cold boot the TGL platform. 3. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] Just correct the typo and have low regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914020/+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 1913410] Re: aws: update Xen hibernation patch set
** Changed in: linux-aws (Ubuntu Focal) Importance: High => Medium ** Changed in: linux-aws (Ubuntu Bionic) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux-aws (Ubuntu Groovy) Assignee: (unassigned) => Andrea Righi (arighi) ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Xenial) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux-aws (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1913410 Title: aws: update Xen hibernation patch set Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Xenial: New Status in linux-aws source package in Bionic: New Status in linux-aws source package in Focal: New Status in linux-aws source package in Groovy: New Bug description: [Impact] Amazon maintains a custom patch to enable hibernation in Xen guests that is not upstream yet. This patch set has been updated in AWS AL2 and we should sync up the patch set in our AWS kernels. [Test case] Tests have been performed (simply doing multiple hibernate/resume cycles) with the new patch set applied and they have shown significant improvement in terms of reliability. [Fix] Backport/apply the new Xen hibernation patch set from AWS AL2. [Regression potential] The patch set is affecting only Xen (in particular the guest code) and only hibernation, so the risk of regressions is restricted to this particular scenario (Xen + hibernation). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1913410/+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 1914007] Re: RT3290 Bluetooth not finding any device
And yeah in that given bug post there is a solution how to get working RT3290 but my problem is different my adapter is working but the agent Bluetoothctl is giving an error related to blueman so isn't it a different problem? @Daniel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [
[Kernel-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
Please suggest me a solution for this @Daniel. ** This bug is no longer a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED"
[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown
Potential solution: https://lore.kernel.org/linux-acpi/20201201213019.1558738-1-furq...@google.com/T/#m8a1f86c7024264201eac37223594c5d15112ae73 -- 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/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1912935] Re: battery drain while notebook off / shutdown
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc5/amd64/ -- 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/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1914007] Re: RT3290 Bluetooth not finding any device
** Changed in: bluez (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: type=1400 audit(1611909043.887:66):
[Kernel-packages] [Bug 1902588] Re: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.6 --- zfs-linux (0.8.3-1ubuntu12.6) focal; urgency=medium [ Didier Roche ] [ Jean-Baptiste Lallement ] * Generate clone uuid without dd which is flagged as having an executable stack. Thanks Usarin Heininga for the patch (LP: #1894329) [ Andrea Righi ] * fix potential user-space double free when running "zfs mount -a" (LP: #1902588) - 4702-Revert-Let-zfs-mount-all-tolerate-in-progress-mounts.patch -- Colin Ian King Mon, 30 Nov 2020 19:00:00 + ** Changed in: zfs-linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1902588 Title: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Bug description: == SRU Justification Focal == zfs mount -a when run on a nonempty mountpoint causes a double free, memory corruption, and a segfault. == Impact == Double free and memory corruption in ZFS when run as root and attempting to mount all. While running this I observed other ZFS volumes randomly unmounting, and mount points owner being spuriously zeroed (set to root). == Fix == https://github.com/openzfs/zfs/commit/d1b84da8c1a69c084f04b504beefe804591bca07 == Test == Steps are laid out in the ZFS issue: https://github.com/openzfs/zfs/issues/9560 == Regression Potential == Limited to the behavior of zfs mount when a previous attempt to mount has failed, or is still in progress. Changes the behavior in that case to failure, instead of double-free. Example case of running into this bug, with dmesg: https://pastebin.com/YRXW8WgM $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.4 Candidate: 0.8.3-1ubuntu12.4 Version table: *** 0.8.3-1ubuntu12.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+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 1894329] Re: ZFS revert from grub menu not working.
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.6 --- zfs-linux (0.8.3-1ubuntu12.6) focal; urgency=medium [ Didier Roche ] [ Jean-Baptiste Lallement ] * Generate clone uuid without dd which is flagged as having an executable stack. Thanks Usarin Heininga for the patch (LP: #1894329) [ Andrea Righi ] * fix potential user-space double free when running "zfs mount -a" (LP: #1902588) - 4702-Revert-Let-zfs-mount-all-tolerate-in-progress-mounts.patch -- Colin Ian King Mon, 30 Nov 2020 19:00:00 + ** Changed in: zfs-linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1894329 Title: ZFS revert from grub menu not working. Status in coreutils package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: Fix Released Status in coreutils source package in Focal: Incomplete Status in zfs-linux source package in Focal: Fix Released Status in coreutils source package in Groovy: Incomplete Status in zfs-linux source package in Groovy: Fix Released Bug description: [Impact] * Users can’t revert to previous snapshots when enabling the hw enablement stack kernel on focal or using any more recent version. * The option is available on grub and will let you with a broken system, partially cloned. [Test Case] * Boot on a system, using ZFS and ZSys. * In grub, select "History" entry * Select one of the "Revert" option: the system should boot after being reverted with an older version. [Where problems could occur] * The code is in the initramfs, where the generated id suffix for all our ZFS datasets was empty due to new coreutils/kernels. * We replace dd with another way (more robust and simple) for generating this ID. - @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the dataset without a proper suffix. Replacing the function with: uid() { grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 } fixes the problem. Ubuntu version is: Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 zfs-initramfs version is: 0.8.4-1ubuntu11 With regards, Usarin Heininga ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 4 20:23:44 2020 InstallationDate: Installed on 2020-09-02 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+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 1902672] Re: Support Advantech UNO-420 platform
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium -- 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/1902672 Title: Support Advantech UNO-420 platform Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: [Impact] There are some drivers are required to enable Advantech UNO-420 platform. [Fix] Advantech is submitting their drivers to upstream for review, and considering that the patches are new drivers, it should be safe pull them back to ubuntu kernel. https://lkml.org/lkml/2021/1/18/500 [Test] Verified on Advantech UNO-420 platform. [Where problems could occur] Those commits create 3 new drivers, and do not modify any existing drivers. Should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902672/+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 1914007] Re: RT3290 Bluetooth not finding any device
Yeah I know that it might be a driver issue, but there no other option for me and I have gone through the given bug by you and its quite old and available for old kernal versions and I am a noob in these bugs and all and have no knowlwdge about this. I tried there given solution but I got errors in them and as I said (have no knowledge) don't know how to fix it.BTW Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: New Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create"
[Kernel-packages] [Bug 1913864] Re: Use gcc-10 to build 5.8 riscv backport kernel for focal
Pulling severity back to high (critical would be data corruption/loss in production) ** Package changed: linux (Ubuntu) => linux-riscv-5.8 (Ubuntu) ** Also affects: linux-riscv-5.8 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-riscv-5.8 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-riscv-5.8 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-riscv-5.8 (Ubuntu Focal) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux-riscv-5.8 (Ubuntu) Importance: Critical => High ** Changed in: linux-riscv-5.8 (Ubuntu) Status: In Progress => Invalid ** Changed in: linux-riscv-5.8 (Ubuntu) Assignee: Colin Ian King (colin-king) => (unassigned) -- 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/1913864 Title: Use gcc-10 to build 5.8 riscv backport kernel for focal Status in linux-riscv-5.8 package in Ubuntu: Invalid Status in linux-riscv-5.8 source package in Focal: In Progress Bug description: == SRU RISC-V 5.8 Focal backport kernel == The 5.8 RISC-V kernel has boot issues when compiled with gcc 9. This can be fixed by building it with gcc-10. == Fix == Use gcc-10, e.g.: diff --git a/debian.master/control.stub.in b/debian.master/control.stub.in index 9c1e956092bf..3b920328caff 100644 --- a/debian.master/control.stub.in +++ b/debian.master/control.stub.in @@ -68,7 +68,7 @@ Section: devel Priority: optional Provides: linux-source Depends: ${misc:Depends}, binutils, bzip2, coreutils -Recommends: libc-dev, gcc, make +Recommends: libc-dev, gcc-10, make Suggests: libncurses-dev | ncurses-dev, kernel-package, libqt3-dev Description: Linux kernel source for version PKGVER with Ubuntu patches This package provides the source code for the Linux kernel version diff --git a/debian/rules b/debian/rules index 627ca3cb968f..425d33b35fde 100755 --- a/debian/rules +++ b/debian/rules @@ -8,6 +8,7 @@ # DEBIAN=$(shell awk -F= '($$1 == "DEBIAN") { print $$2 }' https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1913864/+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 1715866] Re: Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues
Thank you for reporting this bug to Ubuntu. Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1715866 Title: Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues Status in linux package in Ubuntu: Incomplete Bug description: When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized immediately but it doesn't work at all even it "connects" and says connection established with good quality - it's poor and almost zero quality with frequent disconnections. All this makes equipments with ralink wifi cards unable to work under linux distros and there're thousands of them. Recently found modded drivers for RT3290 which installed without any issues and wifi worked after that like a charm, but after system reinstall I can't install theese modded drivers anymore and there're some issues during installation and loading kernel modules (maybe it's something with latest linux kernels)... Anyway it's pointess to use RT2800pci driver for physical RT3290 chip cause it's a wrong piece of code and Ubuntu maintainers should fix this. BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is seriously critical. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pawel 2113 F pulseaudio /dev/snd/controlC0: pawel 2113 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-08 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. X750JB NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X750JB.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X750JB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X750JB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715866/+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 1913859] Re: RT3290 Bluetooth not finding any device
** This bug is no longer a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver ** Changed in: bluez (Ubuntu) Status: Invalid => In Progress ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Piyush Santosh Mhatre (piyush-m) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: In Progress Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw"
[Kernel-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
** This bug is no longer a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: New Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez"
[Kernel-packages] [Bug 1914015] [NEW] hirsute/linux-raspi: Upstream raspberrypi patchset 2021-01-23
Public bug reported: Upstream raspberrypi patchset 2021-01-23 Ported from the following raspberrypi branch: rpi-5.11.y from https://github.com/raspberrypi/linux.git configs: Add CRYPTO_ADIANTUM=m configs: Regenerate defconfigs configs: Add NVMEM_RMEM=m for 2711 ARM: multi_v7_defconfig: Enable nvmem's rmem driver arm64: defconfig: Enable nvmem's rmem driver ARM: dts: bcm2711: Add reserved memory template to hold firmware configuration nvmem: Add driver to expose reserved memory as nvmem dt-bindings: nvmem: Add bindings for rmem driver configs: Add CONFIG_USB_NET_AQC111=m configs: Add CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m staging: vc04_services: ISP: Add colour denoise control uapi: bcm2835-isp: Add colour denoise configuration bcm2835-dma: Add bcm2835-dma: Add DMA_WIDE_SOURCE and DMA_WIDE_DEST flags dt: Enable DMA_WIDE_SOURCE and DMA_WIDE_DEST for hdmi audio configs: Enable BCM2835 thermal driver in kernel8 vc4: Correct POS1_SCL for hvs5 vc4: Correct lbm size and calculation overlays: seeed-can-fd-hat: clarify how to identify HAT version dtoverlays: Update sensor overlays to use cam1_reg where possible dt: Add a camera regulator node to all downstream Pi platforms arch/arm: Add __memset alias to memset_rpi.S overlays: add spi override to merus-amp overlay overlays: add wm8960-soundcard overlay overlays: Add overlay for Seeed Studio CAN BUS FD HAT v1 (based on mcp2517fd) overlays: give Seeed Studio CAN BUS FD HAT a -v2 postfix media: i2c: ov5647: Selection compliance fixes bcm2711-rpi.dtsi: Bump hdmi audio dma priority to max bcm2835-dma: Avoid losing CS flags after interrupt dts: Enable DMA_WIDE_SOURCE for hdmi audio dma staging/bcm2835-isp: Log the number of excess supported formats staging/bcm2835-isp: Add the unpacked (16bpp) raw formats staging/bcm2835-codec: Log the number of excess supported formats staging/bcm2835-codec: Add the unpacked (16bpp) raw formats staging/vc04_services: Add additional unpacked raw formats staging/mmal-vchiq: Fix incorrect static vchiq_instance. staging: vchiq: Fix bulk transfers on 64-bit builds vc-sm-cma: fixed kbuild problem staging: vchiq: Fix bulk userdata handling drm/vc4: hdmi: Enable 10/12 bpc output drm/vc4: hdmi: Limit the BCM2711 to the max without scrambling drm/vc4: hdmi: Use the connector state pixel rate for the PHY drm/vc4: hdmi: Store pixel frequency in the connector state drm/vc4: hdmi: Create a custom connector state drm/vc4: hdmi: Don't access the connector state in reset if kmalloc fails drm/vc4: hdmi: Take into account the clock doubling flag in atomic_check drm/vc4: Pass the atomic state to encoder hooks drm/vc4: hvs: Align the HVS atomic hooks to the new API drm/atomic: Pass the full state to CRTC atomic enable/disable media: i2c: imx477: Selection compliance fixes drm/vc4: Correct DSI register definition vc4_hdmi: Move hdmi reset to bind drm/vc4: Add configuration for BCM2711 DSI1. dt-bindings: Add compatible for BCM2711 DSI1 drm/vc4: Add support for DSI0 media: ov9281: Add 1280x720 and 640x480 modes drm/panel/raspberrypi-ts: Insert delay before polling for startup state drm/panel/raspberrypi-touchscreen: Use independent I2C actions with delay. Input: edt-ft5x06: Poll the device if no interrupt is configured. vc4: Clear unused infoframe packet RAM registers PCI: brcmstb: Restore initial fundamental reset vc4_hdmi: Report that 3d/stereo is allowed phy: broadcom: Add bcm54213pe configuration phy: broadcom: split out the BCM54213PE from the BCM54210E IDs firmware: raspberrypi: Add support for tryonce reboot flag watchdog: bcm2835: Ignore params after the partition number bcm2835-pcm: Fix up multichannel pcm audio PiFi-40 driver, Makefile and Kconfig bcm2708_fb: Fix a build warning rpivid_h625: Fix build warnings gpio-fsm: Fix a build warning dwc_otg: Minimise header and fix build warnings rpisense-fb: Set pseudo_pallete to prevent crash on fbcon takeover staging: bcm2835-audio: Add disable-headphones flag xhci: quirks: add link TRB quirk for VL805 drm/vc4: Add the 2711 HVS as a suitable DMA node drm/vc4: Add all the HDMI registers into the debugfs dumps drm/vc4: Reading the hotplug register is only valid if no GPIO defined gpio: Add gpio-fsm driver staging: vc04_services: ISP: Add a more complex ISP processing component uapi: bcm2835-isp: Add bcm2835-isp uapi header file bcm2835-dma: only reserve channel 0 if legacy dma driver is enabled staging: vc04_services: Add a V4L2 M2M codec driver staging: mmal-vchiq: Use vc-sm-cma to support zero copy staging: mmal-vchiq: Add monochrome image formats staging: vchiq-mmal: Add support for 14bit Bayer staging: vc04_services: Add new vc-sm-cma driver staging: bcm2835-camera: Replace deprecated V4L2_PIX_FMT_BGR32 dwc_otg: initialise sched_frame for periodic QHs that were parked USB: gadget: f_hid: avoid crashes and log spam char: Add broadcom char drivers back to build files net: bcmgenet: Reset RBUF on first open rpivid_h265: Fix width/height typo brcmfmac: Increase power saving delay to 2s
[Kernel-packages] [Bug 1355096] Re: Ralink RT3290 [1814:3298] missing bluetooth support with 12.04.5(kernel 3.13)
*** This bug is a duplicate of bug 1189721 *** https://bugs.launchpad.net/bugs/1189721 ** This bug has been marked a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1355096 Title: Ralink RT3290 [1814:3298] missing bluetooth support with 12.04.5(kernel 3.13) Status in HWE Next: Won't Fix Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Look into the spec, the ralink rt3290 should have bluetooth supported, https://wikidevi.com/files/Ralink/RT3290%20product%20brief.pdf System with fresh 12.04.5 installed does not detect the bluetooth correctly. rfkill failed to show the bluetooth device: ubuntu@201209-11786:~/$ rfkill list all 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no However lspci does listed bluetooth device: ubuntu@201209-11786:~/$ lspci -v|grep -i RT3290 02:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe 02:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: boot/vmlinuz-3.13.0-32-generic] ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Aug 11 05:37:32 2014 InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1355096/+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 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver
** Tags removed: raring ** Tags added: focal xenial ** Package changed: ubuntu => linux (Ubuntu) -- 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/1189721 Title: Ralink RT3290 doesn't have a bluetooth driver Status in bluetooth: Confirmed Status in Linux: Confirmed Status in Linux Mint: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: As of Raring Ubuntu has a wifi driver for the RT3290 that works out of the box. It still does not have bluetooth support. This thread in the Ubuntu forums links to a driver that is claimed to work: http://ubuntuforums.org/showthread.php?t=2115570 --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graeme 2412 F pulseaudio CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70 InstallationDate: Installed on 2013-05-17 (144 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Hewlett-Packard HP ProBook 4540s MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/06/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.32 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1018C1100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/bluetooth/+bug/1189721/+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 1536433] Re: Bluetooth not working for Ubuntu 14.04
*** This bug is a duplicate of bug 1189721 *** https://bugs.launchpad.net/bugs/1189721 ** This bug has been marked a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- 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/1536433 Title: Bluetooth not working for Ubuntu 14.04 Status in linux-firmware package in Ubuntu: New Bug description: My laptop is HP 14r 004TU 64 Bits. I have installed Ubuntu 14.04. The problem is that Bluetooth is not getting activated. It neither gets on nor shows its visibility. All options are shown grey in color. I want to connect my laptop to Bose Soundlink mini, but it is not also paired with any other device. It always say "No Bluetooth adapters found". Please help me regarding this. Thanks in advance. Below are some details of the output. Command - lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 (rev e4) 00:1c.1 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 2 (rev e4) 00:1c.2 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 (rev e4) 00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 (rev e4) 00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04) 08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 07) 09:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe 09:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth Command - lsusb Bus 001 Device 003: ID 064e:c342 Suyin Corp. Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1536433/+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 1582756] Re: Bluetooth Option not found
*** This bug is a duplicate of bug 1189721 *** https://bugs.launchpad.net/bugs/1189721 ** This bug has been marked a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- 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/1582756 Title: Bluetooth Option not found Status in linux package in Ubuntu: Triaged Bug description: After installing Ubuntu 16.04 i cannot find my bluetooth. When I type bluetooth and click on search tab, its all grayed out. My device: 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] DeviceName: Ralink RT3290LE 802.11bgn 1x1 Wi-Fi Adapter Subsystem: Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Adapter [103c:18ec] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: suresh 1644 F pulseaudio /dev/snd/controlC0: suresh 1644 F pulseaudio CurrentDesktop: Unity Date: Tue May 17 16:24:00 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=bf3cfb89-85e2-4c0f-aef8-673d9fec256c InstallationDate: Installed on 2016-05-17 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 350 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=71b1d57d-246d-47a1-9bd5-bc12ca92cde8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 21B8 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 46.0B dmi.chassis.asset.tag: 5CG4382PDH dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd06/12/2014:svnHewlett-Packard:pnHP350G1:pvr099810167:rvnHewlett-Packard:rn21B8:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 350 G1 dmi.product.version: 099810167 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582756/+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 1913859] Re: RT3290 Bluetooth not finding any device
** This bug is no longer a duplicate of bug 1914007 RT3290 Bluetooth not finding any device ** This bug has been marked a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: In Progress Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [
[Kernel-packages] [Bug 1906131] Re: No rule to make target 'scripts/module.lds' while building out-of-tree modules
This is happening to my NVIDIA module build with kernel 5.10.12 as well. root@jaxel:~# dpkg-reconfigure nvidia-dkms-460 Removing all DKMS Modules Done. update-initramfs: deferring update (trigger activated) update-initramfs: Generating /boot/initrd.img-5.9.16-050916-generic INFO:Enable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here Loading new nvidia-460.39 DKMS files... Building for 5.9.16-050916-generic 5.10.12-051012-generic Building for architecture x86_64 Building initial module for 5.9.16-050916-generic Secure Boot not enabled on this system. Done. nvidia.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.9.16-050916-generic/updates/dkms/ nvidia-modeset.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.9.16-050916-generic/updates/dkms/ nvidia-drm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.9.16-050916-generic/updates/dkms/ nvidia-uvm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.9.16-050916-generic/updates/dkms/ depmod... DKMS: install completed. Building initial module for 5.10.12-051012-generic ERROR (dkms apport): kernel package linux-headers-5.10.12-051012-generic is not supported Error! Bad return status for module build on kernel: 5.10.12-051012-generic (x86_64) Consult /var/lib/dkms/nvidia/460.39/build/make.log for more information. --- /var/lib/dkms/nvidia/460.39/build/make.log make -f ./scripts/Makefile.modpost sed 's/ko$/o/' /var/lib/dkms/nvidia/460.39/build/modules.order | scripts/mod/modpost -a -o /var/lib/dkms/nvidia/460.39/build/Module.symvers -e -i Module.symvers -T - make -f ./scripts/Makefile.modfinal make[3]: *** No rule to make target 'scripts/module.lds', needed by '/var/lib/dkms/nvidia/460.39/build/nvidia-drm.ko'. Stop. make[3]: *** Waiting for unfinished jobs cc -Wp,-MMD,/var/lib/dkms/nvidia/460.39/build/.nvidia-drm.mod.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/9/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -fmacro-prefix-map=./= -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-address-of-packed-member -O2 --param=allow-store-data-races=0 -Wframe-larger-than=1024 -fstack-protector-strong -Wno-unused-but-set-variable -Wimplicit-fallthrough -Wno-unused-const-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-stringop-truncation -Wno-array-bounds -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -fno-strict-overflow -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fcf-protection=none -Wno-packed-not-aligned -DMODULE -DKBUILD_BASENAME='"nvidia_drm.mod"' -DKBUILD_MODNAME='"nvidia_drm"' -c -o /var/lib/dkms/nvidia/460.39/build/nvidia-drm.mod.o /var/lib/dkms/nvidia/460.39/build/nvidia-drm.mod.c make[2]: *** [scripts/Makefile.modpost:117: __modpost] Error 2 make[1]: *** [Makefile:1709: modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.10.12-051012-generic' -- 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/1906131 Title: No rule to make target 'scripts/module.lds' while building out-of-tree modules Status in linux package in Ubuntu: Fix Released Status in linux package in Debian: Unknown Bug description: kernel v5.10-rc1 introduced a change ( 596b0474d3d9 "kbuild: preprocess module linker script" ) that affects where and how scripts/module.lds is
[Kernel-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
Thanks for reporting the bug again. Unfortunately because you're using a driver (rtbth kernel module) that's not from Ubuntu, we can't support it. So that makes this bug 'Invalid'. I can see however that you didn't get much choice because it seems Ubuntu doesn't offer a driver for RTL3290 bluetooth. This issue is already covered by bug 1189721 so I will group it there. ** This bug has been marked a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: New Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [
[Kernel-packages] [Bug 1914013] [NEW] linux-raspi: Build compressed arm64 kernel images
Public bug reported: The Raspberry Pi firmware can now handle compressed arm6 kernels, so build them as such to save some disk space. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: In Progress ** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Hirsute) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1914013 Title: linux-raspi: Build compressed arm64 kernel images Status in linux-raspi package in Ubuntu: In Progress Status in linux-raspi source package in Hirsute: In Progress Bug description: The Raspberry Pi firmware can now handle compressed arm6 kernels, so build them as such to save some disk space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914013/+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 1189721] [NEW] Ralink RT3290 doesn't have a bluetooth driver
You have been subscribed to a public bug: As of Raring Ubuntu has a wifi driver for the RT3290 that works out of the box. It still does not have bluetooth support. This thread in the Ubuntu forums links to a driver that is claimed to work: http://ubuntuforums.org/showthread.php?t=2115570 --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graeme 2412 F pulseaudio CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70 InstallationDate: Installed on 2013-05-17 (144 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Hewlett-Packard HP ProBook 4540s MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/06/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.32 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1018C1100 dmi.sys.vendor: Hewlett-Packard ** Affects: bluetooth Importance: Medium Status: Confirmed ** Affects: linux Importance: Medium Status: Confirmed ** Affects: linuxmint Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-stop-nagging focal kernel-request-3.13.0-24.46 trusty xenial -- Ralink RT3290 doesn't have a bluetooth driver https://bugs.launchpad.net/bugs/1189721 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1913859] Re: RT3290 Bluetooth not finding any device
*** This bug is a duplicate of bug 1914007 *** https://bugs.launchpad.net/bugs/1914007 ** This bug has been marked a duplicate of bug 1914007 RT3290 Bluetooth not finding any device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit:
[Kernel-packages] [Bug 1914009] [NEW] Disable unsupported features
Public bug reported: Disable features not supported by the Raspberry Pi firmware/hardware: - CPU hot plugging - Hibernation - Suspend to disk ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: In Progress ** Package changed: linux-raspi2 (Ubuntu) => linux-raspi (Ubuntu) ** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Hirsute) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1914009 Title: Disable unsupported features Status in linux-raspi package in Ubuntu: In Progress Status in linux-raspi source package in Hirsute: In Progress Bug description: Disable features not supported by the Raspberry Pi firmware/hardware: - CPU hot plugging - Hibernation - Suspend to disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914009/+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