Alright. From the top.
Yes, and no difference. Very similar failure messages from lightdm. I can post the log but I donāt think they provide much insight.
When modifying the grub config at boot up, I couldnāt find the keyword āquietā anywhere. I instead with the second half of the instructions and went and modified /etc/default/grub
. The following line
#GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 nowatchdog"
becameā¦
GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi='Windows 2018' rd.udev.log-priority=3 nvme_core.default_ps_max_latency_us=5500"
Then ranā¦
> sudo grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot: initramfs-linux-lts-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: initramfs-linux-fallback.img
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
done
After reboot there was definitely a difference. I saw a long string of modules successfully initializing, followed by my cursor stopping in place and nothing happening. lightdm and sddm both still fail to start.
But, that makes me optimistic, this is the most Iāve seen my laptop do on bootup. Can you ELI5 what did I just do to my grub config? And how can I get a log of the boot up procedure so I can post it here?
Also /dev/sda1
is one of the partitions for a EOS usb image I used to flash my laptop.
edit: when I mention the ā. I saw a long string of modules successfully initializing, followed by my cursor stopping in place and nothing happening.ā above, I think this is the start-up sequence by systemd. Now, it yields a lot of āokā messages, which fit the following format.
[ OK ] Started Authorization Manager.
I donāt know where I can get this log. Naturally, the last 4 messages areā¦
[ OK ] Stopped Light Display Manager.
Starting Light Display Manager.
[ OK ] Finished TLP system startup/shutdown.
[ OK ] Started Light Display Manager.
Then it stops with a blinking cursor. I donāt think this is terribly surprising at this point.
> sudo systemctl status lightdm
ā lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2020-10-28 08:46:55 PDT; 20min ago
Docs: man:lightdm(1)
Process: 928 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
Main PID: 928 (code=exited, status=1/FAILURE)
Oct 28 08:46:55 skyedev systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Oct 28 08:46:55 skyedev systemd[1]: Stopped Light Display Manager.
Oct 28 08:46:55 skyedev systemd[1]: lightdm.service: Start request repeated too quickly.
Oct 28 08:46:55 skyedev systemd[1]: lightdm.service: Failed with result 'exit-code'.
Oct 28 08:46:55 skyedev systemd[1]: Failed to start Light Display Manager.