[opensuse-factory] Removal of SaX2
I see where SaX2 has been removed from M3/GNOME. As this has been the standard way to resolve video card issues, what will be taking its place? Is there a better way to go about this? Jon -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2010/03/17 22:43 (GMT-0500) Jon Cosby composed:
I see where SaX2 has been removed from M3/GNOME. As this has been the standard way to resolve video card issues, what will be taking its place? Is there a better way to go about this?
SaX2 retirement is basically a management cost/benefit decision, a bean counter cutback. Novell won't be devoting time to its support any longer, but has announced it's open to continuation if someone volunteers keep it working as xorg continues to evolve. Scratch one of the last two major openSUSE features that makes it better than other distros. All that's left now is YaST, and inertia. :-( The goal of the upstream Xorg devs is making everything X automatic, which with common modern hardware, works in most cases. I can't imagine how multihead/multigfxcard/multidisplay configs could possibly be automatic. Also, automatic depends on hardware characteristics performing according to X dev expectations, which will never be 100%. X -configure is built into upstream X for building a skeleton xorg.conf. It's crude, and not interactive, but better than nothing for those whose hardware malfunctions under automatic assumptions. Oh, and don't try X -configure if you're running Factory: http://bugzilla.novell.com/show_bug.cgi?id=586053 For a while, most can probably get by using an xorg.conf from an earlier release, such as 11.2. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Torsdag den 18. marts 2010 05:21:30 skrev Felix Miata:
On 2010/03/17 22:43 (GMT-0500) Jon Cosby composed:
I see where SaX2 has been removed from M3/GNOME. As this has been the standard way to resolve video card issues, what will be taking its place? Is there a better way to go about this?
The goal of the upstream Xorg devs is making everything X automatic, which with common modern hardware, works in most cases. I can't imagine how multihead/multigfxcard/multidisplay configs could possibly be automatic. Also, automatic depends on hardware characteristics performing according to X dev expectations, which will never be 100%.
X -configure is built into upstream X for building a skeleton xorg.conf. It's crude, and not interactive, but better than nothing for those whose hardware malfunctions under automatic assumptions. Oh, and don't try X -configure if you're running Factory: http://bugzilla.novell.com/show_bug.cgi?id=586053 For a while, most can probably get by using an xorg.conf from an earlier release, such as 11.2.
Depending on your video card and driver you have nvidia-settings, some ati control center, krandrtray/gnome-xrandr-thingy etc. providing gui alternatives to sax2. So you have other options than automation or handwritten xorg.conf. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Well what used to work doesn't anymore. I have a AGP2 Asus motherboard with a NVidia GForce 7600 AGP2 card. It is no longer being setup at boot time. I have for years used VGA=0x346 to get a 21 inch monitor to have a nice screen. It works in X but not in a console (tty#). It now is not being seen as VESA settings and is only spotted as a VGA card. I have looked at "hwinfo --gfxcard" and hwinfo states the card correctly but doesn't call the correct modules. hwinfo states I need modprobe neuneau and nvidiafb modules. However, they must not be loaded at boot time and therefore, I am getting a black screen and with VGA=(a selection) I get a 21 inch monitor with a 640x480 screen. As I fixed my printer problem by writing a udev rule I guess the video is not found for the same reason. Are there any plans to write a rule for every video card? SaX2 always worked.
The goal of the upstream Xorg devs is making everything X automatic, which with common modern hardware, works in most cases. I can't imagine how multihead/multigfxcard/multidisplay configs could possibly be automatic. Also, automatic depends on hardware characteristics performing according to X dev expectations, which will never be 100%.
Depending on your video card and driver you have nvidia-settings, some ati control center, krandrtray/gnome-xrandr-thingy etc. providing gui alternatives to sax2. So you have other options than automation or handwritten xorg.conf.
-- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb@comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb@arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2010/03/18 08:55 (GMT-0500) Donn Washburn composed:
Well what used to work doesn't anymore. I have a AGP2 Asus motherboard with a NVidia GForce 7600 AGP2 card. It is no longer being setup at boot time. I have for years used VGA=0x346 to get a 21 inch monitor to have a nice screen. It works in X but not in a console (tty#). It now is not being seen as VESA settings and is only spotted as a VGA card. I have looked at "hwinfo --gfxcard" and hwinfo states the card correctly but doesn't call the correct modules. hwinfo states I need modprobe neuneau and nvidiafb modules. However, they must not be loaded at boot time and therefore, I am getting a black screen and with VGA=(a selection) I get a 21 inch monitor with a 640x480 screen.
So which is it? Black screen if you use vga=somethingorother? Black screen if you don't use vga=somethingorother? SaX2 never had anything to do with tty mode. Take a look at http://wiki.debian.org/XStrikeForce/HowToRandR12 to see how the current Xorg versions differ from what used to be and what keeping SaX2 supported might entail. For your ttys, try on cmdline instead of vga=0x346 something like video="VGA1:1600x1200@75" or whatever xrandr shows as the name of the video output port you're using. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, 18 Mar 2010 11:40:54 +0100, Martin Schlander
Depending on your video card and driver you have nvidia-settings, some ati control center, krandrtray/gnome-xrandr-thingy etc. providing gui alternatives to sax2. So you have other options than automation or handwritten xorg.conf.
I'm sure there will nice and flashy GUIs in its place, but when the X server session fails, sax2 in text mode is almost 100% reliable. What will take its place here? Jon -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Mar 18, 2010 at 17:42, Jon Cosby
I'm sure there will nice and flashy GUIs in its place, but when the X server session fails, sax2 in text mode is almost 100% reliable. What will take its place here?
I think you're still thinking in terms of what sax2 did for you when it was relevant.. sax2 in text mode was great for sorting out a borked xorg.xconf file... but in the "new" way of working there is no xorg.conf... things are detected at boot.... and that's it. If you've hand generated your xorg.conf due to some odd or exotic hardware combination or other special needs... then if X fails, you sort it out at the terminal by tweaking your hand generated xorg.conf. To be honest... I'm kind of glad I don't have to deal with sax2 anymore. The new autodetect is working perfect (for me and for everyone I help and support with openSUSE across various laptop and desktop configs) with multiple monitors, with single monitors.. with displays with odd resolutions... with beamers/overhead projectors... with every display device that I've connected so far. I'm sure I'll eventually stumble on one that doesn't work... but that hasn't happened yet. Same goes for mice... and keyboards... everything that was in the xorg.conf is actually... for all hardware I've worked on... works better now than with sax2 and xorg.conf. C. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/18/2010 12:21 AM, Felix Miata wrote:
The goal of the upstream Xorg devs is making everything X automatic, which with common modern hardware, works in most cases. I can't imagine how multihead/multigfxcard/multidisplay configs could possibly be automatic. Also, automatic depends on hardware characteristics performing according to X dev expectations, which will never be 100%.
FWIW, dual head works fine without an Xorg.conf on my T60p. Not automatically; it starts in clone mode. Once I log in the gnome display tool sets everything up for me. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkuiNxUACgkQLPWxlyuTD7IgJQCfRxINSFGe367uTTSVAILrAwEv UlcAnA4oX6UHmE9lQ2JCXUh0WWJOof7h =xuu5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (6)
-
C
-
Donn Washburn
-
Felix Miata
-
Jeff Mahoney
-
Jon Cosby
-
Martin Schlander