Arch Linux

fdservices

Member

From: France

Registered: 2012-02-06

Posts: 413

Times to start up

Arch takes about 1.5 minutes to start up on my laptop.

The systems up to date and running KDE4, also up to date.

The last five lines in dmesg are:

[   17.136178] Bluetooth: RFCOMM ver 1.11
[   46.120227] EXT4-fs (sda1): re-mounted. Opts: commit=600
[   46.570741] EXT4-fs (sda6): re-mounted. Opts: commit=600
[   71.883345] eth1: no IPv6 routers present
[   96.228147] fuse init (API version 7.18)

I presume that the [xx] indicates the elapsed time,if so can someone please explain what is happening over the last 80 seconds?

Thanks

Dheart

Member

From: Sofia, Bulgaria

Registered: 2006-10-26

Posts: 956

Re: Times to start up

Are you using classic (old) init or systemd? Any peculiar output that you might see when booting?

---

My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...

fdservices

Member

From: France

Registered: 2012-02-06

Posts: 413

Re: Times to start up

initd

No odd messages when booting

Last edited by fdservices (2012-08-28 08:34:15)

x33a

Forum Fellow

Registered: 2009-08-15

Posts: 4,587

Re: Times to start up

Arch takes about 1.5 minutes to start up on my laptop.

The systems up to date and running KDE4, also up to date.

The last five lines in dmesg are:

[   17.136178] Bluetooth: RFCOMM ver 1.11
[   46.120227] EXT4-fs (sda1): re-mounted. Opts: commit=600
[   46.570741] EXT4-fs (sda6): re-mounted. Opts: commit=600
[   71.883345] eth1: no IPv6 routers present
[   96.228147] fuse init (API version 7.18)

I presume that the [xx] indicates the elapsed time,if so can someone please explain what is happening over the last 80 seconds?

Thanks

There is a 35 seconds difference between the 3rd and 4th message. So i suspect there's a network problem. Try disabling ipv6 for starters.

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 29,573

Website

Re: Times to start up

Disable IPv6 and/or background network.

---

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

pilotkeller

Member

From: Canada

Registered: 2011-12-22

Posts: 513

Website

Re: Times to start up

Bluetooth finishes loading
[   17.136178] Bluetooth: RFCOMM ver 1.11

Now the last checks of your first and 6th partition then they are mounted.
[   46.120227] EXT4-fs (sda1): re-mounted. Opts: commit=600
[   46.570741] EXT4-fs (sda6): re-mounted. Opts: commit=600

IPv6 checks for any available routes.
[   71.883345] eth1: no IPv6 routers present

Now initd finishes.
[   96.228147] fuse init (API version 7.18)

And you are dropped to your getty program.

---

Nowhere Else and Beyond - Logon To Live On

fdservices

Member

From: France

Registered: 2012-02-06

Posts: 413

Re: Times to start up

That was interesting.

I disabled IPv6 and now the last lines of dmesg show:

[   16.731690] Bluetooth: RFCOMM ver 1.11
[   46.681332] EXT4-fs (sda1): re-mounted. Opts: commit=0
[   47.225736] EXT4-fs (sda6): re-mounted. Opts: commit=0
[   99.761470] fuse init (API version 7.18)

which indicates that the time is unchanged overall.

fdservices

Member

From: France

Registered: 2012-02-06

Posts: 413

Re: Times to start up

fuse is required for compiz amongst others, but on my PC I do not get any messages about fuse in dmesg even though the set up is the same.

So why do I get the
[   96.228147] fuse init (API version 7.18)
message after 45 seconds on the laptop?

x33a

Forum Fellow

Registered: 2009-08-15

Posts: 4,587

Re: Times to start up

Are you measuring the startup time manually or you are just guessing it from the log times. Because kernel events appear in the log even after booting also. So even if fuse starts at 96 seconds doesn't mean that the system hasn't finished booting yet.

Also there can be different causes for fuse starting so late. First could be problem with compiz (in your case). Try disabling compiz and see if the fuse message appears or does it have any effect on the overall boot time.

Or maybe you are mounting an ntfs partition (ntfs-3g), that causes fuse to show in the log.

fdservices

Member

From: France

Registered: 2012-02-06

Posts: 413

Re: Times to start up

I was measuring roughly manually, but also looking at the various log entries to try to understand them.

I think that you are right, fuse probably starts after the boot has finished. It is strange that fuse starts on the laptop and not on the PC though. Both are running compiz.

I don't mount anything other than the root and home filesystems, and I do not have any ntfs partitions.

Thanks to everyone for all the help.