On Thu, 2004-01-15 at 11:50, Chris Anderson wrote: > On Wed, 2004-01-14 at 11:30, Sven Luther wrote: > > On Wed, Jan 14, 2004 at 11:10:34AM -0500, Chris Anderson wrote: > > > On Wed, 2004-01-14 at 10:53, Sven Luther wrote: > > > > On Wed, Jan 14, 2004 at 10:47:15AM -0500, Chris Anderson wrote: > > > > > I'm using a heavily modified defconfig from benh's 2.6.1-rc1 tree. > > > > > > > > Well, first i hope to be making 2.6 powerpc kernels soon, and second, i > > > > guess you should just build the drm modules of your kernel sources, > > > > should be ok. You could even have them builtin. > > > > > > Am I correct to assume the config vars I need are CONFIG_DRM and > > > CONFIG_DRM_RADEON? Also, once those are built does that mean I should > > > > Yep. you can even have them builtin if i remember correcly. > > > > > remove the DRI section of my XF86Config-4 until I get DRI properly > > > working (perhaps by setting up the dri-trunk debs)? > > > > you just have to remove the #load "dri" line to disable the dri. > > Good to know, I'll give this a try when I have some time today.
Ok, I had a chance to rebuild the kernel and try it out with CONFIG_DRM=y and CONFIG_DRM_RADEON=y. I also moved radeonfb to a module and removed the load line for DRI from my XF86Config. Now if I build CONFIG_DRM_RADEON into the kernel (or load the radeon module built) and then start X I get my normal X session except it looks almost like there are scanlines in the display. They move around and if I exit X it looks like the display just smears, any files I have open after this seem to get corrupted and filled with ^@ sometimes (ex: my XF86Config-4 and my pan config files). At this point I'm out of ideas for what to do next. > > > > Friendly, > > > > Sven Luther > > >