Summary: | Flickering in virtual console with post-6.7.192 ati driver | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Luigi Toscano <luigi.toscano> | ||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | normal | ||||||
Priority: | medium | ||||||
Version: | 7.2 (2007.02) | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Luigi Toscano
2007-09-05 14:46:01 UTC
Created attachment 11439 [details]
X.org log (the switches from and to the vt has been emphasized)
Can you try again with ati git master? I compile (almost) daily the git master since the randr-1.2 branch was merged into it, and the problem is still there :( when X.org starts, the system is not able anymore to switch to "text" mode. Any change with current ati git? *** Bug 13917 has been marked as a duplicate of this bug. *** closing due to lack of feedback. Sorry, I forgot to "ping" this bug. The issue is still there (Xorg 7.4 from debian experimental packages, radeon driver from today's git). The messages written in Xorg.0.log during vt switch are slightly different from the ones I reported: Changing to VT: (II) AIGLX: Suspending AIGLX clients for VT switch (II) RADEON(0): RADEONRestoreMemMapRegisters() : (II) RADEON(0): MC_FB_LOCATION : 0x1fff0000 0xd3ffd000 (II) RADEON(0): MC_AGP_LOCATION : 0x27ff2000 finished PLL2 finished PLL1 Entering Restore TV Restore TV PLL Restore TVHV Restore TV Restarts Restore Timing Tables Restore TV standard Leaving Restore TV ================ Restoring from (broken) VT: (II) Open ACPI successful (/var/run/acpid.socket) (II) AIGLX: Resuming AIGLX clients after VT switch (II) RADEON(0): Dynamic Clock Scaling Enabled init memmap init common init crtc1 init pll1 restore memmap (II) RADEON(0): RADEONRestoreMemMapRegisters() : (II) RADEON(0): MC_FB_LOCATION : 0xd3ffd000 0x1fff0000 (II) RADEON(0): MC_AGP_LOCATION : 0xffffffc0 restore common restore crtc1 restore pll1 restore LVDS (II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware. (WW) RADEON(0): DRI init changed memory map, adjusting ... (WW) RADEON(0): MC_FB_LOCATION was: 0xd3ffd000 is: 0xd3ffd000 (WW) RADEON(0): MC_AGP_LOCATION was: 0xffffffc0 is: 0xffffffc0 (II) RADEON(0): RADEONRestoreMemMapRegisters() : (II) RADEON(0): MC_FB_LOCATION : 0xd3ffd000 0xd3ffd000 (II) RADEON(0): MC_AGP_LOCATION : 0xffffffc0 (II) Configured Mouse: ps2EnableDataReporting: succeeded (--) Synaptics Touchpad touchpad found (II) Configured Mouse: ps2EnableDataReporting: succeeded Is this still an issue with kms or newer versions of the driver? (In reply to comment #8) > Is this still an issue with kms or newer versions of the driver? Yes, it is (sorry for my lack of updates), but with KMS is different. I'm currently using Debian Squeeze: xserver-xorg-video-radeon 1:6.13.1-2 xserver-xorg 1:7.5+7 xserver-xorg-core 2:1.7.7-8 libdrm2 2.4.21-1~squeeze3 linux-image-2.6.32-5-686 2.6.32-26 (it contains drm from 2.6.34) When KMS is turned on (default behaviour), the flickering stars when (I think) the kernel module is loaded (I don't know if radeon or drm) and when Xorg starts, the flickering is fixed (just like Xorg change some values) and virtual consoles work again. How can I help to debug this issue? > --- Comment #9 from Luigi Toscano <luigi.toscano@tiscali.it> 2010-10-28 13:57:05 PDT ---
> linux-image-2.6.32-5-686 2.6.32-26 (it contains drm from 2.6.34)
>
from .33 (plus various fixes) actually.
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.