Possibly malfunctioning h7s

[ronand]

If its a faulty/buggy plugin causing the problem how is it a fault of the box? Admittedly I don't use a lot of extra plugins as it is mainly for DVB-S/T viewing and some media playback. I wouldn't waste my time with heavily compressed IPTV video and poor audio and that is where most of the crap plugins are used. There have been no complaints on this forum about low memory on this box despite your claim of being a flood of it on the web.

[chrcoluk]

It wasnt hard to google for it, I apologise if you are unable to find the reports, you do seem to be very defensive, instead of helping to identify things, you in a "there is no problem, it is you" mode.

I am not the one blaming it on a plugin either, there has been assumptions it is a plugin but without any kind of diagnosis to lead to that.

Just to 100% and knock this theory dead, the box had the freeze problems when no IPTV was used on the box. There is no IPTV used on this box right now either, I am testing on freesat tv.

As to whether the ram is enough, well yeah we could all only use these box in pure stock configurations, but then the question why not just use a standard sky tv box? You opening a huge cvan of worms with these defensive statements.

Now if you want to help and contribute to the discussion at hand then I appreciate your help, but if you think its down to some poorly coded plugin that isnt written to work in a tiny amount of available memory then please post the substance of that from the information I have provided, thank you.

I am open to all outcomes here, it could be a rogue plugin with a memory leak (I have said as such), it could be faulty hardware, it could be bad software configuration, it could be bad drivers. This is the basis of testing and diagnosing things. I dont come to assumptions because those assumptions are convenient.

[ronand]

I feel selling a device with only 1 gig of ram in 2021 is a bit questionable, the manufacturers of this device probably should rethink that one.

If you wanted/needed more RAM you should have shelled out for it in the first place. Its a budget/low end 4K receiver. Most of the boxes around the £100 mark have 1GB RAM and some have less. The £200 and upwards boxes have 2/3/4 GBs - there obviously has to be some reason for the price difference. You wont get a Merc for the price of a Ford Cortina I'm afraid.

[ronand]

Its hard to know what the problem is when you haven't provided a single log. Indeed the first test is to run the receiver in a very basic state on FTA TV - no additional plugins or softcams. Disconnect the hard drive and remove any USB device. If it is still freezing then it would more likely be a hardware problem rather than a memory problem.

[chrcoluk]

If you wanted/needed more RAM you should have shelled out for it in the first place. Its a budget/low end 4K receiver. Most of the boxes around the £100 mark have 1GB RAM and some have less. The £200 and upwards boxes have 2/3/4 GBs - there obviously has to be some reason for the price difference. You wont get a Merc for the price of a Ford Cortina I'm afraid.

I accept that view, I perhaps misjudged that the ram would be enough, and if I do diagnose that I need more ram rather than it been a rogue plugin or bad configuration I may well buy a box with more ram.

If I understand right plugins are enigma plugins so there usage would fall under engima? or am I incorrect on that one.

[chrcoluk]

Its hard to know what the problem is when you haven't provided a single log. Indeed the first test is to run the receiver in a very basic state on FTA TV - no additional plugins or softcams. Disconnect the hard drive and remove any USB device. If it is still freezing then it would more likely be a hardware problem rather than a memory problem.

I am open to doing that when this week is up. I want to finish this week first, but then I can remove the hdd and any usb sticks, only things connected, hdmi, power and sat feed cables. Am I ok to delete all plugins in the plugin screen? So effectively running with none at all.

There has been no softcam on here for a long time unless one is lingering somewhere.

[ronand]

Don't start deleting stuff. It may be a problem with your current setup so we need to eliminate that. Install a fresh image in one of the other multiboot slots leaving your current setup intact and just set it up for FTA TV from scratch - dont restore any settings.

[chrcoluk]

Whats the best way to do that, if I use the usb boot image, will that pick a unused slot or let me pick, or should I be using the image manager like I did before?

[ronand]

Use the image manager to download the latest 5.4 image and flash it - it will ask you which slot you want to use.

The purpose of all this is to see if the box is stable (ie the hardware is ok). If it runs fine for a few days then the box should be fine and you can start adding stuff back in stages to see what actually causes your problem.

[lincsat]

I've joined this thread as I'm seeing a similar issue, the RAM is almost full and on boot the box wants to only use swap on /dev/mmcblk0p7. I do have several apps and plugins loaded and I understand that I should really have a box with more RAM but am trying to make the best out of what I have.

I've generated swapfiles on both the USB and HDD of varying sizes from 128Mbit to 1Gbit and tried various entries in fstab. On boot, the system generates a new entry in fstab for a swap on /dev/mmcblk0p7 and uses that by default.

Is there a way of stopping the system generating a new entry for the swap in fstab or giving the /media/usb/swapfile a higher priority and is it worth increasing the swappiness? Be gentle, I'm a Linux novice

[twol]

I've joined this thread as I'm seeing a similar issue, the RAM is almost full and on boot the box wants to only use swap on /dev/mmcblk0p7. I do have several apps and plugins loaded and I understand that I should really have a box with more RAM but am trying to make the best out of what I have.

I've generated swapfiles on both the USB and HDD of varying sizes from 128Mbit to 1Gbit and tried various entries in fstab. On boot, the system generates a new entry in fstab for a swap on /dev/mmcblk0p7 and uses that by default.

Is there a way of stopping the system generating a new entry for the swap in fstab or giving the /media/usb/swapfile a higher priority and is it worth increasing the swappiness? Be gentle, I'm a Linux novice

What does swapmanager show in vix plugin…… if they are named swap###### should find them

[lincsat]

It shows manufacturer defined and won't let me change it

swap.jpg

[twol]

It shows manufacturer defined and won't let me change it

swap.jpg

what does it show in debug log when the ViX plugins are initialised - should list all found.

[twol]

deleted ,,,,,,,,,,,,,,,,,

[twol]

@Lincsat ... can you plugin the attachment ( /usr/lib/enigma2/python/Plugins/SystemPlugins/ViX ) and attach debug log --- might also give you some additional options!! BUT !! do not try deleting mmc swap!
It could be mmc swap is last in list and that's why its picked.... so need to see debug output.