I have managed to install MicroOS on Thinkpad x13s, but it boots into a black screen. I can see the start, but I am not sure how far it gets as it takes only a split second before the screen goes black. I cannot get to tty either, which makes me think that the issue is with some graphic module or settings, but I have no idea.
I would appreciate any suggestions on this matter.
Thank you.
MicroOS is always going to boot into a black screen, as it doesn’t provide a desktop environment.
Kalpa currently has a glitch, that I haven’t been able to fix in the installer yet.
Do ctrl-alt-Fkey pick any of the function keys, to get to a tty. Log in with your regular username and password, then run:
sudo systemctl enable --now --force sddm.service
That should disable display-manager-legacy.service and get sddm up and running.
For future reference, this sort of thing is documented at https://kalpadesktop.org
It shouldn’t boot to a completely black screen, you should still get a login prompt.
I agree that the OS should boot into a tty / loging prompt and not a completely black screen. As I have mentioned, I am unable to use ctrl-alt-Fkey to get a tty.
The installation is just fine and thus I suspect that it has something to do with the graphic drivers in the installed OS? Reinstalation as only a basic system, i.e. into text mode, makes no difference.
Not sure if it is helpful, but I think that the last visible line is *Mounted* Kernel Configuration File System.
If you can’t get to a tty via the key combo, you likely need to add nomodeset to your kernel cmdline, to put yourself in basic graphics mode.
I don’t have a link handy to point you at, but searching something like “add nomodeset grub2 during boot” into your search engine of choice should get you there.
Thank you for the suggestion. I have added nomodesetby editing kernel cmdline before boot, but it made no difference. I will try it once again tonight, just in case I didn’t do it properly.
I wonder what is the difference to MicroOS installer or to normal Tumbleweed, both of which are just fine. I thought that MicorOS is based on Tumbleweed and therefore it would share the basic, such as kernel and all the modules/drivers.
It does, same kernel and whatnot as Tumbleweed, so I’m not real certain what the issue is here, the current “stable” releases use the same installer and everything. (MicroOS and Tumbleweed are still using the YaST installer on the release ISOs)
Offhand, does everything work in Tumbleweed?
Wait. Thinkpad x13s? That’s a Snapdragon X based ARM machine, yes?
Tumbleweed works without any issues, I have been using it now for years. The latest versions run from live usb without problems.
Yes, Thinkpad x13s is ARM Snapdragon with integrated Qualcomm Adreno 690 GPU.
Ah. I have no idea if Kalpa works on ARM reliably or not. I don’t have any hardware to test against, and really have no way to support it.
That doesn’t mean it won’t work, I still publish the aarch64 images just in hopes that somebody will adopt them, but I’m basically of no help when it comes to troubleshooting those issues.
It’s not a matter of not wanting to help, just that I literally can’t.
I am fully aware that Kalpa is not quite ready and I did not expect it to work without some issues. I thought that it may be good and useful to try it and report any issues, and I appreciate your help.
I have mentioned early that I reinstalled MicroOS as only a basic system in text mode, but it did not make difference. Perhaps I should mark this enquiry as generic MircoOS on ARM.
I am sure that I am not the only user of Snapdragon based computer and I am confident that ARM computers would be widely used by end users in coming years.
No, I appreciate the heads up, there’s just not a lot I (personally) can do about it at the moment. I would appreciate filing a bug report at Log in to Bugzilla against the installation component, just so it doesn’t get lost.
Also might not be the least useful thing in the world to drop by https://matrix.to/#/#arm:opensuse.org and asking there, if you’re so inclined?