![]() |
|
|||||||
| Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here. |
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
||||
|
||||
|
HD Homerun issues...
so, I get a call from my mom about the SageTV setup I have over at her house...
the "support" call was mostly unintelligible non technical while trying to be technical gibberish that roughly translated into sage isn't recording her shows, and live TV didn't work... anyway, I go over, seems both HDHR's I set her up with are constantly rebooting... one old v1 HDHR and one of the newer HDHR3's... nothing networky seems to be going on as the reboot even with the network cable unplugged... I am guessing power supplies? why would both supplies go bad at the same time though? just in case it is not the supplies, I also ordered a new HDHR, but now they are calling them the connect or something? is that still plug n' play/compatible with sage? do they work the same as the old HDHR's?
__________________
NOTE: As one wise professional something once stated, I am ignorant & childish, with a mindset comparable to 9/11 troofers and wackjob conspiracy theorists. so don't take anything I say as advice... |
|
#2
|
|||
|
|||
|
It does seem odd that they'd both go bad at the same time, but if I had to guess why they would constantly reboot then power supply would be a good guess. Maybe a power surge could have blown the power supplies. I got a lightning strike once that blew out the power supply in a TV and a VCR.
I guess you should also check the outlet/power strip with a meter to make sure you aren't having power issues from the wall to the units. Or maybe just plug them into another outlet/power strip that you know is good. There were issues with the original V1 power supplies dying, but I surely think you would have seen that already. I had to replace them on my V1s years ago. (bad parts from a supplier according to Silicon Dust) Also, how long have they been installed? I wonder if maybe the firmware might be way out of date. I don't think I've ever heard of it causing reboots, but just another point to check. I had 2 of the original HDHR's and one of the tuners died on one of them so I had to replace it. I also went with an HDHR connect and it indeed does work almost identically to the old V1 HDHRs. Bonus, now you only need one cable input to feed both tuners so you can do away with a splitter that you needed for the old V1s.
__________________
Wayne Dunham Last edited by waynedunham; 04-26-2017 at 03:37 PM. |
|
#3
|
|||
|
|||
|
There is a firmware version that would cause this. I think it was 20140604.
I purchased a HDHR-US on ebay that was supposed to be in GOOD WORKING CONDITION, ( it probably did work for the seller) but when I hooked it up to my router it would reboot every several seconds. I read somewhere about a firmware bug causing it to constantly renew its IP address, and that disconnecting the internet from the router would stop it so I could do the upgrade, and that solved the problem |
|
#4
|
|||
|
|||
|
Quote:
__________________
Wayne Dunham |
|
#5
|
|||
|
|||
|
Here is a link to the silicondust forum that covers this issue in detail.
https://forum.silicondust.com/forum/...ic.php?t=62920 |
|
#6
|
|||
|
|||
|
I have a strange issue with my HDHR tuner where it seems to go down for a minute or two around the top of the hour. I wonder if this could be related to this issue or other DHCP-types of issues with the HDHR described here: https://forum.silicondust.com/forum/...ic.php?t=63510
__________________
New Server - Sage9 on unRAID 2xHD-PVR, HDHR for OTA Old Server - Sage7 on Win7Pro-i660CPU with 4.6TB, HD-PVR, HDHR OTA, HVR-1850 OTA Clients - 2xHD-300, 8xHD-200 Extenders, Client+2xPlaceshifter and a WHS which acts as a backup Sage server |
|
#7
|
||||
|
||||
|
fwiw, the power supplies where fine...
I did not have time to try the Firmware fix, but next time I get over there seems like an easy enough thing to at least try... and it seems to fit the symptoms perfectly... in hindsight, I probably should have tried the FW fix first...
__________________
NOTE: As one wise professional something once stated, I am ignorant & childish, with a mindset comparable to 9/11 troofers and wackjob conspiracy theorists. so don't take anything I say as advice... |
|
#8
|
||||
|
||||
|
just a fwiw, it was in fact the firmware...
thanks for the heads up dstrahler5...
__________________
NOTE: As one wise professional something once stated, I am ignorant & childish, with a mindset comparable to 9/11 troofers and wackjob conspiracy theorists. so don't take anything I say as advice... |
|
#9
|
||||
|
||||
|
now I am wondering about my HDHR's firmware...
I am using the unraid/docker setup... how is HDHR firmware handled in this case? does the docker/linux just take care of it? do I need to upgrade them manually?
__________________
NOTE: As one wise professional something once stated, I am ignorant & childish, with a mindset comparable to 9/11 troofers and wackjob conspiracy theorists. so don't take anything I say as advice... |
|
#10
|
|||
|
|||
|
Interesting point. I just joined the unRaid/Docker club and I don't think I'll ever go back. However before migrating off my windows machine, I took the opportunity to upgrade firmware on all my HDHR devices with the windows setup tool.
There is a Silicondust Linux config tool that looks like it will upgrade firmware. However it requires a development environment to make the tool. I don't think unRaid in its natural state will support that. Seems there is are a few ways to go at this. 1) Use a different machine running Windows with the config tool loaded. Make sure the HDHR devices are on an accessible LAN segment (issue for me as I run all the HDHR devices on an isolated NIC) and upgrade as documented. 2) Spin up a Windows VM. Load the config tool and upgrade as documented (would remove the NIC issue, but seems a lot of overhead for the task). At least you wouldn't need an extra PC to run Windows. 3) Make a "development" docker that loads all the right packages. Download the sources from Silicondust. Make the config tool and run as documented. I wonder how difficult it would be to make a light weight docker development environment? I'm assuming slackware would be the path of least resistance, but if I understand correctly I think the docker engine would let you run any Linux flavor?
__________________
Frankentivo: iStar D-380HB, SuperMicro X107-F-O, Xeon 1270v3 CPU, Kingston 8 GB 1600MHz DDRR3L x 4 Tuners: 4 x HDHR OTA, 4 x HDHR3 OTA, 3 x HDHR Prime UnRAID Pro: 1 x Samsung 500GB Cache, 5 x WD Red 4TB (1 Parity, 4 Data) Extenders: 2 x HD-200, 1 x HD-300 on Atlona PRO3HD66m Sage: V9.0.14.567 with OpenDCT on unRaid docker, Gemstone, BMT, Web UI, PlayOn, TiSage |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Issues with Homerun Prime Network Tuner | jimakrause | SageTV Github Development | 0 | 01-15-2016 06:06 AM |
| HD Homerun Dual tuner issues | animapper | Hardware Support | 6 | 04-08-2013 01:01 PM |
| Sagetv V7 unable to scan channels while HD homerun config reports no issues? | jmcomp124 | Hardware Support | 7 | 09-06-2011 09:17 AM |
| Playback issues with HD Homerun recordings | pknowles | Hardware Support | 3 | 12-20-2009 08:31 PM |
| hd-homerun with nas | tedson | Hardware Support | 3 | 08-05-2009 04:41 PM |