Ubuntu
linux package

  1. Bug #1705748
  2. Comment #73

Comment 73 for bug 1705748

Revision history for this message
Steve Roberts (drgrumpy) wrote :

I installed the files,
removed the nvme_core.default_ps_max_latency_us=0,
did an update-grub and rebooted...
failed to boot into graphical interface and then hung... reset needed

Command line: BOOT_IMAGE=/vmlinuz-4.14.0-rc4-evo+ryzen root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro

Suspect this is the issue:

Oct 16 10:40:17 phs08 systemd[1]: Started Light Display Manager.
Oct 16 10:40:18 phs08 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Oct 16 10:40:18 phs08 systemd[1]: lightdm.service: Unit entered failed state.
Oct 16 10:40:18 phs08 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Oct 16 10:40:18 phs08 systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.

Oct 16 10:40:18 phs08 gpu-manager[2291]: /etc/modprobe.d is not a file
Oct 16 10:40:18 phs08 gpu-manager[2291]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Oct 16 10:40:18 phs08 gpu-manager[2291]: Error: can't open /lib/modules/4.14.0-rc4-evo+ryzen/updates/dkms

Oct 16 10:40:21 phs08 systemd[1]: gpu-manager.service: Start request repeated too quickly.
Oct 16 10:40:21 phs08 systemd[1]: Failed to start Detect the available GPUs and deal with any system changes.
Oct 16 10:40:21 phs08 systemd[1]: lightdm.service: Start request repeated too quickly.
Oct 16 10:40:21 phs08 systemd[1]: Failed to start Light Display Manager.