[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
The IPU6 webcam still does not work on my Dell XPS 16 (9640). I've tested it with Ubuntu 24.04 daily builds including with the 6.9-rc1 kernel. What information would you need to check the problem? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in ipu6-drivers source package in Mantic: Fix Released Status in ivsc-driver source package in Mantic: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Fix Released Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. Need both firmware and driver change to probe the hardware correctly. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI
[Kernel-packages] [Bug 2058691] Re: No sound card detected on the Dell xps 16 2024 (9640)
** Package changed: alsa-driver (Ubuntu) => firmware-sof (Ubuntu) ** Changed in: firmware-sof (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2058691 Title: No sound card detected on the Dell xps 16 2024 (9640) Status in firmware-sof package in Ubuntu: Fix Committed Bug description: The sound card is not detected on the Dell XPS 16 2024 (9640). A Cirrus Logic CS42L43 card is used which apparently got support in Linux 6.6 https://www.google.com/url?sa=t=web=j=89978449=https://www.phoronix.com/forums/forum/software/general- linux-open-source/1408193-linux-6-6-lands-support-for-the-cirrus- logic-cs42l43-audio-codec=2ahUKEwiukq-ZroaFAxUWhf0HHe- jCngQFnoECA8QAQ=AOvVaw3VW5hROJFzdJPUaIX-3igC https://www.reddit.com/r/DellXPS/comments/1ax1i4t/support_for_xps_16_9640_documentation/ No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 21 23:00:06 2024 InstallationDate: Installed on 2024-03-19 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240319) MachineType: Dell Inc. XPS 16 9640 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2024 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 0YFT36 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd01/15/2024:br1.1:efr1.2:svnDellInc.:pnXPS169640:pvr:rvnDellInc.:rn0YFT36:rvrA00:cvnDellInc.:ct10:cvr:sku0C62: dmi.product.family: XPS dmi.product.name: XPS 16 9640 dmi.product.sku: 0C62 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2058691/+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 2043580] Re: New Intel MIPI IPU6 firmware available for MTL-P platform
This bug seems to affect me with a Dell XPS 16 2024. I get the following dmesg output if it is of any use: [2.844944] intel-ipu6 :00:05.0: enabling device ( -> 0002) [2.845217] intel-ipu6 :00:05.0: Device 0x7d19 (rev: 0x4) [2.845232] intel-ipu6 :00:05.0: physical base address 0x522c00 [2.845233] intel-ipu6 :00:05.0: mapped as: 0xd41b05e8 [2.845309] intel-ipu6 :00:05.0: IPU in secure mode [2.845311] intel-ipu6 :00:05.0: IPU secure touch = 0x8000 [2.845312] intel-ipu6 :00:05.0: IPU camera mask = 0x0 [2.857255] intel-ipu6 :00:05.0: IPC reset done [2.857259] intel-ipu6 :00:05.0: cpd file name: intel/ipu6epmtl_fw.bin [2.857398] intel-ipu6 :00:05.0: Direct firmware load for intel/ipu6epmtl_fw.bin failed with error -2 [2.857402] intel-ipu6 :00:05.0: Requesting signed firmware failed [2.857430] intel-ipu6 :00:05.0: probe with driver intel-ipu6 failed with error -2 -- 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/2043580 Title: New Intel MIPI IPU6 firmware available for MTL-P platform Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-firmware source package in Noble: In Progress Bug description: [SRU Justification] [Impact] Intel IPU6 camera drivers may not load with MTL QS stepping CPUs. [Fix] New upstream firmware release in https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87. [Test Case] 1. Install firmware into /lib/firmware/intel/ipu6epmtl_fw.bin and reboot 2. Try access camera via webcamtest.com 3. The camera should be working as verified with ES CPUs. [Where problems could occur] Opaque firmware, and there is no IPU6/MTL platform shipped yet. [Other Info] Intel MIPI IPU6 on Intel Meteor Lake platform is only supported on 6.5 kernels or newer. Nominate Jammy for oem-6.5, Noble as the next LTS, and best effort support for Mantic. == original bug report == https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87 Intel released a new firmware blob for MIPI IPU6 on Intel Meteor Lake platform. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2043580/+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 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
I think we have some options to fix this. Yet, which would be a solution that could be packaged? If I understand https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html correctly there are the following options: Keep the GPU-Memory Running === Pro: * Only need to set a kernel module parameter Con: * Only works in S2 * Uses more power than necessary (at least if more than 256 MB graphic memory are used) * Does not work with suspend-to-disk (at least if I understood things right) Copy Memory to tmpfs Dump the graphic-memory into tmpfs. I wouldn't suggest using /run, but creating a driver-specific tmpfs that is large enough to hold the graphic memory. Pro: * Just works, as the kernel takes care of paging the tmpfs to disk in case of stand-by or suspend-to-disk. Con: * Delayed suspend and wakeup * Unexpected swap-usage -> OOM-Killer might kick in on suspend if there is not enough or no swap. Get everyone to work around it == Get all the affected applications to update their video-memory after suspend-to-X. Pro: * Does not have any of the Cons of the other solutions Con: * Probably very tedious. Keep it as it is Pro: * Minimal effort * Kind of works most of the time. Con: * Nobody is really happy. Comments? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: New Status in Mutter: Fix Released Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-460 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-525 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-535 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on
[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected
As asked by @Hui Wang, I have created a separate bug #1880571 for my problem on focal fossa and run apport-collect. As the data collected by apport showed that timidity was running I have uninstalled timidity and this seems to have fixed the problem: audio output was immediately restored, and after each of three reboots (the last of which after removing "options snd-hda-intel dmic_detect=0" from /etc/modprobe.d /alsa-base.conf), audio output was available right after logging in. So my problem really seems to be a bug in timidity. -- 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/1864061 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: The sof-pci-dev and snd-soc-skl all contains the same pciid, if the soc-skl is loaded ahead of sof-pci-dev, the sof driver will not work anymore, in the oem project, we manually put the soc-skl in the blacklist. From kernel-5.4 (focal kernel), the driver soc-skl is disabled by default, and there is no users report any issues on it. So let us disable soc-skl in the eoan and osp1 kernel too. The patch for eoan kernel doesn't remove the modules because looks like the abi folder are not controlled by git. This will break the modulecheck, so if this patch could be merged, please help remove those modules: snd-soc-skl snd-soc-skl-ipc snd-soc-skl-ssp-clk [Impact] If soc-skl driver is loaded ahead of sof driver, the sof could not work anymore, we need to blacklist the soc-skl manually [Fix] Like the focal kernel, we disable the soc_skl driver in the kernel config [Test Case] Tested on Lenovo and Dell machines which has dmic, the sof driver could be loaded successfully. Tested on the machinces without the dmic, the legacy hda driver worked well as before. [Regression Risk] Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this dirver; and We have not met a machine need the soc_skl driver yet; and Intel claim that the sof could replace the soc_skl driver. In the -41 kernel, we introduced a patch from stable kernel, that make the sof driver crash, and there is a fix patch in the 5.6-rc1, and this fix patch is already in the stable and is merged to focal kernel, now we backport this patch to Eoan kernel if -42 doesn't introduce this fix patch from stable. The patch introduced the crash: commit 063821115e02229d5fd3de31bad270d5e30aeb41 Author: Dragos Tarcatu Date: Mon Dec 9 18:39:38 2019 -0600 ASoC: topology: Check return value for snd_soc_add_dai_link() BugLink: https://bugs.launchpad.net/bugs/1861929 [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ] snd_soc_add_dai_link() might fail. This situation occurs for instance in a very specific use case where a PCM device and a Back End DAI link are given identical names in the topology. When this happens, soc_new_pcm_runtime() fails and then snd_soc_add_dai_link() returns -ENOMEM when called from soc_tplg_fe_link_create(). Because of that, the link will not get added into the card list, so any attempt to remove it later ends up in a panic. Fix that by checking the return status and free the memory in case of an error. Reviewed-by: Ranjani Sridharan Signed-off-by: Dragos Tarcatu Signed-off-by: Pierre-Louis Bossart Link: https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Khalid Elmously [Impact] During the boot, the sof driver crash because the hdmi_pcm_list is not initialized before it is used. [Fix] This bug is fixed in the mainline kernel v5.6-rc1, now backport this patch to ubuntu kernel [Test Case] Boot the -41 kernel with this patch added. blacklist the snd_soc_skl the kernel can boot successfully, and sof driver worked well [Regression Risk] Low, the patches are backported from upstream kernel, and I tested this patch on Lenovo and Dell dmic machines. Focal kernel already has this patch and works well. Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -22 ProblemType: Bug
[Kernel-packages] [Bug 1880571] Re: PCI/internal sound card not detected on ubuntu focal
** Also affects: timidity (Ubuntu) Importance: Undecided Status: New ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in timidity package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Re: PCI/internal sound card not detected on ubuntu focal
Seeing 'timidity' in the data collected by apport I have just uninstalled timidity. This has immediately restored the availability of the sound output. Also after rebooting, sound output is working again (I have since rebooted twice). -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376575/+files/WifiSyslog.txt ** Description changed: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. - HDMI sound output is also does not work when the internal sound output does not work, USB sound output works. + HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: timidity 1144 F timidity - /dev/snd/pcmC0D0p: timidity 1144 F...m timidity - /dev/snd/seq:timidity 1144 F timidity - /dev/snd/timer: timidity 1144 f timidity + USERPID ACCESS COMMAND + /dev/snd/controlC0: timidity 1144 F timidity + /dev/snd/pcmC0D0p: timidity 1144 F...m timidity + /dev/snd/seq:timidity 1144 F timidity + /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 8087:0a2b Intel Corp. - Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2b Intel Corp. + Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-5.4.0-31-generic N/A - linux-backports-modules-5.4.0-31-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-31-generic N/A + linux-backports-modules-5.4.0-31-generic N/A + linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: - + _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04
[Kernel-packages] [Bug 1880571] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376574/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Re: PCI/internal sound card not detected on ubuntu focal
I had thought that appending options snd-hda-intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf had fixed the problem. But the problem has since reappeared. -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376568/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376573/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376569/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376572/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376570/+files/ProcEnviron.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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376571/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376567/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376563/+files/Dependencies.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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376564/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376562/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376565/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376561/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376566/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376560/+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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] [NEW] PCI/internal sound card not detected on ubuntu focal
Public bug reported: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers ** Affects: ubuntu Importance: Undecided Status: New ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: apport-collected focal ** Description changed: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output is also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu - @Hui Wang asked me to report this as a new bug in - https://bugs.launchpad.net/ubuntu/+source/linux-oem- - osp1/+bug/1864061/comments/64 + @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: timidity 1144 F timidity + /dev/snd/pcmC0D0p: timidity 1144 F...m timidity + /dev/snd/seq:timidity 1144 F timidity + /dev/snd/timer: timidity 1144 f timidity + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 + Lsusb: + Bus
[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected
I have had this on 19.10 (see https://bugs.launchpad.net/ubuntu/+source /linux-oem-osp1/+bug/1864061/comments/42) and on 20.04. Adding "options snd-hda-intel dmic_detect=0" to the end of /etc/modprobe.d/alsa-base.conf has apparently fixed the issue on 20.04 (microphone is still working). I probably would have tried this earlier if anyone (@Hui Wang ?) had explained a bit more understandably what the problem is, what the workaround does, why it fixes the issue, and what the possible side effects are. Also the bug description says this issue does not arise in focal (20.04), which is incorrect in my and several other commenters' cases. -- 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/1864061 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: The sof-pci-dev and snd-soc-skl all contains the same pciid, if the soc-skl is loaded ahead of sof-pci-dev, the sof driver will not work anymore, in the oem project, we manually put the soc-skl in the blacklist. From kernel-5.4 (focal kernel), the driver soc-skl is disabled by default, and there is no users report any issues on it. So let us disable soc-skl in the eoan and osp1 kernel too. The patch for eoan kernel doesn't remove the modules because looks like the abi folder are not controlled by git. This will break the modulecheck, so if this patch could be merged, please help remove those modules: snd-soc-skl snd-soc-skl-ipc snd-soc-skl-ssp-clk [Impact] If soc-skl driver is loaded ahead of sof driver, the sof could not work anymore, we need to blacklist the soc-skl manually [Fix] Like the focal kernel, we disable the soc_skl driver in the kernel config [Test Case] Tested on Lenovo and Dell machines which has dmic, the sof driver could be loaded successfully. Tested on the machinces without the dmic, the legacy hda driver worked well as before. [Regression Risk] Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this dirver; and We have not met a machine need the soc_skl driver yet; and Intel claim that the sof could replace the soc_skl driver. In the -41 kernel, we introduced a patch from stable kernel, that make the sof driver crash, and there is a fix patch in the 5.6-rc1, and this fix patch is already in the stable and is merged to focal kernel, now we backport this patch to Eoan kernel if -42 doesn't introduce this fix patch from stable. The patch introduced the crash: commit 063821115e02229d5fd3de31bad270d5e30aeb41 Author: Dragos Tarcatu Date: Mon Dec 9 18:39:38 2019 -0600 ASoC: topology: Check return value for snd_soc_add_dai_link() BugLink: https://bugs.launchpad.net/bugs/1861929 [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ] snd_soc_add_dai_link() might fail. This situation occurs for instance in a very specific use case where a PCM device and a Back End DAI link are given identical names in the topology. When this happens, soc_new_pcm_runtime() fails and then snd_soc_add_dai_link() returns -ENOMEM when called from soc_tplg_fe_link_create(). Because of that, the link will not get added into the card list, so any attempt to remove it later ends up in a panic. Fix that by checking the return status and free the memory in case of an error. Reviewed-by: Ranjani Sridharan Signed-off-by: Dragos Tarcatu Signed-off-by: Pierre-Louis Bossart Link: https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Khalid Elmously [Impact] During the boot, the sof driver crash because the hdmi_pcm_list is not initialized before it is used. [Fix] This bug is fixed in the mainline kernel v5.6-rc1, now backport this patch to ubuntu kernel [Test Case] Boot the -41 kernel with this patch added. blacklist the snd_soc_skl the kernel can boot successfully, and sof driver worked well [Regression Risk] Low, the patches are backported from upstream kernel, and I tested this patch on Lenovo and Dell dmic machines. Focal kernel already has this patch and works well. Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447]
[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected
I am having this problem (only dummy output) on ubuntu 19.10 with linux kernel 5.3.0.45.38. After booting I can make the output show up and work by running pulseaudio -k && sudo alsa force-reload Maybe that workaround helps other people suffering from this problem until a fix is available. -- 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/1864061 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: The sof-pci-dev and snd-soc-skl all contains the same pciid, if the soc-skl is loaded ahead of sof-pci-dev, the sof driver will not work anymore, in the oem project, we manually put the soc-skl in the blacklist. From kernel-5.4 (focal kernel), the driver soc-skl is disabled by default, and there is no users report any issues on it. So let us disable soc-skl in the eoan and osp1 kernel too. The patch for eoan kernel doesn't remove the modules because looks like the abi folder are not controlled by git. This will break the modulecheck, so if this patch could be merged, please help remove those modules: snd-soc-skl snd-soc-skl-ipc snd-soc-skl-ssp-clk [Impact] If soc-skl driver is loaded ahead of sof driver, the sof could not work anymore, we need to blacklist the soc-skl manually [Fix] Like the focal kernel, we disable the soc_skl driver in the kernel config [Test Case] Tested on Lenovo and Dell machines which has dmic, the sof driver could be loaded successfully. Tested on the machinces without the dmic, the legacy hda driver worked well as before. [Regression Risk] Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this dirver; and We have not met a machine need the soc_skl driver yet; and Intel claim that the sof could replace the soc_skl driver. In the -41 kernel, we introduced a patch from stable kernel, that make the sof driver crash, and there is a fix patch in the 5.6-rc1, and this fix patch is already in the stable and is merged to focal kernel, now we backport this patch to Eoan kernel if -42 doesn't introduce this fix patch from stable. The patch introduced the crash: commit 063821115e02229d5fd3de31bad270d5e30aeb41 Author: Dragos Tarcatu Date: Mon Dec 9 18:39:38 2019 -0600 ASoC: topology: Check return value for snd_soc_add_dai_link() BugLink: https://bugs.launchpad.net/bugs/1861929 [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ] snd_soc_add_dai_link() might fail. This situation occurs for instance in a very specific use case where a PCM device and a Back End DAI link are given identical names in the topology. When this happens, soc_new_pcm_runtime() fails and then snd_soc_add_dai_link() returns -ENOMEM when called from soc_tplg_fe_link_create(). Because of that, the link will not get added into the card list, so any attempt to remove it later ends up in a panic. Fix that by checking the return status and free the memory in case of an error. Reviewed-by: Ranjani Sridharan Signed-off-by: Dragos Tarcatu Signed-off-by: Pierre-Louis Bossart Link: https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Khalid Elmously [Impact] During the boot, the sof driver crash because the hdmi_pcm_list is not initialized before it is used. [Fix] This bug is fixed in the mainline kernel v5.6-rc1, now backport this patch to ubuntu kernel [Test Case] Boot the -41 kernel with this patch added. blacklist the snd_soc_skl the kernel can boot successfully, and sof driver worked well [Regression Risk] Low, the patches are backported from upstream kernel, and I tested this patch on Lenovo and Dell dmic machines. Focal kernel already has this patch and works well. Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -22 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error:
[Kernel-packages] [Bug 1763774] Re: nvidia-driver-390 GDM black screen / hang after login
I also have the same problem on Ubuntu 18.04.2.
The login screen starts normally, but right after typing my password and
pressing enter the screen is black.
The problem started after an NVIDIA driver update with "apt upgrade". I was
using the nvidia driver form the CUDA Repository.
I tried removing and reinstalling nvidia-390 from Ubuntu repos, 410 and 418
from cuda repo and 418 runfile installer from NVIDIA Homepage. The bug is the
same for all driver versions.
When I uninstall nvidia driver und use nouveau, everything is fine.
Also when using the nvidia driver i can login with SSH and `systemctl stop
gdm.service` + `systemctl start gdm.service`, then login works fine.
Finally switching to lightdm also works now as workaround.
--
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/1763774
Title:
nvidia-driver-390 GDM black screen / hang after login
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Confirmed
Bug description:
Ubuntu 18.04 x64 / gdm
AMD 1800x
Aorus Gaming K7 (x370 chipset) motherboard
NVidia GTX 1080Ti w/ DisplayPort attached 4k monitor
USB keyboard / mouse
I've recently upgraded from Ubuntu 17.10 x64 to 18.04 x64 via
`do-release-upgrade -d` and uninstalled / purged / reinstalled my NVidia
native drivers using the `ubuntu-drivers autoinstall` approach.
I am able to boot the system and it displays the X login shell at native
resolution with a functioning keyboard and mouse, but I cannot
ctrl+alt+F{1,2,3,4,...} to a non-graphical terminal.
When I click "Sign in" using gnome 3, gnome classic, or Unity, I get a
black screen and my input devices hang (keyboard caps lock key no longer
functions.) If I unplug and replug my input devices, they remain
hanging, with a stuck-on capslock indicator. The mouse is also
illuminated.
I am able to SSH into the machine, and it is still usable. systemctl
status gdm.service indicates that gdm is "running" and does not show an
error, but it shows that the login session opened and closed very quickly.
I rebooted and SSH'd into the machine before the hang, halted GDM via
`systemctl stop gdm.service` and was able to ctrl+alt+F1 into another
shell on the attached keyboard. I then executed `systemctl restart
gdm.service` and got the expected X login shell. I was then able to log
into the desktop environment normally.
My Xorg.0.log is here for the successful login:
https://paste.ubuntu.com/p/SNqJPxV938/
I'll reproduce the behavior and attach an xorg log for the unexpected
behavior.
Bodie
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nvidia-driver-390 390.48-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Fri Apr 13 12:43:48 2018
InstallationDate: Installed on 2017-10-30 (165 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: nvidia-graphics-drivers-390
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/1763774/+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 1686189] Re: External monitor connecting problem on Intel graphics card
I tried Ubuntu 17.04, still the same issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1686189] Re: External monitor connecting problem on Intel graphics card
The drm nightly kernel works for me (4.12.0-994-lowlatency). However, I do not have WLAN. -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1686189] Re: External monitor connecting problem on Intel graphics card
@Kai-Heng: I do use a mini Displayport Cable with a Lenovo Thinkpad T460S. In the meantime I tried every kernel I could install using ukuu. However, none of them worked. Prior to Ukuu I did use a kernel from the nightly builds (drm-intel) and the monitor worked but WLAN not. Therefore, I deinstalled it. Unfortunately, I cannot remember which kernel it was. -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1686189] Re: External monitor connecting problem on Intel graphics card
Still the same issue: 4.11.7-041107-generic #201706240231 SMP Sat Jun 24 06:33:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 07) i915 1495040 9 i2c_algo_bit 16384 1 i915 drm_kms_helper155648 1 i915 drm 352256 10 i915,drm_kms_helper video 40960 2 thinkpad_acpi,i915 -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1699772] Re: linux-image-4.4.0-81-generic Regression: Oracle Java plugin crashes
This should affect all embedded java uses which launch the JVM on the main thread (the regular java launcher does not do that) and is caused by the known buggy (http://www.openwall.com/lists/oss- security/2017/06/22/6) custom CVE-2017-1000364 fix. Testing the upstream patch on debian it seems to be fine (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=865549). ** Bug watch added: Debian Bug tracker #865549 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865549 -- 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/1699772 Title: linux-image-4.4.0-81-generic Regression: Oracle Java plugin crashes Status in eclipse package in Ubuntu: New Status in imagej package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1699772/+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 1592429] Re: trusty kernel crash in OOM killer related to cgroups
I've installed the 3.13.0-92.139 kernel from trusty-proposed on eight production systems. I'll let you know by Monday. -- 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/1592429 Title: trusty kernel crash in OOM killer related to cgroups Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Bug description: The trusty kernel can crash if the OOM killer kills processes which have reached a memory limit imposed by cgroups. More details can be found in this blog post: https://community.nitrous.io/posts/stability-and-a-linux-oom-killer- bug The upstream patch series which ultimately landed in 3.14 is available at: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=4d4048be8a93769350efa31d2482a038b7de73d0=range=9853a407b97d8d066b5a865173a4859a3e69fd8a...4d4048be8a93769350efa31d2482a038b7de73d0 One of those four (0c740d0afc3bff0a097ad03a1c8df92757516f5c) is already part of the trusty kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592429/+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 1592429] Re: trusty kernel crash in OOM killer related to cgroups
This looks good to me: We have been running the test kernel on nine production servers for more than a week now and the systems are stable (while previous we'd seen three kernel hands over the course of 48 hours). -- 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/1592429 Title: trusty kernel crash in OOM killer related to cgroups Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: The trusty kernel can crash if the OOM killer kills processes which have reached a memory limit imposed by cgroups. More details can be found in this blog post: https://community.nitrous.io/posts/stability-and-a-linux-oom-killer- bug The upstream patch series which ultimately landed in 3.14 is available at: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=4d4048be8a93769350efa31d2482a038b7de73d0=range=9853a407b97d8d066b5a865173a4859a3e69fd8a...4d4048be8a93769350efa31d2482a038b7de73d0 One of those four (0c740d0afc3bff0a097ad03a1c8df92757516f5c) is already part of the trusty kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592429/+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 1592429] [NEW] trusty kernel crash in OOM killer related to cgroups
Public bug reported: The trusty kernel can crash if the OOM killer kills processes which have reached a memory limit imposed by cgroups. More details can be found in this blog post: https://community.nitrous.io/posts/stability-and-a-linux-oom-killer-bug The upstream patch series which ultimately landed in 3.14 is available at: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=4d4048be8a93769350efa31d2482a038b7de73d0=range=9853a407b97d8d066b5a865173a4859a3e69fd8a...4d4048be8a93769350efa31d2482a038b7de73d0 One of those four (0c740d0afc3bff0a097ad03a1c8df92757516f5c) is already part of the trusty kernel. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: trusty -- 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/1592429 Title: trusty kernel crash in OOM killer related to cgroups Status in linux package in Ubuntu: In Progress Bug description: The trusty kernel can crash if the OOM killer kills processes which have reached a memory limit imposed by cgroups. More details can be found in this blog post: https://community.nitrous.io/posts/stability-and-a-linux-oom-killer- bug The upstream patch series which ultimately landed in 3.14 is available at: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=4d4048be8a93769350efa31d2482a038b7de73d0=range=9853a407b97d8d066b5a865173a4859a3e69fd8a...4d4048be8a93769350efa31d2482a038b7de73d0 One of those four (0c740d0afc3bff0a097ad03a1c8df92757516f5c) is already part of the trusty kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592429/+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 1451789] Re: bcmwl causes system freeze
Could we please fast-track this solution? My laptop is crashing every other hour because of it :/ -- 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/1451789 Title: bcmwl causes system freeze Status in bcmwl package in Ubuntu: Triaged Bug description: I'll file a bugzilla port on kernel.org with the kernel logs and post the reference here asap. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Tue May 5 13:18:34 2015 InstallationDate: Installed on 2014-04-26 (373 days ago) InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: bcmwl UpgradeStatus: Upgraded to vivid on 2015-04-24 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1451789/+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 1449401] Re: After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno
Thanks for the hint, Timo! 3.16.0-37.51 also doesn't boot on my T450s. Boot process gets stuck displaying: Loading Linux 3.16.0-37-generic Loading initial ramdisk I installed the .deb from the link you provided, Timo, and aptitude tells me the -51 version is installed: $ sudo aptitude show linux-image-3.16.0-37-generic [...] Package: linux-image-3.16.0-37-generic New: yes State: installed Automatically installed: no Version: 3.16.0-37.51 3.16.0-34.47 is still the last kernel that works for me, although not perfectly (rendering issues when using SNA, fallback to UXA makes system usable but with partially very bad 2D graphics performance). -- 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/1449401 Title: After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: Fix Released Bug description: This happens everytime I boot after updating kernel from 3.16.0-34 to 3.16.0-36. Keeping 3.16.0-34 still works. Blackscreen is illuminated. I do not see any splash screen, nor X. Failsafe mode works, booting with nomodeset works (but it's slow). When this happens, on the next reboot I do see some BUG: lines in syslog, like: Apr 27 21:01:54 portable-alex kernel: [2.457904] BUG: unable to handle kernel NULL pointer dereference at (null) Apr 27 21:01:54 portable-alex kernel: [2.457911] IP: [ (null)] (null) Apr 27 21:01:54 portable-alex kernel: [2.457913] PGD 51b93d067 PUD 51b8ec067 PMD 0 Apr 27 21:01:54 portable-alex kernel: [2.457916] Oops: 0010 [#1] SMP Apr 27 21:01:54 portable-alex kernel: [2.457918] Modules linked in: rtsx_pci_sdmmc i915(+) e1000e ahci ptp i2c_algo_bit drm_kms_helper libahci pps_core psmouse drm rtsx_pci wmi video Apr 27 21:01:54 portable-alex kernel: [2.457926] CPU: 0 PID: 128 Comm: systemd-udevd Not tainted 3.16.0-36-generic #48-Ubuntu Apr 27 21:01:54 portable-alex kernel: [2.457929] Hardware name: LENOVO 20BXCTO1WW/20BXCTO1WW, BIOS JBET45WW (1.10 ) 02/03/2015 Apr 27 21:01:54 portable-alex kernel: [2.457930] task: 88051be6bd20 ti: 88051b9a8000 task.ti: 88051b9a8000 Apr 27 21:01:54 portable-alex kernel: [2.457932] RIP: 0010:[] [ (null)] (null) Apr 27 21:01:54 portable-alex kernel: [2.457934] RSP: 0018:88051b9ab890 EFLAGS: 00010286 Apr 27 21:01:54 portable-alex kernel: [2.457936] RAX: 0246 RBX: 88051bbb1928 RCX: 0001 Apr 27 21:01:54 portable-alex kernel: [2.457937] RDX: 0001 RSI: effe RDI: 88051bbb1928 Apr 27 21:01:54 portable-alex kernel: [2.457938] RBP: 88051b9ab8b0 R08: 88051bbb R09: 0246 Apr 27 21:01:54 portable-alex kernel: [2.457940] R10: 880529403900 R11: 811a6ddf R12: effe Apr 27 21:01:54 portable-alex kernel: [2.457941] R13: 88051bbb R14: effe R15: 88051bf90800 Apr 27 21:01:54 portable-alex kernel: [2.457942] FS: 7f8127b4f880() GS:88053dc0() knlGS: Apr 27 21:01:54 portable-alex kernel: [2.457944] CS: 0010 DS: ES: CR0: 80050033 Apr 27 21:01:54 portable-alex kernel: [2.457945] CR2: CR3: 00051b942000 CR4: 003407f0 Apr 27 21:01:54 portable-alex kernel: [2.457947] DR0: DR1: DR2: Apr 27 21:01:54 portable-alex kernel: [2.457948] DR3: DR6: fffe0ff0 DR7: 0400 Apr 27 21:01:54 portable-alex kernel: [2.457949] Stack: Apr 27 21:01:54 portable-alex kernel: [2.457950] c02499fd 88051bbb1928 88051bbb7148 88051bbb7148 Apr 27 21:01:54 portable-alex kernel: [2.457953] 88051b9ab8e8 c022e5b7 efff effe Apr 27 21:01:54 portable-alex kernel: [2.457955] 88051bbb 88051bbb 88051bbb 88051b9ab910 Apr 27 21:01:54 portable-alex kernel: [2.457957] Call Trace: Apr 27 21:01:54 portable-alex kernel: [2.457977] [c02499fd] ? intel_ring_init_seqno+0x3d/0xb0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.457991] [c022e5b7] i915_gem_init_seqno+0x77/0xc0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458002] [c022e629] i915_gem_set_seqno+0x29/0x60 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458013] [c022fdcd] i915_gem_init_hw+0x12d/0x380 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458022] [c0230075] i915_gem_init+0x55/0x1d0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458039] [c02956a2]
[Kernel-packages] [Bug 1449401] Re: After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno
I have to correct my last comment: 3.16.0-37.51 does boot. I had to install the linux-image-extra package, too, which I didn't in the first try. -- 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/1449401 Title: After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: Fix Released Bug description: This happens everytime I boot after updating kernel from 3.16.0-34 to 3.16.0-36. Keeping 3.16.0-34 still works. Blackscreen is illuminated. I do not see any splash screen, nor X. Failsafe mode works, booting with nomodeset works (but it's slow). When this happens, on the next reboot I do see some BUG: lines in syslog, like: Apr 27 21:01:54 portable-alex kernel: [2.457904] BUG: unable to handle kernel NULL pointer dereference at (null) Apr 27 21:01:54 portable-alex kernel: [2.457911] IP: [ (null)] (null) Apr 27 21:01:54 portable-alex kernel: [2.457913] PGD 51b93d067 PUD 51b8ec067 PMD 0 Apr 27 21:01:54 portable-alex kernel: [2.457916] Oops: 0010 [#1] SMP Apr 27 21:01:54 portable-alex kernel: [2.457918] Modules linked in: rtsx_pci_sdmmc i915(+) e1000e ahci ptp i2c_algo_bit drm_kms_helper libahci pps_core psmouse drm rtsx_pci wmi video Apr 27 21:01:54 portable-alex kernel: [2.457926] CPU: 0 PID: 128 Comm: systemd-udevd Not tainted 3.16.0-36-generic #48-Ubuntu Apr 27 21:01:54 portable-alex kernel: [2.457929] Hardware name: LENOVO 20BXCTO1WW/20BXCTO1WW, BIOS JBET45WW (1.10 ) 02/03/2015 Apr 27 21:01:54 portable-alex kernel: [2.457930] task: 88051be6bd20 ti: 88051b9a8000 task.ti: 88051b9a8000 Apr 27 21:01:54 portable-alex kernel: [2.457932] RIP: 0010:[] [ (null)] (null) Apr 27 21:01:54 portable-alex kernel: [2.457934] RSP: 0018:88051b9ab890 EFLAGS: 00010286 Apr 27 21:01:54 portable-alex kernel: [2.457936] RAX: 0246 RBX: 88051bbb1928 RCX: 0001 Apr 27 21:01:54 portable-alex kernel: [2.457937] RDX: 0001 RSI: effe RDI: 88051bbb1928 Apr 27 21:01:54 portable-alex kernel: [2.457938] RBP: 88051b9ab8b0 R08: 88051bbb R09: 0246 Apr 27 21:01:54 portable-alex kernel: [2.457940] R10: 880529403900 R11: 811a6ddf R12: effe Apr 27 21:01:54 portable-alex kernel: [2.457941] R13: 88051bbb R14: effe R15: 88051bf90800 Apr 27 21:01:54 portable-alex kernel: [2.457942] FS: 7f8127b4f880() GS:88053dc0() knlGS: Apr 27 21:01:54 portable-alex kernel: [2.457944] CS: 0010 DS: ES: CR0: 80050033 Apr 27 21:01:54 portable-alex kernel: [2.457945] CR2: CR3: 00051b942000 CR4: 003407f0 Apr 27 21:01:54 portable-alex kernel: [2.457947] DR0: DR1: DR2: Apr 27 21:01:54 portable-alex kernel: [2.457948] DR3: DR6: fffe0ff0 DR7: 0400 Apr 27 21:01:54 portable-alex kernel: [2.457949] Stack: Apr 27 21:01:54 portable-alex kernel: [2.457950] c02499fd 88051bbb1928 88051bbb7148 88051bbb7148 Apr 27 21:01:54 portable-alex kernel: [2.457953] 88051b9ab8e8 c022e5b7 efff effe Apr 27 21:01:54 portable-alex kernel: [2.457955] 88051bbb 88051bbb 88051bbb 88051b9ab910 Apr 27 21:01:54 portable-alex kernel: [2.457957] Call Trace: Apr 27 21:01:54 portable-alex kernel: [2.457977] [c02499fd] ? intel_ring_init_seqno+0x3d/0xb0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.457991] [c022e5b7] i915_gem_init_seqno+0x77/0xc0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458002] [c022e629] i915_gem_set_seqno+0x29/0x60 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458013] [c022fdcd] i915_gem_init_hw+0x12d/0x380 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458022] [c0230075] i915_gem_init+0x55/0x1d0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458039] [c02956a2] i915_driver_load+0xe32/0x1030 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458042] [813a05e8] ? kobject_uevent_env+0x178/0x690 Apr 27 21:01:54 portable-alex kernel: [2.458046] [814cf087] ? get_device+0x17/0x30 Apr 27 21:01:54 portable-alex kernel: [2.458048] [814d4af5] ? klist_class_dev_get+0x15/0x20 Apr 27 21:01:54 portable-alex kernel: [2.458051] [817773b8] ? klist_node_init+0x38/0x60 Apr 27 21:01:54 portable-alex kernel: [2.458054]
[Kernel-packages] [Bug 1450156] Re: kernel 3.16.0-36 won't boot on Lenovo Thinkpad X1 Carbon 3rd Gen
To confirm Stoepsel: 3.16.0-37 doesn't boot on my Thinkpad T450s either. -- 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/1450156 Title: kernel 3.16.0-36 won't boot on Lenovo Thinkpad X1 Carbon 3rd Gen Status in linux package in Ubuntu: In Progress Status in linux-lts-utopic package in Ubuntu: Confirmed Status in linux source package in Utopic: In Progress Status in linux-lts-utopic source package in Utopic: Confirmed Bug description: Brand new install. I have several of these machines all have been happy on 3.16.0-34. Today I did an install the post-install updates picked up 3.16.0-36 now it won't boot successfully -- black screen, backlight still lit, no response to any keyboard input. I downloaded installed the current mainline upstream kernel it works fine. This bit from kern.log appears to be salient: Apr 29 14:44:39 eb-thinkpad- kernel: [1.397152] BUG: unable to handle kernel NULL pointer dereference at (null) Apr 29 14:44:39 eb-thinkpad- kernel: [1.397156] IP: [ (null)] (null) Apr 29 14:44:39 eb-thinkpad- kernel: [1.397158] PGD 21f49e067 PUD 21fa04067 PMD 0 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397161] Oops: 0010 [#1] SMP Apr 29 14:44:39 eb-thinkpad- kernel: [1.397163] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_intel(+) snd_hda_controller serio_raw snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hwdep lpc_ich(+) snd_rawmidi snd_pcm snd_seq wmi snd_seq_device snd_timer shpchp(+) thinkpad_acpi nvram parport_pc mei_me(+) mac_hid ppdev i915(+) mei snd lp parport video drm_kms_helper soundcore drm i2c_algo_bit e1000e psmouse ahci ptp libahci pps_core Apr 29 14:44:39 eb-thinkpad- kernel: [1.397188] CPU: 0 PID: 337 Comm: systemd-udevd Not tainted 3.16.0-36-generic #48~14.04.1-Ubuntu Apr 29 14:44:39 eb-thinkpad- kernel: [1.397190] Hardware name: LENOVO 20BTS1KH00/20BTS1KH00, BIOS N14ET26W (1.04 ) 01/23/2015 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397192] task: 88021fadd180 ti: 88021f6d8000 task.ti: 88021f6d8000 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397193] RIP: 0010:[] [ (null)] (null) Apr 29 14:44:39 eb-thinkpad- kernel: [1.397195] RSP: 0018:88021f6db8a0 EFLAGS: 00010282 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397197] RAX: 0246 RBX: 880036861928 RCX: 0001 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397198] RDX: 0001 RSI: effe RDI: 880036861928 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397199] RBP: 88021f6db8c0 R08: 0246 R09: 000b Apr 29 14:44:39 eb-thinkpad- kernel: [1.397201] R10: e01a3000 R11: 8119bc1f R12: 88003686 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397202] R13: effe R14: effe R15: 8800b88b3800 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397204] FS: 7f97b75b1880() GS:88022dc0() knlGS: Apr 29 14:44:39 eb-thinkpad- kernel: [1.397205] CS: 0010 DS: ES: CR0: 80050033 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397206] CR2: CR3: 00021f69a000 CR4: 003407f0 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397208] DR0: DR1: DR2: Apr 29 14:44:39 eb-thinkpad- kernel: [1.397209] DR3: DR6: fffe0ff0 DR7: 0400 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397210] Stack: Apr 29 14:44:39 eb-thinkpad- kernel: [1.397211] c03ed88e 880036861928 0005 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397214] 88021f6db8f8 c03d2c5d efff effe Apr 29 14:44:39 eb-thinkpad- kernel: [1.397217] 88003686 88003686 88003686 88021f6db920 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397219] Call Trace: Apr 29 14:44:39 eb-thinkpad- kernel: [1.397246] [c03ed88e] ? intel_ring_init_seqno+0x3e/0xb0 [i915] Apr 29 14:44:39 eb-thinkpad- kernel: [1.397265] [c03d2c5d] i915_gem_init_seqno+0x7d/0xc0 [i915] Apr 29 14:44:39 eb-thinkpad- kernel: [1.397280] [c03d2cc9] i915_gem_set_seqno+0x29/0x60 [i915] Apr 29 14:44:39 eb-thinkpad- kernel: [1.397296] [c03d44bd] i915_gem_init_hw+0x1cd/0x3a0 [i915] Apr 29 14:44:39 eb-thinkpad- kernel: [1.397309] [c03d46e5] i915_gem_init+0x55/0x1d0 [i915] Apr 29 14:44:39 eb-thinkpad-
[Kernel-packages] [Bug 1449401] Re: After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno
If someone could point me to a doc on how to install 3.16.0-37.51 in Trusty, I would be happy to test it. I enabled the proposed repository and tried sudo apt-get install linux- image-3.16.0-37-generic/trusty-proposed but it tells me I already have the newest version, which is 3.16.0-37.49~14.04.1. -- 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/1449401 Title: After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: Fix Released Bug description: This happens everytime I boot after updating kernel from 3.16.0-34 to 3.16.0-36. Keeping 3.16.0-34 still works. Blackscreen is illuminated. I do not see any splash screen, nor X. Failsafe mode works, booting with nomodeset works (but it's slow). When this happens, on the next reboot I do see some BUG: lines in syslog, like: Apr 27 21:01:54 portable-alex kernel: [2.457904] BUG: unable to handle kernel NULL pointer dereference at (null) Apr 27 21:01:54 portable-alex kernel: [2.457911] IP: [ (null)] (null) Apr 27 21:01:54 portable-alex kernel: [2.457913] PGD 51b93d067 PUD 51b8ec067 PMD 0 Apr 27 21:01:54 portable-alex kernel: [2.457916] Oops: 0010 [#1] SMP Apr 27 21:01:54 portable-alex kernel: [2.457918] Modules linked in: rtsx_pci_sdmmc i915(+) e1000e ahci ptp i2c_algo_bit drm_kms_helper libahci pps_core psmouse drm rtsx_pci wmi video Apr 27 21:01:54 portable-alex kernel: [2.457926] CPU: 0 PID: 128 Comm: systemd-udevd Not tainted 3.16.0-36-generic #48-Ubuntu Apr 27 21:01:54 portable-alex kernel: [2.457929] Hardware name: LENOVO 20BXCTO1WW/20BXCTO1WW, BIOS JBET45WW (1.10 ) 02/03/2015 Apr 27 21:01:54 portable-alex kernel: [2.457930] task: 88051be6bd20 ti: 88051b9a8000 task.ti: 88051b9a8000 Apr 27 21:01:54 portable-alex kernel: [2.457932] RIP: 0010:[] [ (null)] (null) Apr 27 21:01:54 portable-alex kernel: [2.457934] RSP: 0018:88051b9ab890 EFLAGS: 00010286 Apr 27 21:01:54 portable-alex kernel: [2.457936] RAX: 0246 RBX: 88051bbb1928 RCX: 0001 Apr 27 21:01:54 portable-alex kernel: [2.457937] RDX: 0001 RSI: effe RDI: 88051bbb1928 Apr 27 21:01:54 portable-alex kernel: [2.457938] RBP: 88051b9ab8b0 R08: 88051bbb R09: 0246 Apr 27 21:01:54 portable-alex kernel: [2.457940] R10: 880529403900 R11: 811a6ddf R12: effe Apr 27 21:01:54 portable-alex kernel: [2.457941] R13: 88051bbb R14: effe R15: 88051bf90800 Apr 27 21:01:54 portable-alex kernel: [2.457942] FS: 7f8127b4f880() GS:88053dc0() knlGS: Apr 27 21:01:54 portable-alex kernel: [2.457944] CS: 0010 DS: ES: CR0: 80050033 Apr 27 21:01:54 portable-alex kernel: [2.457945] CR2: CR3: 00051b942000 CR4: 003407f0 Apr 27 21:01:54 portable-alex kernel: [2.457947] DR0: DR1: DR2: Apr 27 21:01:54 portable-alex kernel: [2.457948] DR3: DR6: fffe0ff0 DR7: 0400 Apr 27 21:01:54 portable-alex kernel: [2.457949] Stack: Apr 27 21:01:54 portable-alex kernel: [2.457950] c02499fd 88051bbb1928 88051bbb7148 88051bbb7148 Apr 27 21:01:54 portable-alex kernel: [2.457953] 88051b9ab8e8 c022e5b7 efff effe Apr 27 21:01:54 portable-alex kernel: [2.457955] 88051bbb 88051bbb 88051bbb 88051b9ab910 Apr 27 21:01:54 portable-alex kernel: [2.457957] Call Trace: Apr 27 21:01:54 portable-alex kernel: [2.457977] [c02499fd] ? intel_ring_init_seqno+0x3d/0xb0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.457991] [c022e5b7] i915_gem_init_seqno+0x77/0xc0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458002] [c022e629] i915_gem_set_seqno+0x29/0x60 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458013] [c022fdcd] i915_gem_init_hw+0x12d/0x380 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458022] [c0230075] i915_gem_init+0x55/0x1d0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458039] [c02956a2] i915_driver_load+0xe32/0x1030 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458042] [813a05e8] ? kobject_uevent_env+0x178/0x690 Apr 27 21:01:54 portable-alex kernel: [2.458046] [814cf087] ? get_device+0x17/0x30 Apr 27 21:01:54 portable-alex kernel: [2.458048] [814d4af5] ? klist_class_dev_get+0x15/0x20 Apr 27
[Kernel-packages] [Bug 1449401] Re: After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno
The one in the public Trusty repositories (3.16.0-37.49~14.04.1.) doesn't work on my T450s. I don't know how to install 3.16.0-37.51. I have the proposed repository enabled and tried sudo apt-get install linux-image-3.16.0-37-generic /trusty-proposed but it tells me I already have the newest version (-49). -- 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/1449401 Title: After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: Fix Released Bug description: This happens everytime I boot after updating kernel from 3.16.0-34 to 3.16.0-36. Keeping 3.16.0-34 still works. Blackscreen is illuminated. I do not see any splash screen, nor X. Failsafe mode works, booting with nomodeset works (but it's slow). When this happens, on the next reboot I do see some BUG: lines in syslog, like: Apr 27 21:01:54 portable-alex kernel: [2.457904] BUG: unable to handle kernel NULL pointer dereference at (null) Apr 27 21:01:54 portable-alex kernel: [2.457911] IP: [ (null)] (null) Apr 27 21:01:54 portable-alex kernel: [2.457913] PGD 51b93d067 PUD 51b8ec067 PMD 0 Apr 27 21:01:54 portable-alex kernel: [2.457916] Oops: 0010 [#1] SMP Apr 27 21:01:54 portable-alex kernel: [2.457918] Modules linked in: rtsx_pci_sdmmc i915(+) e1000e ahci ptp i2c_algo_bit drm_kms_helper libahci pps_core psmouse drm rtsx_pci wmi video Apr 27 21:01:54 portable-alex kernel: [2.457926] CPU: 0 PID: 128 Comm: systemd-udevd Not tainted 3.16.0-36-generic #48-Ubuntu Apr 27 21:01:54 portable-alex kernel: [2.457929] Hardware name: LENOVO 20BXCTO1WW/20BXCTO1WW, BIOS JBET45WW (1.10 ) 02/03/2015 Apr 27 21:01:54 portable-alex kernel: [2.457930] task: 88051be6bd20 ti: 88051b9a8000 task.ti: 88051b9a8000 Apr 27 21:01:54 portable-alex kernel: [2.457932] RIP: 0010:[] [ (null)] (null) Apr 27 21:01:54 portable-alex kernel: [2.457934] RSP: 0018:88051b9ab890 EFLAGS: 00010286 Apr 27 21:01:54 portable-alex kernel: [2.457936] RAX: 0246 RBX: 88051bbb1928 RCX: 0001 Apr 27 21:01:54 portable-alex kernel: [2.457937] RDX: 0001 RSI: effe RDI: 88051bbb1928 Apr 27 21:01:54 portable-alex kernel: [2.457938] RBP: 88051b9ab8b0 R08: 88051bbb R09: 0246 Apr 27 21:01:54 portable-alex kernel: [2.457940] R10: 880529403900 R11: 811a6ddf R12: effe Apr 27 21:01:54 portable-alex kernel: [2.457941] R13: 88051bbb R14: effe R15: 88051bf90800 Apr 27 21:01:54 portable-alex kernel: [2.457942] FS: 7f8127b4f880() GS:88053dc0() knlGS: Apr 27 21:01:54 portable-alex kernel: [2.457944] CS: 0010 DS: ES: CR0: 80050033 Apr 27 21:01:54 portable-alex kernel: [2.457945] CR2: CR3: 00051b942000 CR4: 003407f0 Apr 27 21:01:54 portable-alex kernel: [2.457947] DR0: DR1: DR2: Apr 27 21:01:54 portable-alex kernel: [2.457948] DR3: DR6: fffe0ff0 DR7: 0400 Apr 27 21:01:54 portable-alex kernel: [2.457949] Stack: Apr 27 21:01:54 portable-alex kernel: [2.457950] c02499fd 88051bbb1928 88051bbb7148 88051bbb7148 Apr 27 21:01:54 portable-alex kernel: [2.457953] 88051b9ab8e8 c022e5b7 efff effe Apr 27 21:01:54 portable-alex kernel: [2.457955] 88051bbb 88051bbb 88051bbb 88051b9ab910 Apr 27 21:01:54 portable-alex kernel: [2.457957] Call Trace: Apr 27 21:01:54 portable-alex kernel: [2.457977] [c02499fd] ? intel_ring_init_seqno+0x3d/0xb0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.457991] [c022e5b7] i915_gem_init_seqno+0x77/0xc0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458002] [c022e629] i915_gem_set_seqno+0x29/0x60 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458013] [c022fdcd] i915_gem_init_hw+0x12d/0x380 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458022] [c0230075] i915_gem_init+0x55/0x1d0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458039] [c02956a2] i915_driver_load+0xe32/0x1030 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458042] [813a05e8] ? kobject_uevent_env+0x178/0x690 Apr 27 21:01:54 portable-alex kernel: [2.458046] [814cf087] ? get_device+0x17/0x30 Apr 27 21:01:54 portable-alex kernel: [2.458048] [814d4af5] ? klist_class_dev_get+0x15/0x20 Apr
[Kernel-packages] [Bug 1450156] Re: kernel 3.16.0-36 won't boot on Lenovo Thinkpad X1 Carbon 3rd Gen
I think I have the same problem with a Thinkpad T450s. Kernel 3.16.0-34 boots fine. Trying to boot 3.16.0-36 instead shows the same behaviour as reported in bug description. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1450156 Title: kernel 3.16.0-36 won't boot on Lenovo Thinkpad X1 Carbon 3rd Gen Status in linux-lts-utopic package in Ubuntu: Confirmed Bug description: Brand new install. I have several of these machines all have been happy on 3.16.0-34. Today I did an install the post-install updates picked up 3.16.0-36 now it won't boot successfully -- black screen, backlight still lit, no response to any keyboard input. I downloaded installed the current mainline upstream kernel it works fine. This bit from kern.log appears to be salient: Apr 29 14:44:39 eb-thinkpad- kernel: [1.397152] BUG: unable to handle kernel NULL pointer dereference at (null) Apr 29 14:44:39 eb-thinkpad- kernel: [1.397156] IP: [ (null)] (null) Apr 29 14:44:39 eb-thinkpad- kernel: [1.397158] PGD 21f49e067 PUD 21fa04067 PMD 0 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397161] Oops: 0010 [#1] SMP Apr 29 14:44:39 eb-thinkpad- kernel: [1.397163] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_intel(+) snd_hda_controller serio_raw snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hwdep lpc_ich(+) snd_rawmidi snd_pcm snd_seq wmi snd_seq_device snd_timer shpchp(+) thinkpad_acpi nvram parport_pc mei_me(+) mac_hid ppdev i915(+) mei snd lp parport video drm_kms_helper soundcore drm i2c_algo_bit e1000e psmouse ahci ptp libahci pps_core Apr 29 14:44:39 eb-thinkpad- kernel: [1.397188] CPU: 0 PID: 337 Comm: systemd-udevd Not tainted 3.16.0-36-generic #48~14.04.1-Ubuntu Apr 29 14:44:39 eb-thinkpad- kernel: [1.397190] Hardware name: LENOVO 20BTS1KH00/20BTS1KH00, BIOS N14ET26W (1.04 ) 01/23/2015 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397192] task: 88021fadd180 ti: 88021f6d8000 task.ti: 88021f6d8000 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397193] RIP: 0010:[] [ (null)] (null) Apr 29 14:44:39 eb-thinkpad- kernel: [1.397195] RSP: 0018:88021f6db8a0 EFLAGS: 00010282 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397197] RAX: 0246 RBX: 880036861928 RCX: 0001 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397198] RDX: 0001 RSI: effe RDI: 880036861928 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397199] RBP: 88021f6db8c0 R08: 0246 R09: 000b Apr 29 14:44:39 eb-thinkpad- kernel: [1.397201] R10: e01a3000 R11: 8119bc1f R12: 88003686 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397202] R13: effe R14: effe R15: 8800b88b3800 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397204] FS: 7f97b75b1880() GS:88022dc0() knlGS: Apr 29 14:44:39 eb-thinkpad- kernel: [1.397205] CS: 0010 DS: ES: CR0: 80050033 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397206] CR2: CR3: 00021f69a000 CR4: 003407f0 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397208] DR0: DR1: DR2: Apr 29 14:44:39 eb-thinkpad- kernel: [1.397209] DR3: DR6: fffe0ff0 DR7: 0400 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397210] Stack: Apr 29 14:44:39 eb-thinkpad- kernel: [1.397211] c03ed88e 880036861928 0005 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397214] 88021f6db8f8 c03d2c5d efff effe Apr 29 14:44:39 eb-thinkpad- kernel: [1.397217] 88003686 88003686 88003686 88021f6db920 Apr 29 14:44:39 eb-thinkpad- kernel: [1.397219] Call Trace: Apr 29 14:44:39 eb-thinkpad- kernel: [1.397246] [c03ed88e] ? intel_ring_init_seqno+0x3e/0xb0 [i915] Apr 29 14:44:39 eb-thinkpad- kernel: [1.397265] [c03d2c5d] i915_gem_init_seqno+0x7d/0xc0 [i915] Apr 29 14:44:39 eb-thinkpad- kernel: [1.397280] [c03d2cc9] i915_gem_set_seqno+0x29/0x60 [i915] Apr 29 14:44:39 eb-thinkpad- kernel: [1.397296] [c03d44bd] i915_gem_init_hw+0x1cd/0x3a0 [i915] Apr 29 14:44:39 eb-thinkpad- kernel: [1.397309] [c03d46e5] i915_gem_init+0x55/0x1d0 [i915] Apr 29 14:44:39 eb-thinkpad- kernel: [1.397332] [c04385e2]
[Kernel-packages] [Bug 1449401] Re: After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno
Same problem on Thinkpad T450s (Broadwell chip) and Trusty. 3.16.0-34 works fine, 3.16.0-36 just shows black screen with backlight lit. -- 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/1449401 Title: After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno Status in linux package in Ubuntu: Triaged Bug description: This happens everytime I boot after updating kernel from 3.16.0-34 to 3.16.0-36. Keeping 3.16.0-34 still works. Blackscreen is illuminated. I do not see any splash screen, nor X. Failsafe mode works, booting with nomodeset works (but it's slow). When this happens, on the next reboot I do see some BUG: lines in syslog, like: Apr 27 21:01:54 portable-alex kernel: [2.457904] BUG: unable to handle kernel NULL pointer dereference at (null) Apr 27 21:01:54 portable-alex kernel: [2.457911] IP: [ (null)] (null) Apr 27 21:01:54 portable-alex kernel: [2.457913] PGD 51b93d067 PUD 51b8ec067 PMD 0 Apr 27 21:01:54 portable-alex kernel: [2.457916] Oops: 0010 [#1] SMP Apr 27 21:01:54 portable-alex kernel: [2.457918] Modules linked in: rtsx_pci_sdmmc i915(+) e1000e ahci ptp i2c_algo_bit drm_kms_helper libahci pps_core psmouse drm rtsx_pci wmi video Apr 27 21:01:54 portable-alex kernel: [2.457926] CPU: 0 PID: 128 Comm: systemd-udevd Not tainted 3.16.0-36-generic #48-Ubuntu Apr 27 21:01:54 portable-alex kernel: [2.457929] Hardware name: LENOVO 20BXCTO1WW/20BXCTO1WW, BIOS JBET45WW (1.10 ) 02/03/2015 Apr 27 21:01:54 portable-alex kernel: [2.457930] task: 88051be6bd20 ti: 88051b9a8000 task.ti: 88051b9a8000 Apr 27 21:01:54 portable-alex kernel: [2.457932] RIP: 0010:[] [ (null)] (null) Apr 27 21:01:54 portable-alex kernel: [2.457934] RSP: 0018:88051b9ab890 EFLAGS: 00010286 Apr 27 21:01:54 portable-alex kernel: [2.457936] RAX: 0246 RBX: 88051bbb1928 RCX: 0001 Apr 27 21:01:54 portable-alex kernel: [2.457937] RDX: 0001 RSI: effe RDI: 88051bbb1928 Apr 27 21:01:54 portable-alex kernel: [2.457938] RBP: 88051b9ab8b0 R08: 88051bbb R09: 0246 Apr 27 21:01:54 portable-alex kernel: [2.457940] R10: 880529403900 R11: 811a6ddf R12: effe Apr 27 21:01:54 portable-alex kernel: [2.457941] R13: 88051bbb R14: effe R15: 88051bf90800 Apr 27 21:01:54 portable-alex kernel: [2.457942] FS: 7f8127b4f880() GS:88053dc0() knlGS: Apr 27 21:01:54 portable-alex kernel: [2.457944] CS: 0010 DS: ES: CR0: 80050033 Apr 27 21:01:54 portable-alex kernel: [2.457945] CR2: CR3: 00051b942000 CR4: 003407f0 Apr 27 21:01:54 portable-alex kernel: [2.457947] DR0: DR1: DR2: Apr 27 21:01:54 portable-alex kernel: [2.457948] DR3: DR6: fffe0ff0 DR7: 0400 Apr 27 21:01:54 portable-alex kernel: [2.457949] Stack: Apr 27 21:01:54 portable-alex kernel: [2.457950] c02499fd 88051bbb1928 88051bbb7148 88051bbb7148 Apr 27 21:01:54 portable-alex kernel: [2.457953] 88051b9ab8e8 c022e5b7 efff effe Apr 27 21:01:54 portable-alex kernel: [2.457955] 88051bbb 88051bbb 88051bbb 88051b9ab910 Apr 27 21:01:54 portable-alex kernel: [2.457957] Call Trace: Apr 27 21:01:54 portable-alex kernel: [2.457977] [c02499fd] ? intel_ring_init_seqno+0x3d/0xb0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.457991] [c022e5b7] i915_gem_init_seqno+0x77/0xc0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458002] [c022e629] i915_gem_set_seqno+0x29/0x60 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458013] [c022fdcd] i915_gem_init_hw+0x12d/0x380 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458022] [c0230075] i915_gem_init+0x55/0x1d0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458039] [c02956a2] i915_driver_load+0xe32/0x1030 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458042] [813a05e8] ? kobject_uevent_env+0x178/0x690 Apr 27 21:01:54 portable-alex kernel: [2.458046] [814cf087] ? get_device+0x17/0x30 Apr 27 21:01:54 portable-alex kernel: [2.458048] [814d4af5] ? klist_class_dev_get+0x15/0x20 Apr 27 21:01:54 portable-alex kernel: [2.458051] [817773b8] ? klist_node_init+0x38/0x60 Apr 27 21:01:54 portable-alex kernel: [2.458054] [81777476] ? klist_add_tail+0x46/0x50 Apr 27 21:01:54
[Kernel-packages] [Bug 1272777] Re: Elantech touchpads not fully supported for some Gigabyte laptops
Hey guys, i'm on gigabyte u2442n and stopped using ubuntu a couple of month ago because of this bug (mainly use touchpad b/c travelling). Do I understand correctly that kubuntu 14.04 and newer or 3.16 seem to have a fix for this issue? Would love to switch again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1272777 Title: Elantech touchpads not fully supported for some Gigabyte laptops Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Fix Released Bug description: This bug report is in addition to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166442 - the fixes suggested there (which work for others) have been tried but do not work for a small subset of laptops, particularly the Gigabyte U2442 series. Description of the situation for my Gigabyte U2442V most recently running 3.11.0-12-generic on Linux Mint. I tried the updated module mentioned in the above bug report (1166442). It compiles and it detects an Elantech trackpad of *indeterminate version*. I get this in dmesg: [859697.496141] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x450f01) [859697.526011] psmouse serio1: elantech: Synaptics capabilities query result 0x58, 0x17, 0x0c. [859697.765917] psmouse serio1: elantech: retrying ps2 command 0x0b (2). [859698.470556] psmouse serio1: elantech: retrying ps2 command 0x0b (1). I get no Synaptics driver functionality, and only basic touchpad behaviour (motion and tap-to-click for left click, no scroll or disabling the pad when typing, etc.). It seems I don't have a v9 or v10 trackpad, I've never been able to get a definitive indication of which version I have got. The only thing that has remedied this problem for me in the past was the one described in the original bug report (for elantech-v6 - https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/681904/comments/64)... but it no longer applies to newer kernels... With the 3.11.0-12-generic kernel, my Touchpad *is* detected, i.e. xinput shows: ↳ PS/2 Elantech Touchpad id=16 [slave pointer (2)] and dmesg shows: input: PS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input14 There are no useful touchpads settings evident in the normal Cinnamon settings utility (gnome-control-center - Mouse Touchpads). I see a touchpad settings option with the gpointing-device-settings app and I can turn on vertical and horizontal scrolling in the interface, but doing so does not in any way affect that actual touchpad behaviour. I've also tried installing the elantech-v7 module via dkms (see http://ubuntuforums.org/showthread.php?t=2111236p=12850603#post12850603) and it compiles, but it too fails to provide the desired functionality. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=29b0358f-f728-4aea-bce5-e233816f27b1 InstallationDate: Installed on 2013-12-11 (46 days ago) InstallationMedia: Linux Mint 16 petra - Release amd64 20131126 MachineType: GIGABYTE U2442 MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=83fd94b8-53eb-4e68-9eeb-cf2e017cbe0d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: petra Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/26/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U2442.F306 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U2442 dmi.board.vendor: GIGABYTE dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU2442.F306:bd10/26/2012:svnGIGABYTE:pnU2442:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnU2442:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: U2442 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1272777/+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 1308264] Re: Ubuntu 14.04 Beta 2 stuck at Switched to clocksource tsc when booting up, then resumes booting to the login screen, after 1 minute
I just wanted to confirm that Tim's workaround/fix of changing the boot command line in /etc/default/grub works wonderfully! -- 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/1308264 Title: Ubuntu 14.04 Beta 2 stuck at Switched to clocksource tsc when booting up, then resumes booting to the login screen, after 1 minute Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 Beta 2 (Final Beta), it takes remarkebly long to boot up into Ubuntu. Ubuntu gets stuck at Switched to clocksource tsc for a almost 1 minute or longer, then it resumes booting up to the login screen. On Ubuntu 13.10 it only takes about 7 seconds to get to the login screen, while it takes almost more than a minute to get on the login screen on Ubuntu 14.04 Beta 2. I hope this issue could be fixed. I have the Acer C720 (chromebook) that has been enabled to use legacy boot so I can use other OS's. Other Acer C720 users have been faceing the same problem also. Video of Boot https://www.youtube.com/watch?v=PVkFTsEzS80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308264/+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 1280927] Re: Brightness controls do not work on Thinkpad T61
Can also confirm the bug. There seems to be a workaround: Brightness controls do work in terminal mode (Ctrl+Alt+F1) and the change is kept when in GUI mode (Ctrl+Alt+F7). For me, when I use the brightness controls in Gnome, I can see and move the (ThinkPad-) control slide but changes are not affecting the brightness, same with the slider in Gnome settings. -- 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/1280927 Title: Brightness controls do not work on Thinkpad T61 Status in “linux” package in Ubuntu: Confirmed Bug description: I have the nvidia graphics drivers installed on my laptop and the brightess control doesn't work. I will give more info if asked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-8-generic 3.13.0-8.28 [modified: boot/vmlinuz-3.13.0-8-generic] ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jack 3366 F pulseaudio CurrentDesktop: GNOME Date: Sun Feb 16 20:05:42 2014 HibernationDevice: RESUME=UUID=dca68f85-f13a-46ac-a6f1-464953ec1f41 InstallationDate: Installed on 2014-02-16 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140216) MachineType: LENOVO 7663Y1C PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=8c5abef2-b566-4be2-a234-648e209ce22c ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-8-generic N/A linux-backports-modules-3.13.0-8-generic N/A linux-firmware1.124 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 7663Y1C dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn7663Y1C:pvrThinkPadT61:rvnLENOVO:rn7663Y1C:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7663Y1C dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1280927/+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 1284649] Re: bluetooth devices no longer connect to the system
Before the update i had to run bluez-simple-agent to get bluetooth working. Now it just does not find the device. I tested bluetooth with a usb bluetooth dongle, and bluetooth transfers work, given that bluez- simple-agent command is running. I can even discover the native bluetooth adapter through the usb bluetooth dongle. The following dump is made by 'enabling' bluetooth in the unity-control- center. This only lasts a limited time, before the hcidump utility crashes due to the 'Can't open device: No such device' message. ** Attachment added: hci.log https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284649/+attachment/4021852/+files/hci.log -- 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/1284649 Title: bluetooth devices no longer connect to the system Status in “bluez” package in Ubuntu: Confirmed Bug description: Up until some recent trusty update (maybe a week or two ago), bluetooth worked fine, but after the update none of my bluetooth devices connect to the system, nor can I add new ones. The devices I use are an LG HBS-700 headset, an Apple Keyboard and Trackpad. I plugged in an Asus atheros based bluetooth dongle to see if it was the Broadcom driver no longer working, but I have been unable to get that to work either and it has also worked successfully in Ubuntu before. I ran the bluez-hcidump command that was suggested, but it complains about no device being found. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 25 08:47:13 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-14 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro11,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-12-generic.efi.signed root=UUID=aa52ad82-1d45-4456-972d-493b1dab370e ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B03.1310291227 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B03.1310291227:bd10/29/2013:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci1:Type: BR/EDR Bus: USB BD Address: 60:03:08:9A:5C:D1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:558 acl:0 sco:0 events:28 errors:0 TX bytes:355 acl:0 sco:0 commands:28 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284649/+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 1284649] Re: bluetooth devices no longer connect to the system
After the latest update, bluetooth is working without a problem. No workaround is required. However, bluetooth breaks after suspend resume. Following is a hcidump of a suspend resume action. -- 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/1284649 Title: bluetooth devices no longer connect to the system Status in “bluez” package in Ubuntu: Confirmed Bug description: Up until some recent trusty update (maybe a week or two ago), bluetooth worked fine, but after the update none of my bluetooth devices connect to the system, nor can I add new ones. The devices I use are an LG HBS-700 headset, an Apple Keyboard and Trackpad. I plugged in an Asus atheros based bluetooth dongle to see if it was the Broadcom driver no longer working, but I have been unable to get that to work either and it has also worked successfully in Ubuntu before. I ran the bluez-hcidump command that was suggested, but it complains about no device being found. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 25 08:47:13 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-14 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro11,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-12-generic.efi.signed root=UUID=aa52ad82-1d45-4456-972d-493b1dab370e ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B03.1310291227 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B03.1310291227:bd10/29/2013:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci1:Type: BR/EDR Bus: USB BD Address: 60:03:08:9A:5C:D1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:558 acl:0 sco:0 events:28 errors:0 TX bytes:355 acl:0 sco:0 commands:28 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284649/+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 1284649] Re: bluetooth devices no longer connect to the system
After the latest update, bluetooth is working without a problem. No workaround is required. However, bluetooth breaks after suspend resume. Following is a hcidump of a suspend resume action. ** Attachment added: hci.log https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284649/+attachment/4022179/+files/hci.log -- 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/1284649 Title: bluetooth devices no longer connect to the system Status in “bluez” package in Ubuntu: Confirmed Bug description: Up until some recent trusty update (maybe a week or two ago), bluetooth worked fine, but after the update none of my bluetooth devices connect to the system, nor can I add new ones. The devices I use are an LG HBS-700 headset, an Apple Keyboard and Trackpad. I plugged in an Asus atheros based bluetooth dongle to see if it was the Broadcom driver no longer working, but I have been unable to get that to work either and it has also worked successfully in Ubuntu before. I ran the bluez-hcidump command that was suggested, but it complains about no device being found. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 25 08:47:13 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-14 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro11,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-12-generic.efi.signed root=UUID=aa52ad82-1d45-4456-972d-493b1dab370e ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B03.1310291227 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B03.1310291227:bd10/29/2013:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci1:Type: BR/EDR Bus: USB BD Address: 60:03:08:9A:5C:D1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:558 acl:0 sco:0 events:28 errors:0 TX bytes:355 acl:0 sco:0 commands:28 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284649/+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 515090] Re: Amilo Xi 3650: WLAN/BT hotkey doesn't work
Wow, I completely forgot about this bug report. As I found out in the meantime, this problem only occurs if you use both Windows and Linux. On Windows, whenever the switch button is pressed, a popup appears which prompts you to select the devices you want to turn on/off. When you do, the driver seems to do something linux doesn't understand, as whenever you actually switch one of the devices on or off on Windows, you lose the ability to use the switch on Linux until you reset the BIOS settings. Since I'm not using Windows anymore on that particular laptop, I cannot check whether the problem still exists. I suspect it does. However, since I'm not affected anymore, feel free to close this bug due to a lack of interest, if you want. ;-) -- 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/515090 Title: Amilo Xi 3650: WLAN/BT hotkey doesn't work Status in “linux” package in Ubuntu: Incomplete Bug description: Since I bought an AMILO Xi 3650 laptop some months ago, I always had to boot Vista to be able to turn WLAN and Bluetooth on and off via Fn+F1 (there's only one key for both, on Windows a window appears asking me which of them I want to be enabled). In December I upgraded to lucid and at the beginning of January I suddenly noticed that the hotkey was working, turning both WLAN and BT on and off whenever I pressed it. Today I had to find out that it doesn't work anymore again (since I don't need BT most of the time, it could've already been broken for some days). ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moritz 2278 F kmix moritz 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf462 irq 22' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,17341148,00100202' Controls : 26 Simple ctrls : 15 Date: Sun Jan 31 12:16:25 2010 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=74fe59fe-05ba-45ce-a817-6c33f6ebd1c8 MachineType: FUJITSU SIEMENS AMILO Xi 3650 Package: linux-image-2.6.32-12-generic 2.6.32-12.16 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-12-generic root=UUID=29e82293-368a-49f9-8c7c-11c09e185381 ro quiet splash ProcEnviron: LANGUAGE=de_DE:de:en_GB:en LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-12.16-generic Regression: Yes RelatedPackageVersions: linux-firmware 1.28 Reproducible: Yes RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux TestedUpstream: No Uname: Linux 2.6.32-12-generic i686 dmi.bios.date: 04/07/2009 dmi.bios.vendor: Phoenix dmi.bios.version: 1.0G-1646-0024 dmi.board.name: XY680 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 0.3B dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnPhoenix:bvr1.0G-1646-0024:bd04/07/2009:svnFUJITSUSIEMENS:pnAMILOXi3650:pvr10600978653:rvnFUJITSUSIEMENS:rnXY680:rvr0.3B:cvnFUJITSUSIEMENS:ct10:cvrVersion1.0: dmi.product.name: AMILO Xi 3650 dmi.product.version: 10600978653 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/515090/+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
