[Kernel-packages] [Bug 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
xubuntu and kubuntu, as lubuntu do use pipewire for audio. kali switched last night to use it. openSUSE did so too. i did not test on a plain vanilla gnome based ubuntu until now. Will do it later this day (if time permits). -- 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/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
These modules seem to collide with pipewire-media-session, but are required by bluez-stack to connect bluetooth headsets (or other devices) to pulseaudio. -- 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/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
Meanwhile even the distros working until yesterday stopped working today (5. May 2022 around 22:00). The bug seems related to pipewire and switching to this new infrastructure. It breaks nearly everything related with sound and bluetooth. Modules involved: - pipewire-pulse - wireplumber -- 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/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1971534] [NEW] connecting bluetooth devices fails
Public bug reported: Bluetooth devices do not connect. Or better: they connect, disconnect, connect, then finally disconnect. It is the same using graphical tools or cli. It is the same for - ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta) - debian 11.3 - fedora 35 Working distros are: - kali (latest rolling) - openSUSE Leap 15.4 - openSUSE tumbleweed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed May 4 08:57:30 2022 InstallationDate: Installed on 2021-08-18 (258 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-27-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:4581 acl:7 sco:0 events:435 errors:0 TX bytes:46460 acl:7 sco:0 commands:399 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1971534 Title: connecting bluetooth devices fails Status in bluez package in Ubuntu: New Bug description: Bluetooth devices do not connect. Or better: they connect, disconnect, connect, then finally disconnect. It is the same using graphical tools or cli. It is the same for - ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta) - debian 11.3 - fedora 35 Working distros are: - kali (latest rolling) - openSUSE Leap 15.4 - openSUSE tumbleweed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed May 4 08:57:30 2022 InstallationDate: Installed on 2021-08-18 (258 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-27-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:4581 acl:7 sco:0 events:435 errors:0 TX bytes:46460 acl:7 sco:0 commands:399 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1971534/+subs
[Kernel-packages] [Bug 1970202] [NEW] linux-generic kernels are missing nbd modules
Public bug reported: linux-generic kernels are missing nbd modules. Since these modules are not build and not found in linux-generic-extra or other packages it is not possible to - use nbd-devices - it is not possible to mount *.qcow2 qemu virtual harddrives into your host system You can build these nbd modules yourself, but you need to compile the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-generic 5.13.0.41.50 ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps7192 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Apr 25 13:43:48 2022 HibernationDevice: RESUME=/dev/vg/swap_1 InstallationDate: Installed on 2011-10-19 (3840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 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.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2019-04-27 (1093 days ago) dmi.bios.date: 10/21/2013 dmi.bios.release: 2.15 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish package-from-proposed -- 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/1970202 Title: linux-generic kernels are missing nbd modules Status in linux package in Ubuntu: Confirmed Bug description: linux-generic kernels are missing nbd modules. Since these modules are not build and not found in linux-generic-extra or other packages it is not possible to - use nbd-devices - it is not possible to mount *.qcow2 qemu virtual harddrives into your host system You can build these nbd modules yourself, but you need to compile the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-generic 5.13.0.41.50 ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps7192 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Apr 25 13:43:48 2022 HibernationDevice: RESUME=/dev/vg/swap_1 InstallationDate: Installed on 2011-10-19 (3840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 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.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2019-04-27 (1093 days ago) dmi.bios.date: 10/21/2013 dmi.bios.release: 2.15 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15: dmi.product.family: TravelMate
[Kernel-packages] [Bug 1968875] [NEW] Bluetooth devices disconnect, connect, disconnect
Public bug reported: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1968875 Title: Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: New Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1961849] Re: bluetooth connects with headset, deconects, connects, deconnects
Start-Date: 2022-02-21 01:16:18 Commandline: apt -y upgrade Requested-By: tps (1000) Upgrade: firefox-locale-en:amd64 (97.0+build2-0ubuntu1, 97.0.1+build1-0ubuntu1), dmeventd:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), udev:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libctf-nobfd0:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), systemd-container:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libqmi-proxy:amd64 (1.30.2-1, 1.30.4-1), gir1.2-snapd-1:amd64 (1.58-4ubuntu1, 1.60-0ubuntu1), systemd-timesyncd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libpam-systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libarchive13:amd64 (3.5.2-1, 3.5.2-1ubuntu1), openmpi-bin:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), libbinutils:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libfwupd2:amd64 (1.7.4-1ubuntu1, 1.7.5-3), libsnapd-glib1:amd64 (1.58-4ubuntu1, 1.60-0ubuntu1), openmpi-common:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), liblvm2cmd2.03:amd64 (2.03.11-2.1ubuntu3, 2.03.11-2.1ubuntu4), libsystemd0:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libsystemd0:i386 (249.9-0ubuntu2, 249.10-0ubuntu1), binutils-x86-64-linux-gnu:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libnss-systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libudev1:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libudev1:i386 (249.9-0ubuntu2, 249.10-0ubuntu1), lvm2:amd64 (2.03.11-2.1ubuntu3, 2.03.11-2.1ubuntu4), libnss-mymachines:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libctf0:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), dmsetup:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), python3-pil.imagetk:amd64 (9.0.0-1, 9.0.1-1), libhypre-2.22.1:amd64 (2.22.1-6, 2.22.1-7), libdevmapper-event1.02.1:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), binutils-common:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libqmi-glib5:amd64 (1.30.2-1, 1.30.4-1), python3-pil:amd64 (9.0.0-1, 9.0.1-1), libopenmpi3:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), systemd-sysv:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libfwupdplugin5:amd64 (1.7.4-1ubuntu1, 1.7.5-3), libdevmapper1.02.1:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), binutils:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), fwupd:amd64 (1.7.4-1ubuntu1, 1.7.5-3) End-Date: 2022-02-21 01:18:20 Start-Date: 2022-02-21 01:18:24 Commandline: apt -y dist-upgrade Requested-By: tps (1000) Install: libnfsidmap1:amd64 (1:2.6.1-1~exp1ubuntu1, automatic) Upgrade: nfs-common:amd64 (1:1.3.4-6ubuntu1, 1:2.6.1-1~exp1ubuntu1) Remove: libnfsidmap2:amd64 (0.25-6build1) End-Date: 2022-02-21 01:18:28 Start-Date: 2022-02-22 07:07:20 Commandline: apt -y upgrade Requested-By: tps (1000) Install: polkitd:amd64 (0.105-32, automatic), pkexec:amd64 (0.105-32, automatic) Upgrade: libpolkit-agent-1-0:amd64 (0.105-31.1, 0.105-32), libsmartcols1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), debconf-i18n:amd64 (1.5.79, 1.5.79ubuntu1), apt:amd64 (2.3.15, 2.3.15build1), packagekit-tools:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), libxcb-image0:amd64 (0.4.0-1build2, 0.4.0-2), zfs-zed:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), libpipewire-0.3-common:amd64 (0.3.45-1, 0.3.47-1ubuntu1), zfs-initramfs:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), libaom3:amd64 (3.2.0-2, 3.3.0-1), libjpeg-turbo8:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libjpeg-turbo8:i386 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libnvpair3linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), grub-pc-bin:amd64 (2.06-2ubuntu4, 2.06-2ubuntu5), libapt-pkg6.0:amd64 (2.3.15, 2.3.15build1), libuutil3linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), debconf:amd64 (1.5.79, 1.5.79ubuntu1), libmount1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libmount1:i386 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libzpool5linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), system-config-printer-udev:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), pipewire:amd64 (0.3.45-1, 0.3.47-1ubuntu1), libqpdf28:amd64 (10.5.0-1, 10.6.2-1), gir1.2-packagekitglib-1.0:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), util-linux:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libjpeg-turbo-progs:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), fdisk:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libfdisk1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), system-config-printer-common:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), eject:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), packagekit:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), libturbojpeg:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libuuid1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libuuid1:i386 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), make:amd64 (4.3-4ubuntu2, 4.3-4.1build1), uuid-runtime:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), grub-efi-amd64-signed:amd64 (1.177+2.06-2ubuntu4, 1.178+2.06-2ubuntu5), libjpeg-turbo8-dev:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libpolkit-gobject-1-0:amd64 (0.105-31.1, 0.105-32), gir1.2-polkit-1.0:amd64 (0.105-31.1, 0.105-32), libpackagekit-glib2-18:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), pipewire-bin:amd64 (0.3.45-1, 0.3.47-1ubuntu1), system-config-printer:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), grub-efi-amd64-bin:a
[Kernel-packages] [Bug 1961849] [NEW] bluetooth connects with headset, deconects, connects, deconnects
Public bug reported: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1961849 Title: bluetooth connects with headset, deconects, connects, deconnects Status in bluez package in Ubuntu: New Bug description: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 To manage notifications about this
[Kernel-packages] [Bug 1956542] [NEW] usb devices connected via usb 3.*-Hub are not detected
Public bug reported: usb devices connected via an usb 3.x-hub are not detected. [53443.604120] usb 4-4.2: new SuperSpeed USB device number 6 using xhci_hcd [53443.707572] usb 4-4.2: New USB device found, idVendor=2109, idProduct=0813, bcdDevice=90.11 [53443.707583] usb 4-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [53443.707587] usb 4-4.2: Product: USB3.0 Hub [53443.707589] usb 4-4.2: Manufacturer: VIA Labs, Inc. [53443.709682] hub 4-4.2:1.0: USB hub found [53443.709913] hub 4-4.2:1.0: 4 ports detected [53443.795224] usb 4-4.3: new SuperSpeed USB device number 7 using xhci_hcd [53443.829875] usb 4-4.3: New USB device found, idVendor=0557, idProduct=2410, bcdDevice= 1.19 [53443.829885] usb 4-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [53443.829890] usb 4-4.3: Product: 4-Port USB 3.0 Hub [53443.829893] usb 4-4.3: Manufacturer: Generic [53443.840170] hub 4-4.3:1.0: USB hub found [53443.841600] hub 4-4.3:1.0: 4 ports detected [53444.147800] usb 4-4.2.4: new SuperSpeed USB device number 8 using xhci_hcd [53444.251729] usb 4-4.2.4: New USB device found, idVendor=2109, idProduct=0813, bcdDevice=90.11 [53444.251736] usb 4-4.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [53444.251739] usb 4-4.2.4: Product: USB3.0 Hub [53444.251742] usb 4-4.2.4: Manufacturer: VIA Labs, Inc. [53444.257750] hub 4-4.2.4:1.0: USB hub found [53444.257909] hub 4-4.2.4:1.0: 4 ports detected [53444.330559] usb 4-4.3.2: new SuperSpeed USB device number 9 using xhci_hcd [53444.350917] usb 4-4.3.2: New USB device found, idVendor=0451, idProduct=8140, bcdDevice= 1.00 [53444.350926] usb 4-4.3.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [53444.353872] hub 4-4.3.2:1.0: USB hub found [53444.354204] hub 4-4.3.2:1.0: 4 ports detected [53444.647364] usb 4-4.2.4.2: new SuperSpeed USB device number 10 using xhci_hcd [53444.765499] usb 4-4.2.4.2: New USB device found, idVendor=0bda, idProduct=0301, bcdDevice= 1.30 [53444.765507] usb 4-4.2.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [53444.765510] usb 4-4.2.4.2: Product: USB3.0 Card Reader [53444.765512] usb 4-4.2.4.2: Manufacturer: Realtek [53444.765514] usb 4-4.2.4.2: SerialNumber: 201210233001 [53444.777193] usb-storage 4-4.2.4.2:1.0: USB Mass Storage device detected [53444.778469] scsi host7: usb-storage 4-4.2.4.2:1.0 [53444.903836] usb 4-4.2.4.4: new SuperSpeed USB device number 11 using xhci_hcd [53445.010197] usb 4-4.2.4.4: New USB device found, idVendor=2109, idProduct=0813, bcdDevice=90.11 [53445.010203] usb 4-4.2.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [53445.010205] usb 4-4.2.4.4: Product: USB3.0 Hub [53445.010207] usb 4-4.2.4.4: Manufacturer: VIA Labs, Inc. [53445.014033] hub 4-4.2.4.4:1.0: USB hub found [53445.015233] hub 4-4.2.4.4:1.0: 4 ports detected [53445.447869] usb 4-4.2.4.4.4: new SuperSpeed USB device number 12 using xhci_hcd [53445.555240] usb 4-4.2.4.4.4: New USB device found, idVendor=2109, idProduct=0813, bcdDevice=90.11 [53445.555248] usb 4-4.2.4.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [53445.555251] usb 4-4.2.4.4.4: Product: USB3.0 Hub [53445.555254] usb 4-4.2.4.4.4: Manufacturer: VIA Labs, Inc. [53445.557571] hub 4-4.2.4.4.4:1.0: USB hub found [53445.557780] hub 4-4.2.4.4.4:1.0: 4 ports detected Connecting various devices to this 13-port-hub does not lead to device detection. The devices connected are just ignored. Some devices are detected, but it might take some time (up to two minutes until they are): Jan 6 02:11:37 ivory bluetoothd[8177]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc Jan 6 02:11:37 ivory bluetoothd[8177]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc Jan 6 02:11:37 ivory bluetoothd[8177]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Jan 6 02:11:37 ivory bluetoothd[8177]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Jan 6 02:11:37 ivory bluetoothd[8177]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Jan 6 02:11:37 ivory bluetoothd[8177]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Jan 6 02:11:37 ivory bluetoothd[8177]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Jan 6 02:11:37 ivory bluetoothd[8177]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Jan 6 02:11:37 ivory systemd[1]: Starting Load/Save RF Kill Switch Status... Jan 6 02:11:37 ivory kernel: [53825.716387] usb 3-4.2.4.4.1: new full-speed USB device number 61 using xhci_hcd Jan 6 02:11:37 ivory kernel: [53825.850501] usb 3-4.2.4.4.1: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 Jan 6 02:11:37 ivory kernel: [53825.850513] usb 3-4.2.4.4.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 Jan 6 02:11:37 ivory kernel: [53825.850517] usb 3-4.2.4.4.1: Product: CSR8510
[Kernel-packages] [Bug 1943670] [NEW] kernel stops responding to some usb storage devices
Public bug reported: latest ubuntu-kernels stop responding to usb storage devices all using xhci_hcd: - Prolific Technology, Inc. PL2773 SATAII bridge controller maybe others too. Symptom: devices are shown in thunar, nautilus. They show up in /dev as /dev/sdXN, but clicking them in thunar or nautilus only gives the message "Pending operation". "mount" will never finish. Trying to access these devices directly using kernel functions, the called function never comes back. A system shutdown will never finish. I've tried some more recent kernels on a non-zfs system with same results: - linux-5.15.0-rc1-x86_64 - linux-5.14.3-x86_64 - linux-5.13.16-x86_64 - linux-5.10.64-x86_64 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-generic 5.11.0.34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps1991 F pulseaudio CasperMD5CheckResult: pass Date: Wed Sep 15 05:26:30 2021 InstallationDate: Installed on 2021-09-14 (0 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20FAS16K00 ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_eo9ngl@/vmlinuz-5.11.0-34-generic root=ZFS=rpool/ROOT/ubuntu_eo9ngl ro quiet splash vt.handoff=1 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.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943670 Title: kernel stops responding to some usb storage devices Status in linux package in Ubuntu: Confirmed Bug description: latest ubuntu-kernels stop responding to usb storage devices all using xhci_hcd: - Prolific Technology, Inc. PL2773 SATAII bridge controller maybe others too. Symptom: devices are shown in thunar, nautilus. They show up in /dev as /dev/sdXN, but clicking them in thunar or nautilus only gives the message "Pending operation". "mount" will never finish. Trying to access these devices directly using kernel functions, the called function never comes back. A system shutdown will never finish. I've tried some more recent kernels on a non-zfs system with same results: - linux-5.15.0-rc1-x86_64 - linux-5.14.3-x86_64 - linux-5.13.16-x86_64 - linux-5.10.64-x86_64 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-generic 5.11.0.34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps1991 F pulseaudio CasperMD5CheckResult: pass Date: Wed Sep 15 05:26:30 2021 InstallationDate: Installed on 2021-09-14 (0 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20FAS16K00 ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_eo9ngl@/vmlinuz-5.11.0-34-generic root=ZFS=rpool/ROOT/ubuntu_eo9ngl ro quiet splash vt.handoff=1 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.11.0-34-gene
[Kernel-packages] [Bug 1900362] [NEW] Kernel turns off USB-devices
Public bug reported: Kernel turns off USB-devices. A mouse connected to an usb-port works until some time. Then this device is turned off and never turned on again. I tried to turn off power saving for such devices, but without success. This started with kernels 5.4.0-49-generic and later. I do not see this with kernel 5.4.0-48-generic. This bug renders all usb-ports used unusable. You can unplug the device (a mouse or keyboard) to an unused usb-port. But this will be switched off then soon too. At some point in future you are out of working ports, because all of them are switched off and never on again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps6019 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 00:49:09 2020 HibernationDevice: RESUME=/dev/vg/swap_1 InstallationDate: Installed on 2011-10-19 (3287 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 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-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-04-27 (540 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed -- 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/1900362 Title: Kernel turns off USB-devices Status in linux package in Ubuntu: New Bug description: Kernel turns off USB-devices. A mouse connected to an usb-port works until some time. Then this device is turned off and never turned on again. I tried to turn off power saving for such devices, but without success. This started with kernels 5.4.0-49-generic and later. I do not see this with kernel 5.4.0-48-generic. This bug renders all usb-ports used unusable. You can unplug the device (a mouse or keyboard) to an unused usb-port. But this will be switched off then soon too. At some point in future you are out of working ports, because all of them are switched off and never on again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps6019 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 00:49:09 2020 HibernationDevice: RESUME=/dev/vg/swap_1 InstallationDate: Installed on 2011-10-19 (3287 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 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-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-04-27 (540 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.ch
[Kernel-packages] [Bug 1893831] [NEW] linux-image-unsigned-5.4.0-46-generic wont initialize console
Public bug reported: linux-image-unsigned-5.4.0-46-generic wont initialize console as expected. No monitor is used or found. No graphics, no text console. Only a blank black screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-unsigned-5.4.0-46-generic 5.4.0-46.50 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps6668 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 1 21:20:15 2020 HibernationDevice: RESUME=/dev/vg/swap_1 InstallationDate: Installed on 2011-10-19 (3240 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-04-27 (493 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal package-from-proposed -- 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/1893831 Title: linux-image-unsigned-5.4.0-46-generic wont initialize console Status in linux package in Ubuntu: Confirmed Bug description: linux-image-unsigned-5.4.0-46-generic wont initialize console as expected. No monitor is used or found. No graphics, no text console. Only a blank black screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-unsigned-5.4.0-46-generic 5.4.0-46.50 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps6668 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 1 21:20:15 2020 HibernationDevice: RESUME=/dev/vg/swap_1 InstallationDate: Installed on 2011-10-19 (3240 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-04-27 (493 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893831/+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 1802796] Re: Trouble mounting USB-Devices
With kernel 4.18.0 it takes very long (up to minutes) to mount the device from commandline. With kernel 4.4.0 it is done within a second. -- 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/1802796 Title: Trouble mounting USB-Devices Status in linux package in Ubuntu: Confirmed Bug description: kernel 4.18.0-11 -> does not work with Thunnar From Thunnar the device is not mounted. Only error message: "An operation is outstanding" oder "An operation is in progress". The device will never mount. kernel 4.4.0-xxx -> works with Thunnar From Thunnar the device is immediately mounted and accessible. No problems. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps 24718 F pulseaudio Date: Sun Nov 11 20:40:15 2018 HibernationDevice: RESUME=UUID=8d0c54be-1645-4764-abd6-905d8e95659a InstallationDate: Installed on 2011-10-19 (2580 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-11-03 (8 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802796/+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 1802796] [NEW] Trouble mounting USB-Devices
Public bug reported: kernel 4.18.0-11 -> does not work with Thunnar >From Thunnar the device is not mounted. Only error message: "An operation is outstanding" oder "An operation is in progress". The device will never mount. kernel 4.4.0-xxx -> works with Thunnar >From Thunnar the device is immediately mounted and accessible. No problems. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps 24718 F pulseaudio Date: Sun Nov 11 20:40:15 2018 HibernationDevice: RESUME=UUID=8d0c54be-1645-4764-abd6-905d8e95659a InstallationDate: Installed on 2011-10-19 (2580 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-11-03 (8 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug cosmic package-from-proposed -- 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/1802796 Title: Trouble mounting USB-Devices Status in linux package in Ubuntu: Confirmed Bug description: kernel 4.18.0-11 -> does not work with Thunnar From Thunnar the device is not mounted. Only error message: "An operation is outstanding" oder "An operation is in progress". The device will never mount. kernel 4.4.0-xxx -> works with Thunnar From Thunnar the device is immediately mounted and accessible. No problems. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps 24718 F pulseaudio Date: Sun Nov 11 20:40:15 2018 HibernationDevice: RESUME=UUID=8d0c54be-1645-4764-abd6-905d8e95659a InstallationDate: Installed on 2011-10-19 (2580 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-11-03 (8 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.versio
[Kernel-packages] [Bug 1795873] [NEW] endless loop initializing video
Public bug reported: With kernel linux-image-4.15.0-36-generic the system continuously tries ti initialize video. The screen backlight blinks all seconds once, but never starts any display-manager or, if booting in text mode, show any text. You cant do anything except press the power button to shutdown the system again. With kernel linux-image-4.4.0-137-generic the system tries to initialize video, fails and then goes on with text mode. startx can be given after to start X11. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps9296 F pulseaudio /dev/snd/seq:timidity 7270 F timidity Date: Wed Oct 3 13:44:00 2018 HibernationDevice: RESUME=UUID=8d0c54be-1645-4764-abd6-905d8e95659a InstallationDate: Installed on 2011-10-19 (2540 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-137-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-137-generic N/A linux-backports-modules-4.4.0-137-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-02 (1 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.name: TravelMate P643-M dmi.product.version: V2.15 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1795873 Title: endless loop initializing video Status in linux package in Ubuntu: Confirmed Bug description: With kernel linux-image-4.15.0-36-generic the system continuously tries ti initialize video. The screen backlight blinks all seconds once, but never starts any display-manager or, if booting in text mode, show any text. You cant do anything except press the power button to shutdown the system again. With kernel linux-image-4.4.0-137-generic the system tries to initialize video, fails and then goes on with text mode. startx can be given after to start X11. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps9296 F pulseaudio /dev/snd/seq:timidity 7270 F timidity Date: Wed Oct 3 13:44:00 2018 HibernationDevice: RESUME=UUID=8d0c54be-1645-4764-abd6-905d8e95659a InstallationDate: Installed on 2011-10-19 (2540 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-137-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-137-generic N/A linux-backports-modules-4.4.0-137-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-02 (1 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.produ
[Kernel-packages] [Bug 1690157] [NEW] Error where encountered while processing linux-generic
Public bug reported: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 4 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up linux-image-4.4.0-77-generic (4.4.0-77.98) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-77-generic ) points to /boot/initrd.img-4.4.0-77-generic (/boot/initrd.img-4.4.0-77-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-77-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-77-generic ) points to /boot/vmlinuz-4.4.0-77-generic (/boot/vmlinuz-4.4.0-77-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-77-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-77-generic /boot/vmlinuz-4.4.0-77-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-77-generic /boot/vmlinuz-4.4.0-77-generic update-initramfs: Generating /boot/initrd.img-4.4.0-77-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-77-generic /boot/vmlinuz-4.4.0-77-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-77-generic /boot/vmlinuz-4.4.0-77-generic run-parts: executing /etc/kernel/postinst.d/vboxadd 4.4.0-77-generic /boot/vmlinuz-4.4.0-77-generic run-parts: failed to exec /etc/kernel/postinst.d/vboxadd: Exec format error run-parts: /etc/kernel/postinst.d/vboxadd exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-77-generic.postinst line 1052. dpkg: error processing package linux-image-4.4.0-77-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-extra-4.4.0-77-generic: linux-image-extra-4.4.0-77-generic depends on linux-image-4.4.0-77-generic; however: Package linux-image-4.4.0-77-generic is not configured yet. dpkg: error processing package linux-image-extra-4.4.0-77-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-4.4.0-77-generic; however: Package linux-image-4.4.0-77-generic is not configured yet. linux-image-generic depends on linux-image-extra-4.4.0-77-generic; however: Package linux-image-extra-4.4.0-77-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 4.4.0.77.83); however: Package linux-image-generic is not configured No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because MaxReports is reached already yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-4.4.0-77-generic linux-image-extra-4.4.0-77-generic linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Can't recover by dpkg-reconfigure: # dpkg-reconfigure linux-image-extra-4.4.0-77-generic /usr/sbin/dpkg-reconfigure: linux-image-extra-4.4.0-77-generic is broken or not fully installed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.77.83 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dream 1156 F lxpanel Date: Thu May 11 18:18:30 2017 HibernationDevice: RESUME=UUID=9b16760b-b5b9-4461-aa32-d703664fa4bb InstallationDate: Installed on 2017-02-22 (78 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) IwConfig: ens33 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=/dev/sda2 ro quiet splash RelatedPackageVersions: linux-restricted-modu
[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
Next I've tried to install 16.10 without upgrading from 16.04.1 LTS. Install went fine, but rebooting at the end gave the same result: short time cursor blinking behind 'login:'. Within this time keyboard works. As soon, as the cursor vanishes, keyboard is dead. I've tried other kernel too, but nothing changed. -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
I've tried now: With Ubuntu 16.04.1 LTS: - Plain vanilla kernels 4.1.x, 4.4.x, 4.7.10, 4.8.x - Ubuntu-Kernels: 4.5-rc1, 4.5-final, 4.6-final - fedora mainline kernels (only took kernel-config, compiled kernel myself) Result: keyboard, mouse working as expected with all kernels, except 4.8.6 -- maybe there was a missing configuration option with this kernel. I did not dig into it. With Ubuntu 16.10: - Plain vanilla kernels 4.1.x, 4.4.x, 4.7.10, 4.8.x - Ubuntu-Kernels: 4.5-rc1, 4.5-final, 4.6-final - Fedora mainline kernels (compiled using Ubuntu 16.04.1 LTS) Result: no keyboard, no mouse for all kernels. But to be exact: Boot. Wait for Login prompt. For a short time the cursor is blinking behind "login:". While the cursor is blinking there, you can type! If you are fast, you may even press return, and "Password:" pops up. If you have a short password you may now be able to type this password and log in. In most cases at some point the cursor just vanishes and no further keypress is accepted, including CTRL-ALT-DEL. You are locked out. This is for all kernels I tested. It does not depend on some special kernel. With the help of SystemRescueCD I've booted up and analyzed the logs written by systemd: Systemd starts consoles. Then, after starting some further parts of the system, terminates consoles. I could not find any console starts afterwards. I'd expect systemd to restart any terminated console for as long as systemd runs. This does not happen. Systemd is configured to restart consoles, but it does not do it. I was not able to find out why. Networking is started but it seems not to establish network connections until users log in. In tune sshd never starts, because network isn't started at all. If you manage to login typing really fast, while the cursor blinks behind "login:" networking will start! You may be locked out at consoles, because no keypresses are accepted any more, but in case you managed to login, NetworkManager starts networking for the logged in user and in tune sshd is started and you may then login remote. -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
This kernel does not work either. Are you sure it is the kernel? I'd say it is systemd not doing what is expected. ALL kernels you gave me to test WILL work together with Ubuntu 16.04.1 LTS!! ALL WORK. None of them works with Ubuntu 16.10!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
Was to fast -- non of these kernels work! They'll boot to login, but leaving the system alone for some time -> no keyboard, no mouse. Looks like these are started by systemd, but then terminated again. Maybe it's two different errors one being solved by changing kernels, one within system startup ...? -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
I've tested these now (quite difficult to push them into an image not running self contained ...): 4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ -- seems to work: booting is ok, but no keyboard, no mouse. Unsure if keyboard and mouse are available for short, but the cursor blinks behind login, then jumps to blink under the "l" or login. At least once I was able to type "root", before the cursor changed position. Afterwards I could not enter any additional key. The mouse was dead either. 4.6 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ -- seems to hang without "modprobe.balcklist=intel_powerclamp". With it boots to prompt, but looses keyboard and mouse short after the prompt is shown. The cursor jumps to the "l" of login at that point. It is a few seconds. I was able to login once. The system is then accessible. sshd ist started in such a case (it is not, if you cant manage to login). I've tried the latest 4.4 kernel from 16.04.1 -- this one works. I converted CentOS kernels from elrepo using alien. They all worked: 4.4.x (-lt) 4.7.x (-ml) 4.8.x (-ml) -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
And it is not guarantied systems boot through -- about every fifth boot fails. Last printed line on screen: "Reached target multi user system". No keyboard, no mouse, no network. I have to reset VM as I have to reset real Hardware! -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
And what a mess: after about 10 minutes you'll be unable to type anything on consoles. All keyboard events are ignored, as are mouse events! The systems boot thrugh, start networking as expected, but then cancel networking. -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
Should have written modprobe.blacklist=intel_powerclamp -- this works. The systems now boot with kernel v4.7 final, v4.8-rc1 and the default kernel installed. But ssh does not get started as before. Upgrading will make you loose connection to an headless server (tried on VMware, confirmed on real hardware). -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
Have a look at CentOS Mainline-kernels found at "http://elrepo.org/linux/kernel/el7/"; these work even with ubuntu! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
The bug exists in v4.7 final as in v4.8-rc1 -- as long as I use the Ubuntu kernels. compiling plain vanilla kernels seem to not have this bug (taking configuration from Ubuntu). I tried to add modeprobe.blacklist=intel_powerclamp" without any effect: same as before -- no keyboard, no mouse. -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
I've added kernel-bug-exists-upstream since this bug is in the latest upstream kernel, linux-image-4.8.0-17-generic, present. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Fix Released Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 919961] Re: Rescue mode not usable with latest kernel
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/919961 Title: Rescue mode not usable with latest kernel Status in “linux” package in Ubuntu: Fix Released Bug description: If booting the lates kernel "linux-image-3.0.0-15-server", rescue mode is not usable. The system will boot into rescue mode, then show the menu, but no keypress is accepted. You can't select any entry using up- and down-arrow keys, enter isn't accepted, tab is ignored. Booting kernel "linux-image-3.0.0-14-server" all is ok again. The same applies for all other latest kernels for all other Ubuntu- Versions: Ubuntu 10.04 LTS: "linux-image-2.6.32-38-virtual" does not work with rescue mode, while "linux-image-2.6.32-37-virtual" works Ubuntu 10.10: "linux-image-2.6.35-32-server" does not work with rescue mode, while "linux-image-2.6.35-31-server" works Ubuntu 11.04: "linux-image-2.6.38-13-server" does not work with rescue mode, while "linux-image-2.6.38-12-server" works Ubuntu 11.10: "linux-image-3.0.0-15-server" does not work with rescue mode, while "linux-image-3.0.0-14-server" works Ubuntu 12.04: "linux-image-3.2.0-9-generic" does not work with rescue mode, while "linux-image-3.2.0-8-generic" works For plain vanilla kernels: "linux-image-3.1.10" doe not work with rescue mode, while "linux-image-3.1.9" works Other plain vanilla kernels I did not test. All tests where done using kvm-qemu and VMwareWorkstation/Player 7 or 8 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image (not installed) ProcVersionSignature: Ubuntu 3.0.0-14.23-server 3.0.9 Uname: Linux 3.0.0-14-server x86_64 AcpiTables: Error: command ['sudo', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 1: Sorry, try again. Sorry, try again. Sorry, try again. sudo: 3 incorrect password attempts AlsaDevices: total 0 crw-rw 1 root audio 116, 1 2012-01-22 11:09 seq crw-rw 1 root audio 116, 33 2012-01-22 11:09 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 1.23-0ubuntu4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Date: Sun Jan 22 12:01:29 2012 HibernationDevice: RESUME=UUID=f8a560f8-2358-4179-8350-3ba1009f3772 InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release amd64 (20101007) IwConfig: Error: [Errno 2] No such file or directory MachineType: FUJITSU PRIMERGY RX300 S6 PciMultimedia: ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=de_DE.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-server root=UUID=bc692d1e-ddb7-4a4b-b240-95da6efeabc0 ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.0.0-14-server N/A linux-backports-modules-3.0.0-14-server N/A linux-firmware 1.60 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2010 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: 6.00 Rev. 1.08.2619.N1 dmi.board.asset.tag: - dmi.board.name: D2619 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D2619-N15 WGS10 GS02 dmi.chassis.asset.tag: YL6T019858 dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: RX300S6R1 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00Rev.1.08.2619.N1:bd10/06/2010:svnFUJITSU:pnPRIMERGYRX300S6:pvrGS01:rvnFUJITSU:rnD2619:rvrS26361-D2619-N15WGS10GS02:cvnFUJITSU:ct23:cvrRX300S6R1: dmi.product.name: PRIMERGY RX300 S6 dmi.product.version: GS01 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/919961/+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 1270656] Re: Ubuntu 14.04 boots to blank console
Seems fixed now -- 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
With my laptop the problem is gone using my self compiled kernel or the latest one from Ubuntu. It is there using some older kernels. I had to carefully adjust "vga=xxx" to switch to the very same mode than gfxpayload set to 1280x800@32. Took some time and playing around until it worked as expected. After compiling in all deprecated mode-switching stuff into the kernel I didn't have any problems any more. Looks a lot like bugs in mode handling with the kernel and/or grub2. Even access restrictions may be the case, because I saw some non fatal warnings about write restricted warnings hushing by while the kernel initialized. But the main point was to keep all deprecated mode-switching stuff in to have graphics work as expected -- seems there are a lot of parts within all the graphics code depending on these, breaking if they are not 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
Looks like since the later updates the bug seems gone -- at least for vmwares graphics drivers. On an other system running on real hardware the bug seems gone too. I'll check later today on my laptop -- hopefully it is history there too! -- 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
Since today a new version of open-vm-tools is available. I've tested again with this new version. Some of the errors seen with the old version are gone now. ** Attachment added: "New version of open-vm-tools" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3955154/+files/dmsg-201401231619.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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
With this kernel-option I'll get a console prompt, but various kernel log lines are never prinited on screen. Printing stops at about "[ 54.811735] [drm] DMA map mode: Using physical TTM page addresses." and then starts again after a screen size change at about "[ 57.317174] intel_rapl: domain core energy ctr 0:0 not working, skip". With the self compiled kernel all lines are printed. ** Attachment added: "dmesg-log vmwgfx.enable_fbdev=1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3955124/+files/dmsg-201401231548.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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "dmesg-log from Ubuntu-Kernel, no driver blacklisted" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954637/+files/dmsg-201401221500.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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
My fault: picked the wrong dmesg-files …! -- 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "dmesg-log from my own kernel, no driver blacklisted" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954635/+files/dmsg-201401221526.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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "blacklist vmwgfx -- own kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954415/+files/dmsg-201401221458.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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "blacklist simple-framebuffer -- own kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954417/+files/dmsg-201401221500.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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "blacklist simple-framebuffer" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954402/+files/dmsg-201401221458.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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "none blacklisted -- own kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954405/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_035.jpg -- 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "blacklisted vmwgfx" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954399/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_035.jpg -- 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "none blacklisted" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954403/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_037.jpg -- 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "blacklist vmwgfx -- own kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954414/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_036.jpg -- 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "none blacklisted -- own kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954406/+files/dmsg-201401221456.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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
There are slightly differences in character display depending on which driver is blacklisted. With my own kernel I could recognize changes in character display while booting. -- 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "blacklist simple-framebuffer -- own kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954416/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_037.jpg -- 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "none blacklisted" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954404/+files/dmsg-201401221500.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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "blacklist simple-framebuffer" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954401/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_036.jpg -- 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "blacklisted vmwgfx" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954400/+files/dmsg-201401221456.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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
#12: yes this is true, but does not explain why this leads to "blank console" using the ubuntu supplied kernel and not using one self compiled from plain vanilla sources. I've tested since: 3.12.8, 3.13.0-rc8 and 3.13. All show the same result: working console at expected 800x600. The ubuntu supplied kernel does not show a working console: only black blank screen. It does not matter if within VMware, VirtualBox or on real hardware -- it is all the same: console working if 640x480 but not if set to 800x600 (or even higher -- I just do not set VMs to use higher resolutions because my monitor isn't large enough for more). Even the working kernel show this conflict -- IMHO it isn't the cause Ubuntu supplied kernels do not work. I've tired to compile an Ubuntu supplied kernel, but failed miserably (I gave up, because I *can* compile plain vanilla ones -- why should I crop with applied patches?). Within the fb-subsystem there are differences in kernel compile options. Ubuntu kernels use a slightly different setup then I. I'd expect to find the source of this problem there. ** Also affects: linux (Debian) Importance: Undecided Status: New ** Also affects: linux (Fedora) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Debian: New Status in “linux” package in Fedora: New Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
apport-collect fails to login to launchpad after allowing to access on my behalf see: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1270717 -- 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: ""apport-bug linux"-run output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3952531/+files/apport.linux-image-3.13.0-4-generic.aasrvt.apport ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
** Attachment added: "Console using plain vanilla kernel 3.13.0-rc8" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3952528/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_024.jpg -- 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/1270656 Title: Ubuntu 14.04 boots to blank console Status in “linux” package in Ubuntu: Incomplete Bug description: Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console. Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows /sbin/getty running on tty{1..6}: # ps axf | grep tty 880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4 885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5 890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2 891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3 893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6 4290 pts/1S+ 0:00 \_ grep --color=auto tty 1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1 Removing deprecated "vga=768" from kernel commandline => doesn't boot into 800x600, keeps 640x480 Settings GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD=800x600 are ignored. Grub boots up with 800x600, switches back to 640x480 (setting GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back to 800x600. Adding deprecated "vga=768" back in: Grub boots up with 800x600, switches back to 640x480, kernel switches back to 800x600, but doesn't use this console. No output at all. Keys are accepted (you can login, but you'll have to guess what is going on on the screen). Exactly the same error is found with debian. Switching to a self compiled kernel solves this error. Looks a lot like some necessary stuff for console resolution switching is missing in the debian -/ubuntu-kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 20 00:20:36 2014 InstallationDate: Installed on 2012-12-12 (403 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 876715] Re: Message "Unhandled kernel version 3.0" while booting
** Tags removed: needs-upstream-testing ** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.11.0-15 kernel-fixed-upstream-3.4.70 -- 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/876715 Title: Message "Unhandled kernel version 3.0" while booting Status in “linux” package in Ubuntu: Incomplete Bug description: While booting the message "Unhandled kernel version 3.0" is printed. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-server 3.0.0.12.14 ProcVersionSignature: Ubuntu 3.0.0-12.20-server 3.0.4 Uname: Linux 3.0.0-12-server x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 2011-10-14 18:27 seq crw-rw 1 root audio 116, 33 2011-10-14 18:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 1.23-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 20.432121] eth0: no IPv6 routers present Date: Mon Oct 17 19:57:13 2011 HibernationDevice: RESUME=UUID=c77bc4d1-d0f4-4524-854c-a80485e4d232 InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release amd64 (20101007) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs PciMultimedia: ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-server root=/dev/mapper/hostname-root ro vga=0x314 elevator=deadline consoleblank=0 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-server N/A linux-backports-modules-3.0.0-12-server N/A linux-firmware 1.60 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/876715/+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 876715] Re: Message "Unhandled kernel version 3.0" while booting
This Bug doesnt Affect me any more. I can Install all available kernels now on 12.04.3 -- 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/876715 Title: Message "Unhandled kernel version 3.0" while booting Status in “linux” package in Ubuntu: Incomplete Bug description: While booting the message "Unhandled kernel version 3.0" is printed. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-server 3.0.0.12.14 ProcVersionSignature: Ubuntu 3.0.0-12.20-server 3.0.4 Uname: Linux 3.0.0-12-server x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 2011-10-14 18:27 seq crw-rw 1 root audio 116, 33 2011-10-14 18:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 1.23-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 20.432121] eth0: no IPv6 routers present Date: Mon Oct 17 19:57:13 2011 HibernationDevice: RESUME=UUID=c77bc4d1-d0f4-4524-854c-a80485e4d232 InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release amd64 (20101007) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs PciMultimedia: ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-server root=/dev/mapper/hostname-root ro vga=0x314 elevator=deadline consoleblank=0 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-server N/A linux-backports-modules-3.0.0-12-server N/A linux-firmware 1.60 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/876715/+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