When updating, the PC freezes. I had to turn it off hard from the button. I'm trying to boot up and I get this screenshot. Further loading does not occur, switching to another tty does not work.

I booted from Live, mounted the root directory, and fell into the chroot. I tried to execute the command

sudo eopkg check | grep Broken | awk '{print $4}' | xargs -r sudo eopkg it --reinstall

But that didn't help either.

Is there any way to fix it from under Live?

    AlphaElwedritsch (gnome uses the GDM display manager)

    @alexanderzhirov make sure you do this to a tee: https://help.getsol.us/docs/user/troubleshooting/boot-rescue#chrooting-to-your-solus-system It takes me about three times to get it right. Sometimes you think you are in but not in. Maybe its just me. Anyway my 2 cents is did you do the two steps before thecheck one?
    (sudo eopkg rebuild-db
    sudo eopkg up)

    ps--and the steps after that: the usysconf and boot update ones

        If all those required steps produced no output then the assumption is that they worked.
        I see people successfully rolling back but I don't think you can do that in chroot.
        Hang in there. Hope others chime in.

          alexanderzhirov do all the steps in chroot doc. good luck
          edit: you are close I hope you can get all of the way

            just got home from work. if you have the tty and did those 5 commands in sequence..and still nothing then official protocol was followed and it's hard for me to guess.

            Putting "inappropriate ioctl" in a search engine and scanning is truly gut-wrenching reading and indicates some kind of fubar somewhere. At the end of my brain but if I think of anything I'll get back

            Hang in there. Meanwhile I hope someone will ask you for terminal output of t-shooting commands so you can get in the right direction.

            alexanderzhirov Can you try it with eopkg check -N instead of eopkg check in that command? I've sometimes seen eopkg colour output interfere with such operations. Not sure if it's the case here though.
            (maybe also add the -N switch to the eopkg it command at the end if it still doesn't succeed).