bjoernvold.com

This is an error I get on boot. Is it because I'm not using Legacy in BIOS, or ? It doesn't pick up in dmesg when I run it.
It does give a systemctl status command to run, but it goes by so fast on boot I can't see what it is.

[FAILED] Failed to start Load Legacy Module Configuration
See systemctl blah blah blah status something ???

Any clue about this one?

Thanks.

There are a few messages like that on boot. Mostly they have no negative impact (remember that annoying kernel module message?).

Should show you all error messages after the last boot (again; don't panic if there are a lot of them ).


Will show you all messages of the last boot.

The Message you get is probably to check out:

and probably something like this:

https://bugs.mageia.org/show_bug.cgi?id=4172
It should have been fixed here

https://bugs.mageia.org/show_bug.cgi?id=3658

Just guessing based on your description

Maybe a simple:
will clear things up.
It will give you a PID which you can further investigate with:
XXX being the pid number...

viking60 wrote:The Message you get is probably to check out:

Code: Select all

systemctl status fedora-loadmodules.service

This is what it was saying on boot, now that I see it here. This is it.

Thanks! I'll report back when I run it; me 'n systemctl don't jive very well so I may need further help.

Sure that is what we are here for

OK, here's the output. No clue what it all means. I can tell some of it, but need more refreshing on skillz for all of it:
systemctl status fedora-loadmodules.service output (got a General SQL error when I tried to post it in code tags)
systemctl status systemd-modules-load.service output (again, got a General SQL error trying to post this in code tags)
So, the next step would be, ???

Thanks so much.

Looks like that Fedora bug is still active - I don't know what that service does but it is not starting correctly on your box.
Maybe
can confuse us on a higher level.

OK, I think I'll report on the bug. It's been like this ever since I installed Mageia 5, no updates have cleared it up. I'll post the journalctl command here when I'm back at the computer later today or this evening my time.

Oh, sorry, I meant to post this to you as well:


Interesting... and yes, somewhat confusing. I find it really strange that it's considered a modprobe error???

I've also reopened the relevant bug.

Hm there must be a modprobe procedure that takes care of this It sure looks like a bug.

Well, there is a response on the bug already.
Ssooo... Just how do I remove hdaps from my configuration? For that matter, what is hdaps? Evidently it has to go because it's what is causing this.

Edit: This is it.
I'm not so sure I should remove that - maybe file a bug on it if there isn't one already.

It seems to be DE dependant.
If you have KDE you should have something like "kdeplasma-applets-hdaps-monitor". It should be possible to deinstal it.

Ugh. That's what I'm running, yeah, but the error is several times on boot, so it can't be just a DE dependent, can it? I'll check it out though.
Wait, yeah, it can - it would need hdaps on boot to run anyway, is my thinking.

Update: Nothing hdap or hdaps is installed. I tried in file names, in description, in summary, in everything. Ah, wait, the kernel comes up and so does pm-fallback-policy. That's it though.
I guess that could be a reason it's failing, or maybe it's something else making hdaps fail?