Posts by milhouse

  • Can't enable cifs shares in v8.1.2

    Quote from TeHashX

    This mean in v8.1.1 C2 connected with SMBv1 protocol but in V8.1.2 samba was updated and not accept connections until protocol version is added to Options field?

    Partly correct, as it's not really a Samba issue (at least, not in LibreELEC) it's a kernel issue. With 8.1.2 the kernel now establishes CIFS vers=2.1 (aka SMB2) connections by default, whereas with older releases (8.1.1 etc.) the kernel will establish CIFS vers=1.0 (aka SMB1) connections by default.

    With more Samba servers dropping support for SMB1 (and security conscious users disabling it) the kernel developers recently made the decision to stop establishing CIFS vers=1.0 connections by default.

    Most LE 8.1.2 users won't notice this change, it's only going to affect users with older Samba servers that don't support SMB2 (or are not configured to support it, which is probably the case with your server as Samba 3.6.25 is capable of supporting the SMB2 protocol).

    Try adding the following to your Samba 3.6.25 server config, this will disable SMB1 but enable SMB2:

    Code
    min protocol = SMB2

max protocol = SMB2

    Given the age of your server you should also consider an upgrade, as it's not secure.

  • Problem with booting MSI Cubi after update to 8.1.1/8.1.2

    Since 4.9.y appears to work OK, and the problem is there with 4.11.12, it might be worth trying some of the 4.9.y-4.11.12 builds in my test thread to narrow down when the issue started. I announce each new kernel in the summary so it should be possible to find each build with a new kernel.

    Start with 4.11.10 (the last 4.11.y kernel before switching to 4.12.y) as that may give you the same problem. Then test 4.11.0 and if that works OK then try the later 4.11.y kernels to determine which is the first problem kernel.

    If 4.11.0 has the problem, then test 4.10.y. If the 4.10.y kernels don't have the problem then try the 4.11 release candidates (there were 5 in total).

    Once we know when the problem started then we can review what changed in the build and maybe even pin it down to a specific commit.

  • Problem with booting MSI Cubi after update to 8.1.1/8.1.2

    Quote from Adam

    OK - i'll check. But it would be very strange, because when it runs it's rock stable and with bad memory stick it would be almost impossible.

    There are two memory sticks installed in my CUBI, so I can check if removing/swaping one of them makes difference.

    Using 8.0.2 or Windows 10 - no problems - boots in 100% cases.

    You'd think that, but see this thread where 8.0.2 booted fine, but 8.1.0 did not, and memtest86+ revealed a bad memory stick, the replacement of which resolved the issue.


    It's possible the newer 4.11.12 kernel in 8.1.0 tests or otherwise utilises more memory than the 4.9.29 kernel in 8.0.2, and sometimes hits a bad address.

  • Problem with booting MSI Cubi after update to 8.1.1/8.1.2

    Does it still respond to pings when "frozen" at the MSI boot logo?

    If so, see if you can connect with ssh (username: root, password: libreelec) and run "journalctl | pastebinit" and paste the url. You should also check to see if you have any crashlogs and upload the most recent ("cat /storage/.kodi/temp/kodi_crash.log | pastebinit").

    If no response to pings, then try removing "quiet" from the kernel command line (in one of your syslinux.cfg, probably /flash/EFI/BOOT/syslinux.cfg if booting with UEFI) and see if it always hangs at the same point.

  • Can't access SMB share on LE after upgrade to 8.1.1

    That file is not compatible. It's your responsibility to maintain your own custom configuration. This has been explained in the 8.1.0 announcement, which I guess nobody bothers to read.

    You now need to update your custom samba.conf based on the latest /storage/.config/samba.conf.sample - ie. re-apply your changes to the new sample file. Since you've lost Samba access, you'll need to do this via ssh (username: root, password: libreelec).

    In the next 8.1.x release we will now be disabling incompatible custom samba configurations so that, worst case, you have working Samba but none of your custom shares or other changes (until you re-apply them).

  • Can't access SMB share on LE after upgrade to 8.1.1

    By default the LibreELEC Samba server is not configured to use a username/password, but it's hard to know what your settings are now. Are you sure you're using the correct IP address for the LibreELEC server? Are you using a custom samba.conf for the LibreELEC Samba server, because if you are and haven't updated it then that is almost certainly the problem (your old Samba 3 config is not compatible with Samba 4).

    Network browsing has a dependency on the SMB1 protocol and is unlikely to work when the server non longer supports SMB1.

  • Can't access SMB share on LE after upgrade to 8.1.1

    Quote from infoalter

    A normal account.

    I even did try to set in Libreelec the same username AND same password as in my windows PC, no matter what user/pass there is always the same error

    Changing the LibreELEC Samba Server configuration (in the LibreELEC Settings add-on) will have absolutely no effect on how Kodi uses libsmbclient to access your Windows 10 PC.

    The only Samba settings relevant to communication with a Windows Samba share are in Settings > Services > SMB client (Advanced/Expert level settings required).

    If you have previously entered a username/password for your Windows Samba share into Kodi, and ticked "remember this password", then make sure you don't have an invalid password configured in /storage/.kodi/userdata/passwords.xml

  • Can't access SMB shares

    Quote from Issacbinary

    Samba is set to min SMB1 max SMB3

    Why are you changing the LibreELEC Samba Server settings when you're trying to access a Samba server on another machine?

    Try changing the "Maximum protocol version" to SMB1 in Settings > Services > SMB Client (this needs Advanced/Expert level settings) and you'll only use SMB1 (which means you won't be able to access servers supporting only SMB2+, which is a recommended configuration these days) but may allow you to browse your network (network browsing *only* works with the SMB1 protocol, and even then only under certain circumstances depending on other factors, such as server settings so is not guaranteed).

    If you want to browse your smb shares, then add them as sources, or add them as "network locations" in Kodi:

    IMOdG2M.png