Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Apr 2001 19:33:06 +0200 (CEST)
From:      Salvo Bartolotta <bartequi@neomedia.it>
To:        Stijn Hoop <stijn@win.tue.nl>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: AGP module ?
Message-ID:  <987528786.3adc7e52a6e8d@webmail.neomedia.it>
In-Reply-To: <20010417085324.C72128@pcwin002.win.tue.nl>
References:  <987448873.3adb46297fd9a@webmail.neomedia.it> <20010417085324.C72128@pcwin002.win.tue.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
Scrive Stijn Hoop <stijn@win.tue.nl>:

> On Mon, Apr 16, 2001 at 09:21:13PM +0200, Salvo Bartolotta wrote:
> > > You need to do this:
> > 
> > > # cd /usr/ports/x11/XFree86-4    (1)
> > > # make WITH_MATROX_GXX_DRIVER=yes install
> > > # kldload agp
> > > # kldload mga




<snip> 




> > 1) Under -CURRENT, DRI no longer works. The modules are not built at
> >  all. 
> 
> That is so since april 10th. Search freebsd-cvs for the details.




Hmm, a -CURRENT slice of mine (Yup, I'm multibooting FreeBSD OSes, inter alia) -- 
sources as of Mar 28, 2001 -- doesn't build DRI related modules. 

Never mind. -CURRENT has much more serious stuff boiling :-)   



 
> > 2) Under FreeBSD-4.3RC, sources as of April 12 (approximately)
> midnight,
> > kldloading agp and then mga makes the kernel complain about the
> loading order
> > (which is actually correct); subsequently launching KDE2 just causes
> the
> > system to reboot.
> 
> Hmm, strange - I've device agp in my kernel, and I can kldload mga just
> fine
> after I've booted (I haven't tried unloading yet). 




Exactly.

If (and only if) I load agp **at boot time** (ie by editing /boot/loader.conf), I can 
subsequently load/unload mga seamlessly. Needless to say, in this case, the related 
console messages are much like the ones displayed when agp and mga are **both** 
loaded at boot time (cf my previous message).



If I kldload agp and *subsequently* mga, however, the system complains about the 
module loading order. But the order IS correct. In this case, trying to launch KDE2 just 
results in a reboot.

In this situation (kldload agp, then mga), if I try kldunloading drm (a module loaded in 
turn by mga), I get a panic. Ok, that's just to complete the picture; it is probably not 
exactly sound to do that :-)



I don't know whether all this is expexted behavio(u)r.

-- Salvo

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?987528786.3adc7e52a6e8d>