Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › [Solved] Unable to get SLI up and running
New Posts  All Forums:Forum Nav:

[Solved] Unable to get SLI up and running

post #1 of 6
Thread Starter 
Since having 2 cards I have always just pulled one when running Fedora, and put it back when in Windoze. I had some time on my hands today and tried to set up my xorg.conf properly and haven't been able to get it working.

The common solution I have seen is specifying the pci bus, and putting an option in the Screen section for "SLI" "auto" or "SLI" "on"

I scanned the buses and found that 2:0:0 was my primary card's location, so under the Device section I put
BusID "PCI:2:0:0"

and I would get the same result with or without the SLI setting under "Screen"

just a black screen. Now when I would boot up with just 1 card in, I would have to replace xorg.conf with my backup because X wouldn't load properly. It would drop me to desktop but all I could do was open a terminal, no menus, or dragging anything. I can post my whole xorg.conf later, but I'm about to leave for dinner now.

Any help is appreciated.
Edited by esocid - 3/9/10 at 5:35am
Deimos
(11 items)
 
Pluto
(18 items)
 
 
CPUMotherboardGraphicsRAM
AMD 1090T Biostar TA890FXE Nvidia GTX 470 Corsair Vengence 
Hard DriveHard DriveHard DriveHard Drive
Samsung 830 MZ-7PC128D/AM Western Digital Black Western Digital Green Western Digital Blue 
CoolingOSOSMonitor
Dtek v2 Water Windows 7 Pro Fedora 16 LG4250 42" LCD TV 
KeyboardPowerCaseMouse
Microsoft Ergo Silverstone ST-1000P Cooler Master Cosmos 1000 Logitech G500 
Mouse PadAudio
X-Trac Ripper Asus D1 
  hide details  
Reply
Deimos
(11 items)
 
Pluto
(18 items)
 
 
CPUMotherboardGraphicsRAM
AMD 1090T Biostar TA890FXE Nvidia GTX 470 Corsair Vengence 
Hard DriveHard DriveHard DriveHard Drive
Samsung 830 MZ-7PC128D/AM Western Digital Black Western Digital Green Western Digital Blue 
CoolingOSOSMonitor
Dtek v2 Water Windows 7 Pro Fedora 16 LG4250 42" LCD TV 
KeyboardPowerCaseMouse
Microsoft Ergo Silverstone ST-1000P Cooler Master Cosmos 1000 Logitech G500 
Mouse PadAudio
X-Trac Ripper Asus D1 
  hide details  
Reply
post #2 of 6
Use the nvidia-xconfig tool as root to enable SLI:

Code:
# nvidia-xconfig --damage-events --cool-bits=1 --sli=Auto --multigpu=Auto
damage-events to increase performance, and coolbits to enable overclocking through the nVidia CP. The rest is self-explanatory.
#well
(17 items)
 
Lenovo L530
(8 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 4770k Gigabyte Z87X-UD4H XFX Radeon HD 6950 Corsair CMX8GX3M2A2000C9 
Hard DriveHard DriveOptical DriveCooling
OCZ Agility 3 Hitachi HDS722020ALA330 Generic DVD±RW Burner Noctua NH-D14 
OSMonitorKeyboardPower
Windows 8.1 Dell U2711 Ducky DK9008G2 Overclock.net Edition, Cherry MX... Corsair TX850 
CaseMouseMouse PadAudio
Antec Three Hundred Corsair Raptor M40 QPAD HeatoN XL E-MU Tracker|pre 
Audio
Beyerdynamic DT-770 250 Ohm 
CPUGraphicsRAMRAM
Intel Ivy Bridge 3210M Intel HD 4000 Graphics Soldered Corsair Vengeance  
Hard DriveOptical DriveOSMonitor
500GB DVD-+RW Windows 7 Professional 1600x900 
  hide details  
Reply
#well
(17 items)
 
Lenovo L530
(8 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 4770k Gigabyte Z87X-UD4H XFX Radeon HD 6950 Corsair CMX8GX3M2A2000C9 
Hard DriveHard DriveOptical DriveCooling
OCZ Agility 3 Hitachi HDS722020ALA330 Generic DVD±RW Burner Noctua NH-D14 
OSMonitorKeyboardPower
Windows 8.1 Dell U2711 Ducky DK9008G2 Overclock.net Edition, Cherry MX... Corsair TX850 
CaseMouseMouse PadAudio
Antec Three Hundred Corsair Raptor M40 QPAD HeatoN XL E-MU Tracker|pre 
Audio
Beyerdynamic DT-770 250 Ohm 
CPUGraphicsRAMRAM
Intel Ivy Bridge 3210M Intel HD 4000 Graphics Soldered Corsair Vengeance  
Hard DriveOptical DriveOSMonitor
500GB DVD-+RW Windows 7 Professional 1600x900 
  hide details  
Reply
post #3 of 6
Thread Starter 
Quote:
Originally Posted by gonX View Post
Use the nvidia-xconfig tool as root to enable SLI:

Code:
# nvidia-xconfig --damage-events --cool-bits=1 --sli=Auto --multigpu=Auto
damage-events to increase performance, and coolbits to enable overclocking through the nVidia CP. The rest is self-explanatory.
After configuring it like that, I'm now somewhere I've been before. It gets past the loading screen and then to a point where the screen flickers like it's trying to use both cards, with this already on the screen, like it was loading the kernel still
Quote:
virbr0: starting userspace STP failed, starting kernel STP
lo: Disabled Privacy Extensions
then it stops flickering and prints:

Quote:
audit(1267962717.489:55472): auid=4294967295 ses=4294967295 subj=system_u:system_r:readahead_t:s0 op=remove rule key=(null) list=4 res=1
audit(1267962717.489:55473): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=system_u:system_r:readahead_t:s0 res=1

*Edit
Specified my busid and it gives me just a black screen.

Well that message may not even be related. I used my install disc to mount my system and browsed my Xorg.0.log and saw this at the end

Quote:
Failed to load the nvidia kernel module.
UnloadModule: "nvidia"
Unloading /usr/lib64/xorg/modules/drivers//nvidia_drv.so
Failed to load module "nvidia" (module-specific error, 0)
No drivers available.
I have akmod-nvidia installed and up to date, as well as kernel-devel, and kmod-nvidia too.
Running xinit 5 tells me it can't load /lib/modules/2.6.29.4-167.fc11.x86_64/modules.dep: no such file or directory
In addition to those other errors.

I'm wondering if this has something to do with it or it's just because I'm running off the disc, but my system kernel is 2.6.30.

Pulling a card out and booting up with same xorg.conf works fine now though, so that's an improvement.
Edited by esocid - 3/7/10 at 11:02am
Deimos
(11 items)
 
Pluto
(18 items)
 
 
CPUMotherboardGraphicsRAM
AMD 1090T Biostar TA890FXE Nvidia GTX 470 Corsair Vengence 
Hard DriveHard DriveHard DriveHard Drive
Samsung 830 MZ-7PC128D/AM Western Digital Black Western Digital Green Western Digital Blue 
CoolingOSOSMonitor
Dtek v2 Water Windows 7 Pro Fedora 16 LG4250 42" LCD TV 
KeyboardPowerCaseMouse
Microsoft Ergo Silverstone ST-1000P Cooler Master Cosmos 1000 Logitech G500 
Mouse PadAudio
X-Trac Ripper Asus D1 
  hide details  
Reply
Deimos
(11 items)
 
Pluto
(18 items)
 
 
CPUMotherboardGraphicsRAM
AMD 1090T Biostar TA890FXE Nvidia GTX 470 Corsair Vengence 
Hard DriveHard DriveHard DriveHard Drive
Samsung 830 MZ-7PC128D/AM Western Digital Black Western Digital Green Western Digital Blue 
CoolingOSOSMonitor
Dtek v2 Water Windows 7 Pro Fedora 16 LG4250 42" LCD TV 
KeyboardPowerCaseMouse
Microsoft Ergo Silverstone ST-1000P Cooler Master Cosmos 1000 Logitech G500 
Mouse PadAudio
X-Trac Ripper Asus D1 
  hide details  
Reply
post #4 of 6
Quote:
Failed to load the nvidia kernel module.
UnloadModule: "nvidia"
Unloading /usr/lib64/xorg/modules/drivers//nvidia_drv.so
Failed to load module "nvidia" (module-specific error, 0)
No drivers available.
That's quite fatal - take a look in dmesg to see what errors the driver reports.

Quote:
/lib/modules/2.6.29.4-167.fc11.x86_64/modules.dep
That's not supposed to happen either. What does:
Code:
uname -r
return?
#well
(17 items)
 
Lenovo L530
(8 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 4770k Gigabyte Z87X-UD4H XFX Radeon HD 6950 Corsair CMX8GX3M2A2000C9 
Hard DriveHard DriveOptical DriveCooling
OCZ Agility 3 Hitachi HDS722020ALA330 Generic DVD±RW Burner Noctua NH-D14 
OSMonitorKeyboardPower
Windows 8.1 Dell U2711 Ducky DK9008G2 Overclock.net Edition, Cherry MX... Corsair TX850 
CaseMouseMouse PadAudio
Antec Three Hundred Corsair Raptor M40 QPAD HeatoN XL E-MU Tracker|pre 
Audio
Beyerdynamic DT-770 250 Ohm 
CPUGraphicsRAMRAM
Intel Ivy Bridge 3210M Intel HD 4000 Graphics Soldered Corsair Vengeance  
Hard DriveOptical DriveOSMonitor
500GB DVD-+RW Windows 7 Professional 1600x900 
  hide details  
Reply
#well
(17 items)
 
Lenovo L530
(8 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 4770k Gigabyte Z87X-UD4H XFX Radeon HD 6950 Corsair CMX8GX3M2A2000C9 
Hard DriveHard DriveOptical DriveCooling
OCZ Agility 3 Hitachi HDS722020ALA330 Generic DVD±RW Burner Noctua NH-D14 
OSMonitorKeyboardPower
Windows 8.1 Dell U2711 Ducky DK9008G2 Overclock.net Edition, Cherry MX... Corsair TX850 
CaseMouseMouse PadAudio
Antec Three Hundred Corsair Raptor M40 QPAD HeatoN XL E-MU Tracker|pre 
Audio
Beyerdynamic DT-770 250 Ohm 
CPUGraphicsRAMRAM
Intel Ivy Bridge 3210M Intel HD 4000 Graphics Soldered Corsair Vengeance  
Hard DriveOptical DriveOSMonitor
500GB DVD-+RW Windows 7 Professional 1600x900 
  hide details  
Reply
post #5 of 6
Thread Starter 
Well I got it working. With your help, and a little testing of my own to figure out what I did wrong. I did an lspci with only 1 card in, and the card was at 2:0:0, so I figured that was the primary card.

I edited my inittab to boot up at runlevel 3, so it would be using my kernel and not the 2.6.29 from my rescue disc which I used to mount my system, so that error wasn't present. Got that same printout about the audit...etc, but it allowed me to login. Tried xinit5, which gave me the error about I have my primary card listed at the PCI bus 2:0:0, when my primary card is located at 3:0:0. Edited my xorg.conf to fix that, tried xinit5 again and showed no errors, so ran init 5 and X started up fine.

Sooo. The long and short is, make sure you absolutely know for sure what bus your primary card is, and add it to your xorg.conf, after you run

Code:
# nvidia-xconfig --damage-events --cool-bits=1 --sli=Auto --multigpu=Auto
Thanks gonx
e-Rep
Deimos
(11 items)
 
Pluto
(18 items)
 
 
CPUMotherboardGraphicsRAM
AMD 1090T Biostar TA890FXE Nvidia GTX 470 Corsair Vengence 
Hard DriveHard DriveHard DriveHard Drive
Samsung 830 MZ-7PC128D/AM Western Digital Black Western Digital Green Western Digital Blue 
CoolingOSOSMonitor
Dtek v2 Water Windows 7 Pro Fedora 16 LG4250 42" LCD TV 
KeyboardPowerCaseMouse
Microsoft Ergo Silverstone ST-1000P Cooler Master Cosmos 1000 Logitech G500 
Mouse PadAudio
X-Trac Ripper Asus D1 
  hide details  
Reply
Deimos
(11 items)
 
Pluto
(18 items)
 
 
CPUMotherboardGraphicsRAM
AMD 1090T Biostar TA890FXE Nvidia GTX 470 Corsair Vengence 
Hard DriveHard DriveHard DriveHard Drive
Samsung 830 MZ-7PC128D/AM Western Digital Black Western Digital Green Western Digital Blue 
CoolingOSOSMonitor
Dtek v2 Water Windows 7 Pro Fedora 16 LG4250 42" LCD TV 
KeyboardPowerCaseMouse
Microsoft Ergo Silverstone ST-1000P Cooler Master Cosmos 1000 Logitech G500 
Mouse PadAudio
X-Trac Ripper Asus D1 
  hide details  
Reply
post #6 of 6
I figured it had something to do with the BusID. Good to hear that you got it solved
#well
(17 items)
 
Lenovo L530
(8 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 4770k Gigabyte Z87X-UD4H XFX Radeon HD 6950 Corsair CMX8GX3M2A2000C9 
Hard DriveHard DriveOptical DriveCooling
OCZ Agility 3 Hitachi HDS722020ALA330 Generic DVD±RW Burner Noctua NH-D14 
OSMonitorKeyboardPower
Windows 8.1 Dell U2711 Ducky DK9008G2 Overclock.net Edition, Cherry MX... Corsair TX850 
CaseMouseMouse PadAudio
Antec Three Hundred Corsair Raptor M40 QPAD HeatoN XL E-MU Tracker|pre 
Audio
Beyerdynamic DT-770 250 Ohm 
CPUGraphicsRAMRAM
Intel Ivy Bridge 3210M Intel HD 4000 Graphics Soldered Corsair Vengeance  
Hard DriveOptical DriveOSMonitor
500GB DVD-+RW Windows 7 Professional 1600x900 
  hide details  
Reply
#well
(17 items)
 
Lenovo L530
(8 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 4770k Gigabyte Z87X-UD4H XFX Radeon HD 6950 Corsair CMX8GX3M2A2000C9 
Hard DriveHard DriveOptical DriveCooling
OCZ Agility 3 Hitachi HDS722020ALA330 Generic DVD±RW Burner Noctua NH-D14 
OSMonitorKeyboardPower
Windows 8.1 Dell U2711 Ducky DK9008G2 Overclock.net Edition, Cherry MX... Corsair TX850 
CaseMouseMouse PadAudio
Antec Three Hundred Corsair Raptor M40 QPAD HeatoN XL E-MU Tracker|pre 
Audio
Beyerdynamic DT-770 250 Ohm 
CPUGraphicsRAMRAM
Intel Ivy Bridge 3210M Intel HD 4000 Graphics Soldered Corsair Vengeance  
Hard DriveOptical DriveOSMonitor
500GB DVD-+RW Windows 7 Professional 1600x900 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux, Unix
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › [Solved] Unable to get SLI up and running