average linux experience
can play videos on tv with cool interface
based
can’t just turn the TV on though because if you start X without an HDMI client it won’t ever start the display and you have to reboot to get the interface up
cringe
average linux experience
@icedquinn Wait what? I hotplug HDMI displays with X almost every day.
re: average linux experience
That said most sane window managers / desktop environments are capable of fixing that in their own broken ways.
re: average linux experience
@icedquinn Have you tried turning it on with xrandr?
For reference, this is the machine that doubles as my "TV" set top box and general purpose desktop (the "TV" is a projector pointed into the living room from my workshop.) On my machines with integrated graphics cards hotplugging works without anything special in Xorg.conf.
Looking at it now I'm actually not sure why this works.
```~ $ cat /etc/xorg.conf
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib64/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "SWcursor" # [<bool>]
#Option "kmsdev" # <str>
#Option "ShadowFB" # [<bool>]
#Option "AccelMethod" # <str>
#Option "PageFlip" # [<bool>]
#Option "ZaphodHeads" # <str>
#Option "DoubleShadow" # [<bool>]
Identifier "Card0"
# Driver "modesetting"
#Driver "radeon"
BusID "PCI:7:0:0"
EndSection
#swiley added
Section "dri"
Mode 0666
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "ServerFlags"
Option "DontZap" "false"
EndSection
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
~ $
```
re: average linux experience
🚨 🚨
re: average linux experience
you can also export a working config as an executable shell script, and run it on login or w/e
re: average linux experience
of course on mac and windows i just plug them in and it just works(tm)
re: average linux experience
@icedquinn@blob.cat @swiley@qoto.org I have the same category of bs on the pinephone. usb c display hotplug will fuck up X like no other (i thought this was wayland country anyway??)
re: average linux experience
re: average linux experience
@icedquinn@blob.cat @swiley@qoto.org because devices power down and stuff. there's hdmi dongles specifically for your problem.
re: average linux experience
@purple @icedquinn You definitely don't need dongles. You might actually be able to fix this with udevd now that I think about it. I think that's what this guy is doing: https://unix.stackexchange.com/questions/281872/udev-monitor-hotplug-rule-not-running
re: average linux experience
@icedquinn @purple You could run a deamon in the background to do it. None of the OSes I use (besides guix which I haven't tried this with) run *anything* in the background after bootup besides agetty.
re: average linux experience
@icedquinn @purple But you really don't need to restart your display server to enable/disable monitors. It's something like `xrandr --output HDMI-1 --auto` to turn it on IIRC.
re: average linux experience
@icedquinn @purple If OSX works for you it's nice that you can throw money at the problem. OSX has some serious issues that make it useless as far as I'm concerned.
re: average linux experience
@icedquinn @purple The maintainers of your distro probably. You could maybe write a udev rule that works for you and suggest that and see what they say.
IMO: xrandr is pretty user friendly (except that no one tells you about it) and there are worse things to be upset about.
re: average linux experience
@icedquinn @purple That's my main complaint with wayland. It's better than X11 if all your graphics drivers are set up correctly. So if the companies that are worst about screwing their users over screw you over then your computer is basically unusable outside of the kernel VTEs or X11.
re: average linux experience
@purple @icedquinn My solution is a root menu entry to turn off the phone's display and turn on the external one using xrandr (X11 hotplugging works fine, but X gets really slow on the phone with two screens for whatever reason.) My power management scripts undo this if you lock the phone (just in case you yank it out of the dock without manually undoing this.)
IME: X11 is much faster on the pinephone but maybe some of the latest driver updates have changed that.
re: average linux experience
also my desktop (much newer computer) worked with HDMI but since i changed to a displayport monitor X will 'forget' there is a monitor there and won't use it if its turned off too long. have to restart X while the monitor is alive to fix.
but that's the cost of freedom i guess.