Failed to load Kernel Modules

[haaber]

This is the first line while booting. So I checked systemctl status
systemd-modules-load.service that says the below. I see no errors .. all
OK then??

Thank you, Bernhard

[me @dom0 ]

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 Wed 2017-11-22 10:30:29 EST; 2min 35s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 1299 ExecStart=/usr/lib/systemd/systemd-modules-load
(code=exited, status=0/SUCCESS)
Main PID: 1299 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/systemd-modules-load.service

Nov 22 10:30:29 dom0 systemd-modules-load[1299]: Inserted module 'uinput'
Nov 22 10:30:29 dom0 systemd-modules-load[1299]: Module 'xen_evtchn' is
builtin
Nov 22 10:30:29 dom0 systemd[1]: Started Load Kernel Modules.

[cooloutac]

I get failed to load kernels on boot of every qubes version. I just ignore it.

[Tom Zander]

On Tuesday, 28 November 2017 14:18:44 CET cooloutac wrote:
> Of course many feel Qubes is for more advanced users, and apparently that
> will become a self fulfilling prophecy in version 4.

Looking at the (lack of) UI tools at this time, you can be excused thinking
this. I personally think its a focus issue. The core devs are good at
security, and that is where their focus is.
The people behind Qubes don't have to focus on usability, though. They can
focus on an awesome core while others focus on tooling.

I'd love to help write some great user interfaces that improve upon the
Qubes supplied ones (which is a low bar), and do that in an open source
manner which help improve the usability for everyone.
As long as I don't have to use python, so the only thing we really need is a
good interface which is language-agnostic.

--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel

[cooloutac]

understandbale

[Unman]

On Tue, Nov 28, 2017 at 05:03:56PM +0100, 'Tom Zander' via qubes-users wrote:
> On Tuesday, 28 November 2017 14:18:44 CET cooloutac wrote:
> > Of course many feel Qubes is for more advanced users, and apparently that
> > will become a self fulfilling prophecy in version 4.
>
> Looking at the (lack of) UI tools at this time, you can be excused thinking
> this. I personally think its a focus issue. The core devs are good at
> security, and that is where their focus is.
> The people behind Qubes don't have to focus on usability, though. They can
> focus on an awesome core while others focus on tooling.
>
> I'd love to help write some great user interfaces that improve upon the
> Qubes supplied ones (which is a low bar), and do that in an open source
> manner which help improve the usability for everyone.
> As long as I don't have to use python, so the only thing we really need is a
> good interface which is language-agnostic.
>

Hi Tom

From my experience with less advanced users, the last thing they want is
more tooling, and more UI tools. What they want is a system where the
intricacy is completely hidden, with a simple menu that leads them by
the nose to the right qubes.

I think I must be missing your point - it might be clearer if you gave
examples of tasks that these user interfaces would serve.

cheers

unman

[Tom Zander]

On Thursday, 30 November 2017 03:30:35 CET Unman wrote:
> I think I must be missing your point - it might be clearer if you gave
> examples of tasks that these user interfaces would serve.

I think we have some great examples already which could use more love.

The devices app, which allows you to assign drives (partitions really) to
qubes.
It is currently less than complete.
Not only does it have bugs (shutting down a qube and starting it again makes
a logical drive never be shown there again).
But more importantly it just adds a new device in /devs/ without mounting
it. It should allow a user to the first time select a qubes dir to mount it
on.
The goal; to avoid the user having to use the CLI.

But also the Qubes-create-new VM GUI app is rather badly designed. It uses
lots of terms like ‘appvm’ and similar, which is Ok.
The problem is that none of these terms are explained. You have to go to
browse on the internet to find out what those mean.
It would be quite easy to add documentation inside the app in order to
explain it. Maybe add a graphic-widget that shows not just the list of
template VMs, but also which VMs are based on it.
Because honestly, what a user wants is likely “make another VM like Work”.
But then they have to first find out that “Work” is based on a named template,
is an appvm and remember that and open the create-vm screen to base it on
the same...

In short, the tools are designed by technical people to do what they already
know how to do. They are not designed for new users that need to discover
the system at the same time as they get tasks done.

Ths is just an example or two, I hope it explains my thinking.

[Mr. Malatesta]

Absolutely. Imagine the prospective user who requires as much security as is possible who eventually figures out how to install Qubes...someone like me who spent a lot of money because he thought that the Librum would boot right up and the creation of different reasonably secure VM's would be a click away. After purchasing books on Fedora and Linux and Python I have my relatively useless Librum and my impossible to install and use Quebes to remind me that if I could only understand step by step what 99 percent of you guys are talking about I might be able to keep professional/confidential files secure...
Very frustrating. I daily wait for anything that literally shows me the steps to do anything on this obviously important architecture e.g. turn on the machine; the first screen will look like this; at the prompt you will access the menu by typing "x;" then type the following (without the quotes/or, with the quotes): ..... Patiently awaiting a very needed tool...unless Analog is the only answer for those who have not studied coding?