All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650
Date: Sun, 18 Sep 2016 10:30:55 +0000	[thread overview]
Message-ID: <bug-153121-2300-NSas3yaFEi@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-153121-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=153121

Kontantin Ivanov <kostyarin.ivanov@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |low

--- Comment #38 from Kontantin Ivanov <kostyarin.ivanov@gmail.com> ---
There is an opinion that the problem is not inside radeon driver but inside
i915/intel driver. I downgraded my system to Ubuntu 14.04 (3.11 kernel) and
tried to install fglrx (proprietary AMD driver). It doesn't  works. X server
starts normally but screen is show me last image (kubuntu start splash and
mouse cursor) and then it freezes. Xorg.log does'n show anything. Digging
deeper I found some solution that requires modified intel driver
<https://launchpad.net/%7Eandrikos/+archive/ubuntu/ppa/+build/3932032>.
Unfortunately the man, who developed it, removed the package from launchpad.

I've changed urgency to low again, because who cares about old, stupid
hardware.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2016-09-18 10:30 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15  8:52 [Bug 153121] New: UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650 bugzilla-daemon
2016-08-15  8:54 ` [Bug 153121] " bugzilla-daemon
2016-08-15  8:55 ` bugzilla-daemon
2016-08-15  8:55 ` bugzilla-daemon
2016-08-15  8:56 ` bugzilla-daemon
2016-08-15  8:57 ` bugzilla-daemon
2016-08-15  8:57 ` bugzilla-daemon
2016-08-15  8:58 ` bugzilla-daemon
2016-08-15  8:59 ` bugzilla-daemon
2016-08-15  9:01 ` bugzilla-daemon
2016-08-15  9:06 ` bugzilla-daemon
2016-08-15  9:07 ` bugzilla-daemon
2016-08-15  9:07 ` bugzilla-daemon
2016-08-15  9:22 ` bugzilla-daemon
2016-08-15  9:38 ` bugzilla-daemon
2016-08-15  9:41 ` bugzilla-daemon
2016-08-15  9:51 ` bugzilla-daemon
2016-08-15  9:54 ` bugzilla-daemon
2016-08-15 10:03 ` bugzilla-daemon
2016-08-15 10:56 ` bugzilla-daemon
2016-08-15 11:18 ` bugzilla-daemon
2016-08-16 14:01 ` bugzilla-daemon
2016-08-16 14:02 ` bugzilla-daemon
2016-08-16 14:03 ` bugzilla-daemon
2016-08-16 14:04 ` bugzilla-daemon
2016-08-16 14:05 ` bugzilla-daemon
2016-08-16 14:17 ` bugzilla-daemon
2016-08-16 14:18 ` bugzilla-daemon
2016-08-18  5:13 ` bugzilla-daemon
2016-08-18  6:18 ` bugzilla-daemon
2016-08-18  6:28 ` bugzilla-daemon
2016-08-18  6:28 ` bugzilla-daemon
2016-08-22 11:52 ` bugzilla-daemon
2016-08-22 11:54 ` bugzilla-daemon
2016-08-29  9:32 ` bugzilla-daemon
2016-09-02 16:22 ` bugzilla-daemon
2016-09-02 16:22 ` bugzilla-daemon
2016-09-02 16:26 ` bugzilla-daemon
2016-09-14 13:12 ` bugzilla-daemon
2016-09-14 13:20 ` bugzilla-daemon
2016-09-18 10:30 ` bugzilla-daemon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-153121-2300-NSas3yaFEi@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.