[Kernel-packages] [Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter
Walter/wxl asked me to test `sddm-theme-breeze` I skipped in comment #22, report posted (https://discourse.lubuntu.me/t/login-screen- flashes/1634/17?u=guiverc) days ago now pasted here --- I added `sddm-theme-breeze` and rebooted, yuk! (I had forgotten to perform the `sudo update-alternatives --config sddm-ubuntu-theme` step but `sddm` had been changed by the additional of a virtual keyboard) making it harder to use. I've seen this before (*semi-recently with dual screens*) and recalled the on-screen keyboard appearing on secondary display, but it booted with keyboard drawn on black background, on mouse movement etc it would flash between black, on-screen keyboard (using 2/3rds of single display) & background.. *yuk* If a user watched the display, they'd have trouble being able to login. `sddm` is still working, if I close my eyes & login as I'd expect it to operate, I'm logged in, but visually it's a mess & unusable on that box. The behavior is very familiar though, I added `kubuntu-desktop` to my Lubuntu *focal* installs on d755-5 (mentioned 4 messages up, AMD and flashing `sddm`; [lp 1865837](https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1865837)) and that box has only single display and it had the same behavior if I recall correctly. (*it was also added to hp8200 install which has the two displays*) Finally I performed the `sudo update-alternatives --config sddm-ubuntu- theme` to make the 'new' breeze default, and on reboot it hung before eventual shutdown...errors? `sddm` didn't appear again. The GUI session now has a large pointer, which I can move around with the mouse, but nothing more. I can fix this currently by changing the theme to something else, but with the virtual keyboard appearing on all themes now, they're all rather annoying.. I've taken some photos of messages I see on screen (sddm-greeter & nouveau) but my phone is being annoying (no messages in `dmesg` or `journalctl` which I could easily paste; & `/var/log/sddm.log` is empty). Most messages appear during shutdown which was ultra slow with breeze the default. Switching to another theme and shutdown returns to normal, messages gone (*just virtual terminal remains which isn't helpful*). The one message I get on text terminal (with breeze active) is `[ 120.676863] nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon` written after the "Optiplex990 login:" Either a requirement is missing (package error) or we're missing something in config?? -- links to photos - shutdown messages https://photos.app.goo.gl/Yf5pK28w4FMUmSi17 https://photos.app.goo.gl/VBvvRrzKMDWjxPjx5 - switching to text terminal; message https://photos.app.goo.gl/nRJEGJHd45WoenSb8 --- Additional note, the switching-to-text-terminal message (last photo link) I saw once today too, I think when using `gdm3`, but I don't believe I did when using `lightdm`. If this detail is useful, I'd need to re-test to confirm this -- 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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install on dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt) On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095
[Kernel-packages] [Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter
continuing comment #24 (links to photos) - gdm3 photos https://photos.app.goo.gl/koM6HAL4ZDFDTdvc8 https://photos.app.goo.gl/SgBroo8vrMB8Bp6K9 https://photos.app.goo.gl/txdBXNVxii5mHZrZ6 https://photos.app.goo.gl/TVLNm4WFuPQbsTSq6 - logged into plasma (missing character example) https://photos.app.goo.gl/RWKzMzoqTbCmjPXW7 (didn't take photo of menu; screen was glitchy in operation; flashing black triangles (though they settled down when mouse wasn't being touched, until sddm which flashes time/pattern). The graphic glitches have on the desktop have been reported elsewhere ** Tags added: hirsute -- 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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install on dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt) On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc 950 F pulseaudio /dev/snd/controlC0: guiverc 950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-09-17 (-365 days ago)
[Kernel-packages] [Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter
This issue can re-created by booting the Lubuntu daily live (hirsute), logging out and as you go to `sddm` you see the issue. done with today's hirsute daily. @Kai-Heng Feng (kaihengfeng) Using the installation done in comment #21-22, I added - lightdm no issues discovered, I could login normally and no issues discovered in quick play. I did a few groovy Xubuntu installs on this, it was where I discovered other issues, but I don't recall flashing-issues. I also noted Kubuntu is available on the list of sessions, so I tried that.. The kubuntu wasn't usable though; the characters on screen icons are missing.. eg. what I think is supposed to be "Computer" showed as "Co pute" one time, next time only the "t" was missing.. Some issues I wonder if missing packages, but there are graphic issues it feels like here. - gdm3 this doesn't look right. I've taken numerous photos, so I'll upload and paste links, but I'll also find & boot a Ubuntu desktop to compare so I can better describe issues. Once logged in lubuntu was good just as with lightdm/xdm/sddm (issues if I used kubuntu identical to those experienced with lightdm as greeter) The issue with gdm3 is not the same, it's NOT flashing, however graphics just don't like as I believe they should (white areas on screen appears to be issue rather than the flashing). More to come.. No -- 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/1895905 Title: lubuntu groovy; flashing of sddm greeter Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu groovy QA-test install on dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt) On reboot, the login greeter (sddm) screen isn't nice, with areas of the screen flashing white/black/white/black (maybe white & black each second like a ":" might flash on the clock, only the ":" on the clock is static) likely package at fault should be xserver-xorg-video-nouveau Photo can be seen at https://photos.app.goo.gl/SYPytVxtkKBEj9NY8 The - drop down for session (not selected Lubuntu) - language drop down (not US flag) - white/black on login picture (not grey name) flashes black & white on a cycle... The top panel items will eventually stop flashing (ie. session & layout) but time or certain actions cause the flashing white then black in cycle to occur again. ** Expected Result No flashing, its irritating & potentially a problem for some with certain health conditions. ** Not new issue, it's occurred in the past hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt) I've had this issue before on eoan on hp dx6120 i believe but cannot find bug report. The bug was likely not filed as that box was i386 & support was being dropped when I noticed it so I didn't see any point. It's not new, and no doubt relates to Nvidia cards, and I'm convinced I've filed this before on dx6120 so if not eoan, disco, but I've not yet found it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guiverc1095 F pulseaudio /dev/snd/controlC0: guiverc1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 11:13:50 2020 InstallationDate: Installed on 2021-09-17 (-365 days ago) InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc.
[Kernel-packages] [Bug 1894203] Re: Trackpad not get detected and not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894203 Title: Trackpad not get detected and not working Status in linux package in Ubuntu: Expired Bug description: I have checked /proc/bus/input/devices, there is not entry related to trackpad. Below is the content of the same file I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0C:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input6 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:35/LNXVIDEO:00/input/input7 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:03/input/input8 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input9 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input10 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 14:44:59 2020 InstallationDate: Installed on 2020-05-08 (118 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894203/+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']
** Changed in: broadcom-sta (Ubuntu) Status: Triaged => Incomplete ** 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 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: New Status in bcmwl source package in Precise: Fix Released Status in broadcom-sta source package in Precise: Triaged 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 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
@Daniel could you try out the bluez package from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/pi-bluetooth/+packages ? Should be as simple as doing: sudo add-apt-repository ppa:waveform/pi-bluetooth sudo apt update sudo apt upgrade The version in that PPA contains the pi foundation's patches to bluez which were necessary to enable bluetooth on the pi400 (LP: #1903048), but they also alter some of the general initialization of the bluetooth module on all pis (amongst other things). A (slightly tidied up) variant of this is currently intended for hirsute, to be SRU'd to groovy and focal, so I'd be interested to hear if it also fixes this issue. -- 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/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 Status in bluez package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: Incomplete Status in pi-bluetooth package in Ubuntu: Confirmed Status in bluez source package in Groovy: Incomplete Status in linux-raspi source package in Groovy: Incomplete Status in pi-bluetooth source package in Groovy: New Bug description: Raspberry pi 4 4Gb ram Ubuntu desktop 20.10 64 bit After reboot no Bluetooth devices connect, scanning Bluetooth devices works, results with same device name (duplicated and with not set up status). Sometimes after several reboots it works. If I use power off and cycle power then it works fine each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+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 1876753] Re: Thinkpad T430 Power Cycles instead of rebooting
Hi, sorry for the late reply but I had to do a lot of tests with many kernels with both ubuntu 20.04 and 20.10. I have come to the conclusion that it is not a direct problem with some kernel version but with the system itself. I also tried with some old versions of ubuntu up to 19.10 using new kernels and the reboot problem didn't occur and updating to 20.04 onwards the problem appears. Unfortunately I don't know exactly what the problem is but something in the latest version is not working as it should. So I would like to know if there is anything else I could do to verify the root of the problem. -- 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/1876753 Title: Thinkpad T430 Power Cycles instead of rebooting Status in linux package in Ubuntu: Incomplete Bug description: After installing Xubuntu 20.04, Thinkpad T430 does not reboot properly any more. Expected behavior: Power LED and HDD stay on, System reboots. Actual behavior: System switches off (including power LED and HDD which leads to emergency head parking and loud click noise) and switches back on after 5 seconds. Problem occurs with Xubuntu 20.04 and Ubuntu 20.04 even when booted from live USB medium. It also occurs with Mainline Kernel 5.6.7 which I installed for testing. It does not occur with several live media used for testing (Xubuntu 18.04, Windows 10, Manjaro 20, MX 19) or when rebooted from within GRUB2 on my Xubuntu installation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-28-generic 5.4.0-28.32 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1954 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon May 4 17:58:49 2020 HibernationDevice: RESUME=none InstallationDate: Installed on 2020-05-01 (3 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 2351BH6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2351BH6 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:svnLENOVO:pn2351BH6:pvrThinkPadT430:rvnLENOVO:rn2351BH6:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2351BH6 dmi.product.sku: LENOVO_MT_2351 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876753/+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 1902281] Re: aws: disable strict IOMMU TLB invalidation by default
** Changed in: linux-aws (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1902281 Title: aws: disable strict IOMMU TLB invalidation by default Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Groovy: Fix Committed Bug description: [Impact] AWS requires to relax the synchronous IOMMU TLB invalidation by default to get a significant performance improvement on certain arm64 instance types (bare metal). This is not the default behavior in the upstream kernel, that enforces synchronous invalidations to provide a better isolation and potentially prevent side-channel attacks with malicious devices that can be registered in the same IOMMU domain. This behavior cannot be changed at run-time and it is available only via iommu.strict=0|1 (via kernel boot parameters - GRUB). [Test Case] It has been performance-tested by AWS. [Fix] Change iommu.strict in the kernel to be off by default. It will be always possible to revert this change and restore the old behavior by setting iommu.strict=1 in the GRUB parameters (and rebooting). [Regression Potential] The only concern about this change is that we are relaxing a security constraint. After considerable discussion and evaluation (also with the security team) the conclusion was that this change is not realistically affecting the particular AWS environment in terms of security and it can definitely provide a significant performance boost on certain arm64 instance types. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1902281/+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 1903087] Re: AWS: add the nitro_enclaves driver
** Changed in: linux-aws (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1903087
Title:
AWS: add the nitro_enclaves driver
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-aws source package in Focal:
Fix Committed
Status in linux-aws source package in Groovy:
Fix Committed
Status in linux-aws source package in Hirsute:
In Progress
Bug description:
Add the nitro_enclaves driver from mainline to linux-
aws/{focal,bionic-5.4} and linux-aws/{groovy,hirsute}. The driver is
supplied by the following mainline commits, which are all clean cherry
picks for groovy with a couple of trivial backports for focal:
e82ed736ad2d MAINTAINERS: Add entry for the Nitro Enclaves driver
bf15d79ce142 nitro_enclaves: Add overview documentation
acc4229c3990 nitro_enclaves: Add sample for ioctl interface usage
0f5c7b748439 nitro_enclaves: Add Makefile for the Nitro Enclaves driver
07499cc661a9 nitro_enclaves: Add Kconfig for the Nitro Enclaves driver
9c8eb50fe9e2 nitro_enclaves: Add logic for terminating an enclave
111c775a5f0d nitro_enclaves: Add logic for starting an enclave
7dc9d4309fdb nitro_enclaves: Add logic for setting an enclave memory region
988b7a471726 nitro_enclaves: Add logic for getting the enclave image load info
ff8a4d3e3a99 nitro_enclaves: Add logic for setting an enclave vCPU
38907e124088 nitro_enclaves: Add logic for creating an enclave VM
bd47c995c0e4 nitro_enclaves: Init misc device providing the ioctl interface
e5d616d8bb50 nitro_enclaves: Handle out-of-band PCI device events
ad2b6980d0d3 nitro_enclaves: Handle PCI device command requests
89308c11ae3b nitro_enclaves: Init PCI device driver
1df624892c1e nitro_enclaves: Define enclave info for internal bookkeeping
0a44561768c5 nitro_enclaves: Define the PCI device interface
15b760c37ad3 nitro_enclaves: Add ioctl interface definition
linux-aws/focal also needs this prereq:
93ef1429e556 cpu/hotplug: Add new {add,remove}_cpu() functions
[Impact]
* Supplies driver needed to support AWS feature.
[Test Case]
* T.B.D. (to be validated by AWS).
[Regression Potential]
* Low: Just adds a new driver module which won't load by default.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1903087/+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 1902281] Re: aws: disable strict IOMMU TLB invalidation by default
** Changed in: linux-aws (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1902281 Title: aws: disable strict IOMMU TLB invalidation by default Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Bionic: New Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Groovy: Fix Committed Bug description: [Impact] AWS requires to relax the synchronous IOMMU TLB invalidation by default to get a significant performance improvement on certain arm64 instance types (bare metal). This is not the default behavior in the upstream kernel, that enforces synchronous invalidations to provide a better isolation and potentially prevent side-channel attacks with malicious devices that can be registered in the same IOMMU domain. This behavior cannot be changed at run-time and it is available only via iommu.strict=0|1 (via kernel boot parameters - GRUB). [Test Case] It has been performance-tested by AWS. [Fix] Change iommu.strict in the kernel to be off by default. It will be always possible to revert this change and restore the old behavior by setting iommu.strict=1 in the GRUB parameters (and rebooting). [Regression Potential] The only concern about this change is that we are relaxing a security constraint. After considerable discussion and evaluation (also with the security team) the conclusion was that this change is not realistically affecting the particular AWS environment in terms of security and it can definitely provide a significant performance boost on certain arm64 instance types. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1902281/+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 1895327] Re: PRIME Profiles Not Shown in nvidia-settings
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1895327 Title: PRIME Profiles Not Shown in nvidia-settings Status in nvidia-settings package in Ubuntu: Confirmed Bug description: Hi, I've installed Nvidia 450 on new installation of Ubuntu 20.04.1. Prime Render Offload works in manual mode with `__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia` But nvidia-settings says prime is not supported. And so I have no prime entry in the nvidia window. So I think the swith between integrated and nvidia GPU will not be automatic and the "on demand" does not work. I asked nvidia developpers and they said it should be a ubuntu patch : https://forums.developer.nvidia.com/t/prime-no-offloading-required-prime-is-it-supported/154181 **Computer :** Asus A17-TUF766IU-H7074T **OS Details :** Ubuntu 20.04.1 with mainline 5.8.8 kernel Nvidia Driver version : 450.66 Desktop Environment : Plasma Window Manager : KDE **Hardware Details** Processor : AMD Ryzen 4800H GPU : GeForce GTX 1660 Ti 6 Go meloli@Asus-A17:~$ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | egrep "(OpenGL vendor|OpenGL renderer|OpenGL version)" OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 1660 Ti/PCIe/SSE2 OpenGL version string: 4.6.0 NVIDIA 450.66 meloli@Asus-A17:~$ glxinfo | egrep "(OpenGL vendor|OpenGL renderer|OpenGL version)" OpenGL vendor string: X.Org OpenGL renderer string: AMD RENOIR (DRM 3.38.0, 5.8.8-050808-generic, LLVM 10.0.0) OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.8 meloli@Asus-A17:~$ nvidia-settings (nvidia-settings:29678): GLib-GObject-CRITICAL **: 18:02:06.777: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ERROR: nvidia-settings could not find the registry key file. This file should have been installed along with this driver at /usr/share/nvidia/nvidia-application-profiles-key-documentation. The application profiles will continue to work, but values cannot be prepopulated or validated, and will not be listed in the help text. Please see the README for possible values and descriptions. ** Message: 18:02:06.835: PRIME: No offloading required. Abort ** Message: 18:02:06.835: PRIME: is it supported? no meloli@Asus-A17:~$ apt-cache policy nvidia-driver-450 nvidia-driver-450: Installé : 450.66-0ubuntu0.20.04.1 Candidat : 450.66-0ubuntu0.20.04.1 Table de version : *** 450.66-0ubuntu0.20.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1895327/+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 1903217] Re: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope
I am running Ubuntu as part of dual boot so if there is anything I can copy over or run from ChromeOS to provide more information please let me know, this is the output from dmesg in ChromeOS in developer mode, hopefully its useful in understanding what's missing chronos@localhost / $ dmesg [0.00] microcode: microcode updated early to revision 0xd6, date = 2020-04-27 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.232-19103-g45c370e0810f (chrome-bot@chromeos-ci-legacy-us-central2-d-x32-38-6tbk) (Chromium OS 11.0_pre394483_p20200618-r9 clang version 11.0.0 (/var/cache/chromeos-cache/distfiles/egit-src/llvm-project b726d071b4aa46004228fc38ee5bfd167f999bfe)) #1 SMP PREEMPT Sun Nov 1 19:51:22 PST 2020 [0.00] Command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure drm.trace=0x106 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 4710400 verity payload=PARTUUID=888936ea-0bef-2f4d-af0b-a6c2da398a8b/PARTNROFF=1 hashtree=PARTUUID=888936ea-0bef-2f4d-af0b-a6c2da398a8b/PARTNROFF=1 hashstart=4710400 alg=sha256 root_hexdigest=ffabf6b54172c1cfe99119a3d8b21adbcd000aa09335e87c463b367629a59da8 salt=e555f7f66570d372f51db8d2846e893df6243ac8fc1cfec41e953bfa234b0244" noinitrd vt.global_cursor_default=0 kern_guid=888936ea-0bef-2f4d-af0b-a6c2da398a8b add_efi_memmap boot=local noresume noswap i915.modeset=1 nmi_watchdog=panic,lapic intel_idle.slp_s0_check=1 gsmi.s0ix_logging_enable=1 disablevmx=off [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: xstate_offset[3]: 960, xstate_sizes[3]: 64 [0.00] x86/fpu: xstate_offset[4]: 1024, xstate_sizes[4]: 64 [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers' [0.00] x86/fpu: Supporting XSAVE feature 0x08: 'MPX bounds registers' [0.00] x86/fpu: Supporting XSAVE feature 0x10: 'MPX CSR' [0.00] x86/fpu: Enabled xstate features 0x1f, context size is 1088 bytes, using 'standard' format. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0fff] type 16 [0.00] BIOS-e820: [mem 0x1000-0x0009] usable [0.00] BIOS-e820: [mem 0x000a-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x7a986fff] usable [0.00] BIOS-e820: [mem 0x7a987000-0x7aff] type 16 [0.00] BIOS-e820: [mem 0x7b00-0x7fff] reserved [0.00] BIOS-e820: [mem 0xe000-0xe3ff] reserved [0.00] BIOS-e820: [mem 0xfe00-0xfe00] reserved [0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved [0.00] BIOS-e820: [mem 0xfed8-0xfed84fff] reserved [0.00] BIOS-e820: [mem 0xfed9-0xfed91fff] reserved [0.00] BIOS-e820: [mem 0x0001-0x00027eff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.7 present. [0.00] DMI: Google Nami/Nami, BIOS Google_Nami.10775.108.31 09/19/2019 [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] e820: last_pfn = 0x27f000 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-F write-back [0.00] MTRR variable ranges enabled: [0.00] 0 base 00 mask 7F8000 write-back [0.00] 1 base 007B80 mask 7FFF80 uncachable [0.00] 2 base 007C00 mask 7FFC00 uncachable [0.00] 3 base 00C000 mask 7FF000 write-combining [0.00] 4 base 01 mask 7F write-back [0.00] 5 base 02 mask 7F8000 write-back [0.00] 6 disabled [0.00] 7 disabled [0.00] 8 disabled [0.00] 9 disabled [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: last_pfn = 0x7a987 max_arch_pfn = 0x4 [0.00] Scanning 1 areas for low memory corruption [0.00] Base memory trampoline at [88098000] 98000 size 28672 [0.00] Using GB pages for direct mapping [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000F 24 (v02 CORE ) [0.00] ACPI: XSDT 0x7AA990E0 64 (v01 CORE COREBOOT CORE
[Kernel-packages] [Bug 1903048] Re: Bluetooth won't activate on the pi 400
** Tags added: fr-901 -- 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/1903048 Title: Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: New Bug description: The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1903217] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432014/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432015/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432016/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432017/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432012/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432008/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432007/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432004/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432009/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] Re: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope
apport information ** Tags added: apport-collected groovy ** Description changed: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckMismatches: ./casper/filesystem.squashfs + CasperMD5CheckResult: skip + CasperVersion: 1.455 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + Lsusb: + Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera + Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Google Nami + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- + ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-25-generic N/A + linux-backports-modules-5.8.0-25-generic N/A + linux-firmware1.190 + Tags: groovy + Uname: Linux 5.8.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/19/2019 + dmi.bios.release: 4.0 + dmi.bios.vendor: coreboot + dmi.board.name: Nami + dmi.board.vendor: Google + dmi.board.version: 1.0 + dmi.chassis.type: 3 + dmi.chassis.vendor: Google + dmi.ec.firmware.release: 0.0 + dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: + dmi.product.family: Google_Nami + dmi.product.name: Nami + dmi.product.sku: sku16227 + dmi.product.version: 1.0 + dmi.sys.vendor: Google ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432000/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Kernel-packages] [Bug 1903217] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432003/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432011/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432006/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432013/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432010/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432005/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432002/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1903217] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1903217/+attachment/5432001/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nami NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.board.name: Nami dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nami dmi.product.name: Nami dmi.product.sku: sku16227 dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1832472] Re: cdc_ncm floods syslog unneccessarily
Chrome OS also can't support RTL8156 until this is fixed. Every kernel version Chrome OS uses spams /var/log/syslog with ~30 messages/second (~200MB/day or ~1GB/week). We can not use the Realtek "proprietary" (though open source) driver. Realtek needs to look at this and I've contacted Realtek directly about this. I can't determine what is triggering the repeated link status messages from USB CDC specs. From what I understand in the spec, USB_CDC_NOTIFY_SPEED_CHANGE and USB_CDC_NOTIFY_NETWORK_CONNECTION (in that order) messages should only be sent once after device is enumerated and again when link state actually changes. This is in fact how cdc_ether devices behave using the same messages. -- 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/1832472 Title: cdc_ncm floods syslog unneccessarily Status in linux package in Ubuntu: Confirmed Bug description: Upon plugging in a USB adapter for NBase-T ethernet with an Realtek chip RTL8156 the kernel module cdc_ncm starts flooding /var/log/syslog with unneccessary status info. The status lines either say that there's no ethernet link or show the interface as connected and state the link speed. The relevant parts from /var/log/syslog after attaching the adapter without ethernet link read like this: [...] Jun 12 10:48:58 resdz-v13 kernel: [ 4240.398485] usb 2-3: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419463] usb 2-3: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=30.00 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419469] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419472] usb 2-3: Product: USB 10/100/1G/2.5G LAN Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419475] usb 2-3: Manufacturer: Realtek Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419477] usb 2-3: SerialNumber: 1 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447769] cdc_ncm 2-3:2.0: MAC-Address: 00:13:3b:68:00:e9 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447775] cdc_ncm 2-3:2.0: setting rx_max = 16384 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447929] cdc_ncm 2-3:2.0: setting tx_max = 16384 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.448901] cdc_ncm 2-3:2.0 usb0: register 'cdc_ncm' at usb-:00:14.0-3, CDC NCM, 00:13:3b:68:00:e9 Jun 12 10:48:58 resdz-v13 NetworkManager[916]: [1560329338.1872] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/8) Jun 12 10:48:58 resdz-v13 mtp-probe: checking bus 2, device 5: "/sys/devices/pci:00/:00:14.0/usb2/2-3" Jun 12 10:48:58 resdz-v13 mtp-probe: bus: 2, device: 5 was not an MTP device Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: Using default interface naming scheme 'v240'. Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Jun 12 10:48:58 resdz-v13 kernel: [ 4240.466476] cdc_ncm 2-3:2.0 enx00133b6800e9: renamed from usb0 Jun 12 10:48:58 resdz-v13 NetworkManager[916]: [1560329338.2315] device (usb0): interface index 7 renamed iface from 'usb0' to 'enx00133b6800e9' Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: Process 'vlan-network-interface UDEV' failed with exit code 1. Jun 12 10:48:58 resdz-v13 NetworkManager[916]: [1560329338.2431] device (enx00133b6800e9): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jun 12 10:48:58 resdz-v13 charon: 12[KNL] interface enx00133b6800e9 activated Jun 12 10:48:58 resdz-v13 mtp-probe: checking bus 2, device 5: "/sys/devices/pci:00/:00:14.0/usb2/2-3" Jun 12 10:48:58 resdz-v13 mtp-probe: bus: 2, device: 5 was not an MTP device Jun 12 10:48:58 resdz-v13 kernel: [ 4240.524052] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected Jun 12 10:48:58 resdz-v13 kernel: [ 4240.556109] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected Jun 12 10:48:58 resdz-v13 kernel: [ 4240.588054] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected Jun 12 10:48:58 resdz-v13 kernel: [ 4240.620383] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected Jun 12 10:48:58 resdz-v13 kernel: [ 4240.652415] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected [...] Upon plugging in the ethernet cable I see [...] Jun 12 10:49:01 resdz-v13 kernel: [ 4243.372273] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink Jun 12 10:49:01 resdz-v13 kernel: [ 4243.404278] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected [...] and Network Manager starts its work. After the interface is up the flooding continues: [...] Jun 12 10:49:01 resdz-v13 kernel: [ 4243.564056] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink Jun 12 10:49:01
[Kernel-packages] [Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
Hi, Feng Can you, please, give me some instructions on how to download and run the code from these patches? Thank you! -- 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/1872984 Title: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic Status in linux package in Ubuntu: Incomplete Bug description: RTL8822BE crashes after rtw_pci starts on boot after kernel update to 5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is still present on latest mainline kernel version 5.7.0-050700rc1-generic . [ 10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0 [ 10.714544] [ cut here ] [ 10.714545] failed to read DBI register, addr=0x0719 [ 10.714577] WARNING: CPU: 0 PID: 939 at drivers/net/wireless/realtek/rtw88/pci.c:1156 rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714577] Modules linked in: (see attached dmesg) [ 10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 5.7.0-050700rc1-generic #202004122032 [ 10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 01/23/2018 [ 10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00 [ 10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282 [ 10.714618] RAX: RBX: RCX: 0007 [ 10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80 [ 10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004 [ 10.714620] R10: R11: 0001 R12: 933cbdf31ea0 [ 10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: [ 10.714622] FS: 7fbcedc6efc0() GS:933cc9e0() knlGS: [ 10.714622] CS: 0010 DS: ES: CR0: 80050033 [ 10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0 [ 10.714623] Call Trace: [ 10.714627] rtw_pci_link_ps+0x4e/0x90 [rtwpci] [ 10.714630] ? _raw_spin_unlock_bh+0x1e/0x20 [ 10.714637] rtw_leave_ips+0x1f/0x80 [rtw88] [ 10.714640] rtw_ops_config+0xa3/0xe0 [rtw88] [ 10.714658] ieee80211_hw_config+0x95/0x390 [mac80211] [ 10.714669] ieee80211_recalc_idle+0x27/0x30 [mac80211] [ 10.714679] __ieee80211_start_scan+0x334/0x750 [mac80211] [ 10.714688] ieee80211_request_scan+0x30/0x50 [mac80211] [ 10.714699] ieee80211_scan+0x5c/0xa0 [mac80211] [ 10.714719] nl80211_trigger_scan+0x59a/0x6c0 [cfg80211] [ 10.714722] genl_rcv_msg+0x1a8/0x470 [ 10.714724] ? ep_poll_callback+0x2a0/0x2c0 [ 10.714725] ? genl_family_rcv_msg_attrs_parse+0x100/0x100 [ 10.714726] netlink_rcv_skb+0x50/0x120 [ 10.714728] genl_rcv+0x29/0x40 [ 10.714729] netlink_unicast+0x1a8/0x250 [ 10.714730] netlink_sendmsg+0x233/0x460 [ 10.714739] ? _copy_from_user+0x31/0x60 [ 10.714750] sock_sendmsg+0x65/0x70 [ 10.714751] sys_sendmsg+0x212/0x280 [ 10.714752] ? copy_msghdr_from_user+0x5c/0x90 [ 10.714755] ? __check_object_size+0x4d/0x150 [ 10.714756] ___sys_sendmsg+0x81/0xc0 [ 10.714757] ? __check_object_size+0x4d/0x150 [ 10.714759] ? unix_ioctl+0x99/0x180 [ 10.714760] ? sock_getsockopt+0x198/0xc04 [ 10.714761] ? sock_do_ioctl+0x47/0x140 [ 10.714763] ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0 [ 10.714765] ? _cond_resched+0x19/0x30 [ 10.714767] ? aa_sk_perm+0x43/0x1b0 [ 10.714768] __sys_sendmsg+0x5c/0xa0 [ 10.714770] __x64_sys_sendmsg+0x1f/0x30 [ 10.714772] do_syscall_64+0x57/0x1b0 [ 10.714773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 10.714774] RIP: 0033:0x7fbcedffb5b7 [ 10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 002e [ 10.714777] RAX: ffda RBX: 5632787355d0 RCX: 7fbcedffb5b7 [ 10.714777] RDX: RSI: 7fff88e222c0 RDI: 0006 [ 10.714778] RBP: 563278761380 R08: 0004 R09: 563278761380 [ 10.714778] R10: 7fff88e22394 R11: 0246 R12: 5632787354e0 [ 10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 563278766710 [ 10.714780] ---[ end trace f00c16109236af6f ]--- [ 10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5 Device is unable to scan for networks and error
[Kernel-packages] [Bug 1902957] Re: Update kernel packaging to support forward porting kernels
** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902957 Title: Update kernel packaging to support forward porting kernels Status in linux package in Ubuntu: In Progress Status in linux source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: In Progress Bug description: SRU Justification Impact: Our kernel packaging currently has support for backporting kernels to older releases. This includes appending ~BACKPORT_SUFFIX to the version string for the backport kernel, where BACKPORT_SUFFIX is defined in update.conf. We need to start doing similar forward ported kernels, but BACKPORT_SUFFIX should be appended using a + rather than a ~. Our kernel packaging cannot easily determine whether a + or a ~ is appropriate. Fix: Move the leading character into BACKPORT_SUFFIX, and do not insert any leading characters from the kernel packaging scripts. Since the script which generates update.conf has access to information from kernel-series, it can more easily determine whether + or ~ is the appropriate leader. Test Case: Run through the normal steps for updating a backport kernel. The version string generated should have ~SERIES for a backport to an older series, and +SERIES for a backport to a newer series. Regression Potential: Backport kernels could end up with an incorrect version strings. Since all kernel uploads undergo review, any such errors should be caught before uploading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902957/+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 1902926] Re: aws: improve hibernation reliability in groovy
** Changed in: linux-aws (Ubuntu Groovy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1902926 Title: aws: improve hibernation reliability in groovy Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Groovy: Fix Committed Bug description: [Impact] The 5.8 kernel (groovy) is not still 100% reliable with hibernation, especially on the Xen instance type. However, re-aligning the config options as much as possible with the 5.4 kernel (focal) allows to hibernate and resume with a success rate close to 100% (according to our tests on the AWS cloud). [Test case] - spin up an AWS instance (for example a c4.8xlarge instance type) - run a memory stress test - hibernate - resume - verify that the system has been resumed correctly and the memory stress test is still running [Fix] The following fixes must be applied to improve hibernation/resume reliability: - disable CONFIG_SUSPEND (suspend to memory is not supported in AWS and it can introduce a deadlock condition with the Xen hibernation layer) - make sure CONFIG_DMA_CMA is disabled (this introduces another deadlock condition with Xen) - disable CONFIG_FB_HYPERV: this would enable CONFIG_DMA_CMA and we dont' want that (to prevent the Xen deadlock); moreover this driver is not needed at all in the AWS environment - disable CONFIG_XEN_FBDEV_FRONTEND: this is also not required in the AWS environement and it has the potential of breaking hibernation - disable CONFIG_INPUT_XEN_KBDDEV_FRONTEND - compile xen-netfront as module - disable CONFIG_XEN_BALLOON - remove all sound-related modules (not really needed in the AWS cloud, they were also disabled on 5.4) [Regression potential] These are all .config changes. With these changes we are basically re-aligning with the previous 5.4 settings and we have experimentally verified (tests) that these changes are increasing the success rate of hibernation. So the regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1902926/+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 1732512] Re: xen hibernation support for linux-aws
** Changed in: linux-aws (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1732512 Title: xen hibernation support for linux-aws Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Trusty: Fix Released Status in linux-aws source package in Xenial: Fix Released Status in linux-aws source package in Groovy: Fix Committed Bug description: linux-aws needs multiple commits from mainline and Amazon Linux to support xen hibernation: UBUNTU: aws: [Config] disable SUSPEND UBUNTU: aws: [Config] disable XEN_FBDEV_FRONTEND, xen: move xen_setup_runstate_info and get_runstate_snapshot to (cherry picked from commit 4ccefbe597392d2914cf7ad904e33c734972681d) xen/time: use READ_ONCE (cherry picked from commit 2dd887e32175b624375570a0361083eb2cd64a07) xen: add steal_clock support on x86 (back-ported from commit ecb23dc6f2eff0ce64dd60351a81f376f13b12cc) xen: support runqueue steal time on xen (cherry picked from commit 6ba286ad845799b135e5af73d1fbc838fa79f709) x86/xen: use xen_vcpu_id mapping for HYPERVISOR_vcpu_op (cherry picked from commit ad5475f9faf5186b7f59de2c6481ee3e211f1ed7) xen: add static initialization of steal_clock op to xen_time_ops (cherry picked from commit d34c30cc1fa80f509500ff192ea6bc7d30671061) x86/xen: update cpuid.h from Xen-4.7 (cherry picked from commit de2f5537b397249e91cafcbed4de64a24818542e) x86/acpi: store ACPI ids from MADT for future usage (cherry picked from commit 3e9e57fad3d8530aa30787f861c710f598ddc4e7) xen: introduce xen_vcpu_id mapping (back-ported from commit 88e957d6e47f1232ad15b21e54a44f1147ea8c1b) xen: update xen headers (cherry picked from commit 7ba8dba95cb227eb6c270b1aa77f942e45f5e47c) xen: change the type of xen_vcpu_id to uint32_t (cherry picked from commit 55467dea2967259f21f4f854fc99d39cc5fea60e) xen/blkfront: separate per ring information out of device info (cherry picked from commit 81f351615772365d46ceeac3e50c9dd4e8f9dc89) xen/blkfront: pseudo support for multi hardware queues/rings (cherry picked from commit 3df0e5059908b8fdba351c4b5dd77caadd95a949) xen/blkfront: split per device io_lock (cherry picked from commit 11659569f7202d0cb6553e81f9b8aa04dfeb94ce) xen/blkfront: negotiate number of queues/rings to be used with (cherry picked from commit 28d949bcc28bbc2d206f9c3f69b892575e81c040) xen/blkfront: Cleanup of comments, fix unaligned variables, and (cherry picked from commit 6f03a7ff89485f0a7a559bf5c7631d2986c4ecfa) xen/blkfront: Remove duplicate setting of ->xbdev. (cherry picked from commit 75f070b3967b0c3bf0e1bc43411b06bab6c2c2cd) xen/blkfront: make persistent grants pool per-queue (cherry picked from commit 73716df7da4f60dd2d59a9302227d0394f1b8fcc) xen/blkfront: correct setting for xen_blkif_max_ring_order (cherry picked from commit 45fc82642e54018740a25444d1165901501b601b) xen/blkfront: realloc ring info in blkif_resume (cherry picked from commit 3db70a853202c252a8ebefa71ccb088ad149cdd2) blk-mq: dynamic h/w context count (back-ported from commit 868f2f0b72068a097508b6e8870a8950fd8eb7ef) xen-blkfront: save uncompleted reqs in blkfront_resume() (cherry picked from commit 7b427a59538a98161321aa46c13f4ea81b43f4eb) xen-blkfront: fix places not updated after introducing 64KB page (cherry picked from commit 6c647b0eb01cd7326dca093590f5e123e3c68b9c) blk-mq: mark request queue as mq asap (cherry picked from commit 66841672161efb9e3be4a1dbd9755020bb1d86b7) blk-mq: Fix NULL pointer updating nr_requests (cherry picked from commit e9137d4b93078b6a9965acfb18a2a2ad91cf8405) xen-blkfront: fix resume issues after a migration (cherry picked from commit 2a6f71ad99cabe436e70c3f5fcf58072cb3bc07f) xen-blkfront: introduce blkif_set_queue_limits() (back-ported from commit 172335ada40ce26806e514c83a504b45c14a4139) xen/pvhvm: run xen_vcpu_setup() for the boot CPU (cherry picked from commit ee42d665d3f5db975caf87baf101a57235ddb566) UBUNTU: SAUCE: [aws] xen/manage: keep track of the on-going suspend UBUNTU: SAUCE: [aws] xen/manage: introduce helper function to know UBUNTU: SAUCE: [aws] xenbus: add freeze/thaw/restore callbacks UBUNTU: SAUCE: [aws] x86/xen: decouple shared_info mapping from UBUNTU: SAUCE: [aws] x86/xen: add system core suspend and resume UBUNTU: SAUCE: [aws] xen/time: introduce UBUNTU: SAUCE: [aws] x86/xen: save and restore steal clock UBUNTU: SAUCE: [aws] xen/events: add xen_shutdown_pirqs helper UBUNTU: SAUCE: [aws] x86/xen: close event channels for PIRQs in UBUNTU: SAUCE: [aws] xen-netfront: add callbacks for PM suspend and UBUNTU: SAUCE: [aws] xen-blkfront: add callbacks for PM suspend and UBUNTU: SAUCE: [aws]
[Kernel-packages] [Bug 1866149] Re: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl
This is causing LXD VMs (Focal, possibly others) to boot in "degraded" state, see [1]. The underlying cause is: root@paride-f-delme:~# systemctl status systemd-sysctl.service ● systemd-sysctl.service - Apply Kernel Variables Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-11-06 16:43:35 UTC; 14min ago Docs: man:systemd-sysctl.service(8) man:sysctl.d(5) Main PID: 301 (code=exited, status=1/FAILURE) root@paride-f-delme:~# /lib/systemd/systemd-sysctl Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Couldn't write '4194304' to 'kernel/pid_max': Invalid argument [1] https://paste.ubuntu.com/p/TQhpFWYzK7/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1866149 Title: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl Status in linux-kvm package in Ubuntu: Confirmed Bug description: I'm not completely sure which package to log this against. I'm running the kvm focal minimal cloud image from 20200302. I noticed on boot that there was an error complaining that systemd-systemctl couldn't update pid_max to the value it wanted: systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf: # Bump the numeric PID range to its maximum of 2^22 (from the in-kernel default # of 2^16), to make PID collisions less likely. kernel.pid_max = 4194304 However, the linux-image-kvm kernel is compiled with CONFIG_BASE_SMALL=1 and this triggers the following code in include/linux/threads.h #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \ (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT)) which means that if CONFIG_BASE_SMALL is set we get a maximum limit of PAGE_SIZE * 8, which on x86 would be 32768. As a workaround I can override it with a file in /etc/sysctl.d/ but this shouldn't be needed. I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud images, they really aren't small machines in the scheme of things! Cheers David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1866149/+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 1879711] Re: aws: disable CONFIG_DMA_CMA
** Changed in: linux-aws (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1879711 Title: aws: disable CONFIG_DMA_CMA Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Eoan: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux-aws source package in Groovy: Fix Committed Bug description: [Impact] The option CONFIG_DMA_CMA seems to cause hibernation failures on the t2.* instance types (Xen). With this option enabled device drivers are allowed to use the Contiguous Memory Allocator (CMA) for DMA operations. So, drivers can allocate large physically-contiguous blocks of memory, instead of relying on the I/O map or scatter-gather support. However, on resume, the memory used by DMA needs to be re-initialized / re-allocated, but it may fail to allocate large chunks of contiguous memory due to the fact that we also need to restore the hibernation image, using more memory and causing a system hang during the resume process. [Test case] Hibernate / resume any t2.* instance (especially t2.nano, where the problem seems to happen 100% of the times after 2 consecutive hibernate/resume cycles). [Fix] Disable CONFIG_DMA_CMA. NOTE: this option is already disabled in the generic kernel (see LP: #1362261). With this option disabled the success rate of hibernation on the t2.* instance types during our tests jumped to 100%. [Regression potential] It is a .config change, no regression potential except for the fact that disabling this option also disables the module 'etnaviv' (Vivante graphic card), that is not really needed in the aws kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1879711/+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 1903309] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1903309 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903309 Title: wifi not working properly after upgrade to 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Wifi keeps turning off! On 18.04 there was no problem with RTL8821CE and wifi worked fine and stable. network description: Wireless interface product: RTL8821CE 802.11ac PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: a4:fc:77:79:6a:05 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtl8821ce ip=192.168.1.8 latency=0 multicast=yes wireless=IEEE 802.11bgn resources: irq:130 ioport:3000(size=256) memory:a110-a110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903309/+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 1903309] Re: wifi not working properly after upgrade to 20.04
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903309 Title: wifi not working properly after upgrade to 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Wifi keeps turning off! On 18.04 there was no problem with RTL8821CE and wifi worked fine and stable. network description: Wireless interface product: RTL8821CE 802.11ac PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: a4:fc:77:79:6a:05 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtl8821ce ip=192.168.1.8 latency=0 multicast=yes wireless=IEEE 802.11bgn resources: irq:130 ioport:3000(size=256) memory:a110-a110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903309/+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 1894896] Re: [linux-azure][hibernation] Mellanox CX4 NIC's TX/RX packets stop increasing after hibernation/resume
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1894896 Title: [linux-azure][hibernation] Mellanox CX4 NIC's TX/RX packets stop increasing after hibernation/resume Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Focal: Fix Committed Bug description: [Impact] Description of problem: In a VM with CX4 VF NIC on Azure, after hibernation/resume, the TX/RX packet counters stop increaseing. This issue doesn't exist in VM with a CX3 VF NIC. This happens to the latest stable release of the linux-azure 5.4.0-1023.23 kernel and the latest mainline linux kernel. [Test Case] How reproducible: 100% Steps to Reproduce: 1. Start a VM in Azure that supports Accelerated Networking, and enable hibernation properly (please refer to https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 ). Please make sure the VF NIC is CX-4 since the issue doesn't happen to CX-3. 2. Do hibernation from serial console # systemctl hibernate 3. After the VM resumes back, check the MSI interrupt counters in /proc/interrupts for the CX-4 NIC, and also check “ifconfig” (e.g. “ifconfig enP2642s2”) for the RX/TX counters. These counters stop increasing while they should. [Regression Potential] The change touches netvsc and has potential to affect any instances using accelerated networking. However the fix is straightforward and it's a clean cherry-pick from 5.9. [Other Info] BUG FIX: The fix is in the net.git tree now: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=19162fd4063a3211843b997a454b505edb81d5ce To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1894896/+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 1903309] [NEW] wifi not working properly after upgrade to 20.04
You have been subscribed to a public bug: Wifi keeps turning off! On 18.04 there was no problem with RTL8821CE and wifi worked fine and stable. network description: Wireless interface product: RTL8821CE 802.11ac PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: a4:fc:77:79:6a:05 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtl8821ce ip=192.168.1.8 latency=0 multicast=yes wireless=IEEE 802.11bgn resources: irq:130 ioport:3000(size=256) memory:a110-a110 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment problem wifi -- wifi not working properly after upgrade to 20.04 https://bugs.launchpad.net/bugs/1903309 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897942] Re: crash on brcmfmac
Other log: ```log Nov 6 16:31:11 leon-dev-pi kernel: [ 2217.732283] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout Nov 6 16:31:11 leon-dev-pi kernel: [ 2217.738536] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle Nov 6 16:31:11 leon-dev-pi kernel: [ 2217.745435] brcmfmac: dongle trap info: type 0x4 @ epc 0x0007a094 Nov 6 16:31:11 leon-dev-pi kernel: [ 2217.745435] cpsr 0x619f spsr 0x61bf sp 0x0025f888 Nov 6 16:31:11 leon-dev-pi kernel: [ 2217.745435] lr 0x0007a093 pc 0x0007a094 offset 0x25f830 Nov 6 16:31:11 leon-dev-pi kernel: [ 2217.745435] r0 0x0036 r1 0x0005 r2 0x r3 0x0001 Nov 6 16:31:11 leon-dev-pi kernel: [ 2217.745435] r4 0x002494d0 r5 0x r6 0x00249460 r7 0x0004 Nov 6 16:31:14 leon-dev-pi kernel: [ 2220.288341] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout Nov 6 16:31:14 leon-dev-pi kernel: [ 2220.294749] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle Nov 6 16:31:14 leon-dev-pi kernel: [ 2220.301905] brcmfmac: dongle trap info: type 0x4 @ epc 0x0007a094 Nov 6 16:31:14 leon-dev-pi kernel: [ 2220.301905] cpsr 0x619f spsr 0x61bf sp 0x0025f888 Nov 6 16:31:14 leon-dev-pi kernel: [ 2220.301905] lr 0x0007a093 pc 0x0007a094 offset 0x25f830 Nov 6 16:31:14 leon-dev-pi kernel: [ 2220.301905] r0 0x0036 r1 0x0005 r2 0x r3 0x0001 Nov 6 16:31:14 leon-dev-pi kernel: [ 2220.301905] r4 0x002494d0 r5 0x r6 0x00249460 r7 0x0004 Nov 6 16:31:14 leon-dev-pi kernel: [ 2220.301919] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110 ``` -- 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/1897942 Title: crash on brcmfmac Status in linux-firmware package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-raspi source package in Focal: New Bug description: I have Ubuntu 20.04 64bit, ubuntu desktop, network-manager on RPI4 8GB wifi work well for some time but then all gone very slow and system is unusable. to me it seems a brcmfmac module problem. My power configuration do not go well if switch off "wi-fi can be turn off to power save": all wifi crash. Rest of my power conf: automatic suspend = no action on turn off supply button = nothing black screen = never To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1897942/+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 1899993] Re: EFI: Fails when BootCurrent entry does not exist
** Description changed: [Impact] MAAS installs fail on systems that have EFI Variables that include a "/" in the name. Split out of bug 1894217. [Test Case] $ ls /sys/firmware/efi/efivars | grep ^Boot ls: reading directory '/sys/firmware/efi/efivars': Input/output error Boot mode select-7683c190-9523-4402-81ff-a11e93dc389c Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c - The Input/output error is the key symptom. + The Input/output error is the key symptom. See below to see how that + percolates up to MAAS install failures. [Regression Risk] There's a very tiny chance that someone has written code that depends on an the -EIO error for some reason. It's hard to guess why such a script would do that. -- 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/183 Title: EFI: Fails when BootCurrent entry does not exist Status in curtin package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in curtin source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in curtin source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Status in curtin source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in curtin source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in curtin source package in Hirsute: Invalid Status in linux source package in Hirsute: In Progress Bug description: [Impact] MAAS installs fail on systems that have EFI Variables that include a "/" in the name. Split out of bug 1894217. [Test Case] $ ls /sys/firmware/efi/efivars | grep ^Boot ls: reading directory '/sys/firmware/efi/efivars': Input/output error Boot mode select-7683c190-9523-4402-81ff-a11e93dc389c Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c The Input/output error is the key symptom. See below to see how that percolates up to MAAS install failures. [Regression Risk] There's a very tiny chance that someone has written code that depends on an the -EIO error for some reason. It's hard to guess why such a script would do that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/183/+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 1903293] Re: Avoid double newline when running insertchanges
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903293 Title: Avoid double newline when running insertchanges Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: In Progress Bug description: [Impact] When preparing derivative kernels and inserting master kernel changes, if the derivative has not changes on its own, we end up with two empty lines, which is caught up by verify-release-ready. [Test case] Run cranky-close with derivative changes and no derivative changes. [Regression Potential] We could break changelogs, or the kernel preparation altogether. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903293/+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 1903048] Re: Bluetooth won't activate on the pi 400
The attachment "lp1903048.debdiff" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/1903048 Title: Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: New Bug description: The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1899993] Re: EFI: Fails when BootCurrent entry does not exist
** Description changed:
+ [Impact]
+ MAAS installs fail on systems that have EFI Variables that include a "/" in
the name.
+
Split out of bug 1894217.
- We're seeing a situation where curtin fails when the variable
- BootCurrent references does not exist.
+ [Test Case]
+ $ ls /sys/firmware/efi/efivars | grep ^Boot
+ ls: reading directory '/sys/firmware/efi/efivars': Input/output error
+ Boot mode select-7683c190-9523-4402-81ff-a11e93dc389c
+ Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c
+ BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c
+ BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c
+ BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
- At boot, efibootmgr -v shows:
+ The Input/output error is the key symptom.
- BootCurrent: 0003
- Timeout: 10 seconds
- BootOrder: 0003,0004,0005,0006,0001
-
- Note that there are actually no individual boot entries in this output.
- BootCurrent and BootOrder are referencing Boot entries that do not
- apepar to exist.
-
- Later, curtin tries to set a new BootOrder that places the value of
- BootCurrent at the front. This causes efibootmgr to error out,
- apparently escalating to an installation failure:
-
- UEFI efibootmgr output after install:
- {'current': '0003', 'timeout': '10 seconds', 'order': [''],
'entries': {'': {'name
- ': 'ubuntu', 'path':
'HD(1,GPT,0937ffdf-628c-4161-8b2f-5920235669c6,0x800,0x10)/File(\\EFI\\ub
- untu\\shimx64.efi)'}}}
- Setting currently booted 0003 as the first UEFI loader.
- New UEFI boot order: 0003,
- Running command ['mount', '--bind', '/dev',
'/tmp/tmp6ha4_iz2/target/dev'] with allowed re
- turn codes [0] (capture=False)
- Running command ['mount', '--bind', '/proc',
'/tmp/tmp6ha4_iz2/target/proc'] with allowed
- return codes [0] (capture=False)
- Running command ['mount', '--bind', '/run',
'/tmp/tmp6ha4_iz2/target/run'] with allowed re
- turn codes [0] (capture=False)
- Running command ['mount', '--bind', '/sys',
'/tmp/tmp6ha4_iz2/target/sys'] with allowed re
- turn codes [0] (capture=False)
- Running command ['mount', '--bind', '/sys/firmware/efi/efivars',
'/tmp/tmp6ha4_iz2/target/
- sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
- Running command ['unshare', '--fork', '--pid', '--', 'chroot',
'/tmp/tmp6ha4_iz2/target',
- 'efibootmgr', '-o', '0003,'] with allowed return codes [0] (capture=False)
- Invalid BootOrder order entry value0003
- ^
- efibootmgr: entry 0003 does not exist
+ [Regression Risk]
+ There's a very tiny chance that someone has written code that depends on an
the -EIO error for some reason. It's hard to guess why such a script would do
that.
--
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/183
Title:
EFI: Fails when BootCurrent entry does not exist
Status in curtin package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
In Progress
Status in curtin source package in Xenial:
Invalid
Status in linux source package in Xenial:
Fix Committed
Status in curtin source package in Bionic:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in curtin source package in Focal:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in curtin source package in Groovy:
Invalid
Status in linux source package in Groovy:
Fix Committed
Status in curtin source package in Hirsute:
Invalid
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
MAAS installs fail on systems that have EFI Variables that include a "/" in
the name.
Split out of bug 1894217.
[Test Case]
$ ls /sys/firmware/efi/efivars | grep ^Boot
ls: reading directory '/sys/firmware/efi/efivars': Input/output error
Boot mode select-7683c190-9523-4402-81ff-a11e93dc389c
Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
The Input/output error is the key symptom. See below to see how that
percolates up to MAAS install failures.
[Regression Risk]
There's a very tiny chance that someone has written code that depends on an
the -EIO error for some reason. It's hard to guess why such a script would do
that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/183/+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 1903048] Re: Bluetooth won't activate on the pi 400
@henry-sprog yup, that looks like the same Attached a patch to fix this in hirsute; once landed will SRU this to groovy and earlier. ** Patch added: "lp1903048.debdiff" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+attachment/5431962/+files/lp1903048.debdiff -- 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/1903048 Title: Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: New Bug description: The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1881757] Re: webcam is detected but not working with kernel 5.4.0.33
broken again on the latest kernel update 5.4.0-52-generic (why fix when all it does id break on the next update) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1881757 Title: webcam is detected but not working with kernel 5.4.0.33 Status in linux-signed package in Ubuntu: Fix Released Bug description: webcam is detected not working under kernel 5.4.0.33 and 5.4.0.31 . The webcam is functional with kernels 5.0 and 5.6.15 . -usb:1 description: Video product: USB 2.0 Web Camera vendor: Alcor Micro, Corp. physical id: 2 bus info: usb@1:1.2 version: 0.08 capabilities: usb-2.00 configuration: driver=uvcvideo maxpower=200mA speed=480Mbit/s susb; lsb_release -a; uname -a Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1d0b:0021 HAN HUA CABLE & WIRE TECHNOLOGY (J.X.) CO., LTD. Bus 001 Device 003: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux afsal-Excelance 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux more info : https://answers.launchpad.net/ubuntu/+question/691070 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1881757/+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 1903048] Re: Bluetooth won't activate on the pi 400
Is this the same as: #1903286? -- 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/1903048 Title: Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: New Bug description: The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1835660] Re: initramfs unpacking failed
Dziękuję za zainteresowanie. Aktualnie mój HP 8760 nie działa, więc jak dla mnie problem z Ubuntu 20.04 stał się nieistotny. Jeszcze raz dziękuję i pozdrawiam ekipę Ubuntu. Tomek P. 2020-11-06 12:18 GMT+01:00, archi02 <1835...@bugs.launchpad.net>: > Same issue here and no workaround works : neither switching from lz4 to > gzip nor keeping lz4 and only update initramfs. I also tried to launch > with another kernel, without success. > > The computer is now blocked (Xubuntu 20.04, fresh install). I really > don't want to reinstall 18.04. > > What can I do ? Any idea will be welcome ! :) > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1900130). > https://bugs.launchpad.net/bugs/1835660 > > Title: > initramfs unpacking failed > > Status in OEM Priority Project: > New > Status in initramfs-tools package in Ubuntu: > Invalid > Status in linux package in Ubuntu: > Confirmed > > Bug description: > "initramfs unpacking failed: Decoding failed", message appears on > boot up. > > If I "update-initramfs" using gzip instead of lz, then boot up passes > without decoding failed message. > > --- > > However, we currently believe that the decoding error reported in > dmesg is actually harmless and has no impact on usability on the > system. > > Switching from lz4 to gzip compression, simply papers over the > warning, without any benefits, and slows down boot. > > Kernel should be fixed to correctly parse lz4 compressed initrds, or > at least lower the warning, to not be user visible as an error. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions > -- 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1899993] Re: EFI: Fails when BootCurrent entry does not exist
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
EFI: Fails when BootCurrent entry does not exist
Status in curtin package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
In Progress
Status in curtin source package in Xenial:
Invalid
Status in linux source package in Xenial:
Fix Committed
Status in curtin source package in Bionic:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in curtin source package in Focal:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in curtin source package in Groovy:
Invalid
Status in linux source package in Groovy:
Fix Committed
Status in curtin source package in Hirsute:
Invalid
Status in linux source package in Hirsute:
In Progress
Bug description:
Split out of bug 1894217.
We're seeing a situation where curtin fails when the variable
BootCurrent references does not exist.
At boot, efibootmgr -v shows:
BootCurrent: 0003
Timeout: 10 seconds
BootOrder: 0003,0004,0005,0006,0001
Note that there are actually no individual boot entries in this
output. BootCurrent and BootOrder are referencing Boot entries that do
not apepar to exist.
Later, curtin tries to set a new BootOrder that places the value of
BootCurrent at the front. This causes efibootmgr to error out,
apparently escalating to an installation failure:
UEFI efibootmgr output after install:
{'current': '0003', 'timeout': '10 seconds', 'order': [''],
'entries': {'': {'name
': 'ubuntu', 'path':
'HD(1,GPT,0937ffdf-628c-4161-8b2f-5920235669c6,0x800,0x10)/File(\\EFI\\ub
untu\\shimx64.efi)'}}}
Setting currently booted 0003 as the first UEFI loader.
New UEFI boot order: 0003,
Running command ['mount', '--bind', '/dev',
'/tmp/tmp6ha4_iz2/target/dev'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/proc',
'/tmp/tmp6ha4_iz2/target/proc'] with allowed
return codes [0] (capture=False)
Running command ['mount', '--bind', '/run',
'/tmp/tmp6ha4_iz2/target/run'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/sys',
'/tmp/tmp6ha4_iz2/target/sys'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars',
'/tmp/tmp6ha4_iz2/target/
sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['unshare', '--fork', '--pid', '--', 'chroot',
'/tmp/tmp6ha4_iz2/target',
'efibootmgr', '-o', '0003,'] with allowed return codes [0] (capture=False)
Invalid BootOrder order entry value0003
^
efibootmgr: entry 0003 does not exist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/183/+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 1901406] Re: Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8
I have the same problem but on a Lenovo ThinkPad P43s (Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz). -- 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/1901406 Title: Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 20.04 to 20.20 on my laptop, the machine became extremely slow. After a days work I noticed that it never got any faster, and the machine was a lot colder than usual. Running cat /proc/cpuinfo and sudo cpupower frequency-info I noticed that the CPU was locked to 400Mhz. After some googling I found reports of people having trouble with CPU frequency governors on kernel 5.8. I tried to add intel_pstate=active to grub, but that didn't help. My short term workaround is to choose the old 5.4 kernel from 20.04. With this kernel everything is snappy again! Currently it's running at 3.2 Ghz with little load. CPU info from /proc/cpuinfo (with kernel 5.4): processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 142 model name: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz stepping : 12 microcode : 0xd6 cpu MHz : 4551.153 cache size: 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid: 0 initial apicid: 0 fpu : yes fpu_exception : yes cpuid level : 22 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities bugs : spectre_v1 spectre_v2 spec_store_bypass swapgs taa itlb_multihit srbds bogomips : 4199.88 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hennikul 2402 F pulseaudio /dev/snd/pcmC0D0p: hennikul 2402 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-02 (418 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20N2CTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=UUID=a36f1344-fd6c-40ef-a397-57f5a57594df ro intel_pstate=active quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy wayland-session Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-23 (2 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2020 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET83W (1.61 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N2CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN2IET83W(1.61):bd01/19/2020:br1.61:efr1.16:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N2CTO1WW dmi.product.sku: LENOVO_MT_20N2_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901406/+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 1903286] Re: Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative
I can confirm all of the above. Also looking at the Pi OS the in which the bluetooth works it lists BCM2711-rpi-400.dts. Also unblocking the soft block has no effect. -- 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/1903286 Title: Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative Status in bluez package in Ubuntu: New Bug description: Trying to use a Bluetooth mouse with Pi400 running latest Mate 20.10 desktop,to save using a USB port. The mouse does not get recognised, double clicking either Bluetooth Adaptors or Bluetooth Manager has no effect. Full update run this morning. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth 5.55-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 6 10:31:06 2020 ImageMediaBuild: 20201028 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash 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:1920x1080M@60 video=HDMI-A-2:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:E0:8E:57 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 net.ifnames=0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903286/+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 1767971] Re: No such man page: kernel_lockdown.7
This bug has been fixed with the upstream release (some days ago) of man-pages-5.09, which now provides a kernel_lockdown.7 page. -- 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/1767971 Title: No such man page: kernel_lockdown.7 Status in linux package in Ubuntu: Triaged Status in manpages package in Ubuntu: New Status in linux source package in Bionic: Triaged Status in Fedora: Unknown Bug description: When booting in secure boot mode, the Bionic kernel emits the following message: [ 52.035055] Lockdown: Loading of unsigned modules is restricted; see man kernel_lockdown.7 But there is no such man page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767971/+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 1858463] Re: Desktop freezing while SSD under heavy load
Tested right now with kernel 5.10.0-051000rc2-generic #202011012330 SMP Sun Nov 1 23:33:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux The problem happens all the same. Test case : - Launch 1 or 2 heavy downloads, e.g. large torrents with Transmission - Every few seconds (10 ? 15 ? 20 ?), apps (e.g. Chrome) becomes unresponsive (e.g. clicks and keystrokes are not taken into account, switching tabs is impossible) - Afterwards, apps respond for a while... and get stuck again... and so on (Happened half a dozen times while writing this message.) -- 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/1858463 Title: Desktop freezing while SSD under heavy load Status in linux package in Ubuntu: Incomplete Bug description: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least for the past 2 years). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 18:20:01 2020 InstallationDate: Installed on 2018-07-28 (526 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1685 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 Tags: focal wayland-session Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1423 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (208 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002
[Kernel-packages] [Bug 1901903] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1901903 Title: Touchpad Status in linux package in Ubuntu: Confirmed Bug description: My mousepad on laptop doesn't work when i'm in ubuntu system ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexandros 2345 F pulseaudio /dev/snd/controlC0: alexandros 2345 F pulseaudio /dev/snd/controlC2: alexandros 2345 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 16:18:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81W4 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=f5166d1e-dffa-46f3-9b9d-1ee2157d2041 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DZCN19WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32776WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDZCN19WW:bd04/13/2020:svnLENOVO:pn81W4:pvrIdeaPad315ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32776WIN:cvnLENOVO:ct10:cvrIdeaPad315ARE05: dmi.product.family: IdeaPad 3 15ARE05 dmi.product.name: 81W4 dmi.product.sku: LENOVO_MT_81W4_BU_idea_FM_IdeaPad 3 15ARE05 dmi.product.version: IdeaPad 3 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901903/+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 1901540] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1901540 Title: package linux-image-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: installed linux-image-5.4.0-52-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: rfcomm bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic mei_hdcp intel_rapl_msr snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc x86_pkg_temp_thermal intel_powerclamp nvidia_modeset snd_sof snd_sof_xtensa_dsp coretemp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio snd_soc_core ac97_bus snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core mac80211 btusb btrtl btbcm iwlwifi btintel nvidia i915 intel_cstate bluetooth intel_wmi_thunderbolt hid_multitouch cfg80211 wmi_bmof mei_me mei ucsi_acpi processor_thermal_device typec_ucsi intel_rapl_common typec intel_soc_dts_iosf intel_pch_thermal mac_hid ideapad_laptop sparse_keymap int3400_thermal int3403_thermal acpi_thermal_rel int340x_thermal_zone hid_logitech_hidpp hid_logitech_dj intel_lpss_pci r8169 intel_lpss i2c_hid i2c_i801 idma64 realtek virt_dma pinctrl_cannonlake wmi pinctrl_intel ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 26 20:31:40 2020 ErrorMessage: installed linux-image-5.4.0-52-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-10-23 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE Device(8910) Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82B0 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=8a952b02-2ee6-4861-908f-b2b925b955bc ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.6 SourcePackage: linux Title: package linux-image-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: installed linux-image-5.4.0-52-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EFCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y7000P2020 dmi.modalias: dmi:bvnLENOVO:bvrEFCN38WW:bd07/30/2020:svnLENOVO:pn82B0:pvrLenovoLegionY7000P2020:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoLegionY7000P2020: dmi.product.family: Legion Y7000P2020 dmi.product.name: 82B0 dmi.product.sku: LENOVO_MT_82B0_BU_idea_FM_Legion Y7000P2020 dmi.product.version: Lenovo Legion Y7000P2020 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901540/+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 1901540] Re: package linux-image-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: installed linux-image-5.4.0-52-generic package pre-removal script subprocess returned er
** Tags removed: need-duplicate-check -- 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/1901540 Title: package linux-image-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: installed linux-image-5.4.0-52-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: rfcomm bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic mei_hdcp intel_rapl_msr snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc x86_pkg_temp_thermal intel_powerclamp nvidia_modeset snd_sof snd_sof_xtensa_dsp coretemp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio snd_soc_core ac97_bus snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core mac80211 btusb btrtl btbcm iwlwifi btintel nvidia i915 intel_cstate bluetooth intel_wmi_thunderbolt hid_multitouch cfg80211 wmi_bmof mei_me mei ucsi_acpi processor_thermal_device typec_ucsi intel_rapl_common typec intel_soc_dts_iosf intel_pch_thermal mac_hid ideapad_laptop sparse_keymap int3400_thermal int3403_thermal acpi_thermal_rel int340x_thermal_zone hid_logitech_hidpp hid_logitech_dj intel_lpss_pci r8169 intel_lpss i2c_hid i2c_i801 idma64 realtek virt_dma pinctrl_cannonlake wmi pinctrl_intel ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 26 20:31:40 2020 ErrorMessage: installed linux-image-5.4.0-52-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-10-23 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE Device(8910) Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82B0 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=8a952b02-2ee6-4861-908f-b2b925b955bc ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.6 SourcePackage: linux Title: package linux-image-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: installed linux-image-5.4.0-52-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EFCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y7000P2020 dmi.modalias: dmi:bvnLENOVO:bvrEFCN38WW:bd07/30/2020:svnLENOVO:pn82B0:pvrLenovoLegionY7000P2020:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoLegionY7000P2020: dmi.product.family: Legion Y7000P2020 dmi.product.name: 82B0 dmi.product.sku: LENOVO_MT_82B0_BU_idea_FM_Legion Y7000P2020 dmi.product.version: Lenovo Legion Y7000P2020 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901540/+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 1901903] Re: Touchpad
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1901903 Title: Touchpad Status in linux package in Ubuntu: Confirmed Bug description: My mousepad on laptop doesn't work when i'm in ubuntu system ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexandros 2345 F pulseaudio /dev/snd/controlC0: alexandros 2345 F pulseaudio /dev/snd/controlC2: alexandros 2345 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 16:18:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81W4 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=f5166d1e-dffa-46f3-9b9d-1ee2157d2041 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DZCN19WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32776WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDZCN19WW:bd04/13/2020:svnLENOVO:pn81W4:pvrIdeaPad315ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32776WIN:cvnLENOVO:ct10:cvrIdeaPad315ARE05: dmi.product.family: IdeaPad 3 15ARE05 dmi.product.name: 81W4 dmi.product.sku: LENOVO_MT_81W4_BU_idea_FM_IdeaPad 3 15ARE05 dmi.product.version: IdeaPad 3 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901903/+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 1901540] Re: package linux-image-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: installed linux-image-5.4.0-52-generic package pre-removal script subprocess returned er
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1901540 Title: package linux-image-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: installed linux-image-5.4.0-52-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: rfcomm bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic mei_hdcp intel_rapl_msr snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc x86_pkg_temp_thermal intel_powerclamp nvidia_modeset snd_sof snd_sof_xtensa_dsp coretemp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio snd_soc_core ac97_bus snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core mac80211 btusb btrtl btbcm iwlwifi btintel nvidia i915 intel_cstate bluetooth intel_wmi_thunderbolt hid_multitouch cfg80211 wmi_bmof mei_me mei ucsi_acpi processor_thermal_device typec_ucsi intel_rapl_common typec intel_soc_dts_iosf intel_pch_thermal mac_hid ideapad_laptop sparse_keymap int3400_thermal int3403_thermal acpi_thermal_rel int340x_thermal_zone hid_logitech_hidpp hid_logitech_dj intel_lpss_pci r8169 intel_lpss i2c_hid i2c_i801 idma64 realtek virt_dma pinctrl_cannonlake wmi pinctrl_intel ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 26 20:31:40 2020 ErrorMessage: installed linux-image-5.4.0-52-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-10-23 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE Device(8910) Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82B0 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=8a952b02-2ee6-4861-908f-b2b925b955bc ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.6 SourcePackage: linux Title: package linux-image-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: installed linux-image-5.4.0-52-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EFCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y7000P2020 dmi.modalias: dmi:bvnLENOVO:bvrEFCN38WW:bd07/30/2020:svnLENOVO:pn82B0:pvrLenovoLegionY7000P2020:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoLegionY7000P2020: dmi.product.family: Legion Y7000P2020 dmi.product.name: 82B0 dmi.product.sku: LENOVO_MT_82B0_BU_idea_FM_Legion Y7000P2020 dmi.product.version: Lenovo Legion Y7000P2020 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901540/+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 1902737] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1902737 Title: touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input5 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=1100f02902000 8380307cf910f001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys= S: Sysfs=/devices/platform/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input6 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=8000 0 0 1500b0c00 40020030 0 0 B: MSC=10 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input8 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0003 Vendor=0bda Product=58c2 Version=2828 N: Name="Laptop_Integrated_Webcam_HD: In" P: Phys=usb-:00:1d.0-1.8/button S: Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.8/1-1.8:1.0/input/input9 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=046d Product=4023 Version=0111 N: Name="Logitech Wireless Keyboard PID:4023" P: Phys=usb-:00:1d.0-1.4/input1:1 S: Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:046D:C534.0002/0003:046D:4023.0003/input/input27 U: Uniq=4023-00-00-00-00 H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=12001f B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c007 7bfad941dfff ffbeffdfffef fffe B: REL=1040 B: ABS=1 B: MSC=10 B: LED=1f I: Bus=0003 Vendor=046d Product=4054 Version=0111 N: Name="Logitech Wireless Mouse" P: Phys=usb-:00:1d.0-1.4/input1:2 S: Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:046D:C534.0002/0003:046D:4054.0004/input/input28 U: Uniq=4054-6f-3f-62-c1 H: Handlers=mouse0 event9 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 sudo lspci -vnvn.log [sudo] password for priyanka: lspci: invalid option -- '.' Usage: lspci [] Basic display modes: -mm Produce machine-readable output (single -m for an obsolete format) -tShow bus tree Display options: -vBe verbose (-vv or -vvv for higher verbosity) -kShow kernel drivers handling each device -xShow hex-dump of the standard part of the config space -xxx Show hex-dump of the whole config space (dangerous; root only) - Show hex-dump of the 4096-byte extended config space (root only) -bBus-centric view (addresses and IRQ's as seen by the bus) -DAlways show domain numbers -PDisplay bridge path in addition to bus and device number -PP Display bus path in addition to bus and device number Resolving of device ID's to names: -nShow numeric ID's -nn Show both textual and numeric ID's (names & numbers) -qQuery the PCI ID database for unknown ID's via DNS -qq As above, but re-query locally cached entries -QQuery the PCI ID database for all ID's via DNS Selection of devices: -s ]:]]:][][.[]] Show only devices in selected slots -d []:[][:]Show only devices with specified ID's Other
[Kernel-packages] [Bug 1902737] Re: touchpad not working
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1902737 Title: touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input5 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=1100f02902000 8380307cf910f001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys= S: Sysfs=/devices/platform/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input6 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=8000 0 0 1500b0c00 40020030 0 0 B: MSC=10 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input8 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0003 Vendor=0bda Product=58c2 Version=2828 N: Name="Laptop_Integrated_Webcam_HD: In" P: Phys=usb-:00:1d.0-1.8/button S: Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.8/1-1.8:1.0/input/input9 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=046d Product=4023 Version=0111 N: Name="Logitech Wireless Keyboard PID:4023" P: Phys=usb-:00:1d.0-1.4/input1:1 S: Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:046D:C534.0002/0003:046D:4023.0003/input/input27 U: Uniq=4023-00-00-00-00 H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=12001f B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c007 7bfad941dfff ffbeffdfffef fffe B: REL=1040 B: ABS=1 B: MSC=10 B: LED=1f I: Bus=0003 Vendor=046d Product=4054 Version=0111 N: Name="Logitech Wireless Mouse" P: Phys=usb-:00:1d.0-1.4/input1:2 S: Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:046D:C534.0002/0003:046D:4054.0004/input/input28 U: Uniq=4054-6f-3f-62-c1 H: Handlers=mouse0 event9 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 sudo lspci -vnvn.log [sudo] password for priyanka: lspci: invalid option -- '.' Usage: lspci [] Basic display modes: -mm Produce machine-readable output (single -m for an obsolete format) -tShow bus tree Display options: -vBe verbose (-vv or -vvv for higher verbosity) -kShow kernel drivers handling each device -xShow hex-dump of the standard part of the config space -xxx Show hex-dump of the whole config space (dangerous; root only) - Show hex-dump of the 4096-byte extended config space (root only) -bBus-centric view (addresses and IRQ's as seen by the bus) -DAlways show domain numbers -PDisplay bridge path in addition to bus and device number -PP Display bus path in addition to bus and device number Resolving of device ID's to names: -nShow numeric ID's -nn Show both textual and numeric
[Kernel-packages] [Bug 1902902] Re: package libnvidia-compute-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1902902 Title: package libnvidia-compute-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu /libnvidia-ml.so', which is also in package nvidia-340 340.108-0ubuntu2 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Every time I start my laptop . This reporting things pop up . I don't know if anything is wrong with my pc . I am trying to run hashcat but it says no device found/left . I am trying to run it but it just fails . By the way how do I run hashcat ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 AptOrdering: libcuda1-340:amd64: Remove nvidia-opencl-icd-340:amd64: Remove libnvidia-compute-390:amd64: Install nvidia-utils-390:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 4 19:58:18 2020 DpkgTerminalLog: Preparing to unpack .../libnvidia-compute-390_390.138-0ubuntu0.20.04.1_amd64.deb ... Unpacking libnvidia-compute-390:amd64 (390.138-0ubuntu0.20.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libnvidia-compute-390_390.138-0ubuntu0.20.04.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.108-0ubuntu2 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.108-0ubuntu2 InstallationDate: Installed on 2020-11-02 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.108-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1902902/+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 1883905] Re: Touchpad is not being detected by Ubuntu on Lenovo IdeaPad S145-15IIL
Sorry for the long inactivity. I went back to Windows because I really needed that touchpad to work. I tried the solution from the bug report mentioned by Alex Hung. GRUB_CMDLINE_LINUX_DEFAULT = 'i80242.nopnp=1 pci=nocrs quiet splash' Worked perfectly. -- 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/1883905 Title: Touchpad is not being detected by Ubuntu on Lenovo IdeaPad S145-15IIL Status in linux package in Ubuntu: Incomplete Bug description: Laptop is new, I bought it yesterday. I'm dual-booting Windows 10 and Ubuntu 20.04. Touchpad works on Windows. The touchpad does not show up in xinput --list and in the devices (included in the attachment). Its manufacturer is Elantech, at least I suppose it is, based on an output from acpidump which has shown: 27AD0: 54 59 01 70 0D 45 4C 41 4E 30 36 33 33 00 5F 48 TY.p.ELAN0633._H on one line. If it is in fact my touchpad and its ID is 0633, then it is not included in elan_i2c_core.c file in my ubuntu kernel source (IDs end at 0632). I tried to modify it myself and compile a new, custom kernel, but I am quite new to linux so I failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maciek 3356 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 14:50:45 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 0b05:1844 ASUSTek Computer, Inc. ASUS WT205 Wireless Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=9baf434c-2f39-433d-b9ec-ed69c897ef46 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883905/+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 1903288] Re: Power guest secure boot with static keys: kernel portion
Hi Daniel, btw. in which upstream kernel did the kernel patches for this landed (or will land)? Just to be sure - 5.10 or 5.11 or already in with an earlier version? ** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => Critical ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) -- 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/1903288 Title: Power guest secure boot with static keys: kernel portion Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #2 - Daniel John Axtens - 2020-11-05 20:15:10 == This is the kernel side of changes needed for LPAR/guest secure boot. Because Ubuntu keeps its kernels so wonderfully up to date, I don't think there are any extra patches you need to pick up. (I'll double- check against the 21.04 tree once my git pulls finish!) However, we potentially need some configuration changes to make sure kexec-ing into a crashdump kernel still works. Because Lockdown requires that kexec kernels are signed by a key trusted by IMA, the public key for used for signing the kdump kernel needs to be in the IMA keyring or the platform keyring. For host secure boot (and in the UEFI case), it's loaded into the platform keyring. But in the case of guest secure boot with static keys, it's not loaded into the platform keyring so it needs to be loaded into the IMA keyring. This is easy enough to do. Firstly, load the Secure Boot CA into the .primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS property. We assume the key used to sign the kernel is signed by this CA. Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the .primary_trusted_keys keyring to be loaded into the IMA keyring. Then set IMA_X509_PATH to provide a path to the signing key on installed file system. (It may also be possible to do this step in userspace, so long as the CA is trusted by the kernel.) Then that key will be loaded into the .ima keyring at boot and be used to appraise the kexec kernel for crashdumps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+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 1903293] [NEW] Avoid double newline when running insertchanges
Public bug reported: [Impact] When preparing derivative kernels and inserting master kernel changes, if the derivative has not changes on its own, we end up with two empty lines, which is caught up by verify-release-ready. [Test case] Run cranky-close with derivative changes and no derivative changes. [Regression Potential] We could break changelogs, or the kernel preparation altogether. ** Affects: linux (Ubuntu) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Xenial) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Groovy) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress -- 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/1903293 Title: Avoid double newline when running insertchanges Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] When preparing derivative kernels and inserting master kernel changes, if the derivative has not changes on its own, we end up with two empty lines, which is caught up by verify-release-ready. [Test case] Run cranky-close with derivative changes and no derivative changes. [Regression Potential] We could break changelogs, or the kernel preparation altogether. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903293/+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 1835660] Re: initramfs unpacking failed
Same issue here and no workaround works : neither switching from lz4 to gzip nor keeping lz4 and only update initramfs. I also tried to launch with another kernel, without success. The computer is now blocked (Xubuntu 20.04, fresh install). I really don't want to reinstall 18.04. What can I do ? Any idea will be welcome ! :) -- 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1903288] [NEW] Power guest secure boot with static keys: kernel portion
You have been subscribed to a public bug: == Comment: #2 - Daniel John Axtens - 2020-11-05 20:15:10 == This is the kernel side of changes needed for LPAR/guest secure boot. Because Ubuntu keeps its kernels so wonderfully up to date, I don't think there are any extra patches you need to pick up. (I'll double- check against the 21.04 tree once my git pulls finish!) However, we potentially need some configuration changes to make sure kexec-ing into a crashdump kernel still works. Because Lockdown requires that kexec kernels are signed by a key trusted by IMA, the public key for used for signing the kdump kernel needs to be in the IMA keyring or the platform keyring. For host secure boot (and in the UEFI case), it's loaded into the platform keyring. But in the case of guest secure boot with static keys, it's not loaded into the platform keyring so it needs to be loaded into the IMA keyring. This is easy enough to do. Firstly, load the Secure Boot CA into the .primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS property. We assume the key used to sign the kernel is signed by this CA. Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the .primary_trusted_keys keyring to be loaded into the IMA keyring. Then set IMA_X509_PATH to provide a path to the signing key on installed file system. (It may also be possible to do this step in userspace, so long as the CA is trusted by the kernel.) Then that key will be loaded into the .ima keyring at boot and be used to appraise the kexec kernel for crashdumps. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-189099 severity-critical targetmilestone-inin2104 -- Power guest secure boot with static keys: kernel portion https://bugs.launchpad.net/bugs/1903288 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] Re: weird screen display
Hi I am getting this issue while trying to upgrade this. ** Attachment added: "Screenshot from 2020-11-06 16-18-23.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+attachment/5431866/+files/Screenshot%20from%202020-11-06%2016-18-23.png -- 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/1898505 Title: weird screen display Status in linux package in Ubuntu: Incomplete Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash 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: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+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 1903286] [NEW] Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative
Public bug reported: Trying to use a Bluetooth mouse with Pi400 running latest Mate 20.10 desktop,to save using a USB port. The mouse does not get recognised, double clicking either Bluetooth Adaptors or Bluetooth Manager has no effect. Full update run this morning. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth 5.55-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 6 10:31:06 2020 ImageMediaBuild: 20201028 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash 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:1920x1080M@60 video=HDMI-A-2:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:E0:8E:57 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 net.ifnames=0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 groovy -- 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/1903286 Title: Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative Status in bluez package in Ubuntu: New Bug description: Trying to use a Bluetooth mouse with Pi400 running latest Mate 20.10 desktop,to save using a USB port. The mouse does not get recognised, double clicking either Bluetooth Adaptors or Bluetooth Manager has no effect. Full update run this morning. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth 5.55-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 6 10:31:06 2020 ImageMediaBuild: 20201028 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash 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:1920x1080M@60 video=HDMI-A-2:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:E0:8E:57 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 net.ifnames=0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903286/+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 1899993] Re: EFI: Fails when BootCurrent entry does not exist
** Changed in: linux (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
EFI: Fails when BootCurrent entry does not exist
Status in curtin package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
In Progress
Status in curtin source package in Xenial:
Invalid
Status in linux source package in Xenial:
In Progress
Status in curtin source package in Bionic:
Invalid
Status in linux source package in Bionic:
In Progress
Status in curtin source package in Focal:
Invalid
Status in linux source package in Focal:
In Progress
Status in curtin source package in Groovy:
Invalid
Status in linux source package in Groovy:
In Progress
Status in curtin source package in Hirsute:
Invalid
Status in linux source package in Hirsute:
In Progress
Bug description:
Split out of bug 1894217.
We're seeing a situation where curtin fails when the variable
BootCurrent references does not exist.
At boot, efibootmgr -v shows:
BootCurrent: 0003
Timeout: 10 seconds
BootOrder: 0003,0004,0005,0006,0001
Note that there are actually no individual boot entries in this
output. BootCurrent and BootOrder are referencing Boot entries that do
not apepar to exist.
Later, curtin tries to set a new BootOrder that places the value of
BootCurrent at the front. This causes efibootmgr to error out,
apparently escalating to an installation failure:
UEFI efibootmgr output after install:
{'current': '0003', 'timeout': '10 seconds', 'order': [''],
'entries': {'': {'name
': 'ubuntu', 'path':
'HD(1,GPT,0937ffdf-628c-4161-8b2f-5920235669c6,0x800,0x10)/File(\\EFI\\ub
untu\\shimx64.efi)'}}}
Setting currently booted 0003 as the first UEFI loader.
New UEFI boot order: 0003,
Running command ['mount', '--bind', '/dev',
'/tmp/tmp6ha4_iz2/target/dev'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/proc',
'/tmp/tmp6ha4_iz2/target/proc'] with allowed
return codes [0] (capture=False)
Running command ['mount', '--bind', '/run',
'/tmp/tmp6ha4_iz2/target/run'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/sys',
'/tmp/tmp6ha4_iz2/target/sys'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars',
'/tmp/tmp6ha4_iz2/target/
sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['unshare', '--fork', '--pid', '--', 'chroot',
'/tmp/tmp6ha4_iz2/target',
'efibootmgr', '-o', '0003,'] with allowed return codes [0] (capture=False)
Invalid BootOrder order entry value0003
^
efibootmgr: entry 0003 does not exist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/183/+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 1903285] [NEW] Cant enable wifi
Private bug reported: Wifi toggling button not working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 1535 F pulseaudio /dev/snd/controlC0: test 1535 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 6 16:02:25 2020 HibernationDevice: RESUME=UUID=b471a534-60ca-417e-9ab2-6d221fcbfa52 InstallationDate: Installed on 2019-09-24 (408 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E6420 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=a544f77b-bf7c-4073-8df9-f3483f09845a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2020-11-06 (0 days ago) dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 032T9K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Information type changed from Public to Private -- 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/1903285 Title: Cant enable wifi Status in linux package in Ubuntu: New Bug description: Wifi toggling button not working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 1535 F pulseaudio /dev/snd/controlC0: test 1535 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 6 16:02:25 2020 HibernationDevice: RESUME=UUID=b471a534-60ca-417e-9ab2-6d221fcbfa52 InstallationDate: Installed on 2019-09-24 (408 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E6420 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=a544f77b-bf7c-4073-8df9-f3483f09845a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2020-11-06 (0 days ago) dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 032T9K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903285/+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 1902093] Re: Introduce the new NVIDIA 455 series
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Groovy) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux-restricted-modules (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-restricted-modules (Ubuntu) Status: New => Confirmed ** Changed in: linux-restricted-modules (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-restricted-modules (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux-restricted-modules (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-restricted-modules (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-restricted-modules (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux-restricted-modules (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Confirmed Status in linux-restricted-modules source package in Bionic: Confirmed Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Committed Status in linux source package in Focal: Confirmed Status in linux-restricted-modules source package in Focal: Confirmed Status in nvidia-graphics-drivers-455 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-restricted-modules source package in Groovy: Confirmed Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+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 1902934] Re: dmesg is not restricted in linux-raspi kernel
** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => Triaged ** Changed in: linux-raspi (Ubuntu Hirsute) Status: New => Triaged -- 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/1902934 Title: dmesg is not restricted in linux-raspi kernel Status in linux-raspi package in Ubuntu: Triaged Status in linux-raspi source package in Groovy: Triaged Status in linux-raspi source package in Hirsute: Triaged Bug description: The CONFIG_SECURITY_DMESG_RESTRICT option is not set on the Ubuntu Pi kernels, resulting in dmesg being accessible to ordinary users. This is in contrast to PC installs, where dmesg is now restricted to the "root" user in 20.10 onwards. The following messages from the ubuntu-devel list cover the original proposal (which proposed limiting dmesg to root:adm), and earlier discussion from 2011 (which proposed limiting dmesg to root alone, which is what was implemented in groovy): https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html https://lists.ubuntu.com/archives/ubuntu-devel/2011-May/033240.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1902934/+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 1901975] Re: After upgrade to 20.10 got audio dummy output
OK, when you start the machine and get the dummy output, please run pa- info > pa-info.txt-dummy and upload the pa-info.txt-dummy. thx. -- 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/1901975 Title: After upgrade to 20.10 got audio dummy output Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to 20.10 repeatly got audio dummy output ,when I use sudo alsa force_reload and reboot system the audio come back .But after some days the problom reappear use the same method solved the audio issue .It maybe the kernel bug with this issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dell 5398 F pulseaudio dell 5402 F pipewire-media- /dev/snd/controlC1: dell 5402 F pipewire-media- /dev/snd/seq:dell 5397 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Oct 29 12:33:05 2020 HibernationDevice: RESUME=UUID=0c70f08b-8e7f-4c5d-a9d5-a0846776436b InstallationDate: Installed on 2018-06-15 (867 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. G7 7590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu ro quiet splash pti=off nouveau.modeset=0 nouveau.runpm=0 i915.enable_psr=0 init_on_alloc=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-17 (11 days ago) dmi.bios.date: 05/22/2020 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.2 dmi.board.name: 0YC5C7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.2:bd05/22/2020:br1.13:svnDellInc.:pnG77590:pvr:rvnDellInc.:rn0YC5C7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G7 7590 dmi.product.sku: 08EB dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-07-18T14:15:17 mtime.conffile..etc.logrotate.d.apport: 2020-10-26T16:26:26.813657 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901975/+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 1902473] Re: select03 from ubuntu_ltp_syscalls failed on G
Can be found on F-oem-5.10 as well. ** Tags added: 5.10 focal oem ** Tags added: sru-20201103 ** Summary changed: - select03 from ubuntu_ltp_syscalls failed on G + select03 from ubuntu_ltp_syscalls failed on G / F-oem-5.10 -- 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/1902473 Title: select03 from ubuntu_ltp_syscalls failed on G / F-oem-5.10 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: This is a new test case, test failed with: <<>> tag=select03 stime=1604290335 cmdline="select03" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:107: TINFO: Testing libc select() select03.c:62: TPASS: Negative nfds: select() failed as expected: EINVAL (22) select03.c:51: TFAIL: Invalid readfds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid writefds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid exceptfds: select() passed unexpectedly with 0 select03.c:62: TPASS: Faulty readfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty writefds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty exceptfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty timeout: select() failed as expected: EFAULT (14) tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:110: TINFO: Testing SYS_select syscall select03.c:62: TPASS: Negative nfds: select() failed as expected: EINVAL (22) select03.c:51: TFAIL: Invalid readfds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid writefds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid exceptfds: select() passed unexpectedly with 0 select03.c:62: TPASS: Faulty readfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty writefds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty exceptfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty timeout: select() failed as expected: EFAULT (14) tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:113: TINFO: Testing SYS_pselect6 syscall select03.c:62: TPASS: Negative nfds: select() failed as expected: EINVAL (22) select03.c:51: TFAIL: Invalid readfds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid writefds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid exceptfds: select() passed unexpectedly with 0 select03.c:62: TPASS: Faulty readfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty writefds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty exceptfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty timeout: select() failed as expected: EFAULT (14) tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:116: TINFO: Testing SYS_pselect6 time64 syscall select_var.h:81: TCONF: __NR_pselect6 time64 variant not supported tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:119: TINFO: Testing SYS__newselect syscall select_var.h:87: TCONF: syscall(-1) __NR__newselect not supported Summary: passed 15 failed 9 skipped 2 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=1 <<>> ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 28 09:30 seq crw-rw 1 root audio 116, 33 Oct 28 09:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Mon Nov 2 04:10:52 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=f06509c5-4a0a-4cae-be3c-e5d21c1687c9 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1902896] Re: Thunderbolt dock no longer works
** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- 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/1902896 Title: Thunderbolt dock no longer works Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-firmware source package in Focal: New Bug description: I'm using Lubuntu 20.04 on Dell XPS 13 9360. Somehow thunderbolt stopped working. I've attached the relevant output from /var/syslog. I'm using 5.4.0-52-generic. I've updated all my firmware through fwupdmgr. Briefly, the kernel complains kernel: pci :01:00.0: BAR 13: no space for [io size 0x3000] kernel: pci :01:00.0: BAR 13: failed to assign [io size 0x3000] then kernel: usb 3-1.3: config 1 has no interfaces? then kernel: xhci_hcd :39:00.0: xHCI host controller not responding, assume dead kernel: r8152 4-1.4:1.0 enxd481d70b2831: Stop submitting intr, status -108 kernel: xhci_hcd :39:00.0: HC died; cleaning up then kernel: xhci_hcd :39:00.0: Host halt failed, -19 kernel: xhci_hcd :39:00.0: Host not accessible, reset failed. then kernel: pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) kernel: pcieport :00:1c.0: AER: device [8086:9d10] error status/mask=0001/2000 kernel: pcieport :00:1c.0: AER:[ 0] RxErr ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.3 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Nov 4 16:07:31 2020 Dependencies: InstallationDate: Installed on 2020-05-11 (176 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=UUID=95de7ebe-d429-45d7-9548-0d5af627a560 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.2 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.2:bd07/13/2020:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902896/+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 1852002] Re: Desktop frozen for 30 seconds after Nvidia driver crash
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1852002 Title: Desktop frozen for 30 seconds after Nvidia driver crash Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Hi, I just experienced a frozen desktop, where I could barely move the mouse, for maybe 30 seconds or more. When the desktop recovered, I looked at dmesg logs to find these lines: [ 461.937702] NVRM: GPU at PCI::01:00: GPU-734060ac-116d-fbbb-1553-d84896b846a4 [ 461.937710] NVRM: Xid (PCI::01:00): 31, pid=275, Ch 002e, intr . MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_0036d000. Fault is of type FAULT_PTE ACCESS_TYPE_VIRT_READ It looks like a fault from the Nvidia driver. I'm using the tested one "nvidia-driver-435", installed via the GUI tool. Could you report this to Nvidia please ? Thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 17:35:12 2019 InstallationDate: Installed on 2019-09-26 (45 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1852002/+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 1845347] Re: Lenovo Yoga C630 not supported in Ubuntu
That's correct. For support, please go to: https://github.com/aarch64-laptops/build -- 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/1845347 Title: Lenovo Yoga C630 not supported in Ubuntu Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Support for the Lenovo Yoga C630 was added to mainline in v5.4. Ubuntu Eoan will be released based on v5.3, thus the latest release will not boot. This would be a shame, as one of the first laptops based on AArch64 it's a ground breaking piece of H/W. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845347/+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
