[arch-general] updating xorg packages and nvidia packages, now x doesn't start

Ionuț Bîru ibiru at archlinux.org
Mon Dec 20 11:10:59 EST 2010


On 12/20/2010 06:08 PM, Lukáš Jirkovský wrote:
> On 20 December 2010 07:30, Jeffrey Lynn Parke Jr.
> <jeffrey.parke at gmail.com>  wrote:
>> I did a big update on my main arch machine and rebooted, I can't start X
>> anymore. I saw that xorg-xinit and xorg-xauth as well as the nvidia packages
>> were upgraded. Startx gives me a blank screen and switching to the first
>> login (ctrl-alt-F1) shows a never ending "No Protocol Specified" message
>> which finally fails with "xinit: unable to connect to X server: Connection
>> refused" and "Xauth: error in locking authority file /home/user/.Xauthority"
>>
>> I checked my Xorg.0.log file and I see this message listed:
>>
>> (II) NVIDIA(0): Setting mode "nvidia-auto-select" (II) NVIDIA(0): ACPI:
>>> failed to connect to the ACPI event daemon; the daemon (II) NVIDIA(0): may
>>> not be running or the "AcpidSocketPath" X (II) NVIDIA(0): configuration
>>> option may not be set correctly. When the (II) NVIDIA(0): ACPI event daemon
>>> is available, the NVIDIA X driver will (II) NVIDIA(0): try to use it to
>>> receive ACPI event notifications. For (II) NVIDIA(0): details, please see
>>> the "ConnectToAcpid" and (II) NVIDIA(0): "AcpidSocketPath" X configuration
>>> options in Appendix B: X (II) NVIDIA(0): Config Options in the README
>>
>>
>> what could be the problem here?
>>
>
> Do you use testing? If yes, the nvidia drivers are not yet compatible
> with xserver from testing.

what are you talking about?

xorg-server from testing is from 1.9 series, therefor supported.

I suggest to look at nvnews forum and report it there. I saw that some 
models have that bug.

-- 
Ionuț


More information about the arch-general mailing list