Hey guys! Does anyone have any idea why my second monitor connected through thunderbolt is suddenly not working? The monitor displays a "No signal" message, despite the cable being connected. Nvidia drivers are up-to-date, used to work until yesterday. I disconnected the cable briefly and now that I have connected it again it will not work.
#Thunderbolt connected monitor suddenly not working
43 messages · Page 1 of 1 (latest)
Anything on dmesg when plugging/unplugging the cable?
what should I be looking for exactly?
oh ok i see
nope no output
like nothing new
last thing in there is a wifi related warning
besides that nothing
think this could be a hardware related problem?
Yeah nothing on dmesg is likely hardware related. Probably the cable, based on my own past experience, some of those are shit.
oof
If you can, try the cable somewhere else
Will do, I think I have some other cables in a drawer somewhere too, I'll try those too.
Man I hate thunderbolt
The laptop's solid, the monitor as well, I've had some problems in the past on other distros too and those had a mostly software related nature, albeit that should not be outruled.
I'll wait till my father gets home so I can try to see if his MacBook connects properly to the monitor
Say the cable is broken, should I buy a new one or look for an hdmi to bluetooth adapter?
It would get rid of many hassles and bluetooth seems to be working strangely well on arch for a linux distro.
hdmi to bluetooth? u wot
Apparently there's devices that you can connect through hdmi that transform your monitor into a bluetooth connectable one
fair
Also the bandwith of bluetooth is nowhere near close that of HDMI, I wonder how that works 
no idea
Visit https://www.squarespace.com/LTT and use offer code LTT for 10% off
Save 10% and Free Worldwide Shipping at Ridge Wallet by using offer code LINUS at https://www.ridge.com/LINUS
Can a sketchy company make a good product? We tried out PeakDo's wireless HDMI transmitter and receiver and the results might surprise you.
Buy Seasonic X-series...
Yeah that's not bluetooth it's some proprietary mm-wave thing haha but seems pretty cool
oh
Ok so tested it out on a macbook and it worked
I am quite sure that it's not the laptop that's causing the problem, like the hardware itself
Driver problem, hyprland problem, something else entirely?
*bump*
xrandr --auto ``` outputs something a tad bit weird
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 7 (RRSetScreenSize)
Serial number of failed request: 22
Current serial number in output stream: 23```
the second just restarted my whole display manager XD
apparently some nvidia driver problems
trying to resolve them
#1119568798744313916
?