DragonFly bugs List (threaded) for 2004-04
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
Re: New vidcontrol moused error messages
I think we should make one minor change to the code, and that is to
deal with the case where the system boots up on a serial console.
The vidcontrol line should probably be:
vidcontrol ${_mousechar_arg} -m on < /dev/ttyv0
If you test that out and make sure it still works as advertised, I'll
commit it.
-Matt
:Walt,
:
:could you install the attached patch (note: it's a patch to
:/usr/src/etc/rc.d/moused so you have to install this file to /etc/rc.d
:after patching) and tell me if your mouse is behaving normally on _all_
:virtual terminals after rebooting?
:
:The reason for the 11 messages is that /etc/rc.d/moused calls
:'vidcontrol -m' for each virtual terminal it finds in /etc/ttys. This
:works once (for the first terminal) and fails for the rest of the 12
:terminals (syscons returns EINVAL if the SC_MOUSE_ENABLED flag is
:already set). With the old vidcontrol we didn't have an error message
:there so the bug went unnoticed.
:
:The solution seems to be to call 'vidcontrol -m' only once in
:/etc/rc.d/moused. This enables the mouse on all virtual terminals here.
:
:..and it saves a little time during booting...:)
:
:Regards,
:Sascha
:
:--
: esac
:
:! for ttyv in /dev/ttyv* ; do
:! vidcontrol < ${ttyv} ${_mousechar_arg} -m on
:! done
: echo '.'
: }
:
:--- 31,38 ----
: ;;
: esac
:
:! vidcontrol ${_mousechar_arg} -m on
:!
: echo '.'
: }
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]