[arch-general] Xorg broken after last update
Hello. The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything. I'm using X86_64, *without* [testing]. The updated packages were kernel26 nvidia xorg-server (and some others, less important) If I change the driver in xorg.conf from nvidia to vesa X works again. Anyone experienced the same thing? Best regards, Luís Moreira.
Luís Moreira <lmm1987@gmail.com>:
Anyone experienced the same thing? No, work's without any problems here. I have the same setting as you: x86_64 without testing.
-- Gruß, Johannes Täglich http://blog.hehejo.de und du fühlst dich gut. Mast und Schotbruch mit dem http://segelsport-blog.de.
On Sat, Aug 1, 2009 at 6:01 PM, Johannes Held <mail@hehejo.de> wrote:
Luís Moreira <lmm1987@gmail.com>:
Anyone experienced the same thing? No, work's without any problems here. I have the same setting as you: x86_64 without testing.
-- Gruß, Johannes Täglich http://blog.hehejo.de und du fühlst dich gut. Mast und Schotbruch mit dem http://segelsport-blog.de.
Just as a note, there's a forum thread marked with this same issue. Thought I'd link it so that any definitive solution might be shouted over there as well. I think the OP has 32 bit. I have i686 and did not have a problem with the upgrade, but I am running testing. http://bbs.archlinux.org/viewtopic.php?id=77119
2009/8/1, Luís Moreira <lmm1987@gmail.com>:
Hello.
The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything.
I'm using X86_64, *without* [testing].
The updated packages were
kernel26 nvidia xorg-server (and some others, less important)
If I change the driver in xorg.conf from nvidia to vesa X works again.
Anyone experienced the same thing?
It works fine here. I'm using x86_64, nvidia, without testing. -- Arch Linux Developer http://www.archlinux.org http://www.archlinux.it
Hi, I somewhere read something about the latest nvidia driver being broken for notebook chips. I’m not sure if this is correct or was just an issue with the beta drivers but especially as you mention that it worked again after changing to vesa drivers I thought this might be the case here. I’m using nvidia drivers for my notebook as well but have not yet updated them because I read that it might cause problems. Are you, too, running a notebook? If so I’d be interested to hear if the latest nvidia drivers work ok for you. Edgar Am oder ungefähr am Samstag, 01. August 2009, um 23:58:58 schrieb Luís Moreira:
Hello.
The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything.
I'm using X86_64, *without* [testing].
The updated packages were
kernel26 nvidia xorg-server (and some others, less important)
If I change the driver in xorg.conf from nvidia to vesa X works again.
Anyone experienced the same thing?
Best regards, Luís Moreira.
If "notebook" includes HP Pavilion dv8000 laptop with GEFORCE GO 7600 NVIDIA graphics card (why do they capitalize *everything*?), and you're asking referring to i686, then yes, it seems to be fine, for me. :-) On Sat, Aug 1, 2009 at 6:28 PM, Edgar Kalkowski <eMail@edgar-kalkowski.de>wrote:
Hi,
I somewhere read something about the latest nvidia driver being broken for notebook chips. I’m not sure if this is correct or was just an issue with the beta drivers but especially as you mention that it worked again after changing to vesa drivers I thought this might be the case here.
I’m using nvidia drivers for my notebook as well but have not yet updated them because I read that it might cause problems. Are you, too, running a notebook? If so I’d be interested to hear if the latest nvidia drivers work ok for you.
Edgar
Am oder ungefähr am Samstag, 01. August 2009, um 23:58:58 schrieb Luís Moreira:
Hello.
The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything.
I'm using X86_64, *without* [testing].
The updated packages were
kernel26 nvidia xorg-server (and some others, less important)
If I change the driver in xorg.conf from nvidia to vesa X works again.
Anyone experienced the same thing?
Best regards, Luís Moreira.
On Sunday 02 August 2009 00:28:42 Edgar Kalkowski wrote:
Hi,
I somewhere read something about the latest nvidia driver being broken for notebook chips. I’m not sure if this is correct or was just an issue with the beta drivers but especially as you mention that it worked again after changing to vesa drivers I thought this might be the case here. This bug was related only to nvidia-beta, release 190.16 and it was fixed in version 190.18. It has never touched the stable drivers.
(Btw I was trying to track down some informations now abput 190.16, but it seems guys from nVidia removed the announcement thread from nvnews.net and nvidia.com drivers pages are out of order (E404) :-) )
I’m using nvidia drivers for my notebook as well but have not yet updated them because I read that it might cause problems. Are you, too, running a notebook? If so I’d be interested to hear if the latest nvidia drivers work ok for you.
Edgar
Am oder ungefähr am Samstag, 01. August 2009, um 23:58:58 schrieb Luís
Moreira:
Hello.
The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything.
I'm using X86_64, *without* [testing].
The updated packages were
kernel26 nvidia xorg-server (and some others, less important)
If I change the driver in xorg.conf from nvidia to vesa X works again.
Anyone experienced the same thing?
Best regards, Luís Moreira.
-- --------------------------------- Dan Vrátil vratil@progdansoft.com ICQ 249163429 Jabber progdan@jabber.cz Tel. +420 732 326 870 http://www.progdan.homelinux.net
Am oder ungefähr am Sonntag, 02. August 2009, um 02:02:21 schrieb Dan Vratil:
I somewhere read something about the latest nvidia driver being broken for notebook chips. I’m not sure if this is correct or was just an issue with the beta drivers but especially as you mention that it worked again after changing to vesa drivers I thought this might be the case here. This bug was related only to nvidia-beta, release 190.16 and it was fixed in version 190.18. It has never touched the stable drivers.
That is good to hear. In this case I’ll upgrade my drivers right away. :) Edgar
I can confirm this issue for my notebook. Downgrading to the previous version of nvidia and nvidia-utils (version 185.18.14-1) fixed the issue. Graphics Processor: Quadro NVS 140M -Tim Edgar Kalkowski wrote:
Hi,
I somewhere read something about the latest nvidia driver being broken for notebook chips. I’m not sure if this is correct or was just an issue with the beta drivers but especially as you mention that it worked again after changing to vesa drivers I thought this might be the case here.
I’m using nvidia drivers for my notebook as well but have not yet updated them because I read that it might cause problems. Are you, too, running a notebook? If so I’d be interested to hear if the latest nvidia drivers work ok for you.
Edgar
Am oder ungefähr am Samstag, 01. August 2009, um 23:58:58 schrieb Luís Moreira:
Hello.
The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything.
I'm using X86_64, *without* [testing].
The updated packages were
kernel26 nvidia xorg-server (and some others, less important)
If I change the driver in xorg.conf from nvidia to vesa X works again.
Anyone experienced the same thing?
Best regards, Luís Moreira.
2009/8/1, Luís Moreira <lmm1987@gmail.com>:
nvidia
Are you using nvidia-185.18.31-1? -- Arch Linux Developer http://www.archlinux.org http://www.archlinux.it
Yes. I believe that is the latest one, since pacman -Syu shows nothing needs updates. Correct? On Sat, Aug 1, 2009 at 6:33 PM, Giovanni Scafora <giovanni@archlinux.org>wrote:
2009/8/1, Luís Moreira <lmm1987@gmail.com>:
nvidia
Are you using nvidia-185.18.31-1?
-- Arch Linux Developer http://www.archlinux.org http://www.archlinux.it
2009/8/1, Muhammad Qadri <muhammad.a.qadri@gmail.com>:
Yes. I believe that is the latest one, since pacman -Syu shows nothing needs updates. Correct?
Yeah, nvidia-185.18.31-1 is the latest one. I am also using x86_64 (without testing) and kernel 2.6.30.4-1 -- Arch Linux Developer http://www.archlinux.org http://www.archlinux.it
On Sat-2009/08/01-23:58 Lu?s Moreira wrote:
The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything.
I'm using X86_64, *without* [testing].
The updated packages were
kernel26 nvidia xorg-server (and some others, less important)
If I change the driver in xorg.conf from nvidia to vesa X works again.
I'm running i686. The nVIDIA GeForce 6100/nFORCE 430 chipset (AMD64) exhibits segfaults in xorg-server-1.6.3-1 X(1): Backtrace: 0: /usr/bin/X(xorg_backtrace+0x3b) [0x813177b] 1: /usr/bin/X(xf86SigHandler+0x9e) [0x80caf6e] 2: [0xb7f79400] 3: /usr/lib/libdbus-1.so.3 [0xb7e884c9] 4: /usr/bin/X [0x80ab683] 5: /usr/bin/X(WakeupHandler+0x52) [0x8090b42] 6: /usr/bin/X(WaitForSomething+0x1a2) [0x812f2b2] 7: /usr/bin/X(Dispatch+0x80) [0x808c530] 8: /usr/bin/X(main+0x395) [0x8072065] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7b45a36] 10: /usr/bin/X [0x8071511] Fatal server error: Caught signal 11. Server aborting This error occurs often, but today another one showed up: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x3b) [0x813177b] 1: /usr/bin/X(xf86SigHandler+0x9e) [0x80caf6e] 2: [0xb7f96400] 3: /usr/lib/libdbus-1.so.3 [0xb7ea54c9] 4: /usr/bin/X [0x80ab683] 5: /usr/bin/X(WakeupHandler+0x52) [0x8090b42] 6: /usr/bin/X(WaitForSomething+0x1a2) [0x812f2b2] 7: /usr/bin/X(Dispatch+0x80) [0x808c530] 8: /usr/bin/X(main+0x395) [0x8072065] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7b62a36] 10: /usr/bin/X [0x8071511] Fatal server error: Caught signal 4. Server aborting Signal 4 is an illegal instruction. The log also contained, for the sigsegv case: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" after 27 requests (26 known processed) with 0 events remaining. XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" after 103 requests (103 known processed) with 0 events remaining. XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" after 508 requests (508 known processed) with 0 events remaining. urxvt: X connection to ':0.0' broken, unable to recover, exiting. xinit: connection to X server lost. In my case, the error appeared after various intervals of normal operation, but I think I could provoke it by opening more windows. As several components went into the last upgrade, I couldn't tell which one caused the problem. The X11-related packages were: [2009-08-02 16:04] upgraded hal-info (0.20090414-1 -> 0.20090716-1) [2009-08-02 16:04] upgraded inputproto (1.5.0-1 -> 1.5.1-1) [2009-08-02 16:05] upgraded kernel26 (2.6.30.2-1 -> 2.6.30.4-1) [2009-08-02 16:05] upgraded xcb-proto (1.4-1 -> 1.5-1) [2009-08-02 16:05] upgraded libxcb (1.2-1 -> 1.4-1) [2009-08-02 16:05] upgraded libx11 (1.2.1-1 -> 1.2.2-1) [2009-08-02 16:05] upgraded pciutils (3.1.2-1 -> 3.1.3-1) [2009-08-02 16:05] upgraded xcb-util (0.3.4-2 -> 0.3.5-1) [2009-08-02 16:05] upgraded xf86-input-evdev (2.2.2-1 -> 2.2.3-1) [2009-08-02 16:05] upgraded xorg-server (1.6.2-1 -> 1.6.3-1) I don't run a customary desktop, just screen(1) in urxvt(1) on Xorg(7), all applications being ncurses driven. Doing: pacman -U /var/cache/pacman/pkg/xorg-server-1.6.2-1-i686.pkg.tar.gz fixed it. BTW: except for one instance where neither mouse nor keyboard worked, I was dropped back to the console and didn't loose any work, because I could resurrect everything with "screen -R". It is even possible to experiment within X11, detach that screen and resume it in the console, switching back and forth between X11-grafix and console. A wonderful thing, this screen(1) program! One last thing should be mentioned, though: a few days ago, with "xorg-server-1.6.2-1" running, Xorg froze on me, indicating that the problem might not be caused by the hal-debug-patch mentioned in the forum. The more so because I don't have hald(8) running at all, and my /etc/X11/xorg.conf contains: Section "ServerFlags" ... Option "AutoAddDevices" "False" # stop HAL Option "AutoEnableDevices" "false" # stop HAL EndSection The DBUS daemon is up, if that is of interest. clemens
On Mon-2009/08/03-16:52 clemens fischer wrote:
I don't run a customary desktop, just screen(1) in urxvt(1) on Xorg(7), all applications being ncurses driven. Doing:
pacman -U /var/cache/pacman/pkg/xorg-server-1.6.2-1-i686.pkg.tar.gz
fixed it.
xorg-server-1.6.3-2 has not failed me for hours now, after torturing it with "x11perf -all" and all the apps from xorg-apps. clemens
participants (8)
-
clemens fischer
-
Dan Vratil
-
Edgar Kalkowski
-
Giovanni Scafora
-
Johannes Held
-
Luís Moreira
-
Muhammad Qadri
-
Tim Gelter