[opensuse] Still wanting to upgrade to 12.1 ..............
with the following conditions fixed. I would like to here from persons that have had these problems fixed. - Can't get my MB sound card to work (Intel ICH7) consistent. - alsasound will not stay "yes" in the system service levels. - rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active. - Can't get my display to stay at 1024x768 - Can't get rid of the "Nepomuk Indexing Disabled) popups TIA, Duaine -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 2012-04-22 at 20:59 -0500, Duaine Hechler wrote:
with the following conditions fixed.
I would like to here from persons that have had these problems fixed.
- Can't get my MB sound card to work (Intel ICH7) consistent.
- alsasound will not stay "yes" in the system service levels.
- rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active.
- Can't get my display to stay at 1024x768
- Can't get rid of the "Nepomuk Indexing Disabled) popups
TIA, Duaine
-- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years
I haven't had these issues, except the Nepomuk nastiness. The Gnome version of 12.1 has been nearly flawless for me. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/23/2012 10:30 AM, Roger Luedecke wrote:
On Sun, 2012-04-22 at 20:59 -0500, Duaine Hechler wrote:
with the following conditions fixed.
I would like to here from persons that have had these problems fixed.
- Can't get my MB sound card to work (Intel ICH7) consistent.
- alsasound will not stay "yes" in the system service levels.
- rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active.
- Can't get my display to stay at 1024x768
- Can't get rid of the "Nepomuk Indexing Disabled) popups
TIA, Duaine
-- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years
I haven't had these issues, except the Nepomuk nastiness. The Gnome version of 12.1 has been nearly flawless for me.
That's the thing, I don't want to use Gnome. -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Apr 23, 2012 at 03:59, Duaine Hechler <dahechler@att.net> wrote:
with the following conditions fixed.
I would like to here from persons that have had these problems fixed.
- Can't get my MB sound card to work (Intel ICH7) consistent.
- alsasound will not stay "yes" in the system service levels.
- rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active.
Have you tried tinkering with the Pulse settings? The previous discussion you had about this ended (I think) with Rajkos suggestion that you look to see if HDMI is being set as your default sound device. You said you were looking in YaST at the sound configuration... have you tried looking in KDE's system settings instead? Alternatively, have you looked a the troubleshooting steps here? http://en.opensuse.org/SDB:Intel-HDA_sound_problems
- Can't get my display to stay at 1024x768
Are you using a CRT? or a TFT? If you are using a TFT, you should be aware (I'm guessing you are) that they each have a fixed native resolution, and any other resolution is... going to be a problem. When you force a non-native resolution, you end up with fuzzy lines and fonts because the monitor it forced span things that should be single a pixel across several neighboring pixels. On top of that if your monitor is a 16:9 or 16:10 aspect ration you're really going to mess things up visually if you go to 1024x768 which it a 4:3 aspect ratio. Circles will no longer be circles, etc. If the reason you are forcing a non-native resolution is you need the display to be "bigger" to aid visual limitations of the user, then you could maybe look at desktop zoom instead of munging the resolution. Or change the desktop font sizes (default is 9 point) to a larger size.
- Can't get rid of the "Nepomuk Indexing Disabled) popups
Update KDE4 to the latest 4.8.2, and the problem should go away. Another alternative... openSUSE 12.2 M4 will be out soon.. you could give it a whirl and see how it works out. Overall it's working well on my laptop - a few bugs of course, but... it might be worth a shot. C -- openSUSE 12.1 x86_64, KDE 4.8.2 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/23/2012 12:38 PM, C wrote:
with the following conditions fixed.
I would like to here from persons that have had these problems fixed.
- Can't get my MB sound card to work (Intel ICH7) consistent.
- alsasound will not stay "yes" in the system service levels.
- rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active. Have you tried tinkering with the Pulse settings? The previous discussion you had about this ended (I think) with Rajkos suggestion
On Mon, Apr 23, 2012 at 03:59, Duaine Hechler<dahechler@att.net> wrote: that you look to see if HDMI is being set as your default sound device. You said you were looking in YaST at the sound configuration... have you tried looking in KDE's system settings instead?
Alternatively, have you looked a the troubleshooting steps here? http://en.opensuse.org/SDB:Intel-HDA_sound_problems
None of those suggestions work either. I uninstall Pulse and made sure there were no Pulse related modules in the libraries but still no difference. I feel something broke between 11.4 and 12.1 because everything works fine in 11.4.
- Can't get my display to stay at 1024x768 Are you using a CRT? or a TFT?
If you are using a TFT, you should be aware (I'm guessing you are) that they each have a fixed native resolution, and any other resolution is... going to be a problem. When you force a non-native resolution, you end up with fuzzy lines and fonts because the monitor it forced span things that should be single a pixel across several neighboring pixels.
On top of that if your monitor is a 16:9 or 16:10 aspect ration you're really going to mess things up visually if you go to 1024x768 which it a 4:3 aspect ratio. Circles will no longer be circles, etc.
If the reason you are forcing a non-native resolution is you need the display to be "bigger" to aid visual limitations of the user, then you could maybe look at desktop zoom instead of munging the resolution. Or change the desktop font sizes (default is 9 point) to a larger size.
I'm using a Dell 17" LCD. And, as I stated above, I can get the display to stay at 1024x768 in 11.4 and everything looks fine.
- Can't get rid of the "Nepomuk Indexing Disabled) popups Update KDE4 to the latest 4.8.2, and the problem should go away.
Is 4.8.2 in the repositories ?
Another alternative... openSUSE 12.2 M4 will be out soon.. you could give it a whirl and see how it works out. Overall it's working well on my laptop - a few bugs of course, but... it might be worth a shot.
C
-- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Apr 23, 2012 at 20:13, Duaine Hechler <dahechler@att.net> wrote:
Alternatively, have you looked a the troubleshooting steps here? http://en.opensuse.org/SDB:Intel-HDA_sound_problems
None of those suggestions work either. I uninstall Pulse and made sure there were no Pulse related modules in the libraries but still no difference.
I feel something broke between 11.4 and 12.1 because everything works fine in 11.4.
Pulse actually works well in 12.1, so removing it isn't the "fix" like it used to be. Saying "something" went wrong isn't enough information unfortunately.... you need to poke it a bit more and provide everyone here a bit more to work with.
I'm using a Dell 17" LCD. And, as I stated above, I can get the display to stay at 1024x768 in 11.4 and everything looks fine.
I'd say follow up on your previous thread and see where that ends vs starting a whole new discussion on it here.
- Can't get rid of the "Nepomuk Indexing Disabled) popups
Update KDE4 to the latest 4.8.2, and the problem should go away.
Is 4.8.2 in the repositories ?
Yes: http://en.opensuse.org/KDE_repositories#Upstream_release_aka._KR48_.28KDE_SC... C. -- openSUSE 12.1 x86_64, KDE 4.8.2 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/22 20:59 (GMT-0500) Duaine Hechler composed:
- Can't get my MB sound card to work (Intel ICH7) consistent.
- alsasound will not stay "yes" in the system service levels.
- rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active.
I have two 12.1 installations on ICH7/82801G. I did nothing personally involving sound configuration on either. Both were fresh installs. The one with working sound has sysvinit-init installed. The one with non-working sound doesn't. I have no recollection if there's anything else that distinguishes the two other than installation and updates made at different times. According to the release notes (wherever they disappeared to), more than one problem may be solved by installing sysvinit-init, which replaces the buggy immature systemd init system. -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/24/2012 02:15 AM, Felix Miata wrote:
On 2012/04/22 20:59 (GMT-0500) Duaine Hechler composed:
- Can't get my MB sound card to work (Intel ICH7) consistent.
- alsasound will not stay "yes" in the system service levels.
- rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active.
I have two 12.1 installations on ICH7/82801G. I did nothing personally involving sound configuration on either. Both were fresh installs.
The one with working sound has sysvinit-init installed. The one with non-working sound doesn't. I have no recollection if there's anything else that distinguishes the two other than installation and updates made at different times. According to the release notes (wherever they disappeared to), more than one problem may be solved by installing sysvinit-init, which replaces the buggy immature systemd init system.
So who do I install with sysvinit-init installed ? -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/24/2012 02:51 AM, Duaine Hechler wrote:
On 04/24/2012 02:15 AM, Felix Miata wrote:
On 2012/04/22 20:59 (GMT-0500) Duaine Hechler composed:
- Can't get my MB sound card to work (Intel ICH7) consistent.
- alsasound will not stay "yes" in the system service levels.
- rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active.
I have two 12.1 installations on ICH7/82801G. I did nothing personally involving sound configuration on either. Both were fresh installs.
The one with working sound has sysvinit-init installed. The one with non-working sound doesn't. I have no recollection if there's anything else that distinguishes the two other than installation and updates made at different times. According to the release notes (wherever they disappeared to), more than one problem may be solved by installing sysvinit-init, which replaces the buggy immature systemd init system.
So who do I install with sysvinit-init installed ?
-- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Duaine Hechler wrote:
On 04/24/2012 02:15 AM, Felix Miata wrote:
On 2012/04/22 20:59 (GMT-0500) Duaine Hechler composed:
- Can't get my MB sound card to work (Intel ICH7) consistent.
- alsasound will not stay "yes" in the system service levels.
- rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active.
I have two 12.1 installations on ICH7/82801G. I did nothing personally involving sound configuration on either. Both were fresh installs.
The one with working sound has sysvinit-init installed. The one with non-working sound doesn't. I have no recollection if there's anything else that distinguishes the two other than installation and updates made at different times. According to the release notes (wherever they disappeared to), more than one problem may be solved by installing sysvinit-init, which replaces the buggy immature systemd init system.
So who do I install with sysvinit-init installed ?
You do a normal install, and press F5 during the boot-up. -- Per Jessen, Zürich (7.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/24/2012 03:42 AM, Per Jessen wrote:
Duaine Hechler wrote:
On 04/24/2012 02:15 AM, Felix Miata wrote:
On 2012/04/22 20:59 (GMT-0500) Duaine Hechler composed:
- Can't get my MB sound card to work (Intel ICH7) consistent. - alsasound will not stay "yes" in the system service levels. - rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active. I have two 12.1 installations on ICH7/82801G. I did nothing personally involving sound configuration on either. Both were fresh installs.
The one with working sound has sysvinit-init installed. The one with non-working sound doesn't. I have no recollection if there's anything else that distinguishes the two other than installation and updates made at different times. According to the release notes (wherever they disappeared to), more than one problem may be solved by installing sysvinit-init, which replaces the buggy immature systemd init system. So who do I install with sysvinit-init installed ? You do a normal install, and press F5 during the boot-up. Would it work to do a normal install and add sysvinit and delete systemd, then reboot ?
-- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-24 10:52, Duaine Hechler wrote:
On 04/24/2012 03:42 AM, Per Jessen wrote:
So who do I install with sysvinit-init installed ? You do a normal install, and press F5 during the boot-up. Would it work to do a normal install and add sysvinit and delete systemd, then reboot ?
There is no need to install/remove anything. You can add in the kernel boot line "init=/sbin/sysvinit" and it will start in systemv mode. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+WblMACgkQIvFNjefEBxoJNgCdE3riID209gszhBmnMOGPiBb1 XvYAn3nFZJn5QUuKMzUJeOYCbsg7C82p =jNy6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/24 11:11 (GMT+0200) Carlos E. R. composed:
Duaine Hechler wrote:
Per Jessen wrote:
Duaine Hechler wrote:
So who [sic] do I install with sysvinit-init installed ?
You select it during installation. If you forget or otherwise fail during installation, you later either 'zypper in sysvinit-init' from cmdline, or select it for installation in YaST.
You do a normal install, and press F5 during the boot-up.
That doesn't install it, but does boot as if it had been installed.
Would it work to do a normal install and add sysvinit and delete systemd, then reboot ?
That would get it installed, though the F5 method is an easy way to see first if it helps your problem(s).
There is no need to install/remove anything.
No, but it's a logical thing to do if booting that way solves the problem(s).
You can add in the kernel boot line "init=/sbin/sysvinit" and it will start in systemv mode.
Doing the F5 method to test is simple. Installing it if F5 helps is prudent. -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-24 13:07, Felix Miata wrote:
There is no need to install/remove anything.
No, but it's a logical thing to do if booting that way solves the problem(s).
I think it is preferable to leave it installed, in order to learn if the problem has been solved. I assume that all those problems are reported to Bugzilla, and I know for certain that the maintainer is quite active because I have reported several. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+WqfcACgkQIvFNjefEBxpukQCfe1sJ2dAw7Co5gvw+GkWjs6rp rbQAoL23vFSxFmMw6WGthoma8Yk+sc+2 =aGrU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 24 Apr 2012 18:56:16 +0530, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-04-24 13:07, Felix Miata wrote:
There is no need to install/remove anything.
No, but it's a logical thing to do if booting that way solves the problem(s).
I think it is preferable to leave it installed, in order to learn if the problem has been solved. I assume that all those problems are reported to Bugzilla, and I know for certain that the maintainer is quite active because I have reported several.
to not have to bother with <F5> or remembering to type in "init=/sbin/sysvinit" on startup, one can add this command to the kernel parameters, which achieves the same result, i.e., booting with the old system for now. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-24 16:12, phanisvara das wrote:
to not have to bother with <F5> or remembering to type in "init=/sbin/sysvinit" on startup, one can add this command to the kernel parameters, which achieves the same result, i.e., booting with the old system for now.
That is what I said. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+WthMACgkQIvFNjefEBxqPZgCeKYhwRAhDCfcYJvQQDZqm7AWa yD4AnjYePsLTfQb5DhrVoLW7ClB6Y9vB =qOex -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 24 Apr 2012 19:47:55 +0530, Carlos E. R. <robin.listas@telefonica.net> wrote:
That is what I said.
yes, you did; skipped that message somehow...you were there first. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-24 16:41, phanisvara das wrote:
On Tue, 24 Apr 2012 19:47:55 +0530, Carlos E. R. <> wrote:
That is what I said.
yes, you did; skipped that message somehow...you were there first.
No problem with being first or not, I thought you misunderstood what I said. :-) - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+W4M4ACgkQIvFNjefEBxodcgCgmIVeEN3bB4NeiQAexjYqnr7s RSsAoJbWqWbkz3w0EBIWNrZZ2jgOqiwx =/rrS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/24 15:26 (GMT+0200) Carlos E. R. composed:
Felix Miata wrote:
There is no need to install/remove anything.
No, but it's a logical thing to do if booting that way solves the problem(s).
I think it is preferable to leave it installed, in order to learn if the problem has been solved. I assume that all those problems are reported to Bugzilla, and I know for certain that the maintainer is quite active because I have reported several.
For a tester, I can't disagree, or for an ordinary bug. Systemd trouble is no ordinary bug, while the OP certainly seems to be no willing tester. Systemd is a whole class of bugs like KDE4.0-4.5 was, betaware foisted on users prematurely. Ordinary mortal users who need their systems to just work don't need and shouldn't be bothered by major system overhauls that are incomplete, unless the devs' goal is to get them to switch to some other distro. -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-24 17:09, Felix Miata wrote:
On 2012/04/24 15:26 (GMT+0200) Carlos E. R. composed:
Felix Miata wrote:
There is no need to install/remove anything.
No, but it's a logical thing to do if booting that way solves the problem(s).
I think it is preferable to leave it installed, in order to learn if the problem has been solved. I assume that all those problems are reported to Bugzilla, and I know for certain that the maintainer is quite active because I have reported several.
For a tester, I can't disagree, or for an ordinary bug. Systemd trouble is no ordinary bug, while the OP certainly seems to be no willing tester. Systemd is a whole class of bugs like KDE4.0-4.5 was, betaware foisted on users prematurely. Ordinary mortal users who need their systems to just work don't need and shouldn't be bothered by major system overhauls that are incomplete, unless the devs' goal is to get them to switch to some other distro.
You need to be. SystemV is going to disappear sooner or later, like it or not. There is no way around that, and I'm not saying I like it. You'd better get involved in reporting the bugs that impede you using it, because I'm not. Perhaps in a year or two there will not be systemv as backup and you will be stuck. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+W4AgACgkQIvFNjefEBxrNSwCeIWPtsCUYrXGnreQMAUmibFmk d2QAni1ANqrH843Jv1Tod3vP0iNeN50t =q4zK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/24 19:16 (GMT+0200) Carlos E. R. composed:
Felix Miata wrote:
On 2012/04/24 15:26 (GMT+0200) Carlos E. R. composed:
Felix Miata wrote:
There is no need to install/remove anything.
No, but it's a logical thing to do if booting that way solves the problem(s).
I think it is preferable to leave it installed, in order to learn if the problem has been solved. I assume that all those problems are reported to Bugzilla, and I know for certain that the maintainer is quite active because I have reported several.
For a tester, I can't disagree, or for an ordinary bug. Systemd trouble is no ordinary bug, while the OP certainly seems to be no willing tester. Systemd is a whole class of bugs like KDE4.0-4.5 was, betaware foisted on users prematurely. Ordinary mortal users who need their systems to just work don't need and shouldn't be bothered by major system overhauls that are incomplete, unless the devs' goal is to get them to switch to some other distro.
You need to be.
Need to be what? You probably should read the whole thread, including the subject, when you're fully conscious. I'm not the OP. All my 12.1 systems have sysvinit-init installed, but not all of my 12.2 systems do, so that I might be able to spot or test fixes to systemd bugs in a test environment, and not be bothered by betaware in a need to get real work done environment. -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-24 19:37, Felix Miata wrote:
On 2012/04/24 19:16 (GMT+0200) Carlos E. R. composed:
Felix Miata wrote:
For a tester, I can't disagree, or for an ordinary bug. Systemd trouble is no ordinary bug, while the OP certainly seems to be no willing tester. Systemd is a whole class of bugs like KDE4.0-4.5 was, betaware foisted on users prematurely. Ordinary mortal users who need their systems to just work don't need and shouldn't be bothered by major system overhauls that are incomplete, unless the devs' goal is to get them to switch to some other distro.
You need to be.
Need to be what?
bothered. You need to be involved and report.
You probably should read the whole thread, including the subject, when you're fully conscious.
I did, and I'm fully conscious. What are you pointing at? That I'm drunk or under narcotics effects? That's not very polite of you. :-/
I'm not the OP.
But you are defending that the OP do not report. I defend that any body having any problem with systemd report it. ANY problem, one by tedious one. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+W68sACgkQIvFNjefEBxpIjwCgyk8jxtEooerI7oR127kKOtyl TzkAoLXYPvfFzLb6SqJN5I5qK16aBW5y =5zNc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R. <robin.listas@telefonica.net> [04-24-12 14:07]:
But you are defending that the OP do not report. I defend that any body having any problem with systemd report it. ANY problem, one by tedious one.
A "Good Plan" that in the future will benefit all. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/24/2012 2:07 PM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-04-24 19:37, Felix Miata wrote:
On 2012/04/24 19:16 (GMT+0200) Carlos E. R. composed:
Felix Miata wrote:
For a tester, I can't disagree, or for an ordinary bug. Systemd trouble is no ordinary bug, while the OP certainly seems to be no willing tester. Systemd is a whole class of bugs like KDE4.0-4.5 was, betaware foisted on users prematurely. Ordinary mortal users who need their systems to just work don't need and shouldn't be bothered by major system overhauls that are incomplete, unless the devs' goal is to get them to switch to some other distro.
You need to be.
Need to be what?
bothered. You need to be involved and report.
You probably should read the whole thread, including the subject, when you're fully conscious.
I did, and I'm fully conscious. What are you pointing at? That I'm drunk or under narcotics effects?
That's not very polite of you. :-/
I'm not the OP.
But you are defending that the OP do not report. I defend that any body having any problem with systemd report it. ANY problem, one by tedious one.
And Felix was saying quite rightly that no the user does not have to do that. They can use some other distro. If enough people find systemd objectionable there will be at least one distro somewhere that either uses sysv by default, or at least maintains it as a working alternative. suse is only suse, not all of linux. Heck even within the limited scope of suse, evergreen or the evergreen version of os 12.1 or 12.2 will have to have it for as long as that's kept around so there's a suse option for quite a while yet let alone other distros. If users were clamoring for systemd then it would be reasonable to say "hey if you want systemd so bad you can at least help debug it." But the users aren't clamoring for systemd are they? No are they clamoring for features that requires systemd so they're not even demanding it indirectly without knowing it. No, a few developers and distro maintainers want it, and a very few users who are in a position to even care about such things, and they are just railroading it in. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-24 22:06, Brian K. White wrote:
And Felix was saying quite rightly that no the user does not have to do that. They can use some other distro.
All distros will have to migrate to systemd. Read this link that was posted earlier by phanisvara das: <https://plus.google.com/115547683951727699051/posts/X3fUhyJREKq>
If enough people find systemd objectionable there will be at least one distro somewhere that either uses sysv by default, or at least maintains it as a working alternative.
There will not be such luck :-( - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+XF+oACgkQIvFNjefEBxoctQCeO1AdeCHwRf2wFAZBS/rVd4QL 9tcAoK3o7Cf1XKjf+b80P0qQDUwg3itK =NmY4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/24/2012 5:15 PM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-04-24 22:06, Brian K. White wrote:
And Felix was saying quite rightly that no the user does not have to do that. They can use some other distro.
All distros will have to migrate to systemd.
Read this link that was posted earlier by phanisvara das:
<https://plus.google.com/115547683951727699051/posts/X3fUhyJREKq>
Wow what a self serving pile of crap that article is. He thinks entirely too highly of himself. The world is larger than linux too btw. Up to now, although the details varied slightly, every unix had sysv init scripts. freebsd, solaris, open server, unixware, hpux, aix... As both a software developer and as an admin/user, it was valuable that this was among the things that was consistent across all platforms. He's making Linux into exactly the same "island" he's trying to accuse ubuntu of becoming. What a douchbag. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Brian K. White said the following on 04/24/2012 06:43 PM:
The world is larger than linux too btw. Up to now, although the details varied slightly, every unix had sysv init scripts. freebsd, solaris, open server, unixware, hpux, aix...
Once upon a time they didn't. And some of the BSD-tree still don't. -- Everything that is really great and inspiring is created by the individual who can labor in freedom. -- Albert Einstein, in H. Eves Return to Mathematical Circles, Boston: Prindle, Weber and Schmidt, 1988. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/24 20:07 (GMT+0200) Carlos E. R. composed:
On 2012-04-24 19:37, Felix Miata wrote:
On 2012/04/24 19:16 (GMT+0200) Carlos E. R. composed:
Felix Miata wrote:
For a tester, I can't disagree, or for an ordinary bug. Systemd trouble is no ordinary bug, while the OP certainly seems to be no willing tester. Systemd is a whole class of bugs like KDE4.0-4.5 was, betaware foisted on users prematurely. Ordinary mortal users who need their systems to just work don't need and shouldn't be bothered by major system overhauls that are incomplete, unless the devs' goal is to get them to switch to some other distro.
You probably should read the whole thread, including the subject, when you're fully conscious.
I did
By "whole thread" I didn't mean thread in the customary sense, and so it didn't and doesn't seem like you did. I meant within the context of all threads on the same general subject initiated by the OP, which go back several weeks; threads on which the OP followed up instead of leaving the rest of us so inclined to speculate and discuss without his further input. If that's in fact what you did, you might have recognized and agreed with my perception that the OP is just not the type of person to get involved in development issues like recognizing bugs as bugs or filing useful bug reports, much less following up on any he might file. Bug reports are best limited as much as practicable to being filed by those both willing, and able, to do follow-through. The OP just wants a 12.1 install that works as well as his 11.4 does, and doesn't seem the type to deal with bugs beyond what's absolutely necessary to work around the ones he cannot avoid. His goal seems perfectly reasonable, and particularly topical to this list.
I'm not the OP.
But you are defending that the OP do not report. I defend that any body having any problem with systemd report it. ANY problem, one by tedious one.
You have your opinion. I stand by mine. As Brian K. White wrote in reply to you, like I wrote earlier, some people are just not meant to be bug reporters, and are likely to jump distros rather than be bothered if pushed to do so. Remember, this is a general purpose (English) user help list, not a devel list. Focus here should be on helping people get through their problems, not recruiting them to be beta testers, which is what anyone pushing people to get involved solving systemd's problems is doing. -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/24 19:16 (GMT+0200) Carlos E. R. composed:
Felix Miata wrote:
On 2012/04/24 15:26 (GMT+0200) Carlos E. R. composed:
Felix Miata wrote:
There is no need to install/remove anything.
No, but it's a logical thing to do if booting that way solves the problem(s).
I think it is preferable to leave it installed, in order to learn if the problem has been solved. I assume that all those problems are reported to Bugzilla, and I know for certain that the maintainer is quite active because I have reported several.
For a tester, I can't disagree, or for an ordinary bug. Systemd trouble is no ordinary bug, while the OP certainly seems to be no willing tester. Systemd is a whole class of bugs like KDE4.0-4.5 was, betaware foisted on users prematurely. Ordinary mortal users who need their systems to just work don't need and shouldn't be bothered by major system overhauls that are incomplete, unless the devs' goal is to get them to switch to some other distro.
You need to be.
Need to be what? You probably should carefully read the whole thread, including the subject, when you're fully conscious. I'm not the OP. All my 12.1 systems have sysvinit-init installed, but not all of my 12.2 systems do, so that I might be able to spot or test fixes to systemd bugs in a test environment, and not be bothered by betaware in a need to get real work done environment. https://bugzilla.novell.com/show_bug.cgi?id=746594 https://bugzilla.novell.com/show_bug.cgi?id=746595 -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/24/12 13:16, Carlos E. R. pecked at the keyboard and wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-04-24 17:09, Felix Miata wrote:
On 2012/04/24 15:26 (GMT+0200) Carlos E. R. composed:
Felix Miata wrote:
There is no need to install/remove anything.
No, but it's a logical thing to do if booting that way solves the problem(s).
I think it is preferable to leave it installed, in order to learn if the problem has been solved. I assume that all those problems are reported to Bugzilla, and I know for certain that the maintainer is quite active because I have reported several.
For a tester, I can't disagree, or for an ordinary bug. Systemd trouble is no ordinary bug, while the OP certainly seems to be no willing tester. Systemd is a whole class of bugs like KDE4.0-4.5 was, betaware foisted on users prematurely. Ordinary mortal users who need their systems to just work don't need and shouldn't be bothered by major system overhauls that are incomplete, unless the devs' goal is to get them to switch to some other distro.
You need to be.
SystemV is going to disappear sooner or later, like it or not. There is no way around that, and I'm not saying I like it. You'd better get involved in reporting the bugs that impede you using it, because I'm not. Perhaps in a year or two there will not be systemv as backup and you will be stuck.
In a year or two it should be out of alpha/beta stage. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-24 20:52, Ken Schneider - openSUSE wrote:
In a year or two it should be out of alpha/beta stage.
There are things not supported and no intention to. For example, hylafax. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+XGEkACgkQIvFNjefEBxqcQgCgkXeqZr2e+aT0FkGTzNJX9drN +q4AoK8vDIshesGyipHudGndpuRo4P5W =0BEV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-04-24 20:52, Ken Schneider - openSUSE wrote:
In a year or two it should be out of alpha/beta stage.
There are things not supported and no intention to. For example, hylafax.
What's the story wrt Hylafax? Fighting the windmills? -- Per Jessen, Zürich (6.5°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-25 08:30, Per Jessen wrote:
Carlos E. R. wrote:
On 2012-04-24 20:52, Ken Schneider - openSUSE wrote:
In a year or two it should be out of alpha/beta stage.
There are things not supported and no intention to. For example, hylafax.
What's the story wrt Hylafax? Fighting the windmills?
You can read the thread in a recent post. Hylafax uses a line in inittab, which is not supported in systemd. Aparently, their developers do not intend, or even can not, upgrade to systemd. <http://lists.opensuse.org/opensuse/2012-04/msg00158.html> Another question would be "getty" lines. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+X0qIACgkQIvFNjefEBxpGswCfTNEBCc66bG1PT1NcERzNf0zZ Q0sAn0bC6TbkD/liDQPzisNVuytwOkG5 =YnZE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-04-25 08:30, Per Jessen wrote:
Carlos E. R. wrote:
On 2012-04-24 20:52, Ken Schneider - openSUSE wrote:
In a year or two it should be out of alpha/beta stage.
There are things not supported and no intention to. For example, hylafax.
What's the story wrt Hylafax? Fighting the windmills?
You can read the thread in a recent post.
I cant keep up with everything here :-)
Hylafax uses a line in inittab, which is not supported in systemd. Aparently, their developers do not intend, or even can not, upgrade to systemd.
Dear oh dear, heretics! Doesn't seem like a big deal though. Om my telephone exchange, I've got faxgetty and iaxmodem running via inittab - it seems both could be replaced by endless loops running faxgetty and iaxmodem? -- Per Jessen, Zürich (13.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Carlos E. R. wrote:
Hylafax uses a line in inittab, which is not supported in systemd. Aparently, their developers do not intend, or even can not, upgrade to systemd.
Dear oh dear, heretics!
Doesn't seem like a big deal though. Om my telephone exchange, I've got faxgetty and iaxmodem running via inittab - it seems both could be replaced by endless loops running faxgetty and iaxmodem?
Seems it been solved here: http://lists.opensuse.org/opensuse/2012-04/msg00229.html -- Per Jessen, Zürich (13.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-25 12:45, Per Jessen wrote:
Per Jessen wrote:
Carlos E. R. wrote:
Hylafax uses a line in inittab, which is not supported in systemd. Aparently, their developers do not intend, or even can not, upgrade to systemd.
Dear oh dear, heretics!
:-)
Doesn't seem like a big deal though. Om my telephone exchange, I've got faxgetty and iaxmodem running via inittab - it seems both could be replaced by endless loops running faxgetty and iaxmodem?
Perhaps.
Seems it been solved here:
I know, but it is not in the package. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+X2MkACgkQIvFNjefEBxpiyACeJZOQZTIeXIse5R2d2U4LDWtD ce8AoNUekTwsiEQR6iAXK2ZPLfx0RQG6 =ndL3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Ken Schneider - openSUSE said the following on 04/24/2012 02:52 PM:
In a year or two it should be out of alpha/beta stage.
I'm running Fedora-15 with systemd on another machine. I have been since -15 came out. Even from the start I haven't encountered or been able to replicate on the fedora box the problems with systemd that have been described here. My laptop still runs 11.4 .... I don't prefer fedora. I *do* prefer the management systems available under suse: what's under /etc/sysconfig, zypper and the like. I'm ambiguous about _some_ aspects of YAST, but prefer them to what I have under fedora. But fedora is stable and reliable with systemd. I don't think its a alpha/beta issue. It may be a matter of integration, but that's another topic. About fedora-16 I don't know. I'm not committed to redhat. When I got this machine I decided to play with other distributions and saw the postings here about problems with systemd about the time I was installing fedora and stayed with fedora "just to see ..." Systemd works and works well. On fedora. Maybe I'll get another machine and try 12.1 or 12.2 and see if its my "magic fingers" or if there really are problems with systemd on suse. Because there sure aren't the problems I see reported for 12.1 on this fedora-15 I'm running! -- Some day, on the corporate balance sheet, there will be an entry which reads, "Information"; for in most cases the information is more valuable than the hardware which processes it. - Adm. Grace Murray Hopper, USN Ret. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 2012-04-24 at 19:00 -0400, Anton Aylward wrote:
Ken Schneider - openSUSE said the following on 04/24/2012 02:52 PM:
In a year or two it should be out of alpha/beta stage.
I'm running Fedora-15 with systemd on another machine. I have been since -15 came out. Even from the start I haven't encountered or been able to replicate on the fedora box the problems with systemd that have been described here.
My laptop still runs 11.4 ....
I don't prefer fedora. I *do* prefer the management systems available under suse: what's under /etc/sysconfig, zypper and the like. I'm ambiguous about _some_ aspects of YAST, but prefer them to what I have under fedora.
But fedora is stable and reliable with systemd. I don't think its a alpha/beta issue. It may be a matter of integration, but that's another topic.
About fedora-16 I don't know. I'm not committed to redhat. When I got this machine I decided to play with other distributions and saw the postings here about problems with systemd about the time I was installing fedora and stayed with fedora "just to see ..."
Systemd works and works well. On fedora.
Maybe I'll get another machine and try 12.1 or 12.2 and see if its my "magic fingers" or if there really are problems with systemd on suse. Because there sure aren't the problems I see reported for 12.1 on this fedora-15 I'm running!
I am certainly not against change _if_ it leads towards improvement. But some aspects in 12.1 still needs looking after. And the transition could be somewhat more user friendly: For ages i'm used to do /etc/rc.d/daemon_name "start|stop" I know that there are lots of pages on the net explaining how to do that incase you missed the "F5" button, but some of those pages definitely are in need of reviewing ;-[*] probably my bad luck of choosing the wrong ones. There are third party-product that only describe (re)starting/stopping the systemv-way in their manuals. In case systemd is used, it would be handy that _if_ you were issuing a systemV-command it would either translate it into the proper systemd-equivalent, Or at least give a hint. sometimes you are at places where you have no way of accessing the net. Aren't we doing that now if you type the name of a command that you didn't install? (just a thought..) Regarding Fedora: Your version might appear "stable and reliable", but regarding more recently versions, the opinion on their own list indicate otherwise, to put it _very_ mildly. If you read those stories you would almost feel sorry for them, almost i said. So i'm certainly not against systemd, but untill everything works 100% i would rather see it not used as installed as default. Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 25 Apr 2012 13:23:51 +0530, Hans Witvliet <suse@a-domani.nl> wrote:
In case systemd is used, it would be handy that _if_ you were issuing a systemV-command it would either translate it into the proper systemd-equivalent, Or at least give a hint. sometimes you are at places where you have no way of accessing the net.
but that's exactly what's happening. i'm running with systemd at present (had to switch back to sysvinit a while ago because my network wouldn't come up, but that's been fixed now): ------------------- phani:~ # /etc/init.d/squid status redirecting to systemctl squid.service - LSB: Squid web cache Loaded: loaded (/etc/init.d/squid) Active: active (running) since Wed, 25 Apr 2012 08:32:01 +0530; 5h 23min ago Process: 5284 ExecReload=/etc/init.d/squid reload (code=exited, status=0/SUCCESS) Process: 3989 ExecStart=/etc/init.d/squid start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/squid.service ├ 4003 /usr/sbin/squid -sY ├ 4005 (squid) -sY └ 4006 (unlinkd) phani:~ # ------------------- apart from providing the asked for information, it also tells me the correct systemd service to query, i.e., the new command would be systemctl status squid.service -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 2012-04-24 at 10:42 +0200, Per Jessen wrote:
Duaine Hechler wrote:
The one with working sound has sysvinit-init installed. The one with non-working sound doesn't. I have no recollection if there's anything else that distinguishes the two other than installation and updates made at different times. According to the release notes (wherever they disappeared to), more than one problem may be solved by installing sysvinit-init, which replaces the buggy immature systemd init system.
So who do I install with sysvinit-init installed ?
You do a normal install, and press F5 during the boot-up.
I noticed that @12.1 systemd is default, but you can change it at boot time with the F5. Isn't there the possibility to do sysv-init by default? I've been searching through yast, you can change a quite some boot-options, but missed something like that... Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-24 23:26, Hans Witvliet wrote:
Isn't there the possibility to do sysv-init by default? I've been searching through yast, you can change a quite some boot-options, but missed something like that...
I said how several posts ago. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+XG4MACgkQIvFNjefEBxpuwwCg13JR9czH1QBA2MNoNV+HWluk 1G8AoMjcmogHbqO0xO7OV2/pb8FcirXl =D+xg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/22/2012 08:59 PM, Duaine Hechler wrote:
with the following conditions fixed.
I would like to here from persons that have had these problems fixed.
- Can't get my MB sound card to work (Intel ICH7) consistent.
So far so good.... the "init=/sbin/sysvinit" seems to have done the trick for the sound. Developers REALLY need to work on "systemd"
- alsasound will not stay "yes" in the system service levels.
Seems to be fixed from above fix
- rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active.
Seems to be fixed from above fix
- Can't get my display to stay at 1024x768
Did nothing but at install time, do F3 at 1024x768... still sticking.
- Can't get rid of the "Nepomuk Indexing Disabled) popups
Try to edit ~/.config/akonadi/akonadiserverrc and turn StartServer=true to StartServer=false
TIA, Duaine
-- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/25 01:49 (GMT-0500) Duaine Hechler composed:
Duaine Hechler wrote:
with the following conditions fixed.
I would like to here from persons that have had these problems fixed.
- Can't get my MB sound card to work (Intel ICH7) consistent.
So far so good.... the "init=/sbin/sysvinit" seems to have done the trick for the sound.
Developers REALLY need to work on "systemd"
- alsasound will not stay "yes" in the system service levels.
Seems to be fixed from above fix
- rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active.
Seems to be fixed from above fix
Needing an extra cmdline option is a workaround, not a fix. The real (current) fix is in the release notes, installing sysvinit-init, which makes the extra cmdline option unnecessary. http://www.suse.com/releasenotes/i386/openSUSE/12.1/RELEASE-NOTES.en.html#12
- Can't get my display to stay at 1024x768
Did nothing but at install time, do F3 at 1024x768... still sticking.
I don't think you ever explained your rationale for running 1024x768 on a native 1280x1024 display. If all you want is for everything to be bigger, forcing DPI (at the system level, via /etc/X11/xorg.conf*, not via your display manager's desktop preferences) can do and often does a more thorough and higher quality job of it. Forcing DPI amounts to a zoom control that retains the pixel precision of the display's native/preferred mode, and in the 1280x1024 vs. 1024x768 case, retains correct aspect ratio so that images are not materially distorted. http://fm.no-ip.com/PC/aspect.html -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 25 Apr 2012 14:16:13 +0530, Felix Miata <mrmazda@earthlink.net> wrote:
Needing an extra cmdline option is a workaround, not a fix. The real (current) fix is in the release notes, installing sysvinit-init, which makes the extra cmdline option unnecessary. http://www.suse.com/releasenotes/i386/openSUSE/12.1/RELEASE-NOTES.en.html#12
is there any real benefit of installing that package over adding that command line option, i.e., are there any penalties for running with this option in grub, except that it's 'politically correct' to install the package? i find it much easier to switch between sysvinit & systemd by just changing the cmdline, instead of in- or uninstalling a package... -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-25 11:09, phanisvara das wrote:
On Wed, 25 Apr 2012 14:16:13 +0530, Felix Miata <> wrote:
is there any real benefit of installing that package over adding that command line option, i.e., are there any penalties for running with this option in grub, except that it's 'politically correct' to install the package?
Not that I know.
i find it much easier to switch between sysvinit & systemd by just changing the cmdline, instead of in- or uninstalling a package...
Indeed. That command line is just what pressing F5 does, but made permanent, and is easier to undo. I keep two sections in grub, one with each mode, and can select each one permanently by changing the default boot entry. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+X1gsACgkQIvFNjefEBxq2JACeN9vpjo/AMHfQLivnNxzXVstO 6KcAoL1agR80FSAXNNpx3TjnT2clmQqs =0kip -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/25/2012 03:46 AM, Felix Miata wrote:
<snip>
- Can't get my display to stay at 1024x768
Did nothing but at install time, do F3 at 1024x768... still sticking.
I don't think you ever explained your rationale for running 1024x768 on a native 1280x1024 display. If all you want is for everything to be bigger, forcing DPI (at the system level, via /etc/X11/xorg.conf*, not via your display manager's desktop preferences) can do and often does a more thorough and higher quality job of it.
Forcing DPI amounts to a zoom control that retains the pixel precision of the display's native/preferred mode, and in the 1280x1024 vs. 1024x768 case, retains correct aspect ratio so that images are not materially distorted. http://fm.no-ip.com/PC/aspect.html It's very simple - I, permanently, don't want to see - everything - that small. I like 1024 x 768.
As far as aspect goes - nothing is distorted ! And, as for as the xorg.config, it's - NOT - in control: dahechler:~ # cat /etc/X11/xorg.conf.d/50-screen.conf # Having multiple "Screen" sections is known to be problematic. Make # sure you don't have in use another one laying around e.g. in another # xorg.conf.d file or even a generic xorg.conf file. More details can # be found in https://bugs.freedesktop.org/show_bug.cgi?id=32430. # #Section "Screen" # Identifier "Default Screen" # # Device "Default Device" # # ## Doesn't help for radeon/radeonhd drivers; use magic in # ## 50-device.conf instead # Monitor "Default Monitor" # #EndSection -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 25 Apr 2012 04:29:32 -0500 Duaine Hechler <dahechler@att.net> wrote:
It's very simple - I, permanently, don't want to see - everything - that small. I like 1024 x 768.
Hi Duane, Excuse me for intruding if you already know this stuff, but I'm providing it in case you don't so you can make a fully informed decision. The whole point of adjusting DPI while leaving the display at native resolution is to make "everything" exactly the size that you want it, be that larger (for people like me who hate squinting while wearing reading glasses) *or* smaller (as I used to configure my old, lower resolution displays to get as much working 'real estate' as possible ... before I needed reading glasses.) #1) 1,280 x 1,024 is a 5:4 aspect ratio, meaning there are five physical pixels across for every four vertical pixels: . . . . . . . . . . . . . . . . . . . . #2) 1,024 x 768 is a 4:3 aspect ratio, meaning there are four physical pixels across for every three vertical pixels: . . . . . . . . . . . . #3) 1,280 x 1,024 is 'more square' to the eye than 1,024 x 768 #4) Forcing your 1,280 x 1,024 display to emulate 1,024 x 768 pixels can only be accomplished in two ways: a. the emulated 4:3 display field is 'stretched to fit' the native 5:4 resolution and this distorts the output. It causes circles to appear as ellipses and squares to appear as rectangles. b. activating only the center 1,024 x 768 pixels avoids the distortions but it leaves a band (or 'fat border') of unused pixels at the perimeter of the display, thereby *reducing* available workspace. #5) If you run the display at it's native resolution of 1,280 x 1,024, it is then possible to adjust the DPI (dots per inch) setting to make literally "everything," page size, fonts and graphics included, larger or smaller to suit your taste. This approach uses all the available display 'real estate' while keeping circles round and squares square. At 120 DPI a bitmap of 360 x 360 pixels displays as a 3" square At 96 DPI the same graphic displays as a 3.75" square (larger) At 72 DPI it displays as a 5" square ... much larger This is the "zoom" effect that Felix alluded to. Of course, the system belongs to you and you're free to configure it any way you want. I've just guessed from your response that you hadn't quite 'grokked' what Felix was trying to explain. hth & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/25/2012 06:24 AM, Carl Hartung wrote:
On Wed, 25 Apr 2012 04:29:32 -0500 Duaine Hechler<dahechler@att.net> wrote:
It's very simple - I, permanently, don't want to see - everything - that small. I like 1024 x 768. Hi Duane,
Excuse me for intruding if you already know this stuff, but I'm providing it in case you don't so you can make a fully informed decision.
The whole point of adjusting DPI while leaving the display at native resolution is to make "everything" exactly the size that you want it, be that larger (for people like me who hate squinting while wearing reading glasses) *or* smaller (as I used to configure my old, lower resolution displays to get as much working 'real estate' as possible ... before I needed reading glasses.)
#1) 1,280 x 1,024 is a 5:4 aspect ratio, meaning there are five physical pixels across for every four vertical pixels:
. . . . . . . . . . . . . . . . . . . .
#2) 1,024 x 768 is a 4:3 aspect ratio, meaning there are four physical pixels across for every three vertical pixels:
. . . . . . . . . . . .
#3) 1,280 x 1,024 is 'more square' to the eye than 1,024 x 768
#4) Forcing your 1,280 x 1,024 display to emulate 1,024 x 768 pixels can only be accomplished in two ways:
a. the emulated 4:3 display field is 'stretched to fit' the native 5:4 resolution and this distorts the output. It causes circles to appear as ellipses and squares to appear as rectangles.
b. activating only the center 1,024 x 768 pixels avoids the distortions but it leaves a band (or 'fat border') of unused pixels at the perimeter of the display, thereby *reducing* available workspace.
#5) If you run the display at it's native resolution of 1,280 x 1,024, it is then possible to adjust the DPI (dots per inch) setting to make literally "everything," page size, fonts and graphics included, larger or smaller to suit your taste. This approach uses all the available display 'real estate' while keeping circles round and squares square.
At 120 DPI a bitmap of 360 x 360 pixels displays as a 3" square
At 96 DPI the same graphic displays as a 3.75" square (larger)
At 72 DPI it displays as a 5" square ... much larger
This is the "zoom" effect that Felix alluded to.
Of course, the system belongs to you and you're free to configure it any way you want. I've just guessed from your response that you hadn't quite 'grokked' what Felix was trying to explain.
hth& regards,
Carl No, I don't fully understand this because:
a) Yes, I understand aspect ratios b) I've been running 1024x768 for about 5 or more years c) The monitor is not emulating anything. When I hit the monitors settings button, it says that it is displaying at 1024 x 768, although it says "Optimum" 1280 x 1024. So the monitor is displaying what it's set for. d) Everything seems to be displayed correctly - circles are circles and squares are squares - so nothing is getting "stretched" Duaine -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-25 20:07, Duaine Hechler wrote:
c) The monitor is not emulating anything. When I hit the monitors settings button, it says that it is displaying at 1024 x 768, although it says "Optimum" 1280 x 1024. So the monitor is displaying what it's set for.
If your monitor is not a CRT, and it says that the optimum is 1280 x 1024, you must run it at that resolution, any other is emulated and wrong. This is an important difference compared with CRTs. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+YUL0ACgkQIvFNjefEBxovlACeL9JpKH0LqD7sASAg4PqAXckR rAAAoMNxTtp0fKhJ69RefeYNk+F2VIP2 =T+0p -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 25 Apr 2012 13:07:16 -0500 Duaine Hechler <dahechler@att.net> wrote: <snipped>
No, I don't fully understand this because:
a) Yes, I understand aspect ratios
b) I've been running 1024x768 for about 5 or more years
c) The monitor is not emulating anything. When I hit the monitors settings button, it says that it is displaying at 1024 x 768, although it says "Optimum" 1280 x 1024. So the monitor is displaying what it's set for.
d) Everything seems to be displayed correctly - circles are circles and squares are squares - so nothing is getting "stretched"
Duaine
Hi Duaine, Then you have a 'multisync' style monitor; one designed to handle a range of standard display inputs (i.e. VGA, SVGA, XGA and so on.) The "optimum" setting says the best performing (or "native") mode is SXGA, 1,280 x 1,024. This basically means that's the mode that uses the full 5:4 active display area. Since you're running it at a lower resolution, XGA, the scenario "b" that I described earlier is in play. Bottom line? If you're happy with your current settings by all means keep them. If you're doing digital photography or other "serious" graphics work, you might want to think about checking out the "optimum" mode with a lower DPI if items on the screen get too small. regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/25/2012 2:07 PM, Duaine Hechler wrote:
On 04/25/2012 06:24 AM, Carl Hartung wrote:
On Wed, 25 Apr 2012 04:29:32 -0500 Duaine Hechler<dahechler@att.net> wrote:
It's very simple - I, permanently, don't want to see - everything - that small. I like 1024 x 768. Hi Duane,
Excuse me for intruding if you already know this stuff, but I'm providing it in case you don't so you can make a fully informed decision.
The whole point of adjusting DPI while leaving the display at native resolution is to make "everything" exactly the size that you want it, be that larger (for people like me who hate squinting while wearing reading glasses) *or* smaller (as I used to configure my old, lower resolution displays to get as much working 'real estate' as possible ... before I needed reading glasses.)
#1) 1,280 x 1,024 is a 5:4 aspect ratio, meaning there are five physical pixels across for every four vertical pixels:
. . . . . . . . . . . . . . . . . . . .
#2) 1,024 x 768 is a 4:3 aspect ratio, meaning there are four physical pixels across for every three vertical pixels:
. . . . . . . . . . . .
#3) 1,280 x 1,024 is 'more square' to the eye than 1,024 x 768
#4) Forcing your 1,280 x 1,024 display to emulate 1,024 x 768 pixels can only be accomplished in two ways:
a. the emulated 4:3 display field is 'stretched to fit' the native 5:4 resolution and this distorts the output. It causes circles to appear as ellipses and squares to appear as rectangles.
b. activating only the center 1,024 x 768 pixels avoids the distortions but it leaves a band (or 'fat border') of unused pixels at the perimeter of the display, thereby *reducing* available workspace.
#5) If you run the display at it's native resolution of 1,280 x 1,024, it is then possible to adjust the DPI (dots per inch) setting to make literally "everything," page size, fonts and graphics included, larger or smaller to suit your taste. This approach uses all the available display 'real estate' while keeping circles round and squares square.
At 120 DPI a bitmap of 360 x 360 pixels displays as a 3" square
At 96 DPI the same graphic displays as a 3.75" square (larger)
At 72 DPI it displays as a 5" square ... much larger
This is the "zoom" effect that Felix alluded to.
Of course, the system belongs to you and you're free to configure it any way you want. I've just guessed from your response that you hadn't quite 'grokked' what Felix was trying to explain.
hth& regards,
Carl No, I don't fully understand this because:
a) Yes, I understand aspect ratios
b) I've been running 1024x768 for about 5 or more years
c) The monitor is not emulating anything. When I hit the monitors settings button, it says that it is displaying at 1024 x 768, although it says "Optimum" 1280 x 1024. So the monitor is displaying what it's set for.
d) Everything seems to be displayed correctly - circles are circles and squares are squares - so nothing is getting "stretched"
Duaine
It IS getting stretched. The monitor IS "emulating" 1024x768. A 1024x768 pixel does not exactly align with _any_ of the pixels on your display. Every pixel of 1024x768 information is being displayed as some closest approximation of some small group of the monitors 1280x1024 pixels. They are saying that the most technically correct way to get what you want, larger text, icons, and widgets, is to tell the X server the correct size of you monitor so that it can correctly scale the things it displays to you. It will do a better job and produce cleaner imagery than letting the monitor scale everything. But all that said, you should still be free to do it the "wrong" way if you want. Forcing the monitor to scale an arbitrary incoming signal to fill the screen is crude but entirely your prerogative. I kind of wish more of the answers would tackle the question you asked instead of trying to get you to accept an answer to a question you didn't ask. But I'm guilty of doing that myself if I think the asker has no idea what they're asking about. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/25/2012 04:10 PM, Brian K. White wrote:
<snip> It IS getting stretched.
The monitor IS "emulating" 1024x768. A 1024x768 pixel does not exactly align with _any_ of the pixels on your display. Every pixel of 1024x768 information is being displayed as some closest approximation of some small group of the monitors 1280x1024 pixels.
They are saying that the most technically correct way to get what you want, larger text, icons, and widgets, is to tell the X server the correct size of you monitor so that it can correctly scale the things it displays to you. It will do a better job and produce cleaner imagery than letting the monitor scale everything.
But all that said, you should still be free to do it the "wrong" way if you want. Forcing the monitor to scale an arbitrary incoming signal to fill the screen is crude but entirely your prerogative. I kind of wish more of the answers would tackle the question you asked instead of trying to get you to accept an answer to a question you didn't ask. But I'm guilty of doing that myself if I think the asker has no idea what they're asking about.
So with that being said, how do I - easily - change the DPI ? Is it in YAST ? Thanks, Duaine -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/25 16:30 (GMT-0500) Duaine Hechler composed:
So with that being said, how do I - easily - change the DPI ? Is it in YAST ?
There is no "easy" if you want 100% success. The "easy" (simplest) way depends on desktop environment. In KDE, there's a "force fonts DPI" chooser in the fonts panel in system (aka personal) settings. Gnome 2 had something similar in Gnome Control Center, which I think had name changes since. Because there are gotchas, I recommend you only try this to see how you like the results of forcing DPI, and to find out what number pleases you most - after setting the display back to its native/preferred mode. Once you know what DPI works best for you while in native mode, the overall across all apps and toolkits and user logins more thorough and effective, and definitely less than easy, method is via /etc/X11/xorg.conf*. How to do it there is not uniform across all display drivers. The place to tweak is 'Section "Monitor"'. If using an NVidia binary driver, you very logically place 'Option "DPI" "100 x 100"' using whatever DPI number you want, check below for general instruction where and how to place it, and restart X. Absent NVidia binaries, it's more complicated, because it's most thoroughly done via DisplaySize. To get accurate DPI, you use the physical height and width of your display, but in your case of wanting everything bigger, you must lie about the sizes, telling X the sizes are _smaller_ than they actually are. Rather than making the necessary calculations to arrive at the required mm dimensions, you may be able to look suitable ones up in my DisplaySize cheat file[1] where I list the display dimensions that correlate to various combinations of resolution and desired target DPI, mostly multiples of 12, such as 72, 96, 108, 120, 132, 144, plus various others. The file includes an explanation why to prefer a multiple of 12. Rather than putting all the required components into xorg.conf so that it parses correctly, it's supposed to be somewhat simpler to use the files in xorg.conf.d/, 50-device.conf, 50-monitor.conf and 50-screen.conf, with elementary content as follows: # 50-device.conf Section "Device" Identifier "Default Device" EndSection # 50-monitor.conf Section "Monitor" Identifier "Default Monitor" Option "DefaultModes" "on" # only sometimes necessary # DisplaySize 338 270 # 096 DPI @ 1280x1024 (typical size of 17" LCD) DisplaySize 270 216 # 120 DPI @ 1280x1024 (to make things 25% bigger) Option "PreferredMode" "1280x1024" # insurance, probably unnecessary EndSection # 50-screen.conf Section "Screen" Identifier "Default Screen" Device "Default Device" Monitor "Default Monitor" EndSection Those three files are installed by default in 12.1, but include nothing but comments. To use them, uncomment the required lines, add the necessary addition(s) (minimally, a DisplaySize line), and restart X. Combining the three above files into one xorg.conf file should produce the same result as the three individual files, but preserve the originals in their unused and inert state. [1] http://fm.no-ip.com/Share/DisplaySize -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/25/2012 05:27 PM, Felix Miata wrote:
On 2012/04/25 16:30 (GMT-0500) Duaine Hechler composed:
So with that being said, how do I - easily - change the DPI ? Is it in YAST ?
There is no "easy" if you want 100% success.
The "easy" (simplest) way depends on desktop environment. In KDE, there's a "force fonts DPI" chooser in the fonts panel in system (aka personal) settings. Gnome 2 had something similar in Gnome Control Center, which I think had name changes since. Because there are gotchas, I recommend you only try this to see how you like the results of forcing DPI, and to find out what number pleases you most - after setting the display back to its native/preferred mode.
Once you know what DPI works best for you while in native mode, the overall across all apps and toolkits and user logins more thorough and effective, and definitely less than easy, method is via /etc/X11/xorg.conf*. How to do it there is not uniform across all display drivers.
The place to tweak is 'Section "Monitor"'.
If using an NVidia binary driver, you very logically place 'Option "DPI" "100 x 100"' using whatever DPI number you want, check below for general instruction where and how to place it, and restart X.
Absent NVidia binaries, it's more complicated, because it's most thoroughly done via DisplaySize. To get accurate DPI, you use the physical height and width of your display, but in your case of wanting everything bigger, you must lie about the sizes, telling X the sizes are _smaller_ than they actually are. Rather than making the necessary calculations to arrive at the required mm dimensions, you may be able to look suitable ones up in my DisplaySize cheat file[1] where I list the display dimensions that correlate to various combinations of resolution and desired target DPI, mostly multiples of 12, such as 72, 96, 108, 120, 132, 144, plus various others. The file includes an explanation why to prefer a multiple of 12.
Rather than putting all the required components into xorg.conf so that it parses correctly, it's supposed to be somewhat simpler to use the files in xorg.conf.d/, 50-device.conf, 50-monitor.conf and 50-screen.conf, with elementary content as follows:
# 50-device.conf Section "Device" Identifier "Default Device" EndSection
# 50-monitor.conf Section "Monitor" Identifier "Default Monitor" Option "DefaultModes" "on" # only sometimes necessary # DisplaySize 338 270 # 096 DPI @ 1280x1024 (typical size of 17" LCD) DisplaySize 270 216 # 120 DPI @ 1280x1024 (to make things 25% bigger) Option "PreferredMode" "1280x1024" # insurance, probably unnecessary EndSection
# 50-screen.conf Section "Screen" Identifier "Default Screen" Device "Default Device" Monitor "Default Monitor" EndSection
Those three files are installed by default in 12.1, but include nothing but comments. To use them, uncomment the required lines, add the necessary addition(s) (minimally, a DisplaySize line), and restart X. Combining the three above files into one xorg.conf file should produce the same result as the three individual files, but preserve the originals in their unused and inert state.
Well, Felix, Back to the drawing board ! ! ! ! I coded all three files just like above and rebooted each time with each of the DPI settings...... and .... guess what .... each time the monitor came back up in 1024 x 768 mode (even the display (hardware) menu confirms it) So .... now what ? ? ? ? 14: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.319] Unique ID: _Znp.R9e4vZ5lsP8 SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Intel 4 Series Chipset Integrated Graphics Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2e32 "4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x836d Revision: 0x03 Driver: "i915" Driver Modules: "drm" Memory Range: 0xfb800000-0xfbbfffff (rw,non-prefetchable) Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable) I/O Ports: 0xdc00-0xdc07 (rw) IRQ: 42 (7384 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v00008086d00002E32sv00001043sd0000836Dbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=no, avail=yes, need=no, active=unknown -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/25 23:30 (GMT-0500) Duaine Hechler composed:
Well, Felix, Back to the drawing board ! ! ! !
I coded all three files just like above and rebooted each time with each of the DPI settings......
You don't need to reboot. Restarting X is enough. Booting only to runlevel 3 (add 3 to grub line each time you want no KDM during that boot) and using startx instead of KDM makes this kind of testing easier and faster.
and .... guess what .... each time the monitor came back up in 1024 x 768 mode (even the display (hardware) menu confirms it)
So .... now what ? ? ? ?
It was never completely clear to me where or how you were forcing 1024x768. If you were doing it from within KDE system/personal settings only, or with xrandr or krandrtray, you need to reset it/them to pick up resolution (and DPI) automatically from Xorg like is done by default when xorg.conf doesn't exist. -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/25/2012 11:46 PM, Felix Miata wrote:
On 2012/04/25 23:30 (GMT-0500) Duaine Hechler composed:
Well, Felix, Back to the drawing board ! ! ! !
I coded all three files just like above and rebooted each time with each of the DPI settings......
You don't need to reboot. Restarting X is enough. Booting only to runlevel 3 (add 3 to grub line each time you want no KDM during that boot) and using startx instead of KDM makes this kind of testing easier and faster.
I first tried restarting X - but - that did not do a thing !
and .... guess what .... each time the monitor came back up in 1024 x 768 mode (even the display (hardware) menu confirms it)
So .... now what ? ? ? ?
It was never completely clear to me where or how you were forcing 1024x768. If you were doing it from within KDE system/personal settings only, or with xrandr or krandrtray, you need to reset it/them to pick up resolution (and DPI) automatically from Xorg like is done by default when xorg.conf doesn't exist.
All I did was two things (1) at install time did the F3(?) and changed to 1024x768 and (2) used the KDE personal settings to 1024 x 768. That's it. -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/25 23:51 (GMT-0500) Duaine Hechler composed:
Felix Miata wrote:
You don't need to reboot. Restarting X is enough. Booting only to runlevel 3 (add 3 to grub line each time you want no KDM during that boot) and using startx instead of KDM makes this kind of testing easier and faster.
I first tried restarting X - but - that did not do a thing !
...
It was never completely clear to me where or how you were forcing 1024x768. If you were doing it from within KDE system/personal settings only, or with xrandr or krandrtray, you need to reset it/them to pick up resolution (and DPI) automatically from Xorg like is done by default when xorg.conf doesn't exist.
All I did was two things (1) at install time did the F3(?) and changed to 1024x768 and (2) used the KDE personal settings to 1024 x 768.
(1) only affects the mode used on the ttys during and post-installation, and the mode used by the X portion of installation; nothing to do with X post-installation (2) KDE is overriding settings you made in /etc/X11/xorg.con* and the automagic that Xorg would otherwise have used -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/26/2012 01:04 AM, Felix Miata wrote:
All I did was two things (1) at install time did the F3(?) and changed to 1024x768 and (2) used the KDE personal settings to 1024 x 768.
(1) only affects the mode used on the ttys during and post-installation, and the mode used by the X portion of installation; nothing to do with X post-installation
(2) KDE is overriding settings you made in /etc/X11/xorg.con* and the automagic that Xorg would otherwise have used Should KDE be overriding the Xorg settings ?
-- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-26 08:24, Duaine Hechler wrote:
Should KDE be overriding the Xorg settings ?
Yes. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+ZC40ACgkQIvFNjefEBxr9TgCeIx6w6X/YGSwVLi8aH6Q3w/wn SrEAn28/6ewUn5/mPmgxQlf3QE4gWTKO =8UlE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Here is the monitor I'm using: Specifications: Dell 1702FP Flat Panel Color Monitor User's Guide General <http://supportapj.dell.com/support/edocs/monitors/1702fp/en/specs.htm#general> Flat Panel <http://supportapj.dell.com/support/edocs/monitors/1702fp/en/specs.htm#flat_panel> Resolution <http://supportapj.dell.com/support/edocs/monitors/1702fp/en/specs.htm#resolution> Preset Display Modes <http://supportapj.dell.com/support/edocs/monitors/1702fp/en/specs.htm#preset> Electrical <http://supportapj.dell.com/support/edocs/monitors/1702fp/en/specs.htm#electrical> Physical Characteristics <http://supportapj.dell.com/support/edocs/monitors/1702fp/en/specs.htm#physical> Environmental <http://supportapj.dell.com/support/edocs/monitors/1702fp/en/specs.htm#environmental> Power Management Modes <http://supportapj.dell.com/support/edocs/monitors/1702fp/en/specs.htm#power> Pin Assignments <http://supportapj.dell.com/support/edocs/monitors/1702fp/en/specs.htm#pin> Plug and Play Capability <http://supportapj.dell.com/support/edocs/monitors/1702fp/en/specs.htm#plug_and_play_capability> ------------------------------------------------------------------------------------------------------------------------ General Model number 1702FP ------------------------------------------------------------------------------------------------------------------------ Flat Panel Screen dimensions Screen type Active matrix - TFT LCD Screen dimensions 17 inches (17-inch viewable image size) Preset display area: Horizontal 337.92 ± 3 mm (13.3 inches ± 0.12 inches) Vertical 270.34 ± 3 mm (10.6 inches ± 0.12 inches) Pixel pitch 0.264 mm Viewing angle +/- 85° (vertical) typical +/- 85° (horizontal) typical Luminance output 250 CD/m² typical, 200 CD/m² minimum Contrast ratio 500 to 1 typical, 400 to 1 minimum Faceplate coating Antiglare with hard-coating 3H Backlight CCFT (4) edgelight system ------------------------------------------------------------------------------------------------------------------------ Resolution Horizontal scan range 31 kHz to 80 kHz (automatic) Vertical scan range 56 Hz to 76 Hz (automatic) Optimal preset resolution 1280 x 1024 at 60 Hz Highest preset resolution 1280 x 1024 at 75 Hz * Highest addressable resolution 1600 x 1200 at 60 Hz (UXGA) * Addressable means the monitor will sync up to this mode. However, Dell does not guarantee the image will be sized, shaped and centered correctly. * Dell does not officially support the UXGA video mode. Video performance could be impaired in this mode. The following message will appear when in this mode "Cannot Display This Video mode". In the event the system is in UXGA mode, the user will still be able to view the screen in order to change the resolution to optimal. Dell guarantees image size and centering for all preset modes listed in the following table. ------------------------------------------------------------------------------------------------------------------------ Preset Display Modes *Display Mode* *Horizontal Frequency (kHz)* *Vertical Frequency (Hz)* *Pixel Clock (MHz)* *Sync Polarity (Horizontal/Vertical)* IBM®, VGA2, 720 x 400 31.469 70.087 28.3 -/+ IBM, VGA3, 640 x 480 31.469 59.940 25.2 -/- VESA®, 640 x 480 37.500 75.000 31.5 -/- VESA, 800 x 600 37.879 60.317 49.5 +/+ VESA, 800 x 600 46.875 75.000 49.5 +/+ VESA, 1024 x 768 48.363 60.004 65.0 -/- VESA, 1024 x 768 60.023 75.029 78.8 +/+ VESA, 1152 x 864 67.500 75.000 108 +/+ VESA, 1280 x 1024 64.000 60.000 135.0 +/+ VESA, 1280 x 1024 79.976 75.025 135.0 +/+ ------------------------------------------------------------------------------------------------------------------------ On 04/25/2012 11:30 PM, Duaine Hechler wrote:
On 04/25/2012 05:27 PM, Felix Miata wrote:
On 2012/04/25 16:30 (GMT-0500) Duaine Hechler composed:
So with that being said, how do I - easily - change the DPI ? Is it in YAST ?
There is no "easy" if you want 100% success.
The "easy" (simplest) way depends on desktop environment. In KDE, there's a "force fonts DPI" chooser in the fonts panel in system (aka personal) settings. Gnome 2 had something similar in Gnome Control Center, which I think had name changes since. Because there are gotchas, I recommend you only try this to see how you like the results of forcing DPI, and to find out what number pleases you most - after setting the display back to its native/preferred mode.
Once you know what DPI works best for you while in native mode, the overall across all apps and toolkits and user logins more thorough and effective, and definitely less than easy, method is via /etc/X11/xorg.conf*. How to do it there is not uniform across all display drivers.
The place to tweak is 'Section "Monitor"'.
If using an NVidia binary driver, you very logically place 'Option "DPI" "100 x 100"' using whatever DPI number you want, check below for general instruction where and how to place it, and restart X.
Absent NVidia binaries, it's more complicated, because it's most thoroughly done via DisplaySize. To get accurate DPI, you use the physical height and width of your display, but in your case of wanting everything bigger, you must lie about the sizes, telling X the sizes are _smaller_ than they actually are. Rather than making the necessary calculations to arrive at the required mm dimensions, you may be able to look suitable ones up in my DisplaySize cheat file[1] where I list the display dimensions that correlate to various combinations of resolution and desired target DPI, mostly multiples of 12, such as 72, 96, 108, 120, 132, 144, plus various others. The file includes an explanation why to prefer a multiple of 12.
Rather than putting all the required components into xorg.conf so that it parses correctly, it's supposed to be somewhat simpler to use the files in xorg.conf.d/, 50-device.conf, 50-monitor.conf and 50-screen.conf, with elementary content as follows:
# 50-device.conf Section "Device" Identifier "Default Device" EndSection
# 50-monitor.conf Section "Monitor" Identifier "Default Monitor" Option "DefaultModes" "on" # only sometimes necessary # DisplaySize 338 270 # 096 DPI @ 1280x1024 (typical size of 17" LCD) DisplaySize 270 216 # 120 DPI @ 1280x1024 (to make things 25% bigger) Option "PreferredMode" "1280x1024" # insurance, probably unnecessary EndSection
# 50-screen.conf Section "Screen" Identifier "Default Screen" Device "Default Device" Monitor "Default Monitor" EndSection
Those three files are installed by default in 12.1, but include nothing but comments. To use them, uncomment the required lines, add the necessary addition(s) (minimally, a DisplaySize line), and restart X. Combining the three above files into one xorg.conf file should produce the same result as the three individual files, but preserve the originals in their unused and inert state.
Well, Felix, Back to the drawing board ! ! ! !
I coded all three files just like above and rebooted each time with each of the DPI settings......
and .... guess what .... each time the monitor came back up in 1024 x 768 mode (even the display (hardware) menu confirms it)
So .... now what ? ? ? ?
14: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.319] Unique ID: _Znp.R9e4vZ5lsP8 SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Intel 4 Series Chipset Integrated Graphics Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2e32 "4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x836d Revision: 0x03 Driver: "i915" Driver Modules: "drm" Memory Range: 0xfb800000-0xfbbfffff (rw,non-prefetchable) Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable) I/O Ports: 0xdc00-0xdc07 (rw) IRQ: 42 (7384 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v00008086d00002E32sv00001043sd0000836Dbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=no, avail=yes, need=no, active=unknown
-- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
So based on the monitor specs, I'm not emulating anything.... right ? On 04/25/2012 11:47 PM, Duaine Hechler wrote:
Here is the monitor I'm using:
Specifications: Dell 1702FP Flat Panel Color Monitor User's Guide
Resolution
Horizontal scan range 31 kHz to 80 kHz (automatic) Vertical scan range 56 Hz to 76 Hz (automatic) Optimal preset resolution 1280 x 1024 at 60 Hz Highest preset resolution 1280 x 1024 at 75 Hz * Highest addressable resolution 1600 x 1200 at 60 Hz (UXGA) * Addressable means the monitor will sync up to this mode. However, Dell does not guarantee the image will be sized, shaped and centered correctly.
* Dell does not officially support the UXGA video mode. Video performance could be impaired in this mode. The following message will appear when in this mode "Cannot Display This Video mode". In the event the system is in UXGA mode, the user will still be able to view the screen in order to change the resolution to optimal.
Dell guarantees image size and centering for all preset modes listed in the following table.
------------------------------------------------------------------------------------------------------------------------
Preset Display Modes
*Display Mode* *Horizontal Frequency (kHz)* *Vertical Frequency (Hz)* *Pixel Clock (MHz)* *Sync Polarity (Horizontal/Vertical)* IBM®, VGA2, 720 x 400 31.469 70.087 28.3 -/+ IBM, VGA3, 640 x 480 31.469 59.940 25.2 -/- VESA®, 640 x 480 37.500 75.000 31.5 -/- VESA, 800 x 600 37.879 60.317 49.5 +/+ VESA, 800 x 600 46.875 75.000 49.5 +/+ VESA, 1024 x 768 48.363 60.004 65.0 -/- VESA, 1024 x 768 60.023 75.029 78.8 +/+ VESA, 1152 x 864 67.500 75.000 108 +/+ VESA, 1280 x 1024 64.000 60.000 135.0 +/+ VESA, 1280 x 1024 79.976 75.025 135.0 +/+
------------------------------------------------------------------------------------------------------------------------
-- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 25 Apr 2012 23:57:18 -0500 Duaine Hechler <dahechler@att.net> wrote:
So based on the monitor specs, I'm not emulating anything.... right ?
On 04/25/2012 11:47 PM, Duaine Hechler wrote:
Here is the monitor I'm using:
Hi Duaine, Basic specs: Dell 17" LCD 1280 x 1024 5:4 No, it's not emulating XGA. It's displaying "native" XGA by writing to a centered block of 1,024 x 768 pixels. The remaining pixels are simply not being used. Were you to drive the display at the maximum possible resolution of 1,600 x 1,200 pixels (not recommended by myself or Dell,) it would be forced into emulation mode because it has only 1,280 x 1,024 pixels to write to. In your case, you're still writing to a smaller number of pixels than the display has available, so emulation is not required. Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/26 01:20 (GMT-0400) Carl Hartung composed:
Basic specs: Dell 17" LCD 1280 x 1024 5:4
No, it's not emulating XGA. It's displaying "native" XGA by writing to a centered block of 1,024 x 768 pixels. The remaining pixels are simply not being used.
That's not how 1024x768 seems to work on my 1704FP. On http://fm.no-ip.com/Auth/Font/fonts-ptdemo.html the 400px box measures ~140mm tall and ~131mm wide. 1024x768 on a 5:4 display makes people look thinner than they really are in pictures displayed on them. -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 26 Apr 2012 03:26:20 -0400 Felix Miata <mrmazda@earthlink.net> wrote:
On 2012/04/26 01:20 (GMT-0400) Carl Hartung composed:
Basic specs: Dell 17" LCD 1280 x 1024 5:4
No, it's not emulating XGA. It's displaying "native" XGA by writing to a centered block of 1,024 x 768 pixels. The remaining pixels are simply not being used.
That's not how 1024x768 seems to work on my 1704FP. On http://fm.no-ip.com/Auth/Font/fonts-ptdemo.html the 400px box measures ~140mm tall and ~131mm wide. 1024x768 on a 5:4 display makes people look thinner than they really are in pictures displayed on them.
So it's actually *emulating* a lower resolution 'active display field' within a larger, higher resolution matrix? There's a cost savings step or two involved somewhere :-) ... like adapting a display engine that was originally developed for CRT. I'd expect that behavior in a 'multisync' CRT. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/25 23:47 (GMT-0500) Duaine Hechler composed:
Here is the monitor I'm using:
Specifications: Dell™ 1702FP Flat Panel Color Monitor User's Guide
It's a predecessor to a 1704FP I have here for testing. http://fm.no-ip.com/SS/duahech01.jpg was taken while my 1704FP was connected to a 12.1 system with KDE 4.7.2 using the suggested xorg.conf file in my 12/04/25 18:27 -0400 thread post. KDE font settings are set to 10pt except for "small" and taskbar, which are set to 9pt. Font smoothing is enabled and set to medium hinting. Open apps are Konsole, KCalc and Firefox. http://fm.no-ip.com/Auth/Font/fonts-ptdemo.html is the page showing in Firefox. Panel is set taller than default, because I normally use that machine on a larger display running 1600x1200.
Should KDE be overriding the Xorg settings ?
That's why they exist, the "easy" way to force, applicable mostly to KDE and QT apps, which may or may not be applicable to apps built with other toolkits. Kcm_gtk needs to be installed to ensure GTK apps can use your KDE settings if you choose the force via KDE settings method. If you want your xorg.con* settings used, you need to restore auto in your size & orientation section of display settings, and turn off force DPI in the fonts section of appearance. -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/25 07:24 (GMT-0400) Carl Hartung composed:
At 120 DPI a bitmap of 360 x 360 pixels displays as a 3" square
At 96 DPI the same graphic displays as a 3.75" square (larger)
At 72 DPI it displays as a 5" square ... much larger
This is the "zoom" effect that Felix alluded to.
Accurate as what you wrote certainly is, describing it has you have not infrequently causes confusion among users trying to use it in the context of attempting to apply an overall desktop zoom effect. Certainly as DPI goes up for any given resolution, the physical size of a bitmap goes down. The DE scales according to DPI, which is easier with fonts than images. A 12pt font at 96 DPI nominally has about 128 pixels to work with to draw each glyph (16px tall, 8px wide). At a 25% DPI increase to 120 from 96, the nominal available pixel count for a 12pt font jumps to 20px tall x 10 px wide, 200 total, an increase of 56.25%. This difference is in no small part responsible for font quality increase as pixel density goes up. Some people find this difference to be an unappealing increase in stroke weight at commonly used sizes, seeing it as undesirable bolding, until they get used to the naturally reduced or eliminated jaggies and learn to appreciate the more accurately drawn glyphs for what they are - higher overall quality. For icons, the required zoom is traditionally implemented via a selection of discrete images selected according to availability and need. Usually the selection is limited, so going too high in DPI will at a point cease to be able to provide icons sized in reasonably close proportion to the associate text they are typically coupled with. Vector icons are the solution to this problem, but I've yet to see evidence of widespread implementation of vector icons. The biggest drawback to forcing DPI as a desktop zoom effect is that there is no way to make bitmaps bigger except via methods that cannot do more than estimate the required additional information that doesn't exist. There's simply no substitute for having enough pixels in the original image if physical size is to be preserved as density rises. OTOH, there isn't really a whole lot of difference in perceived quality between a bitmap that simply isn't big enough when displayed at its intrinsic size, and one that is isn't big enough displayed at its intrinsic size but is stretched to a size that would be adequate if there were enough pixels in the bitmap to start with. This bitmap size problem is one reason often why some people prefer a lower resolution, even though the overall quality is measurably inferior. Another reason why some prefer a lower resolution is poor (resolution dependent) web page design, which typically: 1-leaves input boxes and text areas small in proportion to the amount of text the designer assumed should fit the input area(s) provided 2-often causes text to disappear or overlap other text or images 3-can cause mangled layout leading to difficult to understand content 4-increases frequency of need to apply zoom In summary, _raising_ the _applied/assumed_ DPI to an arbitrary value on a Linux GUI desktop _raises_ text size, _raises_ icon sizes across a limited range, does an arguably reasonable job of preserving window and tools layout when text and icons are mixed, and does nothing that helps compensate for high screen density WRT to such bitmap images as photos, photo-based background images, or most existing (resolution dependent) web page layouts. -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 26 Apr 2012 00:29:45 -0400 Felix Miata <mrmazda@earthlink.net> wrote: <snipped>
In summary, _raising_ the _applied/assumed_ DPI to an arbitrary value on a Linux GUI desktop _raises_ text size, _raises_ icon sizes across a limited range, does an arguably reasonable job of preserving window and tools layout when text and icons are mixed, and does nothing that helps compensate for high screen density WRT to such bitmap images as photos, photo-based background images, or most existing (resolution dependent) web page layouts.
Hi Felix, I don't recall experimenting with "arbitrary" DPIs, or if I did, the results were so bad it must have dissuaded me from trying it again; it had to have been quite a long time ago... :-) We are definitely treading into territory where my comprehension grows weaker as the complexity and level of detail increases, so, that being said -- and I could be wrong -- my understanding is that 'conventional wisdom' and practices have settled upon a 'base set' of 'standard' display DPI values which include 72, 96 and 120 DPI. These values are then supplemented by finer grained control over discreet objects within the UI, such as fonts, icons, window elements, buttons, thumbnails, and so on. My experience has been that changing from one of these 'base' settings to another causes modern DEs to 'automagically' compensate by adjusting certain of these finer grained settings to keep the perceived outcome within 'sane' boundaries. I believe it is this 'automated magic' happening in the background that causes the (scalable font) text to increase in size with DPI even as bitmaps and other fixed (not scaled) objects decrease. IOW, if one stays within established norms by selecting one of the three DPI settings that I enumerated, the outcome /should/ normally yield a reasonably usable desktop. If further refinements are desired, one can change themes and make adjustments to the elements which make up that theme. Am I still on track here or have I misinterpreted / forgotten a fundamental technical concept? Thx! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/27/2012 09:52 AM, Carl Hartung wrote:
On Thu, 26 Apr 2012 00:29:45 -0400 Felix Miata<mrmazda@earthlink.net> wrote:
<snipped>
In summary, _raising_ the _applied/assumed_ DPI to an arbitrary value on a Linux GUI desktop _raises_ text size, _raises_ icon sizes across a limited range, does an arguably reasonable job of preserving window and tools layout when text and icons are mixed, and does nothing that helps compensate for high screen density WRT to such bitmap images as photos, photo-based background images, or most existing (resolution dependent) web page layouts. Hi Felix,
I don't recall experimenting with "arbitrary" DPIs, or if I did, the results were so bad it must have dissuaded me from trying it again; it had to have been quite a long time ago... :-)
We are definitely treading into territory where my comprehension grows weaker as the complexity and level of detail increases, so, that being said -- and I could be wrong -- my understanding is that 'conventional wisdom' and practices have settled upon a 'base set' of 'standard' display DPI values which include 72, 96 and 120 DPI. These values are then supplemented by finer grained control over discreet objects within the UI, such as fonts, icons, window elements, buttons, thumbnails, and so on.
My experience has been that changing from one of these 'base' settings to another causes modern DEs to 'automagically' compensate by adjusting certain of these finer grained settings to keep the perceived outcome within 'sane' boundaries. I believe it is this 'automated magic' happening in the background that causes the (scalable font) text to increase in size with DPI even as bitmaps and other fixed (not scaled) objects decrease.
IOW, if one stays within established norms by selecting one of the three DPI settings that I enumerated, the outcome /should/ normally yield a reasonably usable desktop. If further refinements are desired, one can change themes and make adjustments to the elements which make up that theme.
Am I still on track here or have I misinterpreted / forgotten a fundamental technical concept?
Thx!
Carl
Which is why I don't bother messing with the DPI setting and use the "density" and the monitors come with different built-in set of defaults (ie. 1024x768). Duaine -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 27 Apr 2012 13:56:50 -0500 Duaine Hechler <dahechler@att.net> wrote: <snipped>
Which is why I don't bother messing with the DPI setting and use the "density" and the monitors come with different built-in set of defaults (ie. 1024x768).
Duaine
As I wrote earlier, there's nothing wrong with running a 1,280 x 1,024 display at 1,024 x 768 if you're happy with it. I just remember being seriously annoyed whenever a newly configured system would refuse to let me use all the available screen 'real estate'. :-) I got very good at fine tuning my display configurations "to taste" including regularly 'bumping' DPI up to the next setting and then adjusting font sizes, etc., until I was happy with it. regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/27/2012 02:30 PM, Carl Hartung wrote:
On Fri, 27 Apr 2012 13:56:50 -0500 Duaine Hechler<dahechler@att.net> wrote:
<snipped>
Which is why I don't bother messing with the DPI setting and use the "density" and the monitors come with different built-in set of defaults (ie. 1024x768).
Duaine As I wrote earlier, there's nothing wrong with running a 1,280 x 1,024 display at 1,024 x 768 if you're happy with it. I just remember being seriously annoyed whenever a newly configured system would refuse to let me use all the available screen 'real estate'. :-) I got very good at fine tuning my display configurations "to taste" including regularly 'bumping' DPI up to the next setting and then adjusting font sizes, etc., until I was happy with it.
regards,
Carl
What kind of monitor are YOU using....I've NEVER had this problem....all the ones I've ever used uses the full "real estate" as you put it. Just sayin' -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 27 Apr 2012 14:45:23 -0500 Duaine Hechler <dahechler@att.net> wrote:
On 04/27/2012 02:30 PM, Carl Hartung wrote:
On Fri, 27 Apr 2012 13:56:50 -0500 Duaine Hechler<dahechler@att.net> wrote:
Which is why I don't bother messing with the DPI setting and use the "density" and the monitors come with different built-in set of defaults (ie. 1024x768).
Duaine As I wrote earlier, there's nothing wrong with running a 1,280 x 1,024 display at 1,024 x 768 if you're happy with it. I just remember being seriously annoyed whenever a newly configured system would refuse to let me use all the available screen 'real estate'. :-) I got very good at fine tuning my display configurations "to taste" including regularly 'bumping' DPI up to
<snipped> the next setting and then adjusting font sizes, etc., until I was happy with it.
regards,
Carl
What kind of monitor are YOU using....I've NEVER had this problem....all the ones I've ever used uses the full "real estate" as you put it.
Just sayin'
I _did_ write "I remember" indicating past tense. I'm currently running two native resolution LCDs in twinview mode. Maximizing screen 'real estate' isn't as much of an issue for me as it used to be. In any case, your monitor says "optimum" next to the native 1,280 x 1,024 setting. By definition, and according to the manufacturer's own specifications, you're not utilizing it to it's fullest. This isn't a criticism. I'm just stating the obvious. As I've already written, leave it as it is if you're happy with it EOT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-25 08:49, Duaine Hechler wrote:
- Can't get my MB sound card to work (Intel ICH7) consistent.
So far so good.... the "init=/sbin/sysvinit" seems to have done the trick for the sound.
Developers REALLY need to work on "systemd"
- alsasound will not stay "yes" in the system service levels.
Seems to be fixed from above fix
Notice that this doesn't solve anything, it just bypasses the problem. You have to report the problems you have with systemd in bugzilla so that the devs solve it. They will never solve them if YOU don't report. The systemv bypass will eventually disappear, and you will be stuck. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+X1v0ACgkQIvFNjefEBxoVCACfeZ48dAyDtcZKqcqgZZMv7SgP 18sAn3aN2re2FSpjh2MPIAaPvl3htWMZ =U0BT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/04/25 12:50 (GMT+0200) Carlos E. R. composed:
The systemv bypass will eventually disappear,
Keyword: eventually. It won't happen in 12.1, because it has already been released. It won't happen in 12.2, because it's still too buggy, and 12.2 is too far along to consider dropping sysvinit from even if it made sense to do so. Even when systemd matures enough that sysvinit could be dropped, it may be several years before it can be dropped. Already released proprietaryware installation scripts in many if not most cases will never be rewritten, while new ones yet to be written may take years to stop being written for sysvinit only.
and you will be stuck.
Not while he's running 12.1. -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Somehow after rebooting (absolutely NO CHANGES) my display is back to 1280 x 1024 - and - now my sound is gone. 12.1 is - too - frickin' - buggy - back - to - 11.4 Good thing I haven't updated my other household computers !!!!!! In MAJOR frustration (although NOT leaving openSUSE - love it too much), Duaine On 04/25/2012 01:49 AM, Duaine Hechler wrote:
On 04/22/2012 08:59 PM, Duaine Hechler wrote:
with the following conditions fixed.
I would like to here from persons that have had these problems fixed.
- Can't get my MB sound card to work (Intel ICH7) consistent.
So far so good.... the "init=/sbin/sysvinit" seems to have done the trick for the sound.
Developers REALLY need to work on "systemd"
- alsasound will not stay "yes" in the system service levels.
Seems to be fixed from above fix
- rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active.
Seems to be fixed from above fix
- Can't get my display to stay at 1024x768
Did nothing but at install time, do F3 at 1024x768... still sticking.
- Can't get rid of the "Nepomuk Indexing Disabled) popups
Try to edit ~/.config/akonadi/akonadiserverrc and turn
StartServer=true
to
StartServer=false
TIA, Duaine
-- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
have these issues been fixed in any of the updates: - Can't get my MB sound card to work (Intel ICH7) consistent. - Somehow after rebooting (absolutely NO CHANGES) my display is back to 1280 x 1024 - alsasound will not stay "yes" in the system service levels. -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 13 August 2012 05:22:39 Duaine Hechler wrote:
have these issues been fixed in any of the updates:
- Can't get my MB sound card to work (Intel ICH7) consistent. lspci please
- Somehow after rebooting (absolutely NO CHANGES) my display is back to 1280 x 1024 What is you screen brand and model ? I bet 1280 x 1024 would be your screen native. Today, xorg is changing "automatically", I don't like this either. So you should write a xorg.conf file. Ask in a new thread if you don't know how to do this, I will help you.
- alsasound will not stay "yes" in the system service levels. I don't understand, could you post a screenshot on a web storage ?
Dsant -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/13/2012 03:21 AM, Dsant wrote:
On Monday 13 August 2012 05:22:39 Duaine Hechler wrote:
have these issues been fixed in any of the updates:
- Can't get my MB sound card to work (Intel ICH7) consistent. lspci please
Under 11.4 dahechler:/home/dahechler # lspci 00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03) 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 01) 00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 01) 00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 01) 00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 01) 00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) 00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA IDE Controller (rev 01) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) 03:01.0 Multimedia video controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) 03:01.2 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
- Somehow after rebooting (absolutely NO CHANGES) my display is back to 1280 x 1024 What is you screen brand and model ? I bet 1280 x 1024 would be your screen native.
Under 11.4 Dell 1702FP - Resolution:1024x768@75Hz - Optimum 1280x1024@60Hz
Today, xorg is changing "automatically", I don't like this either. So you should write a xorg.conf file. Ask in a new thread if you don't know how to do this, I will help you.
When I did my previous testing of 12.1, I did write an xorg.conf file and it still would NOT stay at 1024x768
- alsasound will not stay "yes" in the system service levels. I don't understand, could you post a screenshot on a web storage ?
Under 12.1, I would enable alsasound, save it but then when I come back in it, it was YES*
Dsant
-- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/08/13 04:40 (GMT-0500) Duaine Hechler composed:
When I did my previous testing of 12.1, I did write an xorg.conf file and it still would NOT stay at 1024x768
Did you confirm via Xorg.0.log that your xorg.conf file was 100% valid? Did your xorg.conf file include?: Section "Monitor" ... Option "PreferredMode" "1024x768" ... EndSection Did your /etc/X11/xorg/conf.d/50-monitor.conf file have any uncommented lines in it? -- "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 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/13/2012 05:36 AM, Felix Miata wrote:
On 2012/08/13 04:40 (GMT-0500) Duaine Hechler composed:
When I did my previous testing of 12.1, I did write an xorg.conf file and it still would NOT stay at 1024x768
Did you confirm via Xorg.0.log that your xorg.conf file was 100% valid?
No, but I had it stripped down to what you sent me to test with.
Did your xorg.conf file include?:
Section "Monitor" ... Option "PreferredMode" "1024x768" ... EndSection
Yes
Did your /etc/X11/xorg/conf.d/50-monitor.conf file have any uncommented lines in it?
Not sure, but I had it stripped down to what you sent me to test with. Duaine -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 13 August 2012 12:45:34 Duaine Hechler wrote:
On 08/13/2012 05:36 AM, Felix Miata wrote:
On 2012/08/13 04:40 (GMT-0500) Duaine Hechler composed:
When I did my previous testing of 12.1, I did write an xorg.conf file and it still would NOT stay at 1024x768
Did you confirm via Xorg.0.log that your xorg.conf file was 100% valid?
No, but I had it stripped down to what you sent me to test with.
- Tell us you xorg.conf exact path - Could you post your 2 files, complete please : xorg.conf and /var/log/Xorg.0.log somewhere on a storage place on the internet and tell us where to get these ? Dsant -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/13/2012 12:05 PM, Dsant wrote:
On Monday 13 August 2012 12:45:34 Duaine Hechler wrote:
On 08/13/2012 05:36 AM, Felix Miata wrote:
On 2012/08/13 04:40 (GMT-0500) Duaine Hechler composed:
When I did my previous testing of 12.1, I did write an xorg.conf file and it still would NOT stay at 1024x768 Did you confirm via Xorg.0.log that your xorg.conf file was 100% valid? No, but I had it stripped down to what you sent me to test with.
- Tell us you xorg.conf exact path - Could you post your 2 files, complete please : xorg.conf and /var/log/Xorg.0.log somewhere on a storage place on the internet and tell us where to get these ?
Dsant Those were 12.1 files. I don't have those anymore.
-- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 13 August 2012 19:39:29 Duaine Hechler wrote:
On 08/13/2012 12:05 PM, Dsant wrote:
On Monday 13 August 2012 12:45:34 Duaine Hechler wrote:
On 08/13/2012 05:36 AM, Felix Miata wrote:
On 2012/08/13 04:40 (GMT-0500) Duaine Hechler composed:
When I did my previous testing of 12.1, I did write an xorg.conf file and it still would NOT stay at 1024x768
Did you confirm via Xorg.0.log that your xorg.conf file was 100% valid?
No, but I had it stripped down to what you sent me to test with.
- Tell us you xorg.conf exact path - Could you post your 2 files, complete please : xorg.conf and /var/log/Xorg.0.log somewhere on a storage place on the internet and tell us where to get these ?
Dsant
Those were 12.1 files. I don't have those anymore.
Here is one of mine : Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "USB" Option "Device" "/dev/input/mouse0" Option "Emulate3Buttons" "no" Option "ButtonMapping" "1 2 3 5 4" #dans kcontrol en fait #Option "ZAxisMapping" "5 4" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Device" Identifier "device1" VendorName "nVidia Corporation" BoardName "NVIDIA GeForce GT240" Driver "nvidia" #Driver "nv" BusID "PCI:1:0:0" #Option "DPMS" #Option "UseEvents" "false" #Option "XaaNoOffscreenPixmaps" Screen 0 #Option "Rotate" "inverted" EndSection Section "Monitor" Identifier "sun" VendorName "SUN" ModelName "GDM-5510" #HorizSync 30-130 HorizSync 30-120 #VertRefresh 48-170 VertRefresh 48-150 # TV fullscreen mode or DVD fullscreen output. # 768x576 @ 79 Hz, 50 kHz hsync #ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630 # 768x576 @ 100 Hz, 61.6 kHz hsync #ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616 EndSection Section "Screen" Identifier "screena" Device "device1" Monitor "sun" DefaultDepth 24 Subsection "Display" Depth 24 Modes "800x600" #Virtual 800 600 EndSubsection EndSection Section "ServerLayout" Identifier "layout1" InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" Screen "screena" EndSection Adapt it to your needs, and tell us. Dsant -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Duaine Hechler wrote:
have these issues been fixed in any of the updates:
- Can't get my MB sound card to work (Intel ICH7) consistent.
- Somehow after rebooting (absolutely NO CHANGES) my display is back to 1280 x 1024
- alsasound will not stay "yes" in the system service levels.
The easiest way (for everyone) to find out is to just try it. For a test-installation, I would probably try 12.2rc2 if I were you. -- Per Jessen, Zürich (21.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (14)
-
Anton Aylward -
Brian K. White -
C -
Carl Hartung -
Carlos E. R. -
Dsant -
Duaine Hechler -
Felix Miata -
Hans Witvliet -
Ken Schneider - openSUSE -
Patrick Shanahan -
Per Jessen -
phanisvara das -
Roger Luedecke