https://bugs.freedesktop.org/show_bug.cgi?id=32556
Summary: screen flickers all the time with desktop image
appearing only briefly
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: 3ntr0p13(a)gmail.com
Created an attachment (id=41344)
--> (https://bugs.freedesktop.org/attachment.cgi?id=41344)
dmesg
Machine is the same as in bug report 28331 although with different software
components: Acer Aspire L5100 with an AMD Athlon 64 X2 Dual Core Processor
4000+, this time running a 64 bits debian squeeze.
The machine is a small factor desktop machine designed around laptop
components, so the graphic card is an integrated radeon x1200.
When running a linux vanilla kernel 2.6.37-rc6, the screen flickers all the
time
making the machine unusable, while with debian kernel 2.6.32-5 such "flick to
black" event occur from time to time, making it annoying but usable.
While booting with radeon.modeset=0 the problem doesn't exhibits itself
The following packages version from debian squeeze are installed:
xserver-xorg 1:7.5+8
xserver-xorg-core 2:1.7.7-10
xserver-xorg-video-radeon 1:6.13.1-2+squeeze1
Please find attached Xorg.0.log, dmesg, register dumps for ums and kms for that
machine (when booted on 2.6.37-rc6).
Regards,
Gildas
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=32422
Summary: Large images displayed in Firefox appear corrupted
Product: DRI
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: da_fox(a)mad.scientist.com
Created an attachment (id=41150)
--> (https://bugs.freedesktop.org/attachment.cgi?id=41150)
Picture describing a thousand words.
"A picture says more than a thousand words" (aka see attachment)
This is what happens when I try to view the XKCD "Online Communities 2" map
(http://xkcd.com/802_large/) or other large images in firefox.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=32399
Summary: KMS:RS480:X200M LCD Monitor on VGA-0 shows wavy
picture
Product: Mesa
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: high
Component: Drivers/DRI/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: evillanueva(a)roundbox.com
Depends on: 32350
When second LCD monitor is connected to VGA-0 picture is wavy.
The text on the screen flutters.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=32319
Summary: Display fades to white screen instead of blanking out
in DPMS mode on a Sony Vaio VPCEC3L1E
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: bugs.xorg(a)boris64.net
Created an attachment (id=41011)
--> (https://bugs.freedesktop.org/attachment.cgi?id=41011)
Fade-to-white-picture No.1
On my new Sony Vaio laptop (VPCEC3L1E) the screen fades to white
(with backlights on, i think) instead of simply blanking out.
This can be reproduced by running "xset dpms force off" or
by simply waiting until powermanagement kicks in.
The graphics card used is a radeon 5xxx(?)
(01:00.0 VGA compatible controller: ATI Technologies Inc Device 68e0).
This happens on console and in X.
I'll attach some pictures showing the issue.
Thanks for any help!
PS: I hope i did choose the correct product/component for
this type of bug.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=31230
Summary: [RV250Lf] Corrupted screen after resume
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: johannesobermayr(a)gmx.de
Created an attachment (id=39897)
--> (https://bugs.freedesktop.org/attachment.cgi?id=39897)
specific part of /var/log/messages (~13 MiB, "drm.debug=255")
After resume the screen is totally corrupted.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=31213
Summary: [drm] *ERROR* with KMS (any kernels 2.6.3x.x) and ati
mobility radeon X300
Product: DRI
Version: XOrg CVS
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: djnass_18(a)hotmail.com
when loading the 'radeon' driver with modeset=1 (KMS enabled)
the following error appears in dmesg | grep drm
[drm:r100_ring_test] *ERROR* radeon: ring test failed
(sracth(0x15E4)=0xCAFEDEAD)
[drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22).
the result is that OpenGL renderer with be the 'software rasterizer'. and
performance is obviously crippled.
glxinfo returns:
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.8.1
The error occurs with kernels 2.6.33.4, 2.6.35.7 and even the latest at the
time 2.6.36. The pc is a toshiba satellite m40-185 laptop with ati mobility
radeon X300 (rv370) gpu.
Additionally, I have tried installing the git versions of libdrm, mesa, and
xf86-video-ati to this date (29/10/2010) with Gallium support (enabled in turn
--enable-gallium, --enable-gallium-radeon and even both, using llvm (version
2.8) compiler. The problem persists.
The only way to get 3d accelaration is to disable KMS. then dmesg | grep drm
seems to load up fine (see here: http://pastebin.com/vNfyeq7P). But then I have
problems with 3d applications 'competing' to stay on top - they don't seem to
be able to work well with KDE4 compositing effects. To avoid that I have to
disable the compositing effects ( see here for in depth explanation and some
Xorg.0.log and dmesg outputs
http://www.linuxquestions.org/questions/slackware-14/3d-applications-compet…
)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=30620
Summary: KMS on RS100: no display on VGA
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: zajec5(a)gmail.com
I've bug report from user with old notebook with ATI 320M (RS100). She
installed openSUSE 11.3 which comes with 2.6.34 and can not get driver display
anything.
The important part is that notebook's PANEL is broken and she uses VGA for
external monitor.
There are two KMS cases I got tested by her:
1) "vga=0x31a" ─ black VGA screen right after booting start
2) "" (no vga) ─ black VGA screen right after booting start
So I asked to experiment with UMS a little:
3) "vga=0x31a radeon.modeset=0 3" ─ radeonfb loads, VGA works!
4) "vga=0x31a radeon.modeset=0" ─ radeonfb works, black VGA screen on X start
Without radeonfb:
5) "radeon.modeset=0 3" ─ pure console works on VGA, no radeonfb
6) "radeon.modeset=0" ─ pure console works on VGA, black VGA on X start
My conclusions:
1) KMS can not initialize VGA
2) UMS can not initialize VGA
3) radeonfb *can* initialize VGA
4) There is no conflict with radeonfb, as dropping "vga=0x31a" does not help
What else can I ask for to make it debuggable?
I thought of Xorg.0.log but it may be hard to get for her as she had to mount
some USB storage in console and copy file to it.
Taking "dmesg | grep drm" could be easier. Would it be useful?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=30325
Summary: video=1280x720@50 no longer works
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: marius.groeger(a)web.de
With the current drm-radeon-testing my grub cmdline option video=1280x720@50 no
longer works (RS780, output to LCD TV via HDMI). The fbcon apparently is
enabled, but the TV doen't get a displayable picture anymore. Booting with
d-r-t from 6 weeks ago works and correctly uses the EDID reported 1280x720@50
mode.
I did ask the same thing on the dri-devel mailing list and received no answer
so I'm filing this bug both as another humble nudge to the authors of the drm
video= code, and as a more persistent reminder of the issue.
Thanks
Marius
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=30227
Summary: Radom X.org freeze by a GPU lockup
Product: DRI
Version: XOrg CVS
Platform: PowerPC
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: kronat(a)tiscali.it
Created an attachment (id=38743)
--> (https://bugs.freedesktop.org/attachment.cgi?id=38743)
dmesg after the fail
Apparently random GPU lockup (ati r300), with X.org freeze.
It happens more frequently if I compile and I switch over many applications
(firefox, terminal, opera). Attached there is the dmesg after the fail (I could
continue to work on others console - ctrl+alt+f1,2,3..).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=29941
Summary: radeon/KMS: Screen hotplugging does not work any more
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: direx(a)betriebsdirektor.de
I noticed that in recent kernel versions the runtime detection of newly added
monitors does not work properly.
When I plug in my TV (DVI2HDMI) after booting I cannot enable it. xrandr
correctly shows a new screen and I can even enable the output, but the TV
screen stays black. Restarting X does not help.
The driver also seems to recognize the port status after plugging it in
(/sys/class/drm/card0-DVI-I-2/status) changes from "disconnected" to
"connected".
When I plug the HDMI cable in _before_ booting my computer the TV works just
fine.
GFX: Radeon HD 3870
Linux: 2.6-git (issue appeared in 2.6.35) with KMS
Mesa: git
libdrm: git
xf86-video-ati: git
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.