The OVA for vmware exists for functional testing within the developer team and is not intended or supported for real-world use and playback. If it works, that's great. If things aren't perfect we don't really care because it works 'enough' for our needs, and mouse support isn't essential on a non-Desktop OS. Keyboard navigation works fine.
Posts by chewitt
-
-
nickr sadly it's too simple for people to comprehend
-
It's hard to comment without being a little rude. There is no actual dependency on git for compiling .. but if you have chosen to ignore a sensible workflow for cloning our source code *and* you cannot figure out the build command from the simple instructions in the wiki; the chances of your customisations resulting in a working image are low, and the developers/staff around here will be shy of getting involved. What are you actually trying to achieve with customisations?
-
Quote
Q1. How this can happen? My Windows10 PC still can browse the complete network and show all SMB network shares both on the NAS and on the LE 8.2.0 HTPCs. Browsing is a very basic operation. It should work in any SMB version.
It can happen because Win10 does something new and different from SMB1 era browsing which (whether you choose to believe it or not) was exorcised from the SMB2/3 protocol and is very very definitely not supported under SMB2/3. Basically you are not special and your issue is the same everyone else's issue.
QuoteSMB sources from Samba/NAS devices can normally be browsed via the “ZeroConf network browsing” alternative.
Q2: Unfortunately this does not fly. I can see the SMB and sftp shares of the other LE 8.2.0 HTPCs but not my legacy NAS.
Note the carefully chosen and deliberate choice of the word "normally" in the statement. "Normally" does not equal "always" so it appears your NAS is an exception to the norm and doesn't advertise shares over ZeroConf/Avahi. Most modern/recent NAS 'do' advertise, and for the lucky users with a NAS that does, it works great. It may not 'fly' for you, but there is no bug or problem to be investigated here.
QuoteI understand the security aspects of these improvement, however form usability point of view this is not an acceptable way of operation
We have prioritised security and basic functional support of SMB2/3 for users who MUST use SMB2/3 as the result of MS decisions. There is nothing stopping you from setting up things to use an insecure SMB configuration that works exactly the same as it did under 8.0. Fixing the browse function to use whatever new process Win10 uses (which again, is not how it worked under SMB1) is not an LE issue it is a Kodi issue, so you are complaining to the wrong audience.
-
I must have been half asleep -as the txt file is in /usr/lib/firmware not the brcm subfolder
Download again, the test image is updated.
-
Full debug log please - clean boot and demonstrate the problem
-
Code
dtoverlay=pi3-disable-wifiadd ^ that to config.txt and the internal wifi is disabled and won't interfere with connections etc.
-
Update to LibreELEC-Generic.x86_64-8.2.1.tar and see if it works. It's the 8.2.1 release with the extra .txt file
-
Create the USB .. boot from it and unless you hit the keyboard in the first few seconds to start temp/permanent 'live' (run from USB) modes it will start the installer GUI which asks you to pick a storage device (i.e. internal drive) to install to.
-
^ according to that it has an RTL8812AU chipset which we have driver for (although devices breed new USB ID's sometimes). There is a caution note that there are multiple revisions in circulation. So it probably works. No guarantee though. And before you ask, no we don't recommend devices. I'm happy to share my personal opinion that all Realtek devices are sh1t though .. due to out-of-kernel unmaintained drivers.
-
Kodi is not designed for (and does not support) cross platform profile moving. You can try literally copy/pasting the userdata folder files over .. but I doubt it will work reliably because there are fundamental differences in file paths and some Kodi settings.
-
*debug* log .. not normal log
-
Moved to the Amlogic community section where hacked-up versions of Kodi are 'supported' by their creators.
-
Reboot after installing. Fixed? .. in which case it's about the environment PATH not being set until reboot.
-
"lspci | paste" would be more useful, assuming it's connected to the PCI bus
-
I don't want to appear rude, but Leia is pre-Alpha code. Bugs are normal. If you don't want bugs .. don't run pre-Alpha buggy code. If you want to participate in bug hunting the development threads in the Kodi forum are the appropriate place to provide feedback.
-
Nope - drivers need to be baked into the LE image. You probably need a development version with newer kernel and firmwares .. and even then you would need to tell us the chipsets in the device to get a factual answer on support. As a rule we support stuff found in HTPC boxes; which is likely a bit different to what's found in a Surface.
-
There is a VPN client add-on in our add-on repo. VNC is not VPN.