dri-devel August 2011

dri-devel@lists.freedesktop.org

77 participants
464 discussions

[Bug 25052] kernel modesetting still does not work
by bugzilla-daemon＠bugzilla.kernel.org 09 Aug '11

09 Aug '11

https://bugzilla.kernel.org/show_bug.cgi?id=25052 --- Comment #22 from Elmar Stellnberger <estellnb(a)gmail.com> 2011-08-09 17:44:18 --- Any work in progress on this issue? Many people have to fall back to the proprietary drivers if KMS is not avaiable or functional. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 0

[PATCH] drm/radeon/kms: don't enable connectors that are off in the hotplug handler
by alexdeucher＠gmail.com 09 Aug '11

09 Aug '11

From: Alex Deucher <alexander.deucher(a)amd.com> If we get a hotplug event on an connector that is off, don't attempt to turn it on or off, it should already be off. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=728228 Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Cc: stable(a)kernel.org --- drivers/gpu/drm/radeon/radeon_connectors.c | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/radeon/radeon_connectors.c b/drivers/gpu/drm/radeon/radeon_connectors.c index cbfca3a..8365f75 100644 --- a/drivers/gpu/drm/radeon/radeon_connectors.c +++ b/drivers/gpu/drm/radeon/radeon_connectors.c @@ -54,6 +54,10 @@ void radeon_connector_hotplug(struct drm_connector *connector) radeon_hpd_set_polarity(rdev, radeon_connector->hpd.hpd); + /* if the connector is already off, don't turn it back on */ + if (connector->dpms != DRM_MODE_DPMS_ON) + return; + /* powering up/down the eDP panel generates hpd events which * can interfere with modesetting. */ -- 1.7.1.1

1 0

[Bug 22312] radeon 0000:01:00.0: Invalid ROM contents
by bugzilla-daemon＠bugzilla.kernel.org 09 Aug '11

09 Aug '11

https://bugzilla.kernel.org/show_bug.cgi?id=22312 xpressrazor(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xpressrazor(a)gmail.com --- Comment #1 from xpressrazor(a)gmail.com 2011-08-09 12:20:44 --- [ 15.931030] Linux video capture interface: v2.00 [ 15.948984] [drm] radeon defaulting to kernel modesetting. [ 15.948987] [drm] radeon kernel modesetting enabled. [ 15.949030] radeon 0000:01:00.0: enabling device (0000 -> 0003) [ 15.949040] radeon 0000:01:00.0: found PCI INT A -> IRQ 11 [ 15.949046] radeon 0000:01:00.0: sharing IRQ 11 with 0000:00:02.0 [ 15.949051] radeon 0000:01:00.0: sharing IRQ 11 with 0000:00:16.0 [ 15.949055] radeon 0000:01:00.0: sharing IRQ 11 with 0000:00:1a.0 [ 15.949114] radeon 0000:01:00.0: sharing IRQ 11 with 0000:02:00.0 [ 15.949126] radeon 0000:01:00.0: setting latency timer to 64 [ 15.949409] [drm] initializing kernel modesetting (CAICOS 0x1002:0x6760). [ 15.949466] [drm] register mmio base: 0xE1700000 [ 15.949468] [drm] register mmio size: 131072 [ 15.949997] radeon 0000:01:00.0: Invalid ROM contents [ 15.950088] radeon 0000:01:00.0: Invalid ROM contents [ 15.950116] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM [ 15.950120] radeon 0000:01:00.0: Fatal error during GPU init [ 15.950124] [drm] radeon: finishing device. [ 15.950126] [TTM] Memory type 2 has not been initialized. [ 15.951164] vga_switcheroo: disabled [ 15.951383] radeon: probe of 0000:01:00.0 failed with error -22 I have similar problem. This problem comes in all kernels(2.6.38-8, 2.6.38-10, 3.0.0-0300 and 3.0.1). I have Intel sandy bridge i5 processor. $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 VGA compatible controller: ATI Technologies Inc NI Seymour [AMD Radeon HD 6470M] $ lspci -v -s 00:02.0 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04c1 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at e0000000 (64-bit, non-prefetchable) [size=4M] Memory at d0000000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 $ lspci -v -s 01:00.0 01:00.0 VGA compatible controller: ATI Technologies Inc NI Seymour [AMD Radeon HD 6470M] (prog-if 00 [VGA controller]) Subsystem: Dell Device 04c1 Flags: fast devsel, IRQ 11 Memory at c0000000 (64-bit, prefetchable) [disabled] [size=256M] Memory at e1700000 (64-bit, non-prefetchable) [disabled] [size=128K] I/O ports at 4000 [disabled] [size=256] Expansion ROM at e1720000 [disabled] [size=128K] Capabilities: <access denied> Kernel modules: radeon $ uname -r 2.6.38-8-generic Above 3.0 kernel intel's card seems to work a lot better, but radeon error comes anyway. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 0

[Bug 39162] New: 3.0.0-r5: ftrace: BUG & OOPS
by bugzilla-daemon＠bugzilla.kernel.org 09 Aug '11

09 Aug '11

https://bugzilla.kernel.org/show_bug.cgi?id=39162 Summary: 3.0.0-r5: ftrace: BUG & OOPS Product: Drivers Version: 2.5 Kernel Version: 3.0-rc5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: maciej.rutecki(a)gmail.com CC: rjw(a)sisk.pl, maciej.rutecki(a)gmail.com Regression: Yes Subject : 3.0.0-r5: ftrace: BUG & OOPS Submitter : Brian Marete <marete(a)toshnix.com> Date : 2011-07-07 10:23 Message-ID : CAHVUoiRRGY62BZOMYPYxytG569MD0=8=TEN9pCwYefDBg+J+uQ(a)mail.gmail.com References : http://marc.info/?l=linux-kernel&m=131003426121018&w=2 This entry is being used for tracking a regression from 2.6.39. Please don't close it until the problem is fixed in the mainline. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 4

[Bug 39897] Graphical glitches in some games on Evergreen
by bugzilla-daemon＠freedesktop.org 09 Aug '11

09 Aug '11

https://bugs.freedesktop.org/show_bug.cgi?id=39897 --- Comment #14 from Alex <cerebro.alexiel(a)gmail.com> 2011-08-08 23:30:18 PDT --- alex@Leon:~/Projects/Games/CrayonPhysicsDeluxe$ LIBGL_DEBUG=verbose ./launcher <snip> libGL: OpenDriver: trying /usr/lib/dri/tls/r600_dri.so libGL: OpenDriver: trying /usr/lib/dri/r600_dri.so libGL error: dlopen /usr/lib/dri/r600_dri.so failed (/usr/lib/dri/r600_dri.so: cannot open shared object file: No such file or directory) libGL: OpenDriver: trying /usr/lib/dri-alternates/tls/r600_dri.so libGL: OpenDriver: trying /usr/lib/dri-alternates/r600_dri.so libGL error: dlopen /usr/lib/dri-alternates/r600_dri.so failed (/usr/lib/dri-alternates/r600_dri.so: cannot open shared object file: No such file or directory) libGL: OpenDriver: trying /usr/lib32/dri/tls/r600_dri.so libGL: OpenDriver: trying /usr/lib32/dri/r600_dri.so <snip> alex@Leon:~$ find / -name "r600_dri.so" 2> /dev/null /usr/lib32/dri-alternates/r600_dri.so /usr/lib32/dri/r600_dri.so /usr/lib/x86_64-linux-gnu/dri/r600_dri.so alex@Leon:~$ file /usr/lib32/dri/r600_dri.so /usr/lib32/dri-alternates/r600_dri.so /usr/lib32/dri/r600_dri.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped /usr/lib32/dri-alternates/r600_dri.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped alex@Leon:~$ md5sum /usr/lib32/dri-alternates/r600_dri.so /usr/lib32/dri/r600_dri.so a8b52ca9129e3cc2902f9a9473866972 /usr/lib32/dri-alternates/r600_dri.so fdef193b5e49473c741f3dbfad0c4737 /usr/lib32/dri/r600_dri.so alex@Leon:~$ dpkg -S /usr/lib32/dri/r600_dri.so /usr/lib32/dri-alternates/r600_dri.so ia32-libs: /usr/lib32/dri/r600_dri.so ia32-libs: /usr/lib32/dri-alternates/r600_dri.so alex@Leon:~$ sudo apt-cache show ia32-libs Package: ia32-libs Priority: optional Section: universe/libs Installed-Size: 193896 Maintainer: Ubuntu Developers <ubuntu-devel-discuss(a)lists.ubuntu.com> Original-Maintainer: Debian ia32-libs Team <pkg-ia32-libs-maintainers(a)lists.alioth.debian.org> Architecture: amd64 Version: 20090808ubuntu13 Filename: pool/universe/i/ia32-libs/ia32-libs_20090808ubuntu13_amd64.deb Origin: Ubuntu So that's where the issue come from : a very old ia32-libs package. But on the xorg-edgers home page, there is the following message : == New in the PPA - 2011/06/30 == Multiarch xserver/mesa is in the process of being uploaded to natty and oneiric, this transition will take some time to work out and it's advised not to use the PPA if you are using proprietary drivers. Should I fill a bug anyway ? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

drm/i915: Disabling unused outputs on CPT is broken
by Keith Packard 08 Aug '11

08 Aug '11

Here's a fun sequence: $ xrandr --output LVDS1 --auto --crtc 1 $ sudo chvt 1 (then switch back to X) The LVDS goes black. Why? The LVDS is *disabled*. Turns out that the cause was that after the mode was all nicely set, intel_disable_pch_ports went and turned it back off. Well, a couple of weeks ago, we found that intel_disable_pch_ports was doing the same thing to DP ports, and the cause was that the way to tell which port a DP output was running from is different on CPT that on every other chip. We fixed that, but didn't (foolishly) review the non-DP code. Oddly, the non-DP code had essentially the same bug: [PATCH 3/4] drm/i915: Fix PCH port pipe select in CPT disable paths Also in this sequence is some code that validates the LVDS panel power sequencing which discovered that the LVDS panel wasn't being disabled correctly because the LVDS registers were locked in the DPMS function. Instead of trying to get the LVDS locking right, I've just unlocked the registers in the lvds initialization code and left them unlocked after that: [PATCH 1/4] drm/i915: Wait for LVDS panel power sequence [PATCH 2/4] drm/i915: Leave LVDS registers unlocked Finally, I removed an unused argument to dp_pipe_enable while I was poking around in that code: [PATCH 4/4] drm/i915: Remove unused 'reg' argument to dp_pipe_enable -- keith.packard(a)intel.com

2 17

[PATCH 1/2] radeon: Allow panel preferred EDID to override BIOS native mode
by Matthew Garrett 08 Aug '11

08 Aug '11

We have two sources of information about panel capabilities on mobile radeon - the BIOS, which gives us a native mode, and the panel's preferred mode. In theory these two will always match, but there's some corner cases where the BIOS hasn't been fully initialised and so the native mode in it ends up with default values. However, if we get a panel with reasonable EDID, it's probably the case that the panel's preferred mode does actually represent the panel capabilities. This patch handles that case by replacing the native mode with the panel's preferred mode if the resolutions don't match. Systems without a valid internal panel EDID will still use the BIOS native mode. Signed-off-by: Matthew Garrett <mjg(a)redhat.com> --- drivers/gpu/drm/radeon/radeon_connectors.c | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/radeon/radeon_connectors.c b/drivers/gpu/drm/radeon/radeon_connectors.c index 6d6b5f1..3248738 100644 --- a/drivers/gpu/drm/radeon/radeon_connectors.c +++ b/drivers/gpu/drm/radeon/radeon_connectors.c @@ -474,11 +474,19 @@ static void radeon_fixup_lvds_native_mode(struct drm_encoder *encoder, { struct radeon_encoder *radeon_encoder = to_radeon_encoder(encoder); struct drm_display_mode *native_mode = &radeon_encoder->native_mode; + struct drm_display_mode *t, *mode; + + /* If the EDID preferred mode doesn't match the native mode, use it */ + list_for_each_entry_safe(mode, t, &connector->probed_modes, head) { + if (mode->type & DRM_MODE_TYPE_PREFERRED) { + if (mode->hdisplay != native_mode->hdisplay || + mode->vdisplay != native_mode->vdisplay) + memcpy(native_mode, mode, sizeof(*mode)); + } + } /* Try to get native mode details from EDID if necessary */ if (!native_mode->clock) { - struct drm_display_mode *t, *mode; - list_for_each_entry_safe(mode, t, &connector->probed_modes, head) { if (mode->hdisplay == native_mode->hdisplay && mode->vdisplay == native_mode->vdisplay) { @@ -489,6 +497,7 @@ static void radeon_fixup_lvds_native_mode(struct drm_encoder *encoder, } } } + if (!native_mode->clock) { DRM_DEBUG_KMS("No LVDS native mode details, disabling RMX\n"); radeon_encoder->rmx_type = RMX_OFF; -- 1.7.6

2 3

[Bug 36396] New: r600_state_inlines.h: unsupported color format
by bugzilla-daemon＠freedesktop.org 08 Aug '11

08 Aug '11

https://bugs.freedesktop.org/show_bug.cgi?id=36396 Summary: r600_state_inlines.h: unsupported color format Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: mark(a)tvk.rwth-aachen.de after starting the game Dawn of War with wine (git-version), the following messages are printed several times: EE r600_state_inlines.h/r600_translate_colorformat:408 - unsupported color format 12 EE r600_state_inlines.h/r600_translate_colorformat:408 - unsupported color format 12 EE r600_state_inlines.h/r600_translate_colorformat:408 - unsupported color format 95 EE r600_state_inlines.h/r600_translate_colorformat:408 - unsupported color format 12 EE r600_state_inlines.h/r600_translate_colorformat:408 - unsupported color format 96 EE r600_state_inlines.h/r600_translate_colorformat:408 - unsupported color format 12 some textures and all game-objects like units and buildings aren't drawn, I don't know if this is related. Game has platinum status in winedb, so everything should look fine. mesa: git, xf86-video-ati: git, kernel: d-r-t, HD4350 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1

[Bug 39902] R600g Evergreen: GPU lockup after launch of StarCraft II
by bugzilla-daemon＠freedesktop.org 08 Aug '11

08 Aug '11

1 0

[Bug 39897] Graphical glitches in some games on Evergreen
by bugzilla-daemon＠freedesktop.org 08 Aug '11

08 Aug '11

https://bugs.freedesktop.org/show_bug.cgi?id=39897 --- Comment #13 from Sven Arvidsson <sa(a)whiz.se> 2011-08-08 03:38:00 PDT --- (In reply to comment #11) > I have two questions though > - "32 bit games require a 32 bit 3D driver" : how do we check that ? > LIBGL_DEBUG=verbose glxinfo ? > In my case, it opens r600_dri.so from a x86_64 folder. That's because glxinfo is 64-bit. You need to set the environment variable when you launch a 32-bit app, like BEEP. > I tried to find a guide or a FAQ (as it seems a fairly common issue) in vain. > - Is there a "proper" fix ? Do you want us to test something ? to apply a patch > ? We'd be glad to do the "boring" thing (compiling+testing). This is really more of a distro problem. (Personally I see no real reason to bother with 64-bit if you have any interest to run proprietary games and stuff using Wine. Hopefully this will be less of an issue once Debian and Ubuntu makes the transition to proper multi-arch.) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

← Newer
1
...
39
40
41
42
43
44
45
46
47
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel August 2011