[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
@k3dar7: Thanks a lot for your valuable help! Following script works for me on Ubuntu 21.04 (64-bit): sudo wget https://raw.githubusercontent.com/k3dar/kumk/main/kumk -O /usr/local/bin/kumk sudo chmod a+x /usr/local/bin/kumk sudo kumk install latest -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1199059] Re: blueman and pulse's module-bluetooth-discover (A2DP audio sink devices failed to work with bluetoothd : Unable to select SEP in system log.)
I uninstalled blueman, installed pavucontrol, reboot my PC and then turned on my bluetooth speaker to solve this issue. I also believe that blueman is the main culprit and that blueman keeps unloading the module-bluetooth-discover module. So I agree with remark #28 in this thread. -- 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/1199059 Title: blueman and pulse's module-bluetooth-discover (A2DP audio sink devices failed to work with bluetoothd : Unable to select SEP in system log.) Status in Blueman - Bluetooth Manager: New Status in “blueman” package in Ubuntu: Confirmed Status in “bluez” package in Ubuntu: Incomplete Status in “pulseaudio” package in Ubuntu: Invalid Status in “bluez” package in Debian: Fix Released Bug description: All my A2DP profile devices can't create a audio device properly... My 2 13.04 machines both have this issue(1 notebook, 2 bluetooth dongles) UPDATE: Upgraded to 13.10, still reproducible Possible root cause fix: Please refer #15 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Jul 9 01:01:38 2013 InstallationDate: Installed on 2013-01-26 (162 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130126) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-21-generic root=UUID=9bce9679-da3a-44fd-84ec-b16339a84004 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to raring on 2013-03-01 (128 days ago) dmi.bios.date: 08/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd08/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:15:83:54:59:9F ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:29508 acl:1270 sco:0 events:461 errors:0 TX bytes:5249 acl:165 sco:0 commands:95 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1199059/+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 1199059] Re: blueman and pulse's module-bluetooth-discover (A2DP audio sink devices failed to work with bluetoothd : Unable to select SEP in system log.)
I am using Xubuntu 14.04 LTS (trusty) and running the new lxqt desktop. I also still need to use the workaround in post #13 to get my bluetooth speaker to work correctly. -- 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/1199059 Title: blueman and pulse's module-bluetooth-discover (A2DP audio sink devices failed to work with bluetoothd : Unable to select SEP in system log.) Status in “blueman” package in Ubuntu: Confirmed Status in “bluez” package in Ubuntu: Incomplete Status in “pulseaudio” package in Ubuntu: Invalid Status in “bluez” package in Debian: Fix Released Bug description: All my A2DP profile devices can't create a audio device properly... My 2 13.04 machines both have this issue(1 notebook, 2 bluetooth dongles) UPDATE: Upgraded to 13.10, still reproducible Possible root cause fix: Please refer #15 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Jul 9 01:01:38 2013 InstallationDate: Installed on 2013-01-26 (162 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130126) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-21-generic root=UUID=9bce9679-da3a-44fd-84ec-b16339a84004 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to raring on 2013-03-01 (128 days ago) dmi.bios.date: 08/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd08/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:15:83:54:59:9F ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:29508 acl:1270 sco:0 events:461 errors:0 TX bytes:5249 acl:165 sco:0 commands:95 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1199059/+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 1172151] Re: 168c:0032 ASUS F75A wi-fi disabled by hardware switch
For Patrik Jansson, the following workaround works: echo options asus_nb_wmi wapf=1 | sudo tee /etc/modprobe.d/asus_nb_wmi.conf He is using the following configuration: DISTRIB_DESCRIPTION=Ubuntu 13.10 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Laptop: ASUS a550c (ASUS-NotebookSKU) Kernel 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Sources: https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/241238 http://ubuntuforums.org/showthread.php?t=2181558 -- 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/1172151 Title: 168c:0032 ASUS F75A wi-fi disabled by hardware switch Status in GUI Program to install ath9k_htc (Atheros Linux Driver): Invalid Status in Additional Linux Wireless Drivers: Invalid Status in Wireless Tools - Tools for manipulating Linux Wireless Extensions: Invalid Status in Linux WPA/WPA2/IEEE 802.1X Supplicant: Invalid Status in “linux” package in Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Invalid Bug description: Today, my Uncle purchased a new ASUS F75A laptop, with the following network card: lspci | grep -i wireless 02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01) I've installed Ubuntu 13.04 onto this machine, and each time I log in and click on the network-manager indicator, it is in the following state: 1) Enable Wi-Fi is NOT check and it is GRAYED OUT. 2) wi-fi is disabled by hardware switch WORKAROUND: The following terminal command only resolves the issue for one session: sudo rmmod -f asus_nb_wmi Toggle wi-fi, by holding down the function key and pressing f2 (fn-f2). If one does not do the terminal command above, the wi-fi only stays enabled for about 4 seconds and then resorts back to the previous state mentioned above. WORKAROUND: sudo gedit /etc/modprobe.d/blacklist.conf Add this line: blacklist asus-nb-wmi Save your edit. My Uncle must do this each and every time he logs into his laptop, in order to consume wi-fi. Also, due to his condition, he's practically incapable of these seemingly simple steps. Note: Before removing Windows 7, Window 7 was able to (appearantly) automatically turn on the hardware switch and connect to the wireless network (recurringly) on each login. However, in Ubuntu, the hardware switch is always OFF after login, and I must rmmod before toggling the hardware switch with fn-f2. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Wed Apr 24 01:48:48 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-24 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) IpRoute: default via 192.168.7.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.7.0/24 dev wlan0 proto kernel scope link src 192.168.7.36 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 165281c64-6702-4ff0-bc4e-1b1c2c7b3b4a 802-3-ethernet1366784897 Wed 24 Apr 2013 01:28:17 AM CDTyes no /org/freedesktop/NetworkManager/Settings/1 Video Surveillance7f736f06-a4e9-4340-a9cf-b293812ca247 802-11-wireless 1366786097 Wed 24 Apr 2013 01:48:17 AM CDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled
[Kernel-packages] [Bug 1199059] Re: A2DP audio sink devices failed to work with bluetoothd : Unable to select SEP in system log.
I am running the 64 bit version of Ubuntu 13.10 and face the same problem with Unable to select SEP errors in syslog. The suggestion in comment #7 unfortunately did not solve the problem for me. -- 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/1199059 Title: A2DP audio sink devices failed to work with bluetoothd : Unable to select SEP in system log. Status in “bluez” package in Ubuntu: Confirmed Bug description: All my A2DP devices can't create a audio device properly... My 2 13.04 machines both have this issue(1 notebook, 2 bluetooth dongles) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Jul 9 01:01:38 2013 InstallationDate: Installed on 2013-01-26 (162 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130126) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-21-generic root=UUID=9bce9679-da3a-44fd-84ec-b16339a84004 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to raring on 2013-03-01 (128 days ago) dmi.bios.date: 08/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd08/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:15:83:54:59:9F ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:29508 acl:1270 sco:0 events:461 errors:0 TX bytes:5249 acl:165 sco:0 commands:95 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1199059/+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 319825] Re: acer_wmi in Jaunty on Aspire One exposes non-functional (always disabled) rfkill device
This issue still occurs, even in Ubuntu 13.10. Here is an example: https://answers.launchpad.net/ubuntu/+source/gnome- nettool/+question/240287 Workaround solution was to blacklist the acer_wmi module. -- 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/319825 Title: acer_wmi in Jaunty on Aspire One exposes non-functional (always disabled) rfkill device Status in The Linux Kernel: New Status in Ubuntu Netbook Remix: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Jaunty: Fix Released Status in “linux” package in Fedora: Confirmed Bug description: Upgrading to Jaunty, I found that network-manager would no longer let me make any wireless connections - it turned out that it thought that a killswitch was triggered (in /var/log/daemon.log). However, iwlist wlan0 scan could see networks. Toggling the killswitch apparently did turn the radio off and on, as evidenced by the response of iwlist wlan0 scan, but network-manager remained convinced that radio was killed throughout. I discovered that the acer_wmi rfkill device in sysfs was reporting state=0 regardless what state the killswitch was actually in. Investigating the modules website at http://code.google.com/p/aceracpi/wiki/SupportedHardware revealed the comment that the WMI implementation on the Aspire One does not do anything. Based on that assertion, I did rmmod acer_wmi, and network-manager sprang into life and happily connected my network. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: linux-image-2.6.27-11-generic 2.6.27-11.24 ProcCmdLine: root=UUID=4564f896-7a91-482d-b4fd-ad60ba162fce ro quiet splash ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.27-11.24-generic SourcePackage: linux UnreportableReason: This is not a genuine Ubuntu package To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/319825/+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
