Re: Status of X600 (5B62) support inquiry; bug 5413
On 03/15/2006 04:01:30 AM, Mike Mestnik wrote: --- Pawel Salek [EMAIL PROTECTED] wrote: [snip] Was working fine for me, until trying to use a newer snapshot. I still need to patch drm_pciids.txt and copy over the /scripts dir before ./install.sh 1. you do not need to copy over /scripts - modify drm_pciids.h directly instead: The makefiles won't try to rebuild it then. Of course, the drm_pciids.txt should be eventually modified in CVS so that no manual modification is required. 2. I confirm that something got broken between 20060306 and 20060308. With any recent snapshot like 20060313, I get: $ glxgears *WARN_ONCE* File r300_ioctl.c function r300Clear line 555 CB_DPATH has been enabled. Please let me know if this introduces new instabilities. *** drmRadeonCmdBuffer: -22 (exiting) and following stuff in dmesg: [drm] Initialized radeon 1.24.0 20060225 on minor 0: [drm] Setting GART location based on new memory map [drm] Loading R300 Microcode [drm] writeback test succeeded in 1 usecs [drm] Setting GART location based on new memory map [drm] Loading R300 Microcode [drm] writeback test succeeded in 1 usecs [drm:r300_emit_3d_load_vbpntr] *ERROR* Offset failed range check (k=0 i=2) while processing 3D_LOAD_VBPNTR packet. [drm:r300_emit_packet3] *ERROR* r300_emit_raw_packet3 failed [drm:r300_do_cp_cmdbuf] *ERROR* r300_emit_packet3 failed Pawel --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Status of X600 (5B62) support inquiry; bug 5413
--- Pawel Salek [EMAIL PROTECTED] wrote: Hi, (Q1) Can anybody summarize shortly what's the status of X600 (PCIID: 5B62, PCIE RV370 type card) support? I see its PCIID is still absent in shared-core/drm_pciids.txt in spite of few success reports: http://sourceforge.net/mailarchive/message.php?msg_id=14645441 (BSD) http://sourceforge.net/mailarchive/message.php?msg_id=14281693 (Linux) The latter message is related to https://bugs.freedesktop.org/show_bug.cgi?id=5413 - I am not sure whether the patch 4547 attached to this report (Q2) should be considered a cleanup or vital for the X600 support? Is it believed that this patch should make X600 work with linux? For what is worth, I tried just appending the id to shared-core/drm_pciids.txt and compiling it on the bleeding edge FC5t3 (after disabling module signing and replacing the kernel drm code by the one available in CVS freedesktop.org), and all I got was few drm messages: [drm] Initialized drm 1.0.1 20051102 [drm] Initialized radeon 1.23.0 20060225 on minor 0: [drm] Setting GART location based on old memory map [drm] Loading R300 Microcode [drm] writeback test succeeded in 1 usecs and a hang (the log messages were saved thanks to remote logging). Can anybody, please, answer Q1 and Q2, and comment on the hang? I would try the binary snapshots to make sure I build drm right but the snapshots obviously do not support this PCIID. Was working fine for me, until trying to use a newer snapshot. I still need to patch drm_pciids.txt and copy over the /scripts dir before ./install.sh Pawel --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel __ 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 xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Status of X600 (5B62) support inquiry; bug 5413
For Q1, the status is that it should work, but apparently it locks up for some unknown reason for some people. There was a significant fix for potential lockup problems in the radeon ddx driver in xorg modular cvs, which may or not help you. You should try the snapshots, you can try patching the drm that comes with them or use your own, there is not much you can do to build it wrong. Which gets us to Q2, that patch 4745 is needed for drm/dri (and dma ddx) support of new radeons (it is nothing more than new ids, all the cleanup was commited), but it's not in cvs because it sometimes causes lockups (even though the lockups aren't exactly caused by drm, but xorg ddx if it uses the drm module). (Note though that the ids of new radeons already present in drm are just as likely to cause lockups as those which aren't.) There are more fixes comming into the DDX everyday or so too :) So if it doesn't work, you may want to lurk at the CVS commit list and retry regulary. Ben. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
