27 tty's?...

robin_listas · January 27, 2014, 7:33pm

On 2014-01-27 19:16, gogalthorp wrote:
>
> Is this a desktop and does it have a floppy?
>
> If so check the BIOS/UEFI and see if the floppy is enabled there. If so
> turn it off. There is a known problem if the BIOS has a floppy enabled
> and it does not exist.

The entire Linux boot, from start to prompt, takes 21 seconds. There is
nothing wrong. IMO.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

gogalthorp · January 27, 2014, 8:00pm

MMM maybe he has auto login on and it could take a it longer. But that is a desktop issue. System boot looks fine

Not sure where the hang from the nonexistent floppy happens when it is .

goro_goren · January 27, 2014, 8:08pm

1- **Autologin **enabled

2- Lappy Acer aspire E1 (2gb ram) intel B820 [1.7GHz,2MB L3 cache]

floppy? not at all! (some very bad could be happening)…

gogalthorp · January 27, 2014, 8:43pm

So your boot is ok the time is taking in the Desktop startup.
Which Desktop?
Do you have a lot of apps running at startup?

To see the problem you need to shutdown autologin and log in as normal then maybe we can see what is eating up so much time. It is not boot.

goro_goren · January 27, 2014, 8:49pm

KDE !

Which Desktop?

I’ll do that!

To see the problem you need to shutdown autologin and log in as normal then maybe we can see what is eating up so much time. It is not boot

let me take an image!

Do you have a lot of apps running at startup?

tia!

malcolmlewis · January 27, 2014, 8:53pm

On Mon 27 Jan 2014 07:06:01 PM CST, gogalthorp wrote:

MMM maybe he has auto login on and it could take a it longer. But that
is a desktop issue. System boot looks fine

Not sure where the hang from the nonexistent floppy happens when it is .

Hi
Autologin shouldn’t slow things down, or is the user on KDE?

I have found the critical-chain systemd-analyze option to glean
additional info.

I would remove the 5 plymouth packages installed, then run mkinitrd and
reboot, see how that goes.

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

gogalthorp · January 27, 2014, 9:02pm

No but a regular login it lets the user see that the problem is not in the boot but in the desktop loading. Looks to me that boot is taking around 20 sec. Any additional time is from the desktop

goro_goren · January 28, 2014, 2:35am

do you mean **6 **packages?

http://s21.postimg.org/oelq5n2er/image.jpg](http://postimg.org/image/oelq5n2er/)

chances to break the system after that you suggest?

robin_listas · January 28, 2014, 2:43am

On 2014-01-28 02:36, goro goren wrote:

> ‘[image: http://s21.postimg.org/oelq5n2er/image.jpg]’
> (http://postimg.org/image/oelq5n2er/)

If you mark that one for removal, you will see a few others that are
automatically marked for removal as well, because of dependencies.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

malcolmlewis · January 28, 2014, 3:03am

On Tue 28 Jan 2014 01:36:01 AM CST, goro goren wrote:

malcolmlewis;2619859 Wrote:
>
>
> I have found the critical-chain systemd-analyze option to glean
> additional info.
>
> I would remove the 5 plymouth packages installed, then run mkinitrd
> and reboot, see how that goes

do you mean *6 *packages?

‘[image: http://s21.postimg.org/oelq5n2er/image.jpg]’
(http://postimg.org/image/oelq5n2er/)

Hi
I only had five, no dracut one… must be a KDE thing…

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

wolfi323 · January 28, 2014, 10:07am

??? Why do you think that’s a KDE thing?

dracut is a mkinitrd replacement.

And I don’t have plymouth-dracut either on any of my (KDE) systems.

goro_goren · January 28, 2014, 3:03pm

goro_goren:

~> systemd-analyze
Startup finished in 2.206s (kernel) + 4.540s (initrd) + 17.929s (userspace) = 24.676s

~> systemd-analyze
Startup finished in 2.172s (kernel) + 3.230s (initrd) + 15.207s (userspace) = 20.610s

~> systemd-analyze blame | head
          6.323s plymouth-start.service
          5.084s apparmor.service
          4.712s NetworkManager.service
          4.366s ModemManager.service
          3.357s avahi-daemon.service
          3.282s wpa_supplicant.service
          3.251s xdm.service
          3.209s vmtoolsd.service
          3.011s systemd-logind.service
          2.661s postfix.service

update:

~>  systemd-analyze blame | head
          6.541s apparmor.service
          4.123s NetworkManager.service
          3.952s ModemManager.service
          2.770s xdm.service
          2.495s systemd-udev-root-symlink.service
          2.155s systemd-vconsole-setup.service
          2.090s rsyslog.service
          2.038s avahi-daemon.service
          1.799s wpa_supplicant.service
          1.654s systemd-logind.service

I would remove the 5 plymouth packages installed, then run mkinitrd and
reboot, see how that goes

robin_listas · January 28, 2014, 2:58pm

On 2014-01-28 10:16, wolfi323 wrote:

> dracut is a mkinitrd replacement.

It is, but why should it be installed, because nothing in openSUSE
configures it. openSUSE is not yet prepared to use it.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

goro_goren · January 28, 2014, 3:23pm

can’t get rid **apparmor.service :

**http://s28.postimg.org/iwagk3fuh/image.jpg](http://postimg.org/image/iwagk3fuh/)

TIA!

malcolmlewis · January 28, 2014, 3:22pm

On Tue 28 Jan 2014 02:06:02 PM CST, goro goren wrote:

~> systemd-analyze
Startup finished in 2.206s (kernel) + 4.540s (initrd) + 17.929s (userspace) = 24.676s

update:

~> systemd-analyze blame | head
6.541s apparmor.service
4.123s NetworkManager.service
3.952s ModemManager.service
2.770s xdm.service
2.495s systemd-udev-root-symlink.service
2.155s systemd-vconsole-setup.service
2.090s rsyslog.service
2.038s avahi-daemon.service
1.799s wpa_supplicant.service
1.654s systemd-logind.service

Hi
So I wonder why your systemd-analyze output is different, or is this
dracut related?

You only have 2GB of ram, correct?

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

robin_listas · January 28, 2014, 3:43pm

On 2014-01-28 15:26, goro goren wrote:

> can’t get rid *apparmor.service :
>
> *’[image: http://s28.postimg.org/iwagk3fuh/image.jpg]’
> (http://postimg.org/image/iwagk3fuh/)

That’s similar to trying to remove the antivirus in Windows. Why would
you do it?

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

malcolmlewis · January 28, 2014, 4:09pm

On Tue 28 Jan 2014 02:26:02 PM CST, goro goren wrote:

goro_goren;2620059 Wrote:
>
>
> >
Code:

> > ~> systemd-analyze blame | head
> 6.541s apparmor.service
>

> >

can’t get rid *apparmor.service :

Hi
Can you run;


systemd-analyze critical-chain

Also I asked about the amount of installed ram?

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

goro_goren · January 28, 2014, 4:54pm

~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @13.540s
└─multi-user.target @13.540s
  └─sshd.service @13.261s +278ms
    └─network.target @13.220s
      └─NetworkManager.service @9.352s +3.867s
        └─basic.target @9.320s
          └─timers.target @9.319s
            └─systemd-tmpfiles-clean.timer @9.316s
              └─sysinit.target @9.316s
                └─apparmor.service @4.131s +5.184s
                  └─systemd-tmpfiles-setup.service @3.850s +280ms
                    └─local-fs.target @3.849s
                      └─var-run.mount @3.844s +5ms
                        └─local-fs-pre.target @3.843s
                          └─systemd-tmpfiles-setup-dev.service @3.435s +406ms
                            └─kmod-static-nodes.service @2.044s +1.389s
                              └─systemd-journald.socket
lines 1-20

I know 2**gb **is not too much ram these days…I’d like to to buy 2gb more but I think my lappy does not support it…

I appreciate you time homie!

goro_goren · January 28, 2014, 4:55pm

yep! You got it!!

malcolmlewis · January 28, 2014, 5:13pm

On Tue 28 Jan 2014 03:56:01 PM CST, goro goren wrote:

malcolmlewis;2620082 Wrote:
> Hi
> Can you run;
> >
Code:

> >
> systemd-analyze critical-chain
>

> >
> Also I asked about the amount of installed ram?

Code:

~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the “@”
character. The time the unit takes to start is printed after the “+”
character.
graphical.target @13.540s
└─multi-user.target @13.540s
└─sshd.service @13.261s +278ms
└─network.target @13.220s
└─NetworkManager.service @9.352s +3.867s
└─basic.target @9.320s
└─timers.target @9.319s
└─systemd-tmpfiles-clean.timer @9.316s
└─sysinit.target @9.316s
└─apparmor.service @4.131s +5.184s
└─systemd-tmpfiles-setup.service @3.850s +280ms
└─local-fs.target @3.849s
└─var-run.mount @3.844s +5ms
└─local-fs-pre.target @3.843s
└─systemd-tmpfiles-setup-dev.service @3.435s +406ms
└─kmod-static-nodes.service @2.044s +1.389s
└─systemd-journald.socket
lines 1-20

I know 2*gb *is not too much ram these days…I’d like to to buy 2gb
more but I think my lappy does not support it…

I appreciate you time homie!

Hi
What model laptop from the label on the bottom of the system?

Can you run and post the output from the command;


dmidecode -t Memory

There should be more lines as it only showed 1-20?

I would surmise that this might be as good as it gets…

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

27 tty's?...

goro_goren;2620059 Wrote:
>
>
> >
Code:

> > ~> systemd-analyze blame | head
> 6.541s apparmor.service
>

malcolmlewis;2620082 Wrote:
> Hi
> Can you run;
> >
Code:

> >
> systemd-analyze critical-chain
>

Code:

27 tty's?...

goro_goren;2620059 Wrote: > > > > Code:

> > ~> systemd-analyze blame | head > 6.541s apparmor.service >

malcolmlewis;2620082 Wrote: > Hi > Can you run; > > Code:

> > > systemd-analyze critical-chain >

Code:

goro_goren;2620059 Wrote:
>
>
> >
Code:

> > ~> systemd-analyze blame | head
> 6.541s apparmor.service
>

malcolmlewis;2620082 Wrote:
> Hi
> Can you run;
> >
Code:

> >
> systemd-analyze critical-chain
>