https://bugs.freedesktop.org/show_bug.cgi?id=34740
Summary: Invalid EDID on NEC 225WNX
Product: DRI
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: freiheits(a)mail.ru
Created an attachment (id=43837)
--> (https://bugs.freedesktop.org/attachment.cgi?id=43837)
dmesg log
i have a NEC MultiSync 225WNX display, and ATI Radeon 9800 Pro (R350) AGP
with 2_6_37 it works, but in the log I find error and after loading, KDE offers
me set the screen resolution settings manually.
[ 23.745086] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but
no|invalid EDID
[ 24.438301] start_kdeinit (2339): /proc/2339/oom_adj is deprecated, please
use /proc/2339/oom_score_adj instead.
[ 30.772338] ata3.00: configured for UDMA/133
[ 30.772344] ata3: EH complete
[ 31.570015] eth0: no IPv6 routers present
[ 31.885279] EXT4-fs (sda2): re-mounted. Opts: acl,user_xattr,commit=0
[ 31.979079] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but
no|invalid EDID
[ 32.044963] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but
no|invalid EDID
[ 32.140389] EXT4-fs (sda3): re-mounted. Opts: commit=0
[ 43.879049] i2c i2c-0: readbytes: ack/nak timeout
[ 43.879122] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but
no|invalid EDID
[ 52.805480] bootsplash: status on console 0 changed to on
[ 209.310829] fuse init (API version 7.15)
[ 401.118127] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but
no|invalid EDID
--
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=34632
Summary: RV300 clutter test_texture_pick_with_alpha: assertion
failed
Product: DRI
Version: unspecified
Platform: All
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: py(a)luyten.fr
Created an attachment (id=43721)
--> (https://bugs.freedesktop.org/attachment.cgi?id=43721)
standalone test output
I use jhbuild to build gnome-shell. Clutter module compiles fine but when I
make check , then the "test_texture_pick_with_alpha" fails .
ERROR:test-clutter-texture.c:65:test_texture_pick_with_alpha: assertion failed:
(actor == CLUTTER_ACTOR (tex))
Aborted (core dumped)
ATI card : radeon 9600
GL_VENDOR: X.Org R300 Project
GL_RENDERER: Gallium 0.4 on RV350
GL_VERSION: 2.1 Mesa 7.9
The output is attached.
--
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=34626
Summary: Mesa-Gallium with R600 - Framerate limited to 60 fps
after suspend-cycle
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: peterle(a)hottemptation.org
Hello,
I past I thought this is a bug of IOQuake3, but during switching between
Mesa-Classic and Mesa-Gallium I recognized, that the problem only exists with
Mesa-Gallium!
Reproduce:
1. $export vblank_mode=0 // switching of vsync
2. Launch an IOQuake3 based game (Quake3 Arena, OpenArena, World of Padman...)
3. check that VSYNC in IOQuake3 is also disabled!
4. Start a game and set "cg_drawpfs 1", know you should have at the top right
corner a display with your current framerate which is hopefully over 60 fps
5. switch to a tty during playing (should be no problem with
Kernel-Mode-Setting)
6. #pm-suspend (as root)
7. resume from suspend
8. switch back to X11/IOQuake3 -> framerate is limited to 60 fps
To fix this you have to relaunch IOQuake3 or simply type into quake-console
"vid_restart".
With Mesa-Classic and the R600-Driver this is not necessary, it displays always
the maximum possible framerate.
Maybe Gallium doesn't read or forget the environment-variable export_vblank
during resume from suspend?
--
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=33969
Summary: "unable to handle kernel paging request" crash after
playing tuxracer for a few seconds
Product: DRI
Version: unspecified
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: adam.rak(a)streamnovation.com
Created an attachment (id=42998)
--> (https://bugs.freedesktop.org/attachment.cgi?id=42998)
Full dmesg after the crash
Hardware is Fusion Zacate APU (HD6310)
Mesa is commit ec96b0ecdbe723f4664188010c7f86d5d7f41d82 checkout
ddx is commit a4899db96029acde6cd400fc0541693a487898e7 checkout
linux kernel is 2.6.38-rc3 commit 44f2c5c841da1b1e0864d768197ab1497b5c2cc1
X.Org X Server 1.7.7 (debian squeeze)
Running nexuiz crashes the X when entering play mode. (no apparent error log)
Running(and playing) extremetuxracer produces a kernel oops after a few
seconds, the dmesg is in the attachment.
--
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=33681
Summary: Random system lockup with KMS, Mobility Radeon HD3470
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: jsagarribay(a)gmail.com
Created an attachment (id=42685)
--> (https://bugs.freedesktop.org/attachment.cgi?id=42685)
kernel log
The computer often locks itself, the panel suddenly loses the image (it
sometimes blooms, or get filled with a solid color or a pattern of vertical
white and grey stripes). I don't know how to trigger the bug, it can happen
anytime, even with an idle system.
It has happened to me since I started using KMS, it was stable both with
radeonHD and radeon drivers in UMS mode. The frequency of the problem has
varied a lot; with the first KMS versions it happened a lot, then it seemed to
be fixed with some kernel versions, but reappeared with others... As the
problem is random, it can happen after a few minutes of uptime, or after some
hours, or not happen at all.
At first, I thougth the kernel was completely dead, but I recently found out
that I can use SysRq+S and SysRq+T to get some logs. If I try to reboot with
SysRq+B the system locks fully and doesn't react to anything, I always have to
do a hard reboot.
I'll attach lspci, one X log and three differen kernel logs.
--
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=33301
Summary: dynpm doesn't downclock
Product: DRI
Version: XOrg 6.7.0
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: cristiklein(a)gmail.com
Hello,
I have an ATI Mobility Radeon HD 2400. I am using Linux 2.6.37. Currently,
dynpm does not down-clock the GPU for me. dmesg is filled with the following
messages:
[245199.552075] [drm:r600_pm_get_dynpm_state], Requested: e: 30000 m: 40000 p:
16
(about 10 messages / second)
I attach a script with all the necessary details.
Cristi.
--
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.