sax3 testers needed !!

Hi

Please try out the monitor module, that should work now by using sax3-monitor

Can this be built for 11.3 as well?

Index of /repositories/X11:/sax

I don’t yet have 11.4 installed on my main laptop.

I tried with sax3-monitor and on restarting X I had no screens found.Line 4 of my /etc/X11/99-sax.monitors.conf
didn’t have the required quotation marks. Also only one of my monitors was found.
I was able to recover by removing the /etc/X11/99-sax.monitors.conf and 99-sax.screen.conf files

linux-69p3:/home/dale # cat /etc/X11/xorg.conf.d/99-saxscreen.conf
Section “Screen”
Identifier “SaX3-screen”
Device “SaX3-device”
Monitor SaX3-monitor
DefaultDepth 24
SubSection “Display”
Depth 24
Modes “1024x600_60.00”
EndSubSection
EndSection

linux-69p3:/home/dale # cat /etc/X11/xorg.conf.d/99-saxmonitors.conf
Section “Monitor”
Identifier “SaX3-monitor”
Modeline “1024x600_60.00” 49.00 1024 1072 1168 1312 600 603 613 624 -hsync +vsync
EndSection


sorry i have been out for the last couple of days i will post them later

here is the result from clicking on MOUSE

<M> [ui] YUI.cc:83 YUI(): Creating UI without threads
<M> [ui] YUI.cc:236 topmostConstructorHasFinished(): Running without threads
<M> [qt-styler] QY2Styler.cc:104 loadStyleSheet(): Using style sheet “/usr/share/YaST2/theme/current/wizard/style.qss”
<M> [qt-ui] YQUI.cc:311 processCommandLineArgs(): Qt argument: sax3
<M> [qt-ui] YQUI.cc:445 calcDefaultSize(): Default size: 1176 x 716
<M> [qt-ui] YQUI.cc:275 initUI(): Forcing /usr/lib64/libQtGui.so.4 open successful
<M> [qt-ui] YQApplication.cc:140 loadPredefinedQtTranslations(): Selected language: en_US
<WRN> [qt-ui] YQApplication.cc:164 loadPredefinedQtTranslations(): Can’t load translations for predefined Qt dialogs from /usr/share/qt4/translations/qt_en.qm
<M> [qt-ui] YQUI.cc:288 initUI(): YQUI initialized. Thread ID: 0x7f453e9fc720
DP IF<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut for YPushButton “Monitor” at 0x2322268
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut for YPushButton “Touch Pad” at 0x267de58
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut for YPushButton “KeyBoard” at 0x14e56d8
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut for YPushButton “Mouse” at 0x1b279c8
sax3-mouse
<M> [ui] YUI.cc:529 ~YUITerminator(): Shutting down UI
Segmentation fault

My system configuration

Operating System=SuSE 11.4 x86_64
Kernel=kernel-default 2.6.37.6-0.7.1-x86_64
GUI=KDE: 4.6.00 (4.6.0) “release 6”

if you need anymore information please let me know

I updated it :smiley: That is the no quotation marks

What version should we use to test now ? I note 0.1-15.1 in X11:sax and version 0.1-17.1 in home:manugupt1.

I will give it a try to build it on 11.3, please try and let me know. It may take a bit of time just that.

It will be available in X11:sax itself as sax3-11.3 most probably

I suggest keep X11:sax it is in sync with my home:repository but it might take a bit of time to get synched. It should be already there

Success with sax3-monitor !!

I installed sax3-0.1-18.1.i586 and the tests reported in this post are with that sax3 version. Again, my test PC is a athlon-1100 w/2GB RAM and a nVidia FX5200 graphic card and a Samsung T260 26" monitor connected through an Aten CS1784 KVM switch using the DVI connection.

This version of sax3 works for 1440x900 resolution with nouveau driver selected on an openSUSE-12.1 milestone4 with the ‘workaround’ in place for the nouveau driver (as the nouveau driver is nominally broken on openSUSE-12.1 M3 and M4).

So I think that is a bit challenging for sax3 and it was good to see it pass.

Some history: When trying to run sax3 before this latest version I noted:
(1) the monitor icon in sax3 would crash sax3 without running the sax3-monitor program
(2) the sax3-monitor program created a configuration that would not boot with this monitor.

With sax3-0.1-18.1 clicking on the ‘monitor’ icon did successfully launch the sax3-monitor ! I obtained this setting :
http://thumbnails48.imagebam.com/14687/1d6770146867746.jpg](http://www.imagebam.com/image/1d6770146867746)
[click on image for larger view]

I don’t have the nvidia driver installed, and that is not my desired resolution, so I then tuned it to this setting:
http://thumbnails27.imagebam.com/14687/ef355c146867750.jpg](http://www.imagebam.com/image/ef355c146867750)
[click on image for larger view]

Now I happen to know 1440x900 works, so I thought I would start with that resolution. In truth this video card is capable of a higher resolution, as is this monitor, and I may try to obtain that higher resolution later, but for now, I thought I would stick with a baseline that I have seen work with nouveau in the past.

As soon as I clicked on ‘OK’ the sax3-monitor window closed. There was no remaining ‘sax3’ window showing. The bash shell text that scolled by when running sax3 is copied here on SUSE paste

The /etc/X11/xorg.conf.d/99-saxdevice.conf file created was:


Section "Device"
Identifier "SaX3-device"
Driver "nouveau"
EndSection

and the 99-saxmonitors.conf file created was


Section "Monitor"
Identifier "SaX3-monitor"
Modeline "1440x900_60.00"  106.50  1440 1528 1672 1904  900 903 909 934 -hsync +vsync
EndSection

and the 99-saxscreen.conf file that was created was:


Section "Screen"
Identifier "SaX3-screen"
Device "SaX3-device"
Monitor "SaX3-monitor"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1440x900_60.00"
EndSubSection
EndSection

As noted, a reboot to run level 5 (the LXDE desktop) worked !! Very nice. The /var/log/Xorg.0.log file is pasted here for review

And the xrandr output:


oldcpu@stonehenge01:~> xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 4096 x 4096
VGA-1 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 550mm x 340mm
   1280x1024      60.0  
   1440x900       59.9* 
   1280x960       60.0  
   1280x800       59.8  
   1024x768       60.0  
   800x600        60.3     56.2  
   640x480        60.0  
TV-1 disconnected (normal left inverted right x axis y axis)

Planned Future test

If I get the time, I will test to see if I can obtain 1680x1050 (or 1600x1200) resolution with this monitor/FX5200 combination. In the past the best I have obtained with the nouveau driver is 1440x900, so it will be interesting to see if I can do better with this beta version of sax3.

However I note we have guests planned for the next 3 days, and I go on vacation to North America in 6 days, so if I don’t get around to this test this AM, then I only have a brief 3 day window from Tues to Thurs next week to do a further test.

I’m having second thoughts now on how well it worked, as I note this in the Xorg.0.log file:


    34.968] (II) NOUVEAU(0): Output VGA-1 using monitor section SaX3-monitor
    35.073] (II) NOUVEAU(0): Output DVI-I-1 has no monitor section
....
    35.344] (II) NOUVEAU(0): Output DVI-I-1 connected
    35.344] (II) NOUVEAU(0): Output TV-1 disconnected
    35.344] (II) NOUVEAU(0): Using exact sizes for initial modes
    35.344] (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1440x900

This monitor is connected to the KVM switch by a DVI and to the monitor from there via a DVI. The log files says sax3 is using VGA. Hence it has me thinking that the output I am getting is more due to default nouveau/X/udev settings than due to sax3’s config files. …

If I get to play with a higher resolution I will find out for certain.

From above I note this in the xrandr:


oldcpu@stonehenge01:~> xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 4096 x 4096
VGA-1 disconnected (normal left inverted right x axis y axis)
**DVI-I-1** connected 1440x900+0+0 (normal left inverted right x axis y axis) 550mm x 340mm
   1280x1024      60.0  
   1440x900       59.9* 
   1280x960       60.0  
   1280x800       59.8  
   1024x768       60.0  
   800x600        60.3     56.2  
   640x480        60.0  
TV-1 disconnected (normal left inverted right x axis y axis)

ie DVI-I-1 is the DVI connection. In that case, I am wondering if the /etc/X11/xorg.conf.d/99-saxdevice.conf should not instead read:


Section "Device"
  Identifier "SaX3-device"
**  Option "Monitor-DVI-I-1" "SaX3-monitor"**
  Driver "nouveau"
EndSection

Note the extra line I inserted.

I rebooted with that setting, and now I note in the Xorg.0.log file these two lines:


    34.072] (II) NOUVEAU(0): Output VGA-1 using monitor section SaX3-monitor
    34.204] (II) NOUVEAU(0): Output DVI-I-1 using monitor section SaX3-monitor

and the complete Xorg.0.log file.

How should sax3 handle the output selection to a VGA or DVI device ? DVI is coming quite common. Should there be a DVI or VGA selection option in sax3-monitor (Note - I have no idea what should be there - I’m just brainstorming … )

How should sax3 handle the output selection to a VGA or DVI device ? DVI is coming quite common. Should there be a DVI or VGA selection option in sax3-monitor (Note - I have no idea what should be there - I’m just brainstorming … )

I can’t test sax3 (as I’m still using 11.3), but I’m following this with interest. I think you’re analysis is correct here oldcpu. The correct active device name(s) can be determined from xrandr, and could be displayed for the user to choose from. I’m assuming sax3 cannot yet handle dual monitor set-ups?

I conducted another sax3 test with the same Samsung T260 monitor connected via a Aten CS1784 kvm switch with a different openSUSE version, different PC and different graphic hardware. This time the PC was an Intel Core i7 920 with a nVidia GTX260 graphic card, with the proprietary nvidia graphic driver installed (version 280.13) connected to the KVM (and hence monitor) via a DVI connection. This card has no VGA output. It does have 2 DVI output connectors. This was with a 64-bit openSUSE-11.4. The version of sax3 installed for the test is sax3-0.1-18.1.x86_64.

The test was to create a lower 1680x1050 resolution and it worked !

Graphic card details when running nVidia graphic driver from " lspci -nnk | grep VGA -A2 " :


07:00.0 VGA compatible controller [0300]: nVidia Corporation GT200 [GeForce GTX 260] [10de:05e2] (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:82cf]
	Kernel driver in use: nvidia

BEFORE running sax3, with the nVidia proprietary driver I obtain the 1920x1280 resolution by default (as seen by this xrandr BEFORE running sax3):


Screen 0: minimum 320 x 175, current 1920 x 1200, maximum 1920 x 1200
default connected 1920x1200+0+0 0mm x 0mm
   1920x1200      50.0* 
   1680x1050      51.0  
   1600x1200      52.0  
   1440x900       53.0  
   1400x1050      54.0     55.0  
   1280x1024      56.0     57.0     58.0  
   1280x960       59.0     60.0  
   1280x800       61.0  
   1152x864       62.0  
   1024x768       63.0     64.0     65.0     66.0     67.0     68.0  
   960x720        69.0     70.0  
   928x696        71.0     72.0  
   896x672        73.0     74.0  
   832x624        75.0  
   800x600        76.0     77.0     78.0     79.0     80.0     81.0     82.0     83.0     84.0     85.0  
   720x400        86.0  
   700x525        87.0     88.0  
   640x512        89.0     90.0     91.0  
   640x480        92.0     93.0     94.0     95.0     96.0     97.0     98.0  
   640x400        99.0  
   640x350       100.0  
   576x432       101.0  
   512x384       102.0    103.0    104.0    105.0    106.0  
   416x312       107.0  
   400x300       108.0    109.0    110.0    111.0    112.0  
   360x200       113.0  
   320x240       114.0    115.0    116.0    117.0  
   320x200       118.0  
   320x175       119.0 

with BEFORE running sax3 this default (BEFORE running sax3) /var/log/Xorg.0.log file.

I then ran sax3 obtaining this graphic display:
http://thumbnails54.imagebam.com/14689/f2fd36146885553.jpg](http://www.imagebam.com/image/f2fd36146885553)
[click on image for larger view]

Note I selected 1680x1050 to see if I could get sax3 to produce a lower resolution configuration. I clicked ok, and noted that on that instead of there being a 99-sax3monitor.conf, 99-sax3device.conf and 99-sax3screen.conf created (which happened on a 32-bit PC with the nouveau driver), that instead the existing /etc/X11/xorg.conf.d/ 50-device.conf, 50-monitor.conf and 50-screen.conf were changed by sax3.

These files were changed to:

/etc/X11/xorg.conf.d/50-device.conf


Section "Device"
  Identifier "Default Device"

  #Driver "radeon"

  ## Required magic for radeon/radeonhd drivers; output name
  ## (here: "DVI-0") can be figured out via 'xrandr -q'
  #Option "monitor-DVI-0" "Default Monitor"

EndSection
Section "Device"
Identifier "SaX3-device"
Driver "nvidia"
EndSection

/etc/X11/xorg.conf.d/50-monitor.conf


Section "Monitor"
  Identifier "Default Monitor"

  ## If your monitor doesn't support DDC you may override the
  ## defaults here
  #HorizSync 28-85
  #VertRefresh 50-100

  ## Add your mode lines here, use e.g the cvt tool

EndSection
Section "Monitor"
Identifier "SaX3-monitor"
Modeline "1680x1050_60.00"  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync
EndSection

/etc/X11/xorg.conf.d/50-screen.conf


Section "Screen"
  Identifier "Default Screen"

  Device "Default Device"

  ## Doesn't help for radeon/radeonhd drivers; use magic in
  ## 50-device.conf instead
  Monitor "Default Monitor"

EndSection
Section "Screen"
Identifier "SaX3-screen"
Device "SaX3-device"
Monitor "SaX3-monitor"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1680x1050_60.00"
EndSubSection
EndSection

and then I rebooted and the 64-bit openSUSE-11.4 with the nvidia proprietary driver came up to a resolution of 1680x1050 with the nvidia graphic driver. The xrandr output illustrates the lower resolution in effect:


Screen 0: minimum 320 x 175, current 1680 x 1050, maximum 1680 x 1050
default connected 1680x1050+0+0 0mm x 0mm
   1680x1050      50.0* 
   1440x900       51.0  
   1400x1050      52.0     53.0  
   1280x1024      54.0     55.0     56.0  
   1280x960       57.0     58.0  
   1280x800       59.0  
   1152x864       60.0  
   1024x768       61.0     62.0     63.0     64.0     65.0     66.0  
   960x720        67.0     68.0  
   928x696        69.0     70.0  
   896x672        71.0     72.0  
   832x624        73.0  
   800x600        74.0     75.0     76.0     77.0     78.0     79.0     80.0     81.0     82.0     83.0  
   720x400        84.0  
   700x525        85.0     86.0  
   640x512        87.0     88.0     89.0  
   640x480        90.0     91.0     92.0     93.0     94.0     95.0     96.0  
   640x400        97.0  
   640x350        98.0  
   576x432        99.0  
   512x384       100.0    101.0    102.0    103.0    104.0  
   416x312       105.0  
   400x300       106.0    107.0    108.0    109.0    110.0  
   360x200       111.0  
   320x240       112.0    113.0    114.0    115.0  
   320x200       116.0  
   320x175       117.0  


and the /var/log/Xorg.0.log file is here.

I installed and tested sax3 on an HP dv2815nr laptop that has 1280x768
resolution. It is setup correctly using the framebuffer driver, but nouveau sets
the resolution as 1024x768 and will not let it be changed. Running the
proprietary driver is not an option.

I chose nouveau os the driver. The box of available resolutions was empty so I
selected the “I want my own CVT” and proceeded to choose 1280x768. Sax3 then
seqfaulted. The log is below:

If you need any further testing, please let me know.

finger@larrylap:~/wireless-testing-new> sax3
<M> [ui] YUI.cc:83 YUI(): Creating UI without threads
<M> [ui] YUI.cc:236 topmostConstructorHasFinished(): Running without threads
<M> [qt-styler] QY2Styler.cc:104 loadStyleSheet(): Using style sheet
“/usr/share/YaST2/theme/current/wizard/style.qss”
<M> [qt-ui] YQUI.cc:311 processCommandLineArgs(): Qt argument: sax3
<M> [qt-ui] YQUI.cc:445 calcDefaultSize(): Default size: 800 x 600
<M> [qt-ui] YQUI.cc:275 initUI(): Forcing /usr/lib64/libQtGui.so.4 open successful
<M> [qt-ui] YQApplication.cc:140 loadPredefinedQtTranslations(): Selected
language: en_US
<WRN> [qt-ui] YQApplication.cc:164 loadPredefinedQtTranslations(): Can’t load
translations for predefined Qt dialogs from /usr/share/qt4/translations/qt_en.qm
<M> [qt-ui] YQUI.cc:288 initUI(): YQUI initialized. Thread ID: 0x7fe55a2f3720
DP IF<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid
shortcut for YPushButton “Monitor” at 0x33e40c8
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YPushButton “Mouse” at 0xa42368
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YPushButton “Touch Pad” at 0x1ecac68
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YPushButton “KeyBoard” at 0x173a2f8
sax3-monitor
rm: cannot remove `/tmp/sax*’: No such file or directory

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/larrylap.lan:9
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X.Org X Server 1.9.3
Release Date: 2010-12-13
X Protocol Version 11, Revision 0
Build Operating System: openSUSE SUSE LINUX
Current Operating System: Linux larrylap.lan 3.0.0-Linus+ #96 SMP Thu Aug 4
11:16:18 CDT 2011 x86_64
Kernel command line: root=/dev/disk/by-id/ata-ST9500420AS_5VJ10PW2-part7
resume=/dev/disk/by-id/ata-ST9500420AS_5VJ10PW2-part2 splash=silent quiet vga=0x317
Build Date: 07 June 2011 02:49:07AM

Current version of pixman: 0.20.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (–) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: “/tmp/sax3.0LcWT”, Time: Sat Aug 27 16:07:29 2011
(==) Using config directory: “/etc/X11/xorg.conf.d”
(EE) Failed to load module “nvidia” (module does not exist, 0)

Fatal server error:
xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)

Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at “/tmp/sax3.0LcWT” for additional information.

xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Loading AUgeas/tmp/sax3.0LcWT 98.114] (==) Matched nvidia as autoconfigured
driver 0
98.114] (==) Matched nouveau as autoconfigured driver 1
98.114] (==) Matched nv as autoconfigured driver 2
98.115] (==) Matched fbdev as autoconfigured driver 3
98.115] (==) Assigned the driver to the xf86ConfigLayout
IN DETECT RESOLUTION---->File opened<M> [ui] YUI.cc:83 YUI(): Creating UI
without threads
<M> [ui] YUI.cc:236 topmostConstructorHasFinished(): Running without threads
<M> [qt-styler] QY2Styler.cc:104 loadStyleSheet(): Using style sheet
“/usr/share/YaST2/theme/current/wizard/style.qss”
<M> [qt-ui] YQUI.cc:445 calcDefaultSize(): Default size: 800 x 600
<M> [qt-ui] YQUI.cc:275 initUI(): Forcing /usr/lib64/libQtGui.so.4 open successful
<M> [qt-ui] YQApplication.cc:140 loadPredefinedQtTranslations(): Selected
language: en_US
<WRN> [qt-ui] YQApplication.cc:164 loadPredefinedQtTranslations(): Can’t load
translations for predefined Qt dialogs from /usr/share/qt4/translations/qt_en.qm
<M> [qt-ui] YQUI.cc:288 initUI(): YQUI initialized. Thread ID: 0x7fa0767dc720
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YComboBox “Select the driver” at 0x1f3bb98
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YComboBox “Select resolution” at 0x21bec08
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YComboBox “Depth” at 0x6f3f98
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YCheckBox “Enable Advanced Settings” at 0x61c9d8
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YIntField “Horizontal Refresh Rate(min value)” at 0xdaffc8
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YIntField “Horizontal Refresh Rate(max value)” at 0x35103e8
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YIntField “Vertical Refresh Rate(min value)” at 0x15d4028
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YIntField “Vertical Refresh Rate(max value)” at 0x1fa2fe8
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YCheckBox “I want my own CVT” at 0x1e1b068
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YIntField “X Axis” at 0x3546558
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YIntField “Y Axis” at 0x21b6de8
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YIntField “Refresh Rate” at 0x14afec8
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YPushButton “Ok” at 0x3640548
<M> [ui-shortcuts] YShortcutManager.cc:148 checkShortcuts(): No valid shortcut
for YPushButton “Cancel” at 0x6a39d8
/files/etc/X11/xorg.conf.d/50-monitor.conf/Monitor[last()+1]/Identifier[last()]
no error
“1280x768_60.00” 79.50 1280 1344 1472 1664 768 771 781 798 -hsync
+vsync/files/etc/X11/xorg.conf.d/50-monitor.conf/Monitor[last()]/Modeline[last()]
no error
/files/etc/X11/xorg.conf.d/50-device.conf/Device[last()+1]/Identifier[last()]
no error
nouveau/files/etc/X11/xorg.conf.d/50-device.conf/Device[last()]/Driver[last()]
no error
/files/etc/X11/xorg.conf.d/50-screen.conf/Screen[last()+1]/Identifier[last()]
no error
/files/etc/X11/xorg.conf.d/50-screen.conf/Screen[last()]/Device[last()]
no error
/files/etc/X11/xorg.conf.d/50-screen.conf/Screen[last()]/Monitor[last()]
no error
/files/etc/X11/xorg.conf.d/50-screen.conf/Screen[last()]/DefaultDepth[last()]
no error
/files/etc/X11/xorg.conf.d/50-screen.conf/Screen[last()]/Display[last()+1]/Depth
no error
/files/etc/X11/xorg.conf.d/50-screen.conf/Screen[last()]/Display[last()]/Modes
no error
<M> [ui] YUI.cc:529 ~YUITerminator(): Shutting down UI
Segmentation fault

Hey Larry, was that using the same version as Lee is currently testing with ie sax3-0.1-18.1?

On 08/27/2011 05:06 PM, deano ferrari wrote:
>
> Hey Larry, was that using the same version as Lee is currently testing
> with ie sax3-0.1-18.1?

Yes. Sorry for not posting that with the original message.

I will give it a try to build it on 11.3, please try and let me know. It may take a bit of time just that.
It will be available in X11:sax itself as sax3-11.3 most probably 

Ok, thanks. I’ll keep a look out for it. :slight_smile:

manugupt1,

thanks i got mine updated and it seems to have every thing working now on my test system however i do have a question… Is there a way to have the monitor interface section look like the old sax2 as in that version you were able to select if you wanted to use VESA resolutions or monitor specific resolutions and you were able to set exact resolutions in sax with little trouble and with out having to worry about a lot of other items…

again im just wondering

thanx
linux200418