initrd probably doesn't know about custom .conf file in /etc/modprobe.d. Updating initrd (with command I provided) should solve this problem.
In front of every dmesg line is the time when it was generated (in seconds since kernel boot-up). IMO more than 30 seconds means, that KMS wasn't enabled till X (radeon module is loaded on my system in 4 seconds).
This kernel cmdline doesn't work for me now (it worked before), and it may be the case for you too. However, I appended "video=radeon:modeset=1" to my cmdline, which initrd interprets and modprobe's radeon module with correct arguments (modeset=1) before root is mounted, and that's ok for X.
I think you should run update-initramfs first and see if it solves the problem. If not, try this cmdline argument.
There is unfortunately another issue. Newest initramfs-tools doesn't enable FRAMEBUFFER (including drm modules, like radeon) by default. You must enable it explicitly, by pasting `FRAMEBUFFER=y' to /etc/initramfs-tools/initramfs.conf. It is the case for ubuntu for sure, I don't know if debian is also affected (try grepping /usr/share/initramfs-tools/hooks/framebuffer for "OPTION=FRAMEBUFFER").
And don't forget about update-initramfs (as root) after every initrd-related change (like initramfs.conf change or new file in /etc/modprobe.d).
In front of every dmesg line is the time when it was generated (in seconds since kernel boot-up). IMO more than 30 seconds means, that KMS wasn't enabled till X (radeon module is loaded on my system in 4 seconds).
This kernel cmdline doesn't work for me now (it worked before), and it may be the case for you too. However, I appended "video=radeon:modeset=1" to my cmdline, which initrd interprets and modprobe's radeon module with correct arguments (modeset=1) before root is mounted, and that's ok for X.
I think you should run update-initramfs first and see if it solves the problem. If not, try this cmdline argument.
There is unfortunately another issue. Newest initramfs-tools doesn't enable FRAMEBUFFER (including drm modules, like radeon) by default. You must enable it explicitly, by pasting `FRAMEBUFFER=y' to /etc/initramfs-tools/initramfs.conf. It is the case for ubuntu for sure, I don't know if debian is also affected (try grepping /usr/share/initramfs-tools/hooks/framebuffer for "OPTION=FRAMEBUFFER").
And don't forget about update-initramfs (as root) after every initrd-related change (like initramfs.conf change or new file in /etc/modprobe.d).
Comment