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