Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!psgrain!news.uoregon.edu!raffles.technet.sg!usenet
From: maverick@po.pacific.net.sg (Maverick Research Inc Pte Ltf)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: MATROX METEOR (standard) for FreeBSD on 586 (PCI)
Date: Tue, 20 Feb 1996 23:31:31 GMT
Organization: Pacific Internet, Singapore
Lines: 29
Message-ID: <4gbtbq$brm@raffles.technet.sg>
NNTP-Posting-Host: dyn88.ppp.pacific.net.sg
X-Newsreader: Forte Free Agent v0.55
Has anyone tested the FreeBSD driver for Matrox Metoer ? I am
experiencing some problems. Perhaps you can share with me the
potential pitfalls one may encounter.
I am using the Matrox Metoer (standard).
I have linked the kernel with meteor driver support.
I constantly get the message "meteor: open failed" whenever I run any
of the example prorgams.
I also noticed that the kernel bootup messages say
"meteor00<Matrox Meteor> rev 0 int a irq 11 on pci:9
meteor_attach: mx:264566400: invalid unit number"
Looking at the source code of meteor.c at the function
meteor_attach() where there is a printf statement I guess the
printf("....mx:%d: Invalid unit number");
should be printf("....mx:%d: Invalid unit number", unit);
OF course this is not relevant to why the function failed.
I have since then not been able to relink the kernel.
Thank you very much for your help,
Regards,
Suresh.