On Tuesday 15 February 2005 14:22, Frans Pop wrote:
> Hi Tony,
>
> I've tried your suggestions and the one about using fbset resulted in a
> breakthrough. 'fbset -depth' gave no results, but comparing the output of
> 'fbset -i' from a working kernel and a new one gave me something to try.
>
Okay. It seems that in the working kernel, the default mode, 1152x900, was
taken from the prom (since there is no 1152x900 in the mode database) if you
did not specify any boot mode option.
In the non-working version, without the boot mode option, the default_var
was used (which is only 640x480) or taken from the mode database if you
specified a boot mode. Unfortunately, none of the entries in the mode
database nor the default var has the composite sync set to high, which
causes your display to go out of sync. If I'm going to guess, the 2.6.10
version failed to get the default mode from the prom.
Can you verify if this is the case? Insert a bunch of printk's in and around
this
line "if (node == pcp->prom_node) {" in atyfb_setup_sparc(). For the 2.6.8
kernel, this line is in atyfb_init().
As a workaround, a boot option can be added for csync, hsync and vsync.
Tony
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
