Recent content by /df

So it could be possible to make the box's dnsmasq your DNS (proxy) server. Some tidbits: setup_hosts() in /sbin/modinit creates /tmp/hosts by appending /mod/etc/hosts to a base list with localhost and the box's name, and this is (via symbolic link) what the system uses as /etc/hosts. The...

dnsmasq, which can act as a static DNS and perhaps proxy the ZeroConf names, is already running, isn't it? It was used to redirect iPlayer requests when the Humax app broke a few years ago. The proram documentation is informative.

That's a different problem: https://hummy.tv/forum/threads/start-up-fails-when-hdd-connected.10164/ If you didn't have that problem, you'd be able to format the disk on the box. That's the way to go. To format the disk elsewhere, you'd need a PC that can write filesystems in ext3 format, for...

2025-05-05 is needed for YT now ... ... and it's there!

Combining the undocumented 30s timeout for the I-plate invoked from Info combined with the documented configurable timeout for channel switching makes it edgy. These could have been separate timers, one overriding the other, rather than accumulating. This case is also interesting because Info...

See https://hummy.tv/forum/threads/adding-srt-subtitles-to-a-humax-video-file.10491, especially the linked https://hummy.tv/forum/threads/youtube-dl-download-files-from-youtube-com-or-other-video-platforms.8462/post-147408.

So, this behaviour is in fact (would it be unfair to say "surprisingly"?) just as documented and indeed what I can observe. Two edge cases: the timeout accumulates, so that after quickly changing channel up, then down, say, with timeout 15s, the info bar is shown for ~30s invoking the info bar...

You'd think so, but my unsupported recollection says otherwise. But I'm not sure what "recent" change might be responsible. Maybe some CF package, eg, one that hooks the Humax blob? @xyz321? I see the same thing on the HDR too. The name INFO_DISPLAY_TIME is used in the blob and looks like the...

I've noticed that the Info-bar timeout doesn't appear to respect any timeout value (Off, 1-20s) set in Menu>Settings>Preferences>Screen Display>Info Display Time. Rather, it's always ~30s. Is this happening for anyone else? I could swear that quite recently the Info-bar used to disappear too...

It's quite an extensive update, so it needs a new package version. You could upgrade to the 2025.04.01 code, which should still work, by applying this 1-line change.

2025-04-08 is needed for YT now.

Is the improved wireless-helper package helping now?

There doesn't seem to be a specific thread for the epg package (also, the forum doesn't support searching for TLAs). This output was shown today in the package upgrade dialog: >>> opkg upgrade epg Upgrading epg on root from 1.3.0-1 to 1.3.0-3... Downloading...

Uncommanded resets typically don't appear as crashes. While the Humax s/w is running, apparently one or more of the databases in use is trashed, possibly a flash storage issue, or possibly just Humax s/w. The Humax s/w continues to run, though strange effects may be seen. The next start fails...

Plainly it's not ideal, verging on POSSLQ-exclusive. In due course I could add that sequence to the remote start-up sequence or perhaps organise some CF trickery to send the commands. Or identify which component has gone off-spec and replace it. Could the matching item be in a sacrificial Humax...