From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70035] GPU Lockup on AMD RS880 HD4200
Date: Mon, 07 Oct 2013 08:24:32 +0000 [thread overview]
Message-ID: <bug-70035-502-Ydhj6p4lRY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-70035-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1910 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=70035
--- Comment #10 from Tasev <tasev.stefanoska@skynet.be> ---
(In reply to comment #9)
> Tasev,
>
> If your issue is related to mine then the corresponding debs from the
> 9.3~git1309201759 Sept 20th release should work :-
>
> https://launchpad.net/~oibaf/+archive/graphics-drivers/+build/5036069 [amd64]
> https://launchpad.net/~oibaf/+archive/graphics-drivers/+build/5036070 [i386]
>
>
> ...and the debs from Sept 23rd 9.3~git1309231016 should fail :-
>
> https://launchpad.net/~oibaf/+archive/graphics-drivers/+build/5042397 [amd64]
> https://launchpad.net/~oibaf/+archive/graphics-drivers/+build/5042398 [i386]
>
>
> To find out which mesa packages you have installed (hopefully nothing else
> has a matching version string) :-
>
> dpkg -l | grep ".*9.3~git[0-9]*.[0-9a-z]*~gd~.*"
>
>
> To install the debs download the appropriate packages to
> /path/to/some/directory and then :-
>
> cd /path/to/some/directory
>
> sudo dpkg -i *.deb
>
>
> You can usually find the debs from an older mesa version by looking in apt's
> archives :-
>
> ls -lrt /var/cache/apt/archives/*_9.3~git[0-9]*.[0-9a-z]*~gd~*
>
> And copy them somewhere for easy installation :-
>
> cp /var/cache/apt/archives/*_9.3~git1309040912.644fbb~gd~*
> /path/to/some/directory
>
>
> Hopefully you can find out which version breaks your install or at least get
> things working again.
Thank you Blake,
I reverted the mesa deb's to 9.3~git1309201759 Sept 20th version and my system
is working again.
Then i update my system with the debs from Sept 23rd 9.3~git1309231016 but my
system is still ok.
Only updating to the deb's from Sept 30th 9.3~git1309300954.868791 break my
system so it's probably a different issue from your.
Thank you again for your help, i have a working system again now.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3185 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-10-07 8:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-70035-502@http.bugs.freedesktop.org/>
2013-10-02 13:35 ` [Bug 70035] GPU Lockup on AMD RS880 HD4200 bugzilla-daemon
2013-10-03 9:28 ` bugzilla-daemon
2013-10-05 13:29 ` bugzilla-daemon
2013-10-06 17:18 ` bugzilla-daemon
2013-10-07 8:24 ` bugzilla-daemon [this message]
2013-10-08 7:53 ` bugzilla-daemon
2013-10-08 8:58 ` bugzilla-daemon
2013-10-09 13:12 ` bugzilla-daemon
2013-10-09 13:14 ` bugzilla-daemon
2013-10-14 12:08 ` bugzilla-daemon
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-70035-502-Ydhj6p4lRY@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).