Posts by milhouse

OK thanks, we're looking into it.

Quote from mac89

I have copied the libreelec tar file from the folder update by manual,

You mean you have copied the tar file into the "Update" Samba share?

Quote from mac89

openelec notifies me of the update, but when I reboot, nothing happens like that?

OpenELEC will only notify you about OpenELEC updates, any notification will have nothing to do with anything copied into the "Update" folder.

If you're rebooting OpenELEC and it's not applying the LibreELEC upgrade tar copied into the "Update" folder then OpenELEC is either not finding anything to upgrade with (you've copied the LE tar into the wrong folder) or OpenELEC is showing you an error/failure during the upgrade which you are not mentioning.

Quote from Krautmaster

But any how, im not able to install any addon like tvheadend in 8.2. Maybe a temporary repo issue?

Please post your Kodi debug log after you have tried (and failed) to install one of these addons.

You can also add "textmode" to the kernel command line.

Quote from shaggy996

Im not sure if you started your replay as soon as soon as I posted or did not read my post. Right after the post I edited in more info on the setup.

Nope, hadn't seen it.

Quote from shaggy996

As I said a windows 7 computer sharing folders on an open samba, no username or password.

Issue #2, "Anonymous access no longer works".

Quote from shaggy996

Now when I go to add a share and brows on kodi it does not even see the workgroup

Issue #3, "Network browsing no longer works".

Quote from shaggy996

I have already changed the minimum version to smb v1 and have tried every combination.

Resolve issue #2 (already explained, many times), and learn to live with issue #3 (already explained, many times).

Use "None" for "Maximum protocol" when Windows 7 is the Samba server

If you still have problems after resolving #2: What are you adding as the network location - a screenshot of your "Add network location" dialog please (or paste the contents of your /storage/.kodi/userdata/sources.xml). Also, the error when you try to connect to the share in your kodi debug log might be helpful.

The RPi3 will take at least 2.5 minutes (quite possibly longer) to write up to 1GB RAM to a hibernation file/partition (writing at up to 7MB/s on SD card, and most SD cards will be slower than this), so maybe it's working but it's just not a practical solution because it just takes forever to save the hibernation state.

Saving a small amount of state on shutdown and restoring same on power up would get you most of what you want without waiting while 1GB of RAM is dribbled out to SD card, but you'd need to speak to the Lakka developers about this as I'm not sure what applications they use or what the apps are capable of.

Quote from shaggy996

I never created anything file wise. I installed libreelec using a usb drive installer, started it and went in through the file section in kodi and added samba shares.

Samba shares added in Kodi have nothing to do with the "samba config file" which is for the LibreELEC Samba server and should only be modified by users that understand what it is they are modifying. You're conflating a different issue with whatever problem you have.

Quote from shaggy996

So if i go into the file section and delete the shares and restart it will fix it?

I've no idea what your problem is as you haven't mentioned anything useful, so I can't even hazard a guess as to whether what you suggest will work or not (it probably won't, actually).

If you've got a problem accessing your Samba shares then provide details of your Samba server (make, model, version) and what the problem is. Nobody here knows what server(s) you run in your network, or how they may be configured, or what updates have been applied by you which may or may not have disabled certain Samba-related features. I know for a fact that LibreELEC 8.1.2.will work out of the box with the vast majority of Samba servers, but there are some broken Samba servers that need to be worked around (or contact your vendor for an updated server), and there are some features (anonymous access, network browsing) that are no longer supported.

I'll repeat what is already stated in the announcement when dealing with Samba client issues:

1. Try forcing SMB1 in Kodi Settings > Services > SMB Client > Maximum protocol version. SMB1 should work with old and buggy servers, but won't work with more secure modern Samba servers that only support SMB2+ (in which case use SMB2 or SMB3, or better yet leave it as None so that the client - ie. Kodi - auto-negotiates the best protocol).

2. Anonymous access no longer works. You'll now have to configure a username/password in your server, then enter the same username/password details into Kodi when accessing the share and prompted for authentication.

3. Network browsing no longer works when SMB1 is disabled in your master browser (and is flaky at best even when it is). You'll now need to add a network location before adding your Sources.

Quote from shaggy996

But no one even goes about explaining how to replace your samba config file. All that is said is to replace it with the new one and there is no info at all on how to actually do this.

It's a file that you created - use whatever method you used when you originally created it.

Quote from giannia

I'm seeing a switch to a new repo for the rtl8812au driver on #1012 build. Are there any news? Is AC protocol full supported again? Thanks.

This switch is mainly to allow the building of RTL8814AU - the benefits for RTL8812AU are unknown and will need to be determined. Hopefully the new repository is similar to the old repository, just better maintained. If you find new problems with this RTL8812AU driver please shout.

Quote from SkywalkerPD

The thing I changed, can someone tell me how to get these back to default?

rm /storage/.config/modprobe.d/8812au.conf
reboot

It may do, power management usually causes problems and makes no real sense on mains powered devices. However the RTL8812AU module is being built with power saving disabled, unless that's no longer supported.

LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub

I find it quite stable, though some addons may be broken (mainly game). You can try it, and if you don't like it it's easy enough to downgrade back to an official release.

No, not possible unless you're prepared to build LibreELE 8.1.2 yourself with the alternative driver repository.

Kodi forum is now back, please continue discussion there - this thread is no longer being monitored/updated (unless the Kodi forum disappears again!)

Kodi forum is now back, please continue discussion there - this thread is no longer being monitored/updated (unless the Kodi forum disappears again!)

Can you paste links to your kodi debug log and "journalctl -a" using the latest build.

Have you updated the tvheadend addon? Addons

There were two new commits in the tvheadend42 #1002 build (2 Oct 2017): Commits · tvheadend/tvheadend · GitHub

When did the tvheadend crashing start, with #1002? Try rolling back to tvheadend #1001 and see if that has any effect.

Yes the swap won't be required on a clean install, but may be of benefit once you load up the system with Docker etc. Also this #0928b debug-enabled build will use more RAM than a stripped down non-debug/release build, however I believe you were experiencing freezes on non-debug builds so 128MB of swap may prove useful in the long run (although obviously we would like to get to the bottom of the crashes so that they don't happen!)

Thanks, no under voltage, frequency cap or thermal throttling so looks like we can rule out PSU as well.

Your latest crash is in PERIPHERALS::CPeripheralAddon::ProcessEvents again, which is weird as you have no controllers attached.