[Kernel-packages] [Bug 1717657] Re: Boot hangs when loading initial ramdisk
Actually a later version of UEFI solved the problem again - I am currently running 2.37 and kernel boots properly with secure boot disabled. However, even after intense web research I didn't find a way to update the UEFI without Windows. So in case you have no Windows any more you have to download a Windows trial image and create a Windows start DVD just for UEFI/BIOS updates. -- 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/1717657 Title: Boot hangs when loading initial ramdisk Status in linux package in Ubuntu: Invalid Bug description: Kernel 4.13.2 fails to boot. It stops after Grub printing "Loading initital ramdisk". The last successful kernel which booted was Linux ebola 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I edited Grub command line, removed "quiet splash" and added "earlyprintk=efi" but I see no diagnostic information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1717657/+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 1717657] Re: Boot hangs when loading initial ramdisk
Behavior was caused by buggy Lenovo UEFI Version 2.2 which attempted to verify the Kernel signature even though Secure Boot was disabled. Closing. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1717657 Title: Boot hangs when loading initial ramdisk Status in linux package in Ubuntu: Invalid Bug description: Kernel 4.13.2 fails to boot. It stops after Grub printing "Loading initital ramdisk". The last successful kernel which booted was Linux ebola 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I edited Grub command line, removed "quiet splash" and added "earlyprintk=efi" but I see no diagnostic information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1717657/+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 1717657] [NEW] Boot hangs when loading initial ramdisk
Public bug reported: Kernel 4.13.2 fails to boot. It stops after Grub printing "Loading initital ramdisk". The last successful kernel which booted was Linux ebola 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I edited Grub command line, removed "quiet splash" and added "earlyprintk=efi" but I see no diagnostic information. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: kernel-bug zesty ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1717657/+attachment/4951119/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1717657 Title: Boot hangs when loading initial ramdisk Status in linux package in Ubuntu: Confirmed Bug description: Kernel 4.13.2 fails to boot. It stops after Grub printing "Loading initital ramdisk". The last successful kernel which booted was Linux ebola 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I edited Grub command line, removed "quiet splash" and added "earlyprintk=efi" but I see no diagnostic information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1717657/+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 1717657] Re: Boot hangs when loading initial ramdisk
** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1717657/+attachment/4951120/+files/lspci-vvnn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1717657 Title: Boot hangs when loading initial ramdisk Status in linux package in Ubuntu: Confirmed Bug description: Kernel 4.13.2 fails to boot. It stops after Grub printing "Loading initital ramdisk". The last successful kernel which booted was Linux ebola 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I edited Grub command line, removed "quiet splash" and added "earlyprintk=efi" but I see no diagnostic information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1717657/+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 1162781] Re: bluez package out of date, 5.3 is available
upgrading bluez to bluez5 will be the end for bluetooth hands free support HFP. Many people use that, Skype with bluetooth device anybody? Please don't upgrade unless HFP support is restored. https://bugs.freedesktop.org/show_bug.cgi?id=73325#c7 ** Bug watch added: freedesktop.org Bugzilla #73325 https://bugs.freedesktop.org/show_bug.cgi?id=73325 -- 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/1162781 Title: bluez package out of date, 5.3 is available Status in “bluez” package in Ubuntu: Triaged Bug description: Looks like there have been a lot of improvements to bluez since the 4.x series. Would be nice to get the latest release pulled in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1162781/+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 389494] Re: No HDMI Sound with Jaunty 9.04, Kernel 2.6.30, ALSA 1.0.20, Conexant CX20561 nvidia MCP65 HD Audio (Geforce 8400M GS)
Ok, it's 2013, I have that driver and no sound via HDMI. Wow, that is frustrating! -- 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/389494 Title: No HDMI Sound with Jaunty 9.04, Kernel 2.6.30, ALSA 1.0.20, Conexant CX20561 nvidia MCP65 HD Audio (Geforce 8400M GS) Status in “alsa-driver” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “alsa-driver” package in Arch Linux: New Bug description: I did a fresh install of jaunty on my HP DV9812EG Notebook, but HDMI Audio out isn't working. In the beginning i had ALSA Version 1.0.18 installed, which came with Ubuntu 9.04. Even tough the lastest proprietary geforce driver (NVIDIA-Linux-x86_64-185.18.14-pkg2.run) seems to work properly, there was no HDMI sound. Thus, I updated to the lastest Kernel 2.6.30 (official release, no RC) and ALSA 1.0.20, but it didn't change anything. The HDMI device can't be recognized even tough it should be there. ALSA 1.0.20 was configured with the following command: ./configure --with-cards=all --with-card-options=all --with- sequencer=yes make Under Windows Vista Everest finds the following soundcard and HD Audio Modem: Conexant Cx20561 @ nVIDIA MCP65 - High Definition Audio Controller Modem HDAUDIO Soft Data Fax Modem with SmartCP hwinfo --short under ubuntu 9.04 confirms this, but aplay -l list only these two audio devices (it should be three at least): rennie@Riese:~$ aplay -l Liste von PLAYBACK Geräten Karte 0: NVidia [HDA NVidia], Gerät 0: CONEXANT Analog [CONEXANT Analog] Untergeordnete Geräte: 1/1 Untergeordnetes Gerät '0: subdevice #0 Karte 0: NVidia [HDA NVidia], Gerät 1: Conexant Digital [Conexant Digital] Untergeordnete Geräte: 1/1 Untergeordnetes Gerät '0: subdevice #0 rennie@Riese:~$ So what's missing is something like this: Karte 0: NVidia [HDA NVidia], Gerät 3: NVIDIA HDMI [NVIDIA HDMI] Untergeordnete Geräte: 1/1 Untergeordnetes Gerät '0: subdevice #0 aplay -L shows this result: rennie@Riese:~$ aplay -L default:CARD=NVidia HDA NVidia, CONEXANT Analog Default Audio Device front:CARD=NVidia,DEV=0 HDA NVidia, CONEXANT Analog Front speakers surround40:CARD=NVidia,DEV=0 HDA NVidia, CONEXANT Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=NVidia,DEV=0 HDA NVidia, CONEXANT Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=NVidia,DEV=0 HDA NVidia, CONEXANT Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=NVidia,DEV=0 HDA NVidia, CONEXANT Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=NVidia,DEV=0 HDA NVidia, CONEXANT Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=NVidia,DEV=0 HDA NVidia, Conexant Digital IEC958 (S/PDIF) Digital Audio Output null Discard all samples (playback) or generate zero samples (capture) rennie@Riese:~$ So again there is missing something like: hdmi:CARD=NVidia,DEV=0 HDA NVidia, NVIDIA HDMI HDMI Audio Output I even tried to go back to ALSA 1.0.19 but it is not possible to ./configure the original alsa-driver package (there was an error, but i don't remember which). As an alternative i tried to install the linuxant deb-version of ALSA (alsa-driver-linuxant_1.0.20.3_all.deb) and the realtek version (realtek-linux-audiopack-5.11) but both versions didn't work. So this must be a bug, because everything else works fine (e.g. HDMI Video out, Laptop Speakers, Ear-Plug-Audio out...) Unfortunately, to find and eliminate the bug, I can contribute only with some other information: Result of lspci | grep -i audio!: --- rennie@Riese:~$ lspci | grep -i audio 00:07.0 Audio device: nVidia Corporation MCP65 High Definition Audio (rev a1) ...and the result of cat /proc/asound/cards rennie@Riese:~$ cat /proc/asound/cards 0 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf248 irq 21 rennie@Riese:~$ Result of alsactl init NVidia: rennie@Riese:~$ alsactl init NVidia Unknown hardware: HDA-Intel Conexant CX20561 (Hermosa) HDA:14f15051,103c30cf,0010 0x103c 0x30cf Hardware is initialized using a guess method /usr/share/alsa/init/default:51: control element not found /usr/share/alsa/init/default:52: missing closing brace for format /usr/share/alsa/init/default:52: error parsing CTL attribute /usr/share/alsa/init/default:52: invalid rule rennie@Riese:~$ To manage notifications about this bug go to:
