Bug#443587: marked as done (wobbly and distorted screen dislpay when setting LVDS to 60.0 Hz)
Your message dated Sun, 30 Dec 2007 11:15:40 +0100
with message-id <47776FCC.3080902@ens-lyon.org>
and subject line Bug#443587: some issues with git version 6.7.196
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: wobbly and distorted screen dislpay when setting LVDS to 60.0 Hz
- From: Nadav Kavalerchik <nadavkav@netvision.net.il>
- Date: Sat, 22 Sep 2007 18:53:35 +0200
- Message-id: <200709221853.35206.nadavkav@netvision.net.il>
Package: xserver-xorg-video-ati
Version: 1:6.7.193-1
Severity: normal
--- Please enter the report below this line. ---
normally (when i boot) the LVDS screen is set to: 1024x768 60.0
60.0* according to xrandr, but when i change it and set it to the first 60.0
Hz option it gets distorted and wobble like a bug a filed a while ago.
screen capture:
http://picasaweb.google.com/nadavkav/Screen_capture/photo#5109286800347491394
i don't normally do that (switch to the other 60.0 Hz) but i think you should
know about this issue.
setting it back to the initial 60.0 Hz (second option) clears the screen and
all goes back to normal.
how come i have two 60.0 Hz option to choose from ?
(it's confusing)
the initial good screen display:
laptop:~# xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2304 x 1024
VGA-0 disconnected (normal left inverted right x axis y axis)
LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x
0mm
1024x768 60.0 60.0*
800x600 60.3
640x480 59.9
S-video disconnected (normal left inverted right x axis y axis)
the distorted screen display:
laptop:~# xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2304 x 1024
VGA-0 disconnected (normal left inverted right x axis y axis)
LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x
0mm
1024x768 60.0* 60.0
800x600 60.3
640x480 59.9
S-video disconnected (normal left inverted right x axis y axis)
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.21-2-686
Debian Release: lenny/sid
500 unstable www.debian-multimedia.org
500 unstable mirror.isoc.org.il
500 testing mirror.isoc.org.il
500 experimental www.debian-multimedia.org
500 etch debian.beryl-project.org
1 experimental mirror.isoc.org.il
--- Package information. ---
Depends (Version) | Installed
==================================-+-=============
libc6 (>= 2.6.1-1) | 2.6.1-4
xserver-xorg-core (>= 2:1.4) | 2:1.4-2
--- End Message ---
--- Begin Message ---
Version: 1:6.7.197-1
Nadav Kavalerchik wrote:
works perfect !!!
the xrandr i mean. it detects the modes more accurately , does not
return errors
and switches between modes (on the laptop and the TV screen) with
synchronicity
in resolution too (which is more comfortable)
but these two are still an issue (which i personally don't care too
much about)
(1) Fn-F4 does not work anymore (it used to work, distorted! but working)
pressing the key combination does nothing (visually)
(2) closing the laptop's screen and opening it again, does not
restore graphic
session. screen gets flickering and shifted to the left. restarting X
does
not solve this only restarting of the laptop.
so...
thank you very much :-)
Ok I am closing this bug since the original issue seems to be fixed.
Regarding the other issues: I think somebody else complained about
Fn-F4. I am not sure this is supposed to be used since it might change
things through the BIOS in the back of the driver and thus cause conflicts.
Regarding closing the laptop screen, I am not sure what to do. I am
still putting some git snapshots in experimental every week or so, you
might want to see whether they help for this.
Brice
--- End Message ---
Reply to: