I've just had an email from Humax saying...
As I'm already running CFW based on this version (1.03.12/2.22) will my Hummy ignore it or do I need to prevent it installing it (which is easy enough, just have to remember to do so)?
And does its eventual release mean Chris can spill the beans?
I thought the DLNA server would decrypt HD if it were streaming to a trusted client, such as another Hummy. And it decrypts SD to any client. But in any case, all of the recordings are decrypted on the box, thanks to CFW.
So does the stock firmware not include a DLNA client?
I'm running custom firmware (1.03.12/2.22) on TWO HDR FOX-T2s, named humax3 and humax2 (humax1 broke - see this thread: http://hummy.tv/forum/threads/hdr-fox-t2-stops-seeing-the-hard-drive.4234/) but I don't think that the CFW has anything to do with it. I think this is a feature that is...
Just as a follow-up....
I moved the HDD from my older, broken HDR-FOX-T2 (running 1.02.xx) onto my new box (running 1.03.12/2.22).
The drive was formatted at the factory, presumably by standard firmware v 1.02.xx. On the new 1.03.12 system it appears to work, and fix-disk shows no errors.
So...
More for my own education, how do you capture the OTA file? I mean what combination of hardware/software do you use?
Hmm nice feature would be a package that listens for an OTA upgrade but instead of installing it just saves it and tells you of its existence next time you start the box. A...
I tried installing e3fsprogs 1.41.14-2 from the web interface but it didn't change the binary for e2fsck. Didn't check to see if it changes the binary for the formatter though.
So I guess I've got the latest.
Well, here's the next instalment.
Story so far: All three partitions are formatted from the command line (not Humax's UI) and check out fine with fix-disk.
This evening I ran fix-disk again. Still good.
Ran the Humax UI disk check. No problems.
So I tried formatting it from the Humax UI. The...
Ah good... so that's normal - thanks for pointing that out. And sure enough, power-cycling from the front panel (or remote, presumably) turn it on normally, then off normally. So all good then.
Wonder what fix-disk makes of it. You'll remember before the hard (mains) power cycle it was all...
Further update.
I reformatted the first partition:
mkfs.ext3 -m 0 -O sparse_super -T largefile /dev/sda1
So once again fix-disk is happy. And the box is happy.
Left it in standby overnight, which includes one program record plus the usual wake-up for OTA upgrade.
In the morning, fix-disk...
Well, with
mkfs.ext3 -m 0 -O sparse_super -T largefile /dev/sda[12]
done on sda 1 and 2, and sda3 being clean anyway, I though I'd let it record stuff for a bit then run fix-disk....
Fix-disk completes with no error.
Now, let's see if the stock reformat reintroduces the behaviour....
From the...
Update. fix-disk (with no options) now finds no error or problems, as you might expect. But I imagine that a stock reformat will reintroduce the strangeness.
It was via the Humax UI.
Last night I deleted all the partitions then rebooted, so there couldn't be any funnies left over. Naturally the UI asked me to reformat so I did. Thus the box is now reformatted completely.
running my hacked fix-disk:
...
Inode 15689, i_size is 8030115674518766...
And for the enthusiast, here's the log from running a hacked fix-disk so e2fsck doesn't write to the drive. Log attached.
The closing lines are:
Illegal block #537922567 (4294967295) in inode 15695. IGNORED.
Illegal block #537922568 (4294967295) in inode 15695. IGNORED.
Illegal block...
I think fix-disk has a -y hard-coded into the call to e2fsck.
humax3# fix-disk -B -P -2 -x -n
Running /bin/fix-disk
Custom firmware version 2.22
Checking disk sda
Partition /dev/sda1 is already unmounted
Partition /dev/sda2 is already unmounted
Partition /dev/sda3 is already unmounted...
Well spotted. Because I reformatted the HDD humax3 has no packages installed at all (am I correct?) it will be running the stock Humax version. Whereas humax2 has loads of packages installed.
I assume there's no way the package manager can avoid overwriting newer stock versions? Or do the CFW...
Ok, here they are, although I don't see much untoward.
Here's one:
Humax HDR-Fox T2 (humax3) 1.03.12/2.22
To return to the menu, type: exit
humax3# smartctl -a /dev/sda
smartctl 6.0 2013-04-25 r11898M [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-12, Bruce Allen...
Ok, here they are, although I don't see much untoward.
Here's one:
Humax HDR-Fox T2 (humax3) 1.03.12/2.22
To return to the menu, type: exit
humax3# smartctl -a /dev/sda
smartctl 6.0 2013-04-25 r11898M [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-12, Bruce Allen...
I never got it to work (but the background OPT+ decrypt worked fine). Is it possible it is written for 'proper' bash but I'm only using the standard busybox bash?
I'm the guy from this thread:
http://hummy.tv/forum/threads/hdr-fox-t2-stops-seeing-the-hard-drive.4234/
But this has nothing to do with that. Instead it concerns the two refurbished (graded) HDR-FOX-T2 boxes. I only got the 500Mb ones as it happens.
Basically, in both cases they've...
I've just had an email from Humax saying...
As I'm already running CFW based on this version (1.03.12/2.22) will my Hummy ignore it or do I need to prevent it installing it (which is easy enough, just have to remember to do so)?
And does its eventual release mean Chris can spill the beans?
I thought the DLNA server would decrypt HD if it were streaming to a trusted client, such as another Hummy. And it decrypts SD to any client. But in any case, all of the recordings are decrypted on the box, thanks to CFW.
So does the stock firmware not include a DLNA client?
I'm running custom firmware (1.03.12/2.22) on TWO HDR FOX-T2s, named humax3 and humax2 (humax1 broke - see this thread: http://hummy.tv/forum/threads/hdr-fox-t2-stops-seeing-the-hard-drive.4234/) but I don't think that the CFW has anything to do with it. I think this is a feature that is...
Just as a follow-up....
I moved the HDD from my older, broken HDR-FOX-T2 (running 1.02.xx) onto my new box (running 1.03.12/2.22).
The drive was formatted at the factory, presumably by standard firmware v 1.02.xx. On the new 1.03.12 system it appears to work, and fix-disk shows no errors.
So...
More for my own education, how do you capture the OTA file? I mean what combination of hardware/software do you use?
Hmm nice feature would be a package that listens for an OTA upgrade but instead of installing it just saves it and tells you of its existence next time you start the box. A...
I tried installing e3fsprogs 1.41.14-2 from the web interface but it didn't change the binary for e2fsck. Didn't check to see if it changes the binary for the formatter though.
So I guess I've got the latest.
Well, here's the next instalment.
Story so far: All three partitions are formatted from the command line (not Humax's UI) and check out fine with fix-disk.
This evening I ran fix-disk again. Still good.
Ran the Humax UI disk check. No problems.
So I tried formatting it from the Humax UI. The...
Ah good... so that's normal - thanks for pointing that out. And sure enough, power-cycling from the front panel (or remote, presumably) turn it on normally, then off normally. So all good then.
Wonder what fix-disk makes of it. You'll remember before the hard (mains) power cycle it was all...
Further update.
I reformatted the first partition:
mkfs.ext3 -m 0 -O sparse_super -T largefile /dev/sda1
So once again fix-disk is happy. And the box is happy.
Left it in standby overnight, which includes one program record plus the usual wake-up for OTA upgrade.
In the morning, fix-disk...
Well, with
mkfs.ext3 -m 0 -O sparse_super -T largefile /dev/sda[12]
done on sda 1 and 2, and sda3 being clean anyway, I though I'd let it record stuff for a bit then run fix-disk....
Fix-disk completes with no error.
Now, let's see if the stock reformat reintroduces the behaviour....
From the...
Update. fix-disk (with no options) now finds no error or problems, as you might expect. But I imagine that a stock reformat will reintroduce the strangeness.
It was via the Humax UI.
Last night I deleted all the partitions then rebooted, so there couldn't be any funnies left over. Naturally the UI asked me to reformat so I did. Thus the box is now reformatted completely.
running my hacked fix-disk:
...
Inode 15689, i_size is 8030115674518766...
And for the enthusiast, here's the log from running a hacked fix-disk so e2fsck doesn't write to the drive. Log attached.
The closing lines are:
Illegal block #537922567 (4294967295) in inode 15695. IGNORED.
Illegal block #537922568 (4294967295) in inode 15695. IGNORED.
Illegal block...
I think fix-disk has a -y hard-coded into the call to e2fsck.
humax3# fix-disk -B -P -2 -x -n
Running /bin/fix-disk
Custom firmware version 2.22
Checking disk sda
Partition /dev/sda1 is already unmounted
Partition /dev/sda2 is already unmounted
Partition /dev/sda3 is already unmounted...
Well spotted. Because I reformatted the HDD humax3 has no packages installed at all (am I correct?) it will be running the stock Humax version. Whereas humax2 has loads of packages installed.
I assume there's no way the package manager can avoid overwriting newer stock versions? Or do the CFW...
Ok, here they are, although I don't see much untoward.
Here's one:
Humax HDR-Fox T2 (humax3) 1.03.12/2.22
To return to the menu, type: exit
humax3# smartctl -a /dev/sda
smartctl 6.0 2013-04-25 r11898M [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-12, Bruce Allen...
Ok, here they are, although I don't see much untoward.
Here's one:
Humax HDR-Fox T2 (humax3) 1.03.12/2.22
To return to the menu, type: exit
humax3# smartctl -a /dev/sda
smartctl 6.0 2013-04-25 r11898M [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-12, Bruce Allen...
I never got it to work (but the background OPT+ decrypt worked fine). Is it possible it is written for 'proper' bash but I'm only using the standard busybox bash?
I'm the guy from this thread:
http://hummy.tv/forum/threads/hdr-fox-t2-stops-seeing-the-hard-drive.4234/
But this has nothing to do with that. Instead it concerns the two refurbished (graded) HDR-FOX-T2 boxes. I only got the 500Mb ones as it happens.
Basically, in both cases they've...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.