Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - srto2

#16
BYOB / Re: BYOB Wired And WiFi dropouts et al.
December 27, 2024, 02:26:19 PM
@raymondjpg

The point I was trying to make was that having done all of the power cycles and reboots of both the Icebox and the router ONLY a normal reboot OR power off reboot of the Icebox restores connectivity.  Just unplugging/replugging the network cable results in loss of connection; rebooting only the router causes any connection to be lost and ONLY rebooting or power cycling the Icebox restores the connection..

The Lenovo M920Q does have MEBX (Ctrl P to activate) and as I said, I followed INTEL's instructions but that failed to help.  I don't think it was ever a thing for this issue anyway. I am still of the opinion that it is a LibreElec driver issue.  As is the painful WiFi. Before using the M920Q as an IceBox it was cheerfully running Win 11 and survived many router reboots, router upgrades, network cable rerouting, the whole nine yards.

I don't have much time to look into this as I am currently very stressed - my other half has rapidly deteriorating dementia.  Apologies if my replies sound a little abrupt.

My only reason for posting in the first place was in the hope that someone might have an answer or could maybe point me to a source of network adapter drivers for LibreElec.

In order to further nail the issue down I'll maybe try a USB to LAN network adapter that might (presumably) utilise a different driver but I have no idea when I'll have time to do so.
#17
BYOB / Re: BYOB Wired And WiFi dropouts et al.
December 24, 2024, 04:46:32 PM
Quote from: raymondjpg on December 24, 2024, 10:59:11 AM
Quote from: srto2 on December 24, 2024, 10:13:22 AMIt presumably is a handshaking issue on the part of the router or my BYOB hardware; Lenovo M920Q.
If we're still talking about wired, I'd be more inclined to be looking at the Lenovo than the router. I have a number of NUCs, various Intel CPU generations, with some of them apparently losing MEBX connectivity at times, typically after bios updates. The 8th gen NUC I use for IceBox BYO is one such device.

MEBX subsystem connectivity can only be restored by removing the power jack and re-connecting after a short while. Rebooting the NUC or power cycling will not do it.

I suggest you try that on the Lenovo. It may trick it into a more consistent successful handshake with the router.
I had never heard of MEBX.  This Lenovo M920Q (i7 8700t) had not experienced this kind of issue when it was running Windows 11.

I was supposed to be preparing for Christmas visitors but I followed your suggestions - with no improvement... Unplugging/replugging the network cable results in no connectivity.

I looked up what Intel had to say, entered the MEBX setup, followed their instructions and dutifully reset the AMT configuration.  Well, I think I did.  Whatever, no change.  I have no idea what it all means anyway.

Now I absolutely have to abandon the quest for a solution until I am not tasked with anything else!
#18
BYOB / Re: BYOB Wired And WiFi dropouts et al.
December 24, 2024, 10:13:22 AM
Thanks guys, a quick response for now...

A different cable and/or a different router port makes no difference. (RT-AX3000/RT-AX58U - Merlin RT-AX58U_3004_388.8_4 F/W)

Rebooting the router also causes loss of connection - Libreelec reports connection "idle".  And my router is set to reboot once a week...

But the router has been rebooting weekly for yonks. And I think the issue started after the 12.1.1 update.  I don't recall noticing the issue before, except the wifi issue of course.

It presumably is a handshaking issue on the part of the router or my BYOB hardware; Lenovo M920Q.

The worst of the problem now seems likely to be caused by the router reboots so I'll turn the reboots off for a while and get back to the issue in a few weeks.
#19
BYOB / BYOB Wired And WiFi dropouts et al.
December 23, 2024, 05:38:26 PM
I know that BYOB  boxes receive no official support.  Thanks for that!

But since the update to 12.1.1 my two BYOB boxes both suffer from (wifi or wired) loss of connection at least once a week.  Prior to the update it was a rarer occurrence. In each case only a reboot re-establishes the connection. I assume this is a libreelec issue. I really haven't yet had the urge to visit the libreelec forums again lately, but I will...

One of the boxes is a "secondary" unit with occasional use, the other "primary" is online pretty much continuously and is a **** pain for it's **** loss of connection.  The other 'secondary" unit no longer gets **** guide updates but happily receives timers - if required...  After looking at the issue with a (believe me!!) jaded eye, I'll reinstall on the secondary unit from scratch - if or when the mood strikes me.

I'm just posting this now because I know that no-one has anything else to do over the silly season, and I doubt that anyone really cares!

Have a good Christmas everyone, and thanks for everything you do!  Cheers!

#20
BYOB / Re: Missing Timers
June 07, 2024, 03:44:24 PM
Quote from: raymondjpg on June 07, 2024, 02:50:45 PM
Quote from: srto2 on June 07, 2024, 02:12:19 PMIn my case it only seems to be repeat programs that are affected.
Have you perchance enabled add a repeat (R) flag to the title on the My Recorders page? That has long been known to interfere with timer creation in IceBox.

If you have, try disabling that, saving, then re-sending all recordings.

Many, many thanks!  Yes I had...  Relatively recently too, I think.  I disabled it for both machines and rebooted.  And the timers have now popped up as they should.  All OK now.

With the state of the world lately, I wish I didn't feel the need to worry about these first world problems...
#21
BYOB / Re: Missing Timers
June 07, 2024, 02:12:19 PM
Quote from: raymondjpg on June 07, 2024, 12:28:20 PM
Quote from: srto2 on June 07, 2024, 11:59:57 AMI have rebooted both boxes several times but timers are still missing.
Another thought. If the issue initially was due to gaps in the EPG, maybe that was fixed by the reboots, and maybe if you resend all recordings to your BYO from My recorders page, they will show up.

Been there, done that too.  No change.  In my case it only seems to be repeat programs that are affected.  Could you be so kind as to try that?  Assuming you haven't already of course...  I even started with no timers at all set on the spare box and got the same result.  Non repeat timers are OK.

This is a frustrating kind of issue but, as I said, I can't be too fussed about it.  I'll set the timers manually on the spare box to see if that works but other than that I'm out of ideas.

There is always iView and SBS on Demand etc if necessary... 
#22
BYOB / Re: Missing Timers
June 07, 2024, 11:59:57 AM
Quote from: raymondjpg on June 07, 2024, 11:22:04 AM
Quote from: srto2 on June 07, 2024, 10:49:55 AMI'm a bit vague regarding when this issue started because these missing timers are of repeats, so I'm not overly fussed - but possibly since the recent minor update....

...Why is it so??  Maybe the way the system is handling repeats?
I think you'll find it's because the missing timers are for programs that are missing from the EPG.

This was the issue that was addressed by the "recent minor update".

At first I was encouraged to see that the update had apparently fixed the issue on my BYO, at least for the five primary SD channels in my area. However this morning I noticed gaps in channel 10 and SBS Food. A reboot fixed the issue with channel 10 but not SBS Food. A second reboot fixed the issue with SBS Food.

So it appears that, while the issue may have been at least partially resolved with the update, it my re-occur, and apparently randomly, in the EPG.

I don't see a need for users to reboot to fill gaps as a long term solution for this issue.
Thanks for that.  But in my case the shows are in the Icebox EPG.  I had to check (!) because I mostly tend to peruse the Ice EPG on my phone or PC rather than on screen.  I have rebooted both boxes several times but timers are still missing.

It looks like the latest bug fix has introduced more bugs?
#23
BYOB / Missing Timers
June 07, 2024, 10:49:55 AM
I'm a bit vague regarding when this issue started because these missing timers are of repeats, so I'm not overly fussed - but possibly since the recent minor update.

That said, from at least 3 June my main BYOB Icebox refuses to accept "QI" and "8 out of 10 Cats" on ABC HD / ABC Entertains and SBS Viceland HD respectively.  I fired up my spare Icebox and set the timers for that too, with the same result.  Both machines are running 11.6.2 with the latest patch.

A check of TVheadend confirms that QI and 8/10 Cats aren't set to be recorded on either machine.

So far as I've checked, all other timers are present and correct.

'My Week" shows the timers are present and correct but they don't appear on either machine.

Why is it so??  Maybe the way the system is handling repeats?
#24
Quote from: TimC on April 21, 2024, 04:06:57 PMsometimes settings that the person who set up the update had for their setup can sometimes end up in the update
I had to read this sentence  a few times!
#25
Getting Help / Re: Remote Control
April 12, 2024, 04:50:02 PM
Quote from: MD on April 12, 2024, 11:54:17 AMAn imminent software update should fix that bug (and some others).
Would it be possible to give us a list of bugs that have been fixed (ie 11.3 to 11.6), bugs about to be fixed (ie 11.6-11.x), and known bugs in the future pipeline?
#26
Quote from: IanL-S on March 28, 2024, 11:18:16 AMI cannot find a link for downloading 11.06 - I am chasing it up with the development team.
https://releases.icetv.com.au/generic/IceBox-Generic.x86_64-1.11.6.img.gz
#27
Getting Help / Re: Weird Freeze/s
November 15, 2023, 10:22:36 AM
For what it's worth, my BYOB (Lenovo i7) has been doing the same,"paused" but unresponsive - presumably sometime overnight, for the last two mornings.  Selecting another channel and then back to the "frozen" channel clears the issue.  A subsequent reboot yesterday did not stop the same effect from occurring this morning.  I haven't looked in depth at logs or for anything software-wise that might have changed.  Yet.
#28
Getting Help / Re: Recording Failures
October 13, 2023, 04:05:57 PM
Quote from: DeltaMikeCharlie on October 13, 2023, 11:30:35 AM
Quote from: srto2 on October 13, 2023, 10:31:31 AMMaybe a time sync error can cause the intermittent hiccup?
Unless your battery is already running low, this seems a bit of a reach at the moment.

I'm not thinking of RTC drift but more an NTP sync delay.  I've seen windows grab delayed or incorrect time sync, not recently, but there was something time critical 10 years or so ago, that I mercifully don't remember now, but I do remember switching to "local" ntp servers to side-step the issue.
#29
Getting Help / Re: Recording Failures
October 13, 2023, 10:31:31 AM
Quote from: DeltaMikeCharlie on October 13, 2023, 06:49:57 AMFirstly, I would check to see how many networks (not channels) you can manually record simultaneously via Kodi.  This should tell you fairy quickly how TVH is actually configured.

If this number does not match your expectations, perhaps TVH has a configuration issue with recognising its tuners.

If this is the case, double-check the link between the 'TV adapters' and the 'Networks' in the TVH Web UI.

http://<IceBox_IP_Address>/extjs.html#

In TVH, there is a chain of data structures that are required for a recording to occur.

A recording takes place on a 'channel'.  A 'channel' can be sourced from multiple 'services'.  Each 'service' originates from a 'mux'.  Each 'mux' comes from a 'network' and each 'network' is attached to one or more 'tv adapters' (tuners).

If you go into Configuration -> DVB Inputs -> Networks, you should see one called 'DVB-T Network'.  In Sydney, I have 60 'Services' and 'Mapped Channels' shown, although your location may be different.

Then go into Configuration -> DVB Inputs -> TV adapters and for all of your 'DVB-T' adapters, ensure that 'DVB-T Network' is included in the 'Networks' field.

If all of this is in order, then assuming that the timer in question gets all the way to TVH on the IceBox and then fails, perhaps enabling debugging/tracing on TVH may be able to provide some insights.

In TVH, you need to go into its Web UI -> Configuration -> Debugging.  If you press the Help button, you can get a list of the subsystems.

I would try logging for 'dvr' to see the timers.  I would also try 'epg' and 'epgdb' to see the EPG changes, although this will be very active and create a lot of log entries.  If an EPG change for the programme in question precedes a recording faulire, it may help narrow down the root cause.

Failing these, 'api' may show when TVH receives timer creation commands from the Ice add-on and 'uuid'/'idnode' may show when timer entries are created/edited/deleted.  'subscription' may also show when tuners are called into service, released or not available for live TV and/or recordings.

Because the Ice TV EPG is fed via XMLTV, it should also be possible for ICE to experiment by creating dummy EPG entries and see if they can force the error to occur.

It has been a while since I looked into how LibreELEC is built, however, I seem to recall that whilst Kodi is relatively up-to-date, it uses a very old version of TVH and perhaps you are encountering a bug that has already been identified and fixed long ago.
Thanks DMC,  Just a quickie here as I have to go out.  Sorry for the long quote too!

I can simultaneously, manually, record from four muxes.  I have 61 services and 61 mapped channels.  I've often had timers set for three muxes (ABC, SBS, Seven) with successful recordings

When the timer failure occurred most recently I shut down the BYOB, logged into ICE and transferred the timer list to my second BYOB.  The second BYOB immediately flagged the same timer errors.

Because boot or resume from suspend has been suggested as undesirable I am looking at NTP server queries to see how long each BYOB takes to get time sync.  There is a burst of four queries each to two NTP (1.* and 3.*) servers at bootup.  Maybe a time sync error can cause the intermittent hiccup?  I might point the NTP servers to 0.au.ntp.org and 1.au.ntp.org as well.

I appreciate what you're doing with TVHE and I would second your suggestion of ICE releasing their add-on if only that it would allow me to use an Rpi permanently .

I'll look at the remainder of your suggestions later in the day.

Regards, Rob
#30
Getting Help / Re: Recording Failures
October 12, 2023, 07:26:43 PM
Quote from: Daniel Hall at IceTV on October 12, 2023, 06:08:23 PMHi Rob,

There are a couple of things to this.

The error message on the website doesn't necessarily mean it was a tuner availability issue, this is just the most common cause when the feature was first introduced so it's hard coded into the website. This just means that the timer was marked as failed at some point.

My current theory is that there is a certain combination of EPG updates that cause this, but I have not been able to track down the exact combination as yet. There are some updates and fixes that are being prioritised at the moment ready for the next batch of IceBox's to arrive so it will likely be a couple of weeks before I will have a chance to try and test all the scenarios to find the one that causes this.
Thanks Daniel,

When I embarked on the BYOB exercise I was originally hoping to implement an RPi solution in order to reduce power consumption.  (About $0.58 per peak kW/h here.) The Pi works well but of course I can't schedule recordings with ICE.  So I have played with the two PC's initially hoping that the ICE plugin (and the server end) would be a little more developed, and I'm still waiting!  Many years of pretty much flawless performance with Topfield and Beyonwiz PVR's sucked me in.

Unfortunately perhaps, my major career was aviation based, instrument landing systems, nav-aids, radio communications and so on, mostly back in the analog days, so my programming expertise is somewhat limited. The BYOB is forcing me to get re-acquainted with Linux though.

Meantime I appreciate what's happening in the background and I'll hang in for a bit longer...

Cheers, Rob