20 Nov 2019 - TVDB Scraper v3.2.0 is now available which reinstates scraping. TVDB are still in the process of fixing a number of bugs so there may still be further breakages. See this post. 2901570 (post)

  •   
  • 1
  • 117
  • 118
  • 119(current)
  • 120
  • 121
  • 244
  •   
  Thread Closed
Linux Radeon OSS with vdpau (howto)
(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!?

It's quality support like this that makes a OSS project thrive imho!



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.
HTPC(s): All running LibreELEC
  • AMD 2200G APU on Gigabyte AB350N-Gaming WIFI-CF
  • RPI3 x2 | RPI2 x2
NAS: FreeNAS (Latest Stable) | NFS/CIFS
(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 temp1Smile 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
Adapter: PCI adapter
temp1: +8.0°C (crit = +120.0°C, hyst = +90.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1: +8.6°C (high = +70.0°C)
(crit = +80.0°C, hyst = +79.0°C)
/etc/sensors3.conf is where the ic's are defined and the math is done.
Asus E2KM1I-DELUXE (E2-2000 with HD7340) 60GB SSD + 2TB WD Caviar Green : Xubuntu 18.04 LTS : (mythtv 0.29.1+fixes + TBS 6205 QUAD FREEVIEW DVB-T2)
Odroid C2 Coreelec.
@fritsch -- how can we help?
Linux Mint 18 LTS 64-bit - Kodi 17 Beta6
Odroid-C2 - Libreelec v7.90.009
(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.

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 temp1Smile 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
Adapter: PCI adapter
temp1: +8.0°C (crit = +120.0°C, hyst = +90.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1: +8.6°C (high = +70.0°C)
(crit = +80.0°C, hyst = +79.0°C)

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.
(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 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.

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 ...
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.
Provide all the debug logs, the howto wants you to post.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Weird how Filly's dmesg doesn't mention UVD at all and a Call Trace at the bottom, kernel bug?
Asus E2KM1I-DELUXE (E2-2000 with HD7340) 60GB SSD + 2TB WD Caviar Green : Xubuntu 18.04 LTS : (mythtv 0.29.1+fixes + TBS 6205 QUAD FREEVIEW DVB-T2)
Odroid C2 Coreelec.
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.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
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/
Asrock Q9100-ITX, Peachtree Nova, Audio Physic Sparks, Sony KDL40V400, Synology DS209. Remotes: iPad, Nexus 5, Maraschino.
Man(!)

nomodeset <- how do you think that should work?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Consider me a noob, on this terrain at least. (I follow instructions, but am in no position to find solutions, sorry)
Asrock Q9100-ITX, Peachtree Nova, Audio Physic Sparks, Sony KDL40V400, Synology DS209. Remotes: iPad, Nexus 5, Maraschino.
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.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
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.
Asrock Q9100-ITX, Peachtree Nova, Audio Physic Sparks, Sony KDL40V400, Synology DS209. Remotes: iPad, Nexus 5, Maraschino.
  •   
  • 1
  • 117
  • 118
  • 119(current)
  • 120
  • 121
  • 244
  •   
  Thread Closed
 
Thread Rating:
  • 26 Vote(s) - 4.58 Average



Logout Mark Read Team Forum Stats Members Help
Radeon OSS with vdpau (howto)4.5826