dri-devel December 2010

dri-devel@lists.freedesktop.org

94 participants
405 discussions

[Bug 19002] Radeon rv730 AGP/KMS/DRM kernel lockup
by bugzilla-daemon＠bugzilla.kernel.org 14 Dec '10

14 Dec '10

https://bugzilla.kernel.org/show_bug.cgi?id=19002 --- Comment #24 from Holger Lenz <holger.lenz(a)onlinehome.de> 2010-12-14 21:41:46 --- Created an attachment (id=40192) --> (https://bugzilla.kernel.org/attachment.cgi?id=40192) lspci -vv on the VIA/K8 system -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 19002] Radeon rv730 AGP/KMS/DRM kernel lockup
by bugzilla-daemon＠bugzilla.kernel.org 14 Dec '10

14 Dec '10

https://bugzilla.kernel.org/show_bug.cgi?id=19002 --- Comment #23 from Holger Lenz <holger.lenz(a)onlinehome.de> 2010-12-14 21:40:30 --- > Try adding radeon.no_wb=1 to your kernel command as well. > > Also, some boards set unrealistic latency settings on the AGP bridge the card > is plugged into. Often increasing the latency with setpci will improve > stability. > lspci -vv will show you what it's currently set to. No luck with radeon.no_wb=1, unfortunately. Attached lspci -vv - no idea if the timings are aggressive or not. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 19002] Radeon rv730 AGP/KMS/DRM kernel lockup
by bugzilla-daemon＠bugzilla.kernel.org 14 Dec '10

14 Dec '10

https://bugzilla.kernel.org/show_bug.cgi?id=19002 --- Comment #22 from Alex Deucher <alexdeucher(a)gmail.com> 2010-12-14 21:22:30 --- (In reply to comment #20) > any ideas, how to fix these? Try adding radeon.no_wb=1 to your kernel command as well. Also, some boards set unrealistic latency settings on the AGP bridge the card is plugged into. Often increasing the latency with setpci will improve stability. lspci -vv will show you what it's currently set to. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 19002] Radeon rv730 AGP/KMS/DRM kernel lockup
by bugzilla-daemon＠bugzilla.kernel.org 14 Dec '10

14 Dec '10

https://bugzilla.kernel.org/show_bug.cgi?id=19002 --- Comment #21 from Alex Deucher <alexdeucher(a)gmail.com> 2010-12-14 21:17:59 --- (In reply to comment #19) > > 2) No AGP fast-write here at all. AFAIK it's a chipset errata on AMD 8xxx. It's buggy on all boards. We don't enable it at all with kms. > > 3) 256 MB AGP aperture, half of which is of course reserved for the AGPGART > IOMMU on the AMD 8xxx chipset. The BIOS allows larger (upto 1GB, which happens > to be video memory size as well), but that was a reasonably late addition to > the BIOS (256 was the previous limit), and for whatever reason I couldn't get > it to work in testing, so I've stuck with 256 MB (128 MB of it AGPGART IOMMU), > which /does/ work. > > BTW, /should/ a larger aperture work? Given that half of it's AGGART IOMMU, > should larger == better? I've not tested larger recently, maybe it works now? > Bigger isn't necessarily better, it just means more pages can be mapped into the gart. We default to 512 MB on non-AGP systems. > 4) dmesg says AGP v3 device in 8x mode. Years ago I had problems with 8x and > had to use 4x max, but last I tried, 4x and 8x worked but 1x and 2x were > broken. > AGP v3 devices only support 4x and 8x modes. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 19002] Radeon rv730 AGP/KMS/DRM kernel lockup
by bugzilla-daemon＠bugzilla.kernel.org 14 Dec '10

14 Dec '10

https://bugzilla.kernel.org/show_bug.cgi?id=19002 --- Comment #20 from Holger Lenz <holger.lenz(a)onlinehome.de> 2010-12-14 21:08:06 --- Thanks a lot Ducan, for all the info. You helped me eliminate several variables. AGP still won't work, but I'll just see how far I get with PCI(E) mode I'm now always forcing KMS by using radeon.modeset=1 Looking at the demsg, the following two errors seem to prevent X from loading the r600 module: This (1) [drm] Forcing AGP to PCIE mode [ 17.311865] radeon 0000:01:00.0: PCI: Disallowing DAC for device [ 17.311867] radeon: No suitable DMA available. and this (2) [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 1 pages at 0x00000000 [ 17.485886] radeon 0000:01:00.0: object_init failed for (4096, 0x00000002) [ 17.485889] radeon 0000:01:00.0: (-12) create WB bo failed [ 17.485892] radeon 0000:01:00.0: disabling GPU acceleration [ 17.502518] radeon 0000:01:00.0: f7229e00 unpin not necessary any ideas, how to fix these? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 30488] New: Star Wars - Jedi Kight : Jedi Academy does not render correctly.
by bugzilla-daemon＠freedesktop.org 14 Dec '10

14 Dec '10

https://bugs.freedesktop.org/show_bug.cgi?id=30488 Summary: Star Wars - Jedi Kight : Jedi Academy does not render correctly. Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: oreaus(a)gmail.com Created an attachment (id=39062) --> (https://bugs.freedesktop.org/attachment.cgi?id=39062) Menu screen I installed the game 'Star Wars - Jedi Kight : Jedi Academy' using wine and it runs but does not render correctly. Attached is a screenshot of the menu screen where all buttons are invisible and middle part is not rendering or refreshing there. This is on rv350 using 2.6.36_rc5 on Arch Linux. Can anyone else confirm this problem? -- 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

[Bug 32320] New: vdrift 2010 release cannot start with shaders enabled
by bugzilla-daemon＠freedesktop.org 14 Dec '10

14 Dec '10

https://bugs.freedesktop.org/show_bug.cgi?id=32320 Summary: vdrift 2010 release cannot start with shaders enabled Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: aaalmosss(a)gmail.com the interesting parts of the console log: radeon: Successfully grabbed chipset info from kernel! radeon: DRM version: 2.0.0 ID: 0x4152 GB: 1 Z: 1 radeon: GART size: 253 MB VRAM size: 128 MB radeon: HyperZ: NO INFO: Display change was successful: 1024x768x32 16z fullscreen=0 INFO: Video card information: Vendor: X.Org R300 Project Renderer: Gallium 0.4 on ATI RV350 Version: 2.1 Mesa 7.10-devel Maximum texture size: 2048 Maximum varying floats: 32 Using GLEW 1.5.4 .... INFO: Successfully enabled shaders INFO: Initialized render output: full_scene_depth (FBO) Mesa: User error: GL_INVALID_VALUE in glTexImage2D(internalFormat=GL_RGBA16F) ERROR: OpenGL error "invalid value" during: FBTEX texture storage initialization INFO: Initialized render output: full_scene_color (FBO) INFO: Initialized render output: normal_xy (FBO) INFO: Initialized render output: material_properties (FBO) INFO: Initialized render output: diffuse_albedo (FBO) INFO: Initialized render output: log_luminance (FBO) INFO: Initialized render output: log_luminance_tiny (FBO) ERROR: Framebuffer is not complete: incomplete attachment ERROR: Error initializing FBO: ERROR: 0. NORMAL: RGBA16 vdrift: src/fbobject.cpp:286: void FBOBJECT::Init(GLSTATEMANAGER&, std::vector<FBTEXTURE*, std::allocator<FBTEXTURE*> >, std::ostream&, bool): Assertion `status_ok' failed. SIGABRT detected, releasing the mouse Aborted -- 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 32272] New: tire smoke is solid white in vdrift 2010 release
by bugzilla-daemon＠freedesktop.org 14 Dec '10

14 Dec '10

https://bugs.freedesktop.org/show_bug.cgi?id=32272 Summary: tire smoke is solid white in vdrift 2010 release Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: aaalmosss(a)gmail.com I don't know if it is the game's fault or the gl driver's. It seems they changed the smoke effect, as in the 2009 release it was fine. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 4

radeon: *ERROR* Buffer to small for return answer
by Ortwin Glück 14 Dec '10

14 Dec '10

I am seeing this on a 4670 M96XT RV730 (iMac 11,2) with 2.6.37-rc5 [drm:radeon_process_aux_ch] *ERROR* Buffer to small for return answer 1 16 [drm] Initialized drm 1.1.0 20060810 [drm] radeon defaulting to kernel modesetting. [drm] radeon kernel modesetting enabled. [drm] initializing kernel modesetting (RV730 0x1002:0x9488). [drm] register mmio base: 0xD0420000 [drm] register mmio size: 65536 [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 128bits DDR [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV730 Microcode [drm] ring test succeeded in 1 usecs [drm] radeon: ib pool ready. [drm] ib test succeeded in 0 usecs [drm] Enabling audio support [drm] Radeon Display Connectors [drm] Connector 0: [drm] DisplayPort [drm] HPD1 [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [drm] Encoders: [drm] DFP1: INTERNAL_UNIPHY [drm] Connector 1: [drm] eDP [drm] HPD2 [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [drm] Encoders: [drm] LCD1: INTERNAL_UNIPHY [drm] Connector 2: [drm] VGA [drm] DDC: 0x7f10 0x7f10 0x7f14 0x7f14 0x7f18 0x7f18 0x7f1c 0x7f1c [drm] Encoders: [drm] CRT2: INTERNAL_KLDSCP_DAC2 [drm] Special thermal controller config [drm] radeon: power management initialized [drm:radeon_process_aux_ch] *ERROR* Buffer to small for return answer 1 16 [drm] fb mappable at 0xC0142000 [drm] vram apper at 0xC0000000 [drm] size 3145728 [drm] fb depth is 24 [drm] pitch is 4096 fb0: radeondrmfb frame buffer device drm: registered panic notifier [drm] Initialized radeon 2.7.0 20080528 for 0000:01:00.0 on minor 0

1 0

[Bug 19002] Radeon rv730 AGP/KMS/DRM kernel lockup
by bugzilla-daemon＠bugzilla.kernel.org 14 Dec '10

14 Dec '10

https://bugzilla.kernel.org/show_bug.cgi?id=19002 --- Comment #19 from Duncan <1i5t5.duncan(a)cox.net> 2010-12-14 03:05:58 --- Some additional notes, FWIW. May help compare the two installations, mine now working with either the original reversion or the new patch, his, not. 1) I've been using 100% KMS since the choice was still in staging. Last time I tried radeon.modeset=0 (see comment #9) I had problems and immediately switched back to KMS, which worked. My conclusion then was that UMS was being disabled or at least strongly deprecated, which was fine with me as I prefer KMS, but it seems that was incorrect and it's still available. 2) No AGP fast-write here at all. AFAIK it's a chipset errata on AMD 8xxx. 3) 256 MB AGP aperture, half of which is of course reserved for the AGPGART IOMMU on the AMD 8xxx chipset. The BIOS allows larger (upto 1GB, which happens to be video memory size as well), but that was a reasonably late addition to the BIOS (256 was the previous limit), and for whatever reason I couldn't get it to work in testing, so I've stuck with 256 MB (128 MB of it AGPGART IOMMU), which /does/ work. BTW, /should/ a larger aperture work? Given that half of it's AGGART IOMMU, should larger == better? I've not tested larger recently, maybe it works now? 4) dmesg says AGP v3 device in 8x mode. Years ago I had problems with 8x and had to use 4x max, but last I tried, 4x and 8x worked but 1x and 2x were broken. 5) I've been using the classic r6xx/r7xx driver, not the new gallium stuff, which I've not gotten to work yet. (On Gentoo, I'm naturally compiling my own. At one point it compiled but I wasn't aware then how to switch to it. Later I figured that out, but had to turn off LLVM to get it to compile at all, and I wasn't surprised when that didn't work. So I've never actually had gallium up and running successfully.) 6) I was trying xorg-server 1.9.2.902 (AFAIK, 1.9.3-rc?), but am now back on 1.9.2 stable, as the pre-release throttled DOSBOX performance something terrible. (I only found out and downgraded yesterday, and haven't filed an X bug yet.) 7) Further to comment #0/Description, there was a kde image cache bug in early kde 4.5, fixed with 4.5.4 (maybe 4.5.3). The comic-strip-plasmoid thing was related to that, I believe, and is now fixed. 8) It's a bit late to be mentioning this now but something else that could conceivably be a factor. Apparently on this old hardware, since kernel 2.6.31, ACPI and various hardware sensor addresses conflict, and I have to boot with acpi_enforce_resources=lax or most of my sensors don't work. I have that compiled in as part of my CONFIG_CMDLINE, so tend to forget about it. See kernel bug #13939 . The board was long since past its BIOS update period even back then and I've been unable to find documentation on what sensors drivers might work in place of the ones that broke, so lax enforcement remains my only known option if I want sensors output, which I do. Might that somehow play into this graphics thing or are they entirely unrelated? 9) Further to comment #13. I still can't get over how nice it is to (with the patch applied) have a properly glitch-free OpenGL accelerated X. This is the /first/ time I've had perfect glitch-free graphics since I upgraded from the old r2xx based card. In an improvement since comment #11, kwin now comes up in OpenGL mode without effects disabled (back then I had to manually enable them once up and running) and invert works fine now too. 2.6.37 has actually been very stable all around, without the usual assortment of other bugs in the md/raid system, etc, too. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

← Newer
1
...
26
27
28
29
30
31
32
...
41
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel December 2010