I'm using a TinyPilot pro via the VGA-Adapter on a Precision R7910 that I have to admin remotely. Unfortunately, the server does several graphic mode changes while transitioning through BIOS, before landing on a text console. The mode changes appear to confuse TinyPilot, with results shown in this screen capture. Any advice?
- 9 replies
Hello @dsjstc ! Welcome to the forum and thank you for reporting this issue. There are two things I would like you to do, if it is not too much asking.
Please upload logs so that I can review them. This is how you would upload them: TinyPilot web interface > System > Logs > Get Shareable URL.
Once the R7910 reaches the text console stage you described, try to SSH into the TinyPilot and restart the streaming service (uStreamer), using the command below. Does that improve anything?
sudo service ustreamer restart
- DIn reply todsjstc⬆:
Hi Dylan! Thank you for the logs. I reviewed them, but I don't see anything suspicious. It doesn't look like software problem, it looks more like a hardware issue. I'm thinking the VGA to HDMI adapter might be defective.
- Would it be possible for you to test the Voyager with another system, using the same VGA to HDMI adapter? If you get the same results, then we could ship you a free replacement for the adapter.
Thanks Diego. The VGA->HDMI adapter works fine on another machine, but consistently sends garbage on this one, even through reboots of the Tinypilot. We're going to get an entirely different adapter and see what happens. Will try to remember to update you!
- Progresswith handling this problem
- D2Dylan @dsjstc
We have tried the tinypilot on a different machine and with a different VGA->HDMI adapter. The problem persists on the Dell R7910 with both adapters, but is not observed on the other machines with either.
My suspicion is that there is something a bit weird about the text mode that the R7910 boots into (it's a modern Debian distro with no GUI). When I can afford a reboot, I'll try to reboot it into one of the console framebuffer modes.
For posterity, when I went to investigate, it turned out that it was in framebuffer mode, at resolution 1920x1200. I believe that the HDMI adapter was reporting this as a valid resolution, and so the kernel was choosing it... but something along the chain couldn't sustain it. I actually struggled to make it work even at 1024x768-72.
In the end, I only need very limited visibility -- this is only for correcting broken network connections. So I am just fine with
GRUB_CMDLINE_LINUX_DEFAULT="nomodeset" GRUB_GFXPAYLOAD_LINUX=keep GRUB_GFXMODE=640x480ReplySolution