On Mon, 13 Jan 2003 14:35:43 -0500 (EST)
John Baldwin <[EMAIL PROTECTED]> wrote:

> 
> According to /usr/share/misc/pci_vendors, that device is not for the Pro 133A
> but for the PM133:
> 
>         0605    VT8605 ProSavage PM133 System Controller
>         ....
>         0691    VT82C691/693A/694X Apollo Pro/133/133A System Controller

I promise you it's an Apollo Pro 133A and it identifies with 0605, not with 0691.
This is the mobo I have: http://www.motherboard.cz/mb/asus/CUV4X.htm

> The patch should make no functional difference since the generic probe
> should work (it should be listed as a "VIA Generic host to PCI bridge").

It doesn't, without adding that line my computer reboots when running OpenGL apps.
I have tried maybe 5 times to recompile the kernel without it, same result every time.

Is there anything I can do to confirm, check why I need this or something? I have 
tried checking
the syslogs after the computer reboots but I never found anything related to it.
I'd prefer not to run too many tests though, since sometimes my drives get corrupted.

I just switched back to CURRENT to check how it would behave when I added these lines. 
When I
load agp.ko now I get this extra output:
on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.AGP_ - 
AE_NOT_FOUND

and I had to set the AGP rate to 0, otherwise the machine will hang randomly (not 
OpenGL related
this time since it will hang even though I haven't run any OpenGL apps).
I have tried not loading agp.ko and using nvidias agp (by enabling in XF86Config), but 
that
yields the same result as agp_via.c without the added ID.


Now this is very strange, I did a search and indeed, the id is 0691. I was unable to 
find the
page that said that it was 0605 =(.
Now I'm positive I have a CUV4X mobo which has a 694X AGP chipset. Do you have any 
hints to how
I can debug this, because it works with id 0605 and it doesn't work without it, which 
does not
make any sense I guess.

//David Holm

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to