Posts by milhouse


    You haven't told us anything about the software you are using to share the drive (ie. what is your NAS on

    Is it a LibreELEC host? Or Windows? Or something else? What version of whatever software are you using?

    It looks to me like SMB3 is either not supported or not enabled on the NAS, so you should either enable SMB3 (if the NAS supports it) or try connecting with a lower protocol (ie. vers=2.1, vers=2.0 etc.).

    If the NAS only supports SMB1 you may need to include "sec=ntlm" as an option, and of course specify "vers=1.0".

    so I asume it worked and I am now in this build.

    Yes, you're now using the test build that enables the Marvel wifi driver.

    I did not try the bluetooth stuff as per Chewitt as the wifi is more important than the bluetooth for now

    However you still need to install the firmware as directed by chewitt as the firmware file is also required by the WiFi driver before it can work.

    Please install the firmware file, reboot, enable Wifi and Bluetooth, then post another dmesg.txt, confirming if Wifi and Bluetooth are now working.

    chewitt I'll add the following configs to tonight's #0312 test build - this also enables USB support:

    Comparing LibreELEC:master...MilhouseVH:le10_enable_marvell_wifi · LibreELEC/ · GitHub

    I haven't enabled PCI support because the likelihood of if being needed seems quite low (Marvell are no longer in the WiFi hardware business).

    Normally we would add these same options to all platforms but in this case I'm struggling to see any benefit in doing so.

    ToxicWaste the test build will be posted in this thread later this evening (about 9pm UK time):

    LibreELEC Testbuilds for x86_64 (Kodi 19.0)

    I strongly suggest using a disposable test installation if you can, as the Python3 changes will make a mess of any working LibreELEC 9.2.x system.

    Once you have booted the #0312 test build, you may find that you are still missing WiFi firmware and you will need to install the missing firmware the same way you did the BT firmware. Post your dmesg again if you get stuck.

    Marvell exited the WiFi/BT hardware business in 2019 (selling up to NXP) so including the ~9MB of Marvell firmware in the Generic image is unlikely to pay any dividends - it doesn't seem like Marvell were particularly successful so the handful of users that might be using this hardware would best be supported by the occasional manual firmware install when required.

    Menu will not come up when boot up libreelec I get the kodi side of it but I am trying to get into the rassberry is is there command that I could type in with a keyboard to switch to the os

    What "menu" are you referring to? If you're seeing Kodi, then LibreELEC is working as expected since Kodi is the only GUI we provide. Are you confusing LibreELEC with Raspbian which does have menus, a desktop GUI, consoles etc.?

    Sorry...Access Denied to link.

    Where do I access that BIOS change? Looking all through my LE and Kodi Settings.

    Sorry, you should be able to access the link now - it includes a photo of the BIOS option.

    The BIOS is the firmware built into your PC - if it's an Intel NUC then you should be able to access it using F2 as the device boots.

    milhouse , I was able to make the fix using your first suggestion running "PuTTY". Thank you.

    Yes, ssh (PuTTY) is the way to add the blacklist. However at this time the preferred option would be to disable the BIOS option as it's that setting which is causing the problem in the first place, and blacklisting as the second best choice. But whatever works! :)

    Would someone please explain how/where to execute the code above while in LibreElec?

    Can you try this alternative solution:…ard-regression-9-2-9-2-1/

    In your BIOS, disable "HD-Audio DSP" as it's not required (won't be used by LibreELEC) and is in fact the reason why the audio is misconfigured in the kernel (which then has to be fixed by blacklisting the unwanted DSP driver that the BIOS option has enabled).

    Those wiki instructions are starting to date a little... :(

    Depending on how old your installation is, it may include extlinux.conf (really old OpenELEC install), syslinux.cfg (legacy BIOS) and/or also efi/syslinux.cfg (UEFI). However fairly recent LibreELEC installs (when flashed from img.gz, within last 12-24 months) should only have /flash/syslinux.cfg.

    You can forget the "-w" option on nano. That option disables hard wrapping of long lines, which is now the default (since Feb 2019, LibreELEC 9.0) as we disable hard wrapping by default when building nano. Again this is a case of the wiki having to support both old and new LibreELEC users.

    Edited 2 times, last by Roby77: BTW i checked edid.cpio file and seems that he included now the new edid.bin (6 hours ago).

    So all good now? :)

    So is the one I'm using a stable build ? ( LibreELEC-Generic.x86_64-9.80-nightly-20200214-70b69eb.img.gz )

    No, that's an unstable build based on Master (which does include 440.59)

    Or is it different from LibreELEC-Generic.x86_64-9.80-Milhouse-20200214210338-#0214-gd1fdc57.tar what u shared ? Because both are 0214.

    The nightly build is different from the Milhouse build in that the Milhouse build includes future changes that are not yet in Master, so Milhouse is Master++.

    Both the nightly and Milhouse builds are the same in terms of 440.59 support as both have included 440.59 since 5th Feb, and your "getting stuck" issues would need more detailed investigation - maybe the Milhouse build already includes fixes that resolve whatever issue you are experiencing.

    I'd like to get 440.59 (and support for your GTX 1650 Super) in LibreELEC 9.2.x before the next release. I did recently upload a test build of "stable" LibreELEC 9.2 with 440.59 for another team member to test, but due to time commitments that hasn't happened, so please give this LibreELEC 9.2.x build (with Kodi 18.5) a try and confirm if it works for you or not:


    rtl8812au support is included and enabled by default - no need to install or enable anything, your hardware should be detected automatically (unless it's using a vendor/product id that isn't currently supported).

    If you're having hardware detection problems upload the latest zip file from the "Logfiles" Samba share.