Re: 2.1.107 frame buffer _badly_ broken

Geert Uytterhoeven (Geert.Uytterhoeven@cs.kuleuven.ac.be)
Sun, 28 Jun 1998 19:46:06 +0200 (MET DST)

On Sun, 28 Jun 1998, Gerd Knorr wrote:
> In lists.linux.kernel you write:
> >> Same problem here, i have a S3 Trio64v2dx....
> >> Compiled without framebuffer works but setfont is broken and no scrollback
> >> buffer...
>
> >Does it work with frame buffer support and vgafb instead of vesafb? Vgafb is a
> >text-only frame buffer device and should work.
>
> 2.1.107 does'nt. 10-day old vger checkout does. Looks like a memory
> management problem, serial console says:

Yes, the problem is that the memory subsystem is initialized too late in Linus'
tree... See my patch a few hours ago.

But I just realized that vesafb also uses ioremap(), so it won't work in
2.1.107 neither :-(

> Linux version 2.1.107 (kraxel@bogomips) (gcc version 2.7.2.1) #2 Sun Jun 28 17:55:25 MEST 1998
> kmem_alloc: NULL ptr (name=unknown)
> fb0: VGA frame buffer device, using 32K of video memory
> kmem_alloc: NULL ptr (name=unknown)

These NULL ptrs are harmless.

Greetings,

Geert

--
Geert Uytterhoeven                     Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP}  http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu