Update breaks Nvidia and Xorg.

I get–> server auth: 4031 does not exist.
Could not copy Xorg.0.log Xorg.0.log.old

This is happening to my desktop and laptop. desktop is Intel 330 64 dual core chipset with Nvidia ION graphics.
Laptop is Presareio F767NR Turion 64 dual core with Nvidia 7000 graphics.

I have to boot in as init 3, run yast2, software management, and update the nvidia installs. It will then reboot into
KDE4. On boot after that, it will not autologon or start X. I get the same error message as above. The loop continues.

Master Rod

Could you post some more info:

openSUSE version ?

Which were the updates, did it involve a kernel? Or xorg-server ?
Did you make manual changes to get things working?

Also: please post output of


zypper lr -d

I don’t know if this is relevant, but a number of us after a nvidia driver update were forced to do ALL of the following for the proprietary nVidia driver to work:

  • run “yast” (you can run yast in text mode with root permissions if X window not available) and navigate to yast > System > /etc/sysconfig Editor > System > Kernel > NO_KMS_IN_INITRD and change it to “yes”. This takes a minute or two to save once changed is submitted. That can be done in text mode (guidance here in step 4) SDB:Configuring graphics cards - openSUSE
  • black list the nouveau driver with root permissions:

echo "blacklist nouveau" >> /etc/modprobe.d/50-blacklist.conf

Then re-install the nVidia driver (after a text mode boot with ‘nomodeset’ boot code) , restart the PC and test X.

Since I always install the manual method (from the .run file) I can’t offer any more advice reference the repository method that I believe you used when re-installing the nvidia driver.

linux-jnvc:/home/rodney # zypper lr -d

| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service

—±---------------------------------±----------------------------------±--------±--------±---------±-------±---------------------------------------------------------------------------------------------±-------
1 | Updates-for-openSUSE-11.4-11.4-0 | Updates for openSUSE 11.4 11.4-0 | Yes | Yes | 99 | rpm-md | Index of /update/11.4 |
2 | download.nvidia.com-opensuse | nVidia Graphics Drivers | Yes | Yes | 99 | rpm-md | ftp://download.nvidia.com/opensuse/11.4/ |
3 | download.opensuse.org-Education | openSUSE BuildService - Education | Yes | Yes | 99 | rpm-md | Index of /repositories/Education/openSUSE_11.4 |
4 | openSUSE-11.4-11.4-0 | openSUSE-11.4-11.4-0 | No | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/usb-Toshiba_SuperMultiPA3761_SATASLIM000000045be-0:0,/dev/sr0 |
5 | opensuse-guide.org-repo | libdvdcss repository | Yes | Yes | 99 | rpm-md | http://opensuse-guide.org/repo/11.4/ |
6 | packman.inode.at-suse | Packman Repository | Yes | Yes | 99 | rpm-md | Index of /suse/openSUSE_11.4/ |
7 | repo-debug | openSUSE-11.4-Debug | No | Yes | 99 | NONE | Index of /debug/distribution/11.4/repo/oss |
8 | repo-debug-update | openSUSE-11.4-Update-Debug | No | Yes | 99 | NONE | Index of /debug/update/11.4 |
9 | repo-non-oss | openSUSE-11.4-Non-Oss | Yes | Yes | 99 | yast2 | Index of /distribution/11.4/repo/non-oss |
10 | repo-oss | openSUSE-11.4-Oss | Yes | Yes | 99 | yast2 | Index of /distribution/11.4/repo/oss |
11 | repo-source | openSUSE-11.4-Source | No | Yes | 99 | NONE | Index of /source/distribution/11.4/repo/oss |
linux-jnvc:/home/rodney # lsmod
Module Size Used by
ext4 373665 1
jbd2 78939 1 ext4
crc16 1419 1 ext4
nvidia 9769840 40
af_packet 20330 2
edd 8752 0
snd_pcm_oss 48271 0
snd_mixer_oss 17521 1 snd_pcm_oss
snd_seq 57777 0
snd_seq_device 6678 1 snd_seq
mperf 1271 0
ath3k 3202 0
snd_hda_codec_hdmi 24907 1
snd_hda_codec_via 55104 1
sr_mod 15048 0
cdrom 38437 1 sr_mod
snd_hda_intel 25104 2
snd_hda_codec 95891 3 snd_hda_codec_hdmi,snd_hda_codec_via,snd_hda_intel
joydev 9578 0
snd_hwdep 6198 1 snd_hda_codec
snd_pcm 88841 4 snd_pcm_oss,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer 22055 2 snd_seq,snd_pcm
r8169 38825 0
sg 28446 0
snd 67246 15 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hda_codec_via,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 7270 1 snd
rt2860sta 525148 1
snd_page_alloc 8121 2 snd_hda_intel,snd_pcm
shpchp 27427 0
pcspkr 1662 0
serio_raw 4378 0
pci_hotplug 28814 1 shpchp
crc_ccitt 1419 1 rt2860sta
i2c_nforce2 5927 0
asus_atk0110 14080 0
button 5497 0
wmi 9657 0
reiserfs 247427 3
dm_mirror 13785 1
dm_region_hash 11224 1 dm_mirror
dm_log 9770 3 dm_mirror,dm_region_hash
dm_snapshot 34002 0
dm_mod 76266 17 dm_mirror,dm_log,dm_snapshot
fan 2575 0
processor 36507 0
thermal 13154 0
thermal_sys 14790 3 fan,processor,thermal
linux-jnvc:/home/rodney # /etc/modprobe.d/50-blacklist.conf
bash: /etc/modprobe.d/50-blacklist.conf: Permission denied
linux-jnvc:/home/rodney #

Now, how can permissions be denied while running as root? Makes no sense. OK, will reboot.

My guess is it makes perfect sense. It is a configuration file. It is NOT an executeable file. It is not marked with execution permissions. Hence even as root you are denied the permission to execute a file that has no permissions to execute !

Where did you get the idea from that you should try to execute 50-blacklist.conf ? Not from me. I specifically noted to run:


echo "blacklist nouveau" >> /etc/modprobe.d/50-blacklist.conf

I made it EASY so you could copy and paste that.

What in that code do you NOT understand ?

Calm down Ace…OK, so you don’t run a config file…Duh! I get it. Here is the cat of the conf file.

linux-jnvc:/home/rodney # cat /etc/modprobe.d/50-blacklist.conf

$Id$

Listing a module here prevents modprobe from loading it via modalias (only

aliases from /lib/modules/*/modules.alias). You may still load it explicitely.

We blacklist some modules becaus they may harm on certain devices or they

prevent other modules from grabbing the device.

Syntax: blacklist <driver name>

See ‘man modprobe’.

uhci … usb-uhci handles the same pci class

blacklist uhci

usbcore … module is loaded implicitly, ignore it otherwise

blacklist usbcore

tulip … de4x5, xircom_tulip_cb, dmfe (…) handle same devices

blacklist de4x5

At least 2.4.3 and later xircom_tulip doesn’t have that conflict

xircom_tulip_cb

blacklist dmfe

list all framebuffer drivers, some of them tend to crash during boot

they are either compiled into the kernel, or vesafb is active

X works fine without them, rcfbset can load them if really required

sed -e ‘//drivers/video/..(o|ko)$/{s@^./@@;s@…*$@@;p};d’

blacklist aty128fb
blacklist atyfb
blacklist clgenfb
blacklist cyber2000fb

cyblafb, bug 466280

blacklist cyblafb
blacklist encode-big5
blacklist encode-gb
blacklist encode-gbk
blacklist encode-jis
blacklist encode-kscm
blacklist fbcon-afb
blacklist fbcon-cfb2
blacklist fbcon-cfb4
blacklist fbcon-hga
blacklist fbcon-ilbm
blacklist fbcon-iplan2p2
blacklist fbcon-iplan2p4
blacklist fbcon-iplan2p8
blacklist fbcon-mac
blacklist fbcon-mfb
blacklist fbcon-vga
blacklist fbcon-vga-planes
blacklist fbgen
blacklist g450_pll
blacklist hgafb
blacklist i2c-matroxfb
blacklist i810fb
blacklist intelfbdrv
blacklist intelfbhw
blacklist matroxfb_accel
blacklist matroxfb_base
blacklist matroxfb_crtc2
blacklist matroxfb_DAC1064
blacklist matroxfb_g450
blacklist matroxfb_maven
blacklist matroxfb_misc
blacklist matroxfb_proc
blacklist matroxfb_Ti3026
blacklist mdacon
blacklist neofb
blacklist pm2fb
blacklist pm3fb
blacklist radeonfb
blacklist rivafb
blacklist sisfb
blacklist sstfb
blacklist tdfxfb
blacklist tridentfb
blacklist unikey
blacklist vga16fb
blacklist vgastate
blacklist vmware

for kyrofb see Bug 35810

blacklist kyrofb

list was not complete (bug 106715)

blacklist arcfb
blacklist backlight
blacklist lcd
blacklist cirrusfb
blacklist gx1fb
blacklist intelfb
blacklist macmodes
blacklist nvidiafb
blacklist s1d13xxxfb
blacklist savagefb

additional modules since SLE11, bug 468964

blacklist arkfb
blacklist carminefb
blacklist gxfb
blacklist hecubafb
blacklist lxfb
blacklist s3fb
blacklist sm501fb
blacklist viafb
blacklist vmlfb
blacklist vt8623fb

ISDN modules are load from /lib/udev/isdn.sh

blacklist fcusb
blacklist fcusb2
blacklist fxusb
blacklist fxusb_CZ
blacklist fcdslusb
blacklist fcdslusb2
blacklist fcdslusba
blacklist fcdslslusb
blacklist fcdslslusb2
blacklist e2220pc
blacklist e5520pc
blacklist bfusb
blacklist b1isa
blacklist b1pci
blacklist b1pcmcia
blacklist c4
blacklist t1isa
blacklist t1pci
blacklist divas
blacklist act2000
blacklist hfc_usb
blacklist hisax
blacklist hisax_fcpcipnp
blacklist hisax_st5481
blacklist hysdn
blacklist icn
blacklist pcbit
blacklist sc
blacklist tpam
blacklist fcpci
blacklist fcclassic
blacklist fcdsl
blacklist fcdsl2

mISDN modules

blacklist hfcsusb
blacklist hfcpci
blacklist hfcmulti
blacklist l1oip
blacklist mISDN_dsp
blacklist mISDN_core

OSS PCI sound modules

blacklist ad1889
blacklist ali5455
blacklist btaudio
blacklist cmpci
blacklist cs4281
blacklist emu10k1
blacklist es1370
blacklist es1371
blacklist esssolo1
blacklist forte
blacklist i810_audio
blacklist maestro
blacklist maestro3
blacklist nm256_audio
blacklist opl3sa2 # Bug 219758
blacklist rme96xx
blacklist sonicvibes
blacklist trident
blacklist via82cxxx_audio
blacklist ymfpci

If you really need firewire direct networking, then remove this entry

blacklist eth1394

this is a debugging module which should only be loaded manually

blacklist evbug

These mtd drivers should be loaded manually.

blacklist scb2_flash
blacklist ich2rom
blacklist pci
blacklist l440gx
blacklist amd76xrom

job of rcdvb

blacklist snd_bt87x
blacklist snd-bt87x

HP Touch Screen usb input driver. breaks all other mouse input devices

blacklist tsdev

https://bugzilla.novell.com/show_bug.cgi?id=115132

blacklist slamr
blacklist slusb

This module seems to be good for nothing. See bug 129301.

blacklist dpt_i2o

This driver is obsolete and should never be loaded as default.

See https://bugzilla.novell.com/show_bug.cgi?id=146728

blacklist eepro100

This driver is obsolete and should never be loaded as default.

See https://bugzilla.novell.com/show_bug.cgi?id=146930

blacklist sk98lin

This driver is rarely needed and causes trouble when scanning devices.

See: https://bugzilla.novell.com/show_bug.cgi?id=144623

blacklist stradis

These devices have bt878 chip without PCI Subsystem ID. Without that info bttv

does not know how to treat them properly. Therefore we disable autoloading of

modules for these devices.

See https://bugzilla.novell.com/show_bug.cgi?id=149588

To enable your device create a hardware configuration file for your device.

See man hwup for details.

You will probably have to specify an option to identify your card. Have a

look in /usr/src/linux/Documentation/video4linux/CARDLIST.bttv.

alias pci:v0000109Ed0000036Esv00000000sd00000000bc04sc00i00 bttv_skip_it
alias pci:v0000109Ed00000878sv00000000sd00000000bc04sc80i00 bttv_skip_it
install bttv_skip_it /bin/echo “module alias skipped (bt878 chip without PCI Subsystem ID)”

For some bridges both intel-agp and i82875p_edac are loaded. If i82875p_edac

is loaded first it will grab the device. Then intel-agp doesn’t work.

Therefore we disable automatic loading of 82875p_edac. (Bug 213840)

blacklist i82875p_edac

Blacklist the IBM s390 module for I/O dynamic configuration support

Bug bnc#478601

blacklist chsc_sch
linux-jnvc:/home/rodney #

Now what?

Master Rod
AAAHHHH! I get it! just be root and past the whole enchilada at prompt an press enter!.. You are a wizard!

Cool, blacklist nouveau is now located on the last line of 50-blacklist.conf file. I guess this should stop it from messing up Xorg. Will try it tomorrow I will post any new happenings on this. Is a patch being made to circumvent this problem? Laters

Master Rod

Glad to read the echo command line correctly added the blacklist nouveau entry to the end of the 50-blacklist.conf. A caution about that command:


echo "blacklist nouveau" >> /etc/modprobe.d/50-blacklist.conf

adds ‘blacklist nouveau’ to the end of 50-blacklist.conf

The very very mistaken:


echo "blacklist nouveau" > /etc/modprobe.d/50-blacklist.conf

would replace the entire contents of 50-blacklist.conf with the line “blacklist.conf” and would be a disaster. < gulp > So precision is necessary !

ie the difference between " > " and " >> " is massive.

For some reason as part of the design of nouveau, it became very difficult to remove. Dependent on the version of the nvidia driver (and possibly of the kernel and xorg), the activities that one has to do to prevent the nouveau from inappropriately attempting to load varies.

I have the same problem. OK I removed nouveau with yast, and refreshed the nividia drivers (3). X starts normally. runs fine for the entire duration. Upon reboot, I am back to the text login screen. I log in as root. I key in startx and i get a uid not set error and cannot change Xorg.0.log to Xorg.0.log.old. Might this have to do with permissions? I might just have to reload (boooohoooohoooogaaaaaaadddddnooooooooonot again) the OS and not do any updates?? But then again, if I am having this problem on two computers, I wonder how many other people with the nvidia setup are also struggling(millions)…Must find that bad patch and either remove or fix it. OK, when will openSUSE 12 be out? Maybe my luck will change with that.

Master Rod

You should start your own thread.

I’ve never removed the nouveau rpm as an approach, so I do not know if there are more peculiarities. I’ve NEVER recommended removing the nouveau rpm as an approach.

Did you blacklist the nouveau driver ? Did you disable KMS in the kernel ?

oldcpu this is his thread lol

rdonovan you probably shouldn’t try to startx as root as it’s a popular opinion that this in itself can cause problems, permissions problems among them

Sometimes removing the xauthority file can fix this problem, if you want to try it login as your normal user then do these two commands:

cp /home/yourusername/.Xauthority /home/yourusername/.Xauthority.bak
rm /home/yourusername/.Xauthority

Can’t remember whether I could just startx at this point as it’s a while since I had to do this, so it’s probably as easy to just reboot

If it doesn’t work and you need to put your original xauthority file back you can do it by reversing the two commands like this:

rm /home/yourusername/.Xauthority
cp /home/yourusername/.Xauthority.bak /home/yourusername/.Xauthority

< gulp > lol !! < sigh > … rrdonovan, my apologies. I need to ask everyone else to get off YOUR thread ! …