Mick, Thanks for your response and suggestion !
When compiled the new kernel, there was no error message. I can use the new kernel to boot my laptop successfully. So that I am sure that the relative firmware filenames I gave are correct. I will try another kernel version or Evergreen firmware this weekend. Thank you ! Regards, Phil On Sun, Mar 27, 2016 at 12:47 AM, Mick <[email protected]> wrote: > On Sunday 27 Mar 2016 00:23:21 JingYuan Chen wrote: > > Hello, > > > > I had installed Gentoo in my laptop successfully last weekend. My laptop > > is Toshiba Satellite L840. I found that my VGA card is Radeon HD 7670M > > using "lspci -k" command. Therefore, I refer to Gentoo's Radeon wiki page > > to configure 4.1.15-r1 kernel with TURKS firmware and emerge > linux-firmware > > atom. > > > > However, my new kernel can not load TURKS successfully. I notice that > there > > is an error message with DRM in dmesg's output. It shows > > [drm:evergreen_init] *ERROR* Failed to load firmware. > > So the kernel *wants* to load the Evergreen firmware blobs. > > > > Why Evergreen ? Is not Northern Islands ? I am sure that the filename I > > gave is TURKS's firmware in menuconfig. > > Sure, but the kernel seems to think that the hardware is evergreen for some > reason. The Radeon HD 7670M apparently is based on the same chipset as > Radeon > HD 6650M: > > http://www.notebookcheck.net/AMD-Radeon-HD-7670M.69483.0.html > > so it may be that the foundry it came out of was of an Evergreen batch. > > > > How could I make the dmesg's error message more verbose to debug ? > > > > Are there some configurations should I check again ? > > > > p.s. I built it in kernel not in modules. > > > > Any advice would be greatly appreciated. > > > > Regards, > > Phil > > I would first check that you have in your menuconfig the complete space > separated Turks stanza: > > radeon/BTC_rlc.bin radeon/TURKS_mc.bin radeon/TURKS_me.bin > radeon/TURKS_pfp.bin radeon/TURKS_smc.bin radeon/SUMO_uvd.bin > > and make sure there are no misspellings in there. If it still complains, > then > replace these with the Evergreen (or whatever dmesg complains about) and > try > booting again. > > BTW, have you tried booting different kernels, or LiveISOs to see what they > detect the hardware as? > > -- > Regards, > Mick
