Posts by milhouse

  • Cannot boot from PCIe based SD-card reader

    Quote from chewitt

    The error is clear in the first two images. The syslinux.conf or extlinux.conf is configured for boot=LABEL=System and disk=LABEL=Storage and those partition labels do not exist on the boot device. It should be using boot=UUID=blah something like belo

    This is only partly true for x86 systems, as it turns out. The installer itself will use UUID, but the installed x86 system will use LABELs.


    The x86 installer will create the two partitions and file systems on the x86 client, and then label them "Storage" and "System", before creating /flash/extlinux.conf with LABELs and - if UEFI support is detected - copying /flash/extlinux.conf to /flash/syslinux.cfg and /flash/EFI/BOOT/syslinux.cfg. Copying both syslinux.cfg files ensures that a UEFI-capable client will boot successfully using either legacy BIOS or UEFI.


    So MacNB's syslinux.cfg using LABELs is correct.

    Assuming the problem is the drivers being loaded as modules, there is now a test build available (based on LE9 with Kodi 18a1) that includes in-kernel drivers.

    MacNB can you manually upgrade your SD card by copying the KERNEL and SYSTEM files extracted from the test build tar file, then try booting your newly updated SD card and report if it works or not.

    Edit: I see mglae has posted above - if you want to play it safe, use a fresh SD card based on an official disk image and then manually update the KERNEL and SYSTEM files in the root of the first partition using the files extracted from the tar file, before booting from the SD card in your client device.

  • SMB observations thoughts on newer builds and or millhouse works

    I suppose the default workgroup should be something that can be set via the LibreELEC Settings addon so that there is no need to edit the Samba server config - that's something we could add as a feature in a future build.

    Quote from saltwaterfishlover

    but the only other thing I found was that with the newer builds you may need a username and password for the computer

    Do you mean you need a password to access the LibreELEC Samba server - I haven't experienced that issue myself - or that you now need a password to access your non-LibreELEC Samba servers when accessing them via Kodi? When using Kodi with Samba4 to access Samba servers (ie. "Everyone" access on Windows), anonymous access is known to be broken - presumably this is an upstream Kodi issue. The solution is to use a username/password (add an entry to /storage/.kodi/userdata/passwords.xml).

  • Shuttle Wireless Card Keeps dropping connection

    Are you sure it's still stable if you go back to OE with Kodi 15.2?

    The thing about wifi is that it can be affected by the environment, ie. a neighbour may have started transmitting on the same wifi channel and your two Realtek devices are simply marginal signal-wise and now lose connection because of the overlapping neighbour. You could try using a different channel, preferably one that is relatively free of other users/neighbours (there'll be an app for that - some sort of wifi-scanner app).

    You could try my test builds (based on LE9) as these include slightly updated Realtek drivers, and more recent kernel, but honestly. LibreELEC Testbuilds for x86_64 (Kodi 18.0)

    Failing that, Powerline/Homeplug works really well...

  • USB-SD Creator NOGO

    Sounds to me like the SD card has died. Once an SD card goes into write-protect mode it's usually pretty terminal. It's just random pot-luck when it will happen, as something has now failed (perhaps some critical part of the Flash memory has worn out) within the SD card and caused the controller to go into read-only mode. Bin it, get a new SD card - even if it could be recovered, would you trust it?

    I've had it happen to several SD cards over the years (not all used with Raspberry Pis), and expensive USB flash memory is not immune either. It's just the nature of Flash, unfortunately.

  • Creating WiFi AP on LibreELEC on RPI2

    Quote from willieaames


    The wireless problems mostly have to do with the Broadcom wireless chipset on the RPi. On mobile now, but you can go to the official RPi forums and read all about that if you want.

    I'm aware of some issues which will hopefully be fixed soon when they will be added to LibreELEC. This particular issue is actually a connman 1.32 problem which we will take upstream. As a temporary fix we may use sysctl until there is a complete fix in connman.

  • Time out by 1 hr

    You mean LibreELEC, right? :)

    Also, do you mean the time shown at the command line with the "date" command is wrong (most likely UTC), or the time shown in the GUI? The former can be incorrect if upgrading from an older OE installation, while the later should reflect whatever timezone country you specify in the Kodi GUI (ie. Britain (UK)). Note that you'll only see the "Timezone country" option in Settings > Interface > Regional if your Settings level is Standard or higher.

    If you've set the correct Timezone country and the time is incorrect at the command line, what is the contents of /storage/.cache/timezone ?

  • Windows shared folder access problem

    /storage/.smb/smb.conf is the configuration created by Kodi when using libsmblient for smb:// access.

    /storage/.kodi/.smb/smb.conf is an older version of the above file and can probably be deleted (the entire directory) - newer builds of Kodi use the above file.

    /storage/.config/samba.conf is the Samba server configuration (most people don't need to create this and can just use the system default file).

  • 8.0.X: netconsole feature unusable and the way to fix it

    No build logs I'm afraid. If you just want to change netconsole to a module then that should be relatively straightforward (and once you've pushed a change it can be added in test builds, ie RPi/RPi2/Generic). I suggest running "make oldconfig" for the kernel and updated config if you can, in case there are any other related/dependent changes. If you're not able to do this then I can do it and feed back any necessary changes.

  • 8.0.X: netconsole feature unusable and the way to fix it

    Quote from arek


    Where to submit PR?


    GitHub - LibreELEC/LibreELEC.tv: Just enough OS for KODI

    Quote from arek


    What are other projects?


    LibreELEC.tv/projects at master · LibreELEC/LibreELEC.tv · GitHub

    Quote from arek


    Would be good if thread-83.html mentioned that PR is needed to fix bugs.

    PRs from users are not *needed* to fix bugs, but as it's difficult to describe this as a bug (and even if it is, it affects almost no-one, ie. it's very niche) I simply suggested you submit the changes as I'm not sure anymore else will consider this as something that needs "fixing". Plus, you sounded like you were relatively "technical" so I didn't expect a request for a PR to phase you.

    It's not entirely clear why netconsole is enabled at all, as it obviously doesn't work as configured (in which case, maybe it should be disabled/removed).

  • Sources down? Mirror possible?

    Quote from chogger


    Trying to build LibreELEC 8.0.1 since 2 or 3 days but I can't download package source code. Getting 404 Errors. Is this already known? Or is it a problem on my side?

    Was working flawless last week.

    Can you provide details of the failure - which package?

    Both the devel and mirror servers are responding normally for me, so without more details for now I'd say it's a problem your side.