Darkmatter66_ has quit [Ping timeout: 256 seconds]
Darkmatter66 has joined #linux-amlogic
<Darkmatter66>
narmstrong, I just tried another screen and the crash still happens
<Darkmatter66>
i also tried a different HDMI cable just in case and it didn't change help
<Darkmatter66>
The strange thing is that when i went and connected the box back to my first screen the problem went away
<Darkmatter66>
I had to reboot the box to get the crash back
<Darkmatter66>
after a few tries it turns out that if i turn the box on while the screen is powered off (not from remote but from main power) then after the box has booted I turn on the screen, then the crash doesn't happen at all
<Darkmatter66>
even after power cycling the screen from the remote like before
<Darkmatter66>
and I have to reboot the box while the screen is connected to power to get the crash again
<Darkmatter66>
all I get instead of the crash is a spam of this line "kms: can't enable cloning when we probably wanted to."
<Darkmatter66>
and also the screen doesn't detect the resolution right, it sees the resolution as "576p@50Hz"
chewitt has joined #linux-amlogic
<Darkmatter66>
ahh, and If i start the graphical interface "systemctl start gdm" then the tv loses signal again
sputnik__ has quit [Remote host closed the connection]
random_yanek has quit [Ping timeout: 250 seconds]
random_yanek has joined #linux-amlogic
vagrantc has joined #linux-amlogic
Darkmatter66_ has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 250 seconds]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Read error: Connection reset by peer]