Via Chrome9 resolution problem

giulio_buccini, I asked consused to help here, because frankly I don’t have any experience with this driver, and I feel very inadequate in my recommendations.

In line with consused recommendation, to find drivers in the build service you can search here: Software.openSUSE.org and a search for openchrome will give you this repository:

http://download.opensuse.org/repositories/home:/illuusio:/xorg/openSUSE_11.2/

and you will see this rpm xorg-x11-driver-video-openchrome-0.2.904-4.1.i586.rpm that should be installed AFTER removing both xorg-x11-driver-video-chrome9-5.74.33-2.1.i586 and xorg-x11-driver-video-unichrome-20091020-1.1.1.i586.

My apologies for not being able to help you - and its great to see consused once again lending his expertise!

… further along consused’s recommendation, and looking at the contents of xorg-x11-driver-video-openchrome-0.2.904-4.1.i586.rpm with the command

rpm -qp xorg-x11-driver-video-openchrome-0.2.904-4.1.i586.rpm -l

I see the files

/usr/lib/xorg/modules/updates/drivers/openchrome_drv.la                               
/usr/lib/xorg/modules/updates/drivers/openchrome_drv.so

which leads me to believe “openchrome” is the kernel module/driver. Hence after removing the other chrome rpms and installing the openchrome rpm, I believe you need to try:

sax2 -r -m 0=openchrome

Good luck! … and thanks to consused!

Before all,
thanks consused;
thanks oldcpu.

Having said that, I have:

  1. uninstalled the xorg-x11-driver-video-chrome9 (5.73.23) (using Yast)

  2. uninstalled the xorg-x11-driver-video-unichrome (using Yast)

  3. Disabled the repository containing the chrome9 driver (using Yast)

  4. Added the repository containing the openchrome driver (Index of /repositories/home:/illuusio:/xorg/openSUSE_11.2 - again using Yast)

  5. selected and installed the openchrome driver (using yast)

  6. turned of my pc and started again at level 3

  7. logged in as user and then super user

  8. typed the sax2 -r -m 0=openchrome command

After that, sax2 graphic interface has started (even if I was in normal text mode). The screen was flickering a lot, but I can read options displayed. I have changed nothing and I have pushed the button “Ok” (or “save”, I don’t remember exactly).
After the graphics interface has gone out, I have returned to normal text screen with no errors printed (!!!).

But… I have restarted the system and… nothing has changed! When I run an avi video at fullscreen mode with totem the refresh rate is still frustrating…
I have raised up the colors to 24 bit, but nothing changes… By the way, before “playing” with drivers all video player was working well, but now only Totem runs normally. For the other one I get this messages:

MPlayer:
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory.

Totem:
Error opening/initializating the selected video_ant (-vo) device.

Banshee:
<player run and starts to reproduce video but immediately it stops and terminate>

:open_mouth:

I have a suspect… I have checked the manual of the openchrome driver and I see a lot of options that I can set (for example the “EXA” option). But if I look at the /etc/X11/xorg.conf file I still see my old configuration file! How can this happens? The command sax2 -r -m 0=openchrome has terminated with no error, so why the xorg.conf file has not be modified?

I write here the contents of the xorg.conf file, it seems to me that nothing is changed.

# /.../
# SaX generated X11 config file
# Created on: 2010-02-17T13:27:39+0100.
#
# Version: 8.1
# Contact: Marcus Schaefer <sax@suse.de>, 2005
# Contact: SaX-User list <https://lists.berlios.de/mailman/listinfo/sax-users>
#
# Automatically generated by [ISaX] (8.1)
# PLEASE DO NOT EDIT THIS FILE!
#
Section "Files"
  FontPath     "/usr/share/fonts/misc:unscaled"
  FontPath     "/usr/share/fonts/local"
  FontPath     "/usr/share/fonts/75dpi:unscaled"
  FontPath     "/usr/share/fonts/100dpi:unscaled"
  FontPath     "/usr/share/fonts/Type1"
  FontPath     "/usr/share/fonts/URW"
  FontPath     "/usr/share/fonts/Speedo"
  FontPath     "/usr/share/fonts/PEX"
  FontPath     "/usr/share/fonts/cyrillic"
  FontPath     "/usr/share/fonts/latin2/misc:unscaled"
  FontPath     "/usr/share/fonts/latin2/75dpi:unscaled"
  FontPath     "/usr/share/fonts/latin2/100dpi:unscaled"
  FontPath     "/usr/share/fonts/latin2/Type1"
  FontPath     "/usr/share/fonts/latin7/75dpi:unscaled"
  FontPath     "/usr/share/fonts/baekmuk:unscaled"
  FontPath     "/usr/share/fonts/japanese:unscaled"
  FontPath     "/usr/share/fonts/kwintv"
  FontPath     "/usr/share/fonts/truetype"
  FontPath     "/usr/share/fonts/uni:unscaled"
  FontPath     "/usr/share/fonts/CID"
  FontPath     "/usr/share/fonts/ucs/misc:unscaled"
  FontPath     "/usr/share/fonts/ucs/75dpi:unscaled"
  FontPath     "/usr/share/fonts/ucs/100dpi:unscaled"
  FontPath     "/usr/share/fonts/hellas/misc:unscaled"
  FontPath     "/usr/share/fonts/hellas/75dpi:unscaled"
  FontPath     "/usr/share/fonts/hellas/100dpi:unscaled"
  FontPath     "/usr/share/fonts/hellas/Type1"
  FontPath     "/usr/share/fonts/misc/sgi:unscaled"
  FontPath     "/usr/share/fonts/xtest"
  FontPath     "/opt/kde3/share/fonts"
  InputDevices "/dev/gpmdata"
  InputDevices "/dev/input/mice"
EndSection

Section "ServerFlags"
  Option       "AllowMouseOpenFail" "on"
  Option       "ZapWarning" "on"
EndSection

Section "Module"
  Load         "dbe"
  Load         "glx"
  Load         "dri"
  Load         "extmod"
EndSection

Section "InputDevice"
  # Driver "kbd" will be disabled unless 'Option "AutoAddDevices" "off"' 
  # is set in "ServerFlags" section. 
  Driver       "kbd"
  Identifier   "Keyboard[0]"
  Option       "Protocol" "Standard"
  Option       "XkbLayout" "it"
  Option       "XkbModel" "microsoftpro"
  Option       "XkbRules" "xfree86"
EndSection

Section "InputDevice"
  # Driver "mouse" will be disabled unless 'Option "AutoAddDevices" "off"' 
  # is set in "ServerFlags" section. 
  Driver       "mouse"
  Identifier   "Mouse[1]"
  Option       "Buttons" "9"
  Option       "Device" "/dev/input/mice"
  Option       "Name" "ImExPS/2 Logitech Explorer Mouse"
  Option       "Protocol" "explorerps/2"
  Option       "Vendor" "Sysp"
  Option       "ZAxisMapping" "4 5"
EndSection

Section "Monitor"
  Option       "CalcAlgorithm" "XServerPool"
  DisplaySize  376 301
  HorizSync    30-81
  Identifier   "Monitor[0]"
  ModelName    "NEC LCD93V"
  Option       "DPMS"
  Option       "PreferredMode" "1280x960"
  VendorName   "NEC"
  VertRefresh  43-75
  UseModes     "Modes[0]"
EndSection

Section "Modes"
  Identifier   "Modes[0]"
  Modeline 	"1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +HSync +VSync
EndSection

Section "Screen"
  SubSection "Display"
    Depth      15
    Modes      "default" 
  EndSubSection
  SubSection "Display"
    Depth      16
    Modes      "default" 
  EndSubSection
  SubSection "Display"
    Depth      24
    Modes      "default" 
  EndSubSection
  SubSection "Display"
    Depth      8
    Modes      "default" 
  EndSubSection
  Device       "Device[0]"
  Identifier   "Screen[0]"
  Monitor      "Monitor[0]"
EndSection

Section "Device"
  BoardName    "Framebuffer Graphics"
  Driver       "fbdev"
  Identifier   "Device[0]"
  Screen       0
  VendorName   "VESA"
EndSection

Section "ServerLayout"
  Identifier   "Layout[all]"
  InputDevice  "Keyboard[0]" "CoreKeyboard"
  InputDevice  "Mouse[1]" "CorePointer"
  Option       "Clone" "off"
  Option       "Xinerama" "off"
  Screen       "Screen[0]"
EndSection

Section "DRI"
    Group      "video"
    Mode       0660
EndSection

Section "Extensions"
EndSection

Note: my NEC monitor is correctly detected.

Well done with your methodical approach this far. I believe you are now in better shape despite the problems with Sax2. The next step will be to manually edit and correct your “xorg.conf”.

I am not sure what Sax2 is doing with the new 11.2, but it is on its way out. On my recent failure with chrome9, I used the above command as you did. X was not started normally and the test screen came up. When I tried to save the new configuration of sax2, it overwrote my xorg.conf with a poorly configured one of it’s own. On restoring my original config.sys set up for openchrome, I had a working system again, I think you are now better placed, having the chance to update your existing one manually.

So let’s look at your xorg.conf. I only repeat here the sections that need alteration or comment/question. Be very careful when you edit them, and take a backup copy of xorg.conf file before you begin the editing.

Section "Monitor"
  Option       "CalcAlgorithm" "XServerPool"
  DisplaySize  376 301
  HorizSync    30-81
  Identifier   "Monitor[0]"
  ModelName    "NEC LCD93V"
  Option       "DPMS"
  Option       "PreferredMode" "1280x960"
  VendorName   "NEC"
  VertRefresh  43-75
  UseModes     "Modes[0]"
EndSection

Question: The monitor section contains preferred mode “1280x960”. Is that the resolution you want? Or is it “1280x1024” as given in the Modes section that follows?

If you don’t want 1280x1024, I suggest you let the X system choose a display mode, that can be changed later if unsatisfactory, and you comment-out that modeline by placing “#” at the start as I have done here:

Section "Modes"
  Identifier   "Modes[0]"
#  Modeline 	"1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +HSync +VSync
EndSection

In the Screen section that follows, you may replace those “default” settings with your preferred resolutions but leave it as “default” for now. That way you should get all the resolutions that X believes are valid for your monitor (that’s the theory anyway).

Section "Screen"
  SubSection "Display"
    Depth      15
    Modes      "default" 
  EndSubSection
  SubSection "Display"
    Depth      16
    Modes      "default" 
  EndSubSection
  SubSection "Display"
    Depth      24
    Modes      "default" 
  EndSubSection
  SubSection "Display"
    Depth      8
    Modes      "default" 
  EndSubSection
  Device       "Device[0]"
  Identifier   "Screen[0]"
  Monitor      "Monitor[0]"
EndSection

Now this is the main driver control section. The only parameter you must change is the Driver name to “openchrome”. I have included other changes but they are only cosmetic. Later we may need to introduce driver option parameters into this section as documented in the man/openchrome page. Let’s keep it simple for the next attempt at least.

Section "Device"
  BoardName    "K8M890"
  Driver       "openchrome"
  Identifier   "Device[0]"
  Screen       0
  VendorName   "VIA"
EndSection

I suggest for now you leave the Mode statement in the next section as 0660. For direct rendering and 3D you will need to change it to 0666, but for the K8M890 3D may not work or crash, so leave it for now. Instead, you should get s/w rendering albeit slower.

Section "DRI"
    Group      "video"
    Mode       0660
EndSection

Make those changes carefully to xorg.conf, save and reboot. Good luck, and let us know how you get on with that. :wink:

I meant to add that nowadays you shouldn’t need to specify a modeline in the config.sys, so I would comment-out the line as shown in my post above.

Sorry, the word “that” which got added to the Driver statement above during my posting/editing shouldn’t be there! Please don’t include it.

Thank you for suggested modifications of the xorg.conf file. I will make a backup of it and I will try.

By the way, my preferred screen resolution is 1280x1024 (the one running now), I don’t know way in the “Monitor” section there is a different value.

Now I’m busy, but I will try it in a couple of hour and I will post results.

I will do the “experiment” tomorrow, now is a little bit late for me. Anyway, I would to say thanks to all of the people that are helping me to solve this problem.
Unfortunately, in this moment, I have not so many money available for buying a new video card. I must put big attention in every euro I spend everyday. So, again thanks. :slight_smile:

@giulio, I understand your motivation. Take your time, the forum will still be here, and hopefully we will get a good enough result. I have managed to keep my Via chipset useable with openSUSE for several years by swapping drivers to work around the issues that come with ongoing development. :wink:

Hello consused
IT WORKS !!!

I’m an happy man now! <:)

I have update the xorg.conf file following your istructions. More exactly I have modifed ony the “Device” section of the file with your parameters. For what is concerning the “Modes” section, I left everything as it was 'cause the 1028x1024 resolution is my preferred one.

Not all as gone ok at the first shot. After modifying and rebooting the system, the screen has splashed out with a very high resolution. This is very strange. The screen area was not centered in the monitor and the lower bar of the Gnome desktop was not completely visible.
Anyway, I have immediately started one terminal window and I’ve started the Sax2 program. Sax2 reported me what follows:

resolution = 1400x1050(SXGA+)
color = 24 bit.

So, I have lowered resolution to 1280x1024 and I leaved the color depth to 24 bit.
After rebooting again everything was working fine: screen is centered in the monitor and the resolution is the one I want. Finally, I’ve started the Totem video player on an AVI movie and… tadaaaaaa! No more slow refresh at fullscreen mode! WOW! Simply perfect! :slight_smile:

What can I say more? Thanks!
Obviously, you and oldcpu have both a big big weiss-bier payed here in Munich (Germany).

Do you think that I should post here an history of the solving process for other openSUSE users than me?

I don’t know the reason for what MPlayer and Banshee program stopped to work (see my previous post above), only the Totem player is working now. But I think is depending on different reasons than the video card.
More important, now my wife can watch her preferred movies on Linux. One more user has left Win…:X for Linux.

Mission accomplished rotfl!

Note: do you think that I should try to enable 3D rendering by inserting the “Mode” value to 0666 as you wrote?

Section "DRI"
    Group      "video"
    Mode       0660
EndSection

If video crash, I will able to restart the system at level 3 (Text mode) and restore old values?

Excellent news. Your success on openSUSE is our reward, but thanks for the weiss-bier. :slight_smile:

After modifying and rebooting the system, the screen has splashed out with a very high resolution. This is very strange. The screen area was not centered in the monitor and the lower bar of the Gnome desktop was not completely visible.

Not so strange. The X system will go through all possible resolution and refresh rate modes within parameters defined by your monitor definitions in xorg.conf. If your chip supports free modes (as opposed to fixed modes), the openchrome driver can deliver many free modes to the monitor. Some of those may not display in a practicable way. I use 1280x1024 with no modelines in xorg.conf, but I can display 1600x1200, and X delivers higher resolutions than that which display badly. You can follow this process and the progress of your driver loading and setting up in the X system log in the file /var/log/Xorg.0.log which is overwritten at every startup.

I use this section in xorg.conf to select display resolutions, for example:

Section "Screen"
  SubSection "Display"
    Depth      15
    Modes      "1280x1024" "1024x768" 
  EndSubSection
  SubSection "Display"
    Depth      16
    Modes      "1280x1024" "1024x768" 
  EndSubSection
  SubSection "Display"
    Depth      24
    Modes      "1280x1024" "1024x768"
  EndSubSection
  SubSection "Display"
    Depth      8
    Modes      "1280x1024" "1024x768" 
  EndSubSection
  Device       "Device[0]"
  Identifier   "Screen[0]"
  Monitor      "Monitor[0]"
EndSection 

Note: Just leave out the higher resolutions that you do not want.

Do you think that I should post here an history of the solving process for other openSUSE users than me?
I wouldn’t worry about that, no two problems are exactly the same. Others can search and follow this thread. Keep a note of the process for yourself in future and then you can help others with similar problems. Spend the time now to enjoy your new system.

Besides, there are some unanswered issues with the behaviour of sax2 during the solving process. On issuing the command: sax2 -r -m 0=openchrome, why did it not overwrite your xorg.conf? It did on mine. Your on Gnome, I’m on KDE, so does Yast and/or sax2 behave slightly differently on those DE’s? Secondly, when you last changed your display resolution, presumably using sax2, did it update your xorg.conf i.e. the monitor section? Or did it overwrite xorg.conf with a totally new one? Hmm, once I have a working xorg.conf for openchrome, I never save using sax2 as it tends to ruin it. BTW, just a reminder to always keep a backup copy of your working xorg.conf.

I don’t know the reason for what MPlayer and Banshee program stopped to work (see my previous post above), only the Totem player is working now. But I think is depending on different reasons than the video card.
I don’t use Banshee, but MPlayer and SMPlayer (both from Packman repo) works on my KDE system running openchrome. It may have something to do with XvMC on your card, but I’m only guessing. You should start another thread in Applications for help on those, I think.

Note: do you think that I should try to enable 3D rendering by inserting the “Mode” value to 0666 as you wrote?

Section "DRI"
    Group      "video"
    Mode       0660
EndSection

If video crash, I will able to restart the system at level 3 (Text mode) and restore old values?
I would say don’t, as 3D acceleration for your chip is not implemented. Have a look at what it says about your card in openchrome’s support matrix page. Also note the comment there about XV and EXA!

At some point in the future you should try a knew version of chrome9 when it arrives. Bear in mind that I don’t believe it has 3D working on anything so far.

Well done on your success and for persevering with the problem.

IMHO this is either a Packman packing glitch or an rpm installation glitch. I see this error too on one of my one PCs (with a nVidia GeForce FX5200) where that graphic card does not have vdpau. My other two nVidia PCs (which do have vdpau) do not have the mplayer vdpau error problem.

I also find the Packman packaged libxine1 (replacing the Novell/SuSE-GmbH libxine1) works very well. You can use either xine-ui or kaffeine as a front end to xine.

Also the player “vlc” is pretty good.

Many thanks to consused for his help. Without that, I fear we would have failed.

Hello consused,

thanks for your succestions about resolutions settings, but I think that, for now, I will not touch the xorg.conf file anymore.

I have checked your table reporting basic charateristics for every chipset, and I agree with you: my chipset doesn’t support 3d acceleration. So I will not touch the “mode” parameter in the “DRI” section.

I’ve solved all my video problems by installing the SMPlayer and discharging Banshee.

I really don’t know why the sax2 command has not modified the xorg.conf file… it’s a mystery… Anyway, I have 2 copies of the xorg.conf file. One is previous to entering the command sax2 -r -m 0=openchrome and the other one is previous to modifying the file manually following your suggestion.
I want be sure that the sax2 has not introduced modification. About this, I remember that is available a linux-command to check difference between two files. Do you remember it? In this way I can be sure if the sax2 command has introduced some modifications or not.

@giulio, that’s all fine. I agree with oldcpu concerning libxine1 (packman repo). In fact I use kaffeine as front-end to xine, particularly for playing dvd’s. It works well with openchrome.

There should be the command diff for comparing two files line by line. I haven’t used it recently enough to remember the options, so you need to check the manpage with man diff.

Hello consused,

I’ve runned the diff command as below:

diff -E -b -w -a -B -y <file A> <file B>

where file A is the xorg.conf file before running the sax2 -r -m 0=openchrome command, and the file B is the file obtained after running it.

Below is reported the output. In the left column there are the contents of file A, to the right the contents of the file B.

Diff command uses this symbols (as I understand):

“<” is present in A but not in B,
“>” is present in B but not in A,
“)” content is present in B but at different line (but I’m not sure of this…)
“|” I really don’t know the meaning of this symbol…

# /.../								# /.../
# SaX generated X11 config file					# SaX generated X11 config file
# Created on: 2009-07-13T16:15:11+0200.			      |	# Created on: 2010-02-17T14:24:43+0100.
#								#
# Version: 8.1							# Version: 8.1
# Contact: Marcus Schaefer <sax@suse.de>, 2005			# Contact: Marcus Schaefer <sax@suse.de>, 2005
# Contact: SaX-User list <https://lists.berlios.de/mailman/li	# Contact: SaX-User list <https://lists.berlios.de/mailman/li
#								#
# Automatically generated by [ISaX] (8.1)			# Automatically generated by [ISaX] (8.1)
# PLEASE DO NOT EDIT THIS FILE!					# PLEASE DO NOT EDIT THIS FILE!
#								#
Section "Files"
  FontPath     "/usr/share/fonts/misc:unscaled"			Section "Files"
  FontPath     "/usr/share/fonts/local"				  FontPath     "/usr/share/fonts/misc:unscaled"
  FontPath     "/usr/share/fonts/75dpi:unscaled"		  FontPath     "/usr/share/fonts/local"
  FontPath     "/usr/share/fonts/100dpi:unscaled"		  FontPath     "/usr/share/fonts/75dpi:unscaled"
  FontPath     "/usr/share/fonts/Type1"				  FontPath     "/usr/share/fonts/100dpi:unscaled"
  FontPath     "/usr/share/fonts/URW"				  FontPath     "/usr/share/fonts/Type1"
  FontPath     "/usr/share/fonts/Speedo"			  FontPath     "/usr/share/fonts/URW"
  FontPath     "/usr/share/fonts/PEX"				  FontPath     "/usr/share/fonts/Speedo"
  FontPath     "/usr/share/fonts/cyrillic"			  FontPath     "/usr/share/fonts/PEX"
  FontPath     "/usr/share/fonts/latin2/misc:unscaled"		  FontPath     "/usr/share/fonts/cyrillic"
  FontPath     "/usr/share/fonts/latin2/75dpi:unscaled"		  FontPath     "/usr/share/fonts/latin2/misc:unscaled"
  FontPath     "/usr/share/fonts/latin2/100dpi:unscaled"	  FontPath     "/usr/share/fonts/latin2/75dpi:unscaled"
  FontPath     "/usr/share/fonts/latin2/Type1"			  FontPath     "/usr/share/fonts/latin2/100dpi:unscaled"
  FontPath     "/usr/share/fonts/latin7/75dpi:unscaled"		  FontPath     "/usr/share/fonts/latin2/Type1"
  FontPath     "/usr/share/fonts/baekmuk:unscaled"		  FontPath     "/usr/share/fonts/latin7/75dpi:unscaled"
  FontPath     "/usr/share/fonts/japanese:unscaled"		  FontPath     "/usr/share/fonts/baekmuk:unscaled"
  FontPath     "/usr/share/fonts/kwintv"			  FontPath     "/usr/share/fonts/japanese:unscaled"
  FontPath     "/usr/share/fonts/truetype"			  FontPath     "/usr/share/fonts/kwintv"
  FontPath     "/usr/share/fonts/uni:unscaled"			  FontPath     "/usr/share/fonts/truetype"
  FontPath     "/usr/share/fonts/CID"				  FontPath     "/usr/share/fonts/uni:unscaled"
  FontPath     "/usr/share/fonts/ucs/misc:unscaled"		  FontPath     "/usr/share/fonts/CID"
  FontPath     "/usr/share/fonts/ucs/75dpi:unscaled"		  FontPath     "/usr/share/fonts/ucs/misc:unscaled"
  FontPath     "/usr/share/fonts/ucs/100dpi:unscaled"		  FontPath     "/usr/share/fonts/ucs/75dpi:unscaled"
  FontPath     "/usr/share/fonts/hellas/misc:unscaled"		  FontPath     "/usr/share/fonts/ucs/100dpi:unscaled"
  FontPath     "/usr/share/fonts/hellas/75dpi:unscaled"		  FontPath     "/usr/share/fonts/hellas/misc:unscaled"
  FontPath     "/usr/share/fonts/hellas/100dpi:unscaled"	  FontPath     "/usr/share/fonts/hellas/75dpi:unscaled"
  FontPath     "/usr/share/fonts/hellas/Type1"			  FontPath     "/usr/share/fonts/hellas/100dpi:unscaled"
  FontPath     "/usr/share/fonts/misc/sgi:unscaled"		  FontPath     "/usr/share/fonts/hellas/Type1"
  FontPath     "/usr/share/fonts/xtest"				  FontPath     "/usr/share/fonts/misc/sgi:unscaled"
  FontPath     "/opt/kde3/share/fonts"				  FontPath     "/usr/share/fonts/xtest"
  InputDevices "/dev/gpmdata"					  FontPath     "/opt/kde3/share/fonts"
  InputDevices "/dev/input/mice"				  InputDevices "/dev/gpmdata"
EndSection							  InputDevices "/dev/input/mice"
								EndSection
Section "ServerFlags"
							      )	Section "ServerFlags"
  # Uncomment the following option to reenable kbd/mouse driv <
  # Otherwise evdev driver is used. 			      <
  #Option       "AutoAddDevices" "off"			      <
  Option       "AllowMouseOpenFail" "on"			  Option       "AllowMouseOpenFail" "on"
  Option       "ZapWarning" "on"				  Option       "ZapWarning" "on"
EndSection							EndSection

Section "Module"						Section "Module"
  Load         "glx"						  Load         "glx"
  Load         "dbe"					      <
  Load         "extmod"						  Load         "extmod"
							      >	  Load         "dbe"
  Load         "dri"						  Load         "dri"
  Load         "freetype"				      <
EndSection							EndSection

Section "InputDevice"						Section "InputDevice"
							      >	  # Driver "kbd" will be disabled unless 'Option "AutoAddDevi
							      >	  # is set in "ServerFlags" section. 
  Driver       "kbd"						  Driver       "kbd"
  Identifier   "Keyboard[0]"					  Identifier   "Keyboard[0]"
  Option       "Protocol" "Standard"				  Option       "Protocol" "Standard"
  Option       "XkbLayout" "it"					  Option       "XkbLayout" "it"
  Option       "XkbModel" "microsoftpro"			  Option       "XkbModel" "microsoftpro"
  Option       "XkbRules" "xfree86"				  Option       "XkbRules" "xfree86"
EndSection							EndSection

Section "InputDevice"
							      )	Section "InputDevice"
							      >	  # Driver "mouse" will be disabled unless 'Option "AutoAddDe
							      >	  # is set in "ServerFlags" section. 
  Driver       "mouse"						  Driver       "mouse"
  Identifier   "Mouse[1]"					  Identifier   "Mouse[1]"
  Option       "Buttons" "9"					  Option       "Buttons" "9"
  Option       "Device" "/dev/input/mice"			  Option       "Device" "/dev/input/mice"
  Option       "Name" "ImExPS/2 Logitech Explorer Mouse"	  Option       "Name" "ImExPS/2 Logitech Explorer Mouse"
  Option       "Protocol" "explorerps/2"			  Option       "Protocol" "explorerps/2"
  Option       "Vendor" "Sysp"					  Option       "Vendor" "Sysp"
  Option       "ZAxisMapping" "4 5"				  Option       "ZAxisMapping" "4 5"
EndSection							EndSection

Section "Monitor"
  Option       "CalcAlgorithm" "XServerPool"			Section "Monitor"
  DisplaySize  376 301						  Option       "CalcAlgorithm" "XServerPool"
  HorizSync    30-81						  DisplaySize  376 301
  Identifier   "Monitor[0]"					  HorizSync    30-81
  ModelName    "NEC LCD93V"					  Identifier   "Monitor[0]"
  Option       "DPMS"						  ModelName    "NEC LCD93V"
  Option       "PreferredMode" "1280x960"			  Option       "DPMS"
  VendorName   "NEC"						  Option       "PreferredMode" "1280x960"
  VertRefresh  43-75						  VendorName   "NEC"
  UseModes     "Modes[0]"					  VertRefresh  43-75
EndSection							  UseModes     "Modes[0]"
								EndSection
Section "Modes"
  Identifier   "Modes[0]"
							      )	Section "Modes"
							      )	  Identifier   "Modes[0]"
  Modeline 	"1280x1024" 108.00 1280 1328 1440 1688 1024 1 |	  Modeline 	"1280x1024" 108 1280 1328 1440 1688 1024 1025
EndSection							EndSection

Section "Screen"
  SubSection "Display"						Section "Screen"
    Depth      15						  SubSection "Display"
    Modes      "default" 					    Depth      15
  EndSubSection							    Modes      "default" 
  SubSection "Display"						  EndSubSection
    Depth      16						  SubSection "Display"
    Modes      "default" 					    Depth      16
  EndSubSection							    Modes      "default" 
  SubSection "Display"						  EndSubSection
    Depth      24						  SubSection "Display"
    Modes      "default" 					    Depth      24
  EndSubSection							    Modes      "default" 
  SubSection "Display"						  EndSubSection
    Depth      8						  SubSection "Display"
    Modes      "default" 					    Depth      8
  EndSubSection							    Modes      "default" 
  Device       "Device[0]"					  EndSubSection
  Identifier   "Screen[0]"					  Device       "Device[0]"
  Monitor      "Monitor[0]"					  Identifier   "Screen[0]"
EndSection							  Monitor      "Monitor[0]"
								EndSection
Section "Device"
  BoardName    "Framebuffer Graphics"
  Driver       "fbdev"						Section "Device"
  Identifier   "Device[0]"					  BoardName    "Framebuffer Graphics"
  Screen       0						  Driver       "fbdev"
  VendorName   "VESA"						  Identifier   "Device[0]"
EndSection							  Screen       0
								  VendorName   "VESA"
Section "ServerLayout"						EndSection
  Identifier   "Layout[all]"
  InputDevice  "Keyboard[0]" "CoreKeyboard"
  InputDevice  "Mouse[1]" "CorePointer"
  Option       "Clone" "off"					Section "ServerLayout"
  Option       "Xinerama" "off"					  Identifier   "Layout[all]"
  Screen       "Screen[0]"					  InputDevice  "Keyboard[0]" "CoreKeyboard"
EndSection							  InputDevice  "Mouse[1]" "CorePointer"
								  Option       "Clone" "off"
Section "DRI"							  Option       "Xinerama" "off"
    Group      "video"						  Screen       "Screen[0]"
    Mode       0660						EndSection
EndSection

Section "Extensions"						Section "DRI"
EndSection							    Group      "video"
								    Mode       0660
							      )	EndSection
							      )
							      )	Section "Extensions"
							      )	EndSection
							      )
						      )

Anyway, as you can see, only little things are changed after executing the rpm command, only some comments was added (column right).
Sections “Monitor”, “Device”, “Modes” are untouched. This is the definitive confirmation that sax2 command doesn’t works as thinked/expected at all.
As I understand, the command should activate some “hardware autodetecting” mechanism, but this doesn’t happens.

Section "Device"
  BoardName    "Framebuffer Graphics"
  Driver       "fbdev"						Section "Device"
  Identifier   "Device[0]"					  BoardName    "Framebuffer Graphics"
  Screen       0						  Driver       "fbdev"
  VendorName   "VESA"						  Identifier   "Device[0]"
EndSection							  Screen       0
								  VendorName   "VESA"
						EndSection

I confess to not knowing hardly anything about this, but in both places is that not the “fbdev” driver that is being used and not the “openchrome” driver?

Did not consused ask to change that to:

Section "Device"
  BoardName    "K8M890"
  Driver       "openchrome" 
  Identifier   "Device[0]"
  Screen       0
  VendorName   "VIA"
EndSection

or am I misreading this?

Yes, yes oldcpu, you’re right.

This is only a further investigation, now the xorg.conf contains the command that you have specified.

But we (I and consused) want to know why, after the first execution of the command sax2 -r -m 0=openchrome, the xorg.conf file was not modified to use the openchrome driver.

Why the sax2 command as not worked as expected? :disapointed:
Why the xorg.conf must be edited manually? :disapointed:

Maybe we will never know the reason, I have only posted the proof that the command sax2 is not working well. That’s all.

I hope that now is all more clear for you.

I’m glad you explained that, as on first scan of your diff output, I read it with the same concern as oldcpu. :\ Anyway, I may have a possible explanation.

When you issue the sax2 command for openchrome, sax2 doesn’t know about “openchrome” so when it detects the Via chip it loads the default driver “fbdev” that works on most h/w. Chrome9 as of January (changelog) is no longer loaded as the default driver for Via chip. Neither is the “unichrome” driver loaded as default (and it doesn’t support K8M890 yet).

I note that “openchrome” driver files are installed into /usr/lib/xorg/modules/updates/drivers, whereas all the other X11 drivers are installed into /usr/lib/xorg/modules/drivers, e.g. “fbdev”, “unichrome”, “via” (chrome9), and “vesa”.

I tested the “unichrome” driver today, and it works on my K8M800 chip. Tomorrow I will try to switch to “unichrome” using the sax2 command. If it works, that will support my theory about “openchrome”. If it doesn’t work, then it will probably default to “fbdev” and the command is useless, at least for Via chips. Will report back here after the test. :slight_smile:

BTW, I tried chrome9 on my 11.1 partition today. It failed immediately as it did on 11.2, and Xorg.0.log contained this error soon after the module is loaded:

(II) Primary Device is: PCI 01@00:00:0
(EE) No devices detected.

Fatal server error:
no screens found

Looks like a serious and fundamental driver bug to me.lol! No, it’s really :(.

giulio_buccini & consused, you two are great ! Many thanks for investigating this. :slight_smile:

Having now done several repeated tests, I confirm that this part of my speculation is not true, on my 11.2 KDE4 system. I tested on a stable system, but not on a freshly installed system where a default driver had been auto loaded. It’s quite clear that sax2 correctly detects my K8M800 chip and loads the driver named in the command: sax2 -r -m 0=drivername, every time. Full marks to the 11.2 developers, because they have removed some of those annoying little bugs. At long last, the sax2 generated xorg.conf gives me practicable modelines and valid resolutions. The only change I needed to make drivername can be made using the above sax2 command. I did not include the “vesa” driver in the testing.

I normally use the console on F1 as root for switching between runlevels 3/5, to swap drivers on a running system. I tested “fbdev”; “unichrome”; “openchrome”; and chrome9(“via”). Using the above sax2 command, I switched between each driver, allowing sax2 to initially overwrite my manually updated xorg.conf and subsequently to overwrite its own generated xorg.conf. To be certain, I repeated the tests with the method outlined by oldcpu, involving a reboot and runlevel change using grub. The results were the same for both methods, and were checked by examining xorg.conf and Xorg.0.log after each switch. In fact these checks led me to uncover a potential problem when installing both “unichrome” and chrome9 (“via”) on the same system - see below.

Results: In every test, sax2 performed consistently, switching the driver and producing an updated xorg.conf with only the driver name changed, except for “fbdev” which generated no modelines in its xorg.conf and chrome9 that failed with its fatal error. Chrome9 did not result in updated xorg.conf.

In runlevel 3 on every test, the sax2 command (see above) resulted in a test screen with options: Change Configuration; Ok; and Cancel. I selected “Ok” in every case to accept sax2’s suggestion, except with chrome9 which didn’t get that far due to its fatal error.

I couldn’t reproduce giulio_buccini’s problem of no xorg.conf update by sax2 on switching to openchrome. However, I am not running Gnome.

I note that “openchrome” driver files are installed into /usr/lib/xorg/modules/updates/drivers, whereas all the other X11 drivers are installed into /usr/lib/xorg/modules/drivers, e.g. “fbdev”, “unichrome”, “via” (chrome9), and “vesa”.

Bear in mind that unichrome is included in the distro release, whereas chrome9 and openchrome come from the Build Service. Just to confuse matters further, the unichrome package installs two copies of its driver files into the drivers directory. You can see it with Yast’s display of the rpm’s installed files list. One named “unichrome” and one named “via”, but both are named “unichrome” in Xorg.0.log when switched into use. Yes you guessed it! Potential for conflict with chrome9(“via”). Aargh :O. If unichrome gets re-installed after chrome9, which is what happened to me, you think you are running chrome9(“via”) when you are actually running unichrome(“via”). I had to rerun all my tests involving chrome9 due to unexpected results. Not seen that packaging done on any distro I’ve used with these drivers during 2-3 years. Someone didn’t think that one through for the users. :frowning: