Posts by milhouse

    I do fear problems with unwilling hardware, as the quote says "check its availability on your hardware before enabling this option" and we dont know all hardware where it is running on. Just a precaution.

    Possibly a standard "here be dragons" warning with all new kernel features - I'd hope AMD DC would be able to identify when FBC isn't available in the GPU hardware and try not to use it (which would be the sane thing to do)... only one way to find out!

    Ah yes... to actually build that repo (rather than just review the patches) you'll need my own custom build system which is mentioned here: Python not building

    milhouse.buildcode would be created by my build scripts.

    In addition to the patches my build system automatically updates the source tarballs of several packages (kodi, libcec, libnfs, pvr.* etc.) which you are most likely missing.

    With my build scripts if you wanted to recreate my build, you'd use "./ -s x86-next" and that would Generic with the 4.17 kernel (pulling the latest PRs from github, so you're not always guaranteed a successful build!)

    The main configuration files are lepull.dat and ipatches.dat, with profiles (ie. x86-next) defined in profiles.dat.

    Thanks, I'll enable the CONFIG_DRM_AMD_DC_DCN1_0=y

    I enabled Frame Buffer Compression as in theory it should increase the effective memory bandwidth - have you had any problems with it?

    Sorry, I didn't get any notifications there had been new posts in this thread.

    Yes, looks like Python is crashing.

    The complete source of my build is included within the tar file - there's a file called within the tar file, if you extract this and then extract the contents you'll have all my build scripts, and the configuration for the build, plus all the patches. If you extract the contents of the milhouse tar, cd to a "clean" LibreELEC repository, then run <milhouse tar contents>/config/ it will apply all of my patches to the repository.

    Fortunately it sounds like you've now got a working build - I've lost count of the number of clean builds I've had to make over the last week! :(

    I've started looking at a new mainline 4.17 kernel for Generic, with AMD DC support - the branch is here: Comparing LibreELEC:master...milhousevh:linux4170 · LibreELEC/ · GitHub - I may pinch some of your commits. :)

    I'll post a link to an initial 4.17 build later, as it would be good to get feedback from AMD GPU users.

    At the moment it is really looking bad for my LE 9.0 community build. I cant get a baseline. Every build has the same problem: just a kodi logo and after a while reboot or frozen. The OS is working, ssh too, xrandr showing connected displays ... But that is it.

    I did build now about 10 different version. Even fresh checkout from git does not work (does not even build without a extra PR).

    Do you mean LE master is not booting into Kodi with the 4.14.48 kernel? You will need to build with the sqlite shared PR2760, but with that PR you should have a successful build.

    The current LE master should is working on known-good CPUs, (ie. Skylake etc.). It should work on Coffee Lake, and might even work on Gemini Lake. For Ryzen, it should work, but Vega isn't supported until 4.17.y. Like you I have none of this new hardware, so can only guess at what might not be working.

    If your builds are making it into Kodi and then crashing, there should be a crash log which might give some clues.

    Thanks, for your fast reply. My OS is Win10 Pro - 1803. I discovered, that if minimal version is set to smb1 then it is working. But I think It is a security risk.

    So when you said "It is impossible to connect to RPi" what you actually meant was "I can't see the RPi when browsing the network", correct?

    Network browsing no longer works (and this has been pointed out so many times), as it requires SMB1 which you should not use. Ever. You should not even leave SMB1 enabled in your Windows 10 machine, as SMB1 is a security risk _even when you don't use SMB1_.

    Get used to entering the \\ipaddress as donbrew has pointed out.

    Tried set minimal SMB to all versions and activate authentication, but no results.

    Please be _very_ clear about what you have tried, what the problem is, and what clients are involved.

    What is your client - is it a Windows PC? What version - is it Windows 10 with the latest 1803 update?

    Where did you activate authentication? Activating authentication in the client won't have any effect when accessing the LibreELEC Samba Server, but you may need to activate authentication in the LibreELEC Samba Server if your client (whatever that is, because we don't know) now enforces authentication when accessing shares.

    You should leave the SMB versions at default, as min=SMB2 should be supported by all but the oldest clients.

    I just made new install latest Libre elec on Pi3+ , no SAMBA , I'm with Win 7 , tried to find some tutorial - no any success . Any help ?

    We don't even know what the problem is - are you having a problem accessing your Windows share from LibreELEC, or are you having a problem accessing the LibreELEC shares from Windows?

    Assuming the former, have you read the blog which explains you must now enable authentication when accessing the Windows share (create a username/password in Windows, add this user to your Windows share, use this username/password when accessing the Windows share from LibreELEC).

    I tried on the W7 pc, I turned on sharing needing a password (Change Advanced Sharing Settings) but it never asks for a password in any menu I can find.

    Windows allows you to set the password of a user when you create the new Windows user - that's where you set the password, in the Windows "User Accounts" Control Panel. If you haven't created a user *with a password* then you won't be able to authenticate using SMB when connecting to a Windows share as Microsoft recently made authentication mandatory. Once you've created the Windows user with a password, add this user to your Windows share with the relevant Windows file permissions.

    When you access the share from LibreELEC (with default settings) you should then use the new Windows username/password for authentication.

    Also, you have posted the contents of your passwords.xml where you appear to be using a username/password of kodi:kodi (all lowercase), but then in one of your Windows screenshots you've added a user called Kodi (uppercase K), and in yet another screenshot you're using a user called libreelec. This conflicting information doesn't make solving this issue any easier, but points more strongly towards an incorrect configuration.

    If you've tried accessing the Windows 10 share from Windows 7 and you are not being prompted for a username/password in Windows 7, then you have not configured the Windows 10 share correctly.

    If Windows 7 can't access the share then then chances are something is hosed on your Windows 10 PC, perhaps you've twiddled one too many random knobs.

    durnehviir so there's no confusion, are you having a problem booting the USB flash drive (the "installer"), or are you having problems booting from your internal hard drive after the "installer" has installed LibreELEC to the hard drive? If the latter can you tell me which of these two files you have on the HDD: /flash/extlinux.conf or /flash/syslinux.cfg.

    Also, can you paste the output from the following command when you boot LE from your HDD:

    1. ls -la /sys/firmware/efi