[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
there has been no progress on this issue, it's the same in ubuntu 21.04. the behavior described in #15 is especially annoying since closing the lid by mistake (while eg carrying it around) and opening it immediately does not cancel the suspend, it comes 30s later no matter what one is currently doing. -- 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/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+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 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
there has been no progress on this issue, it's the same in ubuntu 21.04. the behavior described in #15 is especially annoying since closing the lid by mistake (while eg carrying it around) and opening it immediately does not cancel the suspend, it comes 30s later no matter what one is currently doing. -- 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/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+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 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
interesting observation: if i close the lid for, say, 1 sec, and then open it again, after similar time delay as observed in the previous comment, my thinkpad goes into suspend although i am working in my desktop (obviously with the lid open). the lid close seems to trigger the suspend which comes 30 seconds later, no matter what... -- 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/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+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 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
similar thing happens with my lenovo thinkpad x1 carbon gen5. the time it takes for suspend is excrutiationgly long. it used to be a couple of seconds, at most, now the wait for the red led on top of "i" in ThinkPad logo seems to be taking for ages to start blinking. the output of the loop (suggested by @arighi above) while true ; do echo $(date) $(cat /proc/acpi/button/lid/LID/state) ; done gives the following: Thu 11 Jun 2020 09:36:44 AM CEST state: open Thu 11 Jun 2020 09:36:45 AM CEST state: open Thu 11 Jun 2020 09:36:46 AM CEST state: open <-- close lid Thu 11 Jun 2020 09:36:47 AM CEST state: open Thu 11 Jun 2020 09:36:48 AM CEST state: open Thu 11 Jun 2020 09:36:49 AM CEST state: closed Thu 11 Jun 2020 09:36:50 AM CEST state: closed Thu 11 Jun 2020 09:36:51 AM CEST state: closed Thu 11 Jun 2020 09:36:52 AM CEST state: closed Thu 11 Jun 2020 09:36:53 AM CEST state: closed Thu 11 Jun 2020 09:36:54 AM CEST state: closed Thu 11 Jun 2020 09:36:55 AM CEST state: closed Thu 11 Jun 2020 09:36:56 AM CEST state: closed Thu 11 Jun 2020 09:36:57 AM CEST state: closed Thu 11 Jun 2020 09:36:58 AM CEST state: closed Thu 11 Jun 2020 09:36:59 AM CEST state: closed Thu 11 Jun 2020 09:37:00 AM CEST state: closed Thu 11 Jun 2020 09:37:01 AM CEST state: closed Thu 11 Jun 2020 09:37:02 AM CEST state: closed Thu 11 Jun 2020 09:37:03 AM CEST state: closed Thu 11 Jun 2020 09:37:04 AM CEST state: closed Thu 11 Jun 2020 09:37:05 AM CEST state: closed Thu 11 Jun 2020 09:37:06 AM CEST state: closed Thu 11 Jun 2020 09:37:07 AM CEST state: closed Thu 11 Jun 2020 09:37:08 AM CEST state: closed Thu 11 Jun 2020 09:37:09 AM CEST state: closed Thu 11 Jun 2020 09:37:10 AM CEST state: closed Thu 11 Jun 2020 09:37:11 AM CEST state: closed Thu 11 Jun 2020 09:37:12 AM CEST state: closed Thu 11 Jun 2020 09:37:13 AM CEST state: closed Thu 11 Jun 2020 09:37:14 AM CEST state: closed Thu 11 Jun 2020 09:37:15 AM CEST state: closed Thu 11 Jun 2020 09:37:16 AM CEST state: closed Thu 11 Jun 2020 09:37:17 AM CEST state: closed Thu 11 Jun 2020 09:37:18 AM CEST state: closed 19 <-- power led starts blinking 20 21 22 23 24 25 26 27 28 <-- open lid 29 Thu 11 Jun 2020 09:37:30 AM CEST state: open Thu 11 Jun 2020 09:37:31 AM CEST state: open Thu 11 Jun 2020 09:37:35 AM CEST state: open <-- ctrl-c while-loop -- 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/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+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 1874639] [NEW] desktop pcs start to suspend by default
Public bug reported: after the kernel upgrade our office desktops started to suspend after inactivity and with users logged out. this is rather unacceptable since we also use the pcs to run computational jobs. i tried to prevent the suspension via systemctl but the sleep.target, suspend.target, hibernate.target, and hybrid-sleep.target don't exist anyway... how to prevent this from happening? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: darko 5370 F pulseaudio /dev/snd/controlC1: darko 5370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Apr 24 09:46:28 2020 HibernationDevice: RESUME=UUID=df0ed1aa-a505-4fea-b591-fea4ead4d128 InstallationDate: Installed on 2018-01-29 (815 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: FUJITSU ESPRIMO P920 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=13ac4fba-9660-442d-9cb0-424b30c82d4d ro pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-21 (3 days ago) dmi.bios.date: 10/23/2014 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.4 R1.30.0 for D3222-A1x dmi.board.name: D3222-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3222-A1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$WX02 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.30.0forD3222-A1x:bd10/23/2014:svnFUJITSU:pnESPRIMOP920:pvr:rvnFUJITSU:rnD3222-A1:rvrS26361-D3222-A1:cvnFUJITSU:ct6:cvrC$WX02: dmi.product.name: ESPRIMO P920 dmi.product.sku: S26361-Kxxx-Vyyy dmi.sys.vendor: FUJITSU ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- 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/1874639 Title: desktop pcs start to suspend by default Status in linux package in Ubuntu: Confirmed Bug description: after the kernel upgrade our office desktops started to suspend after inactivity and with users logged out. this is rather unacceptable since we also use the pcs to run computational jobs. i tried to prevent the suspension via systemctl but the sleep.target, suspend.target, hibernate.target, and hybrid-sleep.target don't exist anyway... how to prevent this from happening? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: darko 5370 F pulseaudio /dev/snd/controlC1: darko 5370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Apr 24 09:46:28 2020 HibernationDevice: RESUME=UUID=df0ed1aa-a505-4fea-b591-fea4ead4d128 InstallationDate: Installed on 2018-01-29 (815 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: FUJITSU ESPRIMO P920 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=13ac4fba-9660-442d-9cb0-424b30c82d4d ro pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-21 (3 days ago) dmi.bios.date: 10/23/2014 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.4 R1.30.0 for D3222-A1x dmi.board.name: D3222-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3222-A1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$WX02 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.30.0forD3222-A1x:bd10/23/2014:svnFUJITSU:pnESPRIMOP920:pvr:rvnFUJITSU:rnD3222-A1:rvrS26361-D3222-A1:cvnFUJITSU:ct6:cvrC$WX02: dmi.product.name: ESPRIMO P920 dmi.product.sku: S26361-Kxxx-Vyyy dmi.sys.vendor: FUJITSU To manage notifications about
[Kernel-packages] [Bug 1789258] Re: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out
confirmed also on lenovo thinkpad r61 with ubuntu 16.04.5 lts -- 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/1789258 Title: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out Status in linux package in Ubuntu: Confirmed Bug description: every now an then the system freezes but eventually comes back to life. the boot process is especially slow, login greeter takes ages to come up and then, while there, needs some extra time to unfreeze and actually allow typing in the password. the freeze can be easily reproduced each time when switching from graphics to console (with ctrl-alt-fN) and back. each time the dmesg gets also gets appended with the error messages that can be found in the attached text file. is the workaround really to uninstall intel's xorg drivers? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libdrm-intel1 2.4.91-2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Aug 27 20:03:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (primary) [17aa:383e] Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (secondary) [17aa:383e] InstallationDate: Installed on 2018-08-24 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 0769BJG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=5c1b96ff-002e-4358-bf56-8dd74e76584d ro dis_ucode_ldr SourcePackage: libdrm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET37WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769BJG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 0769BJG dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789258/+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 1789258] Re: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out
could be a duplicate of bug #1685442 -- 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/1789258 Title: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out Status in linux package in Ubuntu: Confirmed Bug description: every now an then the system freezes but eventually comes back to life. the boot process is especially slow, login greeter takes ages to come up and then, while there, needs some extra time to unfreeze and actually allow typing in the password. the freeze can be easily reproduced each time when switching from graphics to console (with ctrl-alt-fN) and back. each time the dmesg gets also gets appended with the error messages that can be found in the attached text file. is the workaround really to uninstall intel's xorg drivers? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libdrm-intel1 2.4.91-2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Aug 27 20:03:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (primary) [17aa:383e] Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (secondary) [17aa:383e] InstallationDate: Installed on 2018-08-24 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 0769BJG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=5c1b96ff-002e-4358-bf56-8dd74e76584d ro dis_ucode_ldr SourcePackage: libdrm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET37WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769BJG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 0769BJG dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789258/+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 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
Affects also Lenovo Thinkpad R61 with Ubuntu 16.04.5 LTS. -- 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/1685442 Title: Errors: flip_done timed out during boot-up; slow boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I had been running Ubuntu 16.04 LTS on many laptop computers (especially Dell D620, D630, E6400) with no problem. I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell D630. It was very slow to boot up (about 90 seconds) as opposed to the 30-45 seconds it usually takes. For a few seconds there were error messages that included the phrase "flip_done timed out". When the Ubuntu desktop appeared, the mouse cursor hung for a while, but then came back to life. I didn't do much testing from there. I did a Live session with the 16.04.2 LTS on a different D630 laptop, and the same problem occureed. I Googled the problem, and found several hits. - On an Arch forum, someone reported the problem on a Dell D630, like mine. It also occured on other laptops: https://bbs.archlinux.org/viewtopic.php?id=218581 The suggestion was that the bug was related to kernel version 4.8.x and the 965GM chipset, which is what the D630 has. So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the problem DID NOT occur. --- For a similar boot-up problem, Ubuntu Forum suggested going back to an earlier version of Ubuntu. https://ubuntuforums.org/showthread.php?t=2348892 I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and the problem did NOT occur. So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather than 16.04.2. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware
[Kernel-packages] [Bug 1547599] [NEW] legacy nvidia drivers fail to work with latest kernel
Public bug reported: i have a MacBookPro3,1 with a NVIDIA Corporation G84M [GeForce 8600M GT] (rev a1) video card. while in ubuntu 15.10 everything worked fine, after the upgrade in 16.04 the legacy nvidia-304 drivers do not. the X11 fails to start, the relevant lines in the /var/log/Xorg.0.log file are [ 3021.745] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please [ 3021.745] (EE) NVIDIA(0): check your system's kernel log for additional error [ 3021.745] (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the [ 3021.745] (EE) NVIDIA(0): README for additional information. [ 3021.745] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device! [ 3021.745] (EE) NVIDIA(0): Failing initialization of X screen 0 [ 3021.745] (II) UnloadModule: "nvidia" and the journalctl --dmesg gives kernel: NVRM: failed to copy vbios to system memory. kernel: NVRM: RmInitAdapter failed! (0x30:0x:867) kernel: NVRM: rm_init_adapter(0) failed nevertheless, the nvidia kernel module is loaded without a problem. i also tried more recent versions of nvidia-X but without success. they either fail with the same messages as above or they do not support the video card. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-6-generic 4.4.0-6.21 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country AW: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS Date: Fri Feb 19 18:05:07 2016 HibernationDevice: RESUME=UUID=484d04a2-0891-47bb-b890-ee3ab0189ef7 InstallationDate: Installed on 2016-02-17 (2 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Apple Inc. MacBookPro3,1 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic.efi.signed root=UUID=fddff8cb-9428-47b7-a215-034c4b79c0fe ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-6-generic N/A linux-backports-modules-4.4.0-6-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-17 (1 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8: dmi.product.name: MacBookPro3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1547599 Title: legacy nvidia drivers fail to work with latest kernel Status in linux package in Ubuntu: New Bug description: i have a MacBookPro3,1 with a NVIDIA Corporation G84M [GeForce 8600M GT] (rev a1) video card. while in ubuntu 15.10 everything worked fine, after the upgrade in 16.04 the legacy nvidia-304 drivers do not. the X11 fails to start, the relevant lines in the /var/log/Xorg.0.log file are [ 3021.745] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please [ 3021.745] (EE) NVIDIA(0): check your system's kernel log for additional error [ 3021.745] (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the [ 3021.745] (EE) NVIDIA(0): README for additional information. [ 3021.745] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device! [ 3021.745] (EE) NVIDIA(0): Failing initialization of X screen 0 [ 3021.745] (II) UnloadModule: "nvidia" and the journalctl --dmesg gives kernel: NVRM: failed to copy vbios to system memory. kernel: NVRM: RmInitAdapter failed! (0x30:0x:867) kernel: NVRM: rm_init_adapter(0) failed nevertheless, the nvidia kernel module is loaded without a problem. i also tried more recent versions of nvidia-X but without success. they either fail with the same
