Loading says cf 2.21 but cannot access webif

Luke

Luke

Well-Knwοn Мember
Has anyone got any suggestions how I can get the custom firmware running with the webif on my HDR?

It was on 1.2.29/2.20 and I was trying to change to 1.03.06/2.21.

I presume I must have clicked on RMA instead of "Remove all custom firmware packages and settings" as when I load 1.03.06/2.21 it shows "==RMA==" on the display. When I load the official firmware it dosen’t show ==RMA==.

I’ve toggled between the two loads a few times. DeRMA does not run in either state.
There is no RMA option on the telnet menu.

An attempt to force reinstall displayed the following:

Code: 
Humax HDR-Fox T2 (humax) 1.03.06/2.21
To return to the menu, type: exit
humax# opkg install webif --force-reinstall
No packages removed.
Unknown package 'webif'.
Collected errors:
 * opkg_install_cmd: Cannot install package webif.
 * opkg_finalize_intercepts: Failed to open dir : No such file or directory.
 * rm_r: Failed to open dir : No such file or directory.
 * rm_r: Failed to open dir : No such file or directory.

modinit.log:
Code: 
Humax HDR-Fox T2 (humax) 1.03.06/2.21
To return to the menu, type: exit
humax# opkg install webif --force-reinstall
No packages removed.
Unknown package 'webif'.
Collected errors:
 * opkg_install_cmd: Cannot install package webif.
 * opkg_finalize_intercepts: Failed to open dir : No such file or directory.
 * rm_r: Failed to open dir : No such file or directory.
 * rm_r: Failed to open dir : No such file or directory.
humax# cat /tmp/modinit.log
=== Sat Jan  1 00:00:11 UTC 2000 - modinit - setup_hosts ===========================
=== Sat Jan  1 00:00:11 UTC 2000 - setup hosts ===========================
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
    Interface: [eth0]
    IP: [192.168.0.6]
=== Sat Jan  1 00:00:11 UTC 2000 - complete ===========================
=== Wed Jan 15 19:20:07 UTC 2014 - modinit - ===========================
=== Wed Jan 15 19:20:07 UTC 2014 - diag ===========================
Filesystem                Size      Used Available Use% Mounted on
/dev/root                20.9M     20.9M         0 100% /
tmpfs                    61.0M     24.0K     61.0M   0% /tmp
tmpfs                    61.0M         0     61.0M   0% /media
/dev/mtdblock1            2.0M    524.0K      1.5M  26% /var/lib/humaxtv
/dev/mtdblock2            2.0M      1.2M    796.0K  61% /var/lib/humaxtv_backup
/dev/sda1              1011.4M     37.0M    923.0M   4% /mnt/hd1
/dev/sda2               447.6G      7.2G    417.7G   2% /mnt/hd2
/dev/sda3                 9.8G    170.6M      9.2G   2% /mnt/hd3
eth0      Link encap:Ethernet  HWaddr DC:D3:21:56:14:BF
          inet addr:192.168.0.6  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:762 (762.0 B)  TX bytes:664 (664.0 B)
          Interrupt:16
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  PID USER       VSZ STAT COMMAND
    1 root      1244 S    init
    2 root         0 SW   [migration/0]
    3 root         0 SWN  [ksoftirqd/0]
    4 root         0 SW   [migration/1]
    5 root         0 SWN  [ksoftirqd/1]
    6 root         0 SW<  [events/0]
    7 root         0 SW<  [events/1]
    8 root         0 SW<  [khelper]
    9 root         0 SW<  [kthread]
   10 root         0 SW<  [kblockd/0]
   11 root         0 SW<  [kblockd/1]
   12 root         0 SW<  [khubd]
   13 root         0 SW<  [kseriod]
   14 root         0 SW   [pdflush]
   15 root         0 SW   [pdflush]
   16 root         0 SW<  [kswapd0]
   17 root         0 SW<  [aio/0]
   18 root         0 SW<  [aio/1]
   19 root         0 SW<  [ata/0]
   20 root         0 SW<  [ata/1]
   21 root         0 SW<  [ata_aux]
   22 root         0 SW<  [scsi_eh_0]
   23 root         0 SW<  [scsi_eh_1]
   24 root         0 RW   [mtdblockd]
   25 root         0 SW<  [kpsmoused]
   26 root      1240 S    {rcS} /bin/sh /etc/init.d/rcS
   71 root         0 SWN  [jffs2_gcd_mtd1]
   72 root         0 SWN  [jffs2_gcd_mtd2]
  129 nobody     936 S    /usr/bin/dnsmasq
  135 root       812 S N  /sbin/utelnetd -l /bin/tmenu -p 23 -d -B
  148 root      1244 S    {S90settop} /bin/sh /etc/init.d/S90settop start
  158 root      328m S    /usr/bin/humaxtv
  316 root      1248 S    udhcpc -t 5 -T 10 -p /var/lib/humaxtv/udhcpc.eth0.pid -i eth0
  335 root       840 S    tinyftp -i HumaxFTP -p 0000 -c /media
  376 root      1260 S <  {run-and-gun} /bin/sh /etc/mdev/run-and-gun
  388 root         0 SW<  [kjournald]
  397 root      1260 S <  {run-and-gun} /bin/sh /etc/mdev/run-and-gun
  413 root         0 SW<  [kjournald]
  426 root         0 SW<  [kjournald]
  430 root      1260 S <  {run-and-gun} /bin/sh /etc/mdev/run-and-gun
  485 root      1228 S <  sleep 1
  501 root      1228 S <  sleep 1
  518 root      1252 R <  {modinit} /bin/sh /sbin/modinit
  530 root      1236 R <  ps -w
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
=== Wed Jan 15 19:20:08 UTC 2014 - reset all ===========================
Resetting custom firmware environment.
=== Wed Jan 15 19:20:08 UTC 2014 - rma ===========================
RMA Mode.
humax#
 
Run the 'resetrma' diagnostic from the telnet menu.

For info. it is not necessary to run RMA or "Remove all custom firmware packages and settings" when upgrading the custom firmware.
 
Luke said:
I presume I must have clicked on RMA instead of "Remove all custom firmware packages and settings"
Click to expand...
It's the same thing. That's what you click to clean everything off ready to return under warranty, which then must be followed by installing an official version of the firmware (which then removes the "RMA" display). As xyz321 says, you didn't need to do that, but having done that you can "resetrma" or load official firmware and start all over again.

See entry "RMA" in the Glossary (click).
 
xyz321 said:
For info. it is not necessary to run RMA or "Remove all custom firmware packages and settings" when upgrading the custom firmware.
Click to expand...
I now get the download full webif but ...
Code: 
This may take some time depending on your Internet connection speed.
Please wait..
Collected errors:
* opkg_conf_load: Could not lock /tmp/opkg.lock: Resource temporarily unavailable.
Error retrieving package list from the Internet. Please check your connection
and try again.
Accessing the portal is still OK.

xyz321 said:
For info. it is not necessary to run RMA or "Remove all custom firmware packages and settings" when upgrading the custom firmware.
Click to expand...
Black Hole said:
See entry "RMA" in the Glossary (click).
Click to expand...
The reason I ran it was not because I thought I needed to but because I wanted to try it out and this seemed like an opportunity. I was a bit wrong. :(
 
Loading an official release would have reset the RMA mode for you. In this context, 1.03.06 doesn't count as an official release.

The lock error usually means that a package operation is already in progress and you've attempted a second. If it doesn't clear, reboot and try again.
 
Thanks. I'll try that at the weekend. Its been moved off the shelf for now. Have a good evening.
 
Black Hole said:
It's the same thing. That's what you click to clean everything off ready to return under warranty, which then must be followed by installing an official version of the firmware (which then removes the "RMA" display).
Click to expand...
It is not quite the same thing, RMA mode leaves a lock to prevent the custom firmware reinstalling itself whereas "Remove all custom firmware packages and settings" will allow a new installation of the custom firmware.
HarveyB said:
Can I suggest that a note to this effect be added to the wiki?
Click to expand...
RMA mode should only really be used for returning to the manufacturer. It is not really intended to be used to wipe everything out before a reinstall.
 
xyz321 said:
It is not quite the same thing, RMA mode leaves a lock to prevent the custom firmware reinstalling itself whereas "Remove all custom firmware packages and settings" will allow a new installation of the custom firmware.
Click to expand...
:oops:
 
af123 said:
Loading an official release would have reset the RMA mode for you. In this context, 1.03.06 doesn't count as an official release.

The lock error usually means that a package operation is already in progress and you've attempted a second. If it doesn't clear, reboot and try again.
Click to expand...
Yep that was proabbly it. The first attempt just stalled and so I restarted after waiting a while, but the 'while' was probably not long enough for it.
 
Has anyone else had the remote become unresponsive since custom firmware 2.21? maybe it's just my box and not the software?. I'm running 1.03.06.
 
No, but...

Since I updated both my 'daily used' HDR's to CF2.21, one has experienced a complete freeze. By that I mean completely unresponsive. It wouldn't respond to any key presses on the remote or front panel. The TV picture had frozen but the sound was still playing. I had to do a complete cold boot. I wasn't recording anything at the time (time shift is enabled though so that was obviously writing to the disk, or should have been).

After the cold boot, I placed the HDR in maintenance mode and ran a FIX-DISK. No problems found at all. Not even a CRASH LOG.

It is unexplained for me, I suppose that it can be expected once-in-a-while, and hasn't happened since. It's not happened on my other HDR that is running exactly the same CF and 'Official' FW with the same packages installed.

I didn't bother reporting it here at the time as I thought it was 'just one of those things'. But after reading your post I thought I would mention it. Probably unrelated though.
 
It is just one of those things. I sometimes get a crashed hummytv process (picture freezes, everything unresponsive) if I hit it with too many commands from the remote, eg playing and pausing iPlayer in rapid succession.
 
I am not concerned as I think it's only the second time since I purchased the HDR a couple of years ago. It was my first HDR. One of three.

The funny thing is that I wasn't actually using it at the time. Yes it was switched on and obviously the TS buffer was being filled, but we wern't even watching anything on it as the TV was switched to a different HDMI input. It was only when I tried to put it into standby that I realised it wasn't respnding.

I don't think a cold boot does any harm now-and-again anyway.
 
You must log in or register to reply here.
Back
Top