On Mon, Nov 11, 2013 at 05:41:55PM +0100, Marc Joliet wrote:
> Am Mon, 11 Nov 2013 16:03:23 +0100
> schrieb Elias Diem <pub.li...@webconect.ch>:
> 
> > Hi Bruce
> > 
> > On 2013-11-11,  Bruce Hill wrote:
> > 
> > > If you have CONFIG_DRM_RADEON=m, and
> > > CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/", then the kernel will pick the
> > > right firmware automatically, without having to name the microcode in
> > > CONFIG_EXTRA_FIRMWARE at all.
> > 
> > Yes, thank you. It worked.
> > 
> > > Build your kernel that way and see which firmware shows up issuing:
> > > dmesg | grep -i firmware
> > 
> > Unfortunately I can't figure it out.
> > 
> > 'dmesg | grep -i firmware' doesn't return anything.
> 
> You need to grep for "microcode", not "firmware". On my system I see:
> 
> % dmesg |grep -i microcode
> [   18.890581] [drm] Loading RV730 Microcode
> 
> > 'dmesg | grep -i radeon' returns:
> > 
> > <snip>
> > [    0.030492] smpboot: CPU0: AMD A8-5500B APU with Radeon(tm) HD Graphics 
> > (fam: 15, model: 10, stepping: 01)
> > [    4.600599] [drm] radeon kernel modesetting enabled.
> > [    4.601157] radeon 0000:00:01.0: VRAM: 768M 0x0000000000000000 - 
> > 0x000000002FFFFFFF (768M used)
> > [    4.601159] radeon 0000:00:01.0: GTT: 512M 0x0000000030000000 - 
> > 0x000000004FFFFFFF
> > [    4.601693] [drm] radeon: 768M of VRAM memory ready
> > [    4.601694] [drm] radeon: 512M of GTT memory ready.
> > [    4.881482] radeon 0000:00:01.0: WB enabled
> > [    4.881485] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 
> > 0x0000000030000c00 and cpu addr 0xffff880223f0dc00
> > [    4.882218] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 
> > 0x0000000000075a18 and cpu addr 0xffffc900114b5a18
> > [    4.882220] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 
> > 0x0000000030000c04 and cpu addr 0xffff880223f0dc04
> > [    4.882222] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 
> > 0x0000000030000c08 and cpu addr 0xffff880223f0dc08
> > [    4.882223] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 
> > 0x0000000030000c0c and cpu addr 0xffff880223f0dc0c
> > [    4.882225] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 
> > 0x0000000030000c10 and cpu addr 0xffff880223f0dc10
> > [    4.882245] radeon 0000:00:01.0: irq 45 for MSI/MSI-X
> > [    4.882255] radeon 0000:00:01.0: radeon: using MSI.
> > [    4.882534] [drm] radeon: irq initialized.
> > [    5.023269] [drm] Radeon Display Connectors
> > [    5.044982] [drm] radeon: power management initialized
> > [    5.165005] fbcon: radeondrmfb (fb0) is primary device
> > [    5.231602] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device
> > [    5.231604] radeon 0000:00:01.0: registered panic notifier
> > [    5.231608] [drm] Initialized radeon 2.33.0 20080528 for 0000:00:01.0 on 
> > minor 0
> > </snip>
> 
> That doesn't look too different from my dmesg output. Your last line is almost
> identical to my system.
> 
> However, if Bruce is correct, you'll have to try the proprietary drivers (at
> least for 3D support, I suspect it'll work fine otherwise).
> 
> HTH
> -- 
> Marc Joliet
> --
> "People who think they know everything really annoy those of us who know we
> don't" - Bjarne Stroustrup

Hi Marc,

Do you have DRM_RADEON built in or a module?

Just wondering if that's the difference.
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
supp...@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

Reply via email to