>From: Bill Sommerfeld <sommerfeld@orchard.east-arlington.ma.us>
>
>I suspect this may a kernel bug, not an XFree86 bug..
>
>I'm running a -current kernel, -current libraries, and 1.2C
>rest-of-userland (in the middle of a build...)
>
>the XF86_SVGA server is failing in a rather odd way: it's coming up,
>changing the display resolution, and then dying with the following
>error:
>
>	Unable to set status of mouse fd (Inappropriate ioctl for device)
>
>ktrace shows the syscall which failed like the following:
>
>  4931 XF86_SVGA 866509884.043019 CALL  ioctl(0x4,TIOCSETAW,0xf7bfdb5c)
>  4931 XF86_SVGA 866509885.585032 PSIG  SIGUSR1 caught handler=0xad554 mask=0x0 code=0x0
>  4931 XF86_SVGA 866509885.585372 RET   ioctl -1 errno 25 Inappropriate ioctl for device
>  4931 XF86_SVGA 866509885.585605 CALL  sigreturn(0xf7bfdaa4)
>  4931 XF86_SVGA 866509885.585839 RET   sigreturn JUSTRETURN
>
>The mouse is a logitech 3-button trackball connected through tty00.
>it worked flawlessly until I had to upgrade from 3.2A to 3.3 because
>the #%^$#& 3.2A X server expired on me.
>
>I'm using pcvt as the console..
>
>Additional data available on request.
>
>Anyone else seen this?

I have used XF86_SVGA 3.2A and 3.3 on two -current systems from around
1.2D up to 1.2G and haven't seen this.

My guess is that your /dev/mouse is either a link to the wrong file,
or is a device special file that doesn't match tty00.

I noticed that the XF86Setup distributed with 3.3 wrote "/dev/mouse"
in my XF86Config file, even though I explicitly selected /dev/tty01.
I didn't care much because I already had a link /dev/mouse ->
/dev/tty01.  But I think it's a bug.

--
entropy -- it's not just a good idea, it's the second law.