Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#23754 - xorg-server 1.10.0.902-1 crashing with nvidia-173xx 173.14.28-5

Attached to Project: Arch Linux
Opened by Dominik Köppl (dominikk) - Wednesday, 13 April 2011, 17:07 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 13 April 2011, 22:27 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I've recently updated my xserver.
After update, it is always crashing with
0: X (xorg_backtrace+0x26) [0x45d396]
1: X (0x400000+0x617b9) [0x4617b9]
2: /lib/libpthread.so.0 (0x7fbecc0fb000+0xf150) [0x7fbecc10a150]
3: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbec7c29000+0x4d4a54) [0x7fbec80fda54]
Segmentation fault at address 0x18

I'm using extra/xorg-server 1.10.0.902-1 and extra/nvidia-173xx 173.14.28-5.
The computer is running with a Nvidia GeForce 8400 GS.
According to the output of /var/log/Xorg.1.log, my nvidia-driver seems outdated.

Removing the file /etc/X11/xorg.conf.d/20-nvidia.conf cures the problem by switching from the nividia-driver to extra/xf86-video-vesa 2.3.0-5.
The vesa-driver cannot handle twinview. Thus this configuration results in a disabled second monitor.

Attachment:
Xorg.1.log :: Xorg crashing while using nvidia-driver
Xorg.0.log :: Xorg starting with vesa-driver
This task depends upon

Closed by  Eric Belanger (Snowman)
Wednesday, 13 April 2011, 22:27 GMT
Reason for closing:  Not a bug
Comment by Ionut Biru (wonder) - Wednesday, 13 April 2011, 17:21 GMT
with that card you shouldn't use nvidia-173xx.

nvidia is the right driver for that
Comment by Dominik Köppl (dominikk) - Wednesday, 13 April 2011, 17:21 GMT
Switching to extra/nvidia 270.41.03-1 resolves the problem.

Loading...