Black Hole
May contain traces of nut
I suppose that might be built into the SoC.
-
The forum software that supports hummy.tv has been upgraded to XenForo 2.3!
Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.
No teletext causes odd pop-up
- Thread starter jack616
- Start date
antipodean
Active Member
Looking at that I suspect that the HM probably means humax, and the rest signifies a hex address, hence the x.The 2000T dump gives HMX80BC7E and the 5000T - HMX8B0000. I would guess HMX=Humax. As for the rest - I'm sorry I haven't a clue.
Oh, I see BH beat me to it with the same conclusion. I suspect the screen text is a Linux kernel panic dump of some sort. The string of 'names' after the WAI look like they may be software function names or module names from a stack dump.
Last edited:
prpr
Well-Known Member
Clearly:
HMX is Humax, the hex numbers are parts of the System ID - 80BC7E and 7E0000 is, or should be, rather familiar
SAM is Samsung and the bit after is a model number etc.
MHG is MHEG
CI is Common Interface
DSM is related to MPEG (DSM-CC - Digital storage media command and control)
The "Linux kernel panic dump of some sort" is just plain wrong.
None of it is very interesting, IMHO.
HMX is Humax, the hex numbers are parts of the System ID - 80BC7E and 7E0000 is, or should be, rather familiar
SAM is Samsung and the bit after is a model number etc.
MHG is MHEG
CI is Common Interface
DSM is related to MPEG (DSM-CC - Digital storage media command and control)
The "Linux kernel panic dump of some sort" is just plain wrong.
None of it is very interesting, IMHO.
EEPhil
Number 28
That would have been my guess - although the hex isn't familiar to me.
Except it isn't a Humax feature - it's something more general.
Black Hole
May contain traces of nut
I call it the most interesting thing in Hummyland for ages. The OP found something new, 15 years into HDR-FOX ownership. I admit this may be purely academic, with no practical benefit, but how much else started like that?
Is it generated within the SoC itself, or using firmware Humax were obliged (or chose) to include in the binary blob (where we might leverage it somehow)?
The precise cause remains unknown. It is known that flooding the HDR-FOX with particular button presses can provoke a reboot, but this is a different kind of "crash". Why does it happen on some services with the "i" icon and not others? We can speculate, but hypotheses require confirmation.
Is it generated within the SoC itself, or using firmware Humax were obliged (or chose) to include in the binary blob (where we might leverage it somehow)?
The precise cause remains unknown. It is known that flooding the HDR-FOX with particular button presses can provoke a reboot, but this is a different kind of "crash". Why does it happen on some services with the "i" icon and not others? We can speculate, but hypotheses require confirmation.
Please explain "sometimes".
Black Hole
May contain traces of nut
Menu >> Settings >> System >> System Information >> System ID = 80BC.7E00 for HDR-FOX and 806C.7000 for HD-FOX. However, I didn't spot it as my "office" unit is a HD-FOX and the HD-FOX crash dump doesn't include the System ID string.
It is odd that the 2000T seems to have the same System ID as HDR-FOX, but I guess that's Humax for you. What does your System Information say?The 2000T dump gives HMX80BC7E and the 5000T - HMX8B0000. I would guess HMX=Humax. As for the rest - I'm sorry I haven't a clue.
Last edited:
EEPhil
Number 28
Oh, FFS you mean I have to go and check
...9150T 3024.0000
2000T 80BC.7E10 (not 7E00)
5000T 9010.7D44
(Aura A31DBE00)
Luke
Well-Knwοn Мember
Browsing https://www.digitalbitrate.com, talkSPORT also looked like a candidate in that it has a Data (DSM-CC) stream. When tried, it produces the commonest blue display with a non-zero AppSID (unlike the Sky channels which displays zero for AppSID).
There is a slight difference to the others in that for talkSPORT "Launch:" is "Dark hour" instead of "Light hour".