Nvidia won't select 14.04 LTS

Bug #1311523 reported by Georgio Mosqueda
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-settings (Ubuntu)
New
Undecided
Unassigned

Bug Description

Prologue: I did a fresh install of 14.04 and the install was pretty rough with artifacts all over hdmi and needing to mouse over everything in order to reveal an updated image. Kind of like scratching off gift cards or lotto tickets, but with a screen. After a day or so everything seemed to work alright save for needing to ~$ kill -15 -1 twice in order to use the trackpad and mouse properly. After working fairly well like this (so long as I didn't reboot) for a week, I can't seem to get nvidia working properly today.

What I expected to happen: I typically work from my laptop ( m11x R3 ) during the day and hook it up to an external monitor via hdmi at home. To conserve battery, I use $ sudo tlp bat and use intel on the go. At home I log in, select nvidia, plug in via hdmi & everything runs smoothly.

What actually happened: Today I come home and hdmi won't work, m11x got really hot, and hard drive filled up with 8ish GB each kernlog plus syslog. I deleted kernlog to free up space and reboot in order to open chrome. The following was looped in syslog:
"""
Apr 22 19:27:45 gb9Box kernel: [ 48.032709] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L1B] (20131115/evgpe-580)
Apr 22 19:27:45 gb9Box kernel: [ 48.032759] ACPI Error: [\_SB_.PCI0.PEG0.PEGP.DPLF] Namespace lookup failure, AE_NOT_FOUND (20131115/psargs-359)
Apr 22 19:27:45 gb9Box kernel: [ 48.032780] ACPI Error: Method parse/execution failed [\_GPE._L1B] (Node ffff8801d68cd0f0), AE_NOT_FOUND (20131115/psparse-536)
"""
Please accept this peace offering of supplementary information and dmesg attachment. In return, I'll help out anyway I can at night:

The BIOS installed is the one recommended from Dell; SMBIOS 2.7

Ubuntu 14.04 LTS
~$ sudo prime-select nvidia
Error: alternatives are not set up properly
Error: nvidia mode can't be enabled

nvidia-settings:
  Installed: 331.20-0ubuntu8
  Candidate: 331.20-0ubuntu8
  Version table:
 *** 331.20-0ubuntu8 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

ubuntu-drivers-common Version: 1:0.2.91.4
nvidia-prime Version: 0.6.2

~$ dkms status
bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-settings 331.20-0ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 23 00:37:18 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nvidia-settings
InstallationDate: Installed on 2014-04-18 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-settings
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Georgio Mosqueda (georgio-n) wrote :
Revision history for this message
Georgio Mosqueda (georgio-n) wrote :

So I'm out and about today, and rebooting while disconnected from power is allowing me to select the nvidia card again. When I get home tonight, I'll update if the external monitor over HDMI works again. If anyone can shed some light on why this is happening, especially the bit about /var/log filling up like it did be greatly appreciated.

Revision history for this message
Georgio Mosqueda (georgio-n) wrote :

Looks like rebooting while connected to power will not allow the GPU to work. No matter if the GPU is connected to the monitor over hdmi and working fine before rebooting.

So the jury-rigged fix for now:

1. Unplug from power
2. Reboot and log-in
3. ~$ sudo prime-select nvidia
4. Plug in HDMI (verify in settings the monitor is detected)
5. **Now** plug in power

I wonder if this is an issue with nvidia-settings, prime-select, or an acpi thing? Anywho, I hope this helps some folks out until the issue is resolved.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.