Latest Ceton InfiniTV 4 Info Thread - Page 124

Yup - we just got notification of the final fix yesterday, and haven testing since then. We are starting to get some feedback from affected customers (like yourself) that his resolves it, so that is good. We will ultimately communicate this more widely, as we suspect others are affected that have not opened support tickets with us.

While we drove this with Microsoft, we did invite the other major players in this space (Hauppauge and SiliconDust) to provide a businses impact statement to Microsoft for this issue. Hauppauge is the only company that took us up on our offer

I have two InfiniTv units. One in a WHS setup and the other is a simple HTPC. I am on driver package 12.08.28.0019.

I upgraded to firmware beta 1.2.1.1 and hardware 6408. These hardware and firmware versions have caused problems on both machines: No signal errors are now common. These errors require reboots, sometimes more than one a day.

I would like to rollback the firmware and hardware to the last stable versions, which were the ones that the utility identified as stable. But, the way the new software works, these things are downloaded automatically and I don't know where they are or even what versions they are. Does someone know where the Ceton utility saves downloads? If they are not saved, can someone tell me an easy way to downgrade?

Thanks!

Have you opened a ticket with our support staff? We would like to understand why you are having difficulty.

Confused about Win8 and Ceton with all the talk about the Q being discontinued. If I installed Win8 and the MCE add-on on my HTPC, would the current Ceton USB still work?

Yes. The issue with the Q is in relation to the embedded version of Windows, which is a special version of Windows intended for dedicated devices rather than a general purpose PC. The problem for the Q is that Microsoft's intent to make a version of WMC available for the embedded version of Windows 8 is not well defined - it would be unwise for Ceton to inset in and release a product that they can't get an adequate life cycle out of. None of this affects the viability of our Ceton tuners or the Echo because WMC will be available for the non-embedded version of Windows 8, which ensures us at least -10 years before we have anything to really worry about.

Normally, I would be happy to help. Unfortunately, I just don't have the time right now.

You're going to have to open a support ticket anyway so Ceton can give you links to download the earlier firmwares. They can be installed via the web interface. I know because I installed every firmware ever released when trying to solve a problem recently. Turns out my issue wasn't firmware related at all. Now I'm running the beta F/W again without issue.

I think you can downgrade by uninstalling the current beta driver and re-installing the stable release. It should try to flash the older firmware during the install. PM me if you want a link to the firmware prior to that.

My signal errors turned out to be related to DRM. Don't know if my problem is the same as yours, but HERE are the details and my solution.

I don't want to RMA my Ceton InfiniTV 4 USB because it will not update to latest beta. Looking at the log below, can anyone explain the update failure? It shows "Failed to write sig" then "Unable to handle image" but why?

Jan 1 00:05:48 ocur[21]: ocur: firmware_update.cgi get info 5362266
Jan 1 00:05:48 ocur[21]: ocur: firmware_update.cgi open 5362266
Jan 1 00:05:49 ocur[21]: ocur: web update filename ceton_infinitv_beta_fw_20120915_1_2_1_1.IMAGE
Jan 1 00:05:55 ocur[21]: ocur: firmware_update.cgi close, got 5362065 bytes
Jan 1 00:05:55 ocur[21]: ocur: Starting update from ceton_infinitv_beta_fw_20120915_1_2_1_1.IMAGE (5362014)
Jan 1 00:05:55 ocur[21]: ocur: Built cert store
Jan 1 00:05:55 ocur[21]: ocur: Parsed PKCS7
Jan 1 00:05:55 ocur[21]: ocur: No dp fields specified
Jan 1 00:05:55 ocur[21]: ocur: Got download params
Jan 1 00:06:18 ocur[21]: ocur: Checking signer 1/1
Jan 1 00:06:19 ocur[21]: ocur: Verified signer
Jan 1 00:06:19 ocur[21]: ocur: currentOCUROrganizationName "CableLabs"
Jan 1 00:06:19 ocur[21]: ocur: currentMFGOrganizationName "Ceton Corp."
Jan 1 00:06:19 ocur[21]: ocur: NotAfter: Tue May 22 23:59:59 2018 (0x5b04aeff) UTC
Jan 1 00:06:19 ocur[21]: ocur: NotBefore: Fri May 23 00:00:00 2008 (0x48360900) UTC
Jan 1 00:06:19 ocur[21]: ocur: SigningTime: Sun Sep 16 00:23:55 2012 (0x50551c1b) UTC
Jan 1 00:06:19 ocur[21]: ocur: Signed during validity period
Jan 1 00:06:19 ocur[21]: ocur: Found Mfg signature
Jan 1 00:06:19 ocur[21]: ocur: Verified mfg signature
Jan 1 00:06:19 ocur[21]: ocur: Verify Done.
Jan 1 00:06:19 ocur[21]: ocur: Got valid code image offset
Jan 1 00:06:19 ocur[21]: ocur: board version 4
Jan 1 00:06:19 ocur[21]: ocur: Checking 1 hardware ids
Jan 1 00:06:19 ocur[21]: ocur: This firmware matches our hardware id
Jan 1 00:06:19 ocur[21]: ocur: Firmware version of image 0x1020101 >= current version 0x1010802, continuing
Jan 1 00:06:19 ocur[21]: ocur: Actual Code Image Size 5360650 (header was 144)
Jan 1 00:06:45 ocur[21]: upnp: Done sending rapid advertise
Jan 1 00:06:45 ocur[21]: ocur: Saving signature to "/ceton/rw/ocur/slot_one/sig.dat"
Jan 1 00:06:45 ocur[21]: ocur: ERROR: Failed to write sig
Jan 1 00:06:45 ocur[21]: ocur: ERROR: Unable to write new firmware
Jan 1 00:06:45 ocur[21]: ocur: ERROR: Failed to write firmware
Jan 1 00:06:45 ocur[21]: ocur: ERROR: Unable to handle image
Jan 1 00:06:45 ocur[21]: ocur: ERROR: Failed
Jan 1 00:06:45 ocur[21]: ocur: WebUpdate done

My iTV4 pcie wouldn't update firmware at all. Hardware was fine, but firmware wouldn't take stable or beta. The error was "cannot update, if this continues, contact Ceton support'. I sent Ceton the diag and they are doing a RMA on the card.

It was updating fine until 1.2.1.1 and they said to RMA it too after submitting a ticket with the collected info file but really need it and trying to find a way to fix this without having to RMA it. It works fine just will not update too 1.2.1.1.

did they offer to do an "advanced" RMA? That means they will go ahead and ship you a new iTV4 and once you get it, you ship the broken card back to them. This takes them getting your CC#, however so they will charge you if you fail to return the broken card.

I never RMA'd an item before. Guess I've been really lucky! Didn't know about "advanced" RMA. Thanks for the info. So you were able to "advanced" RMA yours right?

Yes indeed. In fact, all this happened yesterday. The support staff said that they will email me a tracking number for the new card coming my way via fedex 2 day shipping. As soon as I get the new one, I will pack up the broken one (with coax dongle, brackets, etc) and put it in the self addressed box and take it to Fedex.

Just for the record, same thing happened to me. The RMA support was really great, but I was surprised that a beta firmware could 'brick' the ability to upgrade to future firmwares enough to require and RMA (especially since it operated just fine).

What versions are known-brick firmwares?

I was on: ceton_20120626_infinitv_r11_v6212.IMAGE which was a beta to help with tuning speed (for false no signal errors, also fixed in the latest public beta).

xnappo

Mine has ceton_infinitv_fw_20120412_1_1_8_2.IMAGE

Was yours using that image too when you updated too 1.2.1.1?

Well...has anyone on this board...using ceton_infinitv_fw_20120412_1_1_8_2.IMAGE, able to update too 1.2.1.1?
Edited by ChiliBean - 10/16/12 at 7:04am

No - I was running 1.1.7.10.

xnappo

Do you have that image file...1.1.7.10? If so, can you mail it or link it to me so I can upload it using the web interface?

Want to see if it will upload that image. If so, then will update too 1.2.1.1. Just to give that a try or if my current firmware "bricked" any further uploads.

First - no - that is a beta firmware that Ceton does not want distributed

Second -WHY?! - that is the firmware that broke my card.

xnappo

Oh, I thought you said that was the firmware you used to upgrade too 1.2.1.1.

What is the firmware you had when you updated too 1.2.1.1? That's the one I would like to try to upload.

Sorry in I was not clear - there was no fix. I had to do an RMA. It was bricked from the upgrade.

xnappo
Edited by xnappo - 10/16/12 at 7:42am

Thanks.

Please post the firmware and hardware version of your new one when you get it. Just curious what version comes out on the replacement. Thanks again!

I also want to say thanks to the RMA staff. The guy called me to start the RMA process and I was driving around in a low signal area. We couldn't hear each other. I told him that I would call him back asap. He ended up calling me back within the hour, which is unexpected proactive behavior from any support staff.

Ceton support.... great job!

Agreed. The support was great. I actually felt a bit guilty since I know they are a small company and the 2-day shipping with paid return can't be good for the profit margins!

xnappo

I feel even worse.. mine is going from WA to Cincy, OH and back to WA again

Mine was the same hardware version I had before - something starting with a 6 .

Firmware was 1.1.8.2 - but that one doesn't have the fast tuning which messes up my system, so I upgraded to the public beta and it has been working well.

xnappo

Ok, I was waiting to hear more about this, good work from Ceton, especially when dealing with the behemoth MS, but is this KB to fix a specific issue mentioned by Proam, or is this something that fixes other items too, like the 29/59 bug where the broadcasters are screwing with the video TS?
Edited by dbailey75 - 10/18/12 at 9:10am

Should be getting a new one in 2 days and using the shipping container and label to send old one. Thanks for the "advanced" RMA info. It was the first time I RMA'd an item and the only part that really concerned me was when he asked for my credit card info.

I guess this is the same place to talk about the USB iTV4 device?

Anyway, I'm in the middle of building a new, super small, low heat mini ITX HTPC using the iTV4 USB. This system will be in the living room to power the main TV. Once the Ceton Echos come out, I would like to get anywhere from 1-4 Echos to populate the rest of the house.

My question is, how does the USB iTV4 work with extenders when compared to the PCIe version? Is there anything I should be aware of? The only thing I've seen so far is people placing the iTV4 vertically instead of horizontally to help with the heat.

I don't have the PCIe version or multiple extenders, but I'm happy with the performance of the USB version and it works fine when using my Xbox 360 as an extender to watch live TV. Ceton suggests/recommends a USB hotfix referenced in http://cetoncorp.com/support/index.php?/Knowledgebase/Article/View/50/0/usb-hotfixes-and-improvements.