Qubes R3.2 Failed to Load Kernel Modules

[am]

During the boot process I get messages Failed to Load Kernel Modules.Is
this sometyhing I should be concerned about? It does not appear to have
affected the operation of Qubes in any way.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Did you upgraded the system, of did fresh install? I don't see such
error on my system... Can you provide more details, especially which
module failed to load:

sudo systemctl status systemd-modules-load

Anyway, probably harmless.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXdrXyAAoJENuP0xzK19csNB8H/R2tzN+1SL5mylazbCeZstRg
UcyJakG8PMm/MKyImETJXQNoBmJCfq1Fd0kEMC7KXPwRlHZJYIIwTi5avcTLnG5s
AvUMxziL0Nh9BORBzeH8CJ9IQUymzVtFN2+WhgmieYxwwGCsvPeulOqcVpwy891i
k0OEg6pKvqWBiu5FtFHvTb51a/e1XHBre8RBINf0jbnPFlvJQTWMYo4eioz6Ws89
MIEnssoGWLHXDIYk7QT3FHP1HKdeUJ+o2IhlF7PM5MYRKPNp/mRM3rBMO2dTj1tp
2yM4poiI6LJiIe2ZlYSVQgsKyP5PnXp/PdzWqoWGDJMMHRjaxrACfBysxBLEWrs=
=Oz8Q
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

On Fri, Jul 01, 2016 at 07:50:51PM +0000, ama...@riseup.net wrote:

> On 2016-07-01 18:26, Marek Marczykowski-Górecki wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > On Fri, Jul 01, 2016 at 08:13:32AM +0000, am wrote:
> > > During the boot process I get messages Failed to Load Kernel
> > > Modules.Is
> > > this sometyhing I should be concerned about? It does not appear to
> > > have
> > > affected the operation of Qubes in any way.
> >
> > Did you upgraded the system, of did fresh install? I don't see such
> > error on my system... Can you provide more details, especially which
> > module failed to load:
> >
> > sudo systemctl status systemd-modules-load
> >
> > Anyway, probably harmless.
>

> I did fresh install and restored some templatevms and appvms from R3.1.
>
> sudo systemctl status systemd-modules-load
> ● systemd-modules-load.service - Load Kernel Modules
> Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service;
> static; vendor preset: disabled)
> Active: active (exited) since Fri 2016-07-01 17:07:05 BST; 2h 22min ago
> Docs: man:systemd-modules-load.service(8)
> man:modules-load.d(5)
> Process: 801 ExecStart=/usr/lib/systemd/systemd-modules-load
> (code=exited, status=0/SUCCESS)
> Main PID: 801 (code=exited, status=0/SUCCESS)

Looks like a success...

Maybe this is about some other service? Does systemctl list anything
failed?

[Eva Star]

I can confirm. I have the same error while Qubes is loaded. And sudo systemctl status systemd-modules-load also write me about success.

[Alex]

On 07/01/2016 10:31 PM, Marek Marczykowski-Górecki wrote:
> On Fri, Jul 01, 2016 at 07:50:51PM +0000, ama...@riseup.net wrote:
>> On 2016-07-01 18:26, Marek Marczykowski-Górecki wrote:
>>> Anyway, probably harmless.
>>
>> I did fresh install and restored some templatevms and appvms from
>> R3.1.
>>
>> sudo systemctl status systemd-modules-load ●
>> systemd-modules-load.service - Load Kernel Modules Loaded: loaded
>> (/usr/lib/systemd/system/systemd-modules-load.service; static;
>> vendor preset: disabled) Active: active (exited) since Fri
>> 2016-07-01 17:07:05 BST; 2h 22min ago Docs:
>> man:systemd-modules-load.service(8) man:modules-load.d(5) Process:
>> 801 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited,
>> status=0/SUCCESS) Main PID: 801 (code=exited, status=0/SUCCESS)
>
> Looks like a success...
>
> Maybe this is about some other service? Does systemctl list anything
> failed?
>

It is harmless indeed, and I have a laptop with a simple Fedora 23 on it
with the same error message on boot. Still I find it active (exited) in
systemctl status, as in Qubes. It started to happen a couple weeks ago
on Fedora; I updated that laptop to Fedora 24, and the error is still there.

I think the service gets loaded twice: the first time it fails, and the
second time it succeeds. It's not a direct problem with Qubes, but I
can't confirm that the Fedora team has a ticket for this situation.
Sadly I don't have enough information to formalize a ticket...

--
Alex

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sat, Jul 02, 2016 at 10:12:02AM +0200, Alex wrote:
> It is harmless indeed, and I have a laptop with a simple Fedora 23 on it
> with the same error message on boot. Still I find it active (exited) in
> systemctl status, as in Qubes. It started to happen a couple weeks ago
> on Fedora; I updated that laptop to Fedora 24, and the error is still there.
>
> I think the service gets loaded twice: the first time it fails, and the
> second time it succeeds.

This indeed may be the case - the first one would be from initramfs.
I wonder what module fails to load... But probably nothing important.

> It's not a direct problem with Qubes, but I
> can't confirm that the Fedora team has a ticket for this situation.
> Sadly I don't have enough information to formalize a ticket...

- --

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXeWaKAAoJENuP0xzK19csI2sH/j4s1Jvm+jcDGrd8jHXtu46K
WiQ2wrftvrtM6fqOHM3xai5PYw4qjs1/PAf6iwx9COAG9Xx23Wq4FVdNss6rxOjQ
qE+blTYNLshND7MW+FbyUFIkKJbgdMkzqbX37uK9lm5V9MQaHReR8P9bbWlJq1oG
RHps/NQr9f0Am+Ya4KFTmmVwnN6FW1FHCT3o5gYIYRVpUIy0DbAzO019QU8Gk5IB
vSoED0P/VGlsVzrgdaNFvT51CUOzPoKgg5+b82P0cwzzB2V5F0LpqUAUb4Lad6Jx
5RN71quO7czXEOFwqKZITU5hgXKOl7jd6GjVcFnyuLTWFRi8fvgwjY8g3wqffTo=
=ykEu
-----END PGP SIGNATURE-----

[koto...@gmail.com]

I experience the same. It is slightly disturbing since this one of the first message appearing in the console with big red letters: FAILED. :)

[raah...@gmail.com]

On Sunday, August 7, 2016 at 3:42:15 AM UTC-4, koto...@gmail.com wrote:
> I experience the same. It is slightly disturbing since this one of the first message appearing in the console with big red letters: FAILED. :)

I have same issue too on both my qubes machines. I've always just ignored it. Hope its nothing bad. Pretty sure I've seen this on baremetal linux too.

[altern...@gmail.com]

I have the same issue, except Qubes fails to install on my Dell Latitude E6410. This was the second machine I was unable to install Qubes on, and this one I purchased specifically because I saw it on the Hardware Compatibility List. My system also presumably met the core requirements on site. I get stuck at sys-net in the latter part of installation process post-GRUB. systemd-modules-load.service will not load in recovery mode. Machine is a Dell Latitude E6410, Core i5 2.4ghz, 4 GB DDR3 ram. If Qubes worked I would love to join the community, right now seems it's still in alpha stages. Help would surely be appreciated.

[awokd]

Did you see the notes by the entries for that laptop on the HCL? For
example, one says you need to disable hyperthreading on i5. Have you tried
that?

[altern...@gmail.com]

Yeah. I appreciate your feedback. It took me a lot to finally post. I saw everything. I tried everything. Disabled hyperthreading etc. Every time I got to the configuration part it would crash at Setting up Network. I searched every Linux forum. I tried repairing my install six or seven times (this was in fact the second machine I attempted Qubes on). journalctl -xe, didn't seem to list a lot. Systemd-modules-load.service (that one wouldn't work at all), I didn't find much else to try and troubleshoot. I tried to boot in UEFI mode - that didn't work either. I ordered a third machine, a Lenovo to try. My advice to Qubes as a tech savvy user is to meet their users half-way. This is apparently only an OS for rocket scientists or extreme Linux hackers. The HCL doesn't make it very simple to even know what to buy.

[altern...@gmail.com]

And I actually know my way around a Linux command line, but the resources do not exist to help users like me. I returned the Latitude.

[awokd]

I believe that systemd-modules-load.service failure is a false alarm; I
get it too and it doesn't seem to hurt anything. I had another laptop that
would crash on setting up sys-net (Network). My workaround was to
temporarily pull the wifi card for the install. Qubes could then set up
sys-net with just the onboard ethernet and complete the install. Then I
added the wifi card back and could troubleshoot getting it added to a VM.
Once I had that resolved, I added it back to sys-net.