You are not logged in.
Hi,
I am on a 32b updated Arch/KDE 4.3.2 system (with an old Nvidia card) which has been working perfectly till yesterday.
After performing (as root from non graphical terminal) a full system upgrade (pacman -Syu) this morning, X/KDE won't start anymore (even after reboot).
The last X log file shows that the problem is failure to load the /usr/lib/xorg/modules/drivers/nvidia_drv.so file.
However, I've verified that such a file exits there (along with nv_drv.so and vesa_drv.so files).
The pacman log of that last upgrade (which consisted of nearly 60 files) did NOT report any problem, and among others included the following upgrades:
a. xorg server 1.6.3.901 --> 1.7.1-1
b. xf86-video-nv 2.1.14-1 ---> 2.1.15-1
c. mesa 7.5.1.2 ---> 7.6-2
Pacman did NOT upgrade any nvidia driver
Please advise !
Best regards,
Michael Badt
Last edited by mibadt (2009-11-01 08:01:44)
Best regards,
Michael Badt
Offline
There's already a number of threads on this. Anyway:
Offline
The "legacy" Nvidia driver doesn't work with the new Xorg. Either wait it out, or try nouveau.
Offline
Thanks all!
Switching back to the nv driver indeed solved the problem.
By the way, if there is a better / more elegant way to do it, I'd be happy to learn.
The way I did it, considering that xorg.conf is recreated by HAL during every boot is as follows.
a. Modified my xorg.conf to nv and renamed as xorg.conf.nv
b. Added a "cp xorg.conf.nv xorg.conf" to my rc.local file.
Thanks
Best regards,
Michael Badt
Offline
Thanks all!
Switching back to the nv driver indeed solved the problem.
By the way, if there is a better / more elegant way to do it, I'd be happy to learn.
Try the nouveau driver. It has much better 2D acceleration support than nv, and supports KMS.
The way I did it, considering that xorg.conf is recreated by HAL during every boot is as follows.
a. Modified my xorg.conf to nv and renamed as xorg.conf.nv
b. Added a "cp xorg.conf.nv xorg.conf" to my rc.local file.Thanks
Really? How did you get HAL to do that?
Offline
How peachy! Why the &*()%^&^ would you guys release an upgrade that breaks this?
Offline
Well I tried to use the nouveau drive, but It messes up my screen resolution. It looks like pixely strips of my screen at a bad resolution. What is going wrong? All I did was switch xorg to nouveau instead of nvidia, and install said nouveau driver. Help?
Offline
Well I tried to use the nouveau drive, but It messes up my screen resolution. It looks like pixely strips of my screen at a bad resolution. What is going wrong? All I did was switch xorg to nouveau instead of nvidia, and install said nouveau driver. Help?
Try to enable KMS if you haven't already done so. If that doesn't fix it, post your xorg.conf and the contents of /var/log/Xorg.0.log.
Offline
Home PC with ati catalyst drivers - xorg updated and freeze at starting X (solved by reverting to previous version of xorrg)
Work laptop with intel integrated - xorg updated and freze at starting X (EDIT: solved by enabling KMS)
Am I missing something here?
Last edited by alecmg (2009-11-02 13:49:59)
Xyne wrote:
"We've got Pacman. Wacka wacka, bitches!"
Offline
Forgive me for my ignorance. I'm running on a terminal browser which I am not fluent in so it makes it difficult to find concise imformation. How do you enable KMS? Also, I have attempted to use the NV driver, but my card is not recognized (Nvidia Geforce 7150M) So it does not find a device when I start X.
Offline
Forgive me for my ignorance. I'm running on a terminal browser which I am not fluent in so it makes it difficult to find concise imformation. How do you enable KMS? Also, I have attempted to use the NV driver, but my card is not recognized (Nvidia Geforce 7150M) So it does not find a device when I start X.
http://wiki.archlinux.org/index.php/Nouveau#KMS
In short, add "options nouveau modeset=1" to /etc/modprobe.d/modprobe.conf and either "rmmod nouveau && modprobe nouveau" or reboot.
Offline
I get the error:
(EE) [drm] drmOpen failed
(EE) NOUVEAU(0) error opening the drm
any suggestions?
Offline
What's the output of "dmesg | grep drm"?
Offline
Here is the output of thy command:
[drm] Initialized drm 1.1.0 20060810
xorg.conf at pastebin.com/f3edfe847
Last edited by semperfiguy (2009-11-02 20:50:53)
Offline
How peachy! Why the &*()%^&^ would you guys release an upgrade that breaks this?
'you guys' ? You mean why would nVidia release closed binary blobs that cannot be hacked up or patched?
Offline
Here is the output of thy command:
[drm] Initialized drm 1.1.0 20060810xorg.conf at pastebin.com/f3edfe847
According to that command, KMS is not in use. Do you have nouveau-drm installed and "options nouveau modeset=1" in your /etc/modprobe.d/modprobe.conf? What's the output of "cat /proc/fb"?
Also, that xorg.conf is using some nVidia-blob-specific options. I'd go with:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
EndSection
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "True"
EndSection
Section "Device"
Identifier "Card0"
Driver "nouveau"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
EndSection
Offline
From another thread on the same topic - but relevant here too:
Try adding the following to your xorg.conf and updating to the latest nvidia drivers (190.42).
Section "ServerFlags"
Option "IgnoreABI" "on"
EndSection
Last edited by sultanoswing (2009-11-03 15:39:06)
6.5.3.arch1-1(x86_64) w/Gnome 44.4
Arch on: ASUS Pro-PRIME x470, AMD 5800X3D, AMD 6800XT, 32GB, | Intel NUC 7i5RYK | ASUS ux303ua | Surface Laptop
Offline