X Windows System


Results 1 to 15 of 15

Thread: X Windows System

  1. #1
    Join Date
    Apr 2002
    Location
    Augusta Georgia USA
    Posts
    38

    X Windows System

    If anyone out there can help me figure out what, exactly, I need to do to resolve this problem I would be extremely appreciative.

    Yesterday my server crashed for the first time.

    I've been running Mandrake 8.1 for about two months now with no problems. I was attempting to setup a script to do an automatic tape backup on Friday evenings (shouldn't be a problem, I already have a backup scheme in place for my removeable hard drives... but that's not the problem.).

    My server locked up and I was forced to do a reboot.

    When it came back up... no X.

    I searched and searched my system and finally found the inittab file and change my default initlevel to 3. So everyone is able to log in and the shares are all available, yada, yada.

    Now I tried to find out what went wrong but have been unable to find anything.

    When I have my default initlevel set to 5 I get

    screen goes grey
    screen goes black
    screen goes grey
    screen goes black
    screen goes grey
    screen goes black
    screen goes grey
    screen goes black
    screen goes grey
    screen goes black

    I tried to run XFdrake on my server but, after it asked me for a few CD's, it did nothing. I tried to run X and got an error.

    I can SSH into my server, so I did, and I ran X through it so that I could copy and paste the full body of the error here.

    What can I do to fix this? Anyone?

    Thanks in advance!

    [root@r2d2 root]# X

    XFree86 Version 3.3.6 / X Window System
    (protocol Version 11, revision 0, vendor release 6300)
    Release Date: January 8 2000
    If the server is older than 6-12 months, or if your card is newer
    than the above date, look for a newer version before reporting
    problems. (see http://www.XFree86.Org/FAQ)
    Operating System: Linux 2.4.8-5mdkenterprise i686 [ELF]
    Configured drivers:
    SVGA: server for SVGA graphics adaptors (Patchlevel 1):
    NV1, STG2000, RIVA 128, RIVA TNT, RIVA TNT2, RIVA ULTRA TNT2,
    RIVA VANTA, RIVA ULTRA VANTA, RIVA INTEGRATED, GeForce 256,
    GeForce DDR, Quadro, ET4000, ET4000W32, ET4000W32i, ET4000W32i_rev_b,
    ET4000W32i_rev_c, ET4000W32p, ET4000W32p_rev_a, ET4000W32p_rev_b,
    ET4000W32p_rev_c, ET4000W32p_rev_d, ET6000, ET6100, et3000, pvga1,
    wd90c00, wd90c10, wd90c30, wd90c24, wd90c31, wd90c33, gvga, r128, ati,
    sis86c201, sis86c202, sis86c205, sis86c215, sis86c225, sis5597,
    sis5598, sis6326, sis530, sis620, sis300, sis630, sis540, tvga8200lx,
    tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga8900d, tvga9000,
    tvga9000i, tvga9100b, tvga9200cxr, tgui9400cxi, tgui9420, tgui9420dgi,
    tgui9430dgi, tgui9440agi, cyber9320, tgui9660, tgui9680, tgui9682,
    tgui9685, cyber9382, cyber9385, cyber9388, cyber9397, cyber9520,
    cyber9525, 3dimage975, 3dimage985, cyber9397dvd, blade3d, cyberblade,
    clgd5420, clgd5422, clgd5424, clgd5426, clgd5428, clgd5429, clgd5430,
    clgd5434, clgd5436, clgd5446, clgd5480, clgd5462, clgd5464, clgd5465,
    clgd6205, clgd6215, clgd6225, clgd6235, clgd7541, clgd7542, clgd7543,
    clgd7548, clgd7555, clgd7556, ncr77c22, ncr77c22e, cpq_avga, mga2064w,
    mga1064sg, mga2164w, mga2164w AGP, mgag200, mgag100, mgag400, oti067,
    oti077, oti087, oti037c, al2101, ali2228, ali2301, ali2302, ali2308,
    ali2401, cl6410, cl6412, cl6420, cl6440, video7, ark1000vl, ark1000pv,
    ark2000pv, ark2000mt, mx, realtek, s3_savage, s3_virge, AP6422, AT24,
    AT3D, s3_svga, NM2070, NM2090, NM2093, NM2097, NM2160, NM2200,
    ct65520, ct65525, ct65530, ct65535, ct65540, ct65545, ct65546,
    ct65548, ct65550, ct65554, ct65555, ct68554, ct69000, ct64200,
    ct64300, mediagx, V1000, V2100, V2200, p9100, spc8110, i740, i740_pci,
    Voodoo Banshee, Voodoo3, smi, generic
    (using VT number 7)

    XF86Config: /etc/X11/XF86Config
    (**) stands for supplied, (--) stands for probed/default values
    (**) XKB: keycodes: "xfree86"
    (**) XKB: types: "default"
    (**) XKB: compat: "default"
    (**) XKB: symbols: "us(pc105)"
    (**) XKB: geometry: "pc"
    (**) XKB: rules: "xfree86"
    (**) XKB: model: "pc105"
    (**) XKB: layout: "us"
    (**) Mouse: type: IMPS/2, device: /dev/psaux, buttons: 5
    (**) Mouse: zaxismapping: (-)4 (+)5
    (**) SVGA: Graphics device ID: "RIVA TNT2"
    (**) SVGA: Monitor ID: "monitor1"
    (--) SVGA: Mode "1280x1024" needs hsync freq of 74.59 kHz. Deleted.
    (--) SVGA: Mode "1600x1200" needs hsync freq of 75.00 kHz. Deleted.
    (--) SVGA: Mode "1152x864" needs hsync freq of 76.01 kHz. Deleted.
    (--) SVGA: Mode "1280x1024" needs hsync freq of 78.86 kHz. Deleted.
    (--) SVGA: Mode "1024x768" needs hsync freq of 80.21 kHz. Deleted.
    (--) SVGA: Mode "1280x1024" needs hsync freq of 81.13 kHz. Deleted.
    (--) SVGA: Mode "1400x1050" needs hsync freq of 81.49 kHz. Deleted.
    (--) SVGA: Mode "1600x1200" needs hsync freq of 87.50 kHz. Deleted.
    (--) SVGA: Mode "1152x864" needs hsync freq of 89.62 kHz. Deleted.
    (--) SVGA: Mode "1280x1024" needs hsync freq of 91.15 kHz. Deleted.
    (--) SVGA: Mode "1600x1200" needs hsync freq of 93.75 kHz. Deleted.
    (--) SVGA: Mode "1600x1200" needs hsync freq of 105.77 kHz. Deleted.
    (--) SVGA: Mode "1600x1200" needs hsync freq of 106.25 kHz. Deleted.
    (--) SVGA: Mode "1280x1024" needs hsync freq of 107.16 kHz. Deleted.
    (--) SVGA: Mode "1800X1440" needs hsync freq of 96.15 kHz. Deleted.
    (--) SVGA: Mode "1800X1440" needs hsync freq of 104.52 kHz. Deleted.
    (--) SVGA: Mode "1920x1440" needs hsync freq of 90.00 kHz. Deleted.
    (--) SVGA: Mode "1920x1440" needs hsync freq of 112.50 kHz. Deleted.
    (**) FontPath set to "unix/:-1"
    (--) SVGA: PCI: NVidia Riva Ultra Vanta rev 21, Memory @ 0xe6000000, 0xe4000000
    (--) SVGA: chipset: RIVA ULTRA TNT2
    (--) SVGA: videoram: 32640k
    (**) SVGA: Option "dac_8_bit"
    (**) SVGA: Option "power_saver"
    (**) SVGA: Using 16 bpp, Depth 16, Color weight: 565
    (--) SVGA: Maximum allowed dot-clock: 350.000 MHz
    (**) SVGA: Mode "1280x1024": mode clock = 110.000
    (**) SVGA: Mode "1024x768": mode clock = 98.900
    (**) SVGA: Mode "800x600": mode clock = 69.650
    (**) SVGA: Mode "640x480": mode clock = 45.800
    (--) SVGA: Virtual resolution set to 1280x1024
    (--) SVGA: SpeedUp code selection modified because virtualX != 1024
    (--) SVGA: RIVA ULTRA TNT2: Using hardware cursor
    (--) SVGA: Using XAA (XFree86 Acceleration Architecture)
    (--) SVGA: XAA: Solid filled rectangles
    (--) SVGA: XAA: Screen-to-screen copy
    (--) SVGA: XAA: Using 10 128x64 areas for pixmap caching
    (--) SVGA: XAA: Caching tiles and stipples
    (--) SVGA: XAA: Horizontal and vertical lines and segments
    _FontTransSocketUNIXConnect: Can't connect: errno = 2
    failed to set default font path 'unix/:-1'
    Fatal server error:
    could not open default font 'fixed'

    When reporting a problem related to a server crash, please send
    the full server output, not just the last messages

    [root@r2d2 root]#
    Registered Linux User #324436
    Registered Linux Box #209059

    One by one, the Penguins are taking my sanity...

  2. #2
    Join Date
    Jul 2001
    Location
    Oxford
    Posts
    535
    Try changing the fontpath "unix/:-1" to "unix/:7100" in /etc/X11/XF86Config and restart X.

    It's definitely a font server problem (X can't connect to your font server).

    Btw - you do realise you're running Xf86 3.3.6? My parents' system has a Riva TNT2 and Xf86 4.x works great on it - I think you can use XFdrake to switch from 3.3.6 to 4.x.

  3. #3
    Join Date
    Apr 2002
    Location
    Augusta Georgia USA
    Posts
    38
    Thanks for the info, I'll give it a shot!
    Registered Linux User #324436
    Registered Linux Box #209059

    One by one, the Penguins are taking my sanity...

  4. #4
    Join Date
    Apr 2002
    Location
    Augusta Georgia USA
    Posts
    38
    _FontTransSocketUNIXConnect: Can't connect: errno = 2
    failed to set default font path 'unix/:7100'
    Fatal server error:
    could not open default font 'fixed'

    When reporting a problem related to a server crash, please send
    the full server output, not just the last messages



    Tried it, didn't work

    I tried running XF86 4.x when I first installed Mandrake and I got

    screen goes grey
    screen goes black
    screen goes grey
    screen goes black
    screen goes grey
    screen goes black
    screen goes grey
    screen goes black
    screen goes grey
    screen goes black


    so I reinstalled and switched to 3.3.6

    It's been working fine... up until yesterday
    Registered Linux User #324436
    Registered Linux Box #209059

    One by one, the Penguins are taking my sanity...

  5. #5
    Join Date
    Jun 2002
    Posts
    255
    Try adding:

    FontPath "/usr/lib/X11/fonts/misc"
    FontPath "/usr/lib/X11/fonts/100dpi"
    FontPath "/usr/lib/X11/fonts/75dpi"

    to the files section. Comment out the unix/: line. Make sure the paths are real and have files, as these path come from Debian. If it's not right look for the 75dpi directory on your system and use that. This will give you enough fonts to start X. The unix/: is refering to a font server, which probably isn't running. You will want to make sure xfs is running. When it is, add the unix: line again at the top of the "Files" section.

    Good luck,
    chris

  6. #6
    Join Date
    Apr 2002
    Location
    Augusta Georgia USA
    Posts
    38
    Thanks Chris, that seemed to do something.

    X seemed to start, sorta.

    Now I have the grey screen with the X cursor but nothing else.
    Registered Linux User #324436
    Registered Linux Box #209059

    One by one, the Penguins are taking my sanity...

  7. #7
    Join Date
    Dec 2000
    Location
    Glasgow, Scotland
    Posts
    4,361
    OK - you now have X but no window manager - check your ~/.xinitrc and /etc/X11/xinitrc(?) files.
    mrBen "Carpe Aptenodytes"

    Linux User #216794

    My blog page

    3rd year running - get yourself to LugRadio Live 7th-8th July 2007, Wolverhampton, UK. The premier FLOSS community event.

  8. #8
    Join Date
    Apr 2002
    Location
    Augusta Georgia USA
    Posts
    38
    /etc/X11/xinit/xinitrc

    #!/bin/sh
    # (c) 2000 MandrakeSoft

    exec /etc/X11/Xsession $*



    What, exactly, am I looking for?
    Registered Linux User #324436
    Registered Linux Box #209059

    One by one, the Penguins are taking my sanity...

  9. #9
    Join Date
    Dec 2000
    Location
    Glasgow, Scotland
    Posts
    4,361
    OK, try running 'kdm' from the command line, or going back to init level 5 (type init 5 as su)

    Failing that, copy that file to your home directory as .xinitrc and then add:

    exec <myfavwindowmanager>

    to the end, and try startx again.
    mrBen "Carpe Aptenodytes"

    Linux User #216794

    My blog page

    3rd year running - get yourself to LugRadio Live 7th-8th July 2007, Wolverhampton, UK. The premier FLOSS community event.

  10. #10
    Join Date
    Apr 2002
    Location
    Augusta Georgia USA
    Posts
    38
    would be happy to do just that... only I can't get past the grey screen I have now.

    The only way I've been able to get in to see the system files is through SSH
    Registered Linux User #324436
    Registered Linux Box #209059

    One by one, the Penguins are taking my sanity...

  11. #11
    Join Date
    Dec 2000
    Location
    Glasgow, Scotland
    Posts
    4,361
    Press Ctrl-Alt-Backspace to kill XWindows.
    mrBen "Carpe Aptenodytes"

    Linux User #216794

    My blog page

    3rd year running - get yourself to LugRadio Live 7th-8th July 2007, Wolverhampton, UK. The premier FLOSS community event.

  12. #12
    Join Date
    Apr 2002
    Location
    Augusta Georgia USA
    Posts
    38
    That worked.

    The only problem that I have now is when I try to login as myself I get an error message from KDE telling me that the /tmp directory is out of disk space.

    When I try to log in as another user I get the same error.

    So I try logging in with GNOME as my window manager and I get an error that says "GDM is not running - Contact your system administrator"

    The funny thing is, if I log in as "root" I can get into KDE with no problem.

    I went to the software manager and checked for any updates from Mandrake Update and I installed most all of them in the hopes that something, somewhere, was screwed up and that might fix it.

    It didn't.

    Any idea why I keep getting those errors?

    I checked the /tmp directory as well as the $USER/tmp directories and they are all virually empty.

    I have Linux running on a 60GB hard drive so I can't imagine why it keeps telling me I am out of disk space.
    Registered Linux User #324436
    Registered Linux Box #209059

    One by one, the Penguins are taking my sanity...

  13. #13
    Join Date
    Dec 2000
    Location
    Glasgow, Scotland
    Posts
    4,361
    What are the permissions on /tmp?
    mrBen "Carpe Aptenodytes"

    Linux User #216794

    My blog page

    3rd year running - get yourself to LugRadio Live 7th-8th July 2007, Wolverhampton, UK. The premier FLOSS community event.

  14. #14
    Join Date
    Apr 2002
    Location
    Augusta Georgia USA
    Posts
    38
    First the /tmp directory, then the /home/nivuahc/tmp directory:


    drwxrwxrwt 17 root root 1024 Jul 18 11:19 tmp/

    drwx------ 6 nivuahc nivuahc 12288 Jul 18 09:58 tmp/
    Registered Linux User #324436
    Registered Linux Box #209059

    One by one, the Penguins are taking my sanity...

  15. #15
    Join Date
    Apr 2002
    Location
    Augusta Georgia USA
    Posts
    38
    chalk this one up to a very stupid user error.

    I've been so lost in the world of Windows that it hadn't occurred to me that the / directory was a separate partition that was only 235MB.

    And if you look back at the beginning of this whole thread you'll understand why.

    I attempted to do a system backup for the first time using TAR

    So I created a directory called /archive and went to it.

    I couldn't understand why it kept failing... I mean, it would get to about 190MB then just totally crap out.

    Next thing I know, my server crashes.

    I reboot and now I can't get back into KDE.

    Some of my services won't start (namely the font server) and why?

    Because I filled up the / partition.

    Like an idiot.



    consequently, I erased my failed TAR file and everything is a-okay now
    Registered Linux User #324436
    Registered Linux Box #209059

    One by one, the Penguins are taking my sanity...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •