Booting Problem

[tuxpenguin8]

Hi,

When I boot into the grub bootloader and load Mageia, lots of the time it keeps displaying a black screen and the mageia normal loading screen keeps appearing, and it is much much slower to load than usual. So I have to reboot it and go into safe mode then reboot into normal mode, and it boots fine. Do you know what might cause this.

If youn need more info please reply saying what more info you need.

Thanks,

[doktor5000]

When I boot into the grub bootloader and load Mageia, lots of the time it keeps displaying a black screen and the mageia normal loading screen keeps appearing, and it is much much slower to load than usual.

Did you ever press Esc at that time to see what happens in the background?

Also, did you try to wait for say 5 minutes to see if it completes? E.g. compiling dkms kernel modules after a kernel update will take ~1-3 minutes depending on your system speed per kernel module. So if you have 3 dkms kernel modules installed (virtualbox, nvidia, broadcom-wl maybe) it might take up to 10 minutes on a slow systems.

If this happens next time, after the next normal boot please post the output of

Code: Select all

journalctl -ab-1 --no-pager

run as root (shows complete Log of last boot)

[tuxpenguin8]

Hi,

I don't know if this will be of any help but, the times when it won't boot in it keeps displaying this text:
P^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A
Do you know what this means?

Thanks,

[tuxpenguin8]

Hi,

Yes I did press ESC on the times it won't boot, but it is useless. But when I do it on a normal boot, that boots up, it displys text of what is happening. Why won't it work for the one that wont boot. And also is a DKMS a framework used to generate linux kernel modules whose sources do not reside in the linux source tree. So basically, are they pieces of software that allow 3rd party drivers and other kernel modules, that do not ship with linux, but have been added by the user, to run as a kernel module.

Thanks,

[doktor5000]

And also is a DKMS a framework used to generate linux kernel modules whose sources do not reside in the linux source tree. So basically, are they pieces of software that allow 3rd party drivers and other kernel modules, that do not ship with linux, but have been added by the user, to run as a kernel module.

Yes and no. They allow to compile basically anything related to kernel when a new kernel is booted the first time, and the relevant kernel headers are installed.

[tuxpenguin8]

So, DKMS compile 3rd party stuff and other stuff that need to be functioning for the o/s to use them, as kernel modules and etc. And, I've haven't installed new kernels, still using 3.12.20. And also what are kernel headers, and what do they do?

Thanks,

[tuxpenguin8]

Hi,

I did wait for some time for it to boot, (on the times when it was very slow) and it booted. I restarted the computer and it rans smoothly. But what I don't get is that, it keeps occuring, it done it once it shoud be done, right? And also what init system does mageia use by default, if it is sysvinit or similar init systems, that may be the problem, because I read in Linux Format, that one slow service, slows down the entire booting process, whereas in systemd, one slow service won't slow down booting, because they are ran in paralell, not serial, so no queuing behind the slow service. So if mageia uses sysvinit or similar init systems by default, it would be better if we chose systemd as our default init system, because it is more reliable, faster, unit files are more universal than init files, systemd keeps the services running, and there is no queuing behind the slow one. But I don't know if mageia has init or systemd as the default init daemon.

Thanks,

[doktor5000]

For kernel headers, please have a look at http://lmgtfy.com/?q=what+are+kernel+headers

Since Mageia 2 we're using systemd as the only init system.

If you want to know why the boot was so slow, then the next time your system boots slow, let it finish,
and run the following commands as root. Post the output of the first command and attach the created graphic boot.svg here.

Code: Select all

systemd-analyze blame | head
systemd-analyze plot > boot.svg

[tuxpenguin8]

Hi,

I've tried booting up but even after 30 MINUTES, it wont boot!!! So every time I have to boot into Safe Mode. I would like to make one note, that is that I have put vitualbox on my PC and I am running a FreeBSD Virtual Machine.

If you have any advice, questions, infomation, or you might know what is causing this, please post below.

Tahnks,

[doktor5000]

I would like to make one note, that is that I have put vitualbox on my PC and I am running a FreeBSD Virtual Machine.

You should have mentioned that earlier.
Check https://bugs.mageia.org/show_bug.cgi?id=44

[tuxpenguin8]

At the time of the original writing, I didn't have virtual box. I've had virtual box for about 3 days.

Thanks,

[doktor5000]

So the slowness is not about the FreeBSD virtualbox boot, but about the boot of your physical box? Then forget my last post.

I can only repeat my last advice:

If you want to know why the boot was so slow, then the next time your system boots slow, let it finish,
and run the following commands as root. Post the output of the first command and attach the created graphic boot.svg here.

Code: Select all

systemd-analyze blame | head
systemd-analyze plot > boot.svg