Re: 2.1.107 frame buffer _badly_ broken

Gerd Knorr (kraxel@goldbach.isdn.cs.tu-berlin.de)
Sun, 28 Jun 1998 18:29:44 +0200


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:

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)
Console: colour frame buffer device 80x30
[ ... ]
hda: QUANTUM FIREBALL_TM3840A, 3681MB w/76kB Cache, CHS=935/128/63
Partition check:
hda:<0>Kernel panic: Free list corrupted

Gerd

-- 
Gerd Knorr <kraxel@cs.tu-berlin.de>

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