6 May
2012
6 May
'12
1:43 p.m.
That for a shared IRQ the graphics will become an unwanted high prio
doesn't happen with a kernel 2.6.31-rt19 + NVIDIA 195.36.15 on Suse 11.2
on my machine.
As already reported, it also doesn't happen with the kernels
3.0.23-avl-7-pae (threadirqs) and 3.0.23-rt40 on current AV Linux, where
still the nv driver is available and used on my machine.
IIUC it's definitive related to the kernel, I anyway will test the vesa
driver with Ubuntu Studio Precise, but can' get it working.
I modified the xorg.conf I use with the nvida driver, startup ends with
tty, no X. Does anybody notice what I might have missed?
Latest modification:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Module"
#Load "glx"
#Load "dbe"
#Load "dri2"
#Load "extmod"
#Load "record"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
Option "XkbVariant" "ro"
Option "XkbOptions" "lv3:ralt_switch"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
DisplaySize 305 230
HorizSync 29-98
VertRefresh 50-120
#modeline "1152x864" 128.42 1152 1232 1360 1568 864 865 868 910
#Gamma 1.0
EndSection
Section "Device"
Identifier "Card0"
Driver "vesa"
#Option "Coolbits" "1"
#Option "AddARGBGLXVisuals" "true"
#Option "TripleBuffer" "false"
#VendorName "nVidia Corporation"
#BoardName "G72 [GeForce 7300 SE/7200 GS]"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
#Viewport 0 0
#Depth 24
#Modes "1152x864"
#Virtual 3840 1200
EndSubSection
EndSection
#Section "Extensions"
# Option "Composite" "enable"
#EndSection
Regards,
Ralf
PS: If there won't be an rtirq script able to handle it or any other way
to do it, I hadn't time to test until now, I'll simply will use a kernel
<= 3.0 instead > 3.0.