>It seems that recent kernels have problems initialising syscons in VESA pixel
>modes. Particularly "vidcontrol VESA_800x600" (actually "vidcontrol
>VESA_800x600 < /dev/ttyv1" to see what's going on ttyv0) command make my kerne
>l
>panicing with the following output:
[...]
>Looking into nm /kernel output I figured that 0xc01baee9 pointer is within
>sc_mouse_move procedure, however I doesn't use moused. Moreover, disabling
>mouse support in syscons (SC_NO_SYSMOUSE) seems like a temporary workaround to
>this bug.
Thank you for the report. Apply the following patch to
/sys/dev/syscons/scmouse.c and see if it fixes the problem.
Kazu
Index: scmouse.c
===================================================================
RCS file: /src/CVS/src/sys/dev/syscons/scmouse.c,v
retrieving revision 1.10
diff -u -r1.10 scmouse.c
--- scmouse.c 2000/01/20 13:21:45 1.10
+++ scmouse.c 2000/01/24 12:56:02
@@ -124,8 +124,11 @@
s = spltty();
scp->mouse_xpos = x;
scp->mouse_ypos = y;
- scp->mouse_pos = scp->mouse_oldpos =
- (y/scp->font_size - scp->yoff)*scp->xsize + x/8 - scp->xoff;
+ if (ISGRAPHSC(scp))
+ scp->mouse_pos = scp->mouse_oldpos = 0;
+ else
+ scp->mouse_pos = scp->mouse_oldpos =
+ (y/scp->font_size - scp->yoff)*scp->xsize + x/8 - scp->xoff;
splx(s);
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
