Which NFS version is your NFS server using?
AFAIK, nothing in the NFS department has changed, going from 8.2.x to 8.2.4.
Which NFS version is your NFS server using?
AFAIK, nothing in the NFS department has changed, going from 8.2.x to 8.2.4.
Wifi works fine for me on my RPi3B+. Perhaps the new RPi is a bit allergic to your router?
Please use Pastebin.com - #1 paste tool since 2002! next time if you want to share logs, snippets or other long texts.
We prefer not to litter our forum database with unnecessary bulky texts.
You can share other files via SMB, but I have a feeling you won't like that.
That would be an option, although I'm not sure it will make it automatically bootable.
You could also have the LibreELEC USB/SD Creator install the image on the external USB device directly.
The default boot device for a RPi is /dev/mmcblkXXX
For USB it apparently is /dev/sdaX
Replace 'X' with the correct device number.
Mind you, LibreELEC always works with 2 partitions (system and storage), not just one single partition.
I take it you mean that you've enabled UPnP sharing? That will only apply to videos/music that are scraped into the Kodi Libraries.
Multimedia files located elsewhere will not be shared.
It's the Wifi/BT module from the Raspberry Pi Zero, which was considered good.
But wireless connections are always unique in every house/apartment/location.
Did you have any specific overclocking settings or other stuff in the config.txt file?
No. The more 'junk' that is being put into the LibreELEC installer, the bigger the bloat will be on the overall installation. We like to keep LibreELEC as slim as possible. And really, not every Kodi user will use NFS server and MySQL by default. Plenty of them are happy using external USB storage, use UPnP or the already built-in SMB server.
You can use Docker for setting up your additional server demands, personally I would use a separate RPi3B+ box with Ubuntu Mate as a small server.
system will random freeze and log as below-
can someone advice what happened?
What is you posted is not a Kodi crash log nor a debug log.
Our crystal ball is rather limited, I'm afraid.
The videochip has not changed in the 3B+, so HEVC video will still be decoded via software (plus some other tricks). The CPU 1.4Ghz will help, as will some overclocking, but keep in mind that 1080p HEVC videos can easily become a problem for every Raspberry Pi when the video bitrates start climbing. Not to mention a CPU overheating problem.
You can change CEC behavior in the System / Input Devices section.
I thought this software fork started because openELEC was being released with too many bugs.
And where did you get all that utter BS nonsense from? You could have asked the people in LibreELEC for the real reason.
Well this software is full of them.
So one single problem you are mentioning in this topic is the same as "full of them"? You're not being very realistic or logical, are you? Or are you just deliberately trying to piss off the LibreELEC team? It's really not the best way of getting support here.
Now I cannot set the time correctly using a time server.
The default time server options work already for the thousands of other LibreELEC users, using the same time servers as OpenELEC btw. So perhaps your network, your time server or your modus operandi is causing a problem.
LibreELEC shares the same (system) folders as OpenELEC does, nothing changed there. Only that SMBv2 is now used by default.
Also check your Ubuntu box which Samba client type is active.
Welcome,
Rockchip development is still in its early stages. You already found the Rockchip section, which is good
Since I'm not a programmer myself, I cannot outline the latest changes but I'm sure 'the others ' can do that for me.
I don't know how extensive your programming experience is, but for generic Kodi development, have a look here: Development - Official Kodi Wiki
LibreELEC 8.2.3 and up (Leia testbuilds) uses Samba / SMBv2+ by default. SMBv1 was responsible for the worldwide WannaCry outbreak last year, because Microsoft allowed unauthenticated access to Windows machines. In the LibreELEC Settings addon you can still enable SMBv1 for rescue efforts, but you may want to ask yourself if you want to continue to use such a outdated and unsecure network file protocol that can compromise the rest of your local network devices.
Because SMBv2 no longer supports network browsing, you will need to add new samba sources manually via the Add network location... option. If the Ubuntu machine is your Samba server, you could also consider setting up NFS on it instead. NFS has worked for fine me since the XBMC Eden days.
Also because of newer movie and TV scraper functionality, it is recommended you fully re-scrape your video collection(s) since OpenELEC never was updated on that part as well. Call it a spring cleaning.
I was under the impression that the whole point of alpha releases is to get some testing so at least the number of errors can be kept at a minimum.
It is also important that users supply as much information as possible surrounding error/bugs. This is useful when reproducing the reported problems.
You start with saying "bogus error messages" which translates to 'not genuine or true'. Errors appear when something goes wrong. They are not simply invented by a rebellious or recalcitrant operating/server system.
You only provide a list of identical errors instead of the full kodi.log . Puzzles with only 3-4 pieces are impossible to solve.