Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Jan 2000 15:32:19 +0200
From:      Maxim Sobolev <sobomax@altavista.net>
To:        Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Cc:        current@freebsd.org
Subject:   Re: VESA modes broken in syscons driver
Message-ID:  <388C5463.C41DB792@altavista.net>
References:  <388C47D4.50FD2100@altavista.net> <200001241303.WAA06474@zodiac.mech.utsunomiya-u.ac.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
Kazutaka YOKOTA wrote:

> >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
> [Nice patch omitted]

Yes, it solved my problem Thanks!

-Maxim





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?388C5463.C41DB792>