On Sun, Nov 23, 2014 at 7:28 PM, Ken Moffat <[email protected]> wrote:
> On Sun, Nov 23, 2014 at 05:43:29PM -0600, Bruce Dubbs wrote: > > Patrick Kennedy wrote: > > >In fact, I did recompile my kernel for the "Xorg ATI Driver-7.3.0". > When > > >the system boots up, you can see a boot message complaining about not > > >having the fireware for the Radeon video driver. The problem is, the > web > > >page for Radeon firmware ( > http://people.freedesktop.org/~agd5f/radeon_ucode/) > > >has names like Aruba and Hawaii, et al. > > > > > >And I've got a Dell Vostro 3450 that ran Ubuntu when first purchased. > So, > > >it's hard to know what firmware is required. > > > > > >Anyways, definitely learning lots with LFS and BLFS. But it should > would > > >be cool to get X Window up. > > > > http://wiki.gentoo.org/wiki/Radeon#Firmware > > https://packages.debian.org/wheezy/firmware-linux-nonfree > > > > may be helpful. I didn't see a 6600M though. Try lspci -v for details. > > > > -- Bruce > > > > > For me, google suggests it is an HD6630, which is apparently a > hybrid graphic driver. I guess that might mean the server needs > the prime support patch, but that is _only_ a guess. > > Based on > https://packages.debian.org/squeeze-backports/firmware-linux-nonfree > I would try the set of TURKS files. Actually, for installing I > would probably try dumping *all* the radeon firmware ins > /usr/lib/firmware, point the kernel to it, and then start by adding > all the TURKS files, build and boot the new kernel, review, and if > necessary repeat with additional or different firmware (depending on > what the dmesg or messages during the boot say). So, do not throw > away the kernel tree between builds, making a small change should be > much faster on an already compiled kernel tree. > > ĸen > -- > Nanny Ogg usually went to bed early. After all, she was an old lady. > Sometimes she went to bed as early as 6 a.m. > -- > http://lists.linuxfromscratch.org/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > > Okay, so I downloaded TURKS_mc.bin, TURKS_me.bin, TURKS_pfp.bin, and TURKS_smc.bin. I added radeon directory to /lib/firmware, and copied the TURKS files into /lib/firmware/radeon. I then tweaked the kernel as follows: Device Drivers ---> Generic Driver Options ---> -*- Userspace firmware loading support [*] Include in-kernel firmware blobs in kernel binary (radeon/TURKS_mc.bin radeon/TURKS_me.bin radeon/TURKS_pfp.bin radeon/TURKS_smc.bin) (/lib/firmware) Firmware blobs root directory I noticed this: Device Drivers --> Graphics Drivers Options --> [*] Prevent firmware from being built Soooo, I unchecked this: [ ] Prevent firmware from being built Then I added this: Device Drivers ---> Graphics support ---> Direct rendering Manager ---> ATI Radeon: Y or M But here's my output error message: <...snip...> LD sound/usb/caiaq/built-in.o LD sound/usb/hiface/built-in.o LD sound/usb/misc/built-in.o LD sound/usb/usx2y/built-in.o LD sound/usb/built-in.o CC sound/last.o LD sound/built-in.o MK_FW firmware/radeon/TURKS_mc.bin.gen.S make[1]: *** No rule to make target 'firmware/radeon/TURKS_mc.bin', needed by 'firmware/radeon/TURKS_mc.bin.gen.o'. Stop. Makefile:901: recipe for target 'firmware' failed make: *** [firmware] Error 2 Some how, it's not finding additional files, such as *.S noted above. If I change the TURKS files to compile just one of them, the error changes, where different files missing, such as *.o, etc. How to I ensure that the TURKS files are "available" when compiling them? I think I'm very close, given per previous input from Dubbs and Moffat. Also, maybe the Evergreen firmware is better for my HD6600M than the TURKS / Northern Islands as suggested, because http://wiki.gentoo.org/wiki/Radeon#Firmware notes "all HD6xxx not listed under Northern Islands" on the Evergreen row. Any ideas on how to find the various file components, such as *.S, and is Evergreen firmware perhaps better than Northern Islands (TURKS)? Thanks!
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
