Before I do a reinstall. I will try the other catalyst driver that AMD
offers. They also offer a 14.6 beta. I will give it a go this weekend and
report back.
On Thu, Aug 7, 2014 at 9:26 PM, Jk Pieka jkpi...@gmail.com wrote:
I know very little polish from my grandparents who swam over here to the
states. I had to look up the spelling for thank you. The spelling and
pronunciation is crazy different. I've got by with my family by knowing the
basic greetings and numbers. That is about all.
Thanks for the help!
-Jkpieka
On Thu, Aug 7, 2014 at 9:23 PM, Jk Pieka jkpi...@gmail.com wrote:
1. I attached lspci, dmesg, lsmod, and lsusb. I recorded these after the
problem occurred.
2.AMD Catalyst™ 14.4 Proprietary Linux x86 Display Driver
3.
A.
GNOME Shell 3.4.2
B.
X.Org X Server 1.12.4
Release Date: 2012-08-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.11-2-amd64 x86_64 Debian
Current Operating System: Linux jkpieka 3.2.0-4-amd64 #1 SMP Debian
3.2.60-1+deb7u3 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.
0-4-amd64 root=UUID=c5e9cd17-0332-440a-9d55-7b3436a39004 ro quiet
Build Date: 17 December 2013 07:37:58PM
xorg-server 2:1.12.4-6+deb7u2 (Julien Cristau jcris...@debian.org)
Current version of pixman: 0.26.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
On Thu, Aug 7, 2014 at 7:00 PM, Tomasz Nitecki t...@tnnn.pl wrote:
Hey,
Sorry for the late reply, I'm slightly overworked at the moment...
On 05/08/14 05:58, Jk Pieka wrote:
1. I attached lspci, dmesg, lsmod, and lsusb. I recorded these after
the
problem occurred.
Can you please send those to bug tracker too? Anything you send to
756...@bugs.debian.org will show up in the web browsable version [1]
which will allow more people to look into your problem. As a matter of
fact, I might not be able to resolve it by myself and if so, I'll point
you to the correct people who will also require this information.
3.
A.
GNOME Shell 3.4.2
B.
X.Org X Server 1.12.4
Include those in your email too :)
Anyway, lets get back to your problem. In your dmesg there is a message
that indicates an error in fglrx driver (ATI Catalyst):
[10009.718081] [fglrx:firegl_pplib_notify_event] *ERROR* PPLIB: PPLib
Notify Event failed!
[10009.718084] [fglrx:firegl_pplib_notify_event] *ERROR*
ulEventType = 0002, ulEventData =
Searching for it returns a few results (some even mentioning stripes).
Please do one more test for me:
1. Switch to tty1 (ctrl+alt+f1)
2. Run pm-suspend (it will suspend your system)
3. Wake up your system (by using power button)
4. Switch back to DE (alt+f7)
And check if the stripes also appear.
Regards,
T.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756966
I attempted the test in two ways.
First I did it by logging in as root. I ran pm-suspend. My computer
turned off and went into suspend. When I pressed the power button to turn
the computer back on the computer fired up. Fans blazing. I however did not
get an image on my screen. I did not get any video feed at all. My monitor
stayed in stand-by. I waited 2-3 minutes, and was forced to power off the
computer by hand. Restart went fine, and computer booted up like normal.
Second I did it by logging in as my user name. I ram sudo pm-suspend.
Which may be the equivalent of running pm-suspend as root user. I am not
sure, however the same exact result came as the first attempt. I had to
power off manually and restart.
I have only thought of one thing. Mind you I am not a Linux
debugger/programmer, just an avid user. I remember back to my Arch linux
days, that you have to set-up swap space in order to use suspend. When I
installed debian/gnome, I just chose a general installation. I never
created my own partitions. If I create separate partitions on the install
It might have a better chance at success. I'll give it a go this weekend
perhaps.
