general question: xorg & Nvdriver

[Florian Lier]

Hey Beso,

thank you! I'll give it a try!
I wrote a start script for X maybe I'll add a modprobe line...

#!/bin/bash

## MPX RUN() Script v1.0 by  ##

LIBEX="/home/fl0/mpxcompiz/lib"
CONFPATH="/home/fl0/mpxcompiz/xorg.conf"
MPXPATH="/home/fl0/mpxcompiz/bin/Xorg"
DRMPATH="/home/fl0/mpxcompiz/drm/linux-core/drm.ko"

echo "+++ MPX Startscript V 0.1 +++"

/etc/init.d/gdm stop

echo "removing standard DRM Module"

sleep 3

rmmod drm
 
echo DRM_PATH is: $DRMPATH

sleep 4

insmod $DRMPATH

echo LD_LIBRARY_PATH is: $LIBEX

export LD_LIBRARY_PATH=$LIBEX

echo Starting Server on Display 2

sleep 4

startx -- $MPXPATH :2 -config $CONFPATH -verbose

exit

#proper way to leave a script

Beso wrote:
> 2009/1/28 Florian Lier <fl0 at icram.de>:
>   
>> Hey all,
>>
>> I'm trying to get the current (X.Org X Server 1.6.99.1) "X" running on
>> several "test-systems" for like 2 or 3 months now. (for mpx purposes)
>> I tested several systems with ATI, INTEL and NVIDIA gcards...
>> The most "difficult" system seems to be the one with NVIDIA cards.
>> As far as I can interpret the backtrace there is always a problem with the
>> nv driver.
>>
>> Backtrace:
>> 0: /home/fl0/mpxcompiz/bin/Xorg(xorg_backtrace+0x3b) [0x80e829b]
>> 1: /home/fl0/mpxcompiz/bin/Xorg(xf86SigHandler+0x51) [0x809ccb1]
>> 2: [0xb7f78400]
>> 3: /home/fl0/mpxcompiz/bin/Xorg(xf86SetDesiredModes+0x27b) [0x80ab18b]
>> 4: /home/fl0/mpxcompiz/lib/xorg/modules/drivers//nv_drv.so [0xb7a6412c]
>> 5: /home/fl0/mpxcompiz/lib/xorg/modules/drivers//nv_drv.so [0xb7a64562]
>> 6: /home/fl0/mpxcompiz/bin/Xorg(AddScreen+0x19d) [0x80684ad]
>> 7: /home/fl0/mpxcompiz/bin/Xorg(InitOutput+0x23a) [0x808b12a]
>> 8: /home/fl0/mpxcompiz/bin/Xorg [0x8068ba1]
>> 9: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b19685]
>> 10: /home/fl0/mpxcompiz/bin/Xorg [0x8068231]
>>
>>     
> try manually modprobing drm and the nv driver before starting xorg.
> i've been having a very similar issue with radeon driver for a long time
> and the only workaround is modprobing the modules before startup.
> i've learned about this workaround from another user who had the
> same issues with the intel driver.
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg/attachments/20090128/ff71983c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fl0.vcf
Type: text/x-vcard
Size: 274 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20090128/ff71983c/attachment.vcf>