*BSD News Article 13426


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!newsserver.jvnc.net!gmd.de!mururoa!veit
From: veit@mururoa.gmd.de (Holger Veit)
Subject: Re: keyboard problem with XFree
Message-ID: <1993Mar26.142912.8325@gmd.de>
Sender: veit@mururoa (Holger Veit)
Nntp-Posting-Host: mururoa.gmd.de
Organization: GMD - German National Research Center for Computer Science
References:  <1993Mar26.180703.1@usthk.ust.hk>
Date: Fri, 26 Mar 1993 14:29:12 GMT
Lines: 91

In article <1993Mar26.180703.1@usthk.ust.hk>, ccalex@usthk.ust.hk writes:
|> Hi Sirs,
|> 
|>  	I am a new user to 386bsd and XFree, I have the following questions and
|> wish you could help.
|> 
|> 	I have a 486PC, 16MB ram, 2 hard disks (drive C: Quantum 240MB, for DOS
|> and 386bsd, drive D: Quantum 105MB, for DOS only) both are IDE drives. And I
|> don't think my drive C will has bad sectors, because it is a new one, just 
|> bought for several weeks. I don't know what kind of hard disk controller I have
|> got, it is a very small and cheap one, not especially from any popular vendor.
|> But I think it should be a IDE controller. 

An IDE drive has no bad sectors; or more precisely: the on-drive controller
hides them from the user and replaces defective ones by spare sectors.
 
|> 	I always suffered from the problem with XFree, every time I exit from
|> XFree, my screen turn into garbage. Although I can still execute command, 
|> I can not see the characters I typed. Below is the message from the 
|> redirected output file:
|>  
|>  XFree86 Version 1.2 / X Window System
|>  (protocol Version 11, revision 0, vendor release 5000)
|>  Configured drivers:
|>    VGA256 (256 colour SVGA):
|>        et4000, et3000, pvga1, gvga, ati, tvga8900c, tvga9000
|>  Mouse: type: Microsoft, device: /dev/com2, baudrate: 1200
|>  FontPath set to "/usr/X386/lib/X11/fonts/misc/,/usr/X386/lib/X11/fonts/Type1/,
|>                /usr/X386/lib/X11/fonts/Speedo/,/usr/X386/lib/X11/fonts/75dpi/"
|>  VGA256: et4000 (mem: 1024k numclocks: 16)
|>  VGA256:   clocks:  25.2  28.3  32.5  36.1  39.9  44.9  50.4  65.0
|>  VGA256:   clocks:   0.0  56.7   0.0  72.3  79.8  89.8 100.8 130.1
|>  VGA256: Mode "1024x768": mode clock =  65.0, clock used =  65.0
|>  VGA256: Mode "800x600": mode clock =  50.4, clock used =  50.4
|>  VGA256: Mode "640x480": mode clock =  25.2, clock used =  25.2
|>  VGA256: Virtual resolution set to 1024x1024
|>  VGA256: SpeedUp mode selected (Flags=0x3f)
|>  waiting for X server to shut down xterm:  fatal IO error 32 (Broken pipe) or 
|>          KillClient on X server ":0.0"
|>  xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
|>  
|>  Cannot execute KBDFORCEASCII ioctl: Inappropriate ioctl for device
|>   
|>  	Can you tell me what is the meaning of the last three statements.
|>  I wonder they are the reason of the trouble caused. Can you also suggest me 
|>  some solution to correct these problem?

The lines shutting down the xterm are just, let me say, surprising cries by the
xterm which found out that its parent (the xserver) has interrupted the 
connection, they are not serious and do not cause the problem.

The last line can be ignored, it is from the application kbd_mode in the startx
script, not by the xserver. You might send the message to /dev/null.

Garbage on the screen after exit is caused by improper restoration of the
text/font pages. For this job the xserver relies on some defaults in the
video segment register, which do not seem to be available (the defaults),
and restores the font to elsewhere.
 
|> 	Sorry for bringing so many questions, but I really need your help.
|>  
|>  	Thank you very much for your kindly attention.
|> 
|> 	I nearly forget to ask you another question, every time I boot up 
|> 386bsd, I saw the following message on the screen:
|>  
|>  	"find: ./.X11-unix: No such file or directory."

X11 uses /tmp/.X11-unix to negotiate a pointer to the data connections within
the window system. During the run of /etc/rc the /tmp directory is cleared.
This is a non-fatal message from the process (find) which does the clean.
Ignore it, or send it to /dev/null if you do not want to see it.
  
|>  	What does it mean and how to correct the problem?
|> 
|> 	Thank you very much for your kindly attention.
|> 
|> Best regards.
|> Alex
|> P.S. my email address is ccalex@usthk.ust.hk
|> 

Holger

-- 
         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                    |    Three lines Signature space
|  |/    Schloss Birlinghoven              |    available for rent. Nearly
         DW-5205 St. Augustin, Germany     |    unused, good conditions