Re: MGA(0): Unable to map BAR 0. Invalid argument (22) / X.Org Server V. 1.5.3, mga_drv V. 1.9.100, 7.1-STABLE
Hiya, re... > > The 1.4.9 version of mga may work. I'd give portdowngrade instructions > > for it, but the anoncvs server isn't answering. > > I did eye that, funny you say so. I found on some X.org repository that > 1.4.9 was considerably 'younger' than 1.9.100. I may (might) have a look at > it tonight depending on when I may get outta here. I did get out late but I could not leave it, as usual, so got the 1.4.9 (Makefile,v 1.7 2009/01/08 16:58:29 and the corresponding distinfo), rebuilt the port and, success... Well, mostly. I had to DefaultDepth 16 in the Screen to really get her up (errors otherwise, [1]). The other option probably is to go w/o DRI, and I really may consider that since it looks kinda crappy still -- but not today anymore. At least, we're back to xorg.conf, and also there still is the option with the junk box... :) So thanks for the hint, and All the best regards, Peter. --- [1] Errors remain at 24 bpp depth. (EE) MGA(0): Static buffer allocation failed, not initializing the DRI (EE) MGA(0): Need at least 9216 kB video memory at this resolution, bit depth -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: MGA(0): Unable to map BAR 0. Invalid argument (22) / X.Org Server V. 1.5.3, mga_drv V. 1.9.100, 7.1-STABLE
Hi Warren, > The last time I saw that error was on a -CURRENT test system several > months ago. That system is updating now to the latest -CURRENT. Time > will not be available for at least the next few days to try 7.1, but > I'll see what I can do. I know that feeling, so thanks for offering. Please take it easy :) > The 1.4.9 version of mga may work. I'd give portdowngrade instructions > for it, but the anoncvs server isn't answering. I did eye that, funny you say so. I found on some X.org repository that 1.4.9 was considerably 'younger' than 1.9.100. I may (might) have a look at it tonight depending on when I may get outta here. > If you have the option of replacing the Matrox card, better-supported > Radeons are available in AGP, PCI, and PCIE versions. Oh, I had even less success with a radeon in an IBM box but that's admittedly before 7.4 and probably another story. I'll have another dig into my junk box but so far I only got PCI out of it (and the G200 has AGP, dunno if that makes *the* difference though ;-)). Alright, then, Thanks a lot, and All the best, Peter. -- Peter Cornelius - Karlsruhe DE Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: MGA(0): Unable to map BAR 0. Invalid argument (22) / X.Org Server V. 1.5.3, mga_drv V. 1.9.100, 7.1-STABLE
On Sun, 15 Mar 2009, Peter Cornelius wrote: I have an odd Xorg error with a Matrox G200 card here. I have googled for it but only found dual-head installations, plus comments that it allegedly is fixed with the new FreeBSD Xorg 1.5.3 ports. The last time I saw that error was on a -CURRENT test system several months ago. That system is updating now to the latest -CURRENT. Time will not be available for at least the next few days to try 7.1, but I'll see what I can do. The 1.4.9 version of mga may work. I'd give portdowngrade instructions for it, but the anoncvs server isn't answering. If you have the option of replacing the Matrox card, better-supported Radeons are available in AGP, PCI, and PCIE versions. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
