Kodi only supports SMB1 at the moment, so in order to use SMB2 you will need to mount using the kernel cifs driver. This can be done using mount in autostart.sh or a systemd service unit.
You'll need to specify "cifs" filesystem and "vers=2.0" option.
I'm guessing because he did a new install and SSH isn't enabled by default.
CTRL+ALT+F3 should give you a console. What GPU do you have?
The update channels will install regular builds, use the update folder.
It's supposed to be empty. The file is called xorg-configure, the nvidia-legacy part is the argument.
The autostart trick should work for those who have a card supported by nvidia legacy 340.102. The only difference in my build regarding this is I've updated the kernel and added patches for the legacy driver to compile. I'm guessing the same issue will be present in LE9.
The skin sounds were changed to the scroll sound from the default ES theme (simple-dark). You can't actually change them due to the read-only nature of LE, but you could copy the estuary theme from /usr/share/kodi/addons to /storage/.kodi/addons and replace the sounds there.
New build 20170528 has been uploaded that fixes the cherry trail / tronsmart x5 plus pcm issue (updated alsa-lib).
I guess it could be done. An udev rule could say identify older legacy gpu's by pci id and automatically download an addon with the drivers. Would't work without an internet connection though and seems like not an ideal approach. Also I think nobody (in ELEC world) cares enough about that old gpus. I'm just speculating though, better go ask in the feature request section.
Guide how to use the older drivers:
1. Follow official instructions how to get the source of LE8
2. Modify packages/x11/driver/xf86-video-nvidia-legacy/package.mk and downgrade the version
2. Scour the internet and find info on what patches are needed for compiling with 4.9 kernel and then put them in packages/x11/driver/xf86-video-nvidia-legacy/patches/
3. Build
Very simplified but that's basically it 
LE8 switched to 340.xx legacy drivers, older cards won't work. 304.xx is simply not included anymore. I doubt it will be added either as it would add a lot of bulk to the image.
Yeah, I have the same box and noticed the same thing. Wonder if it's got to do with the upgrade to 4.11. It seems PCM is broken, but on the plus side passthrough is now working (if you have a receiver that is).
Sure, you can add your own shortcuts to launch retroarch.sh or emulationstation.sh. As for gamecontrollers, I have ds4 and that's what I'm supporting. You're on your own setting up something else, as long as it's paired and picked up by the kernel as a normal HID device it should configure in any app.
Doesn't look like the X server is configured properly as it's not trying to load the nvidia module. Have a look at the script that was put in your autostart.sh to see how it works and perhaps you can figure it out.
I can't see any gpu there guess that "explains" it.
Edit: im blind i see it now.
1. It's based on LE8, but has lots of changes. All the drivers are included, also I use an updated display driver stack (i.e. updated mesa and kernel).
2. No.
3. I have the same issue some times, switching to a different source on the AVR and then back gives me back the picture though. I believe this bug is with the intel ddx driver, possibly a workaround could be to use the X.org modesetting driver. Or disable the use of KMS as described on the first page.
New build 20170526:
- Linux 4.11.3
- Added fix for NVIDIA GT1030 autodetectionForgot to post about yesterday's 20170525 build, which had Kodi 17.3 and SABnzbd 2.0.1.
Here's the udev rule that decides whether or not you have an nvidia card: LibreELEC.tv/96-nvidia.rules at master · LibreELEC/LibreELEC.tv · GitHub
Any device with vendor id 0x10de will be treated as an nvidia card, then any card not listed with an id will get the legacy driver. I'm assuming your older ION gpu has a different vendor id, but that doesn't really explain why it works for you in vanilla LE.
If you access the logfiles share through smb a new logfile should have been generated, as the script "createlog" is run on each access and that's what put the logfiles in there. I was interested in the pci id of your card, I guess the output of "lspci -nn" should be sufficient as well.
Although they might have a responsibility (which they have already taken care of by working on a new version), they do not IMO have a responsibility to do it faster.
15 days, 28 days, so? They are still a small team, and considerations needs to be taken when doing releases for thousands of users. Sure they can improve (and I'm guessing they will), but demands have no place in an open source project, nobody owes you anything.
Would probably be nice to have, I agree. But demanding it and calling people rude if you don't get it would be inappropriate.
Nobody said that, it was stated 17.3 was on the way and one (rude) user was informed that building was a possibility. If this was a closed source product the user would have no such option. The "go fix it yourself" attitude you talk about was simply offered to someone who was not happy with the FREE work being done.
It's rude to suggest users to build it yourself while you yourself know how hard it is for an inexperienced user to build. Team LibreELEC and Team Kodi needs to care more about security issues. For now it's like: " I don't care about your issues, take care of it yourself!". Remember you have a responsibility.
What do you mean they have a responsibility? The LE team stated that they were waiting for 17.3 which was just around the corner. Are you saying they have a responsibility to fix it faster than say 24 hours? You're forgetting that they are a small team doing this for FREE, in their spare time. Nobody said they weren't going to fix it, or that they didn't care. I have not seen any text on their website promising security updates faster than 24h.
I'm also curious how you find it rude to suggest building? I disagree that it's so hard, simply building it is extremely easy. Knowing how to update the kodi package.mk with the correct githash might be a challenge for a novice, but I'm sure if someone were to create a thread asking how to do this they would get help. It's an open source project. They are friendly to others submitting PR's and participating. You are getting this wonderful product for FREE. I find it very disrespectful for you to call them rude. If you can do a better job, why aren't you?
Note that although my tag says developer, I'm not a member of the team. My thoughts on this are mine alone.
Provide logs from the "Logfiles" SMB share. Try this command in ssh:
echo "rm /var/run/xorg-configure.done && /usr/lib/xorg/xorg-configure nvidia-legacy" > /storage/.config/autostart.shIf that doesn't work, remove autostart.sh.
Also consider getting a GPU that's not ancient. I'm guessing your issue is autodetection is failing because the pci id is not included anymore in the official nvidia drivers (which LE uses to detect your card). In that case the workaround above should work as long as your card is supported by the legacy driver.
It's being worked on:
smbclient: cleanup smbclient configuration by chewitt · Pull Request #12110 · xbmc/xbmc · GitHub
I believe Milhouse have been including it in his builds for a while. I gave the backported Krypton PR a shot in my build and was able to connect directly to shares with SMB2 through Kodi, but browsing didn't work.