<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Okay, new problem:<br>
<br>
I tried to "insmod" the nvdriver...this is the result:<br>
<i><br>
insmod: error inserting 'drm/linux-core/nv.ko': -1 Unknown symbol in
module<br>
<br>
</i>Any suggestions? <br>
<br>
Cheers, florian<i><br>
<br>
<br>
</i><br>
Beso wrote:
<blockquote
cite="mid:d257c3560901281125ye8a1c7aj8768afd29ec2d29e@mail.gmail.com"
type="cite">
<pre wrap="">2009/1/28 Florian Lier <a class="moz-txt-link-rfc2396E" href="mailto:fl0@icram.de"><fl0@icram.de></a>:
</pre>
<blockquote type="cite">
<pre wrap="">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]
</pre>
</blockquote>
<pre wrap=""><!---->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.
</pre>
</blockquote>
<br>
</body>
</html>