> >Sounds like something got broken in vesafb in the meantime.
> Oops, works fine here...
>
> Is vesafb compiled in? The video mode selection code _allways_ happily
> switches to graphics mode if you tell him to do so (even 2.0.x does :-)
^^^^^^^^^
A warning somewhere (lilo ?) would certainly be welcome, but the one who
does things, rules (and both constraints and (lack of) competency prevent
me from doing)
> Without vesafb configured in you'll have a black screen then...
> If vesafb is in: Could you email me the vesafb boot messages?
I'm >really< puzzled. I've redone a whole "make dep && clean && bzImage &&
modules ..." (didn't touch the config) and now the result works. I must be
stupid or(*) have forgotten to type "make clean" the previous time
(remember the original post, how I managed to put that poor SparcIPX into
"I won't boot" coma) ( (*) "or" doesn't mean "xor", naturally).
Anyway, now vesafb works for me, I have another bug report : how long do
you think the penguin will survive without anything to quench its thirst ?
<grin />
-- Cyrille
PS : here's what vesafb says :
vesafb: framebuffer at 0xe7800000, mapped to 0xc6800000, size 2048k
vesafb: mode is 1024x768x16, linelength=2048, pages=0
vesafb: protected mode interface info at c000:7d40
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
------------------------------
Zog Zog
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/