Separate names with a comma.
Discussion in 'DirecTV TiVo Powered PVRs & Receivers' started by wishbone4401, Apr 4, 2012.
The unit is a Hughes DVR40.
stevel is correct, 3.5d is what you need. At this point, it looks like DirecTV is only going to do Series 2 software updates so you'd need to acquire the image and install it yourself to continue using your DSR6000.
Sent you the information on that one as well via PM. Thanks again for all of your help!
some people are on 7 weeks with this issue. That just blows my mind.
These Tivos are a little finicky about using DMA. I would suggest adding "runideturbo=false" to your bootpage parameters.
Then again, it might be something else. I've had one, running stock (unhacked), lock up, reboot, and stick on "Welcome Powering Up" until the plug as pulled.
I am not going to make that much effort to get a hobbled and crippled TIVO working. I have replaced the TIVO unit twice and a couple HDD and power supplies to keep my TIVO active and running. I have brand-new 50 inch plasma that looks like sh*it on the SD signal from my TIVO. D* knows I have a series one, its listed in my account on my "account" web page. They didn't have the common courtesy to let me know they were going to make changes to the network. I understand may it make business sense to stop supporting 10 year-old OS boxes. I can even accept that they may not have known in advance that S1 boxes were going to be killed/disabled/whatever-you-call-it by the actions they have taken. They have had nearly two months to either fix the problem or contact me to make arraignments to get me a new receiver (Tivo or D* DVR). They haven't and based on what I have read here... they can't fix it. They want to send me a new box, they want a "new" contract for a ten-year+ loyal customer. I don't care what "they want".
It looks like to me DirectTv is going to need to invest in several thousand dollars in advertising to get me to trust them again. It was "promised" (or whatever you would call their emails and postings) that they were working with TIVO to create a quality product to replace/upgrade D* with a quality product and they come out with what I consider a vastly inferior product based on an ancient OS.
I don't keep up with all the advances in TIVO and D* DVRs but I know TIVO has better products out in the stand-alone, FIOS and cable environment. If D* wanted to disable the Netflix and other web content, I am OK with that but that's not what they are offering to sell me after a 10 year investment in TIVO and D*.
This next Tuesday morning, I move over to the dark-side with Microsoft's "replacement" to UltimateTV... MediaRoom on "almost" FTTH. My dish will go dark.
I've been bringing my DVR-SD80 to work all week to dial in. Seems about every other day it dials in and it gets a download of something which it then installs (takes about 4 min to process after download (via phone). Other days it's a quick dial in process with nothing to update. Maybe one of these mornings It'll pull down the 6.4 from the stream. Fingers crossed.
My HDVR2 running 6.2a ad the 6.4a software downloaded from the satellite. I decided
to use an old copy of 'the slicer' to install 6.4a via the USB interface (should have used
the serial port instead). HDVR2 rebooted into 6.4a. Only screwedup local channel is
ch4 (KNBC in Los Angeles), which has no audio or video.
I was unable to finish the task using 'the slicer' via USB/ethernet. The USB became
disabled since the reboot into 6.4a. I still need to run a script to restablish the symlinks
in var. I built a null modem serial cable, established a connection with the HDVR2 but
cannot get past the "What is the password?" prompt. Any ideas on how to finish what
I started with 'the slicer'?
Tried an old copy of the Zipper today and fat fingered it. USB not working.
Running 6.4a added missing local channels back to the guide data but did not
resolve the no audio/video on local ch4 KNBC.
For those of you having networking issues after upgrading, the issue is that the stock 6.4a network drivers are not compatible with the hacked kernel. You have to copy over your old drivers, or install new backport drivers. If you can mount your old partition, copy over the driver modules from /lib/modules
I would like to offer a further bit of advice. The issues with drivers and backported drivers were always a little nebulous for me (I didn't do enough reading on it). The latest version of the Zipper will install the backported drivers for you. Earlier versions of the Zipper did not. If you are having network issues after formatting, an easy solution may be to simply pull the drive and run zipper on it, install backported drivers, then assign your IP address and router address.
I rely on this method to get my network issues resolved.
The best way to avoid a driver issue is to copy the ones from the other software partition. Those drivers have already been tested with the kernel you are using, for as long as you have been running that box.
I'm having the same issue as above. Updates fine; next day see all of the channels; runs OK for a couple of days then locks up. Three different drives all acting exactly the same. No problems before the DTV update.
Which unit and which version are you runing?
awsome, just what i was hoping for, downloading and will be seeding to help others. thanks.
Except that no one is seeding it to download in the first place.
I noticed that too.
hmm...just noticed that too!
I am seeding it and I ran a test, im seeing a bunch of PEX errors in the logs and im using the latest uTorrent 3.1.3
[2012-05-20 14:32:22] Connecting ...
[2012-05-20 14:32:22] Checking intermediate networks ...
[2012-05-20 14:32:33] Running Upload test ...
[2012-05-20 14:32:46] Running Download test ...
[2012-05-20 14:32:57] Testing alternate servers...
[2012-05-20 14:33:24] Checking for forwarded port
[2012-05-20 14:33:25] Results: Port is open. Your network is properly configured.
[2012-05-20 14:33:25] Port Forward test complete.
I see plenty of incoming connections and my setup is good
I can see there are 8 of us connected, but not a single seed.