On Wed, 2004-01-14 at 15:36, Michel Dänzer wrote: > On Thu, 2004-01-15 at 20:27, Chris Anderson wrote: > > > > 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 > > Why? You need it.
I was under the impression having both the radeonfb driver and radeon driver loaded at the same time would cause a problem. > > > and removed the load line for DRI from my XF86Config. > > Why, don't you want to enable the DRI? > > > Now if I build CONFIG_DRM_RADEON into the kernel (or load the radeon > > module built) > > That shouldn't matter unless you enable the DRI. > > > 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). > > You're saying it locks up, and the filesystem is corrupted after the > reboot? Yes, X locks (and I get the ugly smearing effect) and I have to reboot. Sometimes files are corrupted when I check them after rebooting. This only seems to affect files that were accessed from within X however. > > > At this point I'm out of ideas for what to do next. > > Try my dri-trunk-sid packages, or in the not unlikely event that I'm > misunderstanding you, please state clearly what you are trying to > achieve and provide the relevant information. Should I downgrade to the sid XFree86 or install the dri-drunk-sid packages over the experimental 4.3 server? As for what I'm trying to achieve, my goal is to get the radeon X driver working with 3d acceleration. > > > -- > Earthling Michel Dänzer | Debian (powerpc), X and DRI developer > Software libre enthusiast | http://svcs.affero.net/rm.php?r=daenzer >
