On 23/07/15 08:59, Roderick Johnstone wrote:
On 22/07/15 21:46, Richard Shaw wrote:
> On Wed, Jul 22, 2015 at 12:57 PM, Roderick Johnstone <rmj(a)ast.cam.ac.uk
> <mailto:firstname.lastname@example.org>> wrote:
> So, having copied the akmods.service file to /etc/systemd/system (as
> Harald Reindl suggested) and added --force it is now building and
> installing the kmod on reboot.
> (Actually I also removed --from-init which I realise now was
> probably a mistake but probably not causing the problems I'm seeing
> However, the kernel module is not loaded and so the graphical
> display does not start until either I reboot again or change run
> levels and run modprobe nvidia.
> Any idea whats going on here?
> Hard to say... It's supposed to run prior to the display manager so I'm
> not sure why a reboot at that point would be necessary.
> One thing I just noticed is there doesn't seem to be a
> display-manager.service symlink anymore, when gdm.service is enabled, an
> systemd unit alias to display-manager.service is created... I would
> think that would still work but it doesn't seem to be in your case.
I'm actually using sddm so gdm.service is disabled for me and
sddm.service is enabled.
I do have a sym link:
so I'm not sure why its not working as expected.
> I wonder if I should change the requirement to "Before=graphical.target"?
I can certainly test that and report back if you like.
I tested this and it didn't work. The kmod is installed successfully but
sddm does not start.
Do you know how the kernel module is supposed to get loaded?