Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 31
  1. #21
    emk
    emk is offline
    Untangler
    Join Date
    Oct 2008
    Location
    Mission Viejo, CA
    Posts
    37

    Default

    Quote Originally Posted by dmorris View Post
    it only boots the untangle xorg file after the main xorg file fails.
    You are quite right! My changes to the xorg.conf file forced the vertical and horizontal refresh rate as discussed here, and resulted in the Xserver getting a signal 11 and failing. So the untangle-named xorg configuration file was used after the failure.

    My suspicion is that this error is because of driver compatibility with the nVidia 8300 chip set on my motherboard: the Xserver works in UT using defaults, but generates too high a refresh rate for the monitor, and the board works with Ubuntu 6.04 using nVidia's current proprietary drives and my xorg.conf changes.

    Since I've got thru the initial installation, I'll probably continue just using web-based management from another host. But I think the refresh issue and the size of the virtual screen in X should be solved in UT before 6.2 is released or the support team will spend lots of time supporting customers on this issue.

    Eric

  2. #22
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    26,510

    Default

    I don't have a 6.2 install to work with...

    but .bashrc is the following in 6.1

    Code:
    XORG_CONF_VESA=xorg-untangle-vesa.conf
    
    sudo tee /etc/X11/$XORG_CONF_VESA <<EOF
    Section "Device"
    Identifier "Configured Video Device"
    Driver "vesa"
    EndSection
    EOF
    
    if [ `tty` = "/dev/tty1" ] ; then
      while true ; do
        ps aux | awk '/^(xinit|X|startx)/ { print $2 }' | xargs kill -9 2> /dev/null
        START_TIME=$(date +%s)
        startx
        STOP_TIME=$(date +%s)
        if [ $(($STOP_TIME - $START_TIME)) -lt 60 ] ; then
          export XORGCONFIG=$XORG_CONF_VESA
          startx
          failures=$(($failures + 1))
          [ $failures -gt 5 ] && exit
        fi
      done
    fi
    So what about...

    Code:
    XORG_CONF_VESA=xorg-untangle-vesa.conf
    
    sudo tee /etc/X11/$XORG_CONF_VESA <<EOF
    Section "Device"
    Identifier "Configured Video Device"
    Driver "vesa"
    EndSection
    Section "Monitor"
    Identifier "Vesa Monitor"
    Option "DPMS"
    HorizSync 30-83
    VertRefresh 56-76
    EndSection
    Section "Screen"
    Identifier "Default Screen"
    Device "vesa"
    Monitor "Vesa Monitor"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    Modes "1024x768"
    EndSubSection
    EndSection
    EOF
    
    if [ `tty` = "/dev/tty1" ] ; then
      while true ; do
        ps aux | awk '/^(xinit|X|startx)/ { print $2 }' | xargs kill -9 2> /dev/null
        START_TIME=$(date +%s)
        startx
        STOP_TIME=$(date +%s)
        if [ $(($STOP_TIME - $START_TIME)) -lt 60 ] ; then
          export XORGCONFIG=$XORG_CONF_VESA
          startx
          failures=$(($failures + 1))
          [ $failures -gt 5 ] && exit
        fi
      done
    fi
    Ok nevermind this is a bad idea... it isn't changing the correct file.
    Last edited by sky-knight; 05-28-2009 at 01:01 PM.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  3. #23
    emk
    emk is offline
    Untangler
    Join Date
    Oct 2008
    Location
    Mission Viejo, CA
    Posts
    37

    Default

    Rob,
    I believe the xorg.conf that will solve the problem should have the following:
    Section "Device"
    Identifier "Configured Video Device"
    Driver "vesa"
    EndSection
    Section "Monitor"
    Identifier "Vesa Monitor"
    VertRefresh 60
    EndSection
    Section "Screen"
    Identifier "Default Screen"
    Device "vesa"
    Monitor "Vesa Monitor"
    SubSection "Display"
    Virtual 1024 768
    Modes "1024x768"
    EndSubSection
    EndSection


    I think the DPMS and horizontal sync lines are not necessary for most monitors. The vertical refresh rate should be set to just 60 Hz, for which the above line should work. The depth need not be specified -- Xserver will figure it out. But the virtual screen size must be specified or the user ends up with a display page that's much larger than the monitor, and that scrolls up/down/left/right as the mouse moves beyond the monitor edges (and that odd behavior is not necessary nor important for the information conveyed in the UT main display page and in the web pages).

    Someone with supported hardware needs to test this configuration.

    Eric

  4. #24
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    26,510

    Default

    Yeah... I'm no master of X I generally just let the script to the configuration. As it stands the script I posted is putting the stuff into the wrong file anyway...
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  5. #25
    Newbie
    Join Date
    Jul 2009
    Posts
    2

    Default Thanks a ton!

    Hey guys,

    This one especially goes out to emk and sky-night. I got my 6.2 untangle working with the help of your config files. I owe you guys a drink!

    Brian

  6. #26
    Untangler jomerx's Avatar
    Join Date
    Aug 2008
    Location
    Iloilo City, Philippines
    Posts
    91

    Default

    May I ask if the xorg.conf code is applicable to my setup?
    UT Ver 6.2 (upgrade from 6.0.2)
    Monitor: Samsung 733NW
    KVM: Dlink DKVM-4K
    UT: Asus P5V800-MX (VT8251)

    I'm limited only @ 800 x 600 resolution right now
    Thanks

  7. #27
    emk
    emk is offline
    Untangler
    Join Date
    Oct 2008
    Location
    Mission Viejo, CA
    Posts
    37

    Default

    jomerx,
    My xorg.conf might work for you. It sets up the system for 1024x768 resolution with a vertical resolution of 60Hz, all of which is pretty common. I'm not familiar with your monitor or KVM or video board, so no guarantees.

    Eric

  8. #28
    Untangler jomerx's Avatar
    Join Date
    Aug 2008
    Location
    Iloilo City, Philippines
    Posts
    91

    Default

    Thanks for the reply emk

    I might give this a shot this week

  9. #29
    Untangler jomerx's Avatar
    Join Date
    Aug 2008
    Location
    Iloilo City, Philippines
    Posts
    91

    Default

    To emk,

    Would this xorg.conf file work for me?
    Please be patient, thanks

    Code:
    XORG_CONF_VESA=xorg-untangle-vesa.conf
    
    sudo tee /etc/X11/$XORG_CONF_VESA <<EOF
    Section "Device"
    Identifier "Configured Video Device"
    Driver "vesa"
    EndSection
    Section "Monitor"
    Identifier "Vesa Monitor"
    VertRefresh 60
    EndSection
    Section "Screen"
    Identifier "Default Screen"
    Device "vesa"
    Monitor "Vesa Monitor"
    SubSection "Display"
    Virtual 1024 768
    Modes "1024x768"
    EndSubSection
    EndSection
    EOF
    
    if [ `tty` = "/dev/tty1" ] ; then
      while true ; do
        ps aux | awk '/^(xinit|X|startx)/ { print $2 }' | xargs kill -9 2> /dev/null
        START_TIME=$(date +%s)
        startx
        STOP_TIME=$(date +%s)
        if [ $(($STOP_TIME - $START_TIME)) -lt 60 ] ; then
          export XORGCONFIG=$XORG_CONF_VESA
          startx
          failures=$(($failures + 1))
          [ $failures -gt 5 ] && exit
        fi
      done
    fi
    Last edited by jomerx; 07-05-2009 at 08:07 PM.

  10. #30
    Untangler
    Join Date
    May 2008
    Posts
    81

    Default

    seriously, this kind of thing still happens with Linux? OMG, no wonder people aren't flocking to it. This is beyond rediculous. I realize it's not technically UT's fault - doesn't matter; it happens in their product, so, to most people, they're to blame.

Page 3 of 4 FirstFirst 1234 LastLast

Posting Permissions

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

SEO by vBSEO 3.6.0 PL2