[arkim]

Testing with kernel 3.14
So far, so good.

with amd fusion e-350 ?

[Claudio.Sjo]

Testing with kernel 3.14
So far, so good.

with amd fusion e-350 ?

No,
my test machine is an iMac 21.5" 2011

[jteeuw]

Testing with kernel 3.14
So far, so good.

How did you upgrade to kernel 3.14 ?

Thanks

[Claudio.Sjo]

Testing with kernel 3.14
So far, so good.

How did you upgrade to kernel 3.14 ?

Thanks

quite easy,
just follow the info from page 1, and replace the modules from the proper modules in the repository.
They are
http://kernel.ubuntu.com/~kernel-ppa/mai..._amd64.deb
http://kernel.ubuntu.com/~kernel-ppa/mai...35_all.deb
http://kernel.ubuntu.com/~kernel-ppa/mai..._amd64.deb

[jteeuw]

Testing with kernel 3.14
So far, so good.

How did you upgrade to kernel 3.14 ?

Thanks

quite easy,
just follow the info from page 1, and replace the modules from the proper modules in the repository.
They are
http://kernel.ubuntu.com/~kernel-ppa/mai..._amd64.deb
http://kernel.ubuntu.com/~kernel-ppa/mai...35_all.deb
http://kernel.ubuntu.com/~kernel-ppa/mai..._amd64.deb

Thanks worked for me gonna test it now

[tomtomme]

@all OpenSUSE users:
I filed a request to officially update Mesa from 9.2 to 10.x in Opensuse Tumbleweed here:

https://features.opensuse.org/317173

please vote up to make it happen!

---

stil these xbmc crashes at the end of an rtmp stream
this time the debug log
http://wklej.org/id/1320252/

You miss the relevant patch in your mesa installation. Did you pick it?

Thanks for the hint.
I misread your former answer that it would be already in mesa 10. Sorry. Bad reading comprehension on my side.
Now I understand it is only in mesa 10.0.4 or 10.1.1 or 10.2.x devel.

[fritsch]

10.0.4 does not have that patch, wsnipex has picked it manually! See his debian package.
10.1.1 will have that patch
10.2.x devel has that patch

[gfisher]

I set up the new bug report. https://bugs.freedesktop.org/show_bug.cgi?id=77009
I am now trying to get a system to show +/- patch shows the screen issue on the refresh change. Not sure what's the easiest way.

[Ectholian]

Tried to update yesterday from Frodo xvba built to Gotham on a 3.14 kernel, but only got strange issues. Like XBMC not starting, and my console screen had a very high resolution, big overscan and switching on and off every second . So tried everything again on a 3.13 kernel with the same issues. XBMC tried to start, but gave a fatal error in the log concerning it was unable to find configuration. After that, I removed xbmc, renamed the .xbmc folder and reinstalled again. This time XBMC booted and worked out of the box Installed MQ5, did the video calibration due the overscan and voila.

This high-resolution console screen sounds anyone familiair? Or the 1-second interval on and off blinking of the screen? Perhaps I still have a misconfiguration but wasn't able to find it yet

[fritsch]

@Ectholian:
Provide the logfiles from the first post and additionally DISPLAY=:0 /usr/lib/xbmc/xbmc-xrandr | pastebinit. Also there is no guided upgrade from frodo xvba to this new version, therefore the howto demonstrates a minimal installation. fglrx could have killed everything with one of its dumper versions.

High resolution terminal is KMS, yes, which is a really great feature against the fglrx vga console. I would suggest you set your TV to "Just Scan" "Fit" or whatever mode - no need to calibrate that in xbmc - which is counter productive anyways when swithing refreshrates.

@gfisher: Christian only wanted the correct kernel outputs. For the rest, use some video camera (mobile phone) and picture it.

[rewizja]

Wow that's impressive. I've been trying a lot since 2 weeks i'd bought AM1 platform. The 3.14 kernel + newest mesa resolved almost all my problems. It's almost perfect and hope that's going better soon, especially with Live-TV (DVB-S2, mpeg-ts) cause it's still a little reserve in it, i feel. For example the same channel on other receiver (vu+) is still better.

thanks!

[Ectholian]

I will clean things up and post some logs tonight.

What is the preferred way? I have a couple scenarios:
receiver off, tv off
receiver on, tv off
receiver off, tv on
receiver on, tv on



Edit: I discovered somehow that XBMC won't boot if both my tv and receiver are turned off :/ so i suppose i need to do some custom edid stuff. Will look into it later tonight since I'm at my work now.

[gfisher]

@gfisher: Christian only wanted the correct kernel outputs. For the rest, use some video camera (mobile phone) and picture it.

What do you mean correct kernel outputs? Pls pardon my ignorance, Foss/Git is still new to me. I pulled OE 4.0 and built it locally now, on a good fast machine with a full os. It is still affected. Which is good. He made me a patch. Plan was to patch and rebuild. I am not sure how to undo the possible offending commit (which the new patch might do), other than by hand, wo breaking newer code (lots of tuts that warn of this). I am not uncomfortable reading the code. I will watch changes. Building OE took a long time on a fast CPU.. So tests will be per day it looks. The amd oss devs are really helpful. I am impressed. Luckily it is the WE soon, so that I can really play with it.

[fritsch]

The patch he posted will apply additionally, it needs to go into the patches directory of the linux image, then you need to use Project=xy scripts/clean linux and then rebuild again with Project=xy make release.

It's perhaps more easy to test that on a non OE system.

[allio]

I feel guilty even asking this here as it's more of a general Linux question, but - how can I stop saucy from trying to replace my manually installed 3.13 kernel with a 3.11.x kernel every time I do a dist-upgrade? I know I can just not upgrade the system, but then I miss upgrades to xbmc and tvheadend.

I've tried reading about pinning and apt-hold and it makes my eyes spin in my head. Thought I'd ask you guys as you'll know exactly what I'm asking. I have an x64 system installed exactly according to the howto in the first post and it's working perfectly in every other respect.

Edit: hang on, don't tell me it's as simple as doing apt-get upgrade instead of apt-get dist-upgrade? I'm going to kick myself if so...