Linux Radeon OSS with vdpau (howto) - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52) +---- Thread: Linux Radeon OSS with vdpau (howto) (/showthread.php?tid=174854) Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
|
Radeon OSS with vdpau (howto) - pyrodex - 2014-01-20 (2014-01-20, 18:57)Packet Loss Wrote: Thank you guys, this guide has worked perfectly for me although I used Raring instead of Saucy. I did notice that the XML hasn't worked for me in terms of pulling the CPU/GPU temps from sensors, possibly due to a lack of support for my mobo in lm-sensors on Raring!? I had the same issue with the sensors and it may vary from motherboard to motherboard. You may need to do a sensors and see if you can parse the data yourself. RE: Radeon OSS with vdpau (howto) - Packet Loss - 2014-01-20 (2014-01-20, 19:20)pyrodex Wrote: I had the same issue with the sensors and it may vary from motherboard to motherboard. You may need to do a sensors and see if you can parse the data yourself. The last time I built this mobo with Raring, sensors-detect only picked up one sensor. This last install I have two and clearly one is GPU and one is CPU (both labelled temp1 but they're far too low to be real temps. They do say +8 c so I'm wondering if there's a base I need to add to the number shown, any ideas? Quote:radeon-pci-0008 RE: Radeon OSS with vdpau (howto) - deadite66 - 2014-01-20 /etc/sensors3.conf is where the ic's are defined and the math is done. RE: Radeon OSS with vdpau (howto) - locomot1f - 2014-01-20 @fritsch -- how can we help? RE: Radeon OSS with vdpau (howto) - gradinaruvasile - 2014-01-20 (2014-01-20, 19:28)Packet Loss Wrote:(2014-01-20, 19:20)pyrodex Wrote: I had the same issue with the sensors and it may vary from motherboard to motherboard. You may need to do a sensors and see if you can parse the data yourself. These 2 temps are provided by the k10temp module which extracts it from the CPU's internal sensors and the radeon module-provided temperatures extracted from the video cards internals. On all my mobos i had these were off (although some pci cards seem to report real-looking values) - AFAIK, especially in the case of APUs these arent "real" temperatures, they are values used internally for thermal throttling - on low or no load, they have very unprecise values and they come closer to "reality" when there is load on the components and temps raise. Now, mobos have a thermal monitoring chip (mostly IT8xxx series) that collects CPU temperatures, fan speeds and voltage levels from various sensors and the BIOS uses it to decide on throttling and stuff. These readings are provided as "real" values (and are the same that you see in the BIOS/UEFI). Sadly, not all are supported under Linux and it seems they will not add newer models since ITE doesnt share diagrams anymore. For example the Gigabyte GA-F2A85X-D3H mobo has an IT87xx chip that shows all these informations, but the GA-F2A88X-D3H has some IT8620 chip that isnt supported (my case) and is imited only to the k10temp and radeon values. I dont know if the values provided by radeon and k10temp can be changed and anyway, because of their non-linear nature, multiplying them with some arbitrary value probably wont help anyway. In my case they are at 0 or below 0 when idle. RE: Radeon OSS with vdpau (howto) - Packet Loss - 2014-01-20 (2014-01-20, 21:01)gradinaruvasile Wrote: Sadly, not all are supported under Linux and it seems they will not add newer models since ITE doesnt share diagrams anymore. For example the Gigabyte GA-F2A85X-D3H mobo has an IT87xx chip that shows all these informations, but the GA-F2A88X-D3H has some IT8620 chip that isnt supported (my case) and is imited only to the k10temp and radeon values. I did find a mechanism to multiple them via /etc/sensors3.conf but I have the GA-F2A88X-D3H mobo like you and don't see the point some arbitrary maths to give me some cosmetic comfort. I'm idling at about 4c with a passive cooling solution which is why I'm a little nervous about the temps. Not to worry, onwards and upwards ... RE: Radeon OSS with vdpau (howto) - User 143004 - 2014-01-20 Followed instructions to the tee twice but no sound and max 1280px reso @ less than 10fps (CPU maxed out constantly). I think video driver is first object of attention. Audio out should be 2 channel over SPDIF (optical). Used to run previous wsnipex on Ubunti 12, now on 13.10. http://paste.ubuntu.com/6787843/ http://paste.ubuntu.com/6788180/ http://paste.ubuntu.com/6788183/ http://paste.ubuntu.com/6788188/ (Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory Error creating VDPAU device: 1) http://paste.ubuntu.com/6788195/ Hmm, nvidia entry? Should be ATI, but where to look. Please advise, thanks. RE: Radeon OSS with vdpau (howto) - fritsch - 2014-01-20 Provide all the debug logs, the howto wants you to post. RE: Radeon OSS with vdpau (howto) - deadite66 - 2014-01-21 Weird how Filly's dmesg doesn't mention UVD at all and a Call Trace at the bottom, kernel bug? RE: Radeon OSS with vdpau (howto) - fritsch - 2014-01-21 Quote:video=uvesafb:mode_option=1920x1080-24,mtrr=3,scroll=ywrap radeon.audio=1 radeon.dpm=1 clocksource=hpet hpet=enable splash quiet vt.handoff=7 You disable radeon .... with setting your nice and nifty splash screen. There is a howto out there that tells "do that" but it's sooo wrong. Remove the uvesafb stuff. RE: Radeon OSS with vdpau (howto) - User 143004 - 2014-01-22 Removed 'uvesafb:mode_option=1920x1080-24,mtrr=3,scroll=ywrap from /etc/default/grub'; no difference. New logs follow: dmesg | pastebinit http://paste.ubuntu.com/6795986/ cat ~/.xbmc/temp/xbmc.log | pastebinit http://paste.ubuntu.com/6795987/ cat /var/log/Xorg.0.log | pastebinit http://paste.ubuntu.com/6795989/ DISPLAY=:0 vdpauinfo | pastebinit Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory Error creating VDPAU device: 1 http://paste.ubuntu.com/6795990/ dpkg -l |grep mesa | pastebinit http://paste.ubuntu.com/6795992/ RE: Radeon OSS with vdpau (howto) - fritsch - 2014-01-22 Man(!) nomodeset <- how do you think that should work? RE: Radeon OSS with vdpau (howto) - User 143004 - 2014-01-22 Consider me a noob, on this terrain at least. (I follow instructions, but am in no position to find solutions, sorry) RE: Radeon OSS with vdpau (howto) - fritsch - 2014-01-22 For the future: Follow exactly one instructions. The howto here never ever wants to to overwrite the default framebuffer nor it wants you to disable the framebuffer with nomodeset. So remove that. RE: Radeon OSS with vdpau (howto) - User 143004 - 2014-01-22 Removed and updated grub, rebooted. Now I have fullHD and fluid responsive interface. No way to reach Video Settings etc, my skin does not support it? Also testing audio, not sure that works as expected. FWIW it now says Pulse, but this is a standalone machine, only need 2channel over toslink. Update: apparent leftover from previous installation or installed by OS update; so sudo apt-get autoremove pulseaudio. Then I got to reselect the proper audio output and got back sound. Rescanning the library as we speak: back on the right track. Now only to git my skin, then i'm good to go and futureproof. Thanks Fritsch, amazin job. |