Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
11-20-2015, 09:41 PM
|
#1
|
Member
Registered: Feb 2013
Posts: 58
Rep: 
|
X not starting
Hello forum,
for a few days now, my HTPC fails to start X.
It's a MythBuntu installation (roughly Ubuntu 12.04 LTS with XFCE and MythTV pre-installed). Maybe there has been an update the day before, but I didn't really pay attention.
The system boots to a console login but "startx" ends in an error message
Code:
xinit: giving up
xinit: unable to connect to X server: No such file or directory
xinit: server error
That's what /var/log/kern.log ends with
Code:
Nov 20 18:00:45 michael kernel: [ 14.018996] init: gdm main process (1408) killed by TERM signal
Nov 20 18:00:45 michael kernel: [ 14.025677] nvidia: module license 'NVIDIA' taints kernel.
Nov 20 18:00:45 michael kernel: [ 14.025681] Disabling lock debugging due to kernel taint
Nov 20 18:00:46 michael kernel: [ 14.445476] nvidia 0000:02:00.0: PCI INT A -> GSI 24 (level, low) -> IRQ 24
Nov 20 18:00:46 michael kernel: [ 14.445567] nvidia 0000:02:00.0: setting latency timer to 64
Nov 20 18:00:46 michael kernel: [ 14.445574] vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
Nov 20 18:00:46 michael kernel: [ 14.446409] NVRM: loading NVIDIA UNIX x86 Kernel Module 304.128 Wed Aug 26 10:41:50 PDT 2015
Nov 20 18:00:46 michael kernel: [ 14.449189] hda_codec: ALC888: BIOS auto-probing.
Nov 20 18:00:46 michael kernel: [ 14.458805] input: HDA VIA VT82xx Line as /devices/pci0000:80/0000:80:01.0/sound/card0/input5
Nov 20 18:00:46 michael kernel: [ 14.459280] input: HDA VIA VT82xx Mic as /devices/pci0000:80/0000:80:01.0/sound/card0/input6
Nov 20 18:00:46 michael kernel: [ 14.459733] input: HDA VIA VT82xx Line-Out Side as /devices/pci0000:80/0000:80:01.0/sound/card0/input7
Nov 20 18:00:46 michael kernel: [ 14.460392] input: HDA VIA VT82xx Line-Out CLFE as /devices/pci0000:80/0000:80:01.0/sound/card0/input8
Nov 20 18:00:46 michael kernel: [ 14.460770] input: HDA VIA VT82xx Line-Out Surround as /devices/pci0000:80/0000:80:01.0/sound/card0/input9
Nov 20 18:00:46 michael kernel: [ 14.461158] input: HDA VIA VT82xx Line-Out Front as /devices/pci0000:80/0000:80:01.0/sound/card0/input10
Nov 20 18:00:47 michael kernel: [ 15.710719] CIFS: Unknown mount option codepage
Nov 20 18:00:47 michael kernel: [ 15.710724] CIFS: Unknown mount option unicode
Nov 20 18:00:47 michael kernel: [ 15.791447] CIFS VFS: default security mechanism requested. The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3
Nov 20 18:00:47 michael kernel: [ 16.072825] NVRM: Xid (PCI:0000:02:00): 2, CCMDs 00000000 00000057 00000300 00000003 0000001c
Nov 20 18:00:47 michael kernel: [ 16.177623] NVRM: Xid (PCI:0000:02:00): 2, CCMDs 00000000 00000057 00000300 00000003 0000001c
Nov 20 18:00:48 michael kernel: [ 16.585064] init: lightdm main process (1375) terminated with status 1
Something seems wrong with the nvidia driver. I tried apt-get update, upgrade as well as dist-upgrade, but to no avail.
That's my xorg.conf
Code:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 304.116 (buildmeister@swio-display-x64-rhel04-04) Mon Oct 28 21:49:10 PDT 2013
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
Any ideas how to get the GUI up and running?
|
|
|
11-21-2015, 04:46 AM
|
#2
|
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 24,263
|
the usual practice is run lightdm by hand with -d and check the debug messages. Sometimes removing xorg.conf may help
|
|
|
11-21-2015, 05:30 AM
|
#3
|
LQ Sage
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675
Rep: 
|
Code:
Section "Device"
Identifier "Device0"
Driver "nvidia"
EndSection
Generating xorg.conf is an old habit, it is not needed as pan64 said. However, to load the binary driver a four-line xorg.conf is needed.
|
|
|
11-21-2015, 09:10 AM
|
#4
|
Member
Registered: Feb 2013
Posts: 58
Original Poster
Rep: 
|
possible version incompatibilities
The kernel version is 3.2.0-94-generic i686. Following friend's hint, I selected an earlier version in GRUB: 3.2.0-92-generic i686. And indeed, X started. But it's only 800x600 and the Display setting doesn't allow higher values.
$lspci -k
02:00.0 VGA compatible controller: NVIDIA Corporation NV43 [GeForce 6600] (rev a2)
Subsystem: ASUSTeK Computer Inc. EN6600 Silencer
Kernel modules: nouveau, nvidiafb
None of the modules is mentioned in
$lsmod
For me, it looks like the nvidia driver doesn't work with the new kernel. Can I get it to?
Keeping the old kernel until a newer one fixes this issue would still leave me at 800x600. How could I change that?
|
|
|
11-21-2015, 10:45 AM
|
#5
|
LQ Sage
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675
Rep: 
|
The proprietary nVidia driver will not load if nouveau is loaded. To make it load nouveau has to be blacklisted or disabled in kernel configuration.
|
|
|
11-21-2015, 10:52 AM
|
#6
|
LQ Veteran
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,843
|
might have to reinstall the nvidia driver for it to work with the current kernel.
|
|
|
11-21-2015, 11:38 AM
|
#7
|
Member
Registered: Feb 2013
Posts: 58
Original Poster
Rep: 
|
Quote:
Originally Posted by colorpurple21859
reinstall the nvidia driver
|
Would that mean
$apt-get purge nvidia-current && apt-get install nvidia-current ?
|
|
|
11-21-2015, 11:41 AM
|
#8
|
Member
Registered: Feb 2013
Posts: 58
Original Poster
Rep: 
|
Quote:
Originally Posted by Emerson
nouveau has to be blacklisted or disabled in kernel configuration.
|
And how do I do that?
Is there a configuration file that's processed on boot?
Or does it mean configuring and compiling a custom kernel?
|
|
|
11-21-2015, 12:47 PM
|
#9
|
Member
Registered: Oct 2013
Location: IN, USA
Distribution: Arch, Debian Jessie
Posts: 814
|
Quote:
Originally Posted by lukeer
And how do I do that?
Is there a configuration file that's processed on boot?
Or does it mean configuring and compiling a custom kernel?
|
On my Debian system, you just add it to /etc/modprobe.d/blacklist:
It should be in the same place on Ubuntu, but I can't personally confirm that.
|
|
|
11-21-2015, 01:37 PM
|
#10
|
Senior Member
Registered: Nov 2003
Location: Minnesota, US
Distribution: Fedora, Ubuntu, Manjaro
Posts: 1,792
|
Regarding blacklisting the nouveau driver, Ubuntu has a number of blacklist files in /etc/modprobe.d. I'd add the line to blacklist.conf (preceded by a comment reminding you of what you did) and run update-grub.
|
|
|
All times are GMT -5. The time now is 04:06 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|