[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Unfortunately the steps in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/89 aren't working for me (I'm a professional developer, am confident i've followed the steps properly, have tried three times) Does anyone else have any other workarounds? -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320 * Test source code: https://github.com/os369510/grub2/tree/lp1842320 * If you built
[Kernel-packages] [Bug 1553503] Re: multi monitors - black flashes or black screen when the mouse cursor leaves a monitor
Ah, sorry if that's dragged the bug off topic. Although, while we're talking about it, I had a dual screen not working issue with an Nvidia card (with Nouveau or Nvidia drivers). When i connected i experienced a near identical stack trace to the one in this ticket. Installing 4.8-rc1 this morning has given me dual screen! It's a happy day indeed. I can't use the Nvidia drivers because i don't think there's any extras packages (not entirely sure how that works) but luckily Nouveau now does the job. I've got some pointer ghosting and replicating-type problems but those are very much live-with-able I've been chasing this bug for months, and been thinking it was an Nvidia driver problem, so i was really happy to come across some of the info in this ticket, thanks also for your tips around installing 4.8-rc1 as well @Joseph Salisbury -- 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/1553503 Title: multi monitors - black flashes or black screen when the mouse cursor leaves a monitor Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When the mouse cursor leaves one of the screens, there is either : - no problem - the screen becomes black just below the position of the cursor and instantly comes back to normal. - the screen becomes entirely black with some random colored pixels flickering on the far left of the screen. I have to move the cursor to the black screen, otherwise it stays black. It happens on Ubuntu Gnome 16.04 Beta and Ubuntu Mate 16.04 Beta. I have tested with other distributions (Debian Jessie and Fedora) and everything is fine. Hardware : Intel Ironlake (Thinkpad X201) with an external monitor plugged in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CasperVersion: 1.367 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Mar 5 13:17:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) MachineType: LENOVO 3680KD3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET70WW (1.40 ) dmi.board.name: 3680KD3 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3680KD3:pvrThinkPadX201:rvnLENOVO:rn3680KD3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3680KD3 dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Sat Mar 5 13:03:55 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id2202 vendor BOE xserver.version: 2:1.17.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1553503/+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 1553503] Re: multi monitors - black flashes or black screen when the mouse cursor leaves a monitor
This also affects me on Xenial, completely breaks my dual screen setup - i'd love a fix for https://bugs.freedesktop.org/show_bug.cgi?id=89055#c62 ** Tags added: kernel-da-key -- 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/1553503 Title: multi monitors - black flashes or black screen when the mouse cursor leaves a monitor Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When the mouse cursor leaves one of the screens, there is either : - no problem - the screen becomes black just below the position of the cursor and instantly comes back to normal. - the screen becomes entirely black with some random colored pixels flickering on the far left of the screen. I have to move the cursor to the black screen, otherwise it stays black. It happens on Ubuntu Gnome 16.04 Beta and Ubuntu Mate 16.04 Beta. I have tested with other distributions (Debian Jessie and Fedora) and everything is fine. Hardware : Intel Ironlake (Thinkpad X201) with an external monitor plugged in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CasperVersion: 1.367 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Mar 5 13:17:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) MachineType: LENOVO 3680KD3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET70WW (1.40 ) dmi.board.name: 3680KD3 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3680KD3:pvrThinkPadX201:rvnLENOVO:rn3680KD3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3680KD3 dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Sat Mar 5 13:03:55 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id2202 vendor BOE xserver.version: 2:1.17.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553503/+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 1567417] Re: WARN_ON(!wm_changed) skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]
4.8 sounds a long way away, is there a way i can get this on Xenial now to get my dual screen setup working? A PPA or something? -- 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/1567417 Title: WARN_ON(!wm_changed) skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo] Status in linux package in Ubuntu: Confirmed Bug description: Hi, I'm using a new Skylake Thinkpad T460s with and external monitor connected via Displayport and Ubuntu 16.04 and the latest kernel as of today: Linux test 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:17:28 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux X will from time to time lock up when the computer is left idle for a long time and both displays (laptop and external) go to sleep and then woken up. Apr 7 08:00:49 test kernel: [9.950929] [ cut here ] Apr 7 08:00:49 test kernel: [9.950950] WARNING: CPU: 0 PID: 214 at /build/linux-YiIlnA/linux-4.4.0/ubuntu/i915/intel_pm.c:3572 skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]() Apr 7 08:00:49 test kernel: [9.950951] WARN_ON(!wm_changed) Apr 7 08:00:49 test kernel: [9.950972] Modules linked in: btusb btrtl btbcm btintel bluetooth binfmt_misc nls_iso8859_1 arc4 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm thinkpad_acpi intel_rapl x86_pkg_temp_thermal nvram intel_powerclamp snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi iwlmvm snd_seq joydev snd_seq_device input_leds mac80211 snd_timer serio_raw snd rtsx_pci_ms memstick soundcore iwlwifi cfg80211 mei_me mei tpm_crb mac_hid shpchp kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg hid_microsoft dm_crypt hid_generic usbhid hid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul i915_bpo aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd intel_ips i2c_algo_bit drm_kms_helper e1000e syscop yarea sysfillrect psmouse sysimgblt ptp fb_sys_fops pps_core drm nvme rtsx_pci wmi video fjes Apr 7 08:00:49 test kernel: [9.950980] CPU: 0 PID: 214 Comm: plymouthd Not tainted 4.4.0-17-generic #33-Ubuntu Apr 7 08:00:49 test kernel: [9.950981] Hardware name: LENOVO 20F9CTO1WW/20F9CTO1WW, BIOS N1CET40W (1.08 ) 03/09/2016 Apr 7 08:00:49 test kernel: [9.950982] 0286 39cb6999 880502bc3618 813e8123 Apr 7 08:00:49 test kernel: [9.950983] 880502bc3660 c0343c70 880502bc3650 8107fe12 Apr 7 08:00:49 test kernel: [9.950984] 880502da8000 880501f79d9c 880502dab000 880508186b78 Apr 7 08:00:49 test kernel: [9.950984] Call Trace: Apr 7 08:00:49 test kernel: [9.950988] [] dump_stack+0x63/0x90 Apr 7 08:00:49 test kernel: [9.950990] [] warn_slowpath_common+0x82/0xc0 Apr 7 08:00:49 test kernel: [9.950991] [] warn_slowpath_fmt+0x5c/0x80 Apr 7 08:00:49 test kernel: [9.951002] [] skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951010] [] skl_update_wm+0x186/0x5f0 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951023] [] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951034] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951048] [] haswell_crtc_enable+0x321/0x8c0 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951061] [] ? intel_finish_crtc_commit+0xe/0x10 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951072] [] ? drm_atomic_helper_commit_planes_on_crtc+0x154/0x270 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951085] [] intel_atomic_commit+0x5dd/0xdb0 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951101] [] ? drm_atomic_check_only+0x18e/0x590 [drm] Apr 7 08:00:49 test kernel: [9.951109] [] drm_atomic_commit+0x37/0x60 [drm] Apr 7 08:00:49 test kernel: [9.951113] [] restore_fbdev_mode+0x22f/0x260 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951121] [] ? drm_modeset_lock_all_ctx+0x9a/0xb0 [drm] Apr 7 08:00:49 test kernel: [9.951125] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951128] [] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951131] [] drm_fb_helper_hotplug_event+0xd2/0x120 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951134] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x56/0x80 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951136] [] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951150] [] intel_fbdev_set_par+0x1a/0x60 [i915_bpo]
[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
timkofu, would you mind telling us about your system? I haven't had success with those drivers, i still just get flickering and then an eventual X crash when trying to connect an external screen to my XPS -- 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/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: Confirmed Status in Ubuntu GNOME: Triaged Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+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 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
Noticed a 367 update today, this problem still persists -- 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/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: Confirmed Status in Ubuntu GNOME: Triaged Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+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 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
Actually looking at what nvidia-367 does it adds its own nouveau blacklist, so if you have these packages you probably already have one in there. Which I guess is why all the "manual reset from the TTY" guides make sure you do a full purge of nvidia-* before attempting to reboot into nouveau -- 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/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: Confirmed Status in Ubuntu GNOME: Triaged Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+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 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
After removing nvidia-364 and installing nvidia-367(.18) from a TTY before rebooting I still cannot get my external monitor to work. When I connect it via HDMI it flickers a lot and unless I unplug the HDMI after the first couple of flickers goes completely black. ubuntu gnome 16.04 Kernel: 4.4.0-22-generic nvidia driver: 367.18 installed from ppa:graphics-drivers/ppa my gpu is: GM107M [GeForce GTX 960M] running on: Dell XPS 15 (9550) Happy to try and help anyone debug, catch me on IRC - ph8 -- 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/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: Confirmed Status in Ubuntu GNOME: Triaged Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+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