Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi I have Slackware ARM -current on a Raspberry Pi 3, up to date.
When I boot up the vga lcd monitor displays fine.
I have two other computers I use the monitor for. If I disconnect from the rpi3 to one of the other computers then back to the rpi3, the monitor is like in sleep.
I ssh to the rpi3 to do things so I don't use the monitor, just wondering if there's anything to get it turn on when reconnecting to the rpi3.
I ssh to the rpi3 to do things so I don't use the monitor, just wondering if there's anything to get it turn on when reconnecting to the rpi3.
I have an Iiyama LCD screen that does exactly the same thing. If it isn't connected to the computer when you boot it there's no way in hell you're ever going to get anything more than a "no signal" error message on the screen. Other screens I can unplug and reconnect them all day long and they work fine. Perhaps your monitor has the same affliction as my Iiyama.
Added this to /boot/config.txt, will see what happens next reboot, will post back.
Does the screen in question work as expected when you're unplugging it and reconnecting it to a system that's not the RPi? Or is this problem only apparent on the RPi?
<edit> Just a thought; the RPi is set to use HDMI by default. You can force it to use HDMI even when there's no screen cable detected. It might be worth trying this in your config.txt file:
Code:
hdmi_force_hotplug=1
hdmi_drive=2
Last edited by Penthux; 04-30-2018 at 02:22 AM.
Reason: what would you use as a reason?
This happens only with reconnecting to the rpi3 and I have those two lines uncommented in config.txt, and this happens only if I disconnect from the rpi3. I've had the monitor connected a few days and have been able to wake it up.
The hdmi dongle to vga has an audio connector I have a pair of speakers connected to using soma to listen to net radio.
So I thought the link in my previous post said "the Pi outputs a relatively weak HDMI signal", I thought maybe the audio connector might have something to do with the hdmi output, I stopped soma, waited a minute and tried to wake up the monitor, didn't work.
As I said, I'll see what happens next reboot with "config_hdmi_boost=4", probably the hdmi output has nothing to do with the audio connector output power wise.
From what I've read, I don't believe it's possible. The DSI interface on the Raspberri Pis appears to be closed architecture, so some users are reporting.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.