Posts by Iridium

Quote from Rootz

Ok Thanks.

For local files I'm using wired Ethernet 10/100.

My mini m8s ii have wireless N
N is faster than wired 100mb/s?

I'm afraid you've been fooled by marketing - N is capable of 150/300Mbps but in reality, you'll never get anywhere near that. Is your router in single mode (20mhz) or dual mode (40mhz). If single mode, you'll be lucky to get a link speed of 72Mbps, in dual 120Mbps.

Depending on where your box is located (How far from the router, inside a case, behind the TV etc, the Wifi reception will be reduced - your box also has a very small antenna so speed will also be reduced.

Those figures are only the link speed, NOT what you can expect.

Too see the current link speed from your box ssh into your box and run

iwconfig

To test internet speed run this:

curl -s https://raw.githubusercontent.com/sivel/speedtest-cli/master/speedtest.py | python -

Run them a number of times and see how and when things change.

In my setup, I bought a Wifi extender with ethernet (which bypass the internal wifi) and I get around 48Mbps, on Wifi i'm lucky to get 5Mbps

It would help to know what chip is used - the piface documentation is a little sketchy at best.
It would also help if you could link the install script as that might help.
It may be as simple as adding dtoverlay=i2c-rtc,<chip> to /flash/config.txt but if the chipset is not included in the kernel, then you are out of luck.

Are you sure your host are correctly linked to "LAPTOP" and DHCP isn't changing the IP addresses (It shouldn't due to the lease.. but)

I agree with kostaman. The buffer will only help for slight glitches.

With testing, the maximum usable buffering I could come up (on a Cubox-i4 2G ram) was:

<advancedsettings>
<cache>
<buffermode>1</buffermode>
<memorysize>524288000</memorysize>
<readfactor>20</readfactor>
</cache>
</advancedsettings>

If the source is reliable then look at your Wifi (if using) as that is sometimes the main issue.

Some time ago, I ran a test to monitor the speed differences between SMB and NFS from a server. The difference between the two was negligible.

So it's not the protocol but the setup, which is causing issues. Use the tools available in LE to determine where the bottleneck is.

The only solution I know of is VNC but depending on your architecture, that may not be possible. I know it works with the RPi and X86 but other platforms may not work. (Of course it will require a change to the router to allow remote access)

From your other posts, it seems you're trying to solve a problem remotely!

You can
1) Use "paste" as

cat /storage/.kodi/temp/kodi.log|paste

and use the url
2) You COULD use the Kodi addon "Log Uploader" but it is reported as BROKEN.
3) Use any number of websites like pastebin.com to upload.

1) To access your internal HDD from an external source (work, parents) is a router issue and nothing to do with LE. There is nothing in LE (as far as I know) that can assist.
2) LE requires only what it needs on the SD card and memory, as the OS is loaded into RAM at boot. However /storage is allocated on the drive. So you can allocate /home to another drive if needed.

I can't believe you lost 1TB from an 8TB drive - something doesn't add up as it's just a data drive, so it should be close to 7.9!! TB as LE is on your msata

Therefore the whole drive should be one partition as ext4.

bhennink If you are happy, can you change the title to "[Solved] pinsentry"
TNX

Not too sure what has happened but it was official:
Add-on:PinSentry - Official Kodi Wiki

See Media sources - Official Kodi Wiki - it might do what you want.

Lama Not a lot of help to you, but I'm running Ubuntu 16.04 off of the same M2 SSD and it works a dream -> 3.1GB/s read rate, so Linux/Debian does support it. Maybe something small is missing from LE?.

I'm guessing the Bios has detected it.

Quote from mrremo

vitorp07 I've tried you code. It make no difference.

Iridium Thanks for your comment. But to increase the buffer works great with all other video stream addons which i use, except SRF Podcast.

I don't know what your setup is but I have a Cubox-i4 with 2GB ram and find that a 500MB memorysize and 20 readfactor works Ok. Anything more and LE tends to crash.
So try 25% of your total free memory as a maximum. If that doesn't work, then back to the drawing board.

I found that playing files over my local wifi network at 300Mbps was not enough. I gave up and bought a 1Gb powerline and all my troubles went away.

I have a feeling you are attempting a "shotgun" approach to changing parameters. Change ONE thing at a time and see if it makes a difference.

If your WIFI is temperamental, then no amount of buffering is going to help - sort your WIFI out first or switch to ethernet.

Run

dmesg|paste

and post the url.
Usual reason for unexpected unmounting is a power issue. How are they powered and what type of drives?

To check cpu usage, install LE system-tools and run nmon, this will give a true CPU value.

4K and HEVC will use much more CPU than normal files.

Try playing "normal" files DVD, x264 and see if you have a CPU issue.

It might help to give more details about your Shuttle PC 286 as Mr Google doesn't know much about it.

I guess this is because you have upgraded from Kodi 16 (Confluence skin) to Kodi 17 (Estuary skin).

On the main screen - go to the "cog wheel" symbol, to the right of "power off" symbol.
Go to system settings -> Audio and change it there.

Qmander I'm running LE 7.90.010 on a Cubox-i4 booting off an esata SSD to a LG TV and don't have any issues with black screen nor journal messages.

Are you getting ERROR: SetString: error writing /sys/class/graphics/fb0/mode in kodi.log when changing resolution?

Are you booting from the esata? If not, try enabling esata hotplug thread-4897.html and see if that helps.

Also I would check that you're not running out of disk space. Also check the size of the journal with

journalctl --disk-usage

. If above 10M try clearing it with

journalctl --vacuum-size=1M

. You could also clear the whole journal with =0M.