S3 Savage framebuffer

raypen · 04-04-2006, 12:19 PM

Don't quite recall whether or not 2.4.31 contains support
for S3 framebuffer, but noticed that 2.6.13 does so I
thought I'd give it a try.

Works, but doesn't give me the resolution I want. Using the
vesafb with a 'vga=773' in lilo.conf gives me the 1024x768
that I normally use. However, this only seems to work for
the vesa frame buffer. S3 seems to go off on its own:

Code:

kernel: savagefb: mapped io at ce880000
kernel: savagefb: probed videoram:  32768k
kernel: savagefb: Detected current MCLK value of 14318 kHz
kernel: savagefb: mapped framebuffer at ce980000, pbase == d0000000
kernel: savagefb v0.4.0_2.6: 32640kB VRAM, using 1600x1200, 93.755kHz, 75Hz
kernel: fb: S3 ProSavage8 frame buffer device

Anyone know how to setup the resolution properly?

Alien_Hominid · 04-04-2006, 12:47 PM

Don't know about Savage but I recall that Nvidia framebuffer support also had some glitches (for example, penguin logos were not working, others were having black screens after boots) and I was advised to better stay with VESA.

cwwilson721 · 04-04-2006, 03:40 PM

Check out my DRI post in my sig...Has a link for Savage in there

raypen · 04-04-2006, 04:01 PM

I don't know how DRI would affect the framebuffer since it is usually
only used under X Windows.

However, after slogging around a bit, I got a hint:

in lilo.conf add:

Code:

append = "video=savagefb:1024x768-8@75"

This works and, apparently, works with Matrox fb and some others.

Just another little tidbit:

You must compile vesafb into the kernel also otherwise the
kernel compile will abort with a '[vmlinux] Error 1'.

The savagefb overrides the vesafb upon boot even though vesafb
is setup on /dev/fb1.

Code:

messages:
kernel: savagefb: mapped io at ce880000
kernel: savagefb: probed videoram:  32768k
kernel: savagefb: Detected current MCLK value of 14318 kHz
kernel: savagefb: mapped framebuffer at ce980000, pbase == d0000000
kernel: savagefb v0.4.0_2.6: 32640kB VRAM, using 1024x768, 60.062kHz, 75Hz
kernel: fb: S3 ProSavage8 frame buffer device
kernel: vesafb: framebuffer at 0xd0000000, mapped to 0xd0a00000, using 1536k, total 31680k
kernel: vesafb: mode is 1024x768x8, linelength=1024, pages=40
kernel: vesafb: protected mode interface info at c000:7fcf
kernel: vesafb: scrolling: redraw
kernel: vesafb: Pseudocolor: size=6:6:6:6, shift=0:0:0:0
kernel: fb1: VESA VGA frame buffer device

syslog:
kernel:       Display is GTF capable
kernel: Console: switching to colour frame buffer device 128x48
kernel: vesafb: cannot reserve video memory at 0xd0000000

cwwilson721 · 04-04-2006, 04:06 PM

Cool. Will add to the post.

The DRI is just accelerated video, but I had a link in there about S3/Savage. Wasn't sure if it was applicable.