dear sir/madam,

i am working in Linux 7.3 version.

i am facing a problem in starting x window.

i have attached entire message given by the system.

kindly provide me the solution to sort out the problem.

Regards,

prasath

v k a prasath

while booting 

VFS filesystem : mount RPC     [FAILED]


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
after that it is displaying following message and startx is given the x window 
is not opening 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

module loader present

markers  : (--) probed ...

(==)

(==) using config file : "/etc/X11/XF86config -4 "

(EE) I810 (0)  :unknown reason for exception

(EE) I810 (0) : cannot continue

symbol xf86InterpretEDID from module /usr/X11R6/lib/modules/libvbe.a  is 
unresolved !

Error loading keymap /var/tmp/server-0.xkm

couldn't load XKB keymap, falling back to pre-XKB keymap

could not init font path element unix/:7100,removing from list !

Fatal server error :
          could not open default font 'fixed '

        
        when reporting a problem related to a server crash,please send full 
server output ,not just the last message.This can be found in the log file 
"/var/log/Xfree86.o.log".
       please report prob to xfree86 @xfree86.org


XIO :fatal IO error 104 (connection reset by peer) on X server " :0.0" after 0 
requests ( 0 known processed ) with 0 events remaining .


[prasath @ipaynet2 prasath ] $ [drm :i810_flush_queue ]*ERROR *lockup.

eth0 : Too much work at interrupt,Intrstatus =0X0001
eth0 : Too much work at interrupt,Intrstatus =0X0001
eth0 : Too much work at interrupt,Intrstatus =0X0001
...
.
.
.

8139too  :rx stop wait too long 
8139too  :rx stop wait too long 
8139too  :rx stop wait too long 
8139too  :rx stop wait too long 
8139too  :rx stop wait too long 
8139too  :rx stop wait too long 
8139too  :rx stop wait too long 
.
.
.
.
.
.
.
.

eth0 : Too much work at interrupt,Intrstatus =0X0001
eth0 : Too much work at interrupt,Intrstatus =0X0001
..
.
.
.
.
.

Reply via email to