Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!darwin.sura.net!spool.mu.edu!sol.ctr.columbia.edu!xlink.net!gmd.de!mururoa!veit
From: veit@mururoa.gmd.de (Holger Veit)
Subject: Re: Inappropriate ioctl for keybd
Message-ID: <1993Jul6.092918.1072@gmd.de>
Sender: veit@mururoa (Holger Veit)
Nntp-Posting-Host: mururoa
Organization: GMD - German National Research Center for Computer Science
References: <21a6el$eh4@stimpy.css.itd.umich.edu>
Date: Tue, 6 Jul 1993 09:29:18 GMT
Lines: 36
In article <21a6el$eh4@stimpy.css.itd.umich.edu>, altitude@css.itd.umich.edu (Alex Tang) writes:
|> Hi again, I've been haiving a problem with my keyboard. about half the time
|> that i log on from console, when I first log in, it says:
|> Warning: no access to tty (Inapppropriate ioctl for device).
|> Thus no job control in this shell.
|>
|> I can't do lots of things when this comes on....I can't do full screen editing
|> for one.
|>
|> What does this mean. If i log off, and log back in, i don't get this
|> message, and i get full control back. I don't understand why this is
|> happening? and at such random times.
|>
|> I don't know if this is connected or not, but somethimes I can't get X to work.
|> If i try to start XFree-1.2, it will say
|> Cannot execute KBDFORCEASCII iocl: Inappropriate ioctl for device.
No, this is not related. The "no access to tty" message means that a special
ioctl didn't execute correctly. There might be still a bug in either the tty
driver (there is always one more bug in the tty driver) or in tcsh, which
corrupts certain driver parameters.
The inability to get XFree86-1.2 running does not have to do anything
to do with this, nor has it something to do with the error message of
KBDFORCEASCII. The latter message is erroneously generated by kbd_mode, which
is executed in the startx script at the end, i.e. when the xserver has
already died. The reason for failure is in the xserver area (fontpath, unsupported
board, bugs in xserver, etc.) but this time not in the tty driver of the kernel.
Regarding the KBDFORCEASCII message, at least this is solved in XFree86-1.3 (:-)).
--
Dr. Holger Veit | INTERNET: Holger.Veit@gmd.de
| | / GMD-SET German National Research | Phone: (+49) 2241 14 2448
|__| / Center for Computer Science | Fax: (+49) 2241 14 2342
| | / P.O. Box 13 16 | Had a nightmare yesterday:
| |/ Schloss Birlinghoven | My system started up with
53731 St. Augustin, Germany | ... Booting vmunix.el ...