Beta firmware candidate for InfiniTV available - 14.10.3.163

[erkotz]

Hi all,
We've got a new beta firmware candidate for InfiniTV tuners. This firmware has the following changes:
-Workaround for issue in NDS CableCARDs
-Resolves an issue where CableCARD firmware updates may not succeed
-General stability improvements.

It is available at http://update.cetoncorp.com/get/infinit ... _163.IMAGE

I'm interested in feedback, whether it fixed an issue for you, no changes were noticed (so no regressions) or introduced a new issue. If you believe it introduced a new issue, please roll back to your prior firmware and confirm the issue goes away, and then let me know. Thanks!

[cwinfield]

Installed without issue, just rebooted and so far so good. I will post if I notice anything unusual.

[kd6icz]

That's not nice erkotz to put this out late on a Friday and peace out for the weekend... j/k. I'll update when I get home and report back.

[golfdude]

channel changes for me definitely seems better, not running into error screens so far..

so far its looking good

[TheOsburnFamil]

Installed on both InfiniTV 4 PCI cards. No problems. No issues. So far so good.

[Sea3]

channel changes for me definitely seems better, not running into error screens so far..

so far its looking good

For channel changing comparison, which build do you upgrade from?

[golfdude]

hewy erk.. whats the status of tuner pooling for the eth 6 in this release? is it out of beta? not in this build at all?

[Rew452]

Installed yesterday, upgraded without incidence on 6ETH. Biggest improvement is channel change time. For now very much improved. I say it that way as I have seen it improve only to continue to take longer after some time of using. So far so good.

Rew

[signcarver]

I am hoping this update allows me to finally get my cablecard firmware update that I reported here on 8/27... but they haven't been sending out the updates each night like they were back then so I generally have seen the same problem one night a week if that... hopefully this fixes it but it isn't enough of a burden for me to get a new card if the problem really is in the card as I suspect.

One thing I did notice since going to this new release is needing to confirm going to cablecard diagnostic screen (and only the diag page, the other 8 don't exhibit this behavior)... Never had to before and I couldn't really tell if this message was coming from the card or the tuner (is it possible my card got a partial update that now exhibits this behavior)... and for some reason when I access that screen, feeds cut to WMC in a few seconds (often resulting in a temporary subscription required) For most this wouldn't be an issue but I happen to go to those screens a lot more often. One thing I noticed is it always seems to recover from such issues where before if there was a problem I'd have to reset either the tuner or the TA. I am going to give it a few days to try and pull in the update before reverting to see if this new behavior follows the firmware or not.

I also got a scare early on after the update as diagnostics said my card wasn't staged anymore and usually that is a pain to fix however a different page said waiting for update (I assumed card firmware update that never came) so I waited a little bit and "not staged" turned to "ready" so I guess it was just taking my card a little bit longer to boot up than normal.

[erkotz]

One thing I did notice since going to this new release is needing to confirm going to cablecard diagnostic screen (and only the diag page, the other 8 don't exhibit this behavior)... Never had to before and I couldn't really tell if this message was coming from the card or the tuner (is it possible my card got a partial update that now exhibits this behavior)... and for some reason when I access that screen, feeds cut to WMC in a few seconds (often resulting in a temporary subscription required) For most this wouldn't be an issue but I happen to go to those screens a lot more often. One thing I noticed is it always seems to recover from such issues where before if there was a problem I'd have to reset either the tuner or the TA. I am going to give it a few days to try and pull in the update before reverting to see if this new behavior follows the firmware or not.

That is the workaround for NDS cards. Cisco actually makes the NDS card, and unfortunately, there is not a good way to tell a "PowerKey" Cisco card from an "NDS" Cisco card, so the workaround is applied to both cards. Accessing that screen breaks Cisco cards, so we reset the card after accessing that screen. We are still trying to get Cisco to fix the actual issue here. When that occurs, we will remove the workaround.

[kd6icz]

I've recorded a few shows with the new firmware. All is normal except for one of the recordings. It macroblocked the entire hour and a half of the program. I've tried to duplicate the issue but haven't been able to do so. So I will let you know if it happens again.

[jaimeknapp]

Update failed on my PCIe4. Ran a diag collection immediately after. Yes, the image file was located in the local directory c:\ceton\ which is writeable.

From Log.txt:

Jan 5 02:29:32 ocur[21]: ocur: firmware_update.cgi get info 5494593
Jan 5 02:29:32 ocur[21]: ocur: firmware_update.cgi open 5494593
Jan 5 02:29:32 ocur[21]: ocur: web update filename ceton_infinitv_beta_fw_14_10_3_163.IMAGE
Jan 5 02:29:37 ocur[21]: ocur: firmware_update.cgi close, got 5494401 bytes
Jan 5 02:29:37 ocur[21]: ocur: Starting update from ceton_infinitv_beta_fw_14_10_3_163.IMAGE (5494254)
Jan 5 02:29:37 ocur[21]: ocur: Built cert store
Jan 5 02:29:37 ocur[21]: ocur: Parsed PKCS7
Jan 5 02:29:37 ocur[21]: ocur: No dp fields specified
Jan 5 02:29:37 ocur[21]: ocur: Got download params
Jan 5 02:29:55 ocur[21]: ocur: Checking signer 1/1
Jan 5 02:29:55 ocur[21]: ocur: Verified signer
Jan 5 02:29:55 ocur[21]: ocur: currentOCUROrganizationName "CableLabs"
Jan 5 02:29:55 ocur[21]: ocur: currentMFGOrganizationName "Ceton Corp."
Jan 5 02:29:55 ocur[21]: ocur: NotAfter: Tue May 22 23:59:59 2018 (0x5b04aeff) UTC
Jan 5 02:29:55 ocur[21]: ocur: NotBefore: Fri May 23 00:00:00 2008 (0x48360900) UTC
Jan 5 02:29:55 ocur[21]: ocur: SigningTime: Fri Oct 3 22:27:16 2014 (0x542f22c4) UTC
Jan 5 02:29:55 ocur[21]: ocur: Signed during validity period
Jan 5 02:29:55 ocur[21]: ocur: Found Mfg signature
Jan 5 02:29:55 ocur[21]: ocur: Verified mfg signature
Jan 5 02:29:55 ocur[21]: ocur: Verify Done.
Jan 5 02:29:55 ocur[21]: ocur: Got valid code image offset
Jan 5 02:29:55 ocur[21]: ocur: board version 17
Jan 5 02:29:55 ocur[21]: ocur: Checking 1 hardware ids
Jan 5 02:29:55 ocur[21]: ocur: This firmware matches our hardware id
Jan 5 02:29:55 ocur[21]: ocur: Firmware version of image 0xe0a03a3 >= current version 0xe040615, continuing
Jan 5 02:29:55 ocur[21]: ocur: Actual Code Image Size 5492890 (header was 144)
Jan 5 02:30:11 ocur[21]: ocur: Saving signature to "/ceton/rw/ocur/slot_two/sig.dat"
Jan 5 02:30:11 ocur[21]: ocur: WARNING: Failed to write sig, trying again
Jan 5 02:30:11 ocur[21]: ocur: ERROR: Failed to write sig
Jan 5 02:30:11 ocur[21]: ocur: ERROR: Unable to write new firmware
Jan 5 02:30:11 ocur[21]: ocur: ERROR: Failed to write firmware
Jan 5 02:30:11 ocur[21]: ocur: ERROR: Unable to handle image
Jan 5 02:30:11 ocur[21]: ocur: ERROR: Failed
Jan 5 02:30:11 ocur[21]: ocur: WebUpdate done

[erkotz]

Update failed on my PCIe4. Ran a diag collection immediately after. Yes, the image file was located in the local directory c:\ceton\ which is writeable.

From Log.txt:

Jan 5 02:29:32 ocur[21]: ocur: firmware_update.cgi get info 5494593
Jan 5 02:29:32 ocur[21]: ocur: firmware_update.cgi open 5494593
Jan 5 02:29:32 ocur[21]: ocur: web update filename ceton_infinitv_beta_fw_14_10_3_163.IMAGE
Jan 5 02:29:37 ocur[21]: ocur: firmware_update.cgi close, got 5494401 bytes
Jan 5 02:29:37 ocur[21]: ocur: Starting update from ceton_infinitv_beta_fw_14_10_3_163.IMAGE (5494254)
Jan 5 02:29:37 ocur[21]: ocur: Built cert store
Jan 5 02:29:37 ocur[21]: ocur: Parsed PKCS7
Jan 5 02:29:37 ocur[21]: ocur: No dp fields specified
Jan 5 02:29:37 ocur[21]: ocur: Got download params
Jan 5 02:29:55 ocur[21]: ocur: Checking signer 1/1
Jan 5 02:29:55 ocur[21]: ocur: Verified signer
Jan 5 02:29:55 ocur[21]: ocur: currentOCUROrganizationName "CableLabs"
Jan 5 02:29:55 ocur[21]: ocur: currentMFGOrganizationName "Ceton Corp."
Jan 5 02:29:55 ocur[21]: ocur: NotAfter: Tue May 22 23:59:59 2018 (0x5b04aeff) UTC
Jan 5 02:29:55 ocur[21]: ocur: NotBefore: Fri May 23 00:00:00 2008 (0x48360900) UTC
Jan 5 02:29:55 ocur[21]: ocur: SigningTime: Fri Oct 3 22:27:16 2014 (0x542f22c4) UTC
Jan 5 02:29:55 ocur[21]: ocur: Signed during validity period
Jan 5 02:29:55 ocur[21]: ocur: Found Mfg signature
Jan 5 02:29:55 ocur[21]: ocur: Verified mfg signature
Jan 5 02:29:55 ocur[21]: ocur: Verify Done.
Jan 5 02:29:55 ocur[21]: ocur: Got valid code image offset
Jan 5 02:29:55 ocur[21]: ocur: board version 17
Jan 5 02:29:55 ocur[21]: ocur: Checking 1 hardware ids
Jan 5 02:29:55 ocur[21]: ocur: This firmware matches our hardware id
Jan 5 02:29:55 ocur[21]: ocur: Firmware version of image 0xe0a03a3 >= current version 0xe040615, continuing
Jan 5 02:29:55 ocur[21]: ocur: Actual Code Image Size 5492890 (header was 144)
Jan 5 02:30:11 ocur[21]: ocur: Saving signature to "/ceton/rw/ocur/slot_two/sig.dat"
Jan 5 02:30:11 ocur[21]: ocur: WARNING: Failed to write sig, trying again
Jan 5 02:30:11 ocur[21]: ocur: ERROR: Failed to write sig
Jan 5 02:30:11 ocur[21]: ocur: ERROR: Unable to write new firmware
Jan 5 02:30:11 ocur[21]: ocur: ERROR: Failed to write firmware
Jan 5 02:30:11 ocur[21]: ocur: ERROR: Unable to handle image
Jan 5 02:30:11 ocur[21]: ocur: ERROR: Failed
Jan 5 02:30:11 ocur[21]: ocur: WebUpdate done

Please open a ticket with our support group.

[jaimeknapp]

Done.

Ticket: GAS-724-74493

[signcarver]

Had a slight glitch this morning where it appeared tuning requests didn't go through. Logs just showed a "playing" on each request and no mention of it actually trying to tune/acquire a channel like normal. This started right when I usually see an attempt to update CableCARD firmware however no such mention of that was in the logs... Checked Ceton Diagnostics and while attempting to view a channel in WMC (forgot to close it) I could see that it reported that no card was inserted and suggesting reseating it (not sure if this is part of the same handling of cisco cards as reported before as to why it would temporarily report no card) ... a few seconds later it showed a cisco card, tried another channel (not protected) and it tuned... tried another and nothing and saw the cycle of card issues again... tried unprotected channel again and it refused to work... power cycled device (USB tuner) and all was well again.

I wanted to report it in case others see this issue and a pattern forms but right now I will just say it was a temporary glitch, possibly set off by another attempt of a firmware update as the timing was correct to when I normally see one but got no notification in logs or WMC that one was being attempted.

[mldenison]

Can you post a link to the prior firmware? I've had a number of problems since updating both ETH's to this firmware. It's required me to reboot the ETH's and the HTPC daily. I've been getting, in no particular order, daily prompts for a new cablecard detected, no tuners available, viewing conflicts, recorded shows that are unwatchable due to audio breakup and video pixelation and occasional loss of connectivity to one ETH. On the prior version I only had most of these issues once a week or so.

Thanks

[cwinfield]

Can you post a link to the prior firmware? I've had a number of problems since updating both ETH's to this firmware. It's required me to reboot the ETH's and the HTPC daily. I've been getting, in no particular order, daily prompts for a new cablecard detected, no tuners available, viewing conflicts, recorded shows that are unwatchable due to audio breakup and video pixelation and occasional loss of connectivity to one ETH. On the prior version I only had most of these issues once a week or so.

Thanks

This is what you want

http://www.cetoncorp.com/downloads/ceto ... 6_21.IMAGE

For some reason ceton has them hidden on the linux support page

[golfdude]

im running into a recording issue that when im recording a show, its not letting me access any other tuners.. so i cant record 1 show and watch another.. to keeps telling me the tuners are in use when they arent... i rebooted both the system and the ETH, and the issue continues..

[mldenison]

This is what you want

http://www.cetoncorp.com/downloads/ceto ... 6_21.IMAGE

For some reason ceton has them hidden on the linux support page

Thanks, I appreciate it.

[kd6icz]

Can you post a link to the prior firmware? I've had a number of problems since updating both ETH's to this firmware. It's required me to reboot the ETH's and the HTPC daily. I've been getting, in no particular order, daily prompts for a new cablecard detected, no tuners available, viewing conflicts, recorded shows that are unwatchable due to audio breakup and video pixelation and occasional loss of connectivity to one ETH. On the prior version I only had most of these issues once a week or so.

Thanks

As I mentioned I had one show record full of digital error. This was on my PCIe 6. I have since integrated my ETH back into my system to bring my tuner total back up to 12. I previously had an issue with what I think was an IP conflict (not sure) and the internal card would just disappear. So far (knock on wood) 24 hours later they are still both functioning together. I was actually able to use all 12 tuners at once for the first time with no errors whatsoever!