On Mon, May 14, 2012 at 09:19:02PM +0200, Josip Rodin wrote:
> > dmesg can't tell you why the kernel module wasn't loaded by udev.
>
> But it *was* loaded by udev. I don't run 'modprobe radeon' at any point
> between the two tests. After the broken startx, it's loaded, which is why
> it is in the dmesg output I sent you.
>
> > Usually it's due to a stale blacklist entry in the udev/modprobe
> > configuration.
>
> I went looking for that and found fglrx-driver's file, from the removed but
> not purged package. I purged it (from the console), then did the first
> startx, and the same thing happened again - I had to run startx twice.
It didn't apply immediately, but it had effect after the next reboot -
during it, radeon was apparently pre-loaded automatically. After that,
it only took one startx to start X.
So it looks like when it's missing, X gets it loaded, but not fast enough to
apply to the same session...?
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120514193321.ga7...@entuzijast.net
