Kodi Community Forum

Full Version: Kodibuntu: ATI Radeon HD6450 issue
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Just fresh installed Kodi[buntu] and also upgraded the graphics card to Radeon HD6450 after using NVIDA for long time. it is working fine when I connect the box to a computer monitor (using HDMI to DVI cable) but the moment I hook it up to the TV, I don't get anything after the purple Kodi splash screen animation. Screen goes blank and stays like that forever.

the card The card appears to be detected properly:

Code:
root@htpc:~# lshw -c video
  *-display              
       description: VGA compatible controller
       product: Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:01:00.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=radeon latency=0
       resources: irq:46 memory:d0000000-dfffffff memory:fe9c0000-fe9dffff ioport:c000(size=256) memory:fe9a0000-fe9bffff


root@htpc:~# lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]

Did anyone see the similar thing? Or any idea what's I'm missing? Best!
Provide dmesg | pastebinit via ssh when connected to the TV.
(2015-01-01, 16:32)fritsch Wrote: [ -> ]Provide dmesg | pastebinit via ssh when connected to the TV.
Thanks for the heads up! log attached: http://pastebin.com/YxrWPJZs
No support for fglrx here, sorry. Not sure how you forced that driver into kodibuntu, but we only support the radeon oss drivers.
(2015-01-01, 20:58)fritsch Wrote: [ -> ]No support for fglrx here, sorry. Not sure how you forced that driver into kodibuntu, but we only support the radeon oss drivers.
Okay, sorry! My bad with fglrx: I was just trying out, I guess.
But exactly the same thing happens even with live-cd. Please find the 2nd log attached, just after another fresh installation.
http://pastebin.com/sEGZ4BJn
Yes, current ubuntu kernel is broken. The updated the kernel and introduced a regression, workaround: http://forum.kodi.tv/showthread.php?tid=212722 for OSS drivers only.
I got almost the same TV as in the post, but GT50.
I still wonder, how it works on a computer monitor? Is it something to do with the TV? Going through the post now and report back shortly.
That other post is not relevant to Nvidia GPUs at all...
I'm not using Nvidia at all this time (ignore the signature). What I meant is the same ATI Radeon HD 6450 works just fine with a computer monitor but failed on the TV.

BTW, it worked finally. I had to upgrade the kernel, as you mentioned in the other post but most importantly, for me, it still didn't work until I added: GRUB_GFXMODE=1280x720 in the /etc/default/grub. Thanks!

Doesn't look like vdpau working though:

Code:
root@htpc:~# DISPLAY=:0 vdpauinfo
display: :0   screen: 0
Error creating VDPAU device: 23

I haven't started digging in yet. Anything you already know about it?
http://paste.ubuntu.com/9658549/
Provide:
dmesg | pastebinit
dpkg -l |grep mesa | pastebinit
id | pastebinit

all with the user that runs your desktop, which is obviously _not_ root
Of course not root (just got fed up with "sudo") User kodi runs kodi
Logs are here.

http://paste.ubuntu.com/9659059/
http://paste.ubuntu.com/9659062/
http://paste.ubuntu.com/9659065/

Another thing I noticed that HDA Intel ALC1200 Analog is [s]elected as default audio device, not the HDA ATI.
All fine.

Now as kodi user:

DISPLAY=:0 vdpauinfo

You can easily change the audio device analog is chosen cause it's the first device we enumerate.
Already did, many times, as kodi user; got the same result

Code:
kodi@htpc:~$ DISPLAY=:0 vdpauinfo
display: :0   screen: 0
Error creating VDPAU device: 23

I know the audio device can be changed easily in the settings. How can I make it permanent? It's going back to the default HDA Intel every time Kodi starts up.
www.openelec.tv - try this. Something is very odd with your installation.
OpenELEC worked straight away and the audio-device doesn't change as well but it's a overall pain in the neck for the people those who still stick to the command-line. Struggling to configure my MonCaso 320 FTDI FT232R remote. That's why I wanted to stay away from OpenELEC.
Pages: 1 2