[ltp] T20/Debian/savagefb: Only top part of display is visible

Sun, 24 Feb 2008 10:16:49 -0600

This is a multi-part message in MIME format.
--------------080306060607090404010304
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Part of original post, with reply:

> >  EndSection
> >
> >  Here is some savagefb-related output from dmesg:
> >
> >  savagefb: mapped io at d0b80000
> >  savagefb: probed videoram:  8192k
> >  savagefb: Detected current MCLK value of 83045 kHz
> >  savagefb: 1024x768 TFT LCD panel detected and active
> >  savagefb: Limiting video mode to 1024x768
> >  savagefb: mapped framebuffer at d0c80000, pbase == f0000000
> >  savagefb v0.4.0_2.6: 8064kB VRAM, using 800x600, 37.878kHz, 60Hz
> >  Console: switching to colour frame buffer device 100x37
> >  fb: S3 Savage/IX-MV frame buffer device
> >
> >  Well, can anyone help me out here? Thanks in advance.
>   

Generally don't mix savagefb and the X savage driver.  they don't
really work together properly.

Alex

OK, but to me it looks otherwise from the ThinkWiki: http://www.thinkwiki.org/wiki/S3_Savage_IX8
In any case, since I'm seeing this problem before I'm even starting xdm, I think it's probably the savagefb that is causing
the problems. As I said, I had this problem in the past, resolved it, but now can't remember what I did. I think I just set 
a kernel parameter to not use the savagefb, but I haven't found any reference to such a thing (other than the "nofb", which 
seems to be ignored). I've seen things that say you can remove it from the kernel, but I'm trying to go from easy to hard, so I'm trying to find a simpler fix if can.

Thanks.

--------------080306060607090404010304
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<pre wrap="">Part of original post, with reply:

</pre>
<blockquote type="cite">
 <pre wrap="">&gt; EndSection
&gt;
&gt; Here is some savagefb-related output from dmesg:
&gt;
&gt; savagefb: mapped io at d0b80000
&gt; savagefb: probed videoram: 8192k
&gt; savagefb: Detected current MCLK value of 83045 kHz
&gt; savagefb: 1024x768 TFT LCD panel detected and active
&gt; savagefb: Limiting video mode to 1024x768
&gt; savagefb: mapped framebuffer at d0c80000, pbase == f0000000
&gt; savagefb v0.4.0_2.6: 8064kB VRAM, using 800x600, 37.878kHz, 60Hz
&gt; Console: switching to colour frame buffer device 100x37
&gt; fb: S3 Savage/IX-MV frame buffer device
&gt;
&gt; Well, can anyone help me out here? Thanks in advance.
 </pre>
</blockquote>
<pre wrap="">
Generally don't mix savagefb and the X savage driver. they don't
really work together properly.

Alex

OK, but to me it looks otherwise from the ThinkWiki: <a class="moz-txt-link-freetext" href="http://www.thinkwiki.org/wiki/S3_Savage_IX8">http://www.thinkwiki.org/wiki/S3_Savage_IX8</a>
In any case, since I'm seeing this problem before I'm even starting xdm, I think it's probably the savagefb that is causing
the problems. As I said, I had this problem in the past, resolved it, but now can't remember what I did. I think I just set 
a kernel parameter to not use the savagefb, but I haven't found any reference to such a thing (other than the "nofb", which 
seems to be ignored). I've seen things that say you can remove it from the kernel, but I'm trying to go from easy to hard, so I'm trying to find a simpler fix if can.

Thanks.

</pre>
</body>
</html>

--------------080306060607090404010304--