Booting to a TTY, not to GUI

Xmetalfanx

I will try to post all the info here, though I admit i am in a rush, posting this.

On my older desktop here, I can boot to a TTY but even with some troubleshooting I have been trying, I cant get the GUI to come back.

some general info is that the 3.99 ISO boots fine, and I have done (@ the date of the 4.0 ISO releases) alot of updates ... including kernel and xorg package updates I see and have rebooted a few times... all was fine ... I install the last few updates including lightdm (not saying that is 100% the cause) and that is when the issue started then... I have reformated and done the same thing ... with the same results. I also have to note that while the 3.99 ISO Mate initially boots fine ... the 4.0 Mate ISO had the same "only booting to a TTY" issue.

Xmetalfanx

intended to post the Xorg.log with the initial post but it keeps telling me "post of that file type not allowed" ... the thing is that I saw (at the very least) "can not load module 'sis' (module does not exist, 0)" or something to that effect and I can confirm that while i forgot the number right off the top of my head, the graphics card 100% IS a sis card

DataDrake

Xmetalfanx grab haste-it from the repo, then link the hastebin URL.

Xmetalfanx

damn ... that should have been an obvious way to do it .. .not sure why I didn't think of it ... anyway here is the pastebin URL ...

also (from Ubuntu mate installed on the hdd) here is some extra info that may be useful

inxi -Gxx
Graphics: Card: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter
bus-ID: 01:00.0 chip-ID: 1039:6330
Display Server: x11 (X.Org 1.19.6 )
drivers: vesa (unloaded: modesetting,fbdev)
Resolution: 1280x1024@0.00hz
OpenGL: renderer: llvmpipe (LLVM 7.0, 128 bits)
version: 3.3 Mesa 18.2.8 (compat-v: 3.1) Direct Render: Yes

DataDrake

uhhh. Your system is crazy outta date if you still have mesa 18 and xorg 1.19.6

DataDrake

/me facepalms.

Install xorg-driver-video-sis, it's not a default package anymore.

Xmetalfanx

installed that ... the install went fine but even after a reboot the issue still occurs .. here is the new Xorg log

Xmetalfanx

not sure if i was suppose to do something else after installing the sis package

DataDrake

Xmetalfanx Well the good news is that your video driver is loading now and I thing we have eliminated Xorg as the cause. Can I see the output of sudo journalctl -b 1 please? Needs to be run as sudo or it will omit log entries.

Xmetalfanx

So sorry for getting sidetracked and not getting back , that is rude of me after asking for help. I just tried the newly released 4.1 ISO for Mate and I didn't boot right to a GUI though what it did, I can not recall since it was a few days since i tried it ... if i remember 4.0 mate didn't boot right to a GUI, but 3.9 Mate did ... slowly doing updates to 3.9 it was ok for awhile but at some point (still not sure what update caused the issue for my OLD rig (2002-ish era) but I will be sure to post back and if i can get the exact command output saved (from the info you requested) I will be sure to post back here .. all I can remember is that it is an old "SiS graphics card" but for the tech that it is (aka "it's not pretty", but it works... heck it's 17+ years old, and Solus Mate 3.9 + a few updates did just peachy on it) , it did work

again sorry for being rude and not at least "closing" this thread or just reporting back

Xmetalfanx

Update... didn't boot by default with Solus 4.1 Mate but after adding "nomodeset" to the boot line, in grub (think it's grub anyway) the 4.1 Mate ISO booted right to a GUI

vasiliospavlos

Xmetalfanx This solved it for me too!

Xmetalfanx

4.1 installed and updated .... even after installing xorg-driver-video-sis (that is all i did), it is not booting to a GUI ... HOWEVER using the same thing I did on the live media, I just added "nomodeset" and the INSTALLED Solus 4.1 is at GUI now on that machine

Xmetalfanx

output too long to post here but I posted it to termbin https://termbin.com/awz6 .. .not sure how long that link is "valid for"