[mhansi]

HW: Gigabyte GA-MA78GM-S2H with onboard ATI HD3200 Graphic,
OS: Ubuntu 8.10 ( Intrepid), GNOME desktop
driver: fglrx driver 9.2 and 9.3 ( latest from yesterday )
SW: SVN Build of XBMC ( seen for sure from Build 18100 and up )

Problem: XBMC hangs during startup, also if ~/.xbmc is completly removed
( XBMC splash screen is seen , no more )
current workaround: going back to 9.1 and I can use xbmc again.

I have tried now 2 times to install ubuntu from scratch - no change.


Have someone the same expericense ? - it seems that I am the only one ...

The funny thing is, that I have installed exactly the enviroment ( incl. same HW) with the ATI 9.2 driver and there there is no problem

any idea or help appreciated !

[MaestroDD]

I can confirm the problem, spend a few hours on the weekend but with not much success.
I'm on Jaunty with Catalyst 9.3 and xbmc hangs with/directly after splash. XBMC and X can't be killed afterwards, machine needs reboot.
Here's a thread where someone's trying the radeon drivers http://ubuntuforums.org/showthread.php?t=1090098 but without success, too.

Funny thing is, that this bug has something in common with the "garbled fullscreen" bug some where seeing with fglrx: starting xbmc as root somehow works. IIRC someone said this has something to do with dri not enabled, but can't find the reference now :/

Log as user: http://pastebin.ubuntu.com/140580/
Log as root: http://pastebin.ubuntu.com/140581/
The difference I see it GL_VERSION = 2.1.8575 and then vsync seems to be handled differently

[mhansi]

Thank you for this helpfull answer and the references ! And thanks to confirm this problem !

I can fully agree what you described. I am also familiar with the "garbled fullscreen" problem in the fglrx releases last year.

For me it seams that ATI is not testing against XBMC for a release !?

[dteirney]

I'm running ATI with AMD 780G chipset (HD3200) and Catalyst 9.3 drivers reasonably successfully.

There was definitely a change in how VSync is handled between 9.2 and 9.3. I had the ATI VSync patch (http://trac.xbmc.org/ticket/5951) applied. However, with that patch xbmc.bin was running 100% CPU even when idling.

Had heaps of problems getting 9.3 working. Seems like I was affected by the problems listed at http://www.phoronix.com/forums/showthrea...069&page=4

No problems with any garbled screens though.

I'm running Mythbuntu 8.10 (XFCE, not Gnome). Catalyst Control Center has VSync Always On and VSync disabled in XBMC.

[MaestroDD]

I'm running ATI with AMD 780G chipset (HD3200) and Catalyst 9.3 drivers reasonably successfully.

Thanks, this gives some hope

There was definitely a change in how VSync is handled between 9.2 and 9.3. I had the ATI VSync patch (http://trac.xbmc.org/ticket/5951) applied. However, with that patch xbmc.bin was running 100% CPU even when idling.

Had heaps of problems getting 9.3 working. Seems like I was affected by the problems listed at http://www.phoronix.com/forums/showthrea...069&page=4

No problems with any garbled screens though.

I'm running Mythbuntu 8.10 (XFCE, not Gnome). Catalyst Control Center has VSync Always On and VSync disabled in XBMC.

Thanks for linking the ticket. Somehow missed it. Will try when I'm back home.
So you say XBMC runs (100% cpu with patch, normal without) with current svn and no lockups?
mind posting your xbmc.log to compare?

[MaestroDD]

Just to post a short success note: Disabling vsync in XBMC did it.

[lcapriotti]

Unfortunately XBMC starts in "always on", so normally you can not have it running on 9.3...
I can confirm that handling vsync from within XBMC creates the issue: If you start with a proper guisettings.xml with sync off and start toggling the gui control, XBMC hangs when "always on" is selected.

[greef]

Had the freeze issue, it helped changing the vzync option.

But I wonder, does anyone else have the 100% cpu issue? I have it and can't get rid of it...

Ubuntu 8.04, ATI HD3200.

Any ideas what to do? Maybe I should try the patch mentioned earlier in this thread? But then I need to go back to catalyst 9.1?

Any other tips?

[b01]

I also have this issue, will try to disable VSync, as soon as I figure out how. Funny thing is, I think this only happened because I'm connected to an HDTV with VGA (HDMI give me a black screen).

The reason I say that cause I install a clean copy of Ubuntu on this very machine, and the ATi 9.3 drivers and XBMC 9.04 alpha. I had no problems what so ever.

But when I tried to connect this PC to my HDTV with an HDMI cable, it never worked and I eventually screwed up the Xorg install, so I just reinstalled Ubuntu all over again , but connected to my Samsung T220 monitor.
After I got Ubuntu install again on this PC, I connected it to the HDTV again, but this time thought the VGA. Worked fine, so I kept it connected to the Samsung HDTV. I installed the ATi 9.3 drivers, then fixed Pulse Audio, then installed XBMC. When I start XBMC it just crashes at Splash screen and I have to reboot.

I'm runinng a BIOSTAR T-Serries TA790GX XE; AMD 64X2 5000+;4GB GSkill 1066; Wetern Digital 640GB 16MB cache HDD.

[jar72]

To disable vsync without loading xbmc: go to ~/.xbmc/userdata/ and open up guisettings.xml with a text editor. Search for "vsync" and change the value to 0.

I was having the same problem with catalyst 9.3 and ubuntu 8.04 on a gigabyte ga-ma78gm, until the fix described above.

[b01]

That solved my problem.

Thanx jar72, wish I had seen you post 2 hours ago. I search the forums and the net and finally found where the guisetting.xml file was. But only after I saw althekiller post http://forum.xbmc.org/showthread.php?tid=34655. It showed me where the debug log was, from there I knew the gui file was close by.

Thanks for letting me know what to set it to, that save me a lot of searching. Everyone just said simple disable it, but they never said how. I was debating using a 0 or the word disable. I wasn't sure sine there was a 2 there instead of a 1. What does vsync set to 2 do anyways?

Man, after all that, I'm REALLY gonna enjoy watching Lost tonight on my HDTV. I will keep trying to get HDMI to work later.