Holy cow, that is fast! And color works too!

On my Beige G3 it reports only 2 MB but I do have the optional 4 MB RAM
upgrade installed to bring it to 6 MB, not that it really matters outside
of X, but just for completeness. This is the onboard Rage IIc+DVD
(according to the chip label) There's a 2" black area above and below the
text but I assume that's font related.

machfb0 at pci0 dev 18 function 0: ATI Technologies 3D Rage I/II (rev.0x9a)
machfb0: 16 MB aperture at 0x82000000, 4 KB registers at 0x00000000
machfb0: 2048 KB SGRAM 62.778 MHz, maximum RAMDAC clock 170 MHz
us  : ff8482f0
inst: ff8d7ec0
node: ff8482f0
machfb0: initial resolution 1024x768 at 8 bpp
wsdisplay0 at machfb0 kbdmux 1: console (default, vt100 emulation), using
wskbd0
wsmux1: connecting to wsdisplay0

The wallstreet is a little more unhappy:

machfb0 at pci0 dev 17 function 0: ATI Technologies 3D Rage LT Pro (rev.
0xdc)
machfb0: 16 MB aperture at 0x82000000, 4 KB registers at 0x00000000
machfb0: 4096 KB SGRAM 30.681 MHz, maximum RAMDAC clock 230 MHz
us  : ff84c2d8
inst: ff8d99c0
node: ff84c2d8
machfb0: initial resolution 1600x1200 at 8 bpp

The external monitor shows the same symptoms as the LCD at 1024x768x8. The
test goes out to the screen, but it won't scroll. So I end up with lines
overwriting lines at the bottom of the screen. top will display but
nothing will scroll or clear from the screen. Typing clear just moves the
prompt to the top of the screen area. There's also like a 2" black space
above and below the screen area but I'm guessing that's a font/res issue.


On Sat, 29 Jan 2005, Michael wrote:

> -----[DTCC GnuPG]-------------------------------------------------[begin]-----
> Hello,
>
> I made a test kernel - get it here:
> http://macallan.homeunix.org:6704/stuff/BSD/
> netbsd_GENERIC_framebuffer.bz2
>
> It has both machfb and voodoofb, so it should work with any Voodoo3 and
> most ATi Mach64 / Rage 3D graphics controllers. Support for ofb isn't
> included, not sure how to force the kernel to try it last.
> The kernel will boot even when it doesn't find a supported graphics
> chip, the console may be functional but things like X won't work.
> Network stuff should be fine though.
> So far both drivers don't try to change resolution or anything like
> that, but they'll try to use acceleration for scrolling and such, the
> difference should be noticable in case it works.
>
> Machfb is completely untested on macppc because I don't have suitable
> hardware, so anything could happen.
>
> voodoofb0 at pci0 dev 14 function 0: 3Dfx Interactive Voodoo3 (rev.
> 0x01)
> initializing engine...vga: 00001344 vidcfg: 00000081
> addr: d4ad2000
> voodoofb0: 32 MB aperture at 0x90000000, 33554432 registers at
> 0x84000000
> fb: d4ad2000
> wsdisplay0 at voodoofb0 kbdmux 1: console (default, vt100 emulation)
> (yeah, it's still full of debugging messages)
>
> good luck
> Michael
> -----[DTCC GnuPG]-------------------------------------------------------------
> gpg: extension `/usr/lib/gnupg/idea' already registered
> gpg: Signature made Sat 29 Jan 2005 08:36:55 PM EST using RSA key ID FC620DA7
> gpg: Good signature from "Michael Lorenz <macallan18@earthlink.net>"
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:          There is no indication that the signature belongs to the owner.
> Primary key fingerprint: 6D32 5005 E75D 2C10 9AC5  4E31 CA67 CE45 FC62 0DA7
> -----[DTCC GnuPG]---------------------------------------------------[end]-----
>

-- 
The nice thing about Windows is - It does not just crash, it displays a
dialog box and lets you press 'OK' first.
						-- Arno Schaefer