On Mon, 26 Nov 2001, Peter Jeremy wrote:
> Having installed a new kernel and userland from sources about a day
> old, my vidcontrol command now causes a panic:
>
> Fatal trap 12: page fault while in vm86 mode
> fault virtual address = 0xc359b
> ...
> The backtrace shows nothing useful - gdb doe
John Baldwin wrote:
> On 27-Nov-01 Jim Bryant wrote:
>
>>VESA is broked. Remove VESA from your config. Been this way for months.
>>
>>It also will panic once in a VESA mode, such as my favorite and yours,
>>132x60, when switching from vty to vty.
>>
>
> Ouch, this is not good. This means vm8
On 27-Nov-01 Jim Bryant wrote:
> VESA is broked. Remove VESA from your config. Been this way for months.
>
> It also will panic once in a VESA mode, such as my favorite and yours,
> 132x60, when switching from vty to vty.
Ouch, this is not good. This means vm86 is likely broke. Hmm, I wonde
+---[ Jim Bryant ]--
| Andrew Kenneth Milton wrote
|
| > +---[ Peter Jeremy ]--
| > | Having installed a new kernel and userland from sources about a day
| > | old, my vidcontrol command now causes a panic:
| >
| > [snip]
| >
| > | The command I u
Andrew Kenneth Milton wrote
> +---[ Peter Jeremy ]--
> | Having installed a new kernel and userland from sources about a day
> | old, my vidcontrol command now causes a panic:
>
> [snip]
>
> | The command I used was "vidcontrol 132x60" after confirming that
> | this was
VESA is broked. Remove VESA from your config. Been this way for months.
It also will panic once in a VESA mode, such as my favorite and yours, 132x60, when
switching from vty to vty.
Peter Jeremy wrote:
> Having installed a new kernel and userland from sources about a day
> old, my vidcontro
On 2001-Nov-26 18:26:14 +1000, Andrew Kenneth Milton <[EMAIL PROTECTED]> wrote:
>+---[ Peter Jeremy ]--
>| Having installed a new kernel and userland from sources about a day
>| old, my vidcontrol command now causes a panic:
>
>[snip]
>
>| The command I used was "vidcontrol
+---[ Peter Jeremy ]--
| Having installed a new kernel and userland from sources about a day
| old, my vidcontrol command now causes a panic:
[snip]
| The command I used was "vidcontrol 132x60" after confirming that
| this was listed in "vidcontrol -i mode". I have previ
Having installed a new kernel and userland from sources about a day
old, my vidcontrol command now causes a panic:
Fatal trap 12: page fault while in vm86 mode
fault virtual address = 0xc359b
fault code = user read, page not present
instruction pointer = 0xc000:0x359b
stack poi
