On Wed, Jul 21, 2010 at 12:25:38 +0200, Aleix Conchillo Flaqué wrote: > On 07/21/2010 11:45 AM, Julien Cristau wrote: > >On Wed, Jul 21, 2010 at 10:41:56 +0200, Aleix Conchillo Flaqué wrote: > >> > >>The solution that works for me is to force loading the radeon module in > >>/etc/modules. > > > >This should not be necessary, udev should autoload radeon on boot. Can > >you attach dmesg after removing radeon from /etc/modules? > > > > From the dmesg timings, I can see that the drm initialization starts > at [ 9.797560] when radeon module loaded in /etc/modules (see drm > messages in original bug). From the dmesg output below, I see that > drm initialization starts at [ 22.688394]. So, it seems to me that > udev is not loading the driver properly. I can easily detect this, > because when radeon module is loaded properly before X, the text > mode resolution changes. > > Also, if I boot with (recovery mode), the radeon module is not > loaded (only if added in /etc/module). > That's weird... Can you get the contents of /sys/bus/pci/devices/0000:01:00.0/modalias, make sure it looks like pci:v00001002d000095C4sv00001043sd000019D3bc03sc00i00 and then give us the output of /sbin/modprobe -R -b $modalias. This *should* show radeon. If not then something's screwy in your modprobe config. If yes then I don't understand why udev isn't loading it.
Cheers, Julien
signature.asc
Description: Digital signature