Re: [blfs-dev] KMS, Gallium, kernel firmware, etc.

2012-04-15 Thread Armin K.
On 04/15/2012 09:43 AM, DJ Lucas wrote:
 After an annoying battle with Gallium, KMS, firmware, etc. on my
 new(ish) system, I think we should probably cover this in the book
 someplace, but I'm not sure how to go about adding it. For starters,
 where does it belong, in Post LFS or in Xorg? I'd be happy to add a
 page, but I'm not at all familiar enough to do so yet.

 For instance, I have a card that is identified as an HD 5400 Cedar Pro
 (it was cheap and I have no need for a monster graphics card). After
 building in first one at a time, and then all of the CEDAR_*.bin files,
 I was still greeted with a ~30 second delay on boot up, and no DRI2 each
 time. As a last ditch attempt, I attempted to include all of the bin
 files in the radeon subdirectory and found that oldconfig choked on it
 and prompted me. I randomly built in the first 9 files (alphabetically)
 which included the CEDAR blobs and it worked, but I have absolutely no
 idea why! Everything I've managed to find has told me that building in
 the CEDAR_*.bin files should be enough.

 I plan to reduce that list later, but I'm on a Java trip now that Gnome
 is working sufficiently well. Perhaps I've simply lost my Google touch,
 but I'm not convinced that good documentation even exists yet! Anybody
 got a pointer? Perhaps a link in the xorg configuration will handle it
 until concise documentation can be produced for the book? Maybe it would
 be better to recommend building the vendor DRM driver only as a module,
 and to install all the firmware in /lib/firmware (I haven't actually
 tried this, but I found documentation that said Xorg would tell you the
 needed file in the log if DRM is a module)? Suggestions?

 -- DJ Lucas



I personaly find it easier to build everything but the stuff that is 
necesary for boot as modules since I want to run one kernel on several 
machines. I did not notice any speed performance with those builtin, 
only failures with Xorg (long time ago, when I was still fresh).

And since firmware is not available in kernel source tree, thus it can't 
be builtin by default, I agree to suggest building DRM drivers as 
modules, since it is lot easier just to put firmware in /lib/firmware 
instead of rebuilding whole kernel. That is the problem with newer 
nouveau cards, since they require firmware not in the kernel, too.
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-dev] KMS, Gallium, kernel firmware, etc.

2012-04-15 Thread DJ Lucas
On 04/15/2012 05:33 AM, Andrew Benton wrote:

 I think we should add a section about kernel config to one of the xorg
 pages, maybe xorg-server? It's xorg-server that needs KMS enabled.


Well, not exactly. The framebuffer console is very nice to work in as 
well, and that was the reason for the question. Placement would quite 
obviously be limited to the xorg section if not for the FB. If it were 
limited to Xorg, the xorg-server page makes more sense to me than the 
generic Xorg configuration pages as was done in the past.


  Maybe there was a typo in one of the names? No, the kernel make would
 barf with a file not found error. Did you use CEDAR_*.bin globing in
 your kernel config?
No, like you said, the build would have stopped. It was exactly as you 
have below, that's why I'm still unsure as to why it is working now. The 
big thing that bothers me is that I found out about compiling in the 
microcode/firmware into the kernel from the Gentoo and Arch wikis, not 
from the ATI page at freedesktop.org's wiki.
 There seem to be 3 CEDAR bin files:
 andy@doughnut:~$ ls /lib/firmware/radeon/CE*
 /lib/firmware/radeon/CEDAR_me.bin
 /lib/firmware/radeon/CEDAR_rlc.bin
 /lib/firmware/radeon/CEDAR_pfp.bin

 CONFIG_EXTRA_FIRMWARE=radeon/CEDAR_me.bin radeon/CEDAR_rlc.bin 
 radeon/CEDAR_pfp.bin
 CONFIG_EXTRA_FIRMWARE_DIR=/lib/firmware

 Yes, I think that's the way to go. Install the linux firmware:
 http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=summary
 If you put it in /lib/firmware so you don't have to keep copying it
 into the kernel source every time you recompile.
 Start by compiling the kernel as a module, boot and then:
 dmesg | grep radeon
 or
 dmesg | grep firmware
 Then recompile with the firmware compiled into the kernel so you get
 KMS, framebuffer, penguins and nice fonts right from the start.

Okay, so that has been tested then. I will revisit this a little later 
and do the same. Intel and Nvidia users have the same issues, or is this 
limited to Radeon devices?

-- DJ Lucas

-- 
This message has been scanned for viruses and
dangerous content, and is believed to be clean.

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page