You are not logged in.
Pages: 1
Xorg doesn't boot and displays no errors.
log file:
https://pastebin.com/rpBcNZnH
I'm not sure what caused this, it could be an upgrade, I tried few things in tty, like pacman -Syu or reinstall xorg with pacman -S xorg. Nothing worked. This is extremely annoying because after I run startx, I can't do anything, even change the tty.
Last edited by Careo (2024-04-06 15:10:58)
Offline
Currently I'm getting error from XKB: Failed to compile keymap
Offline
[ 257.545] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 257.545] (II) Platform probe for /sys/devices/pci0000:00/0000:00:03.1/0000:09:00.0/drm/card1
[ 257.546] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 13 paused 0
[ 257.546] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 257.546] (II) Platform probe for /sys/devices/platform/simple-framebuffer.0/drm/card0
[ 257.546] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 14 paused 0
[ 257.551] (--) PCI:*(9@0:0:0) 10de:1f06:1458:3ff1 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[ 521.900] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
You have 2 drm devices but only 1 card (nvidia) .
This smells like a conflict between the simpledrm device and the nvidia card .
try adding nvidia-drm.modeset=1 as paramter to your kernel command line .
Last edited by Lone_Wolf (2024-04-06 11:24:06)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I did the nvidia thing, confirmed using cat and fixed XKB fail, but now I'm getting different error.
xinit: Unable to run program "xterm": No such file or directory.
I'm puzzled.
xterm problem fixed.
Last edited by Careo (2024-04-06 12:28:51)
Offline
Xorg doesn't start, but log says no errors, very weird. I see the error when running xinit, not startx which freezes my PC
Offline
Currently xorg freezes and outputs no log, I don't know what I can do at this point, please help.
Offline
append systemd.unit=multi-user.target to your boot command line (how to do that depends on your bootloader) .
This will ensure you boot to a console login and not start any graphical stuff.
login as root, run
journalctl -b | curl -F 'file=@-' 0x0.st
It will output an url, post that url.
Also post your user ~/.xinitrc file.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
Before I do that let me quickly add that I'm able to run startx with sudo, but that's not practical solution.
Offline
journalctl:
0x0.st/XiMz.txt
Last edited by Careo (2024-04-06 12:52:10)
Offline
Apr 06 14:35:55 archlinux kernel: Command line: initrd=\amd-ucode.img initrd=\initramfs-linux.img root=PARTUUID=6684c6a6-d1bb-429a-bfd2-94a7806d9505 zswap.enabled=0 rw rootfstype=ext4
I asked you to add stuff to your kernel command line twice now, but you haven't done that.
Maybe i wasn't clear enough that you need to change the actually used kernel boot command, not a file under /etc/modprobe.d .
Apr 06 14:40:11 carch kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
Apr 06 14:40:11 carch kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
Apr 06 14:40:36 carch kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
Confirms the conflict between the simpledrm and the nvidia videocard is causing the problems.
What bootloader are you using ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
You are right, I edited the file instead.
Last edited by Careo (2024-04-06 13:12:16)
Offline
the journal shows nvidia TRIES to use modesetting and FAILS.
Apart from replacing the nvidia card by something else or switching to an old kernel from before arch enabled SimpleDRM, the only known way to fix this is :
add nvidia-drm.modeset=1 to the command that boots your system.
The journal lines I posted in #12 clearly show you have added it somewhere else.
Ok, new journal please.
Last edited by Lone_Wolf (2024-04-06 13:13:07)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I mean that I edited the wrong file under /etc. I'm currently trying to figure out how edit the correct file.
Offline
Sorry, I'm quite lost. I use systemd-boot and I'm trying to follow wikis instructions but I'm failing to do so. It says to hold space while booting to open menu, but I can't seem to do that.
Offline
Okay, I managed to that, but the problem still occurs.
journal:
http://0x0.st/XiMp.txt
Offline
append systemd.unit=multi-user.target to your boot command line (how to do that depends on your bootloader) .
This will ensure you boot to a console login and not start any graphical stuff.login as root, run
journalctl -b | curl -F 'file=@-' 0x0.st
It will output an url, post that url.
Also post your user ~/.xinitrc file.
Here is both xinitrc and xprofile:
https://pastebin.com/kHMMgMAx
Offline
When I try to shutdown my PC after using startx it says: Waiting for X server to accept connections.
Offline
After 8 hours I finally solved it! It had nothing to do with nvidia, xorg, xinit or anything of this nature. It was actually caused by linking /usr/bin/sh to zsh!
I found the answer here:
https://bbs.archlinux.org/viewtopic.php?id=257503
Offline
Pages: 1