Posts by milhouse

    Just so there is no confusion - LE 8.2.3 will include the revert of the ksoftirqd commit which is just a short-term/interim solution (but one we know works, particularly with the older 4.11.y kernel in 8.2.x). Hopefully a better long term fix will be added upstream, maybe along the lines of the suggestion from Linus, in time for LE 9.0.

    blueribb The problem is that without the required information - at least journalctl, ideally the latest zip file from the Logfiles Samba share, as explained here - we don't know for sure what the problem is - it could be missing firmware, or a missing driver.

    The article you linked to (thanks for that) claims the WiFi chipset is RTL8723BS which is now supported by the in-kernel driver in LE9.0 nightlies (but not LE8) so it might be worth the OP giving LE9.0 a try - test builds are here.

    Nvidia officially ended support for the 304 driver series at the end of 2017, so it is now no longer developed/maintained/supported by the manufacturer:

    Support timeframes for Unix legacy GPU releases | NVIDIA

    Building LibreELEC with the final 304 driver and latest kernel and other related packages may be possible in future but will be become increasingly difficult as more patches and fixups are required.

    OK, we did some internal testing and it somewhat supports what you are seeing, but it's probably not a LibreELEC Samba Server issue.

    With Odroid_C2 as the LibreELEC Samba server, a 4GB file copy was attempted from a Linux PC:

    1) Using Nautilus (GUI file manager) copying to Odroid_C2, this failed at 2GB - Nautilus probably uses gfvs or libsmbclient so userland client, and SMB1

    2) Mounting the share with "mount -t cifs -o vers=2.1 //192.168.178.3/videos" (ie. SMB2, using kernel CIFS driver) successfully copied the entire file to Odroid_C2

    So it would appear to be a client issue rather than a server (LibreELEC) issue.

    Depending on how you mount the share on the client it may or may not work. Using the "lfs" option may improve your chances of success. I'm not sure if "cifs" is supported by Mac OS (probably not). SMB2 is better than SMB1.

    Mounting the share with "smbfs" has a known 2GB file size limitation, and "smbfs" is not recommended by the Samba Team, however I don't know what Mac OS is using - it could be "smbfs", in which case try using different mount settings (if this is possible).

    The Windows failure is odd, but could be due to a network issue (try a different network cable, different switch, different port). Are you able to read a file larger than 2GB from the LibreELEC Samba Server to Windows? If not, there's a problem somewhere in your network.

    It might be that the same network issue affecting Windows is the cause of the Mac problem, so probably best to fix the issue with Windows first then see if that also fixes the Mac.

    I just copied a 3.5GB movie file over SMB from Windows 7 to a Skylake NUC running LibreELEC 9.0 Generic without any issue.

    Windows is using wired 1GB ethernet, the Skylake NUC is using 5GHz WiFi, and the NUC is writing to its internal NVME /storage (formatted as ext4), so the LibreELEC Samba server appears to be working as expected and 2GB file sizes are not a problem.

    Have you always had this problem or only since upgrading? I'm surprised Windows is failing to transfer more than 2GB. This sounds more like a problem with the clients (Windows, Mac) than the server, or possibly the network (try a different switch?)

    If Windows can transfer 2.5GB but the Mac chokes on 2GB+ then this sounds like a Mac issue, which isn't really surprising as Apple SMB support is a bit rough, and it's not difficult to find many instances on the web of Mac users struggling to break the 2GB SMB barrier. For example:

    samba - Mount SMB share without 2GB filesize limit in OSX Lion - Super User

    What version of Mac OS do you have? Maybe you can install a better smb client?

    If you only have one USB stick (or one USB port) then after running createlog, run:

    Code
    mount -o remount,rw /flash

    and copy the zip file to /flash.

    Then shutdown the laptop, boot into your normal OS (probably Windows) and upload the zip file from the USB memory stick.

    Presumably this laptop is using unsupported hardware, hardware which may only be supported by Windows drivers.

    Best thing you can do is:

    1. Add "textmode" (without quotes) to the end of the kernel command line of the USB stick - use the "live" mode entry so that it looks like this:

    Code
    APPEND boot=UUID=<something> live quiet tty vga=current textmode

    The file to edit is "syslinux.cfg" - edit the file in the root if booting with legacy BIOS, or edit the file in EFI/BOOT if booting with UEFI.

    2. Boot into "live" mode and you should find yourself in a text console

    3. Run the command "createlog" and this will create a zip archive in /storage/logfiles (ignore the two errors about missing /storage/.kodi/temp)

    4. Copy the zip archive from /storage/logfiles to another USB flash drive

    5. Upload the zip file from the USB flash drive to somewhere on the internet (ie. Dropbox, Googledrive etc.)

    6. Post the URL link for the zip file

    No promises that your hardware (which isn't really the ideal target hardware for LibreELEC) will be supported but the zip file should provide some clues.

    These are the mounted partitions in LibreELEC - I thought you said you had plugged the USB HDD into the Zyxel router?

    The LibreELEC OS won't be mounting the USB HDD that is being shared by your Zyxel router unless you mount the share as a CIFS partition using systemd (or autostart.sh).

    Kodi however should be able to see the shared USB HDD because it is using libsmbclient, but first you'll need to add the share as an smb:// source in the Kodi GUI.

    In order to add this source you will need to add an SMB network location - don't try to browse the network as this is no longer supported. Enter the server name (your router IP address), the share name/folder, and (if configured) the username/password that you have configured in the Zyxel router to protect the share. Then you can add the source using the network location you just created.

    also the one saying enable samba password.

    It sounds like you are modifying the LibreELEC Samba Server configuration which is not relevant if you are using your Zyxel router to share the USB HDD.

    The only Samba settings you are interested in when sharing the HDD via your Zyxel router are in Kodi > Services > SMB client. Make sure you enable the "Expert" setting in order to access the Samba client options.

    The passwords do confuse me i must admit, is it the zyxel router one that i enter when i add new network connection in smb in librelec? all variations of this don't work.

    Yes, you should add a username/password to the SMB share in the Zyxel router if that is the device you are using to share the HDD. However depending on the options available in the router admin console you may not be able to configure a username/password, in which case you'll just have to use guest access (no authentication) and hope it works - it will depend how the Zyxel Samba server has been configured.

    Typically the version of the Samba server that is installed in these router-type devices is very old - sometimes up to 10 years old, and without any security updates in that time. Old Samba servers normally only support the SMB1 protocol, and may also require that the "Legacy" security option is enabled in LibreELEC (this configures libsmbclient to negotiate an even less secure SMB1 protocol with the router than is normally the case).

    If all else fails, why not connect the USB HDD to the Odroid_C2 and share it to your laptop using the LibreELEC Samba Server? You'll have the benefit of a modern, secure Samba server (supporting SMB3) and you can disable the (quite likely insecure) Samba server in your Zyxel router.

    Start a new thread, don't necro an unrelated thread as your inability to add a network location is unlikely to be related to any of the issues discussed previously in this thread (for example the issue raised by the OP is due to a bug in Samba that is fixed in 8.2.0). And no, don't add :5000.