Posts by milhouse

  • LE 8.1.0 bug with auto resulution switcher 1080P/2160P on nvidia

    Quote from Ostrymiecz

    What if I install Ubuntu, latest nvidia driver 384.69 and Kodi from PPA? Will it be the same as in LE 8.1.0 right now

    Yes, that would be the same as LE 8.1.

    Quote from Ostrymiecz

    And lastly? What should I do if Ubuntu will be the same as LE. Use Kodi on Windows?

    If it's the same on Ubuntu with the same driver and same Kodi, then it's either a driver bug or a Kodi bug. Filing a ticket on trac,kodi.tv would be the next step so that a Kodi developer can look into it.

    You could also test a nightly build with LE 9/Kodi 18a1 in order to determine if it's a driver issue: build #0821 is using 384.59, while build #0822 is using 384.69, and there are no significant LE or Kodi changes between these two builds. If you have the same 4K resolution issue in #0822 but NOT in #0821 then we can say fairly confidently it's a 384.69 driver issue. If the issue is already there in #0821 then chances are it's a long term issue (either in the nvidia driver series, or Kodi 18a1 the videoplayer of which has been largely rewritten since Kodi 17.x).

  • Cannot access Libreelec Nuc via Windows 10

    Read the 8.1.0 announcement, in particular the section "!!! SAMBA UPDATE – IMPORTANT !!!" (third bullet point).

    Quote from Mario77

    Should the SMB V2 and V3 be working for me?

    Not if you're forcing SMB1.

    If you haven't already setup your smb:// sources then you'll need to enable SMB1 on your server (and force Kodi to make only SMB1 connections), then set up your sources in Kodi using network browsing (if available). If network browsing no longer works (which is possible, depending on your server, Samba4 in LibreELEC, and the way the wind is blowing), then you'll just have to add network locations manually in Kodi (leave the username/password blank - add this when prompted on first access, saved in passwords.xml), then add your sources.

    Once your sources are all configured, disable SMB1 on your server, configure SMB in Kodi as "None" (ie. auto-negotiate, which should mean SMB3 or maybe SMB2, depending on your server).

  • Image from the compilation of LibreELEC cannot be installed on Intel NUC5i5RYH

    I don't currently have a spare system on to which I can install your image, however I've unpacked your image and both the System and Storage partitions are present.

    I've also booted a Skylake-based NUC using your image and can successfully boot into all the supported modes: "installer", "live" and "run" (the latter correctly resizing the /storage partition on the USB stick). At no point did I experience a Kodi restart loop, so it doesn't look like there's anything wrong with your 8.0.2 image.

    Please double check your hardware (memtest86+ etc.). Without the crash logs, though, it's impossible to tell why Kodi is crashing. Given this is a "weird" and unexplainable situation, it's most likely due to hardware failure of some kind.

  • Image from the compilation of LibreELEC cannot be installed on Intel NUC5i5RYH

    If an older LE or Openelec build is working, then enable ssh in the working build (and confirm it is working), then upgrade by dropping the non-working .img.gz into the Update folder and reboot. If after upgrading you find Kodi is crashing in a loop you should now be able to login with ssh.

    As for the lack of /storage, that seems a little unlikely. Can you upload your .img.gz somewhere?

  • Image from the compilation of LibreELEC cannot be installed on Intel NUC5i5RYH

    oh crap. It probably needs Kodi to start successfully once in order for the LE addon to configure and start the sshd service. Hmmm. You're probably screwed.

    #2 great, then enable ssh and upload the latest crashlog that contains any information. It's possible kodi is crashing immediately without starting which would explain the lack of any information, in which case you should try running Kodi from the command-line but if it's stopped crashing then who knows.

    To be honest though, weird problems like this often turn out to be hardware faults. Check your memory by running memtest86+.

  • Cannot access Libreelec Nuc via Windows 10

    What file are you adding your changes to, paste the full path of the file you are changing.

    The only samba.conf file LibreELEC replaces is /storage/.config/samba.conf.sample.

    I suspect you're either editing the wrong file, or if you're editing via Windows then your Windows editor is creating a file with a .txt extension that is being ignored.

  • Suspend

    Sorry, forum is screwing up the url by replacing "&" with "&".

    If you're using the legacy driver and it still won't suspend that's quite unusual as the legacy driver works in most cases. Make sure your BIOS is up to date, that's the only other suggestion I have.

  • Suspend

    You're most likely using the "modern" 384.59 driver with your GT610M in the 1503. Unfortunately this driver has buggy suspend support.

    The only solution right now is to use the more reliable "legacy" 304.102 driver as your 1503 hardware is supported by both drivers (your 1501 can only use the "legacy" driver).

    See this post for details on how to switch to the legacy driver. You're unlikely to notice any difference in image quality using the older driver.

  • Cannot access Libreelec Nuc via Windows 10

    Quote from Mario77

    and Windows 10 from Libreelec..

    If your using anonymous access (ie. no username/ppasswor and "Everyone" granted access to the Windows share) then this is no longer working as Microsoft have disabled anonymous remote access for SMB shares. You'll now need to create a user with password on the Windows machine, assign the user to the share, then access the share in Kodi via Video > Files which should prompt you for a username/password - enter the username and password of the Windows user, tick the "Remember" box (to save the username/password in passwords.xml) and you should now be able to access the share.

  • Cannot access Libreelec Nuc via Windows 10

    If you're using a customised /storage/.config/samba.conf then you'll need to delete it (using ssh before/after upgrade, or Samba prior to upgrading) and use the new /storage/.config/samba.conf.sample as the basis of your custom samba.conf, then reapplying your custom changes.

    8.2.0 includes Samba 4 which is very different from the Samba 3 in 8.0.2, and any customised samba.conf will not be compatible. Customised configuration files are the responsibility of the user and will not be migrated during the upgrade. Most users should not need a customised samba.conf.

    This is all explained in the blog announcement.