New to Linux in general, met by a black screen showing only my cursor. I tried troubleshooting but to no avail, by using commands on the terminal I can access using cmd alt f3. Appreciate any help! 
1 Like
I am new into arch linux and i can’t help you more. It seems like every compositor or server are not working and there is more error than one. And do you have hibernate or sleep your laptop?
Have you this issue on the live usb when processing the installation of CachyOs?
have you tried to use ubuntu or debian before? (like ZorinOS)
you can look the bios and change may this option
"CONFIG_ACPI is enabled, Intel AX210’ driver will try to call the DSM function in ACPI table.
Thus the error message appears because of no ACPI table in UEFI."
Intel AX210 "failed to evaluate _DSM" messages - Intel Community
Please try an X11 session. It seems that your GPU has problems to use Wayland.
2 Likes
The usb works fine, this is my first time running any OS that isn’t windows
Also it’s an AMD cpu/gpu I doubt an Intel related issue would help a lot
Thanks though!
1 Like
Do I do that with a command in that terminal or do I reinstall?
If you boot into your computer, you get into the displaymanager (where your username is and then you put your password).
On the bottom right you can select between Plasma X11 Session and Plsama Wayland Session. Select there Plasma X11 Session.
When I boot I don’t get a login screen, it’s just black with the Linux cursor but if I spam some random string of f1 f2 fn alt cntrl it gives me the standard cursor and from there cmd alt f3 pops up the terminal login prompt
Any ideas?
Sadly not, no. Our team member with an equal GPU has tested the ISO on his machine, USB flashed via Etcher and also tested with ventoy - both worked fine.
Did you try in the boot menu the “nomodeset” option?
In all honesty I don’t even know what that is, how do I try ?
When you boot the ISO, you have several options.
- CachyOS UEFI Default
- CachyOS UEFI Default NVIDIA
- CachyOS UEFI Fallback (nomodeset)
There you choose option 3.
Boot the iso? So this is only for USB?
You wrote above, that you have issues booting into the ISO, so i guess you want to boot into the ISO, so that you can install the system
No no I can boot fine from the USB, sorry for the confusion.
I already ran the installer from it, set cachyos to replace windows and all, but when I boot my pc (NO USB) it just gives me a black screen with a cursor
Then you should be able to get into the “tty” (terminal console) with follwoing:
CTRL + ALT + F3
Then you can login with your selected username and passwd.
Then you run:
sudo cachyos-bugreport.sh and give us the link.
I’ll gladly do it again but you can find that paste in my initial post
Sorry, ive mixed it up with a different post.
Please try to login into a X11 Session, it seems that your GPU/CPU does not handle this correctly the wayland session:
[ 132.595170] kscreenlocker_g[3017]: segfault at 0 ip 0000000000000000 sp 00007fff2f82dfd8 error 14 in kscreenlocker_greet[5c3df8fff000+d000] likely on CPU 2 (core 2, socket 0)
[ 132.595200] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 132.905368] kwin_wayland[2984]: segfault at 0 ip 0000000000000000 sp 00007fff01fb0938 error 14 in kwin_wayland[651288e42000+37000] likely on CPU 3 (core 3, socket 0)
[ 132.905393] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 136.364025] kscreenlocker_g[3289]: segfault at 0 ip 0000000000000000 sp 00007ffed4c65c78 error 14 in kscreenlocker_greet[5babda0ac000+d000] likely on CPU 2 (core 2, socket 0)
[ 136.364052] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 136.692430] kwin_wayland[3255]: segfault at 0 ip 0000000000000000 sp 00007ffe37c1b898 error 14 in kwin_wayland[556471575000+37000] likely on CPU 2 (core 2, socket 0)
[ 136.692458] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 140.101243] kscreenlocker_g[3560]: segfault at 0 ip 0000000000000000 sp 00007ffd73e82a78 error 14 in kscreenlocker_greet[63dd68d8a000+d000] likely on CPU 0 (core 0, socket 0)
[ 140.101272] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 140.433132] kwin_wayland[3522]: segfault at 0 ip 0000000000000000 sp 00007ffe37524b18 error 14 in kwin_wayland[5df3c7be7000+37000] likely on CPU 3 (core 3, socket 0)
[ 140.433161] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 143.950854] kscreenlocker_g[3834]: segfault at 0 ip 0000000000000000 sp 00007ffe5a28cff8 error 14 in kscreenlocker_greet[62a9fe535000+d000] likely on CPU 0 (core 0, socket 0)
[ 143.950885] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 144.291502] kwin_wayland[3795]: segfault at 0 ip 0000000000000000 sp 00007ffd407efd18 error 14 in kwin_wayland[5f9a6efc0000+37000] likely on CPU 3 (core 3, socket 0)
[ 144.291528] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 146.540447] QQuickPixmapRea[4148]: segfault at 0 ip 0000000000000000 sp 00007fbe093ff5b8 error 14 in sddm-greeter-qt6[55e42f25f000+c000] likely on CPU 3 (core 3, socket 0)
[ 146.540468] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Generally those indicates either that there is a hardware defect or that this GPU is not supported with wayland.
In SDDM on the right bottom, there you can switch to “X11 Plasma Session” and then try to put in your password.
Brother I do not reach the SDDM/login screen, the whole screen is black and all I can see is my cursor. Is there any way to boot x11 from the terminal?
startplasma-x11
Says
$DISPLAY is not set or cannot connect to the X server