1.02.28 (CF 2.11)

Hi AF, I can't seem to get Undelete to work, I tried Force Re-install, but I got an error, then if I try to remove I get the following:

>>> opkg remove undelete

Removing package undelete from root...

No packages removed.

Collected errors:

* pkg_run_script: package "undelete" postrm script returned status 1.


I tried deleting a previously watched recording and it doesn't go into the undelete folder.

Any ideas?
 
Try again without capitalising Undelete
(your browser is probably doing that automatically!)
 
Thanks af123

Got it installed this morning. Had some problems with portal-xtra1.
It wouldn't run. Tried to force a re-install which made no difference and a restart.
Tried uninstalling it - it wouldn't uninstall rebooted again and it works.
 
hi this is going to sound weird but could someone pm then email me the new
1.02.28 (CF 2.11) fw

as i get online through a broadband dongle that blocks zippyshare thanks in advance :)
(or up it for me on here)
 
Web interface version: 0.9.12-5
Custom firmware version: 2.11
Humax Version: 1.02.28

Great work af123, thankyou!
 
I installed the custom firmware 2.11 on Humaz 1.02.28 and when I went to the webif in my browser it showed the following error in a bar on the screen:

Runtime Error: /mod/webif/lib/epg.class:395: no such table: epg.epg in procedure 'epg' called at file "status.jim", line 85 at file "/mod/webif/lib/epg.class", line 395

What's this all about?
 
Owen Smith said:
Runtime Error: /mod/webif/lib/epg.class:395: no such table: epg.epg in procedure 'epg' called at file "status.jim", line 85 at file "/mod/webif/lib/epg.class", line 395

What's this all about?
Click to expand...

It just means that the custom firmware hasn't built an EPG database that it can use yet. It will need an additional reboot to trigger that process. Thanks for the report, we can improve that behaviour for future releases.
 
af123 said:
It just means that the custom firmware hasn't built an EPG database that it can use yet. It will need an additional reboot to trigger that process. Thanks for the report, we can improve that behaviour for future releases.
Click to expand...

Yes this error has gone on subsequent reboots.

However looking at the modinit.log contents it looks like the NTP client isn't working:

Code: 
=== Setting clock === /mod/etc/init.d/S90ntpclient: line 26: date: not found pool.ntp.org: Unknown host === complete

This seems to happen before the wireless network has setup (Humax dongle), so no wonder it fails. Full log is (would be more readable if it contain linefeeds!):

Code: 
>>> Contents of /var/log/modinit.log 5.95 KiB === diag ================================================= Filesystem Size Used Available Use% Mounted on /dev/root 16.4M 16.4M 0 100% / tmpfs 61.0M 28.0K 61.0M 0% /tmp tmpfs 61.0M 0 61.0M 0% /media /dev/mtdblock1 2.0M 516.0K 1.5M 25% /var/lib/humaxtv /dev/mtdblock2 2.0M 1.2M 776.0K 62% /var/lib/humaxtv_backup /dev/sda1 1011.4M 41.2M 918.9M 4% /mnt/hd1 /dev/sda2 447.6G 137.7G 287.1G 32% /mnt/hd2 /dev/sda3 9.8G 725.3M 8.6G 8% /mnt/hd3 eth0 Link encap:Ethernet HWaddr 00:03:78:B9:2C:5B inet addr:192.0.2.100 Bcast:192.0.2.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 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:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.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) wlan0 Link encap:Ethernet HWaddr 00:1F:1F:C8:AD:F3 inet addr:192.0.2.200 Bcast:192.0.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5 errors:0 dropped:0 overruns:0 frame:0 TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:972 (972.0 B) TX bytes:1360 (1.3 KiB) PID USER VSZ STAT COMMAND 1 root 1248 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 SW [mtdblockd] 25 root 0 SW< [kpsmoused] 27 root 1244 S {rcS} /bin/sh /etc/init.d/rcS 73 root 0 SWN [jffs2_gcd_mtd1] 74 root 0 SWN [jffs2_gcd_mtd2] 128 nobody 936 S /usr/bin/dnsmasq 133 root 812 S /sbin/utelnetd -l /bin/sh -p 23 -d 155 root 1252 S {S90settop} /bin/sh /etc/init.d/S90settop start 202 root 352m S /usr/bin/humaxtv 303 root 0 SW [RtmpTimerTask] 304 root 0 DW [RtmpMlmeTask] 305 root 0 SW [RtmpCmdQTask] 324 root 1096 S tinyftp -i HumaxFTP -p 3844 -c /media 340 root 0 SW< [kjournald] 366 root 1248 R < {run-and-gun} /bin/sh /etc/mdev/run-and-gun 372 root 1248 S < {run-and-gun} /bin/sh /etc/mdev/run-and-gun 380 root 0 SW< [kjournald] 383 root 1248 S < {run-and-gun} /bin/sh /etc/mdev/run-and-gun 385 root 0 SW< [kjournald] 401 root 1328 S < sleep 1 414 root 1248 S < {run-and-gun} /bin/sh /etc/mdev/run-and-gun 415 root 1248 R < {run-and-gun} /bin/sh /etc/mdev/run-and-gun 416 root 1248 R < {run-and-gun} /bin/sh /etc/mdev/run-and-gun 417 root 1248 R < {run-and-gun} /bin/sh /etc/mdev/run-and-gun 421 root 1252 R < {modinit} /bin/sh /sbin/modinit 428 root 1336 R < ps -w Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.0.2.0 * 255.255.255.0 U 0 0 0 eth0 192.0.2.0 * 255.255.255.0 U 0 0 0 wlan0 === reset_all ============================================ === upgrade_bootmod ====================================== === setup_directories ==================================== === create_rcS =========================================== === migrate_bootmod ====================================== === setup_hostname ======================================= === setup_hosts ========================================== Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.0.2.0 * 255.255.255.0 U 0 0 0 eth0 192.0.2.0 * 255.255.255.0 U 0 0 0 wlan0 Interface: [wlan0] IP: [192.0.2.200] === run_init ============================================= Loading config file /mod/etc/mongoose.conf Anacron 2.3 started on 2012-06-28 Normal exit (0 jobs run) === Setting clock === /mod/etc/init.d/S90ntpclient: line 26: date: not found pool.ntp.org: Unknown host === complete ============================================= === setup_hosts ========================================== Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0 default 192.168.1.254 0.0.0.0 UG 0 0 0 wlan0 Interface: [wlan0] IP: [192.168.1.71] === complete ============================================= 41086 78356.063 63984.0 34.2 606132.9 60867.3 0 41086 78366.776 93164.0 33.1 42230.4 6912.2 0 41086 78376.873 64191.0 46.6 38093.3 61172.5 0 41086 78386.966 46706.0 61.0 28614.5 52917.5 0 /mod/etc/init.d/S90ntpclient: line 26: date: not found
 
Ignoring the date: not found messages which are a harmless error in the package, the NTP client process should try to set the clock five times at 10 second intervals following boot - by which time the wireless should have come up. It does wait until the Humax software has indicated that the interface is up but it does that prematurely for wireless without DHCP.

(btw, if you wrap the extracts with [code][/code] tags, then it makes it easier to read them : )
 
af123 said:
Ignoring the date: not found messages which are a harmless error in the package, the NTP client process should try to set the clock five times at 10 second intervals following boot - by which time the wireless should have come up. It does wait until the Humax software has indicated that the interface is up but it does that prematurely for wireless without DHCP.

(btw, if you wrap the extracts with [code][/code] tags, then it makes it easier to read them : )
Click to expand...

I'm using wireless with DHCP so based on what you say above the Humax should be indicating the interface is up at the correct time. Maybe the DNS lookup doesn't complete quickly enough the first couple of times?

So how can I tell that the NTP client has in fact set the time correctly? The client doesn't appear to create it's own log file (unlike other packages) and the lines in the general log only tell me about NTP failures. I can't login in and request the general status of the NTP sync because it isn't running ongoing sync like a Unix box normally would..

I don't know what you mean about [code][/code] tags to wrap the extracts, how would this successfully wrap them onto multiple lines? I looked for something to search and replace for in a text editor to put some linefeeds in but couldn't find anything. Can't the custom firmware create the log with each item on a line of its own rather than a great slab of text?

EDIT: figured it out, see above posting. Not much of an improvement for the full log, produces a mostly empty box with a long scroll bar.
 
done, just wacked .28 official on then the new cfw and all looks hunky dory.

I didn't even know there was a youtube problem until ya few days ago, wife was looking to put some nursery rhymes on. So i turned to hummy.tv, where else!
 
First post, although I have been following and using 1.02.22 _ various CF issues for 6 months or so.

Problem is, I didn't get the update quite right...
Was running 1.02.22 + 2.11
Thought that auto update was turned off... it wasn't, so got an over-the-air for 1.02.28 without running prepare_for_upgrade first.
Anyway, what could I do but just put put 2.11 (for .28) on, and most seems OK
- box reports 2.11 on its display at start
- web-if works.
- can access my NAS drive via the storage USB directory
- can access Humax directories from Windows Explorer (samba?)
- can access the webif via the Humax's hostname (rather than just its IP).
but some are not working
- undelete
- redring
They are present on the settings page, but do not appear to be functioning.
I have performed a couple of on-off cycles and a couple of complete power-downs.
I have also gone to the web-if settings page and hit the pakages "update" button

Checked the installed packages page, I believe that these are the packages that I installed (obviously a lot of other dependent packages are also installed)
- auto-unprotect
- network-shares-automount
- nicesplice
- redring
- stripts (installed, but not really tried using it yet)
- undelete
- unencrypt
may have missed some (which package publishes a hostname for the Humax?)

Sorry, waffling on now... any suggestions (if anyone can remember the question)?





I guess the question is something like this...
What does prepare_for_upgrade do? Since I can't find what it does, I cannot work out what else may not be working and what I should do to fix it.
In this case, I might just try uninstalling undelete and re-installing it.

BTW, I am semi competent with Linux, so a few pointers may get me started in the right direction. But I must admit to sometimes getting lost in the Humax directory structure as I am more familiar with the simpler PC file structure rather than the slightly more complex cross-mounted layout that you get with embedded processors.
 
You must log in or register to reply here.
Back
Top