Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!ubc-cs!uw-beaver!mit-eddie!snorkelwacker.mit.edu!shelby!portia.stanford.edu!fangchin
From: fangchin@portia.Stanford.EDU (Chin Fang)
Newsgroups: comp.unix.sysv386
Subject: Re: Re: X11R4 problems
Message-ID: <1991Feb23.024659.21076@portia.Stanford.EDU>
Date: 23 Feb 91 02:46:59 GMT
References: <1175@gagme.chi.il.us> <12870011@hpnmdla.HP.COM>
Organization: AIR, Stanford University
Lines: 30

In article <12870011@hpnmdla.HP.COM> darrylo@hpnmdla.HP.COM (Darryl Okahata) writes:
>In comp.unix.sysv386, proto@gagme.chi.il.us (Mike Protofanouis) writes:
>
>> I have now been able to sucessfully build the kernel, but am now
>> getting an X startup error:  
>>
>> Creating TCP socket: Invalid argument
>
>     This is "normal".  Ignore it.
>
>> After that, the X screen comes up but I can't type anything.
>
>     You're running xinit from the console (alt-F1), right?  If you are,
>run it from another virtual console.  If you must run it from the
>console, run xinit and bang on alt-F2, alt-F3, etc. until you can type
>something (if you are running on the console, X chooses to take input
>from *one* of the virtual consoles instead, and you can't type anything
>until you select that virtual console -- ugh).

On my ESIX box, alt-F[1-4] won't work.  The working key combos are either

(1) <alt><SysReq>N to cycle thru all virtual terminals (only one way) or
(2) <alt><SysReq>F[1-4] both ways. 

Haven't figured out why yet.

Chin Fang
Mechanical Engineering Department
Stanford University
fangchin@leland.stanford.edu