The DEV's can have mine to work on as long as it's sent back.
If you do long term tests, and provide error log files, it would help dev's like escalade a lot.
The DEV's can have mine to work on as long as it's sent back.
If you do long term tests, and provide error log files, it would help dev's like escalade a lot.
How do you start autofs? What's the content of the config files? If it doesn't run in the background (demon mode), we can't expect a re-mount.
Also looking into using AutoFS, as it seems people claim it can handle this sort of situation better.
Does it run as a demon? If yes, you should see it with the "ps -A" command. In that case there is a chance to configure it for re-mount.
You could write a python script, started from autostart.sh, which automatically mounts / re-mounts your CIFS.
Sounds like an add-on error, which does a wrong key re-direction at first press. Try what happens when you uninstall the add-on. You actually don't need an add-on for key mapping, because you can manually create custom keymap files.
2019-04-27 12:07:16.007 T:1937639824 NOTICE: load skin from: /storage/.kodi/addons/skin.aeon.nox.silvo (version: 7.0.1)
2019-04-27 12:07:17.759 T:1937639824 WARNING: Skin has invalid include: skinshortcuts-template-widget1
2019-04-27 12:07:17.759 T:1937639824 WARNING: Skin has invalid include: skinshortcuts-template-widget2
Try the default skin.
I have a BRIX which uses Intel the addon HDhomerun freezes
I know.
You already had issues with the add-on on RPi, so I don't think it will be a fix for you. Here is the quote about Intel API:
Quote from Kodi 18.2 Release NotesVAAPI on Intel has gained some corrections for interlaced content that toggled interlaced flags during playback, and therefore caused stutter by reconfiguring the decoder.
Are there issues with the stability of 9.0.1?
Just to reconsider upgrading from 8.2.5 or wait until 9.0.2 or next iteration considered enough stable.
Depends on your hardware. If you have an RPi like me, you can safely update to 9.0.1. If you have an Intel, at least one issue (video stuttering) will be fixed with 9.0.2, so you better wait for that version.
I have no idea what you're trying to say there. What;s possible?
It is possible that a BIOS does not allow to install an OS from an external (USB) source device to an external (USB) target device.
That was my thoughts KODI it self has always been solid its the addons which makes it unstable. Been with KODI since the beginning of XBMC had problems with Raspberry but the size of library always showed lack of memory is why I went with a NUC
Yes, it's sad, you bought new hardware to fix it.
Maybe your library so large that HD HomeRun developers don't test this scenario very well. Hopefully they'll give you hints, how to solve it. Without a debug output of the app, we really can't do anything here.
Are you sure? Because I've done exactly that on plenty of pc's over the years (openelec and libbreelec) and not many of them are what I'd call remotely modern.
No, I only did external -> internal (IDE) installations on older BIOS PC's. But BIOS'es can be different, so it's possible. Let's wait for his answer.
The output is fine, no need to expand any memory. I think the app of your HD HomeRun could be bad. You should ask those guys (see forum link above).
Using Putty cat /etc/fstab shows empty
OK. It could help to see the output of "free -m" and "df -hT" shortly before it freezes (like after 50 min. or so). Maybe we can find out where most memory is needed.
I don't see relevant errors at the log file. The freeze sounds like a memory overflow. The RAM of the Gigabyte NUC should be large enough (still expandable by a swap file, if necessary).
Maybe it's the size of tmpfs. I can't change it on my RPi, but LE on PC is maybe different. Can you post the output of "cat /etc/fstab" please? That's the place to change tmpfs size on a standard Linux. When it's empty, we probably can't change it from there.
PS: A couple of days ago I guided another user, who installed LE from external to external device. So, I know LE is able to do this on modern PC's, but on most older PC's the BIOS is unable to do this. Take into account that old USB interfaces are usually slow, and an OS at such an interface will run slowly, too.
I'm using a 350gb hard drive, hooked up on a usb adapter I use to read hard drives and program them for pcs. It reads like a usb drive! But the libreelec creator won't pick it up, no matter how it's formatted 32gb 64gb or full 320 will recheck ntfs or fat only other factors that I can think of! Otherwise I should be able to program the drive and install it straight to the pc and run like a os
You said you can boot from USB, but it doesn't mean you can install from external to external device.
It looks like you want to use a modern USB HDD with an old PC. I think that doesn't works, because of the old PC's firmware (BIOS). Find a way to install an HDD internally (maybe use an adapter, if possible). I bet an internal drive will be detected by the LE installer.
Can you describe what installation image you are using, and what happens when you boot the image from stick? If it's a real installer, there should appear the option to install on your HDD.
PS: If you don't see any target drives to install, reformat your HDD with a tool like "GParted Live". You can run it from stick, too. It's interesting whether the tool can "see" your HDD while running from stick.
The result should be a single, error-free partition (ext3 for example) with no boot flag set. Try to run the LE installer on that setup.