<BR>
Thanks Paul,<BR>
<BR>
and others for replying to the post.<BR>
<BR>
I'm tring to run the nvidia 180.60 installer script using the Sidux smxi update script. This is the Sidux standard way to upgrade the system, and add proprietary drivers and fixes. The script handles various versions of the nvidia driver and is tested to work against an updated Sidux installation.<BR>
<BR>
As far as I can see from the error mesages, nvidia is failing to load because of resource conflicts:<BR>
<BR>
snip dmesg:<BR>
<BR>
IRQ 18/nvidia: IRQF_DISABLED is not guaranteed on shared IRQs<BR>
ioremap: invalid physical address 7fca82000000<BR>
NVRM: RmInitAdapter failed! (0x26:0xffffffff:1091)<BR>
NVRM: rm_init_adapter(0) failed<BR>
<BR>
...<BR>
<BR>
so I suspect a kernel option is causing the problem before the driver even attempts to load. I'm going to do a diff of the ubuntu 2.6.28 config and the sidux one to see what might be different.<BR>
<BR>
I can't see that any special grub kernel flags, or nvidia module options are being loaded that might cause a problem.<BR>
<BR>
In any case, the error suggests that it is not a glx issue, and is probably due to buggy hardware.<BR>
<BR>
Thanks also to all who replied for tips and views on running an unstable system.<BR>
<BR>
Sid is indeed called unstable for a reason, and I wouldn't trust a bank who used it. I consider my Mythbox a toy really. It's fun to get stuff working in a non-standard way. Sometimes it's broken, and sometimes it works, but it's always fun :-)<BR>
<BR>
Sidux has been stable for me since I migrated to it when the "Kanotix" team imploded. This is the first time it hasn't worked for my hardware, and as long as I follow the upgrade procedures, I've never had a broken system, despite it being based on current Sid.<BR>
<BR>
Debian Experimental is indeed just what it says on the box.<BR>
<BR>
Cheers!<BR>
<BR>
Marius<BR>
<BR>
<BR>
<BR>
<span style="font-weight: bold;">On Wed Jun 3 20:22 , Paul Gallaway <pgallaway@gmail.com> sent:<BR>
<BR>
</pgallaway@gmail.com></span><blockquote style="border-left: 2px solid rgb(245, 245, 245); margin-left: 5px; margin-right: 0px; padding-left: 5px; padding-right: 0px;">Marius, what driver version are you using? Debian (or maybe Nvidia?)<BR>
recently changed the way the driver is packaged. I found out when I<BR>
had breakage on a Lenny system when I failed to correctly load the<BR>
module after an update. You need to make sure you have the nvidia-glx<BR>
package installed before doing the nvidia-source compile. Not sure how<BR>
the Sidux scripts handle this but I was able to compile the Sid 180.44<BR>
libraries by repository pinning on a Lenny (and also Squeeze) system.<BR>
It was the upgrade to kernel 2.6.26-2 that broke my compiling system<BR>
requiring the installation of the additional nvidia-glx package.<BR>
<BR>
On Wed, Jun 3, 2009 at 9:50 AM, Johnny <<a href="javascript:top.opencompose('jarpublic@gmail.com','','','')">jarpublic@gmail.com</a>> wrote:<BR>
<span style="color: red;">> Being up to date is probably the primary difference between Debian and</span><BR>
<span style="color: red;">> Ubuntu. Ubuntu is on a relatively rapid update schedule (every six</span><BR>
<span style="color: red;">> months) compared to Debian (when its done).</span><BR>
<BR>
This is true for Stable, but there's more to it than that. However,<BR>
Debian development consists of three main branches; stable (currently<BR>
Lenny), testing (currently Squeeze) and unstable (always called Sid).<BR>
There's also an experimental branch I've seen mentioned but not quite<BR>
certain what it is - but assume that it is the unstable version of<BR>
unstable...<BR>
<BR>
Stable, is what it is. It doesn't rock the boat and mainly receives<BR>
updates for security. Much like the MythTV fixes branch you don't see<BR>
new features added here. Not the same as the LTS releases but probably<BR>
the same target users.<BR>
<BR>
Unstable is a rolling architecture, no release, never frozen - the<BR>
best you can hope for is a snapshot. This is the bleeding edge and<BR>
this is the basis for the Ubuntu release. Some, but not all, of the<BR>
Ubuntu code will make it back upstream into Unstable, but Unstable is<BR>
a constantly moving target.<BR>
<BR>
Testing is both a rolling architecture, and at some unknown point it<BR>
will be frozen more like the Stable branch. When a package is stable<BR>
enough in Sid it moves into testing. When it's frozen updates will be<BR>
limited to bug fixes and patches much like stable. When it reaches an<BR>
acceptable threshold it is pushed out as the new Stable branch,<BR>
testing is unfrozen and updates from Sid start dripping in again.<BR>
<BR>
This is of course the poor man's Cole's Notes version. See Debian.org<BR>
for more info.<BR>
<BR>
I've actually switched from Debian to Ubuntu and now back to Debian.<BR>
<BR>
<BR>
-- <BR>
~pAul.<BR>
<BR>
all good things. all in good time.<BR>
_______________________________________________<BR>
mythtv-users mailing list<BR>
<a href="javascript:top.opencompose('mythtv-users@mythtv.org','','','')">mythtv-users@mythtv.org</a><BR>
<a href="parse.pl?redirect=http%3A%2F%2Fmythtv.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fmythtv-users" target="_blank"><span style="color: red;">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</span></a><BR>
</blockquote><BR>