[Kernel-packages] [Bug 2044718] Re: mantic on raspberry5: x and/or lightdm problems
Reassigning to xorg-server initially. Ubuntu doesn't have gldriver-test to enable xorg desktops to work on a raspi5. So is there an equivalent package for Ubuntu or should gldriver-test be added to the ubuntu repo? ** Also affects: xorg-server (Ubuntu) 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/2044718 Title: mantic on raspberry5: x and/or lightdm problems Status in linux-raspi package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: New Bug description: running mantic on raspberry5, graphical sessions doesn't start unless on gdm3; while performing installation, Ubuntu Budgie graphical session goes on without problems but at reboot DE doesn't start. Tried installing "classical" ubuntu and DE came on w/o problems; installed budgie-desktop and lightdm side by side and budgie didn't start; installed sddm with same results. Only gdm3 works See attached logs collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2044718/+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 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes error on login/live session
** Summary changed: - df: /sys/firmware/efi/efivars: Invalid argument causes installation crash + df: /sys/firmware/efi/efivars: Invalid argument causes error on login/live session ** Description changed: df: /sys/firmware/efi/efivars: Invalid argument appears on first display of the live session - I note subsequently that at the end of the installation curtin fails due to an efivars error - looking at syslog I saw various efivars errors so I'm filing this with the kernel since this is the first instance. + + Note - raised separate issue for the installation crash which has now + been duplicated against + https://bugs.launchpad.net/subiquity/+bug/2003222 i.e. running grep efivars /var/log/* ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber /dev/snd/seq:ubuntu-budgie 2074 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.486 CurrentDesktop: Budgie:GNOME Date: Sun Oct 8 16:27:29 2023 LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 (20231008.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.5.0-7-generic N/A linux-backports-modules-6.5.0-7-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D9.B00.1802021100 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. -- 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/2038765 Title: df: /sys/firmware/efi/efivars: Invalid argument causes error on login/live session Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: df: /sys/firmware/efi/efivars: Invalid argument appears on first display of the live session - I note subsequently that at the end of the installation curtin fails due to an efivars error - looking at syslog I saw various efivars errors so I'm filing this with the kernel since this is the first instance. Note - raised separate issue for the installation crash which has now been duplicated against https://bugs.launchpad.net/subiquity/+bug/2003222 i.e. running grep efivars /var/log/* ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber /dev/snd/seq:ubuntu-budgie 2074 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.486 CurrentDesktop: Budgie:GNOME Date: Sun Oct 8 16:27:29 2023 LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 (20231008.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.5.0-7-generic N/A linux-backports-modules-6.5.0-7-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc.
[Kernel-packages] [Bug 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
After installing via the legacy iso I saw the same message on login. Opening a terminal and typing df I saw again the same message in the terminal followed by the normal df output. -- 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/2038765 Title: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: df: /sys/firmware/efi/efivars: Invalid argument appears on first display of the live session - I note subsequently that at the end of the installation curtin fails due to an efivars error - looking at syslog I saw various efivars errors so I'm filing this with the kernel since this is the first instance. i.e. running grep efivars /var/log/* ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber /dev/snd/seq:ubuntu-budgie 2074 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.486 CurrentDesktop: Budgie:GNOME Date: Sun Oct 8 16:27:29 2023 LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 (20231008.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.5.0-7-generic N/A linux-backports-modules-6.5.0-7-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D9.B00.1802021100 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/2038765/+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 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
** Description changed: df: /sys/firmware/efi/efivars: Invalid argument appears on first display - of the installer - I note that at the end of the installation curtin - fails due to an efivars error - looking at syslog I saw various efivars - errors so I'm filing this with the kernel since this is the first - instance. + of the live session - I note subsequently that at the end of the + installation curtin fails due to an efivars error - looking at syslog I + saw various efivars errors so I'm filing this with the kernel since this + is the first instance. i.e. running grep efivars /var/log/* ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber - /dev/snd/seq:ubuntu-budgie 2074 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber + /dev/snd/seq:ubuntu-budgie 2074 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.486 CurrentDesktop: Budgie:GNOME Date: Sun Oct 8 16:27:29 2023 LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 (20231008.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: - LANG=C.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=C.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: - linux-restricted-modules-6.5.0-7-generic N/A - linux-backports-modules-6.5.0-7-generic N/A - linux-firmware 20230919.git3672ccab-0ubuntu2 + linux-restricted-modules-6.5.0-7-generic N/A + linux-backports-modules-6.5.0-7-generic N/A + linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D9.B00.1802021100 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. -- 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/2038765 Title: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash Status in linux package in Ubuntu: Confirmed Bug description: df: /sys/firmware/efi/efivars: Invalid argument appears on first display of the live session - I note subsequently that at the end of the installation curtin fails due to an efivars error - looking at syslog I saw various efivars errors so I'm filing this with the kernel since this is the first instance. i.e. running grep efivars /var/log/* ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber /dev/snd/seq:ubuntu-budgie 2074 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.486 CurrentDesktop: Budgie:GNOME Date: Sun Oct 8 16:27:29 2023 LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 (20231008.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.5.0-7-generic N/A linux-backports-modules-6.5.0-7-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038765/+attachment/5707866/+files/syslog -- 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/2038765 Title: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash Status in linux package in Ubuntu: New Bug description: df: /sys/firmware/efi/efivars: Invalid argument appears on first display of the installer - I note that at the end of the installation curtin fails due to an efivars error - looking at syslog I saw various efivars errors so I'm filing this with the kernel since this is the first instance. i.e. running grep efivars /var/log/* ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber /dev/snd/seq:ubuntu-budgie 2074 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.486 CurrentDesktop: Budgie:GNOME Date: Sun Oct 8 16:27:29 2023 LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 (20231008.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.5.0-7-generic N/A linux-backports-modules-6.5.0-7-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D9.B00.1802021100 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038765/+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 2038765] [NEW] df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
Public bug reported: df: /sys/firmware/efi/efivars: Invalid argument appears on first display of the installer - I note that at the end of the installation curtin fails due to an efivars error - looking at syslog I saw various efivars errors so I'm filing this with the kernel since this is the first instance. i.e. running grep efivars /var/log/* ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber /dev/snd/seq:ubuntu-budgie 2074 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.486 CurrentDesktop: Budgie:GNOME Date: Sun Oct 8 16:27:29 2023 LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 (20231008.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.5.0-7-generic N/A linux-backports-modules-6.5.0-7-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D9.B00.1802021100 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- 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/2038765 Title: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash Status in linux package in Ubuntu: New Bug description: df: /sys/firmware/efi/efivars: Invalid argument appears on first display of the installer - I note that at the end of the installation curtin fails due to an efivars error - looking at syslog I saw various efivars errors so I'm filing this with the kernel since this is the first instance. i.e. running grep efivars /var/log/* ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber /dev/snd/seq:ubuntu-budgie 2074 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.486 CurrentDesktop: Budgie:GNOME Date: Sun Oct 8 16:27:29 2023 LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 (20231008.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.5.0-7-generic N/A linux-backports-modules-6.5.0-7-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D9.B00.1802021100 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: Mac
[Kernel-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
Re secureboot In my case my macbook air was not secure boot enabled but with the same no wireless observation -- 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/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2013236] Re: Failed to install bcmwl wireless driver during the install
ubuntu-drivers install just returns "All the available drivers are already installed" Looking at Additional Drivers it does however offer "Using dkms source for the Broadcom STA Wireless driver from broadcom-sta-dkms I can enable that successfully from the live session but wireless networks are not available in network manager No errors displayed when enabling from software-properties-gtk via the terminal Note - in 20.04.6 enabling via the software properties dialog does enable correctly with wireless networks in network manager -- 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/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2013236] Re: Failed to install bcmwl wireless driver during the install
** Attachment added: "20.04.6 partman" https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+attachment/5658761/+files/partman -- 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/2013236 Title: Failed to install bcmwl wireless driver during the install Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2013236] Re: Failed to install bcmwl wireless driver during the install
attached are the syslog and partman from the recent 20.04.6 install Hardware drivers says Broadcom BCM4331 802.11a/b/g/ using the Broadcom 802.11 Linux STA wireless driver from bcmwl-kernel-source ** Changed in: broadcom-sta (Ubuntu) Status: Incomplete => New -- 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/2013236 Title: Failed to install bcmwl wireless driver during the install Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2013236] Re: Failed to install bcmwl wireless driver during the install
** Attachment added: "20.04.6 syslog" https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+attachment/5658760/+files/syslog -- 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/2013236 Title: Failed to install bcmwl wireless driver during the install Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 1899336] Re: Thinkpad T14s (AMD) external monitors on docking station no longer detected
Thx for the update. interesting to see it was indeed a kernel/firmware issue. I'll close this for now. Please do raise further issues that are potentially a kernel issue via ubuntu-bug linux ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: ubuntubudgie Status: New => Fix Released -- 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/1899336 Title: Thinkpad T14s (AMD) external monitors on docking station no longer detected Status in Ubuntu Budgie: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I run Ubuntu Budgie 20.04 on my Lenovo ThinkPad T14s with Ryzen 4750U processor together with the "Lenovo ThinkPad USB-C Dock (Gen 2)" (40AS0090EU). The docking station is connected via USB-C to the system, supplies it with power via USB Power Delivery and provides USB 3.1 Gen 2 (10 Gbit/s) connectivity (including an Ethernet controller and audio codec running over the USB data path), as well as support for two monitors via "DisplayPort alternate mode" of USB-C, so technically it will configure the four high-speed lanes of USB-C as one lane for SuperSpeed+ RX, one lane for SuperSpeed+ TX, and two lanes for DisplayPort 1.4, the latter of which the docking station will then demultiplex onto two full-size DisplayPort connectors like an MST hub. So far, external monitors have worked fine most of the time. However, for a couple of days now, I cannot get the system to detect the external monitors connected to my docking station anymore. The "BIOS" (EFI) boot screen (with the Lenovo logo) still shows up on the external monitors. However, both the LUKS/dm-crypt pre-boot- authentication screen (since I use full-disk-encryption) and also the desktop after login show up on the internal display, even with the laptop connected to the docking station, so it appears like the kernel no longer detects the monitors connecting via "DisplayPort alternate mode". Yesterday, I could get the monitors to show up by disconnecting the laptop from the docking station and reconnecting it again. Today, not even this appears to work. Sometimes the external monitors are detected (and shown as "enabled") in the display settings of Budgie, sometimes they do not even show up. Even when they show up and are enabled, nothing is displayed on them. The monitors say they do not receive a signal and I should check the connection. Unplugging and replugging the cables from the docking station to the monitors does not change anything. Audio, Ethernet and USB runs fine over the docking station, just DisplayPort does not. This is obviously very bad, since I now have to work on the internal display even with the laptop docked. I have the "amdgpu.exp_hw_support=1" in my kernel arguments (*) and the Ryzen 4000 GPU appears to be recognized. $ lspci -k 06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev d1) Subsystem: Lenovo Renoir Kernel driver in use: amdgpu Kernel modules: amdgpu $ (*) When I installed Ubuntu Budgie 20.04, I needed to add this in order to extend my desktop over the two external monitors. Without this argument, the system only showed a single display in the settings, the same content was displayed on all connected monitors (mirrored) and there was no way to change that. I have attached parts of "dmesg" output which I deem relevant. $ uname -a Linux thinkpad-t14s 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-27 (75 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20UH001AGE Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=UUID=5b605ccb-8a29-46ee-b571-e0d61a323457 ro quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET36W(1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001AGE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Informatio
[Kernel-packages] [Bug 1958318] Re: Desktop hangs - Status reg 3.
** Tags added: jammy -- 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/1958318 Title: Desktop hangs - Status reg 3. Status in linux package in Ubuntu: Incomplete Bug description: Kernel 5.15 causes Ubuntu tu budgie 22.04 live cd desktop to hang. Thinkpad t560 with SSD Errors are DMAR DRHD handling fault status reg 3 DMAR [DMA Write NO_PAID] Request dev fault add… [fault reason 0x05] PTE Write access is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958318/+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 1946368] Re: HDMI output freezes under current/proposed impish kernels
I have no idea why the status has changed ... the fix hasn't entered the archive yet. ** Changed in: linux-raspi (Ubuntu Impish) Status: Fix Released => Fix Committed -- 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/1946368 Title: HDMI output freezes under current/proposed impish kernels Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Impish: Fix Committed Bug description: [Impact] The UI of Impish desktop for raspi occasionally freezes which can be triggered by playing videos and moving windows around. Seems to happen more frequently when using higher resolutions and/or higher refresh rates (higher than 1920x1080@60Hz). Kernel errors are along the lines of: [ 513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co mmit wait timed out [ 513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_ done timed out [Test Case] Install current Impish desktop for raspi on a Pi 4. Use a high- refresh/resolution monitor. Play videos, move windows around. [Fix] The Pi foundation identified a couple of upstream vc4 commits that seem to interfere with their downstream patches. Revert those to match the Pi foundations currently released 5.10 kernel. [Where Problems Could Occur] The changes are confined to the vc4 driver, so problems would only show up if that driver is in use. Which is only the case for the Ubuntu raspi desktop image, so server images should not be impacted at all. [Original Description] Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels for the Ubuntu Pi pre-installed desktop impish release, the HDMI output occasionally freezes. A known workaround at this time is to change the following line in /boot/firmware/config.txt: dtoverlay=vc4-kms-v3d To the following: dtoverlay=vc4-fkms-v3d In other words, to use the "fake" KMS overlay (fkms) instead of the "full" KMS overlay (kms). I've been unable to determine a reliable method of guaranteeing a freeze, but it appears to occur much more readily when video playback is occurring, and when other interactions (especially moving windows around, minimizing, restoring) occurs simultaneously. Display suspend also periodically causes the same hang, which made me suspect this might be related to #1944397 but it appears that had a separate cause (now resolved). The following dmesg outputs have been observed immediately after the display hang; this one from 1007.8: [ 513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co mmit wait timed out [ 513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_ done timed out [ 524.002211] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 524.002404] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:205:plane-25 ] commit wait timed out [ 534.242499] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 534.242657] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit [ 534.250685] [ cut here ] [ 534.250701] refcount_t: underflow; use-after-free. [ 534.250735] WARNING: CPU: 1 PID: 120 at lib/refcount.c:87 refcount_dec_not_one+0xa0/0xbc [ 534.250758] Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg hci_uart btqca btrtl btbcm btintel bnep snd_soc_hdmi_codec vc4 btsdio snd_soc_core input_leds bluetooth snd_compress snd_bcm2835(C) snd_pcm_dmaengine ecdh_generic ecc snd_pcm brcmfmac snd_seq_midi snd_seq_midi_event bcm2835_codec(C) bcm 2835_isp(C) bcm2835_v4l2(C) brcmutil snd_rawmidi v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_seq videobuf2_common videodev snd_seq_devi ce mc snd_timer vc_sm_cma(C) raspberrypi_hwmon snd bcm2835_gpiomem rpivid_mem uio_pdrv_genirq uio sch_fq_ codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon zstd_compress hid_generic usbhid raid 6_pq libcrc32c dm_mirror dm_region_hash dm_log spidev dwc2 v3d roles udc_core gpu_sched crct10dif_ce i2c_ brcmstb i2c_bcm2835 spi_bcm2835 drm_kms_helper syscopyarea xhci_pci xhci_pci_renesas sysfillrect sysimgbl t fb_sys_fops cec drm phy_generic ac97_bus aes_arm64 [ 534.251066] CPU: 1 PID: 120 Comm: kworker/1:2 Tainted: GWC 5.13.0-1007-raspi #8-Ubuntu [ 534.251076] Hardware name: Raspberry Pi 400 Rev 1.1 (DT) [ 534.251083] Workqueue: events drm_mode_rmfb_work_fn [drm] [ 534.251239] p
[Kernel-packages] [Bug 1947472] Re: Medion Akoya S15449: Touchpad key missing
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntubudgie -- 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/1947472 Title: Medion Akoya S15449: Touchpad key missing Status in linux package in Ubuntu: New Bug description: Hardware: Medion Akoya S15449 Ubuntu Budgie 21.10 budgie-desktop 10.5.3 Kernel: 5.13.0-19-generic The right "mouse button" of the touchpad is not working. It works in Windows. It works with the same Ubuntu Budgie version running in a VirtualBox. It works with an external mouse connected via USB. But it does not work on a stand-alone Ubuntu Budgie 21.10 with the built-in touchpad. I suspect this bug is related to a known kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213031 because with previous kernel versions both touchpad and keykoard didn't work at all with any Linux on the Medion Akoya S15449. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947472/+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 1915909] Re: vc4-kms-v3d and vc4-kms-v3d-pi4 should be mapped in build
*** This bug is a duplicate of bug 1918110 *** https://bugs.launchpad.net/bugs/1918110 ** This bug has been marked a duplicate of bug 1918110 overlay_map.dtb is in wrong location -- 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/1915909 Title: vc4-kms-v3d and vc4-kms-v3d-pi4 should be mapped in build Status in linux-raspi package in Ubuntu: New Bug description: This is really just raising this raspi upstream github issue to track when the Canonical raspi kernel maps the two overlays correctly. If it already has been done in the focal and groovy linux-raspi updates then I apologise for the noise - please close. https://github.com/raspberrypi/linux/issues/4080 Phil Ellwell stated "I can see how the problem might have arisen - a build rule that says .dtbo files go into overlays and .dtb files don't, for example - but Canonical are now aware of the problem and it should be fixed in future releases. " (https://github.com/raspberrypi/linux/issues/4080#issuecomment-762709027) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1915909/+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 1922350] [NEW] missing amdgpu firmware reported when updating
Public bug reported: I'm seeing the following: update-initramfs: Generating /boot/initrd.img-5.11.0-13-generic W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_toc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_dmcub.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_dmcub.bin for module amdgpu Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for cups (2.3.3op2-3ubuntu3) ... Processing triggers for gnome-menus (3.36.0-1ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.67.5-2) ... Processing triggers for libc-bin (2.33-0ubuntu4) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for dbus (1.12.20-1ubuntu3) ... ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-11-generic 5.11.0-11.12 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dad2584 F pulseaudio /dev/snd/controlC0: dad2584 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Fri Apr 2 12:27:30 2021 InstallationDate: Installed on 2021-02-08 (52 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210208) MachineType: TUXEDO TUXEDO Pulse 15 Gen1 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic root=UUID=dca66736-5282-45e6-a144-59d3339a8d0f ro quiet splash RebootRequiredPkgs: network-manager RelatedPackageVersions: linux-restricted-modules-5.11.0-11-generic N/A linux-backports-modules-5.11.0-11-generic N/A linux-firmware 1.196 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PULSE1501 dmi.board.vendor: TUXEDO
[Kernel-packages] [Bug 1918013] [NEW] package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi, 3-model-b.txt lib/firmware/brcm
Public bug reported: Upgrade error Unpacking linux-firmware (1.195) over (1.194) ... dpkg: error processing archive /tmp/apt-dpkg-install-N6i2Cp/86-linux-firmware_1. 195_all.deb (--unpack): trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 update-initramfs: Generating /boot/initrd.img-5.8.0-1017-raspi ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] ProcVersionSignature: Ubuntu 5.8.0-1017.20+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu59 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dad1239 F pulseaudio /dev/snd/pcmC1D0p: dad1239 F...m pulseaudio /dev/snd/controlC0: dad1239 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Mar 6 14:59:23 2021 Dependencies: ErrorMessage: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 ImageMediaBuild: 20210302 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1280x1024M@60 smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware StagingDrivers: bcm2835_v4l2 bcm2835_isp bcm2835_codec bcm2835_mmal_vchiq snd_bcm2835 vc_sm_cma Title: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed to install/upgrade: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 hirsute staging -- 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/1918013 Title: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed to install/upgrade: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 Status in linux-firmware package in Ubuntu: New Bug description: Upgrade error Unpacking linux-firmware (1.195) over (1.194) ... dpkg: error processing archive /tmp/apt-dpkg-install-N6i2Cp/86-linux-firmware_1. 195_all.deb (--unpack): trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 update-initramfs: Generating /boot/initrd.img-5.8.0-1017-raspi ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] ProcVersionSignature: Ubuntu 5.8.0-1017.20+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu59 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dad1239 F pulseaudio /dev/snd/pcmC1D0p: dad1239 F...m pulseaudio /dev/snd/controlC0: dad1239 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Mar 6 14:59:23 2021 Dependencies: ErrorMessage: trying to overwrite '/li
[Kernel-packages] [Bug 1915909] [NEW] vc4-kms-v3d and vc4-kms-v3d-pi4 should be mapped in build
Public bug reported: This is really just raising this raspi upstream github issue to track when the Canonical raspi kernel maps the two overlays correctly. If it already has been done in the focal and groovy linux-raspi updates then I apologise for the noise - please close. https://github.com/raspberrypi/linux/issues/4080 Phil Ellwell stated "I can see how the problem might have arisen - a build rule that says .dtbo files go into overlays and .dtb files don't, for example - but Canonical are now aware of the problem and it should be fixed in future releases. " (https://github.com/raspberrypi/linux/issues/4080#issuecomment-762709027) ** Affects: linux-raspi (Ubuntu) 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/1915909 Title: vc4-kms-v3d and vc4-kms-v3d-pi4 should be mapped in build Status in linux-raspi package in Ubuntu: New Bug description: This is really just raising this raspi upstream github issue to track when the Canonical raspi kernel maps the two overlays correctly. If it already has been done in the focal and groovy linux-raspi updates then I apologise for the noise - please close. https://github.com/raspberrypi/linux/issues/4080 Phil Ellwell stated "I can see how the problem might have arisen - a build rule that says .dtbo files go into overlays and .dtb files don't, for example - but Canonical are now aware of the problem and it should be fixed in future releases. " (https://github.com/raspberrypi/linux/issues/4080#issuecomment-762709027) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1915909/+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 1899678] Re: No wifi after installation - does not work with secure boot enabled
Ok. It's been a long weekend after the release... I dont see and lines on the sed output that match the modinfo wl. Double checking dmesg the last lines say Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 As a confirmation that the iso install was ok I reinstalled both with legacy mode and efi with non secure boot enabled and both times the bcmwl wifi was ok after installation and lockdown. So I dont really understand why ubiquity didn't sign the wl module. -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) 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/1899678/+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
Re: [Kernel-packages] [Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)
I can confirm that sound is no longer muted for the ISO and is not muted on installation. So thanks and congrats! On Thu, 22 Oct 2020, 14:30 Launchpad Bug Tracker, < 1897...@bugs.launchpad.net> wrote: > This bug was fixed in the package alsa-lib - 1.2.3.2-1ubuntu3 > > --- > alsa-lib (1.2.3.2-1ubuntu3) groovy; urgency=medium > > * d/p/0001-ucm-add-a-check-for-the-empty-configuration.patch > - Fix the failure on init the HDA-Intel sound card, because there > is no init mixer values in the ucm, the alsa-lib should return > error and then let alsautils init this sound card in the legacy > HDA way. (LP: #1897934) > > -- Hui Wang Thu, 22 Oct 2020 16:46:14 +0800 > > ** Changed in: alsa-lib (Ubuntu Groovy) >Status: Fix Committed => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1897934 > > Title: > [SRU][Intel HDA] The initial sound level is set to zero (muted) > > Status in Release Notes for Ubuntu: > New > Status in alsa-lib package in Ubuntu: > Fix Released > Status in alsa-lib source package in Focal: > Fix Committed > Status in alsa-lib source package in Groovy: > Fix Released > > Bug description: > [Impact] > Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this > results in the failure on setting the init mixer values for HDA sound > card, and users experience the mute of audio after installing the > 20.10. > > [Fix] > Backport a patch from the latest alsa-lib (v1.2.3+) > > [Test] > Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm > /var/lib/alsa/*; > sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is > muted. > > Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm > /var/lib/alsa/*; > sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is > not muted. > > [Regression Potential] > This could make the ucm audio fail to initialize, but this possibility is > very low, since this patch is from upstream, and I tested on a ucm based > machine, the audio is good. > > > On boot into the live session - or on first install the sound level is > muted. > > I have to use GNOME Control Center - Sounds to change to an > appropriate level. Once changed the level chosen is correctly > retained between reboots. > > This appears to be a regression from 20.04 where the sound level was > set to - I guess - 80% on the live-session/first install > > ProblemType: BugDistroRelease: Ubuntu 20.10 > Package: pulseaudio 1:13.99.1-1ubuntu11 > ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 > Uname: Linux 5.8.0-20-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu48 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio > CasperMD5CheckResult: pass > CasperVersion: 1.452 > CurrentDesktop: Budgie:GNOME > Date: Wed Sep 30 16:03:08 2020 > LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 > (20200930) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bashSourcePackage: pulseaudio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 02/15/2016 > dmi.bios.release: 15.31 > dmi.bios.vendor: Insyde > dmi.bios.version: F.1F > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 80BF > dmi.board.vendor: HP > dmi.board.version: 95.16 > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.ec.firmware.release: 95.22 > dmi.modalias: > dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: > dmi.product.family: 103C_5335KV G=N L=CON B=HP > dmi.product.name: HP Notebook > dmi.product.sku: N9S73EA#ABU > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this results in the failure on setting the init mixer values for HDA sound card, and users experience the mute of audio after installing the 20.10. [Fix] Backport a patch from the latest alsa-l
[Kernel-packages] [Bug 1899678] Re: No wifi after installation - does not work with secure boot enabled
The full terminal session is in modprobe.txt but in summary the bcmwl- kernel-source reinstall was simply: apt --reinstall install bcmwl-kernel-source This is a full ISO installation - no extra packages added/nor removed modinfo wl returns a sig_key signature The output of the mokutil sed is dad@dad-HP-Notebook:~$ mokutil --list-enrolled | sed -n -e'/X509v3 Subject Key Identifier:/,/X509v3 Authority Key Identifier:/ { /:..:/p; }' 7F:BE:DE:09:14:7B:0F:BF:30:0C:8E:50:5C:FF:5F:CE:A2:01:95:67 BD:AA:86:36:DB:8B:F4:C4:86:12:E4:98:B7:36:03:9E:CD:CB:21:E5 E8:19:BC:A5:04:AC:51:A2:BC:51:A1:FC:E2:25:FD:69:3F:A6:E6:76 DF:3B:45:81:83:E2:CD:8F:7E:62:D7:F6:01:6C:76:5A:52:E4:ED:47 E7:BA:5F:11:7D:D8:E2:A9:D1:48:57:C1:31:2F:2C:78:99:14:B2:B0 6F:39:87:A1:71:09:A1:F9:6F:81:79:E5:31:5C:0B:24:0A:08:60:05 2F:08:F0:19:48:E3:1B:19:3E:7A:35:22:A4:48:33:B5:D8:EE:44:B8 A0:1E:E8:4E:9B:37:AC:E4:07:96:1C:C4:68:C5:90:94:47:87:84:69 AD:91:99:0B:C2:2A:B1:F5:17:04:8C:23:B6:65:5A:26:8E:34:5A:63 dad@dad-HP-Notebook:~$ -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) 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/1899678/+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
Re: [Kernel-packages] [Bug 1899678] Re: No wifi after installation - does not work with secure boot enabled
To clarify - the modprobe was not a live-session - this was after a full disk install. So - I MOK enrolled after the ubiquity install - no wifi on first logon. Modprobe wl gave the not permitted error. I then manually connected and force a reinstall of bcmwl-kernel-source and subsequently on boot another MOK enroll was requested. It was only then that Wifi was available. On Wed, 21 Oct 2020 at 22:30, Steve Langasek <1899...@bugs.launchpad.net> wrote: > > If you are trying to do the modprobe during the live session, it is > expected that this will not succeed. It's only after MOK enrollment > that these locally-signed modules will be allowed to be loaded by the > kernel under SecureBoot. > > If the modprobe works post-reboot and post-MOK-enrollment, then this is > working as required and I believe we can close the bug report. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1899678 > > Title: > No wifi after installation - does not work with secure boot enabled > > Status in bcmwl package in Ubuntu: > New > Status in dkms package in Ubuntu: > New > Status in shim-signed package in Ubuntu: > New > Status in ubiquity package in Ubuntu: > New > > Bug description: > After installation I noted that my broadcom wifi was not available. > This is a regression from 20.04 where installation automatically > installed the broadcom driver. > > So I tried to force the installation again - see trace below. > > The dialog message to enter the secure password appeared - however on > reboot a confirmation to change the MOK state was not seen - the > distro booted straight in. > > sudo apt install --reinstall bcmwl-kernel-source > [sudo] password for dad: > Reading package lists... Done > Building dependency tree > Reading state information... Done > 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to > upgrade. > Need to get 1,546 kB of archives. > After this operation, 0 B of additional disk space will be used. > Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 > bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] > Fetched 1,546 kB in 0s (5,232 kB/s) > (Reading database ... 202371 files and directories currently installed.) > Preparing to unpack > .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... > Removing all DKMS Modules > Done. > Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over > (6.30.223.271+bdcom-0ubuntu7) ... > Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... > Loading new bcmwl-6.30.223.271+bdcom DKMS files... > Building for 5.8.0-22-generic > Building for architecture x86_64 > Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ > > depmod > > DKMS: install completed. > modprobe: ERROR: could not insert 'wl': Operation not permitted > update-initramfs: deferring update (trigger activated) > Processing triggers for initramfs-tools (0.137ubuntu12) ... > update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 > ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 > Uname: Linux 5.8.0-22-generic x86_64 > ApportVersion: 2.20.11-0ubuntu49 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: Budgie:GNOME > Date: Tue Oct 13 18:32:47 2020 > InstallationDate: Installed on 2020-10-13 (0 days ago) > InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 > (20201013) > 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/1899678/+subscriptions -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password fo
[Kernel-packages] [Bug 1899678] Re: No wifi after installation - does not work with secure boot enabled
ok - just done a fresh entire disk install whilst testing the .2 ISO. See attached modprobe.txt (for the modprobe - I think you meant 'wl' so I did that as well.) I followed up by connecting to the network (RJ45) and reinstalling bcmwl-kernel-source I saw the same wl message as per modprobe. On reboot - I was prompted for the MOK key - so enrolled that. After reboot and login, the wifi networks are now available. So that's a little different now from the initial report - I'm guessing shim-signed as improved matters - but not whilst installing. ** Attachment added: "modprobe.txt" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5425218/+files/modprobe.txt -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) 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/1899678/+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 1899678] Re: No wifi after installation - does not work with secure boot enabled
** Attachment added: "software-properties-gtk.png" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5425197/+files/software-properties-gtk.png -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) 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/1899678/+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 1899678] Re: No wifi after installation - does not work with secure boot enabled
oddly I don't see anything - see dmesg.txt However software-properties-gtk says its in use (see software- properties-gtk.png) ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5425196/+files/dmesg.txt -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) 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/1899678/+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 1899678] Re: No wifi after installation - does not work with secure boot enabled
** Attachment added: "mok2.txt" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5425158/+files/mok2.txt -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) 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/1899678/+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 1899678] Re: No wifi after installation - does not work with secure boot enabled
'fraid shim-signed with the new 20201021 ISO doesn't do the trick. I've also tried to delete all the existing mok keys and do a clean install so boot and use the "Install Ubuntu Budgie" option. Chose UK and London. Selected 3rd party checkbox and entered "password" twice for the secure password After rebooting - the MOK enrollment came up - so i chose the option to enrol the key and entered "password" when prompted. I've collected the /var/log/installer logs and the latest mok logs as above. See the v2 logs attached. ** Attachment added: "installationlogs2.tar" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5425157/+files/installationlogs2.tar -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) 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/1899678/+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
Re: [Kernel-packages] [Bug 1899678] Re: No wifi after installation - does not work with secure boot enabled
Just to say - after installation - I was prompted on reboot to enter my MOK password. So entering the password was accepted and then an auto-boot took me to the normal login manager - and subsequent login. On Wed, 21 Oct 2020 at 13:05, David Mohammed wrote: > > Correct - I ticked the third party checkbox - I needed to-do that so > that I could then enter the secure boot password. > > On Wed, 21 Oct 2020 at 12:40, Iain Lane <1899...@bugs.launchpad.net> wrote: > > > > I think the second part (apt install not showing the prompt on next > > boot) is fixed with shim-signed 1.45 as indicated by Andy in comment #8. > > > > But I'm not quite sure about your initial part where the installer > > didn't do the same. I can make that happen if I tick to install > > proprietary drivers and then untick "Configure secure boot". But that's > > to be expected. If I tick both and fill in a passphrase, then it works > > correctly and I'm prompted to enroll the key after completing the > > installation and rebooting. > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1899678 > > > > Title: > > No wifi after installation - does not work with secure boot enabled > > > > Status in bcmwl package in Ubuntu: > > New > > Status in dkms package in Ubuntu: > > New > > Status in shim-signed package in Ubuntu: > > New > > Status in ubiquity package in Ubuntu: > > New > > > > Bug description: > > After installation I noted that my broadcom wifi was not available. > > This is a regression from 20.04 where installation automatically > > installed the broadcom driver. > > > > So I tried to force the installation again - see trace below. > > > > The dialog message to enter the secure password appeared - however on > > reboot a confirmation to change the MOK state was not seen - the > > distro booted straight in. > > > > sudo apt install --reinstall bcmwl-kernel-source > > [sudo] password for dad: > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to > > upgrade. > > Need to get 1,546 kB of archives. > > After this operation, 0 B of additional disk space will be used. > > Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 > > bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] > > Fetched 1,546 kB in 0s (5,232 kB/s) > > (Reading database ... 202371 files and directories currently installed.) > > Preparing to unpack > > .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... > > Removing all DKMS Modules > > Done. > > Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over > > (6.30.223.271+bdcom-0ubuntu7) ... > > Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... > > Loading new bcmwl-6.30.223.271+bdcom DKMS files... > > Building for 5.8.0-22-generic > > Building for architecture x86_64 > > Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ > > > > depmod > > > > DKMS: install completed. > > modprobe: ERROR: could not insert 'wl': Operation not permitted > > update-initramfs: deferring update (trigger activated) > > Processing triggers for initramfs-tools (0.137ubuntu12) ... > > update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic > > > > ProblemType: Bug > > DistroRelease: Ubuntu 20.10 > > Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 > > ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 > > Uname: Linux 5.8.0-22-generic x86_64 > > ApportVersion: 2.20.11-0ubuntu49 > > Architecture: amd64 > > CasperMD5CheckResult: skip > > CurrentDesktop: Budgie:GNOME > > Date: Tue Oct 13 18:32:47 2020 > > InstallationDate: Installed on 2020-10-13 (0 days ago) > > InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 > > (20201013) > > 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/1899678/+subscriptions -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automa
Re: [Kernel-packages] [Bug 1899678] Re: No wifi after installation - does not work with secure boot enabled
Correct - I ticked the third party checkbox - I needed to-do that so that I could then enter the secure boot password. On Wed, 21 Oct 2020 at 12:40, Iain Lane <1899...@bugs.launchpad.net> wrote: > > I think the second part (apt install not showing the prompt on next > boot) is fixed with shim-signed 1.45 as indicated by Andy in comment #8. > > But I'm not quite sure about your initial part where the installer > didn't do the same. I can make that happen if I tick to install > proprietary drivers and then untick "Configure secure boot". But that's > to be expected. If I tick both and fill in a passphrase, then it works > correctly and I'm prompted to enroll the key after completing the > installation and rebooting. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1899678 > > Title: > No wifi after installation - does not work with secure boot enabled > > Status in bcmwl package in Ubuntu: > New > Status in dkms package in Ubuntu: > New > Status in shim-signed package in Ubuntu: > New > Status in ubiquity package in Ubuntu: > New > > Bug description: > After installation I noted that my broadcom wifi was not available. > This is a regression from 20.04 where installation automatically > installed the broadcom driver. > > So I tried to force the installation again - see trace below. > > The dialog message to enter the secure password appeared - however on > reboot a confirmation to change the MOK state was not seen - the > distro booted straight in. > > sudo apt install --reinstall bcmwl-kernel-source > [sudo] password for dad: > Reading package lists... Done > Building dependency tree > Reading state information... Done > 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to > upgrade. > Need to get 1,546 kB of archives. > After this operation, 0 B of additional disk space will be used. > Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 > bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] > Fetched 1,546 kB in 0s (5,232 kB/s) > (Reading database ... 202371 files and directories currently installed.) > Preparing to unpack > .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... > Removing all DKMS Modules > Done. > Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over > (6.30.223.271+bdcom-0ubuntu7) ... > Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... > Loading new bcmwl-6.30.223.271+bdcom DKMS files... > Building for 5.8.0-22-generic > Building for architecture x86_64 > Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ > > depmod > > DKMS: install completed. > modprobe: ERROR: could not insert 'wl': Operation not permitted > update-initramfs: deferring update (trigger activated) > Processing triggers for initramfs-tools (0.137ubuntu12) ... > update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 > ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 > Uname: Linux 5.8.0-22-generic x86_64 > ApportVersion: 2.20.11-0ubuntu49 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: Budgie:GNOME > Date: Tue Oct 13 18:32:47 2020 > InstallationDate: Installed on 2020-10-13 (0 days ago) > InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 > (20201013) > 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/1899678/+subscriptions -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to u
[Kernel-packages] [Bug 1899678] Re: No wifi after installation - does not work with secure boot enabled
Hi Dimitri, the last time I tested secure boot installation was at 20.04 on this particular laptop. All was ok at that time. enc are the installer tarball and the mok results. TIA ** Attachment added: "installation.tar" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5424744/+files/installation.tar -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) 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/1899678/+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 1899678] Re: No wifi after installation - does not work with secure boot enabled
** Attachment added: "mok.txt" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5424745/+files/mok.txt -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) 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/1899678/+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 1899678] Re: No wifi after installation: could not insert 'wl': operation not permitted
Disabling secure boot allows network-manager to display the wifi connections. Installing WITHOUT secure boot also allows network-manager to display the wifi connections. So currently bcmwl-kernel-source will only work with non-secure boot ** Summary changed: - No wifi after installation: could not insert 'wl': operation not permitted + No wifi after installation - does not work with secure boot enabled -- 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/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) 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/1899678/+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 1899678] [NEW] No wifi after installation: could not insert 'wl': operation not permitted
Public bug reported: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1899678 Title: No wifi after installation: could not insert 'wl': operation not permitted Status in bcmwl package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-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-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.2
[Kernel-packages] [Bug 1899336] Re: Thinkpad T14s (AMD) external monitors on docking station no longer detected
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1899336 Title: Thinkpad T14s (AMD) external monitors on docking station no longer detected Status in Ubuntu Budgie: New Status in linux package in Ubuntu: New Bug description: I run Ubuntu Budgie 20.04 on my Lenovo ThinkPad T14s with Ryzen 4750U processor together with the "Lenovo ThinkPad USB-C Dock (Gen 2)" (40AS0090EU). The docking station is connected via USB-C to the system, supplies it with power via USB Power Delivery and provides USB 3.1 Gen 2 (10 Gbit/s) connectivity (including an Ethernet controller and audio codec running over the USB data path), as well as support for two monitors via "DisplayPort alternate mode" of USB-C, so technically it will configure the four high-speed lanes of USB-C as one lane for SuperSpeed+ RX, one lane for SuperSpeed+ TX, and two lanes for DisplayPort 1.4, the latter of which the docking station will then demultiplex onto two full-size DisplayPort connectors like an MST hub. So far, external monitors have worked fine most of the time. However, for a couple of days now, I cannot get the system to detect the external monitors connected to my docking station anymore. The "BIOS" (EFI) boot screen (with the Lenovo logo) still shows up on the external monitors. However, both the LUKS/dm-crypt pre-boot- authentication screen (since I use full-disk-encryption) and also the desktop after login show up on the internal display, even with the laptop connected to the docking station, so it appears like the kernel no longer detects the monitors connecting via "DisplayPort alternate mode". Yesterday, I could get the monitors to show up by disconnecting the laptop from the docking station and reconnecting it again. Today, not even this appears to work. Sometimes the external monitors are detected (and shown as "enabled") in the display settings of Budgie, sometimes they do not even show up. Even when they show up and are enabled, nothing is displayed on them. The monitors say they do not receive a signal and I should check the connection. Unplugging and replugging the cables from the docking station to the monitors does not change anything. Audio, Ethernet and USB runs fine over the docking station, just DisplayPort does not. This is obviously very bad, since I now have to work on the internal display even with the laptop docked. I have the "amdgpu.exp_hw_support=1" in my kernel arguments (*) and the Ryzen 4000 GPU appears to be recognized. $ lspci -k 06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev d1) Subsystem: Lenovo Renoir Kernel driver in use: amdgpu Kernel modules: amdgpu $ (*) When I installed Ubuntu Budgie 20.04, I needed to add this in order to extend my desktop over the two external monitors. Without this argument, the system only showed a single display in the settings, the same content was displayed on all connected monitors (mirrored) and there was no way to change that. I have attached parts of "dmesg" output which I deem relevant. $ uname -a Linux thinkpad-t14s 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-27 (75 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20UH001AGE Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=UUID=5b605ccb-8a29-46ee-b571-e0d61a323457 ro quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET36W(1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001AGE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR1CET36W(1.05):bd06/11/2020:svnLENOVO:pn20UH001AGE:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001AGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1
[Kernel-packages] [Bug 1899336] Re: Thinkpad T14s (AMD) external monitors on docking station no longer detected
** 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/1899336 Title: Thinkpad T14s (AMD) external monitors on docking station no longer detected Status in Ubuntu Budgie: New Status in linux package in Ubuntu: New Bug description: I run Ubuntu Budgie 20.04 on my Lenovo ThinkPad T14s with Ryzen 4750U processor together with the "Lenovo ThinkPad USB-C Dock (Gen 2)" (40AS0090EU). The docking station is connected via USB-C to the system, supplies it with power via USB Power Delivery and provides USB 3.1 Gen 2 (10 Gbit/s) connectivity (including an Ethernet controller and audio codec running over the USB data path), as well as support for two monitors via "DisplayPort alternate mode" of USB-C, so technically it will configure the four high-speed lanes of USB-C as one lane for SuperSpeed+ RX, one lane for SuperSpeed+ TX, and two lanes for DisplayPort 1.4, the latter of which the docking station will then demultiplex onto two full-size DisplayPort connectors like an MST hub. So far, external monitors have worked fine most of the time. However, for a couple of days now, I cannot get the system to detect the external monitors connected to my docking station anymore. The "BIOS" (EFI) boot screen (with the Lenovo logo) still shows up on the external monitors. However, both the LUKS/dm-crypt pre-boot- authentication screen (since I use full-disk-encryption) and also the desktop after login show up on the internal display, even with the laptop connected to the docking station, so it appears like the kernel no longer detects the monitors connecting via "DisplayPort alternate mode". Yesterday, I could get the monitors to show up by disconnecting the laptop from the docking station and reconnecting it again. Today, not even this appears to work. Sometimes the external monitors are detected (and shown as "enabled") in the display settings of Budgie, sometimes they do not even show up. Even when they show up and are enabled, nothing is displyed on them. The monitors say they do not receive a signal and I should check the connection. Unplugging and replugging the cables from the docking station to the monitors does not change anything. Audio, Ethernet and USB runs fine over the docking station, just DisplayPort does not. This is obviously very bad, since I now have to work on the internal display even with the laptop docked. I have the "amdgpu.exp_hw_support=1" in my kernel arguments (*) and the Ryzen 4000 GPU appears to be recognized. $ lspci -k 06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev d1) Subsystem: Lenovo Renoir Kernel driver in use: amdgpu Kernel modules: amdgpu $ (*) When I installed Ubuntu Budgie 20.04, I needed to add this in order to extend my desktop over the two external monitors. Without this argument, the system only showed a single display in the settings, the same content was displayed on all connected monitors (mirrored) and there was no way to change that. I have attached parts of "dmesg" output which I deem relevant. $ uname -a Linux thinkpad-t14s 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1899336/+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 1843115] Re: Ubiquity crashes when trying to install 19.10 - no wifi - "device not managed"
** Tags removed: disco ** Tags added: eoan ** Description changed: Trying to install 19.10 on a HP ENVY 15-dr0350nd with Intel® Wireless-AC 9560 802.11b/g/n/ac (2x2) Wi-Fi, Ubiquity crashes. Obviously, I cannot send it from 19.10 due to no wifi/no network. Adding these relevant - links: https://bugzilla.redhat.com/show_bug.cgi?id=1733369 and + links I.e. eoaj firmware I think needs updating for kernel 5.2: + https://bugzilla.redhat.com/show_bug.cgi?id=1733369 and https://bugzilla.kernel.org/show_bug.cgi?id=204167. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-firmware 1.178.3 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Sep 7 10:32:47 2019 Dependencies: InstallationDate: Installed on 2019-06-18 (81 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Trying to install 19.10 on a HP ENVY 15-dr0350nd with Intel® Wireless-AC 9560 802.11b/g/n/ac (2x2) Wi-Fi, Ubiquity crashes. Obviously, I cannot send it from 19.10 due to no wifi/no network. Adding these relevant - links I.e. eoaj firmware I think needs updating for kernel 5.2: + links I.e. eoan firmware I think needs updating for kernel 5.2: https://bugzilla.redhat.com/show_bug.cgi?id=1733369 and https://bugzilla.kernel.org/show_bug.cgi?id=204167. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-firmware 1.178.3 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Sep 7 10:32:47 2019 Dependencies: InstallationDate: Installed on 2019-06-18 (81 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1843115 Title: Ubiquity crashes when trying to install 19.10 - no wifi - "device not managed" Status in linux-firmware package in Ubuntu: New Bug description: Trying to install 19.10 on a HP ENVY 15-dr0350nd with Intel® Wireless- AC 9560 802.11b/g/n/ac (2x2) Wi-Fi, Ubiquity crashes. Obviously, I cannot send it from 19.10 due to no wifi/no network. Adding these relevant links I.e. eoan firmware I think needs updating for kernel 5.2: https://bugzilla.redhat.com/show_bug.cgi?id=1733369 and https://bugzilla.kernel.org/show_bug.cgi?id=204167. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-firmware 1.178.3 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Sep 7 10:32:47 2019 Dependencies: InstallationDate: Installed on 2019-06-18 (81 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1843115/+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 1826749] Re: laptop with Ubuntu Budgie crashed after recent update of Kernel
Looks like this should have been filed against the linux kernel from your description. Please run in a terminal the following to collate the correct logs for the linux package: apport-collect 1826749 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid ** 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/1826749 Title: laptop with Ubuntu Budgie crashed after recent update of Kernel Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: It works if I enter grub by pressing shift key during start up and choose the earlier Kernel. Description: Ubuntu 18.04.2 LTS Release: 18.04 Package files: 100 /var/lib/dpkg/status release a=now 500 https://deb.opera.com/opera-stable stable/non-free i386 Packages release o=Opera Software AS,a=stable,n=stable,l=The Opera web browser,c=non-free,b=i386 origin deb.opera.com 500 https://deb.opera.com/opera-stable stable/non-free amd64 Packages release o=Opera Software AS,a=stable,n=stable,l=The Opera web browser,c=non-free,b=amd64 origin deb.opera.com 500 http://archive.ubuntu.com/ubuntu bionic-security/multiverse i386 Packages release v=18.04,o=Ubuntu,a=bionic-security,n=bionic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu bionic-security/universe i386 Packages release v=18.04,o=Ubuntu,a=bionic-security,n=bionic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu bionic-security/restricted i386 Packages release v=18.04,o=Ubuntu,a=bionic-security,n=bionic,l=Ubuntu,c=restricted,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu bionic-security/main i386 Packages release v=18.04,o=Ubuntu,a=bionic-security,n=bionic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com 100 http://archive.ubuntu.com/ubuntu bionic-backports/universe i386 Packages release v=18.04,o=Ubuntu,a=bionic-backports,n=bionic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 100 http://archive.ubuntu.com/ubuntu bionic-backports/main i386 Packages release v=18.04,o=Ubuntu,a=bionic-backports,n=bionic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse i386 Packages release v=18.04,o=Ubuntu,a=bionic-updates,n=bionic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages release v=18.04,o=Ubuntu,a=bionic-updates,n=bionic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu bionic-updates/restricted i386 Packages release v=18.04,o=Ubuntu,a=bionic-updates,n=bionic,l=Ubuntu,c=restricted,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages release v=18.04,o=Ubuntu,a=bionic-updates,n=bionic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu bionic/multiverse i386 Packages release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu bionic/universe i386 Packages release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu bionic/restricted i386 Packages release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=restricted,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com Pinned packages: On starting the laptop, it freezes after the recent update. Using shift key during start allows me to access GRUB and choose the earlier Kernel and then it works. Expected it to start without a hitch. Software is updated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.31 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic i686 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CrashDB: ubuntu CurrentDesktop: Budgie:GNOME Date: Sun Apr 28 21:59:20 2019 InstallationDate: Installed on 2018-06-03 (329 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release i386 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fr
[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142
On disco. 2.6.1-4ubuntu2 Followed the test case and this reported the results (built) Then reinstalled with secure boot enabled. Repeated and enrolled the mok key. Rebooted and wireless was available ** Tags removed: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in dkms package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Invalid Status in dkms source package in Disco: Fix Committed Bug description: [Impact] The dkms version available in disco regressed in behavior in comparison to earlier series, causing `dkms uninstall` removing the module from the built tree instead of only uninstalling it. Per the dkms manpage, an uninstall operation should leave the module in the 'built' state, while currently it ends up only in the 'added' state. This breaks our current shim-signed logic, since on postinst we're uninstalling every dkms module, checking if we uninstalled it correctly by making sure it's in the 'built' state and then signing it if everything is ok. And this is now broken. This seemed to have been introduced unintentionally as the manpage still notes for `dkms uninstall`: "Uninstalls an installed module/module-version combo from the kernel/arch passed in the -k option, or the current kernel if the -k option was not passed upon. After uninstall completion, the driver will be left in the built state. To completely remove a driver, the remove action should be utilized." The bug has been made visible with the bcmwl-kernel-source driver, which, if installed before shim-signed, will then become uninstalled and not reinstalled again (because of the failed status check before signing). [Test Case] An easy way of checking if the uninstall logic has been reverted: 1. On a disco system, install the dkms and bcmwl-kernel-source packages (-proposed disabled). 2. Check the version of the module installed `dkms status`. 3. Once the installation completes, uninstall the bcmwl dkms module from the system: `dkms uninstall bcmwl/` 4. Checks that the status is not reported as 'built' (should be something like 'added' only): `dkms status bcmwl` 5. Enable disco-proposed and upgrade dkms. 6. Re-install the bcmwl-kernel-source package. 7. Once again uninstall the bcmwl dkms module: `dkms uninstall bcmwl/` 8. Check the status and notice that it is now reported as 'built': `dkms status bcmwl` Another way would be checking on a secureboot-enabled system that has Broadcom wireless installing the -proposed dkms, then bcmwl-kernel- source and finally shim-signed (reinstalling if necessary). This operation should result in the broadcom dkms module still being installed and active. But this test should be counted as an optional 'additional test'. [Regression Potential] Since this does change the dkms uninstall behavior, there is always some risk involved. One of the potential regressions could be related to kernel uninstallation, as we are reverting parts of the kernel prerm scripts along with the revert - but the risk should be low as we're actually reverting to the state we had in all series prior to disco. In overall the uninstall command of dkms might have regressed its behavior in case some other place started assuming the removals of modules from the built directory, but seeing the disco diff it's highly improbable. [Original Description] For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadco
[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142
** No longer affects: 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/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in ubiquity package in Ubuntu: New Bug description: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: noSourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1821823/+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 1821823] Re: No wireless networks displayed for broadcom BCM43142
** Attachment added: "installer syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821823/+attachment/5256316/+files/syslog ** Changed in: ubiquity (Ubuntu) Status: Incomplete => 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/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in linux package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: New Bug description: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: noSourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821823/+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 1821823] Re: No wireless networks displayed for broadcom BCM43142
ok - decided to reopen this. Have retested todays release candidate ISO For this laptop - I did not connect via a wired connection. I did choose the restricted drivers option in the installer and during the installation I saw that it said it installed the bcmwl-kernel-source On restart no wifi was available. I connected via wired and ran sudo apt install --reinstall bcmwl-kernel- source and immediately after completion wifi was available. I repeated the whole installation again as above and again no wifi was available after an install. Attached is the installer syslog file found in /var/log/installer ** Changed in: ubiquity (Ubuntu) Status: Invalid => 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/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in linux package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: New Bug description: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: noSourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821823/+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 1821820] Re: Cannot boot or install - have to use nomodeset
Robert suggest create a new bug report to cover your issue. Dont forget to tag this with disco and iso-testing tags. Since I created this issue report I am pleased to report that the kernel update in this release candidate iso has resolved this issue. -- 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/1821820 Title: Cannot boot or install - have to use nomodeset Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Committed Bug description: On this 19.04 beta I have to use nomodeset to boot & install Ubuntu Budgie. This is different behaviour from 18.04 and 18.10 where it booted and installed just fine without nomodeset. Without nomodeset, grub/efi disappears, and after a while a solid rather than blinking cursor on a black screen is seen. It does not boot into a live session, nor displays the ubiquity window ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Mar 26 23:40:49 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf] InstallationDate: Installed on 2019-03-26 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820/+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 1821823] Re: No wireless networks displayed for broadcom BCM43142
Just rerun this on the same iso as above (beta) and this time wireless was found. Putting this down as a glitch. ** Changed in: ubiquity (Ubuntu) Status: Incomplete => 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/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in linux package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Bug description: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: noSourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821823/+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 1821823] Re: No wireless networks displayed for broadcom BCM43142
Odd. That was already installed. I then ran a apt --reinstall install for that package and this time wireless started. Thus it appears the kernel module wasn't successfully installed by ubiquity? -- 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/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in linux package in Ubuntu: Confirmed Bug description: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see and wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821823/+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 1821823] [NEW] No wireless networks displayed for broadcom BCM43142
Public bug reported: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see and wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in linux package in Ubuntu: New Bug description: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see and wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1812867] Re: sound from bluetooth device is like vintage when quiting the hibernate
** Also affects: bluez (Ubuntu) Importance: Undecided Status: 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/1812867 Title: sound from bluetooth device is like vintage when quiting the hibernate Status in Ubuntu Budgie: New Status in bluez package in Ubuntu: New Bug description: Hi I've just noticed this today, with my laptop and my desktop, both under Ubuntu Budgie 18.10, all last updates installed if it can help you. Using a USB Bluetooth key for both After using my wireless speaker (JBL GO for more precision if it's needed) within Bluetooth, I lock my computer when I leave my office. then I unlock my computer when I'm back to. Wanna play some music on the said device. Then I start to play music... with somewhat vintage effect on the sound. I shutdown the device, start it up and same thing. To get a working properly BT, I have to - unplug and plug the USB BT key - middle click two time on the Bluetooth logo at the top, likely to disable / enable it and then it work like a charm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1812867/+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 1793178] Re: [kernel-fixed-upstream]Battery not found on Clevo N350DW laptop
** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793178 Title: [kernel-fixed-upstream]Battery not found on Clevo N350DW laptop Status in linux package in Ubuntu: Confirmed Bug description: Hello, the laptop runs flawlessly with Windows 10 and Linux except that in Linux the battery is not found in the system. I tried launching the Kernel with all acpi_osi and acpi_os_name parameters that the DSDT presented and with acpi=force, no luck. I patched the DSDT, it had 6 errors but 182 warnings, 250 remarks and 350 optimisations. I added under External(...) variable definitions one entry and commented out another that got me rid of the errors and I was able to compile a dsdt.aml. I duplicated the actual initrd and vmlinuz entries and cat the dsdt to the initrd. Restarted everything and it worked but no battery was found. It is completly invisible to the system. No my expertise has reached its limits, maybe you can have a look at it. Thank you very much, tell me what other infos you need. Greetings, Olli ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oliver 3329 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Sep 18 18:39:35 2018 InstallationDate: Installed on 2018-09-17 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) MachineType: TUXEDO N350DW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34.acpi root=UUID=77f9e7b0-9ad2-4aec-bbc6-6a3971cc9134 ro quiet splash acpi_osi=!Windows2012 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/10/2017:svnTUXEDO:pnN350DW:pvrNotApplicable:rvnTUXEDO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793178/+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 1771733] Re: bluetooth device disappears after several minutes of use
Ok. So not a TLP issue. Subscribing to the bluez package. But may also be kernel related. ** Also affects: bluez (Ubuntu) Importance: Undecided Status: 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/1771733 Title: bluetooth device disappears after several minutes of use Status in Ubuntu Budgie: New Status in bluez package in Ubuntu: New Bug description: I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to- date. When I open bluetooth settings, I am able to see many different bluetooth devices detected by my computer, and I can connect to my bluetooth mouse (Microsoft sculpt comfort mouse). However, after several minutes of use, I find that my mouse has disconnected, and I no longer have a bluetooth icon in the top right status indicator. Then, when I open bluetooth settings, the window reads "No bluetooth found: Plug in a dongle to use bluetooth." My laptop has bluetooth built in. It's an Asus UX305CA. This is my first bug report so please let me know if I've left out any important details and I will provide them as soon as possible. Thanks for all your hard work with Ubuntu Budgie! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1744431] Re: TPM 1.2 Update Owned
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntubudgie -- 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/1744431 Title: TPM 1.2 Update Owned Status in linux package in Ubuntu: New Bug description: budgie-desktop 10.4 ubuntu 17.10 86_64 kernel 4.13.0-30 My laptop is a Dell XPS 15 9550 In software center I have 2 updates TPM 1.2 Update 5.81.0.0 -> 5.81.2.1 XPS 15 9550 Precision 5510 System Update 0.1.2.19 -> 0.1.6.1 When installing the updates it prompts me to reboot which I do. In the bios, it attempts to update firmware which then gives me the following errors in separate prompts TPM is owned Firmware is not for this machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744431/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
@anthonywong - is the intention to respin just the 17.10 Ubuntu image with a fix ... or will all flavours also be respun at the same time? -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 The bug also affects Acer Aspire E5-771G. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1731913] Re: New kernel 4.13.0-16 is buggy on session lock
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntubudgie -- 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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Incomplete Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731913/+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 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntubudgie -- 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/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+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 1708931] Re: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04
Justas - yes it does have TLP preinstalled. -- 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/1708931 Title: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04 Status in bluez package in Ubuntu: New Bug description: It happens at every reset, after using bluetooth mouse for a few minutes. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Aug 6 16:42:56 2017 InstallationDate: Installed on 2017-08-05 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80E5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic root=UUID=0585caf9-68a0-4a81-ba3d-c030affa951e ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN97WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: B4:6D:83:B1:A7:87 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:301634 acl:15117 sco:0 events:1578 errors:0 TX bytes:2425 acl:31 sco:0 commands:169 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1708931/+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 1708931] Re: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04
just wondering if this is a TLP / bluetooth interaction issue Can you have a look here - http://linrunner.de/en/tlp/docs/tlp- faq.html#btusb -- 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/1708931 Title: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04 Status in bluez package in Ubuntu: New Bug description: It happens at every reset, after using bluetooth mouse for a few minutes. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Aug 6 16:42:56 2017 InstallationDate: Installed on 2017-08-05 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80E5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic root=UUID=0585caf9-68a0-4a81-ba3d-c030affa951e ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN97WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: B4:6D:83:B1:A7:87 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:301634 acl:15117 sco:0 events:1578 errors:0 TX bytes:2425 acl:31 sco:0 commands:169 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1708931/+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 1710978] Re: bluetooth stack looses connection to bluetooth devices
just wondering if this is a TLP / bluetooth interaction issue Can you have a look here - http://linrunner.de/en/tlp/docs/tlp- faq.html#btusb -- 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/1710978 Title: bluetooth stack looses connection to bluetooth devices Status in bluez package in Ubuntu: New Bug description: In Ubuntu Budgie bluetooth connection is lost in regular intervals (5mins). Thus my mouse stops working, my headset stops playing music. Reconnecting my mouse takes ages requiring a restart of bluez and reconnecting the mouse. This issue became worse ever since installing budgie (17.04) in May. (during writing this, the mouse stopped working again) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Aug 15 23:02:08 2017 InstallationDate: Installed on 2017-05-25 (81 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:10:9F:D2:25:F8 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0 TX bytes:14741 acl:474 sco:0 commands:583 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1710978/+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 1421357] Re: bcmwl cannot be compiled for trusty (14.04) - utopic HWE
Note - if I download and install the utopic bcmwl package then this works i.e. wget http://mirrors.kernel.org/ubuntu/pool/restricted/b/bcmwl/bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu1_amd64.deb sudo dpkg -i bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu1_amd64.deb sudo reboot -- -- 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/1421357 Title: bcmwl cannot be compiled for trusty (14.04) - utopic HWE Status in bcmwl package in Ubuntu: New Bug description: I get the following error when installing the utopic HWE: Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.16.0-30-generic /boot/vmlinuz-3.16.0-30-generic Error! Could not locate dkms.conf file. File: does not exist. Error! Bad return status for module build on kernel: 3.16.0-30-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/make.log for more information. enclosed is the actual make.log that shows the error. Looks like bcmwl needs to be updated for trusty to allow utopic HWE to be installed correctly ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 12 19:05:04 2015 SourcePackage: bcmwl UpgradeStatus: Upgraded to trusty on 2014-08-24 (172 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1421357/+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 1421357] [NEW] bcmwl cannot be compiled for trusty (14.04) - utopic HWE
Public bug reported: I get the following error when installing the utopic HWE: Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.16.0-30-generic /boot/vmlinuz-3.16.0-30-generic Error! Could not locate dkms.conf file. File: does not exist. Error! Bad return status for module build on kernel: 3.16.0-30-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/make.log for more information. enclosed is the actual make.log that shows the error. Looks like bcmwl needs to be updated for trusty to allow utopic HWE to be installed correctly ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 12 19:05:04 2015 SourcePackage: bcmwl UpgradeStatus: Upgraded to trusty on 2014-08-24 (172 days ago) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: "make log" https://bugs.launchpad.net/bugs/1421357/+attachment/4318159/+files/make.log -- 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/1421357 Title: bcmwl cannot be compiled for trusty (14.04) - utopic HWE Status in bcmwl package in Ubuntu: New Bug description: I get the following error when installing the utopic HWE: Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.16.0-30-generic /boot/vmlinuz-3.16.0-30-generic Error! Could not locate dkms.conf file. File: does not exist. Error! Bad return status for module build on kernel: 3.16.0-30-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/make.log for more information. enclosed is the actual make.log that shows the error. Looks like bcmwl needs to be updated for trusty to allow utopic HWE to be installed correctly ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 12 19:05:04 2015 SourcePackage: bcmwl UpgradeStatus: Upgraded to trusty on 2014-08-24 (172 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1421357/+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 1383044] Re: No elantech touchpad support for acer aspire laptop V3-571
doh Fn + F7 makes this work marking as invalid ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1383044 Title: No elantech touchpad support for acer aspire laptop V3-571 Status in “linux” package in Ubuntu: Invalid Bug description: The touch pad for my acer aspire does not appear to work - I have to use an external mouse to scroll and move. I've tried kernel 3.17.1 from the mainline as well - again the touchpad doesnt respond to touch/scroll. The touchpad works under MS Windows 7. The touchpad also worked when Ubuntu 12.04 was installed up-to the saucy lts kernel . xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ USB OPTICAL MOUSE id=10 [slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ HD Webcam id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Acer WMI hotkeysid=14 [slave keyboard (3)] xinput list-props 13 Device 'ETPS/2 Elantech Touchpad': Device Enabled (135): 1 Coordinate Transformation Matrix (137): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (259): 1 Device Accel Constant Deceleration (260): 2.50 Device Accel Adaptive Deceleration (261): 1.00 Device Accel Velocity Scaling (262):12.50 Synaptics Edges (282): 109, 2619, 60, 1056 Synaptics Finger (283): 1, 1, 0 Synaptics Tap Time (284): 180 Synaptics Tap Move (285): 129 Synaptics Tap Durations (286): 180, 180, 100 Synaptics ClickPad (287): 0 Synaptics Middle Button Timeout (288): 75 Synaptics Two-Finger Pressure (289):282 Synaptics Two-Finger Width (290): 7 Synaptics Scrolling Distance (291): 58, 58 Synaptics Edge Scrolling (292): 0, 0, 0 Synaptics Two-Finger Scrolling (293): 1, 1 Synaptics Move Speed (294): 1.00, 1.75, 0.067866, 0.00 Synaptics Off (295):0 Synaptics Locked Drags (296): 0 Synaptics Locked Drags Timeout (297): 5000 Synaptics Tap Action (298): 2, 3, 0, 0, 1, 3, 0 Synaptics Click Action (299): 1, 1, 0 Synaptics Circular Scrolling (300): 0 Synaptics Circular Scrolling Distance (301):0.10 Synaptics Circular Scrolling Trigger (302): 0 Synaptics Circular Pad (303): 0 Synaptics Palm Detection (304): 0 Synaptics Palm Dimensions (305):10, 200 Synaptics Coasting Speed (306): 20.00, 50.00 Synaptics Pressure Motion (307):30, 160 Synaptics Pressure Motion Factor (308): 1.00, 1.00 Synaptics Resolution Detect (309): 1 Synaptics Grab Event Device (310): 1 Synaptics Gestures (311): 1 Synaptics Capabilities (312): 1, 0, 1, 1, 1, 1, 1 Synaptics Pad Resolution (313): 1, 1 Synaptics Area (314): 0, 0, 0, 0 Synaptics Noise Cancellation (315): 14, 14 Device Product ID (254):2, 14 Device Node (255): "/dev/input/event6" dmesg | egrep psmouse [3.946680] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x550f01) [3.970192] psmouse serio1: elantech: Synaptics capabilities query result 0x79, 0x18, 0x0b. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad2129 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 19 22:01:00 2014 HibernationDevice: RESUME=UUID=316f3ae1-4976-40a3-b2b0-dc68f11aa92d InstallationDate: Installed on 2012
[Kernel-packages] [Bug 1383044] Re: No elantech touchpad support for acer aspire laptop V3-571
** Attachment added: "dmesg grep for elan and synap" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383044/+attachment/4240249/+files/dmesg.log -- 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/1383044 Title: No elantech touchpad support for acer aspire laptop V3-571 Status in “linux” package in Ubuntu: New Bug description: The touch pad for my acer aspire does not appear to work - I have to use an external mouse to scroll and move. I've tried kernel 3.17.1 from the mainline as well - again the touchpad doesnt respond to touch/scroll. The touchpad works under MS Windows 7. The touchpad also worked when Ubuntu 12.04 was installed up-to the saucy lts kernel . xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ USB OPTICAL MOUSE id=10 [slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ HD Webcam id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Acer WMI hotkeysid=14 [slave keyboard (3)] xinput list-props 13 Device 'ETPS/2 Elantech Touchpad': Device Enabled (135): 1 Coordinate Transformation Matrix (137): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (259): 1 Device Accel Constant Deceleration (260): 2.50 Device Accel Adaptive Deceleration (261): 1.00 Device Accel Velocity Scaling (262):12.50 Synaptics Edges (282): 109, 2619, 60, 1056 Synaptics Finger (283): 1, 1, 0 Synaptics Tap Time (284): 180 Synaptics Tap Move (285): 129 Synaptics Tap Durations (286): 180, 180, 100 Synaptics ClickPad (287): 0 Synaptics Middle Button Timeout (288): 75 Synaptics Two-Finger Pressure (289):282 Synaptics Two-Finger Width (290): 7 Synaptics Scrolling Distance (291): 58, 58 Synaptics Edge Scrolling (292): 0, 0, 0 Synaptics Two-Finger Scrolling (293): 1, 1 Synaptics Move Speed (294): 1.00, 1.75, 0.067866, 0.00 Synaptics Off (295):0 Synaptics Locked Drags (296): 0 Synaptics Locked Drags Timeout (297): 5000 Synaptics Tap Action (298): 2, 3, 0, 0, 1, 3, 0 Synaptics Click Action (299): 1, 1, 0 Synaptics Circular Scrolling (300): 0 Synaptics Circular Scrolling Distance (301):0.10 Synaptics Circular Scrolling Trigger (302): 0 Synaptics Circular Pad (303): 0 Synaptics Palm Detection (304): 0 Synaptics Palm Dimensions (305):10, 200 Synaptics Coasting Speed (306): 20.00, 50.00 Synaptics Pressure Motion (307):30, 160 Synaptics Pressure Motion Factor (308): 1.00, 1.00 Synaptics Resolution Detect (309): 1 Synaptics Grab Event Device (310): 1 Synaptics Gestures (311): 1 Synaptics Capabilities (312): 1, 0, 1, 1, 1, 1, 1 Synaptics Pad Resolution (313): 1, 1 Synaptics Area (314): 0, 0, 0, 0 Synaptics Noise Cancellation (315): 14, 14 Device Product ID (254):2, 14 Device Node (255): "/dev/input/event6" dmesg | egrep psmouse [3.946680] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x550f01) [3.970192] psmouse serio1: elantech: Synaptics capabilities query result 0x79, 0x18, 0x0b. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad2129 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 19 22:01:00 2014 HibernationDevice: RESUME=UUID=316f3ae1-4976-40a3-b2b0-dc68f11aa92d
[Kernel-packages] [Bug 1383044] [NEW] No elantech touchpad support for acer aspire laptop V3-571
Public bug reported: The touch pad for my acer aspire does not appear to work - I have to use an external mouse to scroll and move. I've tried kernel 3.17.1 from the mainline as well - again the touchpad doesnt respond to touch/scroll. The touchpad works under MS Windows 7. The touchpad also worked when Ubuntu 12.04 was installed up-to the saucy lts kernel . xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ USB OPTICAL MOUSEid=10 [slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ HD Webcam id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] ↳ Acer WMI hotkeys id=14 [slave keyboard (3)] xinput list-props 13 Device 'ETPS/2 Elantech Touchpad': Device Enabled (135): 1 Coordinate Transformation Matrix (137): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (259): 1 Device Accel Constant Deceleration (260): 2.50 Device Accel Adaptive Deceleration (261): 1.00 Device Accel Velocity Scaling (262):12.50 Synaptics Edges (282): 109, 2619, 60, 1056 Synaptics Finger (283): 1, 1, 0 Synaptics Tap Time (284): 180 Synaptics Tap Move (285): 129 Synaptics Tap Durations (286): 180, 180, 100 Synaptics ClickPad (287): 0 Synaptics Middle Button Timeout (288): 75 Synaptics Two-Finger Pressure (289):282 Synaptics Two-Finger Width (290): 7 Synaptics Scrolling Distance (291): 58, 58 Synaptics Edge Scrolling (292): 0, 0, 0 Synaptics Two-Finger Scrolling (293): 1, 1 Synaptics Move Speed (294): 1.00, 1.75, 0.067866, 0.00 Synaptics Off (295):0 Synaptics Locked Drags (296): 0 Synaptics Locked Drags Timeout (297): 5000 Synaptics Tap Action (298): 2, 3, 0, 0, 1, 3, 0 Synaptics Click Action (299): 1, 1, 0 Synaptics Circular Scrolling (300): 0 Synaptics Circular Scrolling Distance (301):0.10 Synaptics Circular Scrolling Trigger (302): 0 Synaptics Circular Pad (303): 0 Synaptics Palm Detection (304): 0 Synaptics Palm Dimensions (305):10, 200 Synaptics Coasting Speed (306): 20.00, 50.00 Synaptics Pressure Motion (307):30, 160 Synaptics Pressure Motion Factor (308): 1.00, 1.00 Synaptics Resolution Detect (309): 1 Synaptics Grab Event Device (310): 1 Synaptics Gestures (311): 1 Synaptics Capabilities (312): 1, 0, 1, 1, 1, 1, 1 Synaptics Pad Resolution (313): 1, 1 Synaptics Area (314): 0, 0, 0, 0 Synaptics Noise Cancellation (315): 14, 14 Device Product ID (254):2, 14 Device Node (255): "/dev/input/event6" dmesg | egrep psmouse [3.946680] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x550f01) [3.970192] psmouse serio1: elantech: Synaptics capabilities query result 0x79, 0x18, 0x0b. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad2129 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 19 22:01:00 2014 HibernationDevice: RESUME=UUID=316f3ae1-4976-40a3-b2b0-dc68f11aa92d InstallationDate: Installed on 2012-08-29 (781 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: Acer Aspire V3-571 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=36a268d8-0e24-4e26-af19-7f0710d526b5 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: Upgraded to trust
[Kernel-packages] [Bug 1095751] Re: bcmwl fails to build with 3.8 kernels [error: ‘struct cfg80211_ibss_params’ has no member named ‘channel’]
The last time I tried to upgrade to the Raring HWE, the old v0.0.1 of bcmwl did not work. Great news. I can confirm that bcmwl v6.20.155.1+bdcom-0ubuntu0.0.2 in proposed works correctly with LTS-Quantal kernel in precise. The dkms module was correctly created. Because of bug report https://bugs.launchpad.net/ubuntu/+source/xorg- lts-raring/+bug/1191563 I had to use this workaround to install the LTS- Raring kernel in precise - http://askubuntu.com/questions/336138/dependency-issues-while-trying- to-upgrade-12-04-2-to-the-12-04-3-hwe-stack However I can confirm that after installing the Raring HWE stack, my broadcom works correctly. Well done Alberto. Many thanks. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1095751 Title: bcmwl fails to build with 3.8 kernels [error: ‘struct cfg80211_ibss_params’ has no member named ‘channel’] Status in “bcmwl” package in Ubuntu: In Progress Status in “broadcom-sta” package in Ubuntu: Confirmed Status in “bcmwl” source package in Precise: In Progress Status in “broadcom-sta” source package in Precise: Confirmed Bug description: Upcoming 3.8 kernels have broken this DKMS package. P SRU request: [Impact] * As a result of this bug, bcmwl-kernel-source will fail to build the module against linux-generic-lts-raring in Ubuntu 12.04. [Test Case] * Enable the precise-proposed repository and install bcmwl-kernel- source (6.20.155.1+bdcom-0ubuntu0.0.2). * Install linux-generic-lts-raring * If the package installs without errors from DKMS with both the linux-generic and lts-raring kernels, then the patches work correctly. [Regression Potential] * The patches that I backported from 13.10 will preserve the current driver behaviour on linux-generic (3.2) and linux-generic-lts-quantal (3.5), thanks to the use of specific macros in the code which check the kernel version. As a result, no regressions of any kind can be expected on these kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1095751/+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 1095751] Re: bcmwl fails to build with 3.8 kernels [error: ‘struct cfg80211_ibss_params’ has no member named ‘channel’]
Hi Scott - once it has completed its passage through raring proposed, will you similarly release this into precise-proposed? -- 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/1095751 Title: bcmwl fails to build with 3.8 kernels [error: ‘struct cfg80211_ibss_params’ has no member named ‘channel’] Status in “bcmwl” package in Ubuntu: In Progress Status in “broadcom-sta” package in Ubuntu: Confirmed Status in “bcmwl” source package in Precise: In Progress Status in “broadcom-sta” source package in Precise: Confirmed Bug description: Upcoming 3.8 kernels have broken this DKMS package. P SRU request: [Impact] * As a result of this bug, bcmwl-kernel-source will fail to build the module against linux-generic-lts-raring in Ubuntu 12.04. [Test Case] * Enable the precise-proposed repository and install bcmwl-kernel- source (6.20.155.1+bdcom-0ubuntu0.0.2). * Install linux-generic-lts-raring * If the package installs without errors from DKMS with both the linux-generic and lts-raring kernels, then the patches work correctly. [Regression Potential] * The patches that I backported from 13.10 will preserve the current driver behaviour on linux-generic (3.2) and linux-generic-lts-quantal (3.5), thanks to the use of specific macros in the code which check the kernel version. As a result, no regressions of any kind can be expected on these kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1095751/+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 547192] Re: serious kernel oops for Belkin wireless F5D7010 card
Christopher - I'm going to mark this as invalid as I no longer have this hardware to test with. Thanks for the reminder. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/547192 Title: serious kernel oops for Belkin wireless F5D7010 card Status in “linux” package in Ubuntu: Invalid Bug description: serious kernel problem report when plugging in a belkin wireless G notebook Network Card Model F5D7010. Have tested the current lucid kernel as well as 2.6.33-020633-generic_2.6.33-020633_i386.deb and 2.6.34-999-generic_2.6.34-999.201003151003_i386.deb Both of these upstream kernels give the same issue. ProblemType: KernelOops AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Annotation: Your system might become unstable now and might need to be restarted. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1438 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with ALC202 at irq 10' Mixer name : 'Realtek ALC202 rev 0' Components : 'AC97a:414c4740' Controls : 37 Simple ctrls : 23 Date: Thu Mar 25 19:30:47 2010 DistroRelease: Ubuntu 10.04 Failure: oops HibernationDevice: RESUME=UUID=d5de6cfd-d9c7-4d95-adf0-4763a9399bb3 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 004 Device 002: ID 15d9:0a4c Dexon Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite A30 Package: linux-image-2.6.32-17-generic 2.6.32-17.26 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=91abadf7-37aa-4581-872c-790d090e2d79 ro noapic quiet splash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes RfKill: SourcePackage: linux TestedUpstream: Yes Title: WARNING: at /build/buildd/linux-2.6.32/drivers/pci/pci.c:79 pci_ioremap_bar+0x57/0x60() Uname: Linux 2.6.32-17-generic i686 dmi.bios.date: 07/22/2004 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.80 dmi.board.name: DBL00 dmi.board.vendor: TOSHIBA dmi.board.version: Null dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.80:bd07/22/2004:svnTOSHIBA:pnSatelliteA30:pvrPSA35E-3KK72-EN:rvnTOSHIBA:rnDBL00:rvrNull:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A30 dmi.product.version: PSA35E-3KK72-EN dmi.sys.vendor: TOSHIBA --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1326 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with ALC202 at irq 10' Mixer name : 'Realtek ALC202 rev 0' Components : 'AC97a:414c4740' Controls : 37 Simple ctrls : 23 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=d5de6cfd-d9c7-4d95-adf0-4763a9399bb3 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 004 Device 002: ID 15d9:0a4c Dexon Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite A30 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=91abadf7-37aa-4581-872c-790d090e2d79 ro i915.modeset=1 noapic quiet splash ProcEnviron: PATH=(custom, user) LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Regression: No RelatedPackageVersions: linux-firmware 1.34 Reproducible: Yes RfKill: Tags: lucid networking needs-upstream-testing Uname: Linux 2.6.32-21-generic i686 UserGroups: adm admin audio cdrom dialout dip fax fuse lpa
[Kernel-packages] [Bug 1095751] Re: bcmwl fails to build with 3.8 kernels [error: ‘struct cfg80211_ibss_params’ has no member named ‘channel’]
@Virgo - has this really been released - I only see bcmwl-kernel-source (6.20.155.1+bdcom-0ubuntu0.0.1) in http://packages.ubuntu.com/search?suite=precise- updates&searchon=names&keywords=bcmwl Also it appears Alberto's 0.0.2 package is in the unapproved upload queue list - https://launchpad.net/ubuntu/precise/+queue?queue_state=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/1095751 Title: bcmwl fails to build with 3.8 kernels [error: ‘struct cfg80211_ibss_params’ has no member named ‘channel’] Status in “bcmwl” package in Ubuntu: Fix Released Status in “broadcom-sta” package in Ubuntu: Fix Released Status in “bcmwl” source package in Precise: Fix Released Status in “broadcom-sta” source package in Precise: Fix Released Bug description: Upcoming 3.8 kernels have broken this DKMS package. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-0.1~apw2-generic 3.8.0-rc2 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.7-0ubuntu2 Architecture: amd64 Date: Thu Jan 3 17:59:26 2013 InstallationDate: Installed on 2012-11-07 (57 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627) MarkForUpload: True 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/1095751/+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 1095751] Re: bcmwl fails to build with 3.8 kernels [error: ‘struct cfg80211_ibss_params’ has no member named ‘channel’]
Matthew "what can I do..." - wait until the SRU is drafted, accepted and rolled out. Until then - look at askubuntu for a workaround. - http://askubuntu.com/questions/337974/broadcom-sta-driver-fails-to- install-missing-wl-on-ubuntu-12-04-3-lts-linux-3 -- 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/1095751 Title: bcmwl fails to build with 3.8 kernels [error: ‘struct cfg80211_ibss_params’ has no member named ‘channel’] Status in “bcmwl” package in Ubuntu: Fix Released Status in “broadcom-sta” package in Ubuntu: Confirmed Status in “bcmwl” source package in Precise: In Progress Status in “broadcom-sta” source package in Precise: Confirmed Bug description: Upcoming 3.8 kernels have broken this DKMS package. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-0.1~apw2-generic 3.8.0-rc2 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.7-0ubuntu2 Architecture: amd64 Date: Thu Jan 3 17:59:26 2013 InstallationDate: Installed on 2012-11-07 (57 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627) MarkForUpload: True 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/1095751/+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 1216288] Re: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1095751 *** https://bugs.launchpad.net/bugs/1095751 hmmm - Daniel - the other bug report says that it is "fix released" - but clearly the issue is not resolved as per the last comment. Can I suggest you either reopen this one or reopen the other bug report? Remember - the other report was for raring - so the package was fixed in the raring repository. This problem is for Precise users - they have the older package which doesnt work for the HWE raring kernel. -- 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/1216288 Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build Status in “bcmwl” package in Ubuntu: Confirmed Bug description: the following error was seen in /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/make.log dad@emachine:/home/home/dad$ more /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/make.log DKMS make.log for bcmwl-6.20.155.1+bdcom for kernel 3.8.0-29-generic (x86_64) Sat Aug 24 11:48:35 BST 2013 make: Entering directory `/usr/src/linux-headers-3.8.0-29-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API LD /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/built-in.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.o /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c: In function ‘wl_cfg80211_join_ibss’: /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:705:26: erro r: ‘struct cfg80211_ibss_params’ has no member named ‘channel’ /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c: At top leve l: /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1560:2: warn ing: initialisation from incompatible pointer type [enabled by default] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1560:2: warn ing: (near initialisation for ‘wl_cfg80211_ops.scan’) [enabled by default] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1565:2: warn ing: initialisation from incompatible pointer type [enabled by default] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1565:2: warn ing: (near initialisation for ‘wl_cfg80211_ops.set_tx_power’) [enabled by defaul t] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1566:2: warn ing: initialisation from incompatible pointer type [enabled by default] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1566:2: warn ing: (near initialisation for ‘wl_cfg80211_ops.get_tx_power’) [enabled by defaul t] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c: In function ‘wl_update_bss_info’: /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1991:11: err or: ‘struct cfg80211_bss’ has no member named ‘information_elements’ /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1992:15: err or: ‘struct cfg80211_bss’ has no member named ‘len_information_elements’ make[1]: *** [/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211. o] Error 1 make: *** [_module_/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build] Error 2 make: Leaving directory `/usr/src/linux-headers-3.8.0-29-generic' dad@emachine:/home/home/dad$ ProblemType: Package DistroRelease: Ubuntu 12.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 DKMSKernelVersion: 3.8.0-29-generic Date: Sat Aug 24 11:49:14 2013 MarkForUpload: True PackageVersion: 6.20.155.1+bdcom-0ubuntu0.0.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: 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/1216288/+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 1216288] Re: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build
I can confirm that if I manually build the saucy deb on this precise raring HWE, the wireless works fine. Therefore, I would suggest that the saucy broadcom source package should be backported to precise so that HWE upgraders dont suffer the same issues. -- 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/1216288 Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build Status in “bcmwl” package in Ubuntu: New Bug description: the following error was seen in /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/make.log dad@emachine:/home/home/dad$ more /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/make.log DKMS make.log for bcmwl-6.20.155.1+bdcom for kernel 3.8.0-29-generic (x86_64) Sat Aug 24 11:48:35 BST 2013 make: Entering directory `/usr/src/linux-headers-3.8.0-29-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API LD /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/built-in.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.o /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c: In function ‘wl_cfg80211_join_ibss’: /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:705:26: erro r: ‘struct cfg80211_ibss_params’ has no member named ‘channel’ /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c: At top leve l: /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1560:2: warn ing: initialisation from incompatible pointer type [enabled by default] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1560:2: warn ing: (near initialisation for ‘wl_cfg80211_ops.scan’) [enabled by default] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1565:2: warn ing: initialisation from incompatible pointer type [enabled by default] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1565:2: warn ing: (near initialisation for ‘wl_cfg80211_ops.set_tx_power’) [enabled by defaul t] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1566:2: warn ing: initialisation from incompatible pointer type [enabled by default] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1566:2: warn ing: (near initialisation for ‘wl_cfg80211_ops.get_tx_power’) [enabled by defaul t] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c: In function ‘wl_update_bss_info’: /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1991:11: err or: ‘struct cfg80211_bss’ has no member named ‘information_elements’ /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1992:15: err or: ‘struct cfg80211_bss’ has no member named ‘len_information_elements’ make[1]: *** [/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211. o] Error 1 make: *** [_module_/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build] Error 2 make: Leaving directory `/usr/src/linux-headers-3.8.0-29-generic' dad@emachine:/home/home/dad$ ProblemType: Package DistroRelease: Ubuntu 12.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 DKMSKernelVersion: 3.8.0-29-generic Date: Sat Aug 24 11:49:14 2013 MarkForUpload: True PackageVersion: 6.20.155.1+bdcom-0ubuntu0.0.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: 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/1216288/+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 1216288] [NEW] bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build
Public bug reported: the following error was seen in /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/make.log dad@emachine:/home/home/dad$ more /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/make.log DKMS make.log for bcmwl-6.20.155.1+bdcom for kernel 3.8.0-29-generic (x86_64) Sat Aug 24 11:48:35 BST 2013 make: Entering directory `/usr/src/linux-headers-3.8.0-29-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API LD /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/built-in.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.o /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c: In function ‘wl_cfg80211_join_ibss’: /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:705:26: erro r: ‘struct cfg80211_ibss_params’ has no member named ‘channel’ /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c: At top leve l: /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1560:2: warn ing: initialisation from incompatible pointer type [enabled by default] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1560:2: warn ing: (near initialisation for ‘wl_cfg80211_ops.scan’) [enabled by default] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1565:2: warn ing: initialisation from incompatible pointer type [enabled by default] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1565:2: warn ing: (near initialisation for ‘wl_cfg80211_ops.set_tx_power’) [enabled by defaul t] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1566:2: warn ing: initialisation from incompatible pointer type [enabled by default] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1566:2: warn ing: (near initialisation for ‘wl_cfg80211_ops.get_tx_power’) [enabled by defaul t] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c: In function ‘wl_update_bss_info’: /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1991:11: err or: ‘struct cfg80211_bss’ has no member named ‘information_elements’ /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1992:15: err or: ‘struct cfg80211_bss’ has no member named ‘len_information_elements’ make[1]: *** [/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211. o] Error 1 make: *** [_module_/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build] Error 2 make: Leaving directory `/usr/src/linux-headers-3.8.0-29-generic' dad@emachine:/home/home/dad$ ProblemType: Package DistroRelease: Ubuntu 12.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 DKMSKernelVersion: 3.8.0-29-generic Date: Sat Aug 24 11:49:14 2013 MarkForUpload: True PackageVersion: 6.20.155.1+bdcom-0ubuntu0.0.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: 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 precise -- 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/1216288 Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build Status in “bcmwl” package in Ubuntu: New Bug description: the following error was seen in /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/make.log dad@emachine:/home/home/dad$ more /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/make.log DKMS make.log for bcmwl-6.20.155.1+bdcom for kernel 3.8.0-29-generic (x86_64) Sat Aug 24 11:48:35 BST 2013 make: Entering directory `/usr/src/linux-headers-3.8.0-29-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API LD /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/built-in.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.o /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c: In function ‘wl_cfg80211_join_ibss’: /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:705:26: erro r: ‘struct cfg80211_ibss_params’ has no member named ‘channel’ /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c: At top leve l: /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_cfg80211.c:1560:2: