https://bugs.freedesktop.org/show_bug.cgi?id=45641
John changed:
What|Removed |Added
Resolution|--- |NOTABUG
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=45641
John changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #19 from John john.etted...@gmail.com ---
Still same behavior with current drivers/kernel/mesa, I was hoping something
would have helped :)
Alex, do you have any other patch I can test against this?
Thanks,
John
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #18 from John ---
I tried the patch today but got another black screen already.
I have an 4670 by the way, not sure if the patch was made for that one or
not...
Thanks
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #18 from John john.etted...@gmail.com ---
I tried the patch today but got another black screen already.
I have an 4670 by the way, not sure if the patch was made for that one or
not...
Thanks
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #17 from Alex Deucher ---
Created attachment 76907
--> https://bugs.freedesktop.org/attachment.cgi?id=76907=edit
possible fix
Does the attached kernel patch help?
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #16 from Jan Pape? (honyczek) ---
(Additional info to comment #12)
> Interesting: If I connect only one monitor (either on cable 1 or 2), it works
> well.
It is not working well, but in only blinks in longer intervals. After
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #16 from Jan Papež (honyczek) honyc...@centrum.cz ---
(Additional info to comment #12)
Interesting: If I connect only one monitor (either on cable 1 or 2), it works
well.
It is not working well, but in only blinks in longer
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #17 from Alex Deucher ag...@yahoo.com ---
Created attachment 76907
-- https://bugs.freedesktop.org/attachment.cgi?id=76907action=edit
possible fix
Does the attached kernel patch help?
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #15 from Alex Deucher ---
(In reply to comment #14)
> Is possible to add these options when using KMS? Modifying
> /etc/X11/xorg.conf.d/*.conf is enough?
yes.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #14 from Jan Pape? (honyczek) ---
(In reply to comment #13)
> 2. Disable acceleration (Option "NoAccel" "True" in the device section of
> your xorg.conf)
> 3. Disable Tiling (Option "ColorTiling" "False" in the device section of
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #13 from Alex Deucher ---
(In reply to comment #12)
> Interesting: If I connect only one monitor (either on cable 1 or 2), it
> works well.
The blinking is caused by data underflow to the display controllers. All
clients on the GPU
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #12 from Jan Pape? (honyczek) ---
Additional specific info:
I'm using extended desktop on two DVI connected monitors (the card has one
connector and you have to use Y cable to connect something). Even if I switch
to cloned desktop,
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #11 from Alex Deucher ---
(In reply to comment #10)
> > For systems where this is a regression, can you bisect?
>
> I don't understand. Could you explain this question please (if it was to me)?
If it worked with an older kernel,
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #10 from Jan Pape? (honyczek) ---
> Does booting with radeon.disp_priority=2 on the kernel command line in grub
> help?
No.
> For systems where this is a regression, can you bisect?
I don't understand. Could you explain this
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #9 from Alex Deucher ---
Does booting with radeon.disp_priority=2 on the kernel command line in grub
help? For systems where this is a regression, can you bisect?
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #8 from Jan Pape? (honyczek) ---
The issue still remains.
openSUSE 12.3
kernel-desktop 3.7.10-1.1.1
xorg-x11-server 7.6_1.13.2-1.2.1
xf86-video-ati 7.0.0-2.1.1
libdrm2 2.4.42-1.1.1
libdrm_radeon1 2.4.42-1.1.1
Mesa
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #8 from Jan Papež (honyczek) honyc...@centrum.cz ---
The issue still remains.
openSUSE 12.3
kernel-desktop 3.7.10-1.1.1
xorg-x11-server 7.6_1.13.2-1.2.1
xf86-video-ati 7.0.0-2.1.1
libdrm2 2.4.42-1.1.1
libdrm_radeon1
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #9 from Alex Deucher ag...@yahoo.com ---
Does booting with radeon.disp_priority=2 on the kernel command line in grub
help? For systems where this is a regression, can you bisect?
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #10 from Jan Papež (honyczek) honyc...@centrum.cz ---
Does booting with radeon.disp_priority=2 on the kernel command line in grub
help?
No.
For systems where this is a regression, can you bisect?
I don't understand. Could you
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #11 from Alex Deucher ag...@yahoo.com ---
(In reply to comment #10)
For systems where this is a regression, can you bisect?
I don't understand. Could you explain this question please (if it was to me)?
If it worked with an older
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #12 from Jan Papež (honyczek) honyc...@centrum.cz ---
Additional specific info:
I'm using extended desktop on two DVI connected monitors (the card has one
connector and you have to use Y cable to connect something). Even if I switch
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #13 from Alex Deucher ag...@yahoo.com ---
(In reply to comment #12)
Interesting: If I connect only one monitor (either on cable 1 or 2), it
works well.
The blinking is caused by data underflow to the display controllers. All
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #14 from Jan Papež (honyczek) honyc...@centrum.cz ---
(In reply to comment #13)
2. Disable acceleration (Option NoAccel True in the device section of
your xorg.conf)
3. Disable Tiling (Option ColorTiling False in the device
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #15 from Alex Deucher ag...@yahoo.com ---
(In reply to comment #14)
Is possible to add these options when using KMS? Modifying
/etc/X11/xorg.conf.d/*.conf is enough?
yes.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #7 from Warren Jones 2012-06-15 16:36:50 PDT
---
I'm experiencing similar problems. My screen will go black for 1-2 seconds at
random intervals, typically more than a dozen times per hour. In a two monitor
configuration, sometimes
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #7 from Warren Jones wjo...@fluke.com 2012-06-15 16:36:50 PDT ---
I'm experiencing similar problems. My screen will go black for 1-2 seconds at
random intervals, typically more than a dozen times per hour. In a two monitor
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #6 from John 2012-02-07 12:22:13 PST
---
It seems quite random to me.
Also I remember it happening around the 3.0 release, but I cannot say that the
issue is coming from there.
For all I know it could be KDE messing up somewhere or
https://bugs.freedesktop.org/show_bug.cgi?id=45641
Alex Deucher changed:
What|Removed |Added
AssignedTo|xorg-driver-ati at lists.x.org |dri-devel at
lists.freedesktop
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #6 from John john.etted...@gmail.com 2012-02-07 12:22:13 PST ---
It seems quite random to me.
Also I remember it happening around the 3.0 release, but I cannot say that the
issue is coming from there.
For all I know it could be KDE
30 matches
Mail list logo
