1 |
On Mon, Nov 11, 2013 at 04:03:23PM +0100, Elias Diem wrote: |
2 |
> Hi Bruce |
3 |
> |
4 |
> On 2013-11-11, Bruce Hill wrote: |
5 |
> |
6 |
> > If you have CONFIG_DRM_RADEON=m, and |
7 |
> > CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/", then the kernel will pick the |
8 |
> > right firmware automatically, without having to name the microcode in |
9 |
> > CONFIG_EXTRA_FIRMWARE at all. |
10 |
> |
11 |
> Yes, thank you. It worked. |
12 |
> |
13 |
> > Build your kernel that way and see which firmware shows up issuing: |
14 |
> > dmesg | grep -i firmware |
15 |
> |
16 |
> Unfortunately I can't figure it out. |
17 |
> |
18 |
> 'dmesg | grep -i firmware' doesn't return anything. |
19 |
> |
20 |
> 'dmesg | grep -i radeon' returns: |
21 |
> |
22 |
> <snip> |
23 |
> [ 0.030492] smpboot: CPU0: AMD A8-5500B APU with Radeon(tm) HD Graphics (fam: 15, model: 10, stepping: 01) |
24 |
> [ 4.600599] [drm] radeon kernel modesetting enabled. |
25 |
> [ 4.601157] radeon 0000:00:01.0: VRAM: 768M 0x0000000000000000 - 0x000000002FFFFFFF (768M used) |
26 |
> [ 4.601159] radeon 0000:00:01.0: GTT: 512M 0x0000000030000000 - 0x000000004FFFFFFF |
27 |
> [ 4.601693] [drm] radeon: 768M of VRAM memory ready |
28 |
> [ 4.601694] [drm] radeon: 512M of GTT memory ready. |
29 |
> [ 4.881482] radeon 0000:00:01.0: WB enabled |
30 |
> [ 4.881485] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000030000c00 and cpu addr 0xffff880223f0dc00 |
31 |
> [ 4.882218] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc900114b5a18 |
32 |
> [ 4.882220] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000030000c04 and cpu addr 0xffff880223f0dc04 |
33 |
> [ 4.882222] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000030000c08 and cpu addr 0xffff880223f0dc08 |
34 |
> [ 4.882223] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000030000c0c and cpu addr 0xffff880223f0dc0c |
35 |
> [ 4.882225] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000030000c10 and cpu addr 0xffff880223f0dc10 |
36 |
> [ 4.882245] radeon 0000:00:01.0: irq 45 for MSI/MSI-X |
37 |
> [ 4.882255] radeon 0000:00:01.0: radeon: using MSI. |
38 |
> [ 4.882534] [drm] radeon: irq initialized. |
39 |
> [ 5.023269] [drm] Radeon Display Connectors |
40 |
> [ 5.044982] [drm] radeon: power management initialized |
41 |
> [ 5.165005] fbcon: radeondrmfb (fb0) is primary device |
42 |
> [ 5.231602] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device |
43 |
> [ 5.231604] radeon 0000:00:01.0: registered panic notifier |
44 |
> [ 5.231608] [drm] Initialized radeon 2.33.0 20080528 for 0000:00:01.0 on minor 0 |
45 |
> </snip> |
46 |
|
47 |
Hi Elias, |
48 |
|
49 |
I don't have an APU, but found this: |
50 |
http://support.amd.com/en-us/kb-articles/Pages/latest-linux-beta-driver.aspx |
51 |
|
52 |
It's not supported by the open source driver, but you can find it in portage |
53 |
through ati-drivers-13.11_beta6 |
54 |
-- |
55 |
Happy Penguin Computers >') |
56 |
126 Fenco Drive ( \ |
57 |
Tupelo, MS 38801 ^^ |
58 |
support@×××××××××××××××××××××.com |
59 |
662-269-2706 662-205-6424 |
60 |
http://happypenguincomputers.com/ |
61 |
|
62 |
A: Because it messes up the order in which people normally read text. |
63 |
Q: Why is top-posting such a bad thing? |
64 |
A: Top-posting. |
65 |
Q: What is the most annoying thing in e-mail? |
66 |
|
67 |
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting |