With beta packages enabled,...I've removed the 1.20 version from the repository - it isn't crashing any of my three boxes though so I don't know what's going on yet.
diag fix-flash-packages
removes and then fails to re-install ir....
Re-installing ir
Removing package ir from root...
Installing ir (1.20) to root...
Downloading http://hpkg.tv/hdrfoxt2/beta/ir_1.20_mipsel.opk.
Collected errors:
* opkg_download: Failed to download http://hpkg.tv/hdrfoxt2/beta/ir_1.20_mipsel.opk, wget returned 8.
* opkg_install_pkg: Failed to download ir. Perhaps you need to run 'opkg update'?
* opkg_install_cmd: Cannot install package ir.
...
wget -U '' http://hpkg.tv/hdrfoxt2/beta/ir_1.19_mipsel.opk
opkg install ir_1.19_mipsel.opk
# or, reverting beta,
wget -U '' http://hpkg.tv/hdrfoxt2/base/ir_1.17_mipsel.opk
opkg install ir_1.17_mipsel.opk
Because /mod/var/opkg/beta still refers to 1.20 even though it's been removed. The file needs to be rebuilt when packages are removed, but it hasn't been.With beta packages enabled,diag fix-flash-packages
removes and then fails to re-install ir.
Unfortunately we are dependent on @af123 for updates and he has been largely out of action since JulyBecause /mod/var/opkg/beta still refers to 1.20 even though it's been removed. The file needs to be rebuilt when packages are removed, but it hasn't been.
I guess we can hope for 1.21 sometime, as alluded to back in July.
All I know is that he has been in hospital but it wasn't COVID-19,Nothing serious I hope.
Oh shit. I thought I would see what happens if I remove the opkg-beta package and then run fix-flash-packages... bad move. It stripped out my beta WebIF and didn't reinstall.With beta packages enabled,diag fix-flash-packages
removes and then fails to re-install ir.
00::
in the map file. The humaxtv.log file says:Initialising IR3 v1.19
IR3 debug: 1
IR3 Mode: 1 (0x1000)
IR3 Options: 0x18
IR3 - Loading custom keymap.
Read 152 bytes from map file.
IR3 map line: [00::]
Parsed [00] []
Not mapping [0].
Humax3# cd /mod/boot
Humax3# cat ir3.map
00:00:POWER <<<<<<<<<< THIS ONE
00:00:STANDBY <<<<<<<<<< AND THIS ONE
02:02:SOURCE
03:03:ONE
04:04:TWO
05:05:THREE
06:06:FOUR
So far as I can see, those are just duplicate entries.Code:00:00:POWER <<<<<<<<<< THIS ONE 00:00:STANDBY <<<<<<<<<< AND THIS ONE
Thanks for that.wiki said:When 'Ir' is installed, it is possible to 'lock out' the power off function by creating a file called /tmp/.irhold, then it won't be possible to power off the Humax using the remote
#!/bin/sh
touch /tmp/.irhold
I think the issue here is that /tmp is in RAM (and recreated fresh each boot), as opposed to /tmp just being a parking space on HDD. Other parts of the file system are in Flash and read-only.Pardon me for being stupid. But isn't every file in /tmp temporary and could be deleted on next reboot?
Thanks once again. Because the Humax remembers where it last was, the button will only work first time around. So I thought to add it as a start-up sequence, which would mean that Media would default to that after reboot. I could not implement/test that, as one has to name the macro "root" and I cannot use 'r' as a character in the filename; 'r' clicks the blue button on the virtual remote instead. I could not figure out how to rename a macro.
Edit: Windows 10; tried on Firefox and on Edge.