dri-devel August 2010

dri-devel@lists.freedesktop.org

82 participants
335 discussions

[Bug 28294] New: [r300g] Unigine Sanctuary: almost everything is black
by bugzilla-daemon＠freedesktop.org 31 Oct '10

31 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=28294 Summary: [r300g] Unigine Sanctuary: almost everything is black Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: drakkk(a)centrum.cz Created an attachment (id=35899) --> (https://bugs.freedesktop.org/attachment.cgi?id=35899) terminal output I noticed ARB_half_float_vertex support in mesa this morning which is needed for Unigine. I gave it a try and it finally starts. However almost everything is black except for fires from torches (screenshot attached). Terminal is full of mesa user errors and there are some missing opcodes like: r300: Unknown TGSI/RC opcode: KILP r300: Unknown TGSI/RC opcode: BGNLOOP r300: Unknown TGSI/RC opcode: BRK r300: Unknown TGSI/RC opcode: ENDLOOP r300 FP: Compiler Error: r500_fragprog_emit.c::translate_rgb_op(): translate_rgb_op(1): unknown opcode Using a dummy shader instead. If there's an 'unknown opcode' message, please file a bug report and attach this log. r300 VP: Compiler error: Unknown opcode 32 Using a dummy shader instead. If there's an 'unknown opcode' message, please file a bug report and attach this log. Probably more than one problem. However this is a big improvement indeed. This may be the first time Unigine actually tries to render something with open source drivers :-) 01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon Mobility X1600] -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 50

[PATCH] drm/radeon/kms: add query for crtc hw id from crtc id to get info
by Jerome Glisse 25 Oct '10

25 Oct '10

Userspace need to know the hw crtc id (0, 1, 2, ...) from the drm crtc id. Bump the minor version so userspace can enable conditionaly features depend on this. Signed-off-by: Jerome Glisse <jglisse(a)redhat.com> --- drivers/gpu/drm/radeon/radeon_drv.c | 3 ++- drivers/gpu/drm/radeon/radeon_kms.c | 18 ++++++++++++++++++ include/drm/radeon_drm.h | 1 + 3 files changed, 21 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/radeon/radeon_drv.c b/drivers/gpu/drm/radeon/radeon_drv.c index b3749d4..df96ace 100644 --- a/drivers/gpu/drm/radeon/radeon_drv.c +++ b/drivers/gpu/drm/radeon/radeon_drv.c @@ -44,9 +44,10 @@ * - 2.1.0 - add square tiling interface * - 2.2.0 - add r6xx/r7xx const buffer support * - 2.3.0 - add MSPOS + 3D texture + r500 VAP regs + * - 2.4.0 - add crtc id query */ #define KMS_DRIVER_MAJOR 2 -#define KMS_DRIVER_MINOR 3 +#define KMS_DRIVER_MINOR 4 #define KMS_DRIVER_PATCHLEVEL 0 int radeon_driver_load_kms(struct drm_device *dev, unsigned long flags); int radeon_driver_unload_kms(struct drm_device *dev); diff --git a/drivers/gpu/drm/radeon/radeon_kms.c b/drivers/gpu/drm/radeon/radeon_kms.c index d3657dc..04ad452 100644 --- a/drivers/gpu/drm/radeon/radeon_kms.c +++ b/drivers/gpu/drm/radeon/radeon_kms.c @@ -98,11 +98,15 @@ int radeon_info_ioctl(struct drm_device *dev, void *data, struct drm_file *filp) { struct radeon_device *rdev = dev->dev_private; struct drm_radeon_info *info; + struct radeon_mode_info *minfo = &rdev->mode_info; uint32_t *value_ptr; uint32_t value; + struct drm_crtc *crtc; + int i, found; info = data; value_ptr = (uint32_t *)((unsigned long)info->value); + value = *value_ptr; switch (info->request) { case RADEON_INFO_DEVICE_ID: value = dev->pci_device; @@ -116,6 +120,20 @@ int radeon_info_ioctl(struct drm_device *dev, void *data, struct drm_file *filp) case RADEON_INFO_ACCEL_WORKING: value = rdev->accel_working; break; + case RADEON_INFO_CRTC_FROM_ID: + for (i = 0, found = 0; i < 6; i++) { + crtc = (struct drm_crtc *)minfo->crtcs[i]; + if (crtc && crtc->base.id == value) { + value = i; + found = 1; + break; + } + } + if (!found) { + DRM_ERROR("unknown crtc id %d\n", value); + return -EINVAL; + } + break; default: DRM_DEBUG("Invalid request %d\n", info->request); return -EINVAL; diff --git a/include/drm/radeon_drm.h b/include/drm/radeon_drm.h index 81e614b..3ff9fc0 100644 --- a/include/drm/radeon_drm.h +++ b/include/drm/radeon_drm.h @@ -902,6 +902,7 @@ struct drm_radeon_cs { #define RADEON_INFO_NUM_GB_PIPES 0x01 #define RADEON_INFO_NUM_Z_PIPES 0x02 #define RADEON_INFO_ACCEL_WORKING 0x03 +#define RADEON_INFO_CRTC_FROM_ID 0x04 struct drm_radeon_info { uint32_t request; -- 1.7.0.1

5 6

[Bug 29367] New: [KMS] Assertion `boi->space_accounted' failed. on rv280
by bugzilla-daemon＠freedesktop.org 20 Oct '10

20 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=29367 Summary: [KMS] Assertion `boi->space_accounted' failed. on rv280 Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r200 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: randrik(a)mail.ru With latest mesa (commit 313df4156279f84ebc5b98a7540820b994762650 Author: Jerome Glisse <jglisse(a)redhat.com> Date: Mon Aug 2 14:21:33 2010 -0400 r600g: add autogenerated reg definition + debug print cleanup) i have very reproductable bug with even glxgears, but also with ray demo. Ray demo aborts at startup, glxgears window must be resized before bug kill it. Xserver - commit a2c13f0d6548310e3cd115cf486d3e43edf23dcc Author: Keith Packard <keithp(a)keithp.com> Date: Wed Jul 14 12:57:29 2010 -0700 Bump to version 1.8.99.905 (1.9 RC5) libdrm - commit b803918f3f77c62edf22e78cb2095be399753423 Author: Chris Wilson <chris(a)chris-wilson.co.uk> Date: Thu Jul 1 22:38:54 2010 +0100 drm mode: Return -errno on drmIoctl() failure ddx - commit aca0a8669b538d58f018f95c9b22e6b3ec1ffe50 Author: Gaetan Nadon <memsize(a)videotron.ca> Date: Wed Jul 21 16:49:04 2010 -0400 config: add comments for main statements kernel - drm-radeon-testing (also tried with 2.6.35) up to commit ab9e1f5966591dc3e811418e96ba04f284c52458 Author: Dave Airlie <airlied(a)redhat.com> Date: Tue Jul 13 11:11:11 2010 +1000 drm/radeon: add basic zmask/hiz support (v4) ----------- Hw - rv280/agp. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 29327] New: radeon interrupts don't fire with MSI
by bugzilla-daemon＠freedesktop.org 18 Oct '10

18 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=29327 Summary: radeon interrupts don't fire with MSI Product: DRI Version: DRI 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: tdroste(a)gmx.de Created an attachment (id=37470) --> (https://bugs.freedesktop.org/attachment.cgi?id=37470) dmesg without MSI If I boot the current d-r-t kernel with MSI enabled the radeon module doesn't fire any interrupts. Without the interrupts and vblank_mode in driconf set to 3 the screen stops refreshing. This is always reproducible. To make it work again I have to boot with pci=nomsi. Software versions kernel current d-r-t (2.6.35-rc2) ddx, mesa, xserver git master Hardware Radeon X1950pro RV570 (AGP) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 15

[Bug 29244] New: [wine][r300g] Spore Creature Creator segfaults
by bugzilla-daemon＠freedesktop.org 13 Oct '10

13 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=29244 Summary: [wine][r300g] Spore Creature Creator segfaults Product: Mesa Version: git Platform: Other URL: http://www.spore.com/trial OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: sa(a)whiz.se Created an attachment (id=37369) --> (https://bugs.freedesktop.org/attachment.cgi?id=37369) backtrace of crash The Spore Creature Creator game (running in Wine) segfaults on start: state_tracker/st_manager.c:475: st_context_notify_invalid_framebuffer: Assertion `stfb && stfb->iface == stfbi' failed. It works (or at least starts) if software mode is forced. Doesn't seem to be a regression, as it doesn't work on the 7.8 branch either. System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: RV570 -- Model: Asus EAX1950Pro 256MB -- Display connector: DVI -- xf86-video-ati: cdeb1949c820242f05a8897d3ddd0718f204dacf -- xserver: 1.8.99.904 (1.9.0 RC 4) -- mesa: 451a0ddb190e5185372fed9ec57d24a822442ecc -- drm: 6ea2bda5f5ec8f27359760ce580fdad3df0464df -- kernel: 2.6.35-rc5 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 8

[Bug 29012] New: [r300g] Driver needs some kind of force_s3tc_enable option
by bugzilla-daemon＠freedesktop.org 11 Oct '10

11 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=29012 Summary: [r300g] Driver needs some kind of force_s3tc_enable option Product: Mesa Version: git Platform: All OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: rankincj(a)googlemail.com Some games (such as World of Warcraft) need S3TC texture support, and so will crash if the OpenGL S3TC extensions are not advertised. Currently, the only way to make Gallium advertise the S3TC extensions is to load the IP-encumbered libtxc_dxtn library. WoW can run successfully using the r300c driver without the libtxc_dxtn, provided the force_s3tc_enable option is used. (There are some issues with corrupt textures, although some of these issues might be caused e.g. by r300c not supporting texture cache regions. However, my point is that WoW doesn't crash instantly with a null pointer exception if the S3TC extensions are available.) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 29834] New: System freeze upon X startup with KMS enabled (RV730)
by bugzilla-daemon＠freedesktop.org 04 Oct '10

04 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=29834 Summary: System freeze upon X startup with KMS enabled (RV730) Product: DRI Version: XOrg 6.7.0 Platform: Other OS/Version: All Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: info(a)noctus.net Created an attachment (id=38216) --> (https://bugs.freedesktop.org/attachment.cgi?id=38216) kern.log messages upon freeze Trying to start X with KMS enabled on my HD4670 (RV730) card freezes the system and I have to SysRq out of that situation. Since this only happens with the final release of the 2.6.35 kernel I am currently stuck with the RC6 which does not display this behavior. See the attached kern.log output in case of such freeze. I am running the latest Git masters of both xf86-video-ati (5a7c9d94733a0db1d3565447acc9f0e751db5950 here ATM) as well as mesa (f3ec111b0af9d268e6b3c6d3226a448d19e45d8c here ATM). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 14

[Bug 29513] New: Kwin crash when i change the decoration.
by bugzilla-daemon＠freedesktop.org 04 Oct '10

04 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=29513 Summary: Kwin crash when i change the decoration. Product: Mesa Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: marokanski.kazak(a)gmail.com I reported this bug to bugs.kde.org and they said that the crash is because of the video driver so i should send it upstream. I have Mesa 7.8.2 and Xorg 1.8.0- the default coming with openSUSE 11.3. My video card is ATI Radeon HD3450. Here is a copy of the bug i sent to Bugs.kde Application: kwin (4.5.00 (KDE 4.5.0)) KDE Platform Version: 4.5.00 (KDE 4.5.0) Qt Version: 4.6.3 Operating System: Linux 2.6.34-12-default i686 Distribution: "openSUSE 11.3 (i586)" -- Information about the crash: - What I was doing when the application crashed: Kwin crashes every time i change the window decoration. It recovers almost instantly with the new decoration that i selected. Sometimes after recovery the desktop effects are stopped and i have to turn them on. The crash also occurrs when i setup transperant windows with exactly the same crash. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin), signal: Segmentation fault [KCrash Handler] #7 0xb6b2727b in dri2DrawableGetMSC (psc=0x83f6ff8, pdraw=0x0, ust=0xbfb51a28, msc=0xbfb51a20, sbc=0xbfb51a18) at dri2_glx.c:226 #8 0xb6b00107 in __glXGetVideoSyncSGI (count=0xbfb51a6c) at glxcmds.c:2317 #9 0xb761d5c4 in KWin::SceneOpenGL::waitSync (this=0x89a96c0) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/scene_opengl.cpp:781 #10 0xb7633874 in KWin::SceneOpenGL::flushBuffer (this=0x89a96c0, mask=32, damage=...) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/scene_opengl.cpp:830 #11 0xb768588a in KWin::SceneOpenGL::paint (this=0x89a96c0, damage=..., toplevels=...) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/scene_opengl.cpp:761 #12 0xb7662794 in KWin::Workspace::performCompositing (this=0x81a2a48) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/composite.cpp:454 #13 0xb7695a5b in KWin::Workspace::qt_metacall (this=0x81a2a48, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfb51d5c) at /usr/src/debug/kdebase-workspace-4.5.0/build/kwin/workspace.moc:583 #14 0xb669befd in QMetaObject::metacall (object=0x81a2a48, cl=QMetaObject::InvokeMetaMethod, idx=190, argv=0xbfb51d5c) at kernel/qmetaobject.cpp:237 #15 0xb66aafe8 in QMetaObject::activate (sender=0x81a2cf8, m=0xb67b25a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295 #16 0xb66f7a35 in QTimer::timeout (this=0x81a2cf8) at .moc/release-shared/moc_qtimer.cpp:134 #17 0xb66b08e6 in QTimer::timerEvent (this=0x81a2cf8, e=0xbfb522b0) at kernel/qtimer.cpp:271 #18 0xb66a8774 in QObject::event (this=0x81a2cf8, e=0xbfb522b0) at kernel/qobject.cpp:1212 #19 0xb5bcfc64 in QApplicationPrivate::notify_helper (this=0x8070350, receiver=0x81a2cf8, e=0xbfb522b0) at kernel/qapplication.cpp:4302 #20 0xb5bd7bf7 in QApplication::notify (this=0xbfb525e4, receiver=0x81a2cf8, e=0xbfb522b0) at kernel/qapplication.cpp:3706 #21 0xb719b2c1 in KApplication::notify (this=0xbfb525e4, receiver=0x81a2cf8, event=0xbfb522b0) at /usr/src/debug/kdelibs-4.5.0/kdeui/kernel/kapplication.cpp:310 #22 0xb75f7c4f in KWin::Application::notify (this=0xbfb525e4, o=0x81a2cf8, e=0xbfb522b0) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/main.cpp:372 #23 0xb6695e0e in QCoreApplication::notifyInternal (this=0xbfb525e4, receiver=0x81a2cf8, event=0xbfb522b0) at kernel/qcoreapplication.cpp:726 #24 0xb66c470e in sendEvent (this=0x8070b28) at kernel/qcoreapplication.h:215 #25 QTimerInfoList::activateTimers (this=0x8070b28) at kernel/qeventdispatcher_unix.cpp:618 #26 0xb66c4ffd in QEventDispatcherUNIX::processEvents (this=0x806f280, flags=...) at kernel/qeventdispatcher_unix.cpp:939 #27 0xb5c80f5a in QEventDispatcherX11::processEvents (this=0x806f280, flags=...) at kernel/qeventdispatcher_x11.cpp:152 #28 0xb669511d in QEventLoop::processEvents (this=0xbfb52534, flags=...) at kernel/qeventloop.cpp:149 #29 0xb6695319 in QEventLoop::exec (this=0xbfb52534, flags=...) at kernel/qeventloop.cpp:201 #30 0xb6699c70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #31 0xb5bcd164 in QApplication::exec () at kernel/qapplication.cpp:3581 #32 0xb7693fab in kdemain (argc=3, argv=0xbfb52834) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/main.cpp:531 #33 0x0804860b in main (argc=3, argv=0xbfb52834) at /usr/src/debug/kdebase-workspace-4.5.0/build/kwin/kwin_dummy.cpp:3 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 5

[Bug 29580] New: Pixmap corruption in gnome-shell when many icons are loaded
by bugzilla-daemon＠freedesktop.org 04 Oct '10

04 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=29580 Summary: Pixmap corruption in gnome-shell when many icons are loaded Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r200 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: fred(a)crozat.net Created an attachment (id=37871) --> (https://bugs.freedesktop.org/attachment.cgi?id=37871) corrupted pixmaps hardware : 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon 9100 IGP (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device f362 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16 Memory at e8000000 (32-bit, prefetchable) [size=64M] I/O ports at c000 [size=256] Memory at ec020000 (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at ec000000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon kernel : 2.6.34-12-desktop (openSUSE 11.3), using KMS radeon driver xorg driver : 6.13.1 Mesa 7.8.2 (openSUSE 11.3 package) when starting GNOME-Shell (2.29.1) with clutter 1.2.8 (or gnome-shell git, compiled against clutter 1.3 branch), if I open gnome-shell application menu, all pixmaps displayed in gnome-shell become corrupted, as well as application window shadows. Kernel sometimes states : radeon 0000:01:05.0: e3e1b280 reserve failed for wait -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 9

Radeon 3650HD laptop LVDS lid open/closed detection problem
by Pasi Kärkkäinen 21 Sep '10

21 Sep '10

Hello, After fixing the dvi/hdmi detection problem I now have another problem with the HP EliteBook 8530p, which has Radeon 3650HD adapter. Here's a summary of the environment: - laptop connected to a docking station. - external display in use, connected with DVI to the dock. - laptop lid closed, so internal LVDS display is not used. Now, when I start the laptop, I can see the BIOS and grub on the external DVI display. All fine so far. I select the Fedora 13 kernel, and Linux starts. I see the Fedora graphical boot on the external DVI display, just like it should be. GDM login prompt appears on the external DVI display, still everything fine. And then it goes wrong. After I login to X, the external display only shows the background picture.. it turns out the desktop stuff has been started to the internal LVDS display, which shouldn't be used at all since the laptop lid is closed!! When the laptop lid is closed, and external display is connected, I want to use only the external display.. Any ideas how to troubleshoot this one? -- Pasi

4 20

← Newer
1
...
6
7
8
9
10
11
12
...
34
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel August 2010