DragonFly BSD
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

To: wa1ter@xxxxxxxxxxxxx
From: Sascha Wildner <saw@xxxxxxxxx>
Date: Mon, 26 Apr 2004 19:35:53 +0200

walt wrote:

This began after today's vidcontrol update:  when starting
moused I get this error message printed eleven times:
vidcontrol: showing the mouse: invalid argument
although the mouse seems to work normally after that.


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...:)


*** /usr/src/etc/rc.d/moused	Tue Jan 27 01:42:45 2004
--- /usr/s/src/etc/rc.d/moused	Mon Apr 26 19:15:27 2004
*** 31,39 ****
! 	for ttyv in /dev/ttyv* ; do
! 		vidcontrol < ${ttyv} ${_mousechar_arg} -m on
! 	done
  	echo '.'
--- 31,38 ----
! 	vidcontrol ${_mousechar_arg} -m on
  	echo '.'

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]