Re: Feedback requested on potential bug.
On Thu, Apr 12, 2007 at 07:54:57AM +0200, Michel Dänzer wrote: On Wed, 2007-04-11 at 22:06 -0700, Ray Van Dolson wrote: I am curious if you would consider the machine freezing when the aperture is set at 64MB to be a bug (didn't try any other setting). It probably is, but I think I might have fixed it in current drm git. Can you link me to the commitdiff for this? Would like to point the RH guys to it possibly for inclusion into FC at some point. Ray - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Feedback requested on potential bug.
Can you link me to the commitdiff for this? Would like to point the RH guys to it possibly for inclusion into FC at some point. There were several related fixes but http://gitweb.freedesktop.org/?p=mesa/drm.git;a=commitdiff;h=8ff026723cf170034173052a58c650c8c1f28c0b;hp=125f3ff36796c8d28c29e960247fdd42d4cd877c is the most likely to help with this. If in doubt, you could just try if the current tree works first. Thanks Michael. I backported this patch into my FC6 kernel and reset my aperture size back to 64MB's. Xorg now starts up at this setting _with_ DRI enabled! I get the following in dmesg: [drm] Initialized drm 1.1.0 20060810 ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 17 [drm] Initialized radeon 1.25.0 20060524 on minor 0 agpgart: Found an AGP 2.0 compliant device at :00:00.0. agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode [drm] Setting GART location based on new memory map [drm] Can't use AGP base @0xf800, won't fit [drm] Loading R300 Microcode [drm] writeback test succeeded in 1 usecs Can you tell me in a nutshell the consequences of the won't fit error above? Performance penalty of any sort? Will certain radeon driver features not work as a result perhaps? The error does not (as expected) appear if my aperture is set to 128MB. My glxinfo shows DRI is working and I get a much healthier score of 3400FPS or so with glxgears. Ray - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Feedback requested on potential bug.
Hi all, it was suggested that I post this here. Please let me know if this isn't the appropriate place. :) I'm using an ASUS Radeon 9800XT (ASUS branded ATI 9800 w/ Vivo, etc): http://www.hardocp.com/article.html?art=NTUy I'm running with it on an ASUS A7V333 motherboard and Fedora Core 6. I am trying to use the 'radeon' driver that comes with Xorg. However, X will not even start up -- the system hangs and I have to hard reset typically. I have also tried with the latest version of Ubuntu Feisty Fawn (live CD). I cannot even get into the GUI at all when booting off the CD. I can only assume the 'radeon' driver is being loaded and the same thing occurs as under Fedora. As soon as I disable dri (alias radeon off in modprobe.conf) I can start X without any problem albeit without DRI. Reenable DRI and X hard locks up again. I'm beginning to wonder if this is a symptom specifically related to my ASUS branded ATI card and not your normal ATI 9800XT... I've filed a bug with RH/Fedora here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=230524 And have attached my xorg.conf files and various dumps per the RH developer's requests. Thus far they are puzzled, but perhaps some of you can glean somethign useful from my filing. Any suggestions or thoughts on my issue? Happy to provide whatever information requested or to file a formal bug with you guys. TIA, Ray - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Feedback requested on potential bug.
On Thu, Apr 12, 2007 at 04:45:04AM +0100, Dave Airlie wrote: I'm running with it on an ASUS A7V333 motherboard and Fedora Core 6. I am trying to use the 'radeon' driver that comes with Xorg. However, X will not even start up -- the system hangs and I have to hard reset typically. Do you have any AGP related settings in the BIOS? Dave. Yes, there are several. Any recommendations on which ones I should play with? I have played with a few different values for the aperture size. I can get you a list of all the settings available if needed. Ray - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Feedback requested on potential bug.
Do you have any AGP related settings in the BIOS? Dave. Well, my aperture was set at 64MB (for a 256MB card) so I changed it to 128. Surprised I didn't check this earlier. I can now start Xorg without alias radeon off in modprobe.conf! Is it a bug still that this wouldn't work when the aperture was set to 64MB's? In addition, I'm not quite sure that all is well. glxinfo still displays: direct rendering: No I see the following in dmesg: [drm] Initialized drm 1.1.0 20060810 ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 17 [drm] Initialized radeon 1.25.0 20060524 on minor 0 [drm] Setting GART location based on new memory map [drm] Loading R300 Microcode [drm] writeback test succeeded in 1 usecs And the following as well: [EMAIL PROTECTED] ~]$ egrep -w dri|drm /var/log/Xorg.0.log (II) LoadModule: dri (II) Module dri: vendor=X.Org Foundation (II) Loading sub module drm (II) LoadModule: drm (II) Module drm: vendor=X.Org Foundation drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: node name is /dev/dri/card0 (II) RADEON(0): [dri] Found DRI library version 1.2.0 and kernel module version 1.25.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: node name is /dev/dri/card0 (II) RADEON(0): [drm] DRM interface version 1.3 (II) RADEON(0): [drm] created radeon driver at busid pci::01:00.0 (II) RADEON(0): [drm] added 8192 byte SAREA at 0xf8d34000 (II) RADEON(0): [drm] mapped SAREA 0xf8d34000 to 0xaff85000 (II) RADEON(0): [drm] framebuffer handle = 0xe800 (II) RADEON(0): [drm] added 1 reserved context for kernel (II) RADEON(0): [drm] register handle = 0xd700 (II) RADEON(0): [dri] Visual configs initialized (II) RADEON(0): [drm] installed DRM signal handler (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers (II) RADEON(0): [drm] dma control initialized, using IRQ 17 (II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: node name is /dev/dri/card0 (II) AIGLX: Loaded and initialized /usr/lib/dri/r300_dri.so glxgears runs at a pathetic 700 FPS. Will tinker with it some more. But perhaps in light of my aperture discovery this isn't quite ready to be brought to the dri-devel list. I should retry a lot of the more obvious stuff once again now that the machine at least doesn't lock up. I am curious if you would consider the machine freezing when the aperture is set at 64MB to be a bug (didn't try any other setting). Ray - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Feedback requested on potential bug.
On Thu, Apr 12, 2007 at 06:10:26AM +0100, Dave Airlie wrote: Do you have any AGP related settings in the BIOS? Dave. Yes, there are several. Any recommendations on which ones I should play with? I have played with a few different values for the aperture size. I can get you a list of all the settings available if needed. Turn off anything like fastwrites or side band addressing.. the aperture size 32MB should be fine.. Dave. My current settings in BIOS: Aperture: 128MB (previously was 64 -- wouldn't work at this setting) AGP Capability: 4X AGP Drive Strength: Auto AGP Performance Control: Enabled AGP FastWrite Control: Enabled Video Memory Cache Mode: UC I'll disable Performance Control and Fast Write. Ray - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
