openSUSE 12.3 and ASUS GeforceGTX460M

English Hardware
1

After a fresh install of 12.3 on my test-hdd (with grub2-efi and GPT) the only availabe screen resolution is 800x600.

It seems as if my monitor / GPU hasn’t been recognized/configured properly during setup.
(ran setup with additional nvidia repository)

now some info:



b3nz0l@linux-7owi:~> sudo /sbin/lspci -nnk | grep VGA -A2
root's password:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF106 [GeForce GTX 460M] [10de:0dd1] (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device [1043:2043]
01:00.1 Audio device [0403]: NVIDIA Corporation GF106 High Definition Audio Controller [10de:0be9] (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device [1043:2043]

b3nz0l@linux-7owi:~> sudo /usr/sbin/hwinfo --monitor
49: None 00.2: 10002 LCD Monitor                                
  [Created at monitor.95]
  Unique ID: aHB6.UMTZkeQzt2E
  Hardware Class: monitor
  Model: "AUO LCD Monitor"
  Vendor: AUO "AUO"
  Device: eisa 0x15ed 
  Resolution: 1920x1080@60Hz
  Size: 344x193 mm
  Detailed Timings #0:
     Resolution: 1920x1080
     Horizontal: 1920 2028 2076 2100 (+108 +156 +180) -hsync
       Vertical: 1080 1090 1100 1130 (+10 +20 +50) -vsync
    Frequencies: 142.40 MHz, 67.81 kHz, 60.01 Hz
  Config Status: cfg=new, avail=yes, need=no, active=unknown

b3nz0l@linux-7owi:~> ll /etc/X11/
insgesamt 44
drwxr-xr-x 1 root root   12  6. Okt 18:14 fs
drwxr-xr-x 1 root root   22  6. Okt 18:09 lbxproxy
drwxr-xr-x 1 root root   16  6. Okt 18:11 proxymngr
drwxr-xr-x 1 root root   44  6. Okt 18:05 rstart
drwxr-xr-x 1 root root  386  7. Okt 19:54 xdm
-rw-r--r-- 1 root root 5708 26. Jan 2013  xim
drwxr-xr-x 1 root root    8  6. Okt 18:15 xim.d
drwxr-xr-x 1 root root   78  6. Okt 18:18 xinit
-rw-r--r-- 1 root root 1353 27. Jan 2013  Xmodmap
-rw-r--r-- 1 root root 1049 27. Jan 2013  Xmodmap.remote
-rw-r--r-- 1 root root 6807  7. Okt 21:54 xorg.conf
drwxr-xr-x 1 root root  174  7. Okt 21:00 xorg.conf.d
-rw-r--r-- 1 root root  874  6. Okt 18:42 xorg.conf.install
-rw-r--r-- 1 root root 1325  6. Okt 20:18 xorg.conf.nvd
-rw-r--r-- 1 root root 7611  7. Okt 19:53 xorg.conf.nvidia-post
-rw-r--r-- 1 root root    0  6. Okt 20:18 xorg.conf.nvidia-xconfig-original
-rw-r--r-- 1 root root 4017 22. Apr 2009  Xresources
drwxr-xr-x 1 root root   20  6. Okt 18:25 xsm

b3nz0l@linux-7owi:~> ll /etc/X11/xorg.conf.d/
insgesamt 24
-rw-r--r-- 1 root root 1099 21. Feb 2013  10-evdev.conf
-rw-r--r-- 1 root root 3640 27. Jan 2013  11-mouse.conf
-rw-r--r-- 1 root root 1918  4. Feb 2013  50-synaptics.conf
-rw-r--r-- 1 root root  115 28. Jan 2013  50-vmmouse.conf
-rw-r--r-- 1 root root  835 28. Jan 2013  50-wacom.conf
-rw-r--r-- 1 root root  141  6. Okt 18:46 90-keytable.conf

b3nz0l@linux-7owi:~> ll /usr/share/X11/xorg.conf.d/
insgesamt 8
-rw-r--r-- 1 root root 1099 21. Feb 2013  10-evdev.conf
-rw-r--r-- 1 root root   73  7. Okt 21:30 zz-50-device.conf.test

b3nz0l@linux-7owi:~> cat /usr/share/X11/xorg.conf.d/zz-50-device.conf.test
Section "Device"
Identifier "Default.Device"
Driver "nouveau"
EndSection
b3nz0l@linux-7owi:~>

and my current Xorg.0.log
SUSE Paste

as /etc/X11/xorg.conf isn’t used anymore, how do i have to configure my system to support my GPU / monitor?
my test device.conf brought no results
i read about blacklisting nouveau and forcing the OS to use the proprietary nvidia drivers, could this be necessary in my case?

2

as /etc/X11/xorg.conf isn’t used anymore, how do i have to configure my system to support my GPU / monitor?
my test device.conf brought no results
i read about blacklisting nouveau and forcing the OS to use the proprietary nvidia drivers, could this be necessary in my case?

Yes you must blacklist the nouveau driver.

To blacklist, open konsole or xterm and type in:

su -

and then your password.

Then type:

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

Then start Yast–>System–>/etc/sysconfig Editor/System–>Kernel–>NO_KMS_IN_INITRD . Change it from no to yes.

Click on the OK buttons and reboot your computer. Install your nVidia drivers.

3

You’re telling X to use nouveau (blacklisted by the nvidia driver), which makes the system fall back to vesafb???
Remove the zz-50-device.conf first, reboot.

4

The Xorg.0.log indicates that the system was booted in failsafe/recovery mode, that’s why the nvidia driver is not used:

    21.139] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.7.10-1.1-desktop root=UUID=83488596-d532-4fc8-9cb2-3b3e95af34be showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe

Choose a standard entry at the boot menu and it should work then. If not post Xorg.0.log again.

And how did you actually install the nvidia driver (and which version)? If using the RPMs you don’t have to manually blacklist or change anything.
xorg.conf is not needed, the nvidia driver is used automatically if installed.

5

The OP has a xorg.conf file (likely created by the Nvidia config tool), and its settings would/should take precedence over those he created in his zz file. However, your point about them trying to load the nouveau driver when the nvidia is installed still stands lol!

which makes the system fall back to vesafb???
vesafb is a kernel console framebuffer driver, so no (for that matter, and as an aside, they mentioned using efi, so, vesafb wouldn’t be applicable anyway; the efifb would).

For X, assuming things were getting mucked up, the fallback would be to the fbdev driver (which doesn’t actually have anything to do with a console framebuffer driver, but is an X driver i.e. userspace … admittedly, the name of this generic driver is confusing given that “fbdev” is also the term used to describe the “frame buffer device”, in relation to console framebuffer drivers used for it and the console framebuffer environment itself.

6

Yes, /etc/X11/xorg.conf.install. This is created by the openSUSE installer and used when you boot a “recovery mode” option from the boot menu (or append “x11failsafe” to the boot options).

From his Xorg.0.log:

    21.140] (==) Using config file: "/etc/X11/xorg.conf.install"
7

yes, of course, but going beyond what you had pointed out earlier, (and not trying to explain the actual problem) I was specifically addressing something (a logic point) out to Knurpht

b3nz0l@linux-7owi:~> ll /etc/X11/
…
-rw-r–r-- 1 root root 6807 7. Okt 21:54 xorg.conf
drwxr-xr-x 1 root root 174 7. Okt 21:00 xorg.conf.d
-rw-r–r-- 1 root root 874 6. Okt 18:42 xorg.conf.install
…

8

Ah right. I haven’t had a look at those directory listings in the original post, I only looked at the Xorg.0.log.

But in addition to what you wrote, that zz-50-device.conf.test wouldn’t make X fallback to vesa (or anything else). It would try to load nouveau and just fail if that doesn’t load (because it is blacklisted e.g.).
Although I’m not really sure if ll /usr/share/X11/xorg.conf.d/ is even respected, Xorg.0.log doesn’t mention it at least.

To beatfreak:
So you should remove /usr/share/X11/xorg.conf.d/zz-50-device.conf.test and /etc/X11/xorg.conf (although you could keep that if the settings in there are ok, but it’s not needed so better remove it), then boot a standard boot entry (no “recovery mode”) and the nvidia driver should work.
If not, please post Xorg.0.log again.

And because you booted to kernel-desktop-3.7.10-1.1 it looks like your system isn’t fully updated.
Install all updates with YaST->Online Update or “zypper up” f.e., otherwise you have to add your user to the “video” group for the nvidia driver to work fully: openSUSE 12.3 Release Notes

9

Blacklisting only prevents the DRM loading at boot; it does not prevent the module from being loaded later on (particularly, as in this case, if he’s calling for X to load the nouveau DDX, which is itself going to result in the nouveau DRM loading)

Although I’m not really sure if ll /usr/share/X11/xorg.conf.d/ is even respected, Xorg.0.log doesn’t mention it at least.
I don’t believe that particular path is searched … see “man xorg.conf” and “man xorg” for nitty gritty pathway details.

In any regard, there is some cruft that the OP needs to clean up.

10

OK, I didn’t know that. I thought blacklisting would prevent it from being automatically loaded even later on.

But anyway, the point was, that specifying Driver “nouveau” in X’s configuration will prevent X from falling back to vesa. It would try to load nouveau and fail to start if it can’t (for whatever reason). :wink:

11

You’re right, the time when i pasted the Xorg.log the system had been booted in failsafe mode. (in normal mode it wont start the GUI probably due to my previous failed attempts to fix it by X -configure / installing-uninstalling nvidia an nouveau drivers.)

However meanwhile it got even weirder, to get back to the original erroneous state i did a full reinstall of the OS (re-formatting root partition with btrfs)
form these repositories:


OSS
NON-OSS
Main Update
non-oss update
Wine
Mozilla
All of Packman
Nvidia

(last 4 as stated on “Additional Package Repositories”)
The only difference from first install is that i included the “updates” repo
And guess what, it’s all fine now → SOLVED

the thing about zz-50-device.conf.test was that i assumed that it won’t get loaded if it’s not ending with .conf. From what you wrote i have been wrong in this case. (in SamyGO.tv extensions it works that way…)

current state:
hwinfo:


b3nz0l@linux-gyvy:~> sudo /usr/sbin/hwinfo --gfxcard
28: PCI 100.0: 0300 VGA compatible controller (VGA)             
  [Created at pci.319]
  Unique ID: VCu0.IrNsb6Wafk1
  Parent ID: 3hqH.NZk+zWrXLs4
  SysFS ID: /devices/pci0000:00/0000:00:03.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "nVidia VGA compatible controller"
  Vendor: pci 0x10de "nVidia Corporation"
  Device: pci 0x0dd1 
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x2043 
  Revision: 0xa1
  Driver: "nvidia"
  Driver Modules: "nvidia"
  Memory Range: 0xd4000000-0xd4ffffff (rw,non-prefetchable)
  Memory Range: 0xc8000000-0xcfffffff (ro,non-prefetchable)
  Memory Range: 0xd0000000-0xd1ffffff (ro,non-prefetchable)
  I/O Ports: 0xd000-0xdfff (rw)
  Memory Range: 0xd6000000-0xd607ffff (ro,non-prefetchable,disabled)
  IRQ: 16 (446532 events)
  Module Alias: "pci:v000010DEd00000DD1sv00001043sd00002043bc03sc00i00"
  Driver Info #0:
    Driver Status: nvidiafb is not active
    Driver Activation Cmd: "modprobe nvidiafb"
  Driver Info #1:
    Driver Status: nouveau is not active
    Driver Activation Cmd: "modprobe nouveau"
  Driver Info #2:
    Driver Status: nvidia is active
    Driver Activation Cmd: "modprobe nvidia"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #9 (PCI bridge)

Primary display adapter: #28

b3nz0l@linux-gyvy:~> sudo /usr/sbin/hwinfo --monitor
49: None 00.2: 10002 LCD Monitor                                
  [Created at monitor.95]
  Unique ID: aHB6.UMTZkeQzt2E
  Hardware Class: monitor
  Model: "AUO LCD Monitor"
  Vendor: AUO "AUO"
  Device: eisa 0x15ed 
  Resolution: 1920x1080@60Hz
  Size: 344x193 mm
  Detailed Timings #0:
     Resolution: 1920x1080
     Horizontal: 1920 2028 2076 2100 (+108 +156 +180) -hsync
       Vertical: 1080 1090 1100 1130 (+10 +20 +50) -vsync
    Frequencies: 142.40 MHz, 67.81 kHz, 60.01 Hz
  Config Status: cfg=new, avail=yes, need=no, active=unknown

b3nz0l@linux-gyvy:~> sudo /sbin/lspci -nnk | grep VGA -A5
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF106 [GeForce GTX 460M] [10de:0dd1] (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device [1043:2043]
        Kernel driver in use: nvidia
01:00.1 Audio device [0403]: NVIDIA Corporation GF106 High Definition Audio Controller [10de:0be9] (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device [1043:2043]
        Kernel driver in use: snd_hda_intel

files:


b3nz0l@linux-gyvy:~> ll /etc/X11/
insgesamt 24
drwxr-xr-x 1 root root   12  8. Okt 11:38 fs
drwxr-xr-x 1 root root   22  8. Okt 11:37 lbxproxy
drwxr-xr-x 1 root root   16  8. Okt 11:40 proxymngr
drwxr-xr-x 1 root root   44  8. Okt 11:28 rstart
drwxr-xr-x 1 root root  386  8. Okt 12:00 xdm
-rw-r--r-- 1 root root 5708 26. Jan 2013  xim
drwxr-xr-x 1 root root    8  8. Okt 11:39 xim.d
drwxr-xr-x 1 root root   78  8. Okt 11:47 xinit
-rw-r--r-- 1 root root 1353 27. Jan 2013  Xmodmap
-rw-r--r-- 1 root root 1049 27. Jan 2013  Xmodmap.remote
drwxr-xr-x 1 root root  288  8. Okt 12:19 xorg.conf.d
-rw-r--r-- 1 root root  874  8. Okt 12:14 xorg.conf.install
-rw-r--r-- 1 root root 4017 22. Apr 2009  Xresources
drwxr-xr-x 1 root root   20  8. Okt 11:58 xsm
b3nz0l@linux-gyvy:~> ll /etc/X11/xorg.conf.d
insgesamt 40
-rw-r--r-- 1 root root   61  1. Mär 2013  05-glamor.conf
-rw-r--r-- 1 root root 1099 15. Jul 14:25 10-evdev.conf
-rw-r--r-- 1 root root 3640 27. Jan 2013  11-mouse.conf
-rw-r--r-- 1 root root  529  1. Jul 2011  50-device.conf
-rw-r--r-- 1 root root  527  1. Jul 2011  50-monitor.conf
-rw-r--r-- 1 root root  491  1. Jul 2011  50-screen.conf
-rw-r--r-- 1 root root 1918  4. Feb 2013  50-synaptics.conf
-rw-r--r-- 1 root root  115 28. Jan 2013  50-vmmouse.conf
-rw-r--r-- 1 root root  835 28. Jan 2013  50-wacom.conf
-rw-r--r-- 1 root root  141  8. Okt 12:19 90-keytable.conf
b3nz0l@linux-gyvy:~> 
b3nz0l@linux-gyvy:~> 
b3nz0l@linux-gyvy:~> cat /etc/X11/xorg.conf.d/50-device.conf
# Having multiple "Device" sections is known to be problematic. Make
# sure you don't have in use another one laying around e.g. in another
# xorg.conf.d file or even a generic xorg.conf file. More details can
# be found in https://bugs.freedesktop.org/show_bug.cgi?id=32430.
#
#Section "Device"
#  Identifier "Default Device"
#
#  #Driver "radeon"
#
#  ## Required magic for radeon/radeonhd drivers; output name
#  ## (here: "DVI-0") can be figured out via 'xrandr -q'
#  #Option "monitor-DVI-0" "Default Monitor"
#
#EndSection
b3nz0l@linux-gyvy:~> cat /etc/X11/xorg.conf.d/50-monitor.conf
# Having multiple "Monitor" sections is known to be problematic. Make
# sure you don't have in use another one laying around e.g. in another
# xorg.conf.d file or even a generic xorg.conf file. More details can
# be found in https://bugs.freedesktop.org/show_bug.cgi?id=32430.
#
#Section "Monitor"
#  Identifier "Default Monitor"
#
#  ## If your monitor doesn't support DDC you may override the
#  ## defaults here
#  #HorizSync 28-85
#  #VertRefresh 50-100
#
#  ## Add your mode lines here, use e.g the cvt tool
#
#EndSection
b3nz0l@linux-gyvy:~> cat /etc/X11/xorg.conf.d/50-screen.conf
# Having multiple "Screen" sections is known to be problematic. Make
# sure you don't have in use another one laying around e.g. in another
# xorg.conf.d file or even a generic xorg.conf file. More details can
# be found in https://bugs.freedesktop.org/show_bug.cgi?id=32430.
#
#Section "Screen"
#  Identifier "Default Screen"
#
#  Device "Default Device"
#
#  ## Doesn't help for radeon/radeonhd drivers; use magic in
#  ## 50-device.conf instead
#  Monitor "Default Monitor"
#
#EndSection
b3nz0l@linux-gyvy:~> 
b3nz0l@linux-gyvy:~> 
b3nz0l@linux-gyvy:~> ll /usr/share/X11/xorg.conf.d/
insgesamt 4
-rw-r--r-- 1 root root 1099 15. Jul 14:25 10-evdev.conf
b3nz0l@linux-gyvy:~> ll /etc/modprobe.d/
insgesamt 56
-rw-r--r-- 1 root root 3613 26. Jan 2013  00-system.conf
-rw-r--r-- 1 root root  532 14. Nov 2012  10-unsupported-modules.conf
-rw-r--r-- 1 root root  181 10. Apr 11:19 50-alsa.conf
-rw-r--r-- 1 root root 5921 25. Mär 2013  50-blacklist.conf
-rw-r--r-- 1 root root  128 29. Jan 2013  50-bluetooth.conf
-rw-r--r-- 1 root root   33 19. Jul 11:03 50-ipw2200.conf
-rw-r--r-- 1 root root   34 19. Jul 11:03 50-iwl3945.conf
-rw-r--r-- 1 root root   31 19. Jul 11:03 50-iwlagn.conf
-rw-r--r-- 1 root root   86 15. Jul 14:25 50-nvidia.conf
-rw-r--r-- 1 root root   18 19. Jul 11:03 50-prism54.conf
-rw-r--r-- 1 root root  217  8. Okt 12:19 50-sound.conf
-rw-r--r-- 1 root root    0  8. Okt 12:19 50-sound.conf.YaST2save
-rw-r--r-- 1 root root    0  8. Okt 12:19 50-tv.conf
-rw-r--r-- 1 root root   47 22. Nov 2011  99-local.conf
-rw-r--r-- 1 root root   18 28. Jun 13:55 nvidia-desktop.conf
b3nz0l@linux-gyvy:~> 
b3nz0l@linux-gyvy:~> 
b3nz0l@linux-gyvy:~> 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
# uas has been confirmed to be hopelessly broken
# Bug bnc#770301
blacklist uas
b3nz0l@linux-gyvy:~> cat /etc/modprobe.d/50-nvidia.conf
options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660

Xorg.0.log
SUSE Paste

NO_KMS_IN_INITRD is set to “yes” by default

12

On 2013-10-08 18:36, wolfi323 wrote:
> OK, I didn’t know that. I thought blacklisting would prevent it from
> being automatically loaded even later on.

In general, blacklisting impedes automatic loading of a module; but if
something requests that specific module it will be loaded.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

13

Could have been caused by the xorg.conf or the missing updates (see my link to the release notes).
b3nz0l@linux-gyvy:~> ll /etc/modprobe.d/
insgesamt 56
…
-rw-r–r-- 1 root root 18 28. Jun 13:55 nvidia-desktop.conf[/QUOTE]
This one contains the blacklist for nouveau and comes with the nvidia driver RPMs (the kmp to be precise).

Xorg.0.log
SUSE Paste

This shows that the nvidia driver is in use.

NO_KMS_IN_INITRD is set to “yes” by default

Wrong, it’s “no” by default. See the shipped (with 12.3) file /var/adm/fillup-templates/sysconfig.kernel-mkinitrd (which is the template for /etc/sysconfig/kernel):

## Type:        yesno## Command:     /sbin/mkinitrd
## Default:     ""
#
#
# This variable disables the initialization of KMS in the initrd
# by not including the modules required for KMS even though KMS is
# supported on the underlying hardware.
# After changing run mkinitrd again.
#
NO_KMS_IN_INITRD="no"

But setting it to “yes” shouldn’t normally be necessary.

14

He means that he set it yes as his new default. However, it was the wrong play on the word “default”. And yes, when installing the nVidia drivers the installer sets up the new settings automagically.
Users should learn the basics from the openSUSE Reference pdfs which are on the DVD or for download.

The reason it was mentioned was that openSUSE allows the users to use the powerful /etc/sysconfig Editor to configure specific settings and loading of modules.