Re: nVidia FX Support?

On Thursday 06 May 2004 09:00 am, Kenneth Culver wrote:
> Quoting Hendrik Hasenbein <hhasenbe_at_techfak.uni-bielefeld.de>:
> > Kenneth Culver wrote:
> >> Quoting Daniel O'Connor <doconnor_at_gsoft.com.au>:
> >>> -----BEGIN PGP SIGNED MESSAGE-----
> >>> Hash: SHA1
> >>>
> >>> On Thu, 6 May 2004 05:48, Kenneth Culver wrote:
> >>>> > If it still hangs, or is unstable, you might try forcing the AGP
> >>>> > down to 4x or 2x.  Many motherboards are unstable at 8x.
> >>>>
> >>>> I'm thinking it's because I had the XFree86-Server-Snap port
> >>>> installed... that nvidia driver wasn't designed to work with that
> >>>> server. Also, I have the acpi module loaded, and I've heard of that
> >>>> causing problems. The card works fine in 8x mode in windows, so I
> >>>> don't think that's the problem.
> >>>
> >>> The Windows drivers could have workarounds for broken AGP hardware
> >>> (ie the AGP
> >>> driver itself)
> >>
> >> I don't think the AGP hardware is broken, but BSD can't seem to route
> >> the interrupt correctly for the AGP port. It cause the video card to be
> >> routed to
> >> IRQ 11 in FreeBSD, but in Windows, it is routed to irq 16. They
> >> should be the
> >> same in both OS's, and since it works in windows, I'm assuming it's
> >> FreeBSD that's broken.
> >
> > No they don't need to be reported as the same interrupt. Just look at
> > APIC vs non-APIC. IRQ11 looks like non-APIC, IRQ16 is most likely APIC
> > driven.
> >
> > If you have agp in your kernel, remove that line and preload the
> > nvidia.ko from the bootloader. That way my system works with a 5900XT.
> > (nforce2, no apic, acpi enabled)
> >
> > Hendrik
>
> The thing that bugs me is that I have apic in the kernel, and the card
> is still
> at irq 11. I already tried removing agp from the kernel along with apic,
> but the only thing that shows up on the screen is garbage. (the machine
> doesn't hang though :-P.

Your BIOS sucks and doesn't properly tell us which interrupt to use.  I don't 
know how Windows figures out which IRQ to use.  If I did I'd add that into 
the current code as a workaround to this problem.  So, yes, FreeBSD isn't 
routing the IRQ properly, but it's because the BIOS doesn't tell us where to 
route it. :(

-- 
John Baldwin <jhb_at_FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org