Date: Wed, 29 Oct 2003 22:22:05 -0800 From: andi payn <andi_payn@speedymail.org> To: freebsd-questions@freebsd.org Subject: ATI video questions again Message-ID: <1067494925.36829.1955.camel@verdammt.falcotronic.net>
next in thread | raw e-mail | index | archive | help
I already asked some of this before, so I apologize. If anyone here doesn't know the answers, but does know where I should go to ask, that would be just as helpful. I have a Mach64 video card (a 3D Rage IIc rev 7a), and I can't get Xv or DRI to work under FreeBSD. I'm using the XFree86-Server-4.3.0_11 port under FreeBSD 5.1. With the XFree86 4.3 packages from Mandrake 9.2, Xv and DRI work fine. Looking at my XFree86.0.logs, I've seen three different things that might indicate the problem, but I don't know which it is, or where to go from here. First, after loading ati_drv.o, whhen it tries to initialize the driver, it goes through the R128 and RADEON drivers only--no Rage/Mach64. Maybe this is the problem? Is FreeBSD's XFree86-Server port missing/disabling the ati.2 drivers? (And yet I see the message "For information on using the multimedia capabilities of this adapter, please see http://gatos.sf.net.", which I think came along with the ati.2 driver?) Second, when initializing the driver "atimisc_drv.o", I get the following messages in FreeBSD: > (==) ATI(0): Write-combining range (0xa0000,0x20000) was already clear > (==) ATI(0): Write-combining range (0xc0000,0x40000) was already clear > (II) ATI(0): Primary V_BIOS segment is: 0xc000 > (==) ATI(0): Write-combining range (0x0,0x1000) was already clear I get no such messages under linux. However, when I first upgraded to 2.4.22, I got the following messages (and no Xv or DRI, and X slowed to a crawl, too)--which went away (along with the problems) when I fixed the broken ServerWorks code in the kernel: > (==) ATI(0): Failed to set up write-combining range (0xa0000,0x20000) > (==) ATI(0): Failed to set up write-combining range (0xc0000,0x40000) So, maybe there's a similar problem in FreeBSD causing similar issues? Third, when initializing the vbe sub module, I see this: > (II) ATI(0): VESA VBE DDC supported > (II) ATI(0): VESA VBE DDC Level none > (II) ATI(0): VESA VBE DDC transfer in appr. 2 sec. > (II) ATI(0): VESA VBE DDC read failed > (==) ATI(0): Write-combining range (0x0,0x1000) was already clear > (==) ATI(0): Write-combining range (0xa0000,0x10000) was already clear > (==) ATI(0): Write-combining range (0xfe101000,0x1000) was already clear Something is obviously wrong here. Besides the write-combining stuff appearing again (and again, in sub module "fb"), there's that VBE DDC error (and the fact that all of the results are missing, of course). The equivalent in linux is: > (II) ATI(0): VESA VBE DDC supported > (II) ATI(0): VESA VBE DDC Level 2 > (II) ATI(0): VESA VBE DDC transfer in appr. 2 sec. > (II) ATI(0): VESA VBE DDC read successfully > (II) ATI(0): Manufacturer: OQI Model: 4a32 Serial#: 1097 > ... I have no idea where to go from here (short of tramping through megabytes of XF86 code...). Can anyone help? Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1067494925.36829.1955.camel>