update to 9.0 with libreboot, now computer won't boot into GUI
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.
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
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.
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!
That message at startup is totally benign. You can ignore it.
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?
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 :)
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
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
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?
I just got the Taurinus X200 from Libiquity yesterday. I can confirm that Trisquel 9 works well on it. I had to remove the modified libreboot from Libiquity and just software flash the rom using the utilities on libreboot.org and I just copied the rom image that I needed to the utilities directory rebooted and did a text intstall because the graphical install wouldn't boot. Just make sure not to install grub at the end of the install.
Hopefully this helps and Thanks @libreleah
Thansk for the hint however it didn't help me. I've tried 9.0 on a Curry/PC World own brand "Advent" laptop. 9 installs find and works fine with no problems - until the pending updates are installed, then the booting issues start. I attached my bootlog to another post so maybe that may help.
The problems I'm experiencing doesn't seemed to be BIOS related as both libre and non BIOS have the problems - even using fresh ISO downloads. Maybe I'll stick with 8 as I don't have problems with that.
What I also find confusing is only a couple of people seemed to be having the problem, either no one is doing fresh installs or using VMs for testing - I'm not sure.
Just a bit downhearted as 8 worked fantastically, I feel 9 should still in beta testing.
Just downloaded a new iso of 9.0, still having problems booting after a fresh install. Attached the systems boot journal can someone see why my system is stalling on boot?
| Attachment | Size |
|---|---|
| bootup.log | 207.42 KB |
Has no one managed to get to the bottom of this problem? I have tried a fresh iso download of mate 9 and mini 9 i386 both of have starting issues. Oddly enough Trisquel 8 & Triskel 9 (KDE) boots fine even when updated however support for mounted samba shares is not good on KDE between applications
I have tried lubuntu which works fine - also with all updates
Hello,
I had the same problem on my HP Compaq nx7300 32 bit laptop without Libreboot. I tried out the Trisquel-mini. I tried it a few times with a new installing Trisquel 9 and upgrading from Trisquel 8 to 9. Without success.
I think it is an lightdm or X issue.
These are the steps I did and it worked for me:
A fresh install of Trisquel 9 or an upgrade from Trisquel 8 to Trisqul 9.
If you can login via terminal you can do the following:
1. Don't run a system upgrade after the installation!
2. Install lightdm-gtk-greeter-settings. sudo apt install lightdm-gtk-greeter-settings. This will change a little bit your login screen.
3. Now run a system update. sudo apt update && sudo apt upgrade
4. Reboot your system.
I hope it will work for you too.
Diopon
Worked works a treat, thanks.
I succeeded with doopon's approach WITHOUT a fresh install.
After a release upgrade AND a following update I had the issue of the OP.
It was solved solely by entering terminal mode (ctrl+alt+F1), logging in and then run the commands proposed by diopon: sudo apt update && sudo apt upgrade
Sorry for the delay in getting back, your suggestion did work and your right about the sign in manager being different!
I tried and am currently using using the KDE version "Triskel" which works quite impressively moreover it seems to be a bit more savvy of resources - I recommend giving it a go.
I think I'll next for the next snapshot point of 9 mini/MATE as I am guessing that will have the corrections needed for a smoother experience.
I did find another way around the problem is when installing automatically sign in instead of prompt for sign in.
Thanks for the reply.. I'll pop on a spare laptop and check it out.
Thanks
a
Hello diopon,
I had no problem with mine until I messed with it to see if the commands I had copy and pasted in another thread, dealing with a seemingly similar issue, from libreboot.org worked. I ran 'systemctl disable lightdm'. After that I got error messages when I tried to enable it.
I tried just your method and still only got a log in prompt in tty.
I ultimately, uninstalled every installed package of "lightdm*", and after reboot, reinstalled those packages you mentioned in your post and lightdm was again started and the login screen appeared.
It took a bit to get the screen image back to "etiona". The settings lightdm-gtk-settings app was not affecting that screen image even after I pointed it to the "etiona.jpg".
As you mentioned, the final result is not quite the same as the original login page, which had the login prompt and the title bar hidden, unless or until the mouse would be moved.
Note: Mine was working originally because I had never run an update or upgrade after the 2nd installation. Also, I notice that even though I have auto updates turned off in the software manager app., I see in the "System Monitor" app that there appears to be an attempt to auto update that fails.
Thanks
Yes diopons solution worked for me too. It seems the login on Trisquel 9 mini (32bit) gets broken with the first update.
It's a shame that it only works with the old login since the new one is very beautiful and fits well to the new design. The old one is nice too but it doesn't fit as well to the system. Probably mainly because I am used to it and it just feels like the last version.