Subject: Re: wsfb and WSDISPLAYIO_GINFO and Inappropriate ioctl for device
To: Jeremy C. Reed <reed@reedmedia.net>
From: Michael Lorenz <macallan@netbsd.org>
List: tech-x11
Date: 05/26/2006 02:25:11
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
> I am trying to get modular X.org's wsfb to work on my i386 laptop.
uh-oh...
> Note: I have not yet tried the NetBSD version with the split out
> hardware
> cursor support (wsfb_cursor.c), but the code in use for this error
> appears
> to be the same.
Unrelated. It will fall back to a software cursor if
ioctl(WSDISPLAYIO_SCURSOR) fails.
> ktrace shows:
>
> 1363 1 Xorg NAMI "/dev/ttyE0"
> 1363 1 Xorg RET open 8
> 1363 1 Xorg CALL ioctl(8,_IOR('W',0x41,0x10),0x81d1004)
> 1363 1 Xorg RET ioctl -1 errno 25 Inappropriate ioctl for
> device
>
> X log shows:
>
> (II) wsfb: driver for wsdisplay framebuffer: wsfb
> (II) Primary Device is: PCI 01:00:0
> (II) wsfb(0): using default device
> (II) Running in FRAMEBUFFER Mode
> (EE) wsfb(0): ioctl WSDISPLAY_GINFO: Inappropriate ioctl for device
> (II) UnloadModule: "wsfb"
>
> And dmesg has:
>
> vga1 at pci1 dev 0 function 0: VIA Technologies VT8623 (Apollo CLE266)
> VGA
> Controller (rev. 0x03)
> wsdisplay0 at vga1 kbdmux 1: console (80x25, vt100 emulation), using
> wskbd0
> wsmux1: connecting to wsdisplay0
> Maybe /dev/ttyE0 is wrong?
no.
Your vga is running in text mode, wsfb needs something in graphics mode.
have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iQEVAwUBRHafSMpnzkX8Yg2nAQKGIwgAhlAUllQRWNlvLCL9L09sh7YCSLSciLwA
n1jLUbyWXBzIsbMUs3ArfkQzs6j0VNGQIbEky5cUycE1+enZg7SDfFebiYqKF6dq
NjA+yaquOSttJKM7FqZS3pHAILmMA2IOsTiveGS+QyNXyq/RMb81zeBBFb8TE/bc
Zyo6lwkkEya/Clh1cJobsIE/aswTOP/WvCzvmS+OxGqCk7rsYxux1y1+IrNYuH50
45sOdDrbKRO0jUFACihvUaY5qDWfjcJJjGLUd+7E3Xc4B7+JWJZR0hW8xZUAL+4h
n6gFyp3EMgB28Rl8TCJX3YR1JQvQJdK7YaGfO8myP0smlkRH48i7zg==
=zw+N
-----END PGP SIGNATURE-----