On 12/05/10 16:26, Andy Walls wrote: <snip> > This explanation is consistent with Dale Pontius' occasional red screen > problem after boot up, if we assume things in the kernel occasionally > get initialized or allocated in a different order on boot up. <snip> > Dale, > > Do you use Ubuntu and/or the nv driver in your machine? > Just saw this thread and my name in it, sorry for taking so long to respond. Everything I've run MythTV on so far has used the nvidia drivers. All of my systems run Gentoo. For a while both of my kids were running Ubuntu 9.04, and I believe I moved them both to the proprietary binaries. When I installed those systems nouveau was nowhere near ready, and nv was just too slow.
I just realized that nothing on a client machine matters - you're looking for interactions on the backend machine. My backend machine has 2 hvr-1600s, an nVidia 6200 running Gentoo's "stable" driver selection, currently 260.19.29. I also have "vmalloc=256MB" on the kernel command line. Oh, and some time back, perhaps late spring, I moved to in-kernel drivers for the hvr-1600s. (If you need more info, just let me know.) Incidentally, I don't believe I've had any red-screen problems since this past summer. I don't appear to have enough kernel history laying around, but I believe they stopped somewhere around 2.6.34 or 2.6.35. Nor is it easy to time-slide a level of nvidia-drivers, either. I never noticed exactly when they stopped - it's one of those things where one day it dawns on you that something annoying is gone. By the same token, I haven't had the silent audio problem on either hvr-1600 recently, either. Again, I don't have an exact date, but it kept happening after the red-screen stopped. It may well have stopped when I started running 2.6.36. I don't believe the disappearance of that problem time-aligns well with any nvidia-drivers update. Dale _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
