• The forum software that supports hummy.tv will be upgraded to XenForo 2.3 on Wednesday the 20th of November 2024 starting at 7pm

    There will be some periods where the forum is unavailable, please bear with us. More details can be found in the upgrade thread.

Major issue with installing CF HDR FOX T2 1.03.12 mod 3.02

There is clearly a problem with the SATA interface:
Code: 
ata1: SATA link down (SStatus 4 SControl 300)
ATA: abnormal status 0x7F on port 0xb051001c
The last section of the output (in post #19) shows the system trying (and failing) to bring the SATA connection up.

Edit. So the above error message is not unusual (see post below), but there is ultimately a failure to bring the SATA connection up.
 
Last edited:
For reference, this is what mine shows relating to the disk port:

Code: 
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

ata1: exception Emask 0x10 SAct 0x0 SErr 0x40000 action 0x42 frozen
ata1: soft resetting port
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8, max UDMA/133, 3907029168 sectors: LBA48 NCQ (depth 0/32)
ata1.00: configured for UDMA/133
ata1: EH complete
  Vendor: ATA  Model: ST2000VM002-9UY1  Rev: SC01
  Type:  Direct-Access  ANSI SCSI revision: 05

So the difference is that the soft reset fails with:

Code: 
ata1: SRST failed (status 0xFF)
ata1: SRST failed (err_mask=0x100)
 
And apparently the 0xff status is not a reset failure. It indicates no device.
 
Guys please take a step backwards, it's been over 30 years since I last looked at any type of programming language.

Black Hole - software I use can take a scrolling window screen shot, easier for me to use, no pasting.

OK MontysEvilTwin & af123, since I know that the SATA interface & disk works fine with older CF - where is the problem being generated, hardware or software and what can be done to try and resolve it.

afi23 "And apparently the 0xff status is not a reset failure. It indicates no device." Since I know that the HDD is present, what would be causing this.
 
@Will42. Figuring out why it is not working is beyond my limited knowledge, I'm afraid: af123 is the expert. If you need to use the unit I would install standard 1.03.12 (to get the latest official kernel) then 1.03.12/ CFW 2.23 in the interim.
 
The custom kernel is built using the sources and configuration published by Humax on their open source site.
I'm pretty sure that they have made further changes since these were published which aren't included in the custom version. We could probably get them to update the downloads under the terms of the open source licence, anyone want to try?

Almost everyone is perfectly fine with CFW 3 but there is at least one other user that has had a problem since upgrading - http://hummy.tv/forum/threads/problem-with-ntfs-3g-package-on-hdr-fox-t2.5927/
That user's problem is that the external disk stops working unless it is kept spinning by periodically being written to.
When I compare the available kernel source code from the HDR and HD models, I see the following difference which could explain it:

Code: 
--- stblinux-2.6.18-7.1_r3761/drivers/usb/storage/scsiglue.c  2009-07-14 06:06:44.000000000 +0000
+++ stblinux-2.6.18-7.1_hd/drivers/usb/storage/scsiglue.c  2010-07-14 08:37:54.000000000 +0000
@@ -171,6 +171,12 @@
  sdev->retry_hwerror = 1;

+#if defined(HUMAX_PLATFORM_BASE)
+  /* USB disks should allow restart.  Some drives spin down
+  * automatically, requiring a START-STOP UNIT command. */
+  sdev->allow_restart = 1;
+#endif
+
  } else {

The HD kernel also forces the SATA link speed to 1.5Gb/s in some cases..
 
@af123. Presumably then without the up to date kernel specifications (which Humax would need to supply) there is no easy way to modify the custom kernel to make it work for @Will42? Rather than continue full support for CFW pre version 3.00, could you supply him with a kernel only update file (based on official 1.03.12) that could be applied after the update to 1.03.12/ CFW 3.02? Apart from the DLNA-Filter package, everything else should be compatible with the official kernel.
 
MontysEvilTwin said:
@af123. Presumably then without the up to date kernel specifications (which Humax would need to supply) there is no easy way to modify the custom kernel to make it work for @Will42? Rather than continue full support for CFW pre version 3.00, could you supply him with a kernel only update file (based on official 1.03.12) that could be applied after the update to 1.03.12/ CFW 3.02? Apart from the DLNA-Filter package, everything else should be compatible with the official kernel.
Click to expand...
I have some things to try and would like to get to the bottom of it, but yes, he could use a hybrid system with the stock kernel. The files I have sent him will enable him to do that in case the new test version doesn't improve things.
 
I have had an occurrence where the box was in standby (recording a programme) but trying to access it via the web interface I was greeted with the screen that states:

“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.”

Which I thought was odd as it was happily recording! Bringing it out of standby did nothing but a power down into standby and backup (after the recording had finished) cured it.

Only had it happen once so far!
 
@Will42 - I've sent you a personal message with a new version to try. Simpler process too so quicker to try and to revert.
 
Hi,
Over the last few days I am having similar problems, where the disk drive is not being recognised when powering up. If I go to menu->settings->systems, data storage is greyed out. The only way to recover seems to be power off the box for half an hour, and switch it back on. I am using CF 3.00 (build 2137), over humax ver 1.03.12. The hard disk is a new disk (as detailed in my other post, a 2TB Segate) after the original one died. Since installing it a few months ago, I've not really had any trouble, until now, where the hard disk doesn't seem to power up coming out of standby, a couple of times now. Could something else be failing, such as the hard disk controller, maybe due to overheating?
 
It happened again this morning, coming out of standby the first time I switched on. So, I guess it's not overheating, since it was cold! I telneted in and restarted to maintenance mode and did a short disk check, which completed, so this disk must have come back online. Exiting and rebooting into normal got everything going again. This is going to be a pain if it keeps happening, as I'm not always around to try and get it up and running. I suspect something more serious is causing these failures!
 
@af123 work around was successful, as per your email:

"...... then you can install CFW3.02 and then the second update file above so you'll end up with CFW3.02 on top of the stock 1.03.12 kernel.. it will be a working CFW3 system apart from the one package that Monty mentioned."

Here is the code that you asked for:

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

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=1000
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 19 2015 20:54:01
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 0x4050000 action 0x42 frozen
ata1: soft resetting port
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F0000)
ata1.00: ATA-8, max UDMA/133, 1953525168 sectors: LBA48 NCQ (depth 0/32)
ata1.00: configured for UDMA/133
ata1: EH complete
  Vendor: ATA       Model: ST31000424CS      Rev: SC13
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on sda2, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda3, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Adding 131064k swap on /mnt/hd3/.swap0.  Priority:-1 extents:35 across:269036k
humax#

Thanks guys for your help.
 
Last edited:
phd said:
It happened again this morning, coming out of standby the first time I switched on. So, I guess it's not overheating, since it was cold! I telneted in and restarted to maintenance mode and did a short disk check, which completed, so this disk must have come back online. Exiting and rebooting into normal got everything going again. This is going to be a pain if it keeps happening, as I'm not always around to try and get it up and running. I suspect something more serious is causing these failures!
Click to expand...
I have two units with Seagate Pipeline 2TB disks (ST2000VM003). One has been running for six months or so without issue. The other, within a day, started exhibiting similar symptoms to yours until, within a few days, the disk was only recognised after a cold reboot. I could always hear the disk spinning up; it just wasn't being recognised. I returned the disk and the replacement has been fine for two months now. If af123 releases a new kernel it wouldn't hurt to try it out, but it may be a faulty disk. You might have to return it to the vendor under warranty.
 
This whole scenario is open to the possibility that the OP's disk is faulty in some way which does not affect operation with the old kernel - or is it that the new kernel is not sufficiently tolerant of some kind of manufacturing variability?
 
The OP's (@Will42) issue does seem to be related to the kernel as it only manifested when upgrading to CFW3.00: it sounds like af123 has found a fix. The problem encountered by @phd sounds more like a faulty disk as it is intermittent (so it does sometimes work with with the custom kernel of CFW 3.00) and sounds just like the problem I described above, which was cured by disk replacement.
 
Both could be explained by manufacturing variability, if the new kernel is less tolerant of such.
 
Black Hole said:
Both could be explained by manufacturing variability, if the new kernel is less tolerant of such.
Click to expand...
You could be right.
Since I posted above (post #38), Will42 has added to post #34. It sounds like his system is now working with CFW 3.02/ official 1.03.12 kernel. It must be nigh on impossible to replicate all the features of the official kernel as Humax have not published up to date specifications.
 
You must log in or register to reply here.
Back
Top