update to 9.0 with libreboot, now computer won't boot into GUI

9 risposte [Ultimo contenuto]
dln949
Offline
Iscritto: 02/13/2018

I have a Libiquity Taurinus X200. I recently did the upgrade of Trisquel to 9.0. Did not get any error messages.

Now, when I boot the computer, it briefly goes to a black screen with this on it:

DMAR: Failed to map dmar2

Then, it brings up a different black screen asking me to login to Trisquel. I can log in, but I am then in terminal mode, I never get to the Trisquel GUI desktop.

I am far, far from a computer expert. I have searched around, but maybe I'm using the wrong search terms, I'm not finding anything helpful.

What are these messages telling me?

How do I fix this?

Thanks in advance.

eliotime3000
Offline
Iscritto: 06/05/2016

Well, I seriously don't know about it, but @libreleah is actually working woth Trisquel 9 and Libreboot. So she can help you in this kind of business.

You can contact her throught this link:
https://trisquel.info/es/users/libreleah

libreleah
Offline
Iscritto: 04/03/2017

I can confirm that Trisquel 9 works on Libreboot systems. However, I think Libiquity uses their own custom libreboot images. I would suggest that you flash the latest stable version of libreboot, from libreboot.org. You can do this with taking apart your laptop. Instructions are provided on libreboot.org

However, the above is likely not your problem, just general advice I give to people who buy from that particular company. Last I checked, they use Libreboot but not the official version.

It sounds to me like this is a bug in Trisquel 8 upgrading to Trisquel 9 though, and your Trisquel installation b0rked. I have no issue doing fresh Trisquel 9 installs on Libreboot systems.

Perhaps try a fresh install?

(obviously back up your data first)

Doing an in-place upgrade from one distro to another is never a good idea.

kerdadit
Offline
Iscritto: 06/06/2018

I also have a Taurinus X200, and I get the DMAR error every time I boot. I'm currently running Trisquel 8. The GUI starts up just fine, even with that error. I might try the upgrade myself this weekend. Please keep us posted on how it's going for you!

libreleah
Offline
Iscritto: 04/03/2017

That message at startup is totally benign. You can ignore it.

amtrakuk
Offline
Iscritto: 11/25/2019

I have the same problem with a Libreboot X60. Works fine under Trisquel (mini) 8 but after upgrading to 9 and running available updated the X server seems to crash after the trisquel plymouth screen.

I have been playing round with a Advent 5421 with a non supported SIS GPU. After doing a Ctl+Alt+F1 and trying to run startx, the error suggested the access to the Xserver is denied. That may also be the same issue?

libreleah
Offline
Iscritto: 04/03/2017

This is likely not a Libreboot issue. I do fresh installs of Trisquel 9 all the time.

This is most likely just a bug when updated in-place from Trisquel 8 to Trisquel 9, without doing a fresh install. Therefore it could happen on any system.

I can confirm that Trisquel 9 works very well on Libreboot systems :)

amtrakuk
Offline
Iscritto: 11/25/2019

A fresh install of 9 seems to go without a hitch on my libreboot X60. A reboot into a fresh install of 9 works no prob. Problem I started when I installed the available updates - I'm thinking it maybe something to do with connecting to the x-server in the latest push of updates. I should be getting a T60 tomorrow so will try a lenovo bios'd build, than pop on libreboot - thanks for your feedback

amtrakuk
Offline
Iscritto: 11/25/2019

I can confirm Libre boot doesn't seemed to be the cause. I tried a new build on a Lenovo BIOS'd T60 with Trisquel 9 mini (i386) with the same results. The live ISO works fine. The fresh install boots and works fine. The problems start once this latest round of updates are applied. For me something to do with the X server???

I can do a Ctrl+Alt+F1 to get a command prompt up. running 'startx' brings up a generic LXDE session

amtrakuk
Offline
Iscritto: 11/25/2019

using the command startlxde generates

(lxsession:1255): Gtk-WARNING **: 17:07:21.940: cannot open display:

I dont know if this could be a clue?