From owner-freebsd-current@FreeBSD.ORG Mon Feb 17 10:09:34 2014 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CE490B1A; Mon, 17 Feb 2014 10:09:34 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8CD231BBA; Mon, 17 Feb 2014 10:09:33 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA27704; Mon, 17 Feb 2014 12:09:30 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1WFL8k-000BEh-IY; Mon, 17 Feb 2014 12:09:30 +0200 Message-ID: <5301DF89.5030707@FreeBSD.org> Date: Mon, 17 Feb 2014 12:08:09 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: FreeBSD Current , Aleksandr Rybalko Subject: vt(9): couple of small issues X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 7bit Cc: freebsd-x11@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Feb 2014 10:09:34 -0000 I used to have mousechar_start="3" in my r.conf. To be honest I can not even recall why. But this worked fine with syscons without any glitches. With vt I get the following during boot up: vidcontrol: setting mouse character: Inappropriate ioctl for device And mouse cursor is never drawn, apparently vidcontrol -m on -M just fails. Looks like with syscons MOUSE_MOUSECHAR ioctl is handled by a terminal device and consolectl device while with vt it is handled only by sysmouse device. Another issue is that I see the following messages appearing during boot and from time to time afterwards in the system log: kernel: sysmouse: unknown ioctl: t:40007413 kernel: sysmouse: unknown ioctl: t:80007410 The ioctls seem to be TIOCFLUSH and TIOCGETA, so I am not sure why sysmouse gets involved. Maybe the same issue exists with syscons's sysmouse as well, but it is just silent about it. Seems like ioctls are called by X server. For example: sysmouse_ioctl:entry kernel`devfs_ioctl_f+0x11c kernel`kern_ioctl+0x1db kernel`sys_ioctl+0x142 kernel`amd64_syscall+0x3c9 kernel`0xffffffff8080e6db libc.so.7`ioctl+0xa Xorg`xf86OpenSerial+0x221 mouse_drv.so`MouseProc+0x2f3 Xorg`EnableDevice+0x214 Xorg`xf86Wakeup+0x57b Xorg`WakeupHandler+0x42 Xorg`WaitForSomething+0x317 Xorg`Dispatch+0x92 Xorg`main+0x475 Xorg`_start+0x14f sysmouse_ioctl:entry kernel`devfs_ioctl_f+0x11c kernel`kern_ioctl+0x1db kernel`sys_ioctl+0x142 kernel`amd64_syscall+0x3c9 kernel`0xffffffff8080e6db libc.so.7`ioctl+0xa Xorg`xf86FlushInput+0x21 mouse_drv.so`MouseProc+0x376 Xorg`EnableDevice+0x214 Xorg`xf86Wakeup+0x57b Xorg`WakeupHandler+0x42 Xorg`WaitForSomething+0x317 Xorg`Dispatch+0x92 Xorg`main+0x475 Xorg`_start+0x14f ld-elf.so.1`0x8007d5000 -- Andriy Gapon