--- Glenn Johnson [EMAIL PROTECTED] wrote:
Thanks for the response!
Try the following in your XF86Config file in the
Device section:
Option NoHal true
That will prevent the server from trying to load the
HAL module.
That does prevent the failure message, but hasn't
changed
Glenn Johnson writes:
On Wed, Mar 12, 2003 at 03:38:02PM -0800, J. Kanowitz wrote:
With 4.3.0, I've not seen the usual reminder about the driver, and
blindly specifying WITH_MATROX_GXX_DRIVER (without bothering to pore
over the build output; see previous comment on 'lazy') doesn't do the
On Thu, 13-Mar-2003 at 13:32:21 +0100, Gary Jennejohn wrote:
Glenn Johnson writes:
On Wed, Mar 12, 2003 at 03:38:02PM -0800, J. Kanowitz wrote:
With 4.3.0, I've not seen the usual reminder about the driver, and
blindly specifying WITH_MATROX_GXX_DRIVER (without bothering to pore
over
Keeping this brief, I'm a lazy sod, and it's fairly
obvious the 4.3.0 integration is in flux.
I've got a G200:
drm0: Matrox G200 (AGP) mem
0xf780-0xf7ff,0xf77fc000-0xf77f,0xf600-0xf6ff
irq 11 at device 0.0 on pci1
On:
FreeBSD mustelid.gateway.2wire.net 5.0-RELEASE FreeBSD
On Wed, Mar 12, 2003 at 03:38:02PM -0800, J. Kanowitz wrote:
Keeping this brief, I'm a lazy sod, and it's fairly obvious the 4.3.0
integration is in flux.
I've got a G200:
drm0: Matrox G200 (AGP) mem
0xf780-0xf7ff,0xf77fc000-0xf77f,0xf600-0xf6ff
irq 11 at device 0.0 on
