3

I've been running Ubuntu 20.04.3 LTS on my Lenovo Thinkpad T14 for around a year now with little to no issue. However, very recently I have been experiencing issues with ubuntu-desktop not loading on boot.

Occasionally when I boot my machine I will be met with a black screen with a cursor flashing in the top left corner (rather than booting to the log in screen). Thus far I have managed to fix this by going to tty5 or tty6, logging in and using the command apt-get install --reinstall ubuntu-desktop. After rebooting, the system then tends to boot to the desktop as normal. I say tends as it is not always the case, e.g., today I had to reinstall ubuntu-desktop twice before it worked.

One possible cause that I can see is I have a Nvidia MX330 graphics card, which has not played so nicely with my machine in the past. For instance I previously upgraded the driver for the card and could no longer boot my machine until I rolled back the upgrade. Moreover, I recently purged all of the Nvidia packages from my machine apt-get purge nvidia* and now my machine runs a lot smoother!

I am wondering if anyone has any ideas as to why ubuntu-desktop would be sporadically breaking or as to ways to debug this issue? I checked my update logs less /var/log/apt/history.log and it doesn't seem to correlate with recent updates.

Update 31/08

My issue has seemingly evolved slightly. No longer to I need to reinstall ubuntu-desktop but now when I am stuck at the black screen I can simply switch to tty5 and then back to tty1 and the desktop environment will load. It is a bit strange but it works. Just to clarify I want to understand why my boot is not working properly (although the extent to which it is not working has now changed quite a bit).

I actually don't care so much about the official Nvidia drivers for the graphics card, since switching to the nouveau driver my battery life is longer, the laptop is a lot cooler and everything runs smoother.

The kernel I am currently booting is Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22. Looking at the update logs I am fairly reasonably certain that the problems did start after a kernel upgrade.

7
  • Have you tried doing an update and upgrade?
    – David
    Aug 27, 2021 at 8:41
  • @David Yes, during the first time this occurred I made sure to update and upgrade.
    – Rammus
    Aug 27, 2021 at 9:10
  • So, does this mean your problem is currently fixed? You just want to see if you can solve this problem and have NVidia drivers working? Unfortunately, getting it working is not always easy. What you can try is the latest NVidia drivers from its web site. I can't give you an explanation other than maybe "compatibility". That is, if it doesn't work, remove it. And then try again if you see new drivers on the web site. Maybe there are other suggestions that others can give, but that is what I'd try as a start.
    – Ray
    Aug 29, 2021 at 11:37
  • 1
    Or the mesa drivers. When was your last kernel upgrade? (Remember this can happen automatically as part of the update / upgrade process.) You can probably grep it pretty easily from the Apt logs. Let me know if you need help. Does this correspond to the first incident?
    – Nate T
    Aug 29, 2021 at 16:17
  • hi @Rammus. Which kernnel are you booting? ("uname -a on a terminal")
    – jpbrain
    Aug 31, 2021 at 0:39

2 Answers 2

1

Since you have purged all of your nvidia* packages, it's likely that you are now using the nouveau driver, which you can check by running lsmod | grep -Ei nvidia\|nouveau.

I had reliability issues with the 460 and 465 versions of the nvidia driver, which I fixed by downgrading to version 450. You can see a full list of available drivers with apt list nvidia-driver-*

0

After a successful login, open a terminal an type
sudo systemctl set-default graphical.target
Then type sudo shutdown -r now

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .