Major issue with installing CF HDR FOX T2 1.03.12 mod 3.02

Will42

New Member
Major issue with installing CF HDR FOX T2 1.03.12 mod 3.02. Every time I have installed:
1. WebIF tells me that no HDD can be found.
2. Pressing Media button on RC displays nothing on TV although I know programmes have been recorded.
3. Re-installing previous version of CF HDR FOX T2 1.03.12 mod 2.22 does not fix the problem.

I have to re-install official firmware release HDR FOX T2 1.03.12 before HDD can be used plus CF HDR FOX T2 1.03.12 mod 2.22 to use WebIF. Again I'm told that I need to upgrade CF.

Have I missed something or has anyone else been having this problem and more importantly has a solution been found.
 

Black Hole

May contain traces of nut
Er, no...

Install the CF and run the Telnet stuff (as per my link). The HDD has probably gone "read only", which would not affect the standard firmware or access to existing recordings.
 
OP
W

Will42

New Member
Er, no...

Install the CF and run the Telnet stuff (as per my link). The HDD has probably gone "read only", which would not affect the standard firmware or access to existing recordings.

Black Hole, with the CF installed, I can’t write/record to the HDD or read any pre-recorded files. The CF temporally makes the HDD invisible to either write to or read from, as far as I can see this can only be resolved by re-installing previous software.
What I mean by invisible:
  1. By pressing Media button on the RC does nothing i.e. nothing appears on TV screen and therefore I can’t play pre-recorded programmes.
  2. Pressing Menu button on the RC, selecting Video from the Channel List does nothing therefore again I can’t play pre-recorded programmes.
  3. Pressing Record button on RC, nothing happens including no red ring to show recording has started.
  4. Using WebIF I get two messages “Custom Firmware Successfully Installed!” and “To install the full web interface and supporting packages a suitably formatted internal hard disk must be present and none was detected. This is unexpected - a HDR-Fox T2 should have an internal disk which is already formatted appropriately.”
  5. Using Telnet Software advises me “Unable to find a disk.” (See Screen Shots)
WebIF Screen.jpg Putty Telnet Screen.jpg
I do understand that CF should not affect the resident firmware but co-exists with it. At the moment I am happy to run with the older CF, but one of the main reasons I bought the Humax HDR-Fox T2 was due to the custom firmware and support (going that extra mile).
 
Last edited:

Black Hole

May contain traces of nut
Using Telnet Software advises me “Unable to find a disk.” (See Screen Shots)
Hmm. I'm sure this can be fixed, but it will need someone more knowledgable in this area than me. We have enough satisfied users to know this is not an interaction between the standard firmware and custom firmware - it has to be a problem in your particular unit's file systems.
 

prpr

Well-Known Member
How can it be a filesystem problem when it can't even find the flippin' disk? For goodness sake, sometimes you can seem extremely dim.
 
OP
W

Will42

New Member
I have to disagree with you Black Hole, I have my unit for 2 years which is when I installed CF and had no problems with CF updates until now. As the screen shot of WebIF proves the CF was installed correctly (file structure must be intact). Since I have no problems using previous CF, whatever changes have been made to this latest version has affected my unit and this is where the problem stems from. As to the question "Does the CF interact with the standard firmware" I think that it is very possible, maybe af123 could shed some light.
 
Last edited:

Black Hole

May contain traces of nut
How can it be a filesystem problem when it can't even find the flippin' disk? For goodness sake, sometimes you can seem extremely dim.
Why else wouldn't the CF be able to see the disk? Maybe I was a bit loose calling it a file system problem, but it's got to be something to do with the disk hasn't it? Instead of handing out insults, how about diagnosing the problem.
 
Last edited:

Trev

The Dumb One
If the filing system/disc is broken, why is it OK with the older/standard firmware? (Posts #84, #86 and #88)
 
OP
W

Will42

New Member
How can it be a filesystem problem when it can't even find the flippin' disk? For goodness sake, sometimes you can seem extremely dim.

I agree with Black Hole, PLEASE NO INSULTS, I am looking to resolve my problem rather than trade insults.
 
Last edited:

af123

Administrator
Staff member
It is most likely being caused by the kernel in CFW 3.xx but nobody else has reported this problem.
I have a debugging kernel that you can try that will provide more diagnostics, I'll send you the link tonight.
 

Owen Smith

Active Member
It is most likely being caused by the kernel in CFW 3.xx but nobody else has reported this problem.
I have a debugging kernel that you can try that will provide more diagnostics, I'll send you the link tonight.

I thought we had one other person that had a similar serious problem with CFW 3.00 which was never diagnosed?
 

prpr

Well-Known Member
Why else wouldn't the CF be able to see the disk?
I don't know. Like af123 said, probably kernel related.
Maybe I was a bit loose calling it a file system problem
Yes, very.
but it's got to be something to do with the disk hasn't it? Instead of handing out insults, how about diagnosing the problem.
Obviously it's something to do with the disk. I don't know what it is, but I know what it ISN'T - it isn't a readonly filesystem, it isn't any filesystem/format problem, it isn't a partition problem and it isn't a partition table problem.
It's is a bit like saying you can't see the box inside three other boxes, when you can't see the outer box at all. It might be true that you can't, but it isn't the source of the trouble.
 
OP
W

Will42

New Member
I think it is not a disk problem, read my posts #84 & #86. The latest version of CF has changed a setting or something like that (possibly to the standard firmware). As re-installing an earlier version of CF DOES NOT correct the fault. Only by re-installing the standard firmware removes the fault (which MUST reset the rogue setting), this allows me to record and watch programmes even before I install any version of CF. Now that you have read my views - why do members tell me that it is A DISK ISSUE!!!!!!!!!! to me it software related even though it may be a 1 in a million chance it happens.
 

MontysEvilTwin

Well-Known Member
@Will42. Try what af123 suggested in post #13. Standard firmware update files from Humax always include a kernel. Before version 3.00, custom firmware updates did not, so when installed, the kernel version was the same as that installed the last time a standard update was applied. So reverting to pre 3.00 custom firmware does not replace the kernel; to do that requires a standard firmware version to be installed first. This fits with your observations. The one known incompatibility with the new CFW kernel is a replacement wifi driver: the rt3070 package. This has been removed from the repository. If you have this package installed, remove it.
 
Last edited:

af123

Administrator
Staff member
(which MUST reset the rogue setting)
No, it replaces the kernel with the official one as MontysEvilTwin said.

Hopefully the debugging kernel will provide some clues about what's going on. It can be downloaded from http://hpkg.tv/
Install CFW 3.00 first and then this additional update file.
Then get access to the command line interface through the telnet menu and type 'dmesg'. Post the ouput here and let's see what it says.
 
OP
W

Will42

New Member
@af123 - Hope this helps:

Code:
Humax HDR-Fox T2 (humax) 1.03.12/3.02

humax# dmesg
Primary instruction cache 32kB, physically tagged, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, linesize 64 bytes.
Synthesized TLB refill handler (23 instructions).
Synthesized TLB load handler fastpath (37 instructions).
Synthesized TLB store handler fastpath (37 instructions).
Synthesized TLB modify handler fastpath (36 instructions).
PID hash table entries: 2048 (order: 11, 8192 bytes)
Found MIPS counter frequency: 203 Mhz
Using 202.501 MHz high precision timer.
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 124416k/262144k available (3129k kernel code, 137568k reserved, 740k data, 160k init, 0k highmem)
Calibrating delay loop... 402.43 BogoMIPS (lpj=201216)
Mount-cache hash table entries: 512
Checking for 'wait' instruction...  available.
plat_prepare_cpus: ENABLING 2nd Thread...
TP0: prom_boot_secondary: Kick off 2nd CPU...
CPU revision is: 0002a044
FPU revision is: 00130001
Primary instruction cache 32kB, physically tagged, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, linesize 64 bytes.
Synthesized TLB refill handler (23 instructions).
Calibrating delay loop... 404.48 BogoMIPS (lpj=202240)
Brought up 2 CPUs
migration_cost=2000
NET: Registered protocol family 16
registering PCI controller with io_map_base unset
registering PCI controller with io_map_base unset
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 4096)
TCP reno registered
brcm-pm: disabling power to USB block
brcm-pm: disabling power to ENET block
brcm-pm: disabling power to SATA block
squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher
NTFS driver 2.1.27 [Flags: R/O].
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver $Revision: 1.90 $ 3 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 22) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 66) is a 16550A
serial8250: ttyS2 at MMIO 0x0 (irq = 67) is a 16550A
loop: loaded (max 8 devices)
brcm-pm: enabling power to ENET block
Broadcom BCM7413 P21 Ethernet Network Device v2.0 Feb 18 2015 19:49:06
Config Internal PHY Through MDIO: 100 MB Full-Duplex (auto-neg)
libata version 2.00 loaded.
brcm-pm: enabling power to SATA block
sata_svw 0000:01:00.0: version 4.0
ata1: SATA max UDMA/133 cmd 0xB0510000 ctl 0xB0510020 bmdma 0xB0510030 irq 42
ata2: SATA max UDMA/133 cmd 0xB0510100 ctl 0xB0510120 bmdma 0xB0510130 irq 42
scsi0 : sata_svw
ata1: SATA link down (SStatus 4 SControl 300)
ATA: abnormal status 0x7F on port 0xb051001c
scsi1 : sata_svw
ata2: SATA link down (SStatus 4 SControl 300)
ATA: abnormal status 0x7F on port 0xb051011c
BCM97XXX flash device: 0x02000000 @ 0x1e000000
Broadcom 9xxxx mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
erase region 0: offset=0x0,size=0x0,blocks=32768
erase region 1: offset=0x20000,size=0x0,blocks=131072
Creating 6 MTD partitions on "Broadcom 9xxxx mapped flash":
0x0000000000000000-0x0000000001800000 : "rootfs"
0x0000000001800000-0x0000000001a00000 : "humaxtv_db"
0x0000000001a00000-0x0000000001c00000 : "backup"
0x0000000001c00000-0x0000000001da0000 : "cfe"
0x0000000001da0000-0x0000000001e00000 : "reserve0"
0x0000000001e00000-0x0000000002000000 : "vmlinux"
physmap platform flash device: 02000000 at 1e000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
erase region 0: offset=0x0,size=0x0,blocks=32768
erase region 1: offset=0x20000,size=0x0,blocks=131072
cmdlinepart partition parsing not available
RedBoot partition parsing not available
usbmon: debugfs is not available
ehci_hcd_brcm_init: Initializing 2 EHCI controller(s)
brcm-pm: enabling power to USB block
10 Dec 2004 USB 2.0 'Enhanced' Host Controller (EHCI) Driver (EHCI-brcm-0)
drivers/usb/host/ehci-brcm.c: starting brcm EHCI USB Controller
- USB h/w setup mode <N>
- USB power enable set for active HIGH mode
brcm-ehci brcm-ehci.0: BRCM EHCI
brcm-ehci brcm-ehci.0: new USB bus registered, assigned bus number 1
brcm-ehci brcm-ehci.0: irq 62, io mem 0x10480300
brcm-ehci brcm-ehci.0: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
10 Dec 2004 USB 2.0 'Enhanced' Host Controller (EHCI) Driver (EHCI-brcm-1)
drivers/usb/host/ehci-brcm.c: starting brcm EHCI USB Controller
brcm-ehci-1 brcm-ehci-1.1: BRCM EHCI
brcm-ehci-1 brcm-ehci-1.1: new USB bus registered, assigned bus number 2
brcm-ehci-1 brcm-ehci-1.1: irq 57, io mem 0x10480500
brcm-ehci-1 brcm-ehci-1.1: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd_brcm_init: Initializing 2 OHCI controller(s)
2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (OHCI-brcm-0)
drivers/usb/host/ohci-brcm.c: starting brcm OHCI USB Controller
- Resetting at b0480408
<-- brcm_start_hc
brcm-ohci-0 brcm-ohci-0.0: BRCM OHCI
brcm-ohci-0 brcm-ohci-0.0: new USB bus registered, assigned bus number 3
brcm-ohci-0 brcm-ohci-0.0: irq 63, io mem 0x10480400
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (OHCI-brcm-1)
drivers/usb/host/ohci-brcm.c: starting brcm OHCI USB Controller
- Resetting at b0480608
<-- brcm_start_hc
brcm-ohci-1 brcm-ohci-1.1: BRCM OHCI
brcm-ohci-1 brcm-ohci-1.1: new USB bus registered, assigned bus number 4
brcm-ohci-1 brcm-ohci-1.1: irq 64, io mem 0x10480600
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
i8042.c: i8042 controller self test timeout.
mice: PS/2 mouse device common for all mice
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
VFS: Mounted root (squashfs filesystem) readonly.
Freeing unused kernel memory: 160k freed
bcmdriver: module license 'Proprietary' taints kernel.
ata1: exception Emask 0x10 SAct 0x0 SErr 0x40000 action 0x42 frozen
ata1: soft resetting port
ata1: SRST failed (status 0xFF)
ata1: SRST failed (err_mask=0x100)
ata1: softreset failed, retrying in 5 secs
ata1: hard resetting port
ata1: COMRESET failed (device not ready)
ata1: hardreset failed, retrying in 5 secs
ata1: limiting SATA link speed to 1.5 Gbps
ata1: hard resetting port
ata1: COMRESET failed (device not ready)
ata1: reset failed, giving up
ata1: EH complete
humax#
 
Last edited:

Black Hole

May contain traces of nut
Inserting a text copy from the console screen into [code]...[/code] tags would have been preferable, but at least we have some data. Splicing together that screen shot as an image must have taken a while.

(Window Telnet provides a "select all" option on right-click, then pressing Return copies the selection to the paste buffer. Other Telnet clients do something similar.)
 
Top