You are not logged in.
can not receive the HDMI signal
Option "Enable" "True"When I remove the display-start-script, it is exactly like the case described in the previous line.
This should make it very easy to provide the xrandr output from the graphical session, though. Once w/ and once w/o the HDMI output attached, please.
Offline
The output without the startup script, once with HDMI and one without HDMI?
I will need a few hours to go back home and hook up my display though
Offline
Yes. I want to see what xrandr actually reports in either condition.
If DP2-3 isn't listed as disconnected, the misbehaving script isn't surprising.
Offline
Sorry, I can't do this right now -- somehow my keyboard/mouse drivers are not working. Both the external (through USB) ones and the laptop ones.
On the bright side, I can follow Arch's official guide and hand you the log with zero modifications to the system (if the problem persists), if that's the output that you'd like.
EDIT I mean this link: https://wiki.archlinux.org/title/Installation_guide ; can I confirm that this supports dual-boot? I'm not ready to ditch Windows yet
Last edited by crimsonpython24 (2021-05-11 10:26:19)
Offline
https://wiki.archlinux.org/title/Dual_boot_with_Windows
I'd like to see the output of xrandr, not you re-installing the system. The point of the latter is so that you have an idea about the system in front of you - it will not impact the immediate situation, but hopefully your understanding of it.
Offline
I don't seem to have a choice... as mentioned, all my input devices are not detected (driver updates?) If there's a way to get around the problem, I'd be really grateful
Offline
Things don't just break out of nowhere and I doubt that it's a "driver update"…
It might generally benefit you to start from scratch so that these things don't happen because you're not doing random things to the system.
The typical cause for failing ushid btw. is that you updated the kernel but forgot to mount the /boot partition (or actually boot from the root partition) and now the kernel modules don't meet the running kernel.
You can compare "uname -a" and "pacman -Qs linux", but in any event that's vastly off topic in this thread.
Offline
But the problem is that, for now, I can't type... whether it's booting into the vertical terminal or Arch system, keyboard won't respond. So it the mouse/trackpad
Offline
What ist the "vertical terminal"…?
The typical cause for failing ushid btw. is that you updated the kernel but forgot to mount the /boot partition (or actually boot from the root partition) and now the kernel modules don't meet the running kernel.
If that may fit your situation you'll have to fix your update offline, ie. from eg. the live installation.
Essentially like https://wiki.archlinux.org/title/Pacman … an_upgrade but don't copy and paste that. You'll still want to look at the boot partition and the kernel versions.
You may want to postpone arch and start w/ a distro that's more tailored towards beginners and shovels a preconfigured system onto your disk, eg. ubuntu.
Then get familiar with the basic concepts of the operating system before you approach arch again.
Offline
I meant the console that pops up on ctrl+alt+f2, whatever that's called.
The point is that I have no problem using Debian-based distros, but I just don't like PPA -- more like a personal preference thing, but I feel like Arch's package manager is much more convenient to use.
Offline