[opensuse] Opensuse 11.2, KDE4 Factory:, yast
HI Anyone know why Sax2 is no longer in Yast? Or is there another way to find out about your graphics card, its driver version etc (apart from the "Hardware" probe option in Yast). Should something like Sax2 be apart of the Advanced section of "System Settings"? My preferred option would be when all options related to a device e.g. display, are accessible from a single point as well as being distributed in other places such as Yast. For example,for me its the logical thing to have all display related options in one place whether it be a theme change, driver change etc and all advanced config be protected via the root password as per normal. It makes support so much easier when you can tell a newbie to right click the desktop and select "Display Settings". regards Ian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anyone know why Sax2 is no longer in Yast?
It's being phased out - as was discussed on the Factory list a couple months ago. You can still launch it from CLI, but in future releases... it won't be included anymore. It's basically lived out most of its life. X has a relatively robust autodetect now... it works in 99% of the cases.
Or is there another way to find out about your graphics card, its driver version etc (apart from the "Hardware" probe option in Yast).
In KDE4, sysinfo:/ in Konqueror provides some really basic info. Configure Desktop > Display provides the same basic information that SAX2 did about your card/resolution etc. SAX2 doesn't provide driver version information (at least not on my system). In Gnome, it's in Control Center > Display where again, the same basic information is shows as is/was in SAX2. This method (autodetect) works WAY better than the old SAX2 tool ever did - assuming you're not one of the unlucky/rare few who have an undetected monitor. I've used the autodetect a lot with my laptop, connecting it to an external projector, and it's got it right 100%.
Should something like Sax2 be apart of the Advanced section of "System Settings"?
No, since SAX2 is no longer necessary for most system configs. There are still a few unusual monitors that the auto config thing doesn't pick up on, but they are not all that common. If you have a config that is not working with the autodetect in X, then it needs to be raised as a bug so it can be fixed/added etc.
My preferred option would be when all options related to a device e.g. display, are accessible from a single point as well as being distributed in other places such as Yast. For example,for me its the logical thing to have all display related options in one place whether it be a theme change, driver change etc and all advanced config be protected via the root password as per normal. It makes support so much easier when you can tell a newbie to right click the desktop and select "Display Settings".
They are all in a single point.... the only place a new user needs to go is Configure Desktop (KDE4) or Control Center (Gnome). In the other lesser used GUIs it's basically the same... using whatever desktop Configure tools they provide. C. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anyone know why Sax2 is no longer in Yast?
It's being phased out - as was discussed on the Factory list a couple months ago. You can still launch it from CLI, but in future releases... it won't be included anymore. It's basically lived out most of its life. X has a relatively robust autodetect now... it works in 99% of the cases. Its the 1% where a manual set up will be required. I was wondering how you change which driver the graphics card uses - e.g.. if i wanted to change from the proprietary Nvidia (or ATI) driver to the open
Or is there another way to find out about your graphics card, its driver version etc (apart from the "Hardware" probe option in Yast).
In KDE4, sysinfo:/ in Konqueror provides some really basic info. Configure Desktop > Display provides the same basic information that SAX2 did about your card/resolution etc. SAX2 doesn't provide driver version information (at least not on my system). Thanks In Gnome, it's in Control Center > Display where again, the same basic information is shows as is/was in SAX2.
This method (autodetect) works WAY better than the old SAX2 tool ever did - assuming you're not one of the unlucky/rare few who have an undetected monitor. I've used the autodetect a lot with my laptop, connecting it to an external projector, and it's got it right 100%. Sax2 got rid of a problem on my display I had after upgrading to 11.2 and KDE4 Factory. I had a thin stripe of random colours down the right hand side. I didn't have an issue before the KDE4 Factory install so i was wondering if
On Sunday 10 Jan 2010 11:07:40 Clayton wrote: source ones - how do i do it? there was anything in it that could have affected it.
Should something like Sax2 be apart of the Advanced section of "System Settings"?
No, since SAX2 is no longer necessary for most system configs. There are still a few unusual monitors that the auto config thing doesn't pick up on, but they are not all that common. If you have a config that is not working with the autodetect in X, then it needs to be raised as a bug so it can be fixed/added etc.
My preferred option would be when all options related to a device e.g. display, are accessible from a single point as well as being distributed in other places such as Yast. For example,for me its the logical thing to have all display related options in one place whether it be a theme change, driver change etc and all advanced config be protected via the root password as per normal. It makes support so much easier when you can tell a newbie to right click the desktop and select "Display Settings".
They are all in a single point.... the only place a new user needs to go is Configure Desktop (KDE4) or Control Center (Gnome). In the other lesser used GUIs it's basically the same... using whatever desktop Configure tools they provide. Is "Configure Desktop" the same as "System Settings"? In system settings you have 5 display related icons on the general page and then one on the Advanced C.
C. Cheers
Ian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Jan 10, 2010 at 13:10, ianseeks <ianseeks@dsl.pipex.com> wrote:
Its the 1% where a manual set up will be required.
Probably less than that. Do you have a specific case where manual setup is required? I've installed 11.2 on a lot of machines/hardware combos, and so far haven't had any issues with display setup. I do know there are a few of what has been termed "corner cases" but I have not yet encountered them. The statement on the Factory list was if you have a case where autodetect is not working it should be raised as a bug and fixed. That said, sax2 is still there in 11.2 so you're not left hanging.. you juat have to launch it from a terminal.
I was wondering how you change which driver the graphics card uses - e.g.. if i wanted to change from the proprietary Nvidia (or ATI) driver to the open source ones - how do i do it?
Add/remove the proprietary driver. That's all I've had to do. You can also still use an xorg.conf file if youre situation requires it.
Sax2 got rid of a problem on my display I had after upgrading to 11.2 and KDE4 Factory. I had a thin stripe of random colours down the right hand side. I didn't have an issue before the KDE4 Factory install so i was wondering if there was anything in it that could have affected it.
Possibly... did your update also include a different version of xorg? Do you know what was changed/added by sax2? Is there some custom config or some odd hardware combination that you have? Maybe there's a bug you've bumped into... I don't know.. I'm on KDE4.4Beta, and it's fine on my Acer AL2016W and nVidia GTX260.
Is "Configure Desktop" the same as "System Settings"? In system settings you have 5 display related icons on the general page and then one on the Advanced
In KDE4.4Beta, I only see Appearance, Desktop, Display icons in the General tab... and... in Advanced... I suppose you could include Desktop Theme Details... and Power Management... but they should be a part of Advanced. To my way of thinking, I think that the breakdown of the display related icons in the KDE4.4 Configure Desktop window is pretty good, and quite logical. Cramming them all under one would make it very cluttered. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 10 Jan 2010 23:02:42 Clayton wrote:
On Sun, Jan 10, 2010 at 13:10, ianseeks <ianseeks@dsl.pipex.com> wrote:
Its the 1% where a manual set up will be required.
Probably less than that. Do you have a specific case where manual setup is required? I've installed 11.2 on a lot of machines/hardware combos, and so far haven't had any issues with display setup. I do [...]
Any time I've wanted to have a reliable *working* dual-head setup with NVidia proprietary drivers I had to manually hack the xorg.conf file (until I found the NVidia configuration tool, which works a treat for that), especially with older monitors where the auto-detect doesn't work too well. I also have an LCD TV that has 1366x768 native resolution but there are only 2 resolution/refresh rate combos that it will properly display from the VGA input: 1360x768x60Hz (no, that isn't a typo, and I'm yet to find a graphics driver that will natively support 1360x768 instead of 1366x768) or 1680x1050x75Hz (no that isn't a typo either). It isn't recognized by Sax2 or X. Unfortunately both laptops have Intel graphics chips so I can't use the NVidia config utility, so I had to generate the modeline manually and again, hack the xorg.conf file. Otherwise, no 2nd monitor. But then again even the "other" OS has problems getting a reliable dual-head display on that TV - it fails more often than it works (and exactly *how* I've occasionally gotten it to work I've got absolutely no idea - I can never do it twice in a row under 'doze). Unfortunately neither laptop supports 1680x1050x75 under 'doze and if anyone can tell me how to hack the windows graphics config to allow 1360x768 instead of 1366x768 I'll give them a medal (or something). -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Jan 10, 2010 at 15:13, Rodney Baker <rodney.baker@iinet.net.au> wrote:
Any time I've wanted to have a reliable *working* dual-head setup with NVidia proprietary drivers I had to manually hack the xorg.conf file (until I found the NVidia configuration tool, which works a treat for that), especially with older monitors where the auto-detect doesn't work too well.
Is that with 11.2? or with previous versions/installs? I've set up dual head using 2xTFT monitors and it's been fine. I've not had to use the nVidia config too at all anymore... just the KDE4 config tool.
I also have an LCD TV that has 1366x768 native resolution but there are only 2 resolution/refresh rate combos that it will properly display from the VGA input: 1360x768x60Hz (no, that isn't a typo, and I'm yet to find a graphics driver that will natively support 1360x768 instead of 1366x768) or 1680x1050x75Hz (no that isn't a typo either). It isn't recognized by Sax2 or X. Unfortunately both laptops have Intel graphics chips so I can't use the NVidia config utility, so I had to generate the modeline manually and again, hack the xorg.conf file. Otherwise, no 2nd monitor.
Hmmm I have something similar here... I'll give it a try with my KDE4.4 laptop... be an interesting test to see if the autodetect will work for me. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010/01/11 00:43 (GMT+1030) Rodney Baker composed:
I also have an LCD TV that has 1366x768 native resolution but there are only 2 resolution/refresh rate combos that it will properly display from the VGA input: 1360x768x60Hz (no, that isn't a typo, and I'm yet to find a graphics driver that will natively support 1360x768 instead of 1366x768) or 1680x1050x75Hz (no that isn't a typo either).
The way I understand it, display drivers are designed for specific standard aspect ratios: narrowest aspect 5:4 (1280x1024; non-square pixels and/or distortion on standard CRT displays) 4:3 (NTSC, PAL, Secam TV & PC display standards) 16:10 (widescreen PC display) 16:9 (HDTV, and HDTV marketed as PC display) widest aspect 1360x768 is not any of those. 1366x768, within 1px, is. Thus, display manufacturers who design 1360x768 as a native mode for computer use in lieu of 1366x768 appear to be incompetent. 1360x768 & 1366x768 are native modes mostly only in 720p HDTVs. FHDTV OTOH @ 1920x1080 is a true 16:9 supported by more gfxchips and their drivers than any other post-4:3 mode. I wouldn't expect a significant proportion of volunteer OSS driver devs to have or care about 720p 1360x768 or 1366x768 hardware to test with. 1680x1050 is a common 16:10 mode, so wouldn't be a typo. -- "Our Constitution was made only for a moral and religious people. It is wholly inadequate to the government of any other." John Adams, 2nd US President Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 10 Jan 2010 12:32:42 Clayton wrote: > On Sun, Jan 10, 2010 at 13:10, ianseeks <ianseeks@dsl.pipex.com> wrote: > > Its the 1% where a manual set up will be required. > > Probably less than that. Do you have a specific case where manual > setup is required? I've installed 11.2 on a lot of machines/hardware > combos, and so far haven't had any issues with display setup. I do > know there are a few of what has been termed "corner cases" but I have > not yet encountered them. The statement on the Factory list was if > you have a case where autodetect is not working it should be raised as > a bug and fixed. I know they are few and far between but isn't it one of the main benefits of *nix systems where you can get to various levels of the bare bones of configuration options right down to editing a config file (but then again bare bones of Xorg is a step too far for my little brain) > That said, sax2 is still there in 11.2 so you're not left hanging.. > you juat have to launch it from a terminal. > > > I was wondering how you change which driver the graphics card uses - > > e.g.. if i wanted to change from the proprietary Nvidia (or ATI) driver > > to the open source ones - how do i do it? > > Add/remove the proprietary driver. That's all I've had to do. This is not an obvious way to do it, I would prefer that there was a Driver choice option on the advanced the in the "Display" > You can also still use an xorg.conf file if youre situation requires it. > > Sax2 got rid of a problem on my display I had after upgrading to 11.2 and > > KDE4 Factory. I had a thin stripe of random colours down the right hand > > side. I didn't have an issue before the KDE4 Factory install so i was > > wondering if there was anything in it that could have affected it. > > Possibly... did your update also include a different version of xorg? > Do you know what was changed/added by sax2? Is there some custom > config or some odd hardware combination that you have? Maybe there's > a bug you've bumped into... I don't know.. I'm on KDE4.4Beta, and it's > fine on my Acer AL2016W and nVidia GTX260. No, just added KDE4 Factory. I was going add others later but haven't done so yet. > > Is "Configure Desktop" the same as "System Settings"? In system settings > > you have 5 display related icons on the general page and then one on the > > Advanced > > In KDE4.4Beta, I only see Appearance, Desktop, Display icons in the > General tab... and... in Advanced... I suppose you could include > Desktop Theme Details... and Power Management... but they should be a > part of Advanced. To my way of thinking, I think that the breakdown > of the display related icons in the KDE4.4 Configure Desktop window is > pretty good, and quite logical. Cramming them all under one would > make it very cluttered. > > C. There is also "Window Behaviour". All these could appear under just one icon - Display - and from there you can split them out into the separate options. I believe the "Systems Settings" should also be hierarchical like a menu with the top level being the most high level description. It makes it so much easier for someone learning the system and positive comments about KDE's ease of use. regards Ian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Jan 11, 2010 at 21:54, ianseeks <ianseeks@dsl.pipex.com> wrote:
I know they are few and far between but isn't it one of the main benefits of *nix systems where you can get to various levels of the bare bones of configuration options right down to editing a config file (but then again bare bones of Xorg is a step too far for my little brain)
Sure, but you generally select a distro that suits the task. For example on a very low spec machine I would not be running KDE4, and probably not even openSUSE... DamnSmallLinux is nice for older hardware for example... or openSUSE with say... XFCE. IF you go the route of DSL.. sax2 isn't even in the equation anymore :-) C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2010-01-10 at 12:10 -0000, ianseeks wrote:
Its the 1% where a manual set up will be required. I was wondering how you change which driver the graphics card uses - e.g.. if i wanted to change from the proprietary Nvidia (or ATI) driver to the open source ones - how do i do it?
You just need the part of the configuration file with the change, leave the rest on automatic. I have a "/etc/X11/xorg.conf.nv" file which I copy to "/etc/X11/xorg.conf" or delete if I want the nv driver or the default, nvidia driver. No need to remove drivers. /etc/X11/xorg.conf.nv: Section "Device" Identifier "Configured Video Device" Driver "nv" EndSection thats all it has. Simple :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAktKgFIACgkQtTMYHG2NR9VRTwCgjSd6izkw1rvS/0cQzEpEA/Xu H8sAn1Zb93gwRYyGkOChtRgdMY5Ap72/ =rA1Q -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
i wanted to change from the proprietary Nvidia (or ATI) driver to the open source ones - how do i do it?
You just need the part of the configuration file with the change, leave the rest on automatic. I have a "/etc/X11/xorg.conf.nv" file which I copy to "/etc/X11/xorg.conf" or delete if I want the nv driver or the default, nvidia driver. No need to remove drivers.
/etc/X11/xorg.conf.nv:
Section "Device" Identifier "Configured Video Device" Driver "nv" EndSection
thats all it has. Simple :-)
Ah cool. Thanks for the tip Carlos.... I'd forgotten that you could do that (I rarely ever use anything but the proprietary drivers). The fact that your xorg.conf need only contain the customizations on top of the autodetect bit is an important one to note for those with the odd hardware combos that do require some manual intervention.. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 11/01/10 18:46, Clayton wrote:
i wanted to change from the proprietary Nvidia (or ATI) driver to the open source ones - how do i do it?
You just need the part of the configuration file with the change, leave the rest on automatic. I have a "/etc/X11/xorg.conf.nv" file which I copy to "/etc/X11/xorg.conf" or delete if I want the nv driver or the default, nvidia driver. No need to remove drivers.
/etc/X11/xorg.conf.nv:
Section "Device" Identifier "Configured Video Device" Driver "nv" EndSection
thats all it has. Simple :-)
Ah cool. Thanks for the tip Carlos.... I'd forgotten that you could do that (I rarely ever use anything but the proprietary drivers).
The fact that your xorg.conf need only contain the customizations on top of the autodetect bit is an important one to note for those with the odd hardware combos that do require some manual intervention..
C.
I suspect - know - that I have missed the more salient points in this thread, but one can still configure the main bit of SAX2 with: Kickoff>Applications>System>Configuration>Configure x11 System. What I do not know if this will remain after 11.2 (I am using 11.2 at the moment). BC -- Take the bull by the tail and look the facts in the face. W C Fields -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-01-11 at 20:43 +1100, Basil Chupin wrote:
I suspect - know - that I have missed the more salient points in this thread, but one can still configure the main bit of SAX2 with:
Kickoff>Applications>System>Configuration>Configure x11 System.
What I do not know if this will remain after 11.2 (I am using 11.2 at the moment).
The tool will be there, not maintained, and perhaps with some sections disabled. After some time, it will simply stop working, because the changes it does in the config will be ignored, I think. Then it will be removed completely. That's what I understood, at least. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAktLeWAACgkQtTMYHG2NR9XbVACfet56XMvZVvzOW8enli/Y7lYa gQoAnRKmg1ZyI3M3VHjwerJNq818WlO2 =p1Mr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-01-11 at 08:46 +0100, Clayton wrote:
/etc/X11/xorg.conf.nv:
Section "Device" Identifier "Configured Video Device" Driver "nv" EndSection
thats all it has. Simple :-)
Ah cool. Thanks for the tip Carlos.... I'd forgotten that you could do that (I rarely ever use anything but the proprietary drivers).
Me, I always used the open driver, except when I want to use a game with 3D. Unfortunately, my new machine is unable to hibernate with the open (nv) driver. The problem is that the first time I switched to the proprietary driver, my gnome desktop drove me nuts: windows "wobbled" when I moved them. I thought the display was using a terribly slow refresh or redraw speed; perhaps I had been had with my shiny big new display. I fought the problem for an hour or two. Suddenly I hit ctrl-alt-right to change to another workspace and I saw "the" cube rotating... all was clear. Suse guys have enabled compiz by default, but it is inactive till you put a capable driver in. I had to remove completely the compiz rpms from the system. I could not find a master switch to just disable compiz. Novell says it is very easy (I wrote a bugzilla on this issue which they disregarded succinctly), but it mustn't be that easy when there is a wiki page on how to disable compiz... :-( I recogn, though, that it has never been so easy to enable the nvidia driver before. That's a good thing. Just enable the repo, update, done. Works! Such a difference from a decade ago... And I did not have to configure xorg.conf, either. I suppose my machines are easy, or I was lucky.
The fact that your xorg.conf need only contain the customizations on top of the autodetect bit is an important one to note for those with the odd hardware combos that do require some manual intervention..
Absolutely. We'll probably need a new tool to do that, though. I don't like leaving this to the user on the desktop: it should be done by the administrator, for all users and all possible desktop choices. And it can not be Sax. For technical reasons I don't fully understand, but the thing is, keyboard and mouse is out of the direct control of the X system, it comes from... was it hal? Therefore, Sax can do nought on that side. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAktLeNYACgkQtTMYHG2NR9UlBgCfQaVwOPB0u3wYZPs1ogfSU6lS b0MAoI3DnZGuvBobBCrpfw4FdeP3alVV =cQNB -----END PGP SIGNATURE-----
On Mon, Jan 11, 2010 at 20:15, Carlos E. R. <robin.listas@telefonica.net> wrote:
The problem is that the first time I switched to the proprietary driver, my gnome desktop drove me nuts: windows "wobbled" when I moved them. I thought the display was using a terribly slow refresh or redraw speed; perhaps I had been had with my shiny big new display. I fought the problem for an hour or two. Suddenly I hit ctrl-alt-right to change to another workspace and I saw "the" cube rotating... all was clear. Suse guys have enabled compiz by default, but it is inactive till you put a capable driver in.
In KDE4 the compositing thing is very toned down in comparison - eg no wobbly windows. Plus, disabling compositing is super easy with an Alt+Shift+F12. (there must be something similar in Gnome.. or have the Gnome devs decided that that too is too confusing and removed it?) I have tried using the nv driver, but.. overall it simply doesn't work well enough for me.. i hate having to re-enable the proprietary driver every time I want to do something extra... so it's always enabled/in use on my system. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-01-11 at 20:24 +0100, Clayton wrote:
On Mon, Jan 11, 2010 at 20:15, Carlos E. R. <robin.listas@telefonica.net> wrote:
The problem is that the first time I switched to the proprietary driver, my gnome desktop drove me nuts: windows "wobbled" when I moved them. I thought the display was using a terribly slow refresh or redraw speed; perhaps I had been had with my shiny big new display. I fought the problem for an hour or two. Suddenly I hit ctrl-alt-right to change to another workspace and I saw "the" cube rotating... all was clear. Suse guys have enabled compiz by default, but it is inactive till you put a capable driver in.
In KDE4 the compositing thing is very toned down in comparison - eg no wobbly windows. Plus, disabling compositing is super easy with an Alt+Shift+F12. (there must be something similar in Gnome.. or have the Gnome devs decided that that too is too confusing and removed it?)
You have to know beforehand that there is a key that disables it. I don't. It is enabled in the control center, I think it is called "desktop effects" or similar. Actually, it is enabled by default, and it works as soon as you have 3D driver installed. As I did not enable compiz, I had no idea how to disable it, I had not read any docs. And I still don't know. They say it is very simple... well, it can't be so simple, as there are one or two wiki pages describing how to disable compiz.
I have tried using the nv driver, but.. overall it simply doesn't work well enough for me.. i hate having to re-enable the proprietary driver every time I want to do something extra... so it's always enabled/in use on my system.
I usually don't need anything the propietary driver provides. I don't play games. What else is it good for? >:-) Except that hybernation is broken. That's the only reason I need it on my new machine. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAktQwmwACgkQtTMYHG2NR9VU4wCeKlrdiMuT5T9iJADL8peZyhDF WR0An2m9R66wRgCMj0kUcRTIEd96Umad =66Yq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Jan 15, 2010 at 20:30, Carlos E. R. <robin.listas@telefonica.net> wrote:
You have to know beforehand that there is a key that disables it. I don't.
Neither did I.... but on the KDE side, it conveniently told me at some point or another when the effects were auto-disabled for some reason.
It is enabled in the control center, I think it is called "desktop effects"
Yup.. dead easy to turn off... In Gnome, you click Control Center > Desktop Effect > Enable desktop effects (check box). Seems pretty darned easy to me. It's no where near as horrific as it's been made out to be. That said, I do agree that the default desktop effects setting in Gnome could *definitely* do with a revisit and tone them down just a little. Wobbly windows look neat and all and are nice for showing off, but in reality, I'd bet that few people actually leave the wobbly windows turned on in the long term.
or similar. Actually, it is enabled by default, and it works as soon as you have 3D driver installed. As I did not enable compiz, I had no idea how to disable it, I had not read any docs. And I still don't know.
Oh come on... it's not hard... I don't use Gnome.. took me all of 10 seconds to figure it out when I logged into Gnome on my test computer.... and I'm not that smart :-) I'd bet you'd figure it out in about the same length of time. It took more effort to grumble about it on the mailing list :-)
They say it is very simple... well, it can't be so simple, as there are one or two wiki pages describing how to disable compiz.
Old info in most cases. Disabling Compiz is really easy now... In both KDE and Gnome it's a checkbox... that's it. No restart of the window manager is needed... it just toggles on/off. Other WMs... I can't speak for since I only use KDE and occasionally Gnome.
I usually don't need anything the propietary driver provides. I don't play games. What else is it good for? >:-)
It REALLY makes a difference in my experience on my media center (using the proprietary drivers), and it makes a difference in my experience with Flash in web pages. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2010-01-15 at 22:13 +0100, Clayton wrote:
That said, I do agree that the default desktop effects setting in Gnome could *definitely* do with a revisit and tone them down just a little. Wobbly windows look neat and all and are nice for showing off, but in reality, I'd bet that few people actually leave the wobbly windows turned on in the long term.
Most certainly.
or similar. Actually, it is enabled by default, and it works as soon as you have 3D driver installed. As I did not enable compiz, I had no idea how to disable it, I had not read any docs. And I still don't know.
Oh come on... it's not hard... I don't use Gnome.. took me all of 10 seconds to figure it out when I logged into Gnome on my test computer.... and I'm not that smart :-) I'd bet you'd figure it out in about the same length of time. It took more effort to grumble about it on the mailing list :-)
It took me an hour, no less. The "enable" icon did not disable it. I had to go disabling every single item in the configuration, and that produced a desktop that simply did not work in "plain" mode. I had to remove the compiz rpms, and delete all the gnome config files. Certainly, no "checkbox" was there to disable it. Now that I know, I could reinstall it and try, if I have time.
I usually don't need anything the propietary driver provides. I don't play games. What else is it good for? >:-)
It REALLY makes a difference in my experience on my media center (using the proprietary drivers), and it makes a difference in my experience with Flash in web pages.
Flash? Dunno, I haven't noticed. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAktTCXoACgkQtTMYHG2NR9VWyQCfSMh05BmGSgCWqwY3B2NbEk2r KuIAn1xLOMFn+NOoTcmgyoMr40kyT5MH =3TiZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 11 Jan 2010 01:35:10 Carlos E. R. wrote:
On Sunday, 2010-01-10 at 12:10 -0000, ianseeks wrote:
Its the 1% where a manual set up will be required. I was wondering how you change which driver the graphics card uses - e.g.. if i wanted to change from the proprietary Nvidia (or ATI) driver to the open source ones - how do i do it?
You just need the part of the configuration file with the change, leave the rest on automatic. I have a "/etc/X11/xorg.conf.nv" file which I copy to "/etc/X11/xorg.conf" or delete if I want the nv driver or the default, nvidia driver. No need to remove drivers.
/etc/X11/xorg.conf.nv:
Section "Device" Identifier "Configured Video Device" Driver "nv" EndSection
thats all it has. Simple :-) Thanks. but it would be easier/more obvious if it was an option in the "Display" option.
regards Ian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Sonntag, 10. Januar 2010 12:07:40 schrieb Clayton:
Anyone know why Sax2 is no longer in Yast? It's being phased out - as was discussed on the Factory list a couple months ago. You can still launch it from CLI, but in future releases... it won't be included anymore. It's basically lived out most of its life. X has a relatively robust autodetect now... it works in 99% of the cases. Does that mean I could just connect a graphics tablet on USB and it would just work without any intervention? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Jan 10, 2010 at 16:20, Stefan Quandt <st.quandt@googlemail.com> wrote:
Does that mean I could just connect a graphics tablet on USB and it would just work without any intervention?
Ummm.. in theory... it depends :-) If the tablet is supported in Linux... possibly. You are depending on the drivers being in place and supporting the Xorg version in 11.2. Assuming all that lines up... still possibly. You may need to generate an xorg.conf file (X -configure) and add the tablet specific bits by hand... something you had to do by hand anyway after using sax2 in the past (at least in my experience setting up a Bamboo Wacom tablet) Basically... at least for me.. sax2 did very little to help set up any tablets I connected. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anyone know why Sax2 is no longer in Yast?
It's being phased out - as was discussed on the Factory list a couple months ago. You can still launch it from CLI, but in future releases... it won't be included anymore.
This is opensuse list. Most of the members here, I guess, are not reading factory list. I never understood why people have to reference to the factory list (except if it is a direct link to a specific message). It is nonsene.
It's basically lived out most of its life. X has a relatively robust autodetect now... it works in 99% of the cases. I can't understand these types of explanations either. What does it mean "lived out most of its life"? It can not be stated until it is still required by users and functional. (Similarly it is said by some that KDE3 lived out its life, and it is not true either.)
Furthermore the autodetect method just does not work. I had to configure 7 or 8 monitors recently, and the autodect method failed every time. It is not 1 % or less. The autodect method forces a given setup and does not let you choose. How the autodectect method could find out what the resolution is I want to use? How can it find out if I want 1600x1200, 1280x960, 1024x768 or only 800x600? The autodetect method can not read anybody's thoughts. Why don't the system let the user select what he wants?
This method (autodetect) works WAY better than the old SAX2 tool > ever did - assuming you're not one of the unlucky/rare few who have an undetected monitor. I've used the autodetect a lot with my > >laptop, connecting it to an external projector, and it's got it right >100%. I don not know why it is WAY better to configure a monitor to flicker than to not flicker? Can you explain it?
Should something like Sax2 be apart of the Advanced section of "System Settings"?
No, since SAX2 is no longer necessary for most system configs. There are still a few unusual monitors that the auto config thing doesn't pick up on, but they are not all that common. If you have a config that is not working with the autodetect in X, then it needs to be raised as a bug so it can be fixed/added etc. This is completely nonsense. The issue is that the system forces you to accept something that may not be correct or according to your needs. This regards to not only opensuse but other distros too.
They are all in a single point.... the only place a new user needs to go is Configure Desktop (KDE4) or Control Center (Gnome). In the other lesser used GUIs it's basically the same... using whatever desktop Configure tools they provide. Yes and at next login you have to set it again, since the system soulc not remember the stting (Xubuntu). But if it can you still might have a badly configured login window.
All in all I agree with the idea/goal that setup should be made automatically but completely disagree with removing tools used for adjusting settings according to users needs. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
This is opensuse list. Most of the members here, I guess, are not reading factory list. I never understood why people have to reference to the factory list (except if it is a direct link to a specific message). It is nonsene.
And.. what's your point? I listen in on the Factory list... and all I was doing is letting the OP know that this was discussed on the Factory list. Nothing more. I wasn't suggesting that the OP should be subscribed there.. if it was interpreted that way... well.... that was not the intention.
It's basically lived out most of its life. X has a relatively robust autodetect now... it works in 99% of the cases. I can't understand these types of explanations either. What does it mean "lived out most of its life"? It can not be stated until it is still required by users and functional. (Similarly it is said by some that KDE3 lived out its life, and it is not true either.)
Simple... in most cases it's not needed anymore.. thus it's lived out most of its life. You can phrase it however you want, but the reality is that it is an old technology that is being replaced by soemthing newer and frankly easier to use. I'm not a dev, just a user relaying that info that I read on the Factory mailing list. If you don't like it.. take it up with the devs.
Furthermore the autodetect method just does not work. I had to configure 7 or 8 monitors recently, and the autodect method failed every time. It is not 1 % or less. The autodect method forces a given setup and does not let you choose. How the autodectect method could find out what the resolution is I want to use? How can it find out if I want 1600x1200, 1280x960, 1024x768 or only 800x600? The autodetect method can not read anybody's thoughts. Why don't the system let the user select what he wants?
It does work and it does let you choose... if you stop trying to make it work the old way. You can chose your monitor resolution... I've already detailed where to go to do this... or use xrandr... it works fine on all monitors I've tried on.. TFT and CRT and LCD TVs. That said, yes there will be a few that won't work... if you happen to have one.. raise a bug. Seems pretty simple. As well.. if the autodetect doesn't work on your setup, then use sax2. it's still there... but again... it you're forced to drop back to sax2 then raise a bug. I just now (before replying) tested it on 3 different monitors, one being my Toshiba LCD 32" TV. In each case, it autodetected the monitor and set it up to the max resolution. In each case I could go into the Display settings and change that resolution to any one of the supported resolutions for that monitor by picking from a drop down list. I also set-up and tested multiple monitors and in each case (TFT and projector, TFT and LCD TV, etc etc) it detected and set up multi-monitor correctly. It was WAY easier than the old sax2 method.
I don not know why it is WAY better to configure a monitor to flicker than to not flicker? Can you explain it?
Sure... set your refresh rate higher. Where... in the same place you set your resolution.. in the Display part of the Configure window if your preferred Window Manager. It has the same basic setup options as sax2 does (I just compared the two on my computers), including a setting for refresh rates.
pick up on, but they are not all that common. If you have a config that is not working with the autodetect in X, then it needs to be raised as a bug so it can be fixed/added etc. This is completely nonsense. The issue is that the system forces you to accept something that may not be correct or according to your needs. This regards to not only opensuse but other distros too.
And.. your point? If it isn't working.. raise it with the developers and those that build openSUSE... or any other distro out there. They are ALL starting to use the autodetect in X. Your statement is complete nonsense, and a complete lack of willingness to actually try to see how the new way works. You are not forced to do anything.
Yes and at next login you have to set it again, since the system soulc not remember the stting (Xubuntu). But if it can you still might have a badly configured login window.
Huh? So you've problems with Xubuntu? So? And? openSUSE works fine. I can reboot, log out, log in... pull the second monitor cable etc etc, and autodetect hums right along no problem.
All in all I agree with the idea/goal that setup should be made automatically but completely disagree with removing tools used for adjusting settings according to users needs.
It's not removed. It's still there. It's just not linked in YaST and it is no longer being devloped/changed/improved/maintained by the dev guys. I would expect it to be completely removed in a future openSUSE release. Sigh.. this whole discussion reminds me of the same discussion that came up when hal was introduced and the oldschool guys wailed about being forced to use hal instead of manually mounting... C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
This is opensuse list. Most of the members here, I guess, are not reading factory list. I never understood why people have to reference to the factory list (except if it is a direct link to a specific message). It is nonsene.
And.. what's your point? I listen in on the Factory list... and all I was doing is letting the OP know that this was discussed on the Factory list. Nothing more. I wasn't suggesting that the OP should be subscribed there.. if it was interpreted that way... well.... that was not the intention.
Sorry for I was rude. I misundertsood you, thougt that you expected us to read factory list. I apologize.
It's basically lived out most of its life. X has a relatively robust autodetect now... it works in 99% of the cases. I can't understand these types of explanations either. What does it mean
"lived out most of its life"? It can not be stated until it is still required by users and functional. (Similarly it is said by some that KDE3 lived out its life, and it is not true either.)
Simple... in most cases it's not needed anymore.. thus it's lived out most of its life. You can phrase it however you want, but the reality is that it is an old technology that is being replaced by soemthing newer and frankly easier to use. I'm not a dev, just a user relaying that info that I read on the Factory mailing list. If you don't like it.. take it up with the devs. This could be a discussion beyond the borders of this topic.
Once more, autodetection is good (and it worked in earlier SUSE versions as well). What I am saying is that tools which can be used to change default settings should not be removed from the main configuration center, not to mention the whole distro. So those who are satisfied with the results of autodetection are not going to use use them, those who want to change something has a tool and do not have to hack config files and/or file bug reports. Cheers, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Once more, autodetection is good (and it worked in earlier SUSE versions as well). What I am saying is that tools which can be used to change default settings should not be removed from the main configuration center, not to mention the whole distro. So those who are satisfied with the results of autodetection are not going to use use them, those who want to change something has a tool and do not have to hack config files and/or file bug reports.
That was brought up on the Factory list... I forget the exact details... there was a decision taken though in terms of manpower (devs available) to stop maintenance on sax2. It's still there, still available for those few people who still need it for some reason or another, but for the vast majority - virtually all users (but not quite all just yet) sax2 is redundant. Not my opinion... just a simple statement of fact. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 11/01/10 22:15, Istvan Gabor wrote:
This is opensuse list. Most of the members here, I guess, are not
reading factory list. I never understood why people have to reference to the factory list (except if it is a direct link to a specific message). It is nonsene.
And.. what's your point? I listen in on the Factory list... and all I was doing is letting the OP know that this was discussed on the Factory list. Nothing more. I wasn't suggesting that the OP should be subscribed there.. if it was interpreted that way... well.... that was not the intention.
Sorry for I was rude. I misundertsood you, thougt that you expected us to read factory list. I apologize.
[pruned] Istvan, my most humble apologies but could you, *please*, configure whatever mail client - most probably some MS <shudder> production - you are using so that it quotes at the beginning the name of the poster to whom you are replying and the date (and time) of that poster's message? I haven't a bloody clue to whom and to what you are replying to and when the part you are replying to was posted (was it last week or last year or yesterday)? :-) Thank you muchly :-) . BC -- Take the bull by the tail and look the facts in the face. W C Fields -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Basil Chupin -
Carlos E. R. -
Clayton -
Felix Miata -
ianseeks -
Istvan Gabor -
Rodney Baker -
Stefan Quandt