https://bugzilla.kernel.org/show_bug.cgi?id=80331 --- Comment #11 from Colin <colin.bruce@xxxxxxxxxxx> --- (In reply to Alex Deucher from comment #10) > (In reply to Colin from comment #9) > > but it was you that said it always failed to load so I am getting confused > > now. > > > > It is not to do with X because the problem shows up in plain text mode as > > well before X is ever loaded. With the patch installed it won't load any > > fonts other than the default one when it is booting. With the patch removed > > it will with no other changes. > > > > If I undo the patch and make no other changes what so ever it works correctly > > > > If I compile the driver as a module it with no other changes what so ever it > > works correctly. > > > > If I apply the patch and compile the kernel with the driver statically > > linked but no other changes what so ever it works correctly. > > > > I don't see how it can be my setup when the only change to make it work or > > break is that patch. > > I was referring to your setup. All the patch does it move the firmware > loading earlier in the driver init process. So if the firmware loading > fails with the patch applied, it should also fail without it asuming > everything else is the same in your setup. Something is wrong with your > local configuration such that the firmware is not availabl at driver load in > some cases. The firmware is required to use acceleration in the driver. I've built three versions of the same kernel 3.15.4. The first is the standard kernel including the patch with the radeon driver built as a module. The second is the kernel with the radeon driver statically linked and the third is also statically linked but this time with that patch removed. I've booted from each kernel and made copies of the output from dmesg, the output of setfont and the Xorg log file. I've put the 9 files in a zip file and attached it. The names of each file will tell you what they are. I think your suggestion is correct. With the patch applied something is not ready that prevents the firmware from being loaded. Without the patch or with the driver loaded as a module the firmware loads every time. Loading as a module will presumably mean that it tries to access the firmware file later in the boot process. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
