On 01/25/10 13:11, Michel Dänzer wrote: > On Sun, 2010-01-24 at 15:00 +0000, Dick Middleton wrote: >> Julien Cristau wrote: >> >>>> Following upgrade DRI is no longer enabled for display: >>>> >>>> (WW) RADEON(0): Direct rendering is not supported when VGA arb is >>>> necessary for the device >>>> (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. >>>> >>> This is fixed with kernel mode setting, AIUI. I don't think it will be >>> fixed for userspace mode setting. >> >> Thanks for that. radeon.modeset=1 kernel option works. However I get >> no output on VTs. > > That's usually due to one of two things: > > * Your X driver doesn't support KMS (none of the radeon driver > packages in Debian do, only upstream Git master), so it's > touching the hardware directly behind the kernel's back. > * The fbcon kernel module isn't loaded.
I can't fathom it all out! With modeset=1 DRI is still disabled (not supported) but rendering performance is significantly improved. However I get no VTs. If I set framebuffer and modeset=1 I can switch to a VT once; if I switch back to X then back to VT I get no visible output. Framebuffer (radeonfb) doesn't seem to work with modeset=1. With modeset=0 framebuffer VTs work but X rendering is slow. Anyway, if there's support for radeon KMS in GIT I'll wait for next release. Many thanks for your pointers. Dick -- Dick Middleton d...@lingbrae.com PGP Key ID: 0x9F9434FD -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
