No Signal - USB Grabber Keeps Losing Signal #1361
Answered
by
Johnson145
Johnson145
asked this question in
Q&A
-
|
First of all, awesome project, thank you very much! My problem: Initially, everything is working fine. However, after a while I always end up with the live preview showing only the "No Signal" screen of HyperHDR. Toggling only the USB grabber does not fix it. Toggling all components does work though. Relevant logs in HyperHDR seem to be limited to
Details``` [19336.467436] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [109517.624613] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [114011.419152] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [115846.444348] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [115846.444408] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [115846.444433] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [160796.964405] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [180543.012743] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [182116.609091] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [182116.609142] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [182116.609163] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [182116.609191] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [184067.472579] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [189741.225434] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [199358.313443] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [226487.412191] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [234730.016974] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [240141.084327] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [246527.394486] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [247875.239141] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [249659.185517] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [260808.978373] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [261810.526250] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [264822.095779] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [269130.219317] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [274753.802442] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [282477.238335] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [322209.663711] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [343700.935392] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [345270.822271] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [349657.159536] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [352122.379105] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [352122.379158] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [352122.380234] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [356853.172614] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [360538.619533] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [369669.011039] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [399315.269685] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [431091.753864] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [438333.508891] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [438412.005832] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [445128.020722] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [455234.387115] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [455234.387161] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [455234.387186] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [455703.671847] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [486669.629393] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [495593.034372] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [495593.034439] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [496015.530645] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [498643.346488] usb 2-2: USB disconnect, device number 2 [498643.351709] usb 2-2:1.1: Failed to set UVC probe control : -108 (exp. 34). [498646.582834] usb 2-2: new SuperSpeed USB device number 3 using xhci_hcd [498646.603235] usb 2-2: LPM exit latency is zeroed, disabling LPM. [498646.633908] usb 2-2: config 1 has an invalid interface number: 7 but max is 4 [498646.633914] usb 2-2: config 1 has no interface number 4 [498646.634678] usb 2-2: New USB device found, idVendor=3188, idProduct=1000, bcdDevice= 1.00 [498646.634685] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [498646.634689] usb 2-2: Product: UGREEN 25173 [498646.634693] usb 2-2: Manufacturer: ITE [498646.634696] usb 2-2: SerialNumber: 00000001 [498646.646637] usb 2-2: Found UVC 1.10 device UGREEN 25173 (3188:1000) [498646.681451] hid-generic 0003:3188:1000.0002: hiddev96,hidraw0: USB HID v1.11 Device [ITE UGREEN 25173] on usb-0000:01:00.0-2/input7 [507621.920682] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [528337.505930] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [533283.321838] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [534903.497365] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [534964.164974] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [534964.164974] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [534964.165011] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [534964.165013] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [534979.791905] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [538707.541584] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [543681.504242] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [547721.381797] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [572880.252447] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [572907.766338] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [585164.349611] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [585174.185585] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [601767.780275] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [601880.343473] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [601880.343509] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [601880.343531] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [601880.343558] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1). [631881.608470] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [664728.358702] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [674006.464282] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [674766.450773] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [675634.755347] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [675743.120094] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. [675940.405725] uvcvideo 2-2:1.1: Non-zero status (-71) in video completion handler. ```My setup:
I've already searched through existing discussions. Most often, an insufficient power supply is assumed. However, I'm already using the official PSU for the Pi. As far as I understand, the Pi4 may still have problems providing full power via USB. I don't understand if/how I can workaround this. Many people are using this hardware, so there must be a way, right? I've reduced video capturing settings to 1280x720 (minimum for P010) 30 frames and quarter of frame mode to reduce load as much as possible. I've updated the eeprom to the latest version, too. I've play around with a different usb grabber, a different HyperHDR version and video capturing settings for I'm desperately looking for a fix, but have no clue how to continue. Any help is appreciated very much! |
Beta Was this translation helpful? Give feedback.
Answered by
Johnson145
Dec 5, 2025
Replies: 2 comments 14 replies
-
|
Hi |
Beta Was this translation helpful? Give feedback.
12 replies
-
|
Unfortunately, changing the USB cable isn't the solution yet. Still having troubles with a good cable. I did ensure to push the After disabling the auto restart automation via home assistant, HyperHDR hasn't started after turning on the TV tonight. Again Anyway, here are new logs, which do contain new grabber errors: Details
|
Beta Was this translation helpful? Give feedback.
-
|
I have at least a second variant of this problem: sometimes I only see the |
Beta Was this translation helpful? Give feedback.
-
|
It is a system (kernel) or hardware problem (broken unit, bad or too long usb cables, insufficient power supply etc), even without a video signal this ugreen grabber should not disappear from the OS. In such situation it displays green (not yellow at least when HDR tone mapping is enabled and correctly calibrated) text: no signal. But it's still a valid video stream. |
Beta Was this translation helpful? Give feedback.
-
|
If I'm lucky, it was the HDMI cable which came with the Ugreen grabber. I've replaced it with a new certified one and haven't experienced any troubles since then. Hopefully not just a coincidence and it stays that way. |
Beta Was this translation helpful? Give feedback.
Answer selected by
Johnson145
-
Just double checked: it's yellow for me. HDR is enabled and calibrated. 
|
Beta Was this translation helpful? Give feedback.
-
|
Well, mine is yellow only when tone mapping is off an green if on in P010. LUT P010 available in the download section in GUI. But if it works fine for you then it's OK. I once had a case with the AV ACCESS 4KVC00 and its included long USB cable because sometimes grabber wouldn't work properly with it causing error 19/grabber disappears from the OS for few seconds . |
Beta Was this translation helpful? Give feedback.
-
|
Observed this for a while now and it looks like the main problem was actually the HDMI cable which came with the Ugreen grabber. In case I'm not the only one reporting such problems, maybe worth a short note in the hardware suggestions? The main problem discussed here, the recurring no-signal screen of HyperHDR, is basically solved. I still saw the grabber's no-signal screen once or twice within the last two weeks, although content was playing. Don't know why, but that's rare enough to get solved by a simple restart workaround. Regarding the color of the grabber's no-signal screen: When using your LUT, it is inseed green instead of yellow. My own calibration yields a yellow one though. Don't know why and obviously the color of that screen does not matter, I was just afraid of a more general color calibration problem. While most colors look quite accurate, I feel like having an issue with "white and gray colors getting too blue". That's probably a different story and I may open a separate discussion later on. THANK YOU for the project and the good support. |
Beta Was this translation helpful? Give feedback.
-
|
Poor quality or damaged cables can, of course, cause 'no signal' screens, but the grabber shouldn't disconnect in such cases unless it has a firmware bug, which I haven't noticed with mine. Disconnects in the OS likely indicate a hardware issue (grabber/RPI), drivers, or power supply. But it's hard for me to say for sure since I can't replicate it myself – these are just my guesses based on experience with other grabbers. |
Beta Was this translation helpful? Give feedback.
-
|
hello , i had a very similar setup and experienced the same problem ( though still using MS2130 and no WLED ) . it turned out to be apperently a handshake problem between EZ-SP12H21 and my TV ( no matter if EDID was copied or fixed to 4K60 ) . reverting back to EZ-SP12H2 solved it . |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Thanks for your response! That's interesting. I thought that the connection to the TV is not relevant, because the grabber is connected to the splitter independently of the TV, isn't it? Could be worth a try though. Unfortunately, i don't have another separate splitter. If I understand correctly, I could try using only the UGREEN for both jobs (without HDCP at least). You have been using the same cables for both setups? Which TV do you have? LG OLED xy, too? |
Beta Was this translation helpful? Give feedback.
-
|
same cables all along , old samsung 4K60 HDR TV . all sources going through an AVR , then to splitter , out1 to tv , out2 to grabber . i noticed very long waiting times between 2 sources ( 1 being HDR , the other not ) , TV " recovered " after 10 seconds , grabber never went out of " no signal " . all of that was gone after " downgrading " to SP12H2 again |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I'm lucky, it was the HDMI cable which came with the Ugreen grabber. I've replaced it with a new certified one and haven't experienced any troubles since then.
Hopefully not just a coincidence and it stays that way.