Why "xinit: Unknown error (errno 0): Client error."?

Why "xinit: Unknown error (errno 0): Client error."?

Post by Ken Neighbo » Tue, 15 Mar 1994 16:37:08



Nothing critical, but why does xinit exit with an error message and
non-zero exit status?  Is something setup wrong--does it do that
for everyone?  (I'm running Slackware 1.1.2, and I type "startx".)

I even get this message when I just type "xinit" and then exit the
xterm.

Thanks
Ken Neighbors

 
 
 

Why "xinit: Unknown error (errno 0): Client error."?

Post by hkenn.. » Wed, 16 Mar 1994 00:20:38



>Nothing critical, but why does xinit exit with an error message and
>non-zero exit status?  Is something setup wrong--does it do that
>for everyone?  (I'm running Slackware 1.1.2, and I type "startx".)

>I even get this message when I just type "xinit" and then exit the
>xterm.

>Thanks
>Ken Neighbors


I have a similiar problem. Nothing major.

Hi,

I just upgraded to sls 1.1.2 (I think that is correct ver. number).
When I boot the system the following error occurs with init[1]. Can
anyone point to the correct place where this file is started, so I can
change the options.

*************************** Start of boot screen ********************

Partition check:
  sda: sda1 < sda5 sda6 sda7 > sda2 sda3
VFS: Mounted root (ext2 filesystem) readonly.

init[1]: unrecognized option "ro"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Mar 13 14:50:20 init[1]: unrecognized option "ro"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Mar 13 14:50:20 init[1]: version 2.4 booting
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
sh: Testing filesystem status: Read-only file system
e2fsck 0.4a, 93/11/29 for EXT2 FS 0.4a, 93/11/19
/dev/sda7 is clean, no check.
Remounting root device with read-write enabled.
/dev/sda3 on /c type msdos (rw)
none on /proc type proc (rw)
Mar 13 20:50:25 init[1]: Entering runlevel: 5
*************************** End of boot screen *************************

Thanks

Helen


 
 
 

Why "xinit: Unknown error (errno 0): Client error."?

Post by Fled Fairla » Wed, 16 Mar 1994 18:54:15



| >Nothing critical, but why does xinit exit with an error message and
| >non-zero exit status?  Is something setup wrong--does it do that
| >for everyone?  (I'm running Slackware 1.1.2, and I type "startx".)
| >
| >I even get this message when I just type "xinit" and then exit the
| >xterm.
| >
| >Thanks
| >Ken Neighbors

|
| I have a similiar problem. Nothing major.
|

Actually, your problem is not even remotely similar to the original
poster's. Look's like you have a bad command in one of your rc.????
files; probably rc.S in the /etc/rc.d directory. You can put echo's in
these files to trace down exactly which line is causing the error, if you
can't tell just by looking at it.
        Now, does anyone have a response to the original posting? I'm
curious too...

=O.|     fled
=O

| Hi,
|
| I just upgraded to sls 1.1.2 (I think that is correct ver. number).
| When I boot the system the following error occurs with init[1]. Can
| anyone point to the correct place where this file is started, so I can
| change the options.
|
| *************************** Start of boot screen ********************

| Partition check:
|   sda: sda1 < sda5 sda6 sda7 > sda2 sda3
| VFS: Mounted root (ext2 filesystem) readonly.
|
| init[1]: unrecognized option "ro"
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| Mar 13 14:50:20 init[1]: unrecognized option "ro"
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| Mar 13 14:50:20 init[1]: version 2.4 booting
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| sh: Testing filesystem status: Read-only file system
| e2fsck 0.4a, 93/11/29 for EXT2 FS 0.4a, 93/11/19
| /dev/sda7 is clean, no check.
| Remounting root device with read-write enabled.
| /dev/sda3 on /c type msdos (rw)
| none on /proc type proc (rw)
| Mar 13 20:50:25 init[1]: Entering runlevel: 5
| *************************** End of boot screen *************************
|
| Thanks
|
| Helen

|

 
 
 

Why "xinit: Unknown error (errno 0): Client error."?

Post by Me Myself and » Thu, 17 Mar 1994 00:14:21



 [ deleted ]

Quote:

>I have a similiar problem. Nothing major.

Similar? :)

Quote:

>Hi,

>I just upgraded to sls 1.1.2 (I think that is correct ver. number).
>When I boot the system the following error occurs with init[1]. Can
>anyone point to the correct place where this file is started, so I can
>change the options.

Init is started by lilo, which is what passes the options to it.
'ro' was to make the / filing system mount read only, it doesn't seem
to do this now (new version of init? Kernel change? dunno ...).
lilo will pass this flag if there is a line in your lilo config file
saying :-

        READ-ONLY

if you remove this line and re-install lilo, the error should go away.

You then may need to do :-

        rdev -R /vmlinuz 1
                ^^^^^^^^ or whatever your kernel is called.

To make it mount the / filing system read-only.

But then I could just be barking uo completely the wrong tree ...

Andy.

 
 
 

1. tinyX gives "xinit: Unknown error (errno 0): Client error." error and dies

I am trying to set up tinyX on a system I have at home. The system is
a 386SX/16 with 8 megs of RAM, 12 megs of swap space, and around 160
megs of hard drive space. It has a generic 256K video card and a Dell
13 inch monitor. (Not much of a system, I know, but I got it for
free). When I try to start up tinyX, the X server starts up (I see the
dithered background with the X cursor), and then it dies. Below is the
output it produces on the console as it is starting and dying:

Script started on Sun Oct  1 14:31:24 1995
dogbert:/usr/X386# startx

XFree86 Version 2.0 / X Window System
(protocol Version 11, revision 0, vendor release 5000)
Operating System: Linux
Configured drivers:
  VGA16: server for 4-bit colour VGA (Patchlevel 0):
      et4000, generic
(using VT number 9)

Xconfig: /usr/X386/lib/X11/Xconfig
(**) stands for supplied, (--) stands for probed/default values
(**) Mouse: type: Microsoft, device: /dev/ttyS0, baudrate: 1200
(**) FontPath set to "/usr/X386/lib/X11/fonts/misc/"
(--) VGA16: chipset:  generic
(--) VGA16: videoram: 256k (using 256k)
(--) VGA16: clocks:  25.50  28.32  35.50   0.00
(--) VGA16: Maximum allowed dot-clock: 90MHz
(**) VGA16: Mode "640x480": mode clock =  28.322, clock used =  28.322
(**) VGA16: Virtual resolution set to 800x600

waiting for X server to shut down

xinit:  Unknown error (errno 0):  Client error.
dogbert:/usr/X386#

Does anyone have any idea what is causing it to die like this?
Suggestions are greatly appreciated. Obviously it would be better if I
were running on a faster machine, but I can't afford to upgrade just
yet, so if anyone can suggest how to get this working in the meantime,
I would be most grateful.

TIA,

/Matthew

--
Matthew Cravit,               | "Cum catapultae proscriptae erunt tum
DePaul University, Chicago IL |  soli proscripti catapultas haberunt."

2. disk-less clients

3. What's "Unknown error (errno 0): Client error"

4. Finger showing garbage - How to fix?

5. xinit: Unknown error (errno 0): Client error.

6. Please, help! rsh hangs at the end of execution!

7. Install error on G3: "error unpacking archive: unknown error"

8. Problem Frontpage-Apache

9. "syslogd: unknown priority "24" " error - won't boot!

10. dip error "unknown server error"

11. "error 2 reading header: unknown error" - what is this?

12. SLIP error: "Unknown Server Error" ??

13. APACHE Error: "Signaling Error: error already pending"