Hi
i have 12.1 on my computer but it takes something around 20 seconds to show me the gdm/kdm. i think that it must be less than this, so i’ve posted a picture showing were the boot process spends most of it’s time. the photo is at bottom of the post (sorry for quality, awful HTC camera ) and these the issues i’m talking about:
first it fails to execute ifup-sysctl at the 3rd line. what is the problem? how can it be solved?
seconds it seems that it is doing a fsck. as far as i can remember, fsck was mandatory only one time in about 50 boots; but it does it every time. is everything ok? or it is the problem?
after that it shows an error with graphics card. what does it say? is it a real problem? also my graphics card is nvidia, but it talks about intel. what is it?
just after the previous error, it prints an error about SN06. it think it is a problem with vaio laptops, huh? because i had it in ubuntu too.
the last line takes the most time, or it seems so. i think it is showing the fsck report, and telling that just everything is ok! after printing this line, the system sticks maybe around 4-5 seconds, that is really annoying. i don’t know whether this lines consumes this time or the processes that are executed after that are doing this. is there any better log to look into?
sorry, i have entered wrong timings. i rebooted the system and measured again with a clock:
from grub menu to gdm, takes 57 seconds. in the line after “Mounting root” it sticks around 10 seconds, and it takes near 30 seconds after the last line.
On 2012-02-15 21:16, sazary wrote:
>
> Hi
> i have 12.1 on my computer but it takes something around 20 seconds to
> show me the gdm/kdm. i think that it must be less than this, so i’ve
> posted a picture showing were the boot process spends most of it’s time.
In a terminal, as root, run:
systemd-analyze blame
and find out where the time is spent. Alternatively, you can also do
systemd-analyze plot > p.svg
Then you can use “display p.svg” to see the graphics, or use the tool you
prefer. The graphics shows where time is used.
> - seconds it seems that it is doing a fsck. as far as i can remember,
> fsck was mandatory only one time in about 50 boots; but it does it
> every time. is everything ok? or it is the problem?
I don’t remember, but some filesystem types are quick checked on every boot.
> - the last line takes the most time, or it seems so. i think it is
It just seems so, it is doing things that do not print any message.
But 20 seconds is fast.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2012-02-15 21:56, sazary wrote:
>
> sorry, i have entered wrong timings. i rebooted the system and measured
> again with a clock:
> from grub menu to gdm, takes 57 seconds. in the line after “Mounting
> root” it sticks around 10 seconds, and it takes near 30 seconds after
> the last line.
The method I posted will tell you the exact timing and where it waits.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
wow! really thanx! that was a powerful tool. based on it’s output, it takes 55 seconds to boot, that i think is way too long. this is the blame output:
based on the image, i think that the problematic process is NetworkManager, exactly “NetworkManager-wait-online.service”. am i right? if yes, then what should i do?
On 2012-02-16 08:26, sazary wrote:
> based on the image, i think that the problematic process is
> NetworkManager, exactly “NetworkManager-wait-online.service”. am i
> right? if yes, then what should i do?
Look at the log to see what it does. Wait for an IP? Wait for wifi? Wait
for a network share?
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
But you’ve said that most of the time is spent on the screen that you’ve posted and it has nothing to do with networking directly. The posted picture shows that most of the time is spent on fsck. Network services may take a long time to set up, because it cannot find network configuration script file at first and fsck on /dev/sda5 (this partition is mounted as “/”, right?) is run to fix it. I am not sure, but I think it may work this way.
fsck shouldn’t run every time you boot if you haven’t told the OS to do so - there might be something wrong with your hard drive, especially with partition /dev/sda5.