Re: OT: fglrx linux 2.6.16.1
This is somewhat off-topic but I figured I'd mention it anyway... Boris Peterbarg wrote: fglrx halts even with glxinfo here for some reason (linux 2.6.15.1, xorg 2.6.9) I've attached the dump with USE_ARB_F_P == 1. Oops, should've been xorg 6.9.0 I discovered the same problem this morning on my Athlon64 box using the 64-bit drivers with xorg 6.8.2. It appears to be something with fglrx and 2.6.15.1... even with the latest fglrx drivers it hangs, and dmesg shows a number of kernel stack traces... but when I switched back to a 2.6.14.4 kernel everything was fine again. - Brian __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: r300 DRI killing X
Small update that might help... taking the setup that works, unloading the drm and radeon modules, loading the newer drm and radeon modules (the versions reported by the radeon are 1.15.0 and 1.16.0, respectively), then restarting X causes the same error message about a corrupted page table. My guess therefore is that the problem I'm seeing is from some change in the DRM code, and not the Mesa drivers or Xorg. - Brian --- [EMAIL PROTECTED] wrote: I've been following the r300 driver development though I've not done much with it lately, but while trying the latest version that was merged into the DRI CVS tree I'm unable to successfully start X. First, the system: it's an Athlon 64 laptop with a 128MB Mobilitiy Radeon 9700 and 2 GB of RAM, running a custom 64-bit Linux with glibc 2.3.5, gcc 3.4.4, and a 2.6.12 kernel with the CKO patchset applied. The last version of the r300 driver before the merge to the drm and Mesa CVS repos works (mostly) fine, though I've not done a lot of testing with it. Now on to the crashing... I've gone back to what appears to be when it was first merged in (doing a cvs up -D 2005-07-21 for Mesa, drm, and xc (Xorg CVS repo)) and get the same error every time if I have the glx module enabled in the xorg.conf. In the terminal (I am sshing into the box since the screen goes black right before it dies and the console doesn't come back) I see: X Window System Version 6.8.99.900 (6.9.0 RC 0) Release Date: 01 August 2005 + cvs X Protocol Version 11, Revision 0, Release 6.8.99.900 Build Operating System: Linux 2.6.12-cko3 x86_64 [ELF] Current Operating System: Linux paradys 2.6.12-cko3 #3 Mon Aug 1 17:37:51 EDT 2005 x86_64 Build Date: 03 August 2005 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Aug 3 19:37:08 2005 (==) Using config file: /etc/X11/xorg.conf (WW) INVALID MEM ALLOCATION b: 0xd800 e: 0xe000 correcting (WW) INVALID IO ALLOCATION b: 0x2000 e: 0x2100 correcting Killed And in dmesg I get: [drm] Initialized drm 1.0.0 20040925 ACPI: PCI Interrupt :01:00.0[A] - GSI 18 (level, low) - IRQ 209 [drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] X: Corrupted page table at address 2aaab5648000 PGD 7d61e067 PUD 7d594067 PMD 7d1e0067 PTE c22f9037 Bad pagetable: 000f [1] CPU 0 Modules linked in: radeon drm snd_via82xx snd_ac97_codec snd_mpu401_uart i2c_viapro i2c_core uhci_hcd yenta_socket rsrc_nonstatic pcmcia_core r8169 amd64_agp agpgart nls_iso8859_1 nls_cp437 vfat fat nls_base rt2500 snd_usb_audio snd_pcm snd_timer snd_page_alloc snd_usb_lib snd_rawmidi snd_hwdep snd joydev evdev Pid: 2075, comm: X Tainted: G M 2.6.12-cko3 RIP: 0033:[2b100470] [2b100470] RSP: 002b:7fb12cb8 EFLAGS: 00013283 RAX: 0080 RBX: 0007 RCX: 2aaab5648000 RDX: 2000 RSI: RDI: 2aaab5648000 RBP: 007696b0 R08: R09: c22f9000 R10: 00400200 R11: 004605f0 R12: 0002 R13: R14: 00769040 R15: 0002 FS: 2b2e7ef0() GS:80449340() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 2aaab5648000 CR3: 7dabc000 CR4: 06e0 Process X (pid: 2075, threadinfo 81007d7c4000, task 81007e0fd7b0) RIP [2b100470] RSP 7fb12cb8 and the last few lines of the Xorg log file (which I've attached as Xorg-crashed.0.log) are: drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: Searching for BusID pci::01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: drmOpenMinor returns 7 drmOpenByBusid: drmGetBusid reports pci::01:00.0 (II) RADEON(0): [drm] DRM interface version 1.2 (II) RADEON(0): [drm] created radeon driver at busid pci::01:00.0 (II) RADEON(0): [drm] added 8192 byte SAREA at 0xc22f9000 Now, as I said, it works fine with the last version of the r300 driver from before the merge (using Mesa, xc, and r300_driver trees last updated I think on 2005-07-15). At the terminal when I start X: X Window System Version 6.8.99.14 Release Date: 03 July 2005 + cvs X Protocol Version 11, Revision 0, Release 6.8.99.14 Build Operating System: Linux 2.6.12-cko3 x86_64 [ELF] Current Operating System: Linux paradys 2.6.12-cko3 #3 Mon Aug 1 17:37:51 EDT 2005 x86_64 Build Date: 03 August 2005 Before reporting
r300 DRI killing X
I've been following the r300 driver development though I've not done much with it lately, but while trying the latest version that was merged into the DRI CVS tree I'm unable to successfully start X. First, the system: it's an Athlon 64 laptop with a 128MB Mobilitiy Radeon 9700 and 2 GB of RAM, running a custom 64-bit Linux with glibc 2.3.5, gcc 3.4.4, and a 2.6.12 kernel with the CKO patchset applied. The last version of the r300 driver before the merge to the drm and Mesa CVS repos works (mostly) fine, though I've not done a lot of testing with it. Now on to the crashing... I've gone back to what appears to be when it was first merged in (doing a cvs up -D 2005-07-21 for Mesa, drm, and xc (Xorg CVS repo)) and get the same error every time if I have the glx module enabled in the xorg.conf. In the terminal (I am sshing into the box since the screen goes black right before it dies and the console doesn't come back) I see: X Window System Version 6.8.99.900 (6.9.0 RC 0) Release Date: 01 August 2005 + cvs X Protocol Version 11, Revision 0, Release 6.8.99.900 Build Operating System: Linux 2.6.12-cko3 x86_64 [ELF] Current Operating System: Linux paradys 2.6.12-cko3 #3 Mon Aug 1 17:37:51 EDT 2005 x86_64 Build Date: 03 August 2005 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Aug 3 19:37:08 2005 (==) Using config file: /etc/X11/xorg.conf (WW) INVALID MEM ALLOCATION b: 0xd800 e: 0xe000 correcting (WW) INVALID IO ALLOCATION b: 0x2000 e: 0x2100 correcting Killed And in dmesg I get: [drm] Initialized drm 1.0.0 20040925 ACPI: PCI Interrupt :01:00.0[A] - GSI 18 (level, low) - IRQ 209 [drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] X: Corrupted page table at address 2aaab5648000 PGD 7d61e067 PUD 7d594067 PMD 7d1e0067 PTE c22f9037 Bad pagetable: 000f [1] CPU 0 Modules linked in: radeon drm snd_via82xx snd_ac97_codec snd_mpu401_uart i2c_viapro i2c_core uhci_hcd yenta_socket rsrc_nonstatic pcmcia_core r8169 amd64_agp agpgart nls_iso8859_1 nls_cp437 vfat fat nls_base rt2500 snd_usb_audio snd_pcm snd_timer snd_page_alloc snd_usb_lib snd_rawmidi snd_hwdep snd joydev evdev Pid: 2075, comm: X Tainted: G M 2.6.12-cko3 RIP: 0033:[2b100470] [2b100470] RSP: 002b:7fb12cb8 EFLAGS: 00013283 RAX: 0080 RBX: 0007 RCX: 2aaab5648000 RDX: 2000 RSI: RDI: 2aaab5648000 RBP: 007696b0 R08: R09: c22f9000 R10: 00400200 R11: 004605f0 R12: 0002 R13: R14: 00769040 R15: 0002 FS: 2b2e7ef0() GS:80449340() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 2aaab5648000 CR3: 7dabc000 CR4: 06e0 Process X (pid: 2075, threadinfo 81007d7c4000, task 81007e0fd7b0) RIP [2b100470] RSP 7fb12cb8 and the last few lines of the Xorg log file (which I've attached as Xorg-crashed.0.log) are: drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: Searching for BusID pci::01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: drmOpenMinor returns 7 drmOpenByBusid: drmGetBusid reports pci::01:00.0 (II) RADEON(0): [drm] DRM interface version 1.2 (II) RADEON(0): [drm] created radeon driver at busid pci::01:00.0 (II) RADEON(0): [drm] added 8192 byte SAREA at 0xc22f9000 Now, as I said, it works fine with the last version of the r300 driver from before the merge (using Mesa, xc, and r300_driver trees last updated I think on 2005-07-15). At the terminal when I start X: X Window System Version 6.8.99.14 Release Date: 03 July 2005 + cvs X Protocol Version 11, Revision 0, Release 6.8.99.14 Build Operating System: Linux 2.6.12-cko3 x86_64 [ELF] Current Operating System: Linux paradys 2.6.12-cko3 #3 Mon Aug 1 17:37:51 EDT 2005 x86_64 Build Date: 03 August 2005 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Aug 3 19:47:01 2005 (==) Using config file: /etc/X11/xorg.conf (WW) INVALID MEM ALLOCATION b: 0xd800 e: 0xe000 correcting (WW) INVALID IO ALLOCATION b: 0x2000 e: 0x2100 correcting
Re: [R300] Radeon 9550 Problems
Thank you for the advice. The problem I had before with the DRM modules (drm.ko and radeon.ko) from the r300 CVS was that drm.ko would load fine but loading radeon.ko was causing my computer to lock up after a kernel panic. I had tried it rebuilding both it and the kernel several times without success. However, last night I went back to a 2.6.10 kernel and was able to get things working; I unpacked the vanilla kernel sources, compiled the kerne and rebooted, then compiled and successfully loaded the right DRM modules. :D glxgears runs at about 200fps without DRI, and 600-700fps with DRI (though the gears appear to turn rather slowly with DRI enabled). I also get 30 to 60 fps running Scorched3D at 800x600 with the options Don't draw water, No multi texture, No combined textures, and No VBO (vertex buffer objects) checked--unchecking any of the last three causes the game to die when starting the first round, otherwise the game is playable. I'll be sure to test out the new DRM code tonight or tomorrow. - Brian --- Vladimir Dergachev [EMAIL PROTECTED] wrote: On Tue, 1 Mar 2005 [EMAIL PROTECTED] wrote: Hi, I'm new to DRI development but am interested in helping with the r300 driver. I am trying to get the driver working with my Radeon 9550 and I have glxinfo reporting that direct rendering is enabled and the OpenGL renderer string is Mesa DRI R300 20040924 AGP 4x x86/MMX+/3DNow!+/SSE NO-TCL, but glxgears exits almost immediately with the last message it prints out being drmRadeonCmdBuffer: -22 (exiting). I am running a 2.6.11-rc5 kernel using the DRM modules that come with it (I can't get the DRM modules from CVS to load with a 2.6.10 kernel), the latest Xorg, Mesa, and r300_driver sources from ^^ You need the right DRM module. I am running 2.6.10 as well and there were no compilation problems. Make sure to cd into linux-core and type make there. best Vladimir Dergachev anonymous CVS as of about 11am today (2005-03-01). Everything has been compiled against glibc 2.3.4 using gcc 3.4.3. I'm not using merged-fb nor is the kernel radeon framebuffer module loaded. The error is identical regardless of whether I have immediate mode or VB mode enabled (I don't think it is making it that far in the driver code before exiting...). I have attached the output from glxgears with LIBGL_DEBU=verbose and RADEON_DEBUG=all. Any ideas, or advice for debugging this problem? - Brian __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel __ Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web http://birthday.yahoo.com/netrospective/ --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
