2012. február 15. 21:37 napon Steven Hess írta:

On Wed, Feb 15, 2012 at 6:50 AM, Peter Suetterlin wrote:

...

Istvan Gabor wrote:

...

Hello:

The subject tells: How can get a boot progress indicator in oS 12.1? A similar one to any of that of previous suse versions.

I'd be happy to get *any* info on the progress.  Even screen output in text mode is stopped after fsck - the first time I thought the system has crashed.

-- Dr. Peter "Pit" Suetterlin                 http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590  (Spain)             P.Suetterlin@royac.iac.es      +46 8 5537 8507  (Sweden)            Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

My /boot/grub/menu.lst stanza looks like this and I get a verbose boot in 12.1:

title Desktop -- openSUSE 12.1 - 3.1.9-1.4 (desktop) root (hd0,5) kernel /boot/vmlinuz-3.1.9-1.4-desktop root=/dev/disk/by-id/ata-ST3500630AS_9QG141S6-part6 resume=/dev/disk/by-id/ata-ST3500630AS_9QG141S6-part5 splash=verbose verbose showopts vga=0x31a initrd /boot/initrd-3.1.9-1.4-desktop

Hope this helps.

This is different thing. I meant that the splash screen in every previous suse version showed a progress bar which indicated that the progress of the boot process. For some reason the developers removed this progress bar and only the splash image is shown. You can press escape and go to verbose mode any time but then you can not get back to the splash screen. What Peter mentioned about fsck was again a different issue. From 11.x version the progress of fsck is not shown at boot. In 9.x and 10.x versions the fsck showed its progress during boot. This was discussed here: http://lists.opensuse.org/opensuse/2010-02/msg01277.html but no solution was given, only hints, and I could not solve it. I would like to know how I could enable fsck progress bar for both root and non-root filesystems during bootup. Peter, if you are interested in this one, please start a specific new thread devoted to this question. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Under systemd there can be no such thing as a progress indicator because there is no such thing as "100% completed" or any other % completed. Because that is one of the fundamental differences in the way systemd works vs how sysvinit works. Systemd does not process a list of scripts in an orderly fashion and there is no first and no last action. Systemd reads all it's various service descriptor config files and all of them start doing their individual things essentially at the same time. Some do have to wait for others, but there is no inherent order laid down ahead of time like sysv init scripts. Also, many services start and stop dynamically in response to various run-time conditions. There isn't a "done" state, because it's basically always watching to start and stop things if they are needed the entire time the machine is running, even one second before you shut it off after a year, not just starting them all up once at the beginning. Since there is no "done" state, there is no such thing as "75% of the way to done" either. There might be _something_ that could be monitored in systemd that could give you _some_ sort of progress, but I don't know what it would be or how it would work. basically, at least right now, it's just a meaningless concept. -- bkw On 2/16/2012 5:49 AM, Istvan Gabor wrote:

2012. február 15. 21:37 napon Steven Hess írta:

...

On Wed, Feb 15, 2012 at 6:50 AM, Peter Suetterlin wrote:

...

Istvan Gabor wrote:

...

Hello:

The subject tells: How can get a boot progress indicator in oS 12.1? A similar one to any of that of previous suse versions.

I'd be happy to get *any* info on the progress. Even screen output in text mode is stopped after fsck - the first time I thought the system has crashed.

-- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8507 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

My /boot/grub/menu.lst stanza looks like this and I get a verbose boot in 12.1:

title Desktop -- openSUSE 12.1 - 3.1.9-1.4 (desktop) root (hd0,5) kernel /boot/vmlinuz-3.1.9-1.4-desktop root=/dev/disk/by-id/ata-ST3500630AS_9QG141S6-part6 resume=/dev/disk/by-id/ata-ST3500630AS_9QG141S6-part5 splash=verbose verbose showopts vga=0x31a initrd /boot/initrd-3.1.9-1.4-desktop

Hope this helps.

This is different thing. I meant that the splash screen in every previous suse version showed a progress bar which indicated that the progress of the boot process. For some reason the developers removed this progress bar and only the splash image is shown. You can press escape and go to verbose mode any time but then you can not get back to the splash screen.

What Peter mentioned about fsck was again a different issue. From 11.x version the progress of fsck is not shown at boot. In 9.x and 10.x versions the fsck showed its progress during boot.

This was discussed here: http://lists.opensuse.org/opensuse/2010-02/msg01277.html but no solution was given, only hints, and I could not solve it.

I would like to know how I could enable fsck progress bar for both root and non-root filesystems during bootup.

Peter, if you are interested in this one, please start a specific new thread devoted to this question.

Istvan

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, Feb 16, 2012 at 04:56:13PM +0100, Peter Suetterlin wrote:

Istvan Gabor wrote:

...

What Peter mentioned about fsck was again a different issue. From 11.x version the progress of fsck is not shown at boot. In 9.x and 10.x versions the fsck showed its progress during boot.

No, I'm not refering to a missing fsck progress, but everything after mounting the disks is just not reported on the verbose screen. This is a systemd thing I think, or one of its integration in the boot process, but probably related to the fact that there is (also) no progress bar in splash mode. So I didn't want to hijack your thread but point towards another facette of the issue...

While using systemd to boot all messages are passed to syslog. /var/log/boot.msg isn't used. You see this by checking the timestamp. I would try to use sysvinit instead of systemd. See http://en.opensuse.org/openSUSE:Most_annoying_bugs_12.1 section Bug #725917 Problem: System is switched from sysvinit to systemd during upgrade. Workaround: is to install the sysvinit-init package. As soon as its install gets acknowledged the removal of the systemd-sysvinit package will be suggested. iIf you had an up to date system and after switching to sysvinit all is better please be this nice and file a bug report and report the ID back in this thread. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

On Thu, 16 Feb 2012 20:20:25 -0200 Marco Calistri wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Il 16/02/2012 15:45, Lars Müller ha scritto:

...

On Thu, Feb 16, 2012 at 04:56:13PM +0100, Peter Suetterlin wrote:

...

Istvan Gabor wrote:

...

What Peter mentioned about fsck was again a different issue. From 11.x version the progress of fsck is not shown at boot. In 9.x and 10.x versions the fsck showed its progress during boot.

No, I'm not refering to a missing fsck progress, but everything after mounting the disks is just not reported on the verbose screen. This is a systemd thing I think, or one of its integration in the boot process, but probably related to the fact that there is (also) no progress bar in splash mode. So I didn't want to hijack your thread but point towards another facette of the issue...

While using systemd to boot all messages are passed to syslog. /var/log/boot.msg isn't used. You see this by checking the timestamp.

I would try to use sysvinit instead of systemd. See http://en.opensuse.org/openSUSE:Most_annoying_bugs_12.1 section

Bug #725917

Problem: System is switched from sysvinit to systemd during upgrade.

Workaround: is to install the sysvinit-init package. As soon as its install gets acknowledged the removal of the systemd-sysvinit package will be suggested.

iIf you had an up to date system and after switching to sysvinit all is better please be this nice and file a bug report and report the ID back in this thread.

Thanks,

Lars

Sorry to breaking-in by asking a bit different thing: whatn does it means boot "default" when booting opensuse 12.1?

System uses SYSVINIT or SYSTEMD in that case?

Regards,

- -- Marco Calistri (amdturion) opensuse 12.1 (Aspargus) - Kernel 3.1.9-1.4-desktop x86_64 Gnome 3.2.1 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk89gSkACgkQi4zJuA3lyFfucgCfZFMSj6cE0N6o64RrlUdu75fL +qYAoJVAuIgLB7oRALmcFnZJ4k2u5AdY =txnv -----END PGP SIGNATURE-----

"Default" at boot means the kernel that is chosen from GRUB display. One or more kernels may be installed with each being best suited for personal preference. For more information on that subject see the SuSE documentation and Google for "linux kernel variations" Tom -- Tom Taylor - retired penguin openSUSE 11.4 x86_64 openSUSE 12.1 x86_64 openSUSE 12.2-M1 x86_64 KDE 4.6.00, FF 4.0 KDE 4.7.2, FF 8.0 KDE 4.8.0 FF 10.0 claws-mail 3.8.0 registered linux user 263467 linxt-At-comcast-DoT-net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, 16 Feb 2012 20:20:25 -0200 Marco Calistri wrote:

System uses SYSVINIT or SYSTEMD in that case?

Default as in above is systemd. Temporary switch to sysvinit is to use a function key offered at the bottom of the grub boot screen. (I never try to remember function key numbers as description is clear.) Permanent is mentioned in Lars email. Install the sysvinit-init package, which I'm doing right now to troubleshoot intermittent error with network card being disabled during the boot. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org