No internet connection
  1. Home
  2. Technical Support

NO SIGNAL but keyboard and mouse are working

By @bakabonpapa
    2021-06-22 23:53:18.415Z

    Hi Michael.

    I purchased TinyPilot voyager and set it up for a laptop recently.
    It worked fine after my first setup.

    But once I detached the device from the laptop and did attach to the laptop, TinyPilot started to fail to catch the screen (NO SIGNAL message in https://tinypilot page).
    The keyboard input and mouse movement are OK through the page though.
    I uploaded the log already.
    Can you check it and tell me what is happening, and what should i do to solve it?

    https://logs.tinypilotkvm.com/Aqp3IuVP

    Thank you in advance.
    bakabonpapa

    • 24 replies

    There are 24 replies. Estimated reading time: 27 minutes

    1. B
      @bakabonpapa
        2021-06-23 00:04:39.861Z

        Addition.
        I plugined another monitor to the laptop, and could display the screen on the monitor.
        Maybe video output from the VGA is fine.

        1. B@bakabonpapa
            2021-06-23 08:05:52.522Z

            i changed to different pc attached with TinyPilot.
            Then, I connected TinyPilot to the original pc that had the screen problem.
            And now, the problem was solved and TinyPilot started to show the screen.
            Why?

            1. Hmm, that's difficult.

              It looks like the streaming service was failing to start:

              May 20 17:51:14 tinypilot ustreamer[576]: ================================================================================
              May 20 17:51:14 tinypilot ustreamer[576]: -- INFO  [170.184    stream] -- Device fd=9 opened
              May 20 17:51:14 tinypilot ustreamer[576]: -- INFO  [170.184    stream] -- Using input channel: 0
              May 20 17:51:14 tinypilot ustreamer[576]: -- INFO  [170.191    stream] -- Got new DV timings: resolution=1920x1080, pixclk=148500000
              May 20 17:51:14 tinypilot ustreamer[576]: -- INFO  [170.211    stream] -- Using resolution: 1920x1080
              May 20 17:51:14 tinypilot ustreamer[576]: -- INFO  [170.211    stream] -- Using pixelformat: UYVY
              May 20 17:51:14 tinypilot ustreamer[576]: -- INFO  [170.211    stream] -- Querying HW FPS changing is not supported
              May 20 17:51:14 tinypilot ustreamer[576]: -- INFO  [170.211    stream] -- Using IO method: MMAP
              May 20 17:51:14 tinypilot ustreamer[576]: -- INFO  [170.236    stream] -- Requested 5 device buffers, got 5
              May 20 17:51:14 tinypilot ustreamer[576]: -- ERROR [170.237    stream] -- Unable to start capturing: Invalid argument
              

              Did you change resolution on the target machine? Would you mind sharing the logs now that it's working?

              1. B@bakabonpapa
                  2021-06-24 03:40:04.115Z

                  Hi Michael.
                  Thank you for your comment.

                  Did you change resolution on the target machine?

                  What I did, I wrote it concicely below

                  1, After first arrival of TinyPilot, I setup it and it worked fine with Laptop A (1366x768).
                  2, I detached TinyPilot from A, and shutdowned the device and A.
                  3, I reattached A with the device, but the browserscreen showed "NO SIGNAL" as in the first post (collected first log here).
                  4, I detached the device again, and attached it to another Laptop B (1920x1080), and it worked fine.
                  5, After 4, I plugged the device into A and it recoverd the screen (Now)

                  Would you mind sharing the logs now that it's working?

                  I am now in above No.5, and collected the log again.
                  https://logs.tinypilotkvm.com/ym97PX4N

                  I like to know what happened for future failure.

                  By the way, your product is very nice.

                  Thank you.
                  Bakabonpapa

                  1. Did you restart the TinyPilot between machines? It might have been that the second machine's resolution somehow affected state and caused it to fail capturing video from the first machine.

                    In the failing logs, we see TinyPilot trying to capture at 1920x1080:

                    May 20 17:51:09 tinypilot ustreamer[576]: -- INFO  [164.853    stream] -- Device fd=9 opened
                    May 20 17:51:09 tinypilot ustreamer[576]: -- INFO  [164.853    stream] -- Using input channel: 0
                    May 20 17:51:09 tinypilot ustreamer[576]: -- INFO  [164.860    stream] -- Got new DV timings: resolution=1920x1080, pixclk=148500000
                    May 20 17:51:09 tinypilot ustreamer[576]: -- INFO  [164.880    stream] -- Using resolution: 1920x1080
                    May 20 17:51:09 tinypilot ustreamer[576]: -- INFO  [164.880    stream] -- Using pixelformat: UYVY
                    May 20 17:51:09 tinypilot ustreamer[576]: -- INFO  [164.880    stream] -- Querying HW FPS changing is not supported
                    May 20 17:51:09 tinypilot ustreamer[576]: -- INFO  [164.880    stream] -- Using IO method: MMAP
                    May 20 17:51:09 tinypilot ustreamer[576]: -- INFO  [164.903    stream] -- Requested 5 device buffers, got 5
                    May 20 17:51:09 tinypilot ustreamer[576]: -- ERROR [164.904    stream] -- Unable to start capturing: Invalid argument
                    

                    In the successful logs, we see it capturing at 1366x768:

                    Jun 23 21:32:05 tinypilot ustreamer[1810]: -- INFO  [69835.686    stream] -- Device fd=9 opened
                    Jun 23 21:32:05 tinypilot ustreamer[1810]: -- INFO  [69835.686    stream] -- Using input channel: 0
                    Jun 23 21:32:05 tinypilot ustreamer[1810]: -- INFO  [69835.693    stream] -- Got new DV timings: resolution=1360x768, pixclk=85800960
                    Jun 23 21:32:05 tinypilot ustreamer[1810]: -- INFO  [69835.714    stream] -- Using resolution: 1360x768
                    Jun 23 21:32:05 tinypilot ustreamer[1810]: -- INFO  [69835.714    stream] -- Using pixelformat: UYVY
                    Jun 23 21:32:05 tinypilot ustreamer[1810]: -- INFO  [69835.714    stream] -- Querying HW FPS changing is not supported
                    Jun 23 21:32:05 tinypilot ustreamer[1810]: -- INFO  [69835.715    stream] -- Using IO method: MMAP
                    Jun 23 21:32:05 tinypilot ustreamer[1810]: -- INFO  [69835.723    stream] -- Requested 5 device buffers, got 5
                    Jun 23 21:32:05 tinypilot ustreamer[1810]: -- INFO  [69835.728    stream] -- Capturing started
                    

                    I'm wondering if going from device B back to device A somehow breaks TinyPilot's video capture because it's "remembering" settings from the old device. A reboot of the TinyPilot should clear any persistent state.

                    1. B@bakabonpapa
                        2021-06-25 01:55:56.484Z

                        After a certain amount of time of working fine from the last message,
                        TinyPilot started to show "NO SIGNAL" again.
                        I failed to tell you but the Laptop A is jump machine for Citrix virtual desktop.
                        "NO SIGNAL" screen does not change between before and after connecting to the virtual desktop.

                        Debug logs right now.
                        https://logs.tinypilotkvm.com/qqhH4F6n

                        Did you restart the TinyPilot between machines?

                        I think so, I did several restarts or shutdown while trying to recover the screen.

                        It might have been that the second machine's resolution somehow affected state and caused it to fail capturing video from the first machine.

                        In the failing logs, we see TinyPilot trying to capture at 1920x1080:

                        Jun 23 21:32:05 tinypilot ustreamer[1810]: -- INFO [69835.686 stream] -- Device fd=9
                        I'm wondering if going from device B back to device A somehow breaks TinyPilot's video capture because it's "remembering" settings from the old device. A reboot of the TinyPilot should clear any persistent state.

                        Can you tell me the steps to recover the screen when I fall into such state and having "NO SIGNAL" screen?
                        Is Reboot enough?
                        But mere rebooting is not working right now.

                        Thank you.

                        1. It seems to fail when the target machine outputs a resolution of 1920x1080, but it succeeds when the target machine uses 1366x768.

                          Is it possible to change the resolution on the target machine to always output 1366x768?

                          1. B@bakabonpapa
                              2021-06-30 08:08:01.866Z

                              Is it possible to change the resolution on the target machine to always output 1366x768?

                              Yes, possible.
                              But how am I suppose to change configurations when switching between different PCs with different resolutions?

                              1. Is this a problem on multiple machines? I thought that there was just one machine that failed to get a display consistently.

                                1. B@bakabonpapa
                                    2021-07-01 09:12:14.426Z

                                    Is this a problem on multiple machines?
                                    I thought that there was just one machine that failed to get a display consistently.

                                    No. As you lined, this failure has been happening in just one machine (Laptop A).
                                    As for Laptop B, TinyPilot seems to be working fine functioning after changing resolutions.
                                    For Laptop A, the desktop is administered by AD and I cannot change the resolutions of the screen.

                                    But, at the same time, i wanted to know if there is a "Official" steps for switching the device between PCs with different resolutions like this time.
                                    Or is TinyPilot supposed to work "automatically" when switching?

                                    1. Michael Lynch @michael2021-07-02 21:46:38.105Z2022-06-01 16:09:36.458Z

                                      It should just work automatically, so I'm surprised it's getting stuck when switching machines.

                                      One other thing you can try is to change the EDID. Those are the settings the TinyPilot uses to negotiate video settings with the target machine. To try an alternate EDID, run these commands:

                                      EDID="/home/ustreamer/edids/tc358743-edid.hex"
                                      
                                      # Back up original EDID
                                      cp --no-clobber "${EDID}" ~/tc358743-edid.hex.bak
                                      
                                      # Set a new EDID
                                      echo -ne "" | sudo tee "${EDID}" && \
                                        echo '00ffffffffffff0052628888008888882d1e0103' | sudo tee -a "${EDID}" && \
                                        echo '800000780aee91a3544c99260f50542540000100' | sudo tee -a "${EDID}" && \
                                        echo '0100010001000100010001010101d51b00505000' | sudo tee -a "${EDID}" && \
                                        echo '19400820b80080001000001eec2c80a070381a40' | sudo tee -a "${EDID}" && \
                                        echo '3020350040442100001e000000fc00546f736869' | sudo tee -a "${EDID}" && \
                                        echo '62612d4832430a20000000fd00323d0f2e0f0000' | sudo tee -a "${EDID}" && \
                                        echo '000000000000012a02030400de0d20a030581220' | sudo tee -a "${EDID}" && \
                                        echo '30203400f0b400000018e01500a0400016303020' | sudo tee -a "${EDID}" && \
                                        echo '3400000000000018b41400a050d0112030203500' | sudo tee -a "${EDID}" && \
                                        echo '80d810000018ab22a0a050841a3030203600b00e' | sudo tee -a "${EDID}" && \
                                        echo '1100001800000000000000000000000000000000' | sudo tee -a "${EDID}" && \
                                        echo '0000000000000000000000000000000000000000' | sudo tee -a "${EDID}" && \
                                        echo '00000000000000000000000000000045' | sudo tee -a "${EDID}" && \
                                        sudo v4l2-ctl --device=/dev/video0 --set-edid=file="${EDID}" --fix-edid-checksums
                                      

                                      That setting will persist across reboots but not across updates. To make it permanent across updates, see this post.

                                      If the new EDID causes problems, you can restore the original EDID with these commands:

                                      # Do this only if the steps above cause issues.
                                      EDID="/home/ustreamer/edids/tc358743-edid.hex"
                                      sudo cp ~/tc358743-edid.hex.bak "${EDID}" && \
                                        sudo chown ustreamer:ustreamer "${EDID}" && \
                                        sudo v4l2-ctl --device=/dev/video0 --set-edid=file="${EDID}" --fix-edid-checksums
                                      
                  2. O
                    In reply tobakabonpapa:
                    Oriol Espanyol @Oriol
                      2021-06-26 20:55:00.080Z

                      Hi Michael,

                      I also purchased TinyPilot voyager recently for my laptop and have the same problem as reported in this post.

                      It work first time on the target laptop (Windows) using HDMI port. However, after first reboot of the TinyPilot I also get the "NO SIGNAL" message and keyboard and mouse sometimes working, sometimes not. I tried different configurations on the same laptop, using Docking Station, VGA to HDMI adapter, etc. Rebooted several times the TinyPilot and the laptop without success.
                      When I try on different laptop (Mackbook Pro) it works fine (HDMI on USB-c hub). However, when I try back on Windows laptop it continues to show the "NO SIGNAL" message. Windows laptop works with additional screen via VGA and HDMI. So all hardware seems to be fine.

                      Please advice.

                      Oriol

                      1. Sorry to hear you're running into this.

                        Can you share your logs from System > Logs?

                        Did it just work that first time on the Windows laptop or has it ever worked after that? Have you tried reducing the video resolution on the Windows laptop?

                        1. OOriol Espanyol @Oriol
                            2021-07-01 10:58:19.827Z

                            Yes, please see below:

                            https://logs.tinypilotkvm.com/PG7tiNPN

                            Tried different display resolutions without success

                            1. In reply tomichael:
                              OOriol Espanyol @Oriol
                                2021-07-01 11:34:00.802Z

                                Some additional information and testing from my side:

                                1. My Windows laptop has two video output ports: VGA and DisplayPort but no HDMI. I have two adapters, one for VGA to HDMI and another one for DisplayPort to HDMI.
                                  When using the VGA port and the corresponding adapter to HDMI, I could not manage to get the Tinypilot working even though I tried all resolution options from my laptop.
                                  When using the DisplayPort with the corresponding adapter, the Tinypilot works just fine.
                                2. My MacOS laptop has also no HDMI output, but I have an adapter for USB-C to HDMI, and that seems to work fine as well.
                                3. The Windows laptop works with the VGA output and VGA to HDMI adapter to a HDMI screen.
                                1. Thanks for the additional explanation!

                                  So, it works with all scenarios except VGA to HDMI on the Windows laptop?

                                  It's possible that the VGA adaptor doesn't work with TinyPilot. Which brand VGA to HDMI adaptor is it? I rarely hear of VGA adaptors that don't work with TinyPilot, but a couple brands that I know work are FOINNEX and uoeos.

                                  You could also try the alternate EDID solution that I suggested in a thread above.

                            2. Progress
                              with handling this problem
                            3. H
                              @Herry
                                2022-02-08 13:05:48.809Z

                                Hi @michael ,

                                Just got my Voyager 2 around two weeks ago, great product btw.

                                I have found an issue similar with @bakabonpapa,
                                In my case, try to remote control with Dell laptops, when I tried to go into bios mode, enter delete/F12, with the Dell laptop it can enter the bios mode but on the tinypilot web interface it always shows up "no signal" (mouse and keyboards still works), after the laptop run into login screen it was able to capture the video by doing nothing. I have tried it on two models of Dell laptop 7420/7390.

                                Please kindly advise how to solve.

                                Thanks!

                                1. Michael Lynch @michael2022-02-08 20:10:23.123Zreplies toHerry:

                                  @Herry - Thanks for reporting this. Sorry about the trouble here.

                                  Some laptops refuse to show the BIOS screen on an external display. Other laptops can show BIOS on an external display, but you have to change the laptop's BIOS options to enable it.

                                  • Are there any BIOS options that control displaying to an external monitor?
                                  • If you connect the laptop to a regular monitor and enter BIOS, does the BIOS screen show up on the monitor?
                                  1. H
                                    @Herry
                                      2022-02-09 03:58:56.412Zreplies tomichael:

                                      Hi Michael,

                                      Thank you for your comment.

                                      At first may I know how to restore the original "tc358743-edid.hex.bak" file, I accidently no backup the origin file run the follow command,

                                       readonly EDID="/home/ustreamer/edids/tc358743-edid.hex"
                                      echo -ne "" | sudo tee "${EDID}" && \
                                        echo '00ffffffffffff0052628888008888882d1e0103' | sudo tee -a "${EDID}" && \
                                        echo '800000780aee91a3544c99260f50542540000100' | sudo tee -a "${EDID}" && \
                                        echo '0100010001000100010001010101d51b00505000' | sudo tee -a "${EDID}" && \
                                        echo '19400820b80080001000001eec2c80a070381a40' | sudo tee -a "${EDID}" && \
                                        echo '3020350040442100001e000000fc00546f736869' | sudo tee -a "${EDID}" && \
                                        echo '62612d4832430a20000000fd00323d0f2e0f0000' | sudo tee -a "${EDID}" && \
                                        echo '000000000000012a02030400de0d20a030581220' | sudo tee -a "${EDID}" && \
                                        echo '30203400f0b400000018e01500a0400016303020' | sudo tee -a "${EDID}" && \
                                        echo '3400000000000018b41400a050d0112030203500' | sudo tee -a "${EDID}" && \
                                        echo '80d810000018ab22a0a050841a3030203600b00e' | sudo tee -a "${EDID}" && \
                                        echo '1100001800000000000000000000000000000000' | sudo tee -a "${EDID}" && \
                                        echo '0000000000000000000000000000000000000000' | sudo tee -a "${EDID}" && \
                                        echo '00000000000000000000000000000045' | sudo tee -a "${EDID}" && \
                                        sudo v4l2-ctl --device=/dev/video0 --set-edid=file="${EDID}" --fix-edid-checksums
                                      
                                      sudo cp ~/tc358743-edid.hex.bak "${EDID}"
                                      

                                      when I tried to run the command you provide shows : No such file or director
                                      and the resolution now shows wired I guess is 1024*768, I wish to restore it back can you help on this?

                                      According to your advise, I have tried it on external monitor and it works via using Fn + F8 to switch the display, then I found a similar topic Pre-boot display output on laptops, how to trigger ,
                                      same with @hicktastic results push Fn+F8 in TinyPilot, the JavaScript key translation for this combination is MediaStop and TinyPilot won't send it (shows up in red). So I'm wondering is there any update on this.

                                      Here's my logs https://logs.tinypilotkvm.com/13E9zaM5

                                      Thanks!

                                      1. Michael Lynch @michael2022-02-09 23:20:39.024Zreplies toHerry:

                                        You can run this command to restore the default EDID:

                                        EDID="/home/ustreamer/edids/tc358743-edid.hex"
                                        echo "00ffffffffffff005262888800888888
                                        2d1e0103800000780aee91a3544c9926
                                        0f505400000001010101010101010101
                                        010101010101011d007251d01e206e28
                                        5500c48e2100001e8c0ad08a20e02d10
                                        103e9600138e2100001e000000fc0054
                                        6f73686962612d4832430a20000000fd
                                        003b3d0f2e0f1e0a2020202020200135
                                        020321434e041303021211012021a23c
                                        3d3e1f2309070766030c00300080e300
                                        7f8c0ad08a20e02d10103e9600c48e21
                                        0000188c0ad08a20e02d10103e960013
                                        8e210000188c0aa01451f01600267c43
                                        00138e21000098000000000000000000
                                        00000000000000000000000000000000
                                        00000000000000000000000000000028" | sudo tee "${EDID}"
                                        

                                        According to your advise, I have tried it on external monitor and it works via using Fn + F8 to switch the display, then I found a similar topic Pre-boot display output on laptops, how to trigger ,
                                        same with @hicktastic results push Fn+F8 in TinyPilot, the JavaScript key translation for this combination is MediaStop and TinyPilot won't send it (shows up in red). So I'm wondering is there any update on this.

                                        The Fn key varies by keyboard, so hitting Fn+F8 on your client machine (where you're viewing TinyPilot in the browser) is not necessarily the same as hitting Fn+F8 on your laptop. Can you share a photo of what the F8 key looks like on your laptop?

                                        1. H
                                          @Herry
                                            2022-02-10 15:02:41.140Zreplies tomichael:

                                            Hi Michael,

                                            Thanks for your prompt response!

                                            I'm able to get it back at normal resolution.

                                            Here's the keyboard image same as Dell 7420

                                            Thnaks,
                                            Herry

                                            1. Michael Lynch @michael2022-02-11 19:43:34.456Zreplies toHerry:

                                              Okay, I have a Dell laptop here with a similar button. I'm going to try to capture the HID code to see if I can get a workaround for you, but I won't be able to set it up until next week.

                                              1. Michael Lynch @michael2022-02-14 22:37:52.067Zreplies tomichael:

                                                @Herry - I unfortunately wasn't able to find a way to get TinyPilot to send this key. I'm not sure it's possible for external keyboards to even send this key, as I don't see it documented in the USB spec for keyboards. I've filed a bug to investigate:

                                                If this breaks the scenario you had in mind for your Voyager 2, please shoot the team an email at support@tinypilotkvm.com and we'll find a fair resolution for you.

                                                1. H
                                                  @Herry
                                                    2022-02-18 06:55:58.120Zreplies tomichael:

                                                    Hi Michael,

                                                    First of all, thank you for your comments and suggestions,
                                                    For your information I did tried it with a external keyboard connect it with the Dell laptop, and it don't work.

                                                    Thanks, I still try digging more possibility on this great products, so for now not consider return it.
                                                    In the meantime, I'll keep following on your investigate topic, hopes to hear the good news soon.

                                                    Thanks,
                                                    Herry