Dear Maintainer,

Since last upgrade from 1:6.14.4-8 to 1:7.2.0-1 X does not start for me.
I've tried moving my custom xorg.conf out of the way but to no avail.
I've also tried using an old linux kernel, also unsuccessfully, that's
why I'm filing the bug here.

Please tell me if you need more info, however my availibity may be
scarce for the next week. The comments on xorg.conf are from 2010 where
I had another issue and tried some alternative configurations, I tested
the other Screen directives on ServerLayout, they didn't work either
but for reasons apparently unrelated (fglrx not supporting my chipset
anymore, vesa complaining about "No matching modes").

The computer is a 5-year-old Samsung R60+ laptop using a Radeon X1250.

[...]

[...]

Looks like the radeon kernel module doesn't get loaded before X starts.
Current upstream xf86-video-ati only works with the radeon kernel module
loaded in KMS mode.

Maybe some leftover from fglrx is preventing the radeon kernel module
from getting loaded.

El Dimecres, 4 de setembre de 2013, a les 12:47:32, Michel Dänzer va escriure:

I have no fglrx packages installed, however I purged them to try to get rid of
possible leftovers. That didn't work.

Then I manually loaded the radeon module using modprobe, expecting some sort
of error or more clues, but it worked. After this and a kdm restart,
everything seems back to normal.

For some reason, xorg does not load (or tries to and fails) the readon kernel
module. I added radeon to /etc/modules so it's loaded at every startup, which
it does earlier at boot, noticeable due to the smaller console font.

If you consider appropiate, I am willing to do some tests on my machine to
check why the radeon module is not automatically loaded, but please tell me
how to proceed (I am almost clueless about kernel whereabouts). If not, for me
the problem is solved and the bug may be closed.

Thank you for your help :-)

Did you reboot after purging the fglrx stuff?
Check for any blacklist in /etc/modprobe.d/ maybe.

Cheers,
Julien

El Dimecres, 4 de setembre de 2013, a les 22:41:56, Julien Cristau va
escriure:

Yes. In fact, I did reboot after a manual "modprobe radeon" and found myself
in the same situation: xorg didn't insert the module on its own, and after
running again modprobe it started. That's when I put it in /etc/modules.

entfe001@portatil2:~$ grep radeon /etc/modprobe.d/*
/etc/modprobe.d/fbdev-blacklist.conf:blacklist radeonfb
/etc/modprobe.d/radeon-kms.conf:options radeon modeset=1

OTOH all but one of the uncommented blacklists come from fbdev-blacklist and
all its modules end with fb. The other one is at alsa-base-blacklist.conf and
blocks snd-pcsp.