This seems to solve the problem. Thank you.
How soon before VESA will be stable? I do prefer a 132x60 text-mode console...
Kazutaka YOKOTA wrote:
> Would you please remove the vesa driver from the kernel and
> do not try loading the vesa module either, and see if things work?
>
>
>>Actuall
Would you please remove the vesa driver from the kernel and
do not try loading the vesa module either, and see if things work?
>Actually, I have tried to get the VESA splash thing going, but never can get a
>nything to display... I can try removing that... I
>believe it is still set up this w
Actually, I have tried to get the VESA splash thing going, but never can get anything
to display... I can try removing that... I
believe it is still set up this way...
What are the limitations on image size and color-depth for the boot splash thing?
Kazutaka YOKOTA wrote:
> Do you by any ch
Do you by any chance use a VESA mode in text vtys?
The vesa module in -CURRENT has problems now. If you try to
set the VESA_800x600 mode in syscons, you will likely to
hang your machine. This is a known problem, and is somewhat
related to vm86 and context switching. I am afraid there is
no immed
I am getting this with regularity now.
The one time I was available to see the panic, I forgot to go into the debugger and do
a traceback, but it had something to do with
a mwrite, and had a line concerning [maybe a buffer is?]...
I know this isn't much to go on, but that's what I have. I
