My screen is black

WetGeek

[deleted] I enter my username and my password, and I get a blinking underscore

Then it sounds like a hardware or driver problem. We need to bring in @Girtablulu to help with that, if he has time. He's part of the core team, and understands error logs much better than I do. He'll know which ones he needs to see in order to help.

You may be getting logged in okay, but the problem might be with your video card, or its driver, or a mismatch between the two, because that should be the next step after logging in. It would also explain why you've had to use a text-only TTY in the first place.

Girtablulu

chroot into your system as per https://getsol.us/articles/troubleshooting/boot-rescue/en/, should be enough just to mount your partition where your home folder is

and remove that export path

WetGeek

Girtablulu chroot into your system

Thanks! I've never had a reason to use chroot for anything, although I know what it does. It didn't occur to me that it would be what was needed for this. I'm glad you're here.

[deleted]

Girtablulu I need a USB with the Live ISO, right?

[deleted]

Girtablulu I've got mount point does not exist for the three mount commands, and chroot: cannot change root directory to '/target': No such file or directory for the last one.

Girtablulu

[deleted] yes or CD

WetGeek

[deleted] I need a USB with the Live ISO, right?

I'm pretty sure Girtablulu meant a DVD. I don't think any CD would work. A high-density CD will hold 700 MB, and if I remember right, a Solus installation requires almost 2 GB.

Lots of computers these days don't even have a DVD player, because USB drives are so popular and cheap. If you haven't burned an ISO to a DVD drive, a good utility to do that is Etcher, and it's in the Solus repository.

If I'm telling you what you already know, my apologies. That's better than not telling you enough.

[deleted]

WetGeek Thanks for telling me things I may not know.

Infamous711

[deleted]

Have you followed the "Mounting your system" section of https://getsol.us/articles/troubleshooting/boot-rescue/en/ ? At first you have to mount your system by following along the steps given there and then do chroot.

My another suggestion is reading through that whole page thoroughly 😉

[deleted]

Infamous711 Thanks. I should have read the whole page.
Now I've mount everything but the first thing. I get this: unknow filesystem type 'LVM2_member'.

Infamous711

[deleted] export PATH=$PATH:~/.zig/zig-090

I don't know if I am right in this but I think you should export and update the PATH variable in .bashrc (if you use bash, which is the default in solus) or .zshrc (if you use zsh). I always use this method and it always works for me and nothing broke because of this. Also I update my path variable like export PATH=/my/custom/dir:$PATH Although I don't know if I am using the correct way of doing this or not. But this works so maybe I am using the correct method 🤷‍♂️

kuki

Your user and pass have to work in tty, have you another characters on your name or pass, I think default keyboard in tty is US-ENG , you have to find maybe it’s in another place key for your pass.
I had a problem with that.

[deleted]

kuki Some keys are different, but the ones that I use for user and pass have not changed.

Infamous711

[deleted]

Do you have lvm enabled? (You can check with sudo lvscan)

If you have then you have to mount the system with mount /dev/SolusSystem/Root /target (My lvm root partition is /dev/SolusSystem/Root, yours maybe different. So check with lsblk and find your root partition)

If you are unsure, just post your lsblk output here. We will try to help.

[deleted]

Infamous711 It worked! My LVM root partition was the same as yours.
Finally I'm editing the problematic file.

[deleted]

@nolan, @pomon, @WetGeek, @Girtablulu, @Infamous711, @kuki THANK YOU VERY MUCH!

Infamous711

[deleted]

That's great to hear! Do remember that if you want to update or modify the PATH variable, update it like this export PATH=/my/custom/path:$PATH in the .bashrc file. Then just as usual source ~/.bashrc and everything should work as usual. Hope this helps.

[deleted]

Infamous711 Thanks, I'll remember that.

« Previous Page