• The forum software that supports hummy.tv has been upgraded to XenForo 2.1!

    This upgrade brings a number of improvements including the ability to bookmark posts to come back to later. Please bear with us as we continue to tweak things and open a new thread for any questions, issues or suggestions in Site/Forum Issues.

[boot-settings] Apply settings during boot

prpr

Well-Known Member
If it was a recording problem why would rebuilding database cure it albeit temporarily
I don't know, seeing as we don't really know exactly what the Humax software does in relation to this or how it works.
I was just going on my (one) personal experience of this problem.
 

Border

Member
Download the system flush update from https://wiki.hummy.tv/wiki/Firmware_Downloads copy it to a USB memory stick and apply it to the Humax like a normal software update
I tried that and it didn't work. I had a few wizard restarts (at least 4) since then.

This package doesn't appear to work as intended on my box, I installed as Content Sharing keeps turning itself off!
Do you use WiFi or wired connection?

Easily fixed with tunefix.

Did anyone ever try my suggestion in post #75?
I have read post 75 and think it is worth a try. I use WiFi and I think my router handshakes with the WiFi dongle and allocates it's address before the hdr is able to handshake with the dongle This may be causing me some problems.

I have had problems with start up, and wizard rescanning and reinstalling channels.( I don't want the children to access the adult channels). I tried tunefix but have multiple region signals.

it did not affect as far as I can recall the content share setting.

I have tried manual address and fixed address (via router) but my suspicions are that the wizard restart occurs when there is an IP address conflict between the hdr and some other device on the network.

When the box starts which is on first DLNA index or content sharing? I suppose that is where this tread lead to. When shutting down if the DlNA was automatically reset would it take too much time to reindex on reboot?

Did anyone ever try my suggestion in post #75?
I'll let you know how I get on
 
Last edited:

Black Hole

May contain traces of nut
I think my router handshakes with the WiFi dongle and allocates it's address before the hdr is able to handshake with the dongle
I don't. The WiFi link is a physical layer and establishes point-to-point communications independent of the TCP/IP traffic that crosses it. The IP address negotiation then takes place between the Humax and the router using the WiFi as a transport mechanism no different than a piece of wire. There may be a problem if the WiFi has not established the link by the time the DHCP request is issued by the Humax.

What you need to do is go into Menu >> Settings >> System >> Internet Setting >> Configure LAN, set "DHCP" and click Apply. The WiFi should be up by then, and the fields get populated by the DHCP response from the router - this ensures you have the right parameters. Now you change the DHCP field to "Manual".

Next time you boot up, the Humax will already have the correct parameters without requiring a DHCP which fails if the WiFi hasn't set up.

That will probably be sufficient, the router will keep the same IP address for the Humax's MAC. However, you could go into the router settings and set that IP on infinite lease, or allocate an IP address outside the DHCP pool (and manually set the same IP on the Humax).

You should also install the wireless-helper package.
 

prpr

Well-Known Member
I think my router handshakes with the WiFi dongle and allocates it's address before the hdr is able to handshake with the dongle
It doesn't work like that. As BH said, although the bit about "problem if the WiFi has not established the link by the time the DHCP request is issued" is wrong.
I tried tunefix but have multiple region signals.
Tunefix supports multiple regions (with caveats).
 

Black Hole

May contain traces of nut
although the bit about "problem if the WiFi has not established the link by the time the DHCP request is issued" is wrong.
In what way? The Humax firmware doesn't retry DHCP, so if the link isn't up the box ends up with default (wrong) IP details. I see this all the time when I visit my supported user: if I have my phone hotspot turned on when the HDR boots, it links up fine. If I turn the hotspot on later, the WiFi links up but the HDR is unreachable.

Edit: actually, thinking back there's something not right about that. I have the HDR set to manual, so DHCP shouldn't be the problem - and yet the WiFi links up without necessarily establishing an Ethernet link. I have wireless-helper installed. This warrants further investigation (when/if I get the opportunity).
 

Border

Member
Did anyone ever try my suggestion in post #75?
Thank you (I think).....
Humax crashed again but, hurrah!!, no wizard reset. However in one of the logs there was the following entry :

Boot log says last modified Wed Nov 16 12:35:01 2011 (over 7 years ago???)
And the first 2 lines state :


/var/lib/humaxtv/var/lib/humaxtv/mod/bootstrap.d/setdlnaname: Next DLNA Server Name is now "**** ".
mod/bootstrap.d/setdlnaname: Matched: entry 3 "1.02.32" for process 419.
Server name asterisked out but there were a few spaces included between quotes after the server name
I can't find an exact time for the crash

activity log
315818/02/2019 21:51:05 - Scheduled --- Auto Update --- @ 1550550600
315718/02/2019 21:49:08 - System booted (Front panel button).
315618/02/2019 04:20:06 - System booted (Scheduled event).
I thought I had autoupdate disabled ... I have checked schedule and no autoupdate in schedule.
 

Matthew

Member
Possibly you have a corrupted recording that is upsetting DLNA. Finding it might be tricky though.
Thanks for the pointer, I have an idea now of what may be the cause (in my case anyway) as I stated elsewhere the IRS signal provided here has very poor quality (though the measure on the Humax is either 100% or 0% so not a guide) the time when we stopped getting constant 'Content Share Off' coincides with my fitting an aerial, though the levels were low quality was good, I suspect the low levels (it was borderline at around 35dBuv) caused the recurrence, adding an amplifier to correct that has meant no further recurrence so far! :)
 
Top