[Kernel-packages] [Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
*** This bug is a duplicate of bug 1910709 *** https://bugs.launchpad.net/bugs/1910709 ** This bug has been marked a duplicate of bug 1910709 DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 -- 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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: Confirmed Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN
[Kernel-packages] [Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
Upgrading to nvidia-opencl-icd-340:amd64 (340.108-0ubuntu2, 340.108-0ubuntu5.20.04.1) from focal-proposed solves this problem. See bug #1910709. I came to this conclusion after testing the focal-daily (20210116) and finding that nvidia-340 installed just fine. Since LTS daily builds always have the proposed repos enabled it was just a matter of parsing what packages were available in proposed. Probably OK to mark this fix released but I'll leave that decision up to one of the devs. -- 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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: Confirmed Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No
[Kernel-packages] [Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
I changed the package name from "meta" to just linux to get apport- collect to work. Hope that's OK. -- 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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: Confirmed Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1912032] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453633/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9
[Kernel-packages] [Bug 1912032] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453635/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor:
[Kernel-packages] [Bug 1912032] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453634/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor:
[Kernel-packages] [Bug 1912032] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453636/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9
[Kernel-packages] [Bug 1912032] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453629/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9
[Kernel-packages] [Bug 1912032] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453630/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type:
[Kernel-packages] [Bug 1912032] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453632/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9
[Kernel-packages] [Bug 1912032] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453631/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9
[Kernel-packages] [Bug 1912032] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453624/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor:
[Kernel-packages] [Bug 1912032] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453627/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9
[Kernel-packages] [Bug 1912032] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453622/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9
[Kernel-packages] [Bug 1912032] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453625/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9
[Kernel-packages] [Bug 1912032] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453621/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell
[Kernel-packages] [Bug 1912032] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453623/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9
[Kernel-packages] [Bug 1912032] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453628/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9
[Kernel-packages] [Bug 1912032] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453626/+files/Lsusb.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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor:
[Kernel-packages] [Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
apport information ** Package changed: linux-meta-hwe-5.8 (Ubuntu) => linux (Ubuntu) ** Tags added: apport-collected ** Description changed: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: lance 829 F pulseaudio + /dev/snd/controlC1: lance 829 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-01-15 (0 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: Dell Inc. Latitude E6510 + Package: linux (not installed) + PccardctlIdent: + Socket 0: +no product info available + PccardctlStatus: + Socket 0: +no card + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 nouveaudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-38-generic N/A + linux-backports-modules-5.8.0-38-generic N/A + linux-firmware1.187.2 + Tags: focal + Uname: Linux 5.8.0-38-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/12/2017 + dmi.bios.release: 4.6 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A17 + dmi.board.name: 0N5KHN + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA17:bd05/12/2017:br4.6:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn0N5KHN:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.name: Latitude E6510 + dmi.product.version: 0001 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt"
[Kernel-packages] [Bug 1537918] Re: Kernel doesn't support UDF
*** This bug is a duplicate of bug 1584509 *** https://bugs.launchpad.net/bugs/1584509 ** This bug has been marked a duplicate of bug 1584509 hybrid CDs/DVDs not mounted in xenial -- 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/1537918 Title: Kernel doesn't support UDF Status in linux package in Ubuntu: Confirmed Bug description: I was pulling my hair out for the last six months trying to figure out why the heck some DVDs (encrypted, pressed, burned, it doesn't matter) just will not be recognized. In the GNOME Disk Utility, the disks show up as X.X GB Unknown, and will not mount. I have to manually go into a terminal, type sudo mount /dev/sr0 /mnt and just deal with it. This is a real pain, and I just recently figured out why. According to this: http://superuser.com/questions/730130/how-to-get-ubuntu-12-04-to- recognize-the-udf-filesystem in addition to this: http://www.linuxquestions.org/questions/linux-desktop-74/some-udf- dvds-will-not-mount-unknown-filesystem-4175550577/ I deduced that the kernel was not compiled with UDF support. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihatewindows 28002 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 22 13:55:28 2016 HibernationDevice: RESUME=UUID=2f0f1d7c-4117-40df-9314-f2556c82fc3b InstallationDate: Installed on 2015-11-12 (71 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E5420 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd11/30/2011:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537918/+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 1537918] Re: Kernel doesn't support UDF
"I'm leaning towards this" . "this" being the ability to mount optical discs with existing data. -- 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/1537918 Title: Kernel doesn't support UDF Status in linux package in Ubuntu: Confirmed Bug description: I was pulling my hair out for the last six months trying to figure out why the heck some DVDs (encrypted, pressed, burned, it doesn't matter) just will not be recognized. In the GNOME Disk Utility, the disks show up as X.X GB Unknown, and will not mount. I have to manually go into a terminal, type sudo mount /dev/sr0 /mnt and just deal with it. This is a real pain, and I just recently figured out why. According to this: http://superuser.com/questions/730130/how-to-get-ubuntu-12-04-to- recognize-the-udf-filesystem in addition to this: http://www.linuxquestions.org/questions/linux-desktop-74/some-udf- dvds-will-not-mount-unknown-filesystem-4175550577/ I deduced that the kernel was not compiled with UDF support. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihatewindows 28002 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 22 13:55:28 2016 HibernationDevice: RESUME=UUID=2f0f1d7c-4117-40df-9314-f2556c82fc3b InstallationDate: Installed on 2015-11-12 (71 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E5420 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd11/30/2011:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537918/+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 1537918] Re: Kernel doesn't support UDF
I'm leaning towards this being a duplicate of bug 1577768, or vice versa, and thinking the actual culprit may be util-linux / libblkid1. -- 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/1537918 Title: Kernel doesn't support UDF Status in linux package in Ubuntu: Confirmed Bug description: I was pulling my hair out for the last six months trying to figure out why the heck some DVDs (encrypted, pressed, burned, it doesn't matter) just will not be recognized. In the GNOME Disk Utility, the disks show up as X.X GB Unknown, and will not mount. I have to manually go into a terminal, type sudo mount /dev/sr0 /mnt and just deal with it. This is a real pain, and I just recently figured out why. According to this: http://superuser.com/questions/730130/how-to-get-ubuntu-12-04-to- recognize-the-udf-filesystem in addition to this: http://www.linuxquestions.org/questions/linux-desktop-74/some-udf- dvds-will-not-mount-unknown-filesystem-4175550577/ I deduced that the kernel was not compiled with UDF support. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihatewindows 28002 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 22 13:55:28 2016 HibernationDevice: RESUME=UUID=2f0f1d7c-4117-40df-9314-f2556c82fc3b InstallationDate: Installed on 2015-11-12 (71 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E5420 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd11/30/2011:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537918/+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 1359689] Re: cryptsetup password prompt not shown
I was not able to reproduce this behavior using the Ubuntu GNOME Xenial 20160323.1 images. -- 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/1359689 Title: cryptsetup password prompt not shown Status in linux package in Ubuntu: Triaged Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Triaged Status in plymouth package in Debian: Fix Released Bug description: Currently in utopic the following happens when booting an encrypted setup: Press enter in grub, after a while screen freezes (or turns completely black) and stays like that. When I press the down key, I can see the password prompt. When I press the up key again, I get to the graphical password prompt. This is demonstrated in the following screencast: https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing Maybe this is related to the version of plymouth utopic currently uses, a similar debian bug report seems to be resolved with a newer version 0.9.0-6, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752. --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) MachineType: Dell Inc. Precision M4600 Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689/+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 1359689] Re: cryptsetup password prompt not shown
This is fixed in Ubuntu GNOME Xenial 20160225.1 amd64. -- 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/1359689 Title: cryptsetup password prompt not shown Status in linux package in Ubuntu: Triaged Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Triaged Status in plymouth package in Debian: Fix Released Bug description: Currently in utopic the following happens when booting an encrypted setup: Press enter in grub, after a while screen freezes (or turns completely black) and stays like that. When I press the down key, I can see the password prompt. When I press the up key again, I get to the graphical password prompt. This is demonstrated in the following screencast: https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing Maybe this is related to the version of plymouth utopic currently uses, a similar debian bug report seems to be resolved with a newer version 0.9.0-6, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752. --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) MachineType: Dell Inc. Precision M4600 Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689/+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 1359689] Re: cryptsetup password prompt not shown
I'm seeing this with the latest Ubuntu GNOME Xenial images. After completing a full disk encryption install the newly installed OS just boots to a blank, black screen. Then if you fiddle around with various key combinations (sometimes just repeatedly pressing esc) text will finally appear on the screen asking to "please unlock disk sda5_crypt". And if you hold your mouth just right you may be able to blindly enter the encryption password and boot with just the right keyboard combination. (pic attached) ** Attachment added: "IMG_5112.JPG" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689/+attachment/4580589/+files/IMG_5112.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/1359689 Title: cryptsetup password prompt not shown Status in linux package in Ubuntu: Triaged Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Triaged Status in plymouth package in Debian: Fix Released Bug description: Currently in utopic the following happens when booting an encrypted setup: Press enter in grub, after a while screen freezes (or turns completely black) and stays like that. When I press the down key, I can see the password prompt. When I press the up key again, I get to the graphical password prompt. This is demonstrated in the following screencast: https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing Maybe this is related to the version of plymouth utopic currently uses, a similar debian bug report seems to be resolved with a newer version 0.9.0-6, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752. --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) MachineType: Dell Inc. Precision M4600 Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689/+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 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
** Changed in: linux (Ubuntu) Status: Confirmed = Fix Released ** Changed in: linux (Ubuntu Trusty) Status: Confirmed = Fix Released ** Changed in: linux (Ubuntu Utopic) Status: Confirmed = Fix Released ** Changed in: linux (Ubuntu Vivid) Status: Confirmed = Fix Released ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New = Fix Released ** Changed in: xserver-xorg-video-nouveau (Ubuntu Trusty) Status: New = Fix Released ** Changed in: xserver-xorg-video-nouveau (Ubuntu Utopic) Status: New = Fix Released ** Changed in: xserver-xorg-video-nouveau (Ubuntu Vivid) Status: New = 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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Nouveau Xorg driver: Unknown Status in linux package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in xserver-xorg-video-nouveau source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in xserver-xorg-video-nouveau source package in Utopic: Fix Released Status in linux source package in Vivid: Fix Released Status in xserver-xorg-video-nouveau source package in Vivid: Fix Released Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ### Additional workaround and debug info ### The focus of this bug report is limited to screen corruption and X-freezes that either prevent the installation of Ubuntu (or other flavors) and/or booting the installed system even long enough to enable the third party nvidia driver. There are almost certainly other instances of screen corruption and hard (or soft) lockups that may also be related to the nouveau driver but those are beyond the scope of this specific bug report. To workaround this bug, or to see if you're affected by it you can boot using this boot parameter: nouveau.config=NvMSI=0 You'll find general instructions for using custom boot parameters at these links: https://help.ubuntu.com/community/BootOptions https://wiki.ubuntu.com/Kernel/KernelBootParameters In addition to what's said at the latter link about temporarily adding a kernel boot parameter to an installed system; after using the arrow keys to navigate to the line beginning with linux /boot you'll notice that line ends with quiet splash $vt_handoff. The boot parameter belongs between the quiet splash and $vt_handoff like this: quiet splash nouveau.config=NvMSI=0 $vt_handoff ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
No surprise but since the 14.04.2 20150217 images still have 3.16.0-30 generic they are affected. Since it's a hardware specific corner issue I don't know if it's worth mentioning in the release notes or not. -- 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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Accelerated Xorg driver for nVidia cards: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in xserver-xorg-video-nouveau source package in Trusty: New Status in linux source package in Utopic: Confirmed Status in xserver-xorg-video-nouveau source package in Utopic: New Status in linux source package in Vivid: Confirmed Status in xserver-xorg-video-nouveau source package in Vivid: New Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ### Additional workaround and debug info ### The focus of this bug report is limited to screen corruption and X-freezes that either prevent the installation of Ubuntu (or other flavors) and/or booting the installed system even long enough to enable the third party nvidia driver. There are almost certainly other instances of screen corruption and hard (or soft) lockups that may also be related to the nouveau driver but those are beyond the scope of this specific bug report. To workaround this bug, or to see if you're affected by it you can boot using this boot parameter: nouveau.config=NvMSI=0 You'll find general instructions for using custom boot parameters at these links: https://help.ubuntu.com/community/BootOptions https://wiki.ubuntu.com/Kernel/KernelBootParameters In addition to what's said at the latter link about temporarily adding a kernel boot parameter to an installed system; after using the arrow keys to navigate to the line beginning with linux /boot you'll notice that line ends with quiet splash $vt_handoff. The boot parameter belongs between the quiet splash and $vt_handoff like this: quiet splash nouveau.config=NvMSI=0 $vt_handoff ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 19 17:41:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
** Description changed: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu- desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. + ##Additional workaround and debug info: + + The focus of this bug report is limited to screen corruption and + X-freezes that either prevent the installation of Ubuntu (or other + flavors) and/or booting the installed system even long enough to enable + the third party nvidia driver. There are almost certainly other + instances of screen corruption and hard (or soft) lockups that may also + be related to the nouveau driver but those are beyond the scope of this + specific bug report. + + To workaround this bug, or to see if you're affected by it you can boot + using this boot parameter: + + nouveau.config=NvMSI=0 + + You'll find general instructions for using custom boot parameters at + these links: + + https://help.ubuntu.com/community/BootOptions + + https://wiki.ubuntu.com/Kernel/KernelBootParameters + + In addition to what's said at the latter link about temporarily adding a + kernel boot parameter to an installed system; after using the arrow keys + to navigate to the line beginning with linux /boot you'll notice that + line ends with quiet splash $vt_handoff. The boot parameter belongs + between the quiet splash and $vt_handoff like this: + + quiet splash nouveau.config=NvMSI=0 $vt_handoff + + ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 .tmp.unity.support.test.0: - + ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 19 17:41:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) -Subsystem: Biostar Microtech Int'l Corp Device [1565:1405] + NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) + Subsystem: Biostar Microtech Int'l Corp Device [1565:1405] InstallationDate: Installed on 2015-01-19 (0 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118) Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 002: ID 046d:c52e Logitech, Inc. - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 046d:c52e Logitech, Inc. + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: BIOSTAR Group N68SB-M2S ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
OK I did some more testing last night and this AM, so here's a quick recap to reduce any confusion (both for others and myself): Vivid: This is fixed in 3.18.0-13 generic. I verified that this AM by testing the Ubuntu GNOME Vivid 20150215 amd64 iso. Utopic: This is fixed in 3.16.0-31 generic which is in utopic-proposed. No additional problems were encountered. Trusty with the Utopic HWE: This is fixed in 3.16.0-31 generic which is in trusty-proposed. The bug I mentioned in comment #19 was observed and I think it may be bug #1291574. I'll follow up on that separate issue appropriately ASAP. Trusty with the OEM 3.13 series kernel: This remains under investigation. I know that both the 14.04 and 14.04.1 images are affected as well as 3.13.0-45-generic. I'll also follow up on this ASAP. -- 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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Accelerated Xorg driver for nVidia cards: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in xserver-xorg-video-nouveau source package in Trusty: New Status in linux source package in Utopic: Confirmed Status in xserver-xorg-video-nouveau source package in Utopic: New Status in linux source package in Vivid: Confirmed Status in xserver-xorg-video-nouveau source package in Vivid: New Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 19 17:41:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp Device [1565:1405] InstallationDate: Installed on 2015-01-19 (0 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c52e Logitech, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: BIOSTAR Group N68SB-M2S ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
Regarding Trusty with the OEM 3.13 series kernel: This is NOT fixed in 3.13.0-46-generic from trusty-proposed. That can be verified because using the nouveau.config=NvMSI=0 boot parameter gets me past the screen corruption/X freeze. So evidently the upstream fix has not yet trickled down to the 3.13 series kernel. -- 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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Accelerated Xorg driver for nVidia cards: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in xserver-xorg-video-nouveau source package in Trusty: New Status in linux source package in Utopic: Confirmed Status in xserver-xorg-video-nouveau source package in Utopic: New Status in linux source package in Vivid: Confirmed Status in xserver-xorg-video-nouveau source package in Vivid: New Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 19 17:41:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp Device [1565:1405] InstallationDate: Installed on 2015-01-19 (0 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c52e Logitech, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: BIOSTAR Group N68SB-M2S ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=acf0fd65-0d6d-4da6-9532-2adc558bc0a7 ro quiet splash init=/lib/systemd/systemd SourcePackage: xserver-xorg-video-nouveau UdevLog: UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 06/24/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: N68SB-M2S dmi.board.vendor: BIOSTAR Group dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: N68SB-M2S dmi.modalias:
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
Sorry to take so long getting back to this. The affected PC is usually used as my media center but I've now been able to move it into my testing suite so hopefully once 14.04.2 milestone testing is out of the way I'll be able to respond more quickly and efficiently. Regarding the screen corruption in Utopic I've now found that it does eventually occur even running GNOME Classic but just much less frequently than in a GNOME Shell session. This includes both the stock Utopic kernel as well as the 3.16.7-031607-generic kernel Joseph Salisbury requested I try. So, moving on to Vivid for the moment - last night I installed Ubuntu GNOME Vivid Alpha 2 and this AM I booted it using the nouveau.config=NvMSI=0 boot parameter, then applied all available updates, and it seems to be running GNOME Shell just fine with the latest Vivid kernel using the nouveau driver: lance@lance-AMD-desktop:~$ uname -r 3.18.0-13-generic lance@lance-AMD-desktop:~$ sudo lshw -c video [sudo] password for lance: *-display description: VGA compatible controller product: C61 [GeForce 7025 / nForce 630a] vendor: NVIDIA Corporation physical id: d bus info: pci@:00:0d.0 version: a2 width: 64 bits clock: 66MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:21 memory:fb00-fbff memory:e000-efff memory:fc00-fcff memory:8000-8001 So some recent kernel update in Vivid appears to have fixed this issue. Is there still any point in trying the 3.18.5-031805-generic mainline kernel? For the next 5 or 6 days I'll be shifting my focus almost totally onto 14.04.2, in fact my next two tests on this hardware will be 14.04.1 with the latest Trusty kernel and then 14.04.2 with the Utopic HWE. -- 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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Accelerated Xorg driver for nVidia cards: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in xserver-xorg-video-nouveau source package in Trusty: New Status in linux source package in Utopic: Confirmed Status in xserver-xorg-video-nouveau source package in Utopic: New Status in linux source package in Vivid: Confirmed Status in xserver-xorg-video-nouveau source package in Vivid: New Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
I was encountering some issues installing 14.04.1 which I'll get into later, but for now I moved on to testing 14.04.2, this one installed w /Ubuntu-GNOME 14.04.2 LTS Trusty Tahr - Release amd64 (20150203), and while 3.16.0-30-generic was affected I pulled 3.16.0-31-generic from trusty-proposed and it appeared to be OK for a while, at least I was not getting the same screen corruption. In fact I began a forum post from that Trusty install but before I was done the screen became unresponsive, but not entirely frozen because I could move the mouse pointer, then after a minute or two the screen displayed the error in the attached pic. ** Attachment added: Trusty_full_screen.JPG https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1412602/+attachment/4319358/+files/Trusty_full_screen.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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Accelerated Xorg driver for nVidia cards: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in xserver-xorg-video-nouveau source package in Trusty: New Status in linux source package in Utopic: Confirmed Status in xserver-xorg-video-nouveau source package in Utopic: New Status in linux source package in Vivid: Confirmed Status in xserver-xorg-video-nouveau source package in Vivid: New Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 19 17:41:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp Device [1565:1405] InstallationDate: Installed on 2015-01-19 (0 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c52e Logitech, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: BIOSTAR Group N68SB-M2S ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
@ Tim Lunn, This is totally unrelated, but to be certain that Vivid is working properly w/3.18.0-13-generic I've been using it to post all of these messages and on the last boot apport presented me with a gdm error so I accepted the automated reporting which is bug #1421991. Poorly written for sure, but I really had no idea what was going on. -- 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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Accelerated Xorg driver for nVidia cards: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in xserver-xorg-video-nouveau source package in Trusty: New Status in linux source package in Utopic: Confirmed Status in xserver-xorg-video-nouveau source package in Utopic: New Status in linux source package in Vivid: Confirmed Status in xserver-xorg-video-nouveau source package in Vivid: New Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 19 17:41:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp Device [1565:1405] InstallationDate: Installed on 2015-01-19 (0 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c52e Logitech, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: BIOSTAR Group N68SB-M2S ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=acf0fd65-0d6d-4da6-9532-2adc558bc0a7 ro quiet splash init=/lib/systemd/systemd SourcePackage: xserver-xorg-video-nouveau UdevLog: UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 06/24/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: N68SB-M2S dmi.board.vendor: BIOSTAR Group dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: N68SB-M2S
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
It turns out that both 14.04 and 14.04.1 are affected by this bug. I had to look in the installer log to see what version I'd begun with (and have been running on that box as my stable OS) = Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140129). So I was undoubtedly able to install Trusty at that point but hadn't noticed a problem because I was already using the third-party nvidia driver after that date. -- 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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Accelerated Xorg driver for nVidia cards: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in xserver-xorg-video-nouveau source package in Trusty: New Status in linux source package in Utopic: Confirmed Status in xserver-xorg-video-nouveau source package in Utopic: New Status in linux source package in Vivid: Confirmed Status in xserver-xorg-video-nouveau source package in Vivid: New Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 19 17:41:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp Device [1565:1405] InstallationDate: Installed on 2015-01-19 (0 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c52e Logitech, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: BIOSTAR Group N68SB-M2S ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=acf0fd65-0d6d-4da6-9532-2adc558bc0a7 ro quiet splash init=/lib/systemd/systemd SourcePackage: xserver-xorg-video-nouveau UdevLog: UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 06/24/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: N68SB-M2S dmi.board.vendor: BIOSTAR Group dmi.chassis.type: 3
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
Hi Tim, As far as I can tell ATM the only difference in most of these crashes/freezes/screen-corruptions is the frequency with which they occur and the screen color depending on what point during boot and/or operation the freeze occurs. Like this is the pic I included with original bug report: https://launchpadlibrarian.net/195348138/IMG_4796.JPG And this is a pic from Ubuntu GNOME Utopic with the amd64 version of 3.16.7-031607-generic (mainline kernel): https://launchpadlibrarian.net/196872607/IMG_4817.JPG The frequency of crashes/freezes (or the point at which they occur) is sometimes random with the exact same images. Sometimes it may prevent me from even getting to the live desktop or booting to the desktop of an installed OS. Other times it may not happen until I'm performing some random task on the desktop. Or it may occur at any random point during installation. It seems to affect Unity, GNOME Shell, and Flashback w/Compiz somewhat more frequently that GNOME Classic and I've not been able to reproduce this bug with the same versions of Lubuntu so I assume it's a load or demand related issue??? The one exception is 14.04.2 with 3.16.0-31-generic from trusty-proposed which may (or may not) fix this issue but results in an unrelated crash (see comment #19) so I'll check the changelogs and see if there is a tracking bug # to refer to. I'll then file a new bug report ASAP. But yes, this does appear to be fixed in Vivid w/3.18.0-13-generic. I will be glad to try the 3.18.5-031805-generic mainline kernel in Vivid also if desired. I should also probably test Utopic again and see if I can find the equivalent of trusty-proposed 3.16.0-31-generic since it really is part of the 14.04.2 LTS HWE for Trusty. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Accelerated Xorg driver for nVidia cards: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in xserver-xorg-video-nouveau source package in Trusty: New Status in linux source package in Utopic: Confirmed Status in xserver-xorg-video-nouveau source package in Utopic: New Status in linux source package in Vivid: Confirmed Status in xserver-xorg-video-nouveau source package in Vivid: New Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
I have been able to reproduce that a few times in a gnome-shell session but it's not specific to any one task. It crashed/froze twice just looking for logs and once again while launching Firefox. OTOH I can use the classic session w/o a problem - in fact I'm streaming the nightly news right now. I know that X actually freezes when the screen tears because I'd set Ctrl+Alt+Backspace to kill X and tested it in both sessions. When the screen tears as shown in the attached pic the keyboard is just totally unresponsive causing me to do a hard reset. There are no .xsession-errors in Home and I don't see anything unusual in /var/log/Xorg.0.log but there is also an /var/log/Xorg.0.log.old that I can't read. FYI sometime tomorrow I'll add some storage to that box so I can retain 4 or 5 installs at the same time. That way I can dig for logs and/or do some retesting without having to reinstall and update each time. ** Attachment added: IMG_4817.JPG https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1412602/+attachment/4314052/+files/IMG_4817.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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Accelerated Xorg driver for nVidia cards: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in xserver-xorg-video-nouveau source package in Trusty: New Status in linux source package in Utopic: Confirmed Status in xserver-xorg-video-nouveau source package in Utopic: New Status in linux source package in Vivid: Confirmed Status in xserver-xorg-video-nouveau source package in Vivid: New Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 19 17:41:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp Device [1565:1405] InstallationDate: Installed on 2015-01-19 (0 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
@ Joseph Salisbury, There seemed to be some improvement in Ubuntu GNOME Utopic with the amd64 version of 3.16.7-031607-generic, at least I was able to boot that kernel w/o adding the nouveau.config=NvMSI=0 boot parameter, but then after spending a couple of minutes fiddling around when I attempted to open the System Settings UI the screen tore and X froze. So nouveau is still a failure with that specific GPU. I doubt it's arch specific so I'll move on to testing the Vivid mainline kernel next. -- 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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Accelerated Xorg driver for nVidia cards: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in xserver-xorg-video-nouveau source package in Trusty: New Status in linux source package in Utopic: Confirmed Status in xserver-xorg-video-nouveau source package in Utopic: New Status in linux source package in Vivid: Confirmed Status in xserver-xorg-video-nouveau source package in Vivid: New Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 19 17:41:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp Device [1565:1405] InstallationDate: Installed on 2015-01-19 (0 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c52e Logitech, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: BIOSTAR Group N68SB-M2S ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=acf0fd65-0d6d-4da6-9532-2adc558bc0a7 ro quiet splash init=/lib/systemd/systemd SourcePackage: xserver-xorg-video-nouveau UdevLog: UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 06/24/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
Perhaps oddly (perhaps not oddly at all) I decided to reboot and select GNOME Classic rather than booting into the standard GNOME Shell and it seems to work fine - no screen tearing or X-freezes under fairly heavy use. So maybe nouveau itself is simply not capable of running GNOME Shell. I find that a bit odd as I'd assumed both use mutter but Tim could probably provide some insight in that regard. I should probably try that same kernel with Ubuntu in a Unity session to see what happens. ATM I'm inclined to think that kernel fixes this specific issue, but that other underlying issues exist in nouveau itself which may actually be an Xorg issue beyond the scope of this bug or is it??? -- 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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Accelerated Xorg driver for nVidia cards: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in xserver-xorg-video-nouveau source package in Trusty: New Status in linux source package in Utopic: Confirmed Status in xserver-xorg-video-nouveau source package in Utopic: New Status in linux source package in Vivid: Confirmed Status in xserver-xorg-video-nouveau source package in Vivid: New Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 19 17:41:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp Device [1565:1405] InstallationDate: Installed on 2015-01-19 (0 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c52e Logitech, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: BIOSTAR Group N68SB-M2S ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=acf0fd65-0d6d-4da6-9532-2adc558bc0a7 ro quiet splash init=/lib/systemd/systemd SourcePackage:
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
@ Joseph Salisbury, I'll be glad to do that but it'll be a couple of days due to prior commitments. -- 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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Accelerated Xorg driver for nVidia cards: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in xserver-xorg-video-nouveau source package in Trusty: New Status in linux source package in Utopic: Confirmed Status in xserver-xorg-video-nouveau source package in Utopic: New Status in linux source package in Vivid: Confirmed Status in xserver-xorg-video-nouveau source package in Vivid: New Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 19 17:41:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp Device [1565:1405] InstallationDate: Installed on 2015-01-19 (0 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c52e Logitech, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: BIOSTAR Group N68SB-M2S ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=acf0fd65-0d6d-4da6-9532-2adc558bc0a7 ro quiet splash init=/lib/systemd/systemd SourcePackage: xserver-xorg-video-nouveau UdevLog: UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 06/24/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: N68SB-M2S dmi.board.vendor: BIOSTAR Group dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: N68SB-M2S dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/24/2010:svnBIOSTARGroup:pnN68SB-M2S:pvr:rvnBIOSTARGroup:rnN68SB-M2S:rvr:cvnBIOSTARGroup:ct3:cvrN68SB-M2S: dmi.product.name: N68SB-M2S dmi.sys.vendor: BIOSTAR Group version.compiz: compiz
[Kernel-packages] [Bug 1410384] Re: linux: 3.13.0-45.74 -proposed tracker
This kernel results in bug #1412602 but I'm not tech savvy enough to parse the changelogs other than noticing a few mentions of MSI. -- 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/1410384 Title: linux: 3.13.0-45.74 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow package-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.13.0-45.74 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 13. January 2015 17:34 UTC kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 02:05 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 02:05 UTC ppa-package-testing-start:Wednesday, 14. January 2015 02:05 UTC kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 17:48 UTC kernel-stable-Verification-testing-start:Friday, 16. January 2015 19:01 UTC kernel-stable-Certification-testing-start:Friday, 16. January 2015 19:02 UTC kernel-stable-Security-signoff-start:Friday, 16. January 2015 19:02 UTC kernel-stable-Regression-testing-start:Friday, 16. January 2015 19:02 UTC kernel-stable-Verification-testing-end:Monday, 26. January 2015 19:35 UTC kernel-stable-Regression-testing-end:Monday, 26. January 2015 19:35 UTC kernel-stable-Certification-testing-end:Tuesday, 27. January 2015 07:01 UTC kernel-stable-Promote-to-updates-start:Wednesday, 28. January 2015 16:01 UTC kernel-stable-Security-signoff-end:Wednesday, 28. January 2015 16:01 UTC kernel-stable-Promote-to-updates-end:Friday, 30. January 2015 16:01 UTC kernel-stable-phase:Released kernel-stable-phase-changed:Friday, 30. January 2015 17:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1410384/+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 1220165] Re: Error informing the kernel about modificatons
I fell on my face performing this: https://wiki.ubuntu.com/DebuggingUbiquity#Deeper_debugging_of_partman I think I didn't quite know how to restart rsyslog :^( I'm tired now but maybe I'll try just using ubiquity -d tomorrow. Look, I'm no dev by any means, but I believe this bug is tagged wrong! It's much more likely a ubiquity bug than a kernel bug, and it is critical! Colin Watson would know how to properly assign this :^) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1220165 Title: Error informing the kernel about modificatons Status in “linux” package in Ubuntu: Confirmed Status in “linux-ppc” package in Ubuntu: Confirmed Bug description: When installing the desktop powerpc image, the installer comes up with an error message: Error informing the kernel about modifications to partitino /dev/sda3 - Device or resource busy. This means Linuxc won't know about any changes you made to /dev/sda3 until you reboot - so you shouldn't mount it or use it in any way before rebooting. I made no changes. The installer comes up with this error all on its own right before the Where are you? screen. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity 2.15.16 ProcVersionSignature: Ubuntu 3.11.0-1.2-powerpc-smp 3.11.0-rc7 Uname: Linux 3.11.0-1-powerpc-smp ppc ApportVersion: 2.12.1-0ubuntu3 Architecture: powerpc CasperVersion: 1.336 Date: Tue Sep 3 09:51:27 2013 InstallCmdLine: ro ramdisk_size=1048576 file=/cdrom/preseed/lubuntu.seed boot=casper quiet splash -- video=radeonfb:1280x854-32@60 LiveMediaBuild: Lubuntu 13.10 Saucy Salamander - Alpha powerpc (20130902.1) MarkForUpload: True SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1220165/+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 1220165] Re: Error informing the kernel about modificatons
@ Phil, while I'm sure there are other ways of reproducing this look at comment #15. I can reliably reproduce this in a *buntu dual boot time and time again. I'm suspicious of ubiquity-partman but that's just a guess. -- 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/1220165 Title: Error informing the kernel about modificatons Status in “linux” package in Ubuntu: Confirmed Status in “linux-ppc” package in Ubuntu: Confirmed Bug description: When installing the desktop powerpc image, the installer comes up with an error message: Error informing the kernel about modifications to partitino /dev/sda3 - Device or resource busy. This means Linuxc won't know about any changes you made to /dev/sda3 until you reboot - so you shouldn't mount it or use it in any way before rebooting. I made no changes. The installer comes up with this error all on its own right before the Where are you? screen. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity 2.15.16 ProcVersionSignature: Ubuntu 3.11.0-1.2-powerpc-smp 3.11.0-rc7 Uname: Linux 3.11.0-1-powerpc-smp ppc ApportVersion: 2.12.1-0ubuntu3 Architecture: powerpc CasperVersion: 1.336 Date: Tue Sep 3 09:51:27 2013 InstallCmdLine: ro ramdisk_size=1048576 file=/cdrom/preseed/lubuntu.seed boot=casper quiet splash -- video=radeonfb:1280x854-32@60 LiveMediaBuild: Lubuntu 13.10 Saucy Salamander - Alpha powerpc (20130902.1) MarkForUpload: True SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1220165/+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 1220165] Re: Error informing the kernel about modificatons
I'll see what I can do, but this bugs UbiquityPartman log shows: /lib/partman/commit.d/30parted: paragraph: Error informing the kernel about modifications to partition /dev/sda3 -- Device or resource busy. This means Linux won't know about any changes you made to /dev/sda3 until you reboot -- so you shouldn't mount it or use it in any way before rebooting. /lib/partman/commit.d/30parted: error_handler: reading options /lib/partman/commit.d/30parted: option: Ignore /lib/partman/commit.d/30parted: option: Cancel And my two duplicates show the same thing except the device designation is /dev/sda1. ** Tags added: ubi-partman -- 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/1220165 Title: Error informing the kernel about modificatons Status in “linux” package in Ubuntu: Confirmed Status in “linux-ppc” package in Ubuntu: Confirmed Bug description: When installing the desktop powerpc image, the installer comes up with an error message: Error informing the kernel about modifications to partitino /dev/sda3 - Device or resource busy. This means Linuxc won't know about any changes you made to /dev/sda3 until you reboot - so you shouldn't mount it or use it in any way before rebooting. I made no changes. The installer comes up with this error all on its own right before the Where are you? screen. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity 2.15.16 ProcVersionSignature: Ubuntu 3.11.0-1.2-powerpc-smp 3.11.0-rc7 Uname: Linux 3.11.0-1-powerpc-smp ppc ApportVersion: 2.12.1-0ubuntu3 Architecture: powerpc CasperVersion: 1.336 Date: Tue Sep 3 09:51:27 2013 InstallCmdLine: ro ramdisk_size=1048576 file=/cdrom/preseed/lubuntu.seed boot=casper quiet splash -- video=radeonfb:1280x854-32@60 LiveMediaBuild: Lubuntu 13.10 Saucy Salamander - Alpha powerpc (20130902.1) MarkForUpload: True SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1220165/+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 1229719] Re: Error Informing kernel about modifications to partition on saucy desktop installation on mac mini 5.1
Would you please see if this is a duplicate of bug #1220165 -- 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/1229719 Title: Error Informing kernel about modifications to partition on saucy desktop installation on mac mini 5.1 Status in “linux” package in Ubuntu: Confirmed Bug description: The following error occurred in a manual partitioning test of amd64+mac image of 20130923.2 on Mac mini 5.1 Error informing the kernel about modifications to partition /dev/sda2 -Device or resource busy. This means Linux wont know about changes you made to /dev/sda2 until you reboot- so you shouldn't mount it or use it any way before rebooting. The following is seen in dmesg [ 104.483873] EXT3-fs (sda1): error: can't find ext3 filesystem on dev sda1. [ 104.484261] EXT4-fs (sda1): VFS: Can't find ext4 filesystem [ 104.484705] FAT-fs (sda1): invalid media value (0x7d) [ 104.484712] FAT-fs (sda1): Can't find a valid FAT filesystem [ 104.496625] ISOFS: Unable to identify CD-ROM format. [ 104.497043] SQUASHFS error: Can't find a SQUASHFS superblock on sda1 [ 104.497420] EXT2-fs (sda1): error: can't find an ext2 filesystem on dev sda1. [ 104.499045] XFS (sda1): bad magic number [ 104.499055] 88006eb9c000: 52 e8 28 01 74 08 56 be 33 81 e8 4c 01 5e bf f4 R.(.t.V.3..L.^.. [ 104.499061] 88006eb9c010: 81 66 8b 2d 83 7d 08 00 0f 84 e9 00 80 7c ff 00 .f.-.}...|.. [ 104.499065] 88006eb9c020: 74 46 66 8b 1d 66 8b 4d 04 66 31 c0 b0 7f 39 45 tFf..f.M.f1...9E [ 104.499070] 88006eb9c030: 08 7f 03 8b 45 08 29 45 08 66 01 05 66 83 55 04 E.)E.f..f.U. [ 104.499076] XFS (sda1): Internal error xfs_sb_read_verify at line 780 of file /build/buildd/linux-3.11.0/fs/xfs/xfs_mount.c. Caller 0xa07f6b75 [ 104.499076] [ 104.499085] CPU: 0 PID: 5 Comm: kworker/0:0H Tainted: GF 3.11.0-8-generic #15-Ubuntu [ 104.499089] Hardware name: Apple Inc. Macmini5,1/Mac-8ED6AF5B48C039E1, BIOS MM51.88Z.0077.B0F.1110201309 10/20/2011 [ 104.499128] Workqueue: xfslogd xfs_buf_iodone_work [xfs] [ 104.499134] 0001 880071c4fd68 816f2f71 88006d16f000 [ 104.499142] 880071c4fd80 a07f925b a07f6b75 880071c4fdb8 [ 104.499149] a07f92b5 030c63006183 880070940c00 0016 [ 104.499156] Call Trace: [ 104.499170] [816f2f71] dump_stack+0x45/0x56 [ 104.499201] [a07f925b] xfs_error_report+0x3b/0x40 [xfs] [ 104.499230] [a07f6b75] ? xfs_buf_iodone_work+0x85/0xf0 [xfs] [ 104.499259] [a07f92b5] xfs_corruption_error+0x55/0x80 [xfs] [ 104.499307] [a084b413] xfs_sb_read_verify+0x113/0x130 [xfs] [ 104.499335] [a07f6b75] ? xfs_buf_iodone_work+0x85/0xf0 [xfs] [ 104.499363] [a07f6b75] xfs_buf_iodone_work+0x85/0xf0 [xfs] [ 104.499372] [8107cfbc] process_one_work+0x17c/0x430 [ 104.499379] [8107dc0c] worker_thread+0x11c/0x3c0 [ 104.499386] [8107daf0] ? manage_workers.isra.24+0x2a0/0x2a0 [ 104.499395] [81084710] kthread+0xc0/0xd0 [ 104.499404] [81084650] ? kthread_create_on_node+0x120/0x120 [ 104.499414] [81702d6c] ret_from_fork+0x7c/0xb0 [ 104.499422] [81084650] ? kthread_create_on_node+0x120/0x120 [ 104.499427] XFS (sda1): Corruption detected. Unmount and run xfs_repair [ 104.499453] XFS (sda1): SB validate failed with error 22. === Steps: 1. Start the installation 2. Go straight to 'Install Ubuntu' ( since live session installation is broken at them moment) 3. Select 'something else' in the Installation type menu to perform manual partitioning 4. Select Ext4 file system for /, /boot and /home partitions leaving adequate swap space 5. Click continue and the above errors will be reported ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-8-generic 3.11.0-8.15 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2695 F pulseaudio ubuntu19520 F pulseaudio CasperVersion: 1.336 Date: Tue Sep 24 13:21:17 2013 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Beta amd64+mac (20130923.2) MachineType: Apple Inc. Macmini5,1 MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
