On 25 Feb 2003, Eric Esterle wrote: >> Just so you are aware, GATOS drivers, or any drivers for that >> matter that are not supplied by Red Hat as part of Red Hat Linux >> - are totally unsupported by Red Hat. > >I am aware of this. > >> If you're using GATOS drivers, then you must use GATOS DRM. >> Because the kernel.org kernel does not contain the GATOS DRM. > >Yes, I have done this. >> >> Not really. You're not using Red Hat DRM with supported drivers. >> The DRM in Red Hat Linux is not the GATOS DRM, and you wont get >> GATOS to work with it. This is not a Red Hat bug, nor a Red Hat >> DRM problem. GATOS is simply not compatible with the DRM in Red >> Hat Linux, and the GATOS site explicitly states that you require >> to use their DRM modules. >> >I have been using the Gatos ATI.2 drivers and the Gatos DRM kernel. >Everything works fine with the Gatos aside from no gears being displayed >in GLXGEARS. To keep this post somewhat relevant I think I know what I >did incorrectly. In the DRM section of the kernel I set it to NO >instead of Module so when I did insmod radeon.o I'm not sure if it used >it because this section of the kernel was not set to module. Another thing you did wrong, is "insmod radeon". You _never_ _ever_ need to insmod or modprobe agpgart nor any DRM module. The X server takes care of this properly on it's own accord. >> If you can't get GATOS to work, then you're doing something >> wrong, or the GATOS drivers are broken that you're trying to use. >> I suspect the former is the case however as I'm able to run GATOS >> drivers locally, and I know many others who are able to do so as >> well. > >I agree, and I am not saying the Gatos drivers are broken. I am the one >making the mistake(s) most definitely. It must have been my DRM build >drivers not being set to module in the kernel that caused no gears to be >displayed in GLXGEARS. glxinfo will tell you if you're using DRI or not >> Perhaps a future XFree86 release will merge pieces of the GATOS >> code, and end users won't have to jump through hoops like this to >> get things working. > >That would be nice but I wouldn't expect it. Parts of it will occur over time, but it wont happen all at once. >> Just keep in mind that while this is fairly simple to get going, >> it is totally unsupported by Red Hat. > >Let me ask you a question about a stock installation of Redhat 8 >though. Why does this appear in my X log? > >drmOpenDevice: Open failed >drmOpenDevice: Open failed That happens on pretty much all hardware supported by DRI for some reason in the last few releases of XFree86. It is harmless for the most part, but it is a bit annoying to me. I believe someone upstream screwed something up, but it still actually works, just doesn't open the device properly the first time. I plan on investigating that sometime soon, but it hasn't been important since it doesn't actually affect DRI working or not. >My intention with this post was not to try and get Redhat support for >something that Redhat shouldn't support. I only wanted to create a >thread that would help myself and others out. At this point I don't >feel like I have accomplished that. No problem, I just wanted to clarify that your problem was not a Red Hat or Red Hat kernel issue, because you seemed to imply that it might be. Take care, TTYL -- Mike A. Harris ftp://people.redhat.com/mharris OS Systems Engineer - XFree86 maintainer - Red Hat _______________________________________________ xfree86-list mailing list xfree86-list@redhat.com https://listman.redhat.com/mailman/listinfo/xfree86-list IRC: #xfree86 on irc.redhat.com
