proto@gagme.chi.il.us (Mike Protofanouis) (02/19/91)
From article <1173@gagme.chi.il.us>, by proto@gagme.chi.il.us: > I am having a few problems installing Roell's X11R4 1.1 on an ESIX system. > > ERROR: No such device 'sp' in mdevice > FATAL ERROR: Errors encountered. Configuration terminated. > Ok, I discovered that installing the Remote File Sharing Disk takes care of the above problem. I have now been able to sucessfully build the kernel, but am now getting an X startup error: Creating TCP socket: Invalid argument After that, the X screen comes up but I can't type anything. Any info/help would be appreciated. Thanks.
fangchin@elaine44.Stanford.EDU (Chin Fang) (02/22/91)
In article <1175@gagme.chi.il.us> 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 > >After that, the X screen comes up but I can't type anything. > Please do the following (assuming you use C shell): xinit 2> ~/errlog to capature all errors emitted by xinit. ls -l /usr/bin/X11/X /usr/bin/X11/X386 >> ~/errlog ls -ld /usr/lib/X11/fonts >> ~/errlog ls -ld /dev/X >> ~/errlog displaypkg >> ~/errlog Do a ls -l in /usr/bin/X11 and /usr/lib/X11/fonts/[misc,75dpi,100dip] and take a look of these file permissions, are they owned by root? grouped by other? By the way, you don't need to have the Remote File Sharing Package installed to use X386 1.1. But you will always get three *error* messages (no harm however). Finally, please DON'T use Thomas' install.sh for ESIX without checking/ editing it first. There are some small difference between ISC for which the script was written and ESIX. A very quick simple heck can fix it. Please post and I will respond. (I went thru all your problems already!) Regards, Chin Fang Mechanical Engineering Department Stanford University fangchin@leland.stanford.edu
protofan@motcid.UUCP (Mike S. Protofanousis) (02/23/91)
From article <1991Feb21.183435.5623@portia.Stanford.EDU>, by fangchin@elaine44.Stanford.EDU (Chin Fang): > > By the way, you don't need to have the Remote File Sharing Package installed > to use X386 1.1. But you will always get three *error* messages (no harm > however). > I have now gotten X386 1.1 to work on my ESIX system. The problem was that I was trying to run xinit from the console. When I switched to a virtual terminal, xinit worked just fine. Well, since I did use install.sh to install everything, I ended up installing the RFS package. I don't plan on using it, so is it safe to do a sysadm rmpkg? I still only get 1 error message: the "Creating TCP socket: invalid argument" What other error messages is anyone getting with ESIX? Finally, I would like to thank all the people who made it possible for me to get a working version of X (esp. Thomas Roell). -- Mike Protofanousis msp@pronet.chi.il.us uunet!motcid!protofan
darrylo@hpnmdla.HP.COM (Darryl Okahata) (02/23/91)
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). -- Darryl Okahata UUCP: {hplabs!, hpcea!, hpfcla!} hpnmd!darrylo Internet: darrylo%hpnmd@relay.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion or policy of Hewlett-Packard or of the little green men that have been following him all day.
fangchin@portia.Stanford.EDU (Chin Fang) (02/23/91)
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
darrylo@hpnmdla.HP.COM (Darryl Okahata) (02/26/91)
Here is a document that describes how to get Herr Roell's X11R4
package running with Esix. I originally sent it out to the Esix-user's
mailing list, but I never posted it here.
-- Darryl Okahata
UUCP: {hplabs!, hpcea!, hpfcla!} hpnmd!darrylo
Internet: darrylo%hpnmd@relay.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion or policy of Hewlett-Packard or of the
little green men that have been following him all day.
===============================================================================
Here is a summary of my experiences with running Thomas Roell's
X11R4 version 1.1 with Esix. Some of this is documented elsewhere, or
has already been said, but it's nice to have a single document
describing everything.
First of all, the /usr/lib/X11/X386/install.sh script will not work
"as is" (it appears to be ISC-specific). You have to comment out the
tests for the "sp" (stream pipes) driver. *HOWEVER*, this does not mean
that you do not need the "sp" driver -- you do need it. With Esix, the
stream pipes driver is part of the "Network Servers" disk, and so you
must have the contents of this disk installed on your system before
X11R4 will work. Also, the install.sh script will not work properly
unless you have /usr/bin/X11 in your $PATH.
The Microsoft mouse driver in this X11R4 release seems to be
broken. As a workaround, if you have a Microsoft mouse (I do), use the
following mouse configuration line in /usr/lib/X11/X386/Xconfig:
MouseSystems 2 MS "/dev/tty00"
(The Mouse System's mouse apparently uses the same protocol as the
Microsoft Mouse.) Don't forget to edit the above line to reflect the
serial port of the mouse. Thanks to Chuck Murcko
(cmurcko@topsail.Topsail.ORG) for this fix. Microsoft mice also have a
problem where button presses are not recognized by the server until the
button is released or the mouse is moved. I don't have a fix for this.
Logitech mice (which most people seem to have) work fine.
Don't run X11R4 from the "console" console; use one of the other
nine virtual consoles. Running xinit from the console requires that a
virtual console be free (no getty or user session attached to that
console). If you, like me, have gettys running on all nine virtual
consoles, this means that you have to edit /etc/inittab (and the other
associated file below /etc/conf) to disable one of the virtual consoles.
The easiest way to avoid having to do all this work is to run xinit from
a virtual console.
Make sure that the X server /usr/bin/X11/X386 is linked to
/usr/bin/X11/X, and that it has setuid root permissions. Initially (the
first time you ever run it), the server needs to create a /dev/X
subdirectory with world-writable/readable permissions.
You'll get an error, "Creating TCP socket: Invalid argument". You
can ignore this.
Mike Knister (mknister@eecs.umich.edu) says that the cursor keys,
etc. do not work well, and that the solution is the following (I haven't
had the time to test it):
------------------------------------------------------------------------------
The following file helps with the cursor and delete keys. Put it into
a file like .xmodmap, and load (after xinit) it using:
xmodmap .xmodmap
! ---------xmodmap file to map life bearable under Esix:----------
! (for X386 1.1)
keycode 90 = Delete period
keycode 89 = Insert KP_0
keycode 86 = End KP_1
keycode 87 = Down KP_2
keycode 88 = Next KP_3
keycode 82 = Left KP_4
keycode 84 = Right KP_6
keycode 78 = Begin KP_7
keycode 79 = Up KP_8
keycode 80 = Prior KP_9
! Backspace key: I personally like it to be delete
keycode 21 = Delete
!-------------end of xmodmap file -----------------------
-------------------------------------------------------------------------------
Here are some useful screen sizes for people with the NEC Multisync
II (these were taken from Chin Fang's (fangchin@portia.Stanford.EDU)
postings in comp.unix.sysv386). I have a Multisync II and have found
that the Xconfig timings for the 800x600 resolution cause a fair amount
of flicker, not to mention poor resolution due to the large color mask
size. While not all people can use the following, due to differences in
clock frequencies, they are much nicer than using a 640X480 resolution.
-------------------------------------------------------------------------------
name clock horizontal timing vertical timing flag
# 704x528 -> ~66Hz vert freq
"704x528" 32 704 736 856 888 528 528 533 545
# 752x564 Multisync II - only -> ~64 Hz
"752x564" 36 752 788 916 952 564 564 569 594
# "No-flicker" VGA-resolution -> ~68 Hz
"640x480" 28 640 676 776 812 480 480 485 505
-------------------------------------------------------------------------------
I've only tested the "704x528" resolution.
-- Darryl Okahata
UUCP: {hplabs!, hpcea!, hpfcla!} hpnmd!darrylo
Internet: darrylo%hpnmd@relay.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion or policy of Hewlett-Packard or of the
little green men that have been following him all day.roell@informatik.tu-muenchen.de (Thomas Roell) (02/26/91)
> The Microsoft mouse driver in this X11R4 release seems to be >broken. As a workaround, if you have a Microsoft mouse (I do), use the >following mouse configuration line in /usr/lib/X11/X386/Xconfig: This is a trivial bug, which will be fixed in the next version. > MouseSystems 2 MS "/dev/tty00" > >(The Mouse System's mouse apparently uses the same protocol as the >Microsoft Mouse.) Don't forget to edit the above line to reflect the >serial port of the mouse. Thanks to Chuck Murcko >(cmurcko@topsail.Topsail.ORG) for this fix. Microsoft mice also have a >problem where button presses are not recognized by the server until the >button is released or the mouse is moved. I don't have a fix for this. It's not so simple. There is much more to configure with a mouse, but I thought it would be complicated to mention the whole syntax. But since the bug is there now lets talk about it. A mouse configuration has following format: DefaultName [buttons] [packages/sec] [baudrate] [protocol] I/O-Port Defaultname: Microsoft | Mousesystems | MMseries | Logitech | Busmouse buttons: 2 | 3 (2 selects threebutton emulation) packages/sec: 10 | 15 | 20 | 30 | 50 | 100 (all your mouse allows) baudrate: 1200 | 2400 | 4800 | 9600 (default used by mouse) Protocol: MS | (Microsoft) MSC | (Mousesystems) MM | (MMseries) RE (Bitpad relativ) Normally all optional parameters are normally selected by the Defaultname. If you specify "MouseSystems 2 MS" you select threebutton-emulation and override the default MSC protocol with MS, thus specifying a MicroSoft mouse. If you don't want this quircky threebutton-emulation, type instead of the 2 a 3. BTW, selection packages and baudrate does not work for every mouse, since only a Logitech does support this by hardware. > Mike Knister (mknister@eecs.umich.edu) says that the cursor keys, >etc. do not work well, and that the solution is the following (I haven't >had the time to test it): > >! ---------xmodmap file to map life bearable under Esix:---------- >! (for X386 1.1) >keycode 90 = Delete period > >keycode 89 = Insert KP_0 >keycode 86 = End KP_1 >keycode 87 = Down KP_2 >keycode 88 = Next KP_3 >keycode 82 = Left KP_4 >keycode 84 = Right KP_6 >keycode 78 = Begin KP_7 >keycode 79 = Up KP_8 >keycode 80 = Prior KP_9 Well this is not a bug, it's a feature. REALLY !!! It's the way the new PC/AT Keyboard proposal suggests it. But since the yuserfeedback showed me that they want to have working keyboards instead a braindamaged standard, the next X386 version will do it the old, compatible way. - Thomas -- _______________________________________________________________________________ E-Mail (domain): roell@lan.informatik.tu-muenchen.de UUCP (if above fails): roell@tumult.{uucp | informatik.tu-muenchen.de} famous last words: "diskspace - the final frontier..."
ilan343@violet.berkeley.edu (Geraldo Veiga) (02/27/91)
Is it possible to run client a linked with the X11R4 libraries under an X11R3 server? I have started playing with the X386 distribution, and tried to run the client binaries under an old ISC X server (version 1.0). Without fail, I get the message: Error: Can't Open display I have the R4 shared libraries installed. At the moment, I lack the appropriate hardware to run the X386 server. Also, I'd to know if it is possible to exchange X client binaries across 386 platforms.