Posts by kurai

Never mind - dug out an old USB 1GbE adapter (also Realtek, as it happens) and a network connection was achieved.

Created the log batch from the Logfiles share - attached here log-2023-12-09-15.40.59.zip (300KB)

The onboard 2.5GbE ethernet devices (eth0 & eth1) both seem to be detected and started without errors that I can see, but for some reason they don't show up in LE/Kodi.

My previously working device on the older nightly builds is eth1.

The temporary 1GbE USB adapter is eth2.

Can anyone see why eth1 isn't working ?

Hi.

Since about mid November the nightly 12.0 Generic builds have resulted in a booted & running LE/Kodi system, but no networking.

Device is an Odroid H3+ (N6005 Celeron) with onboard Realtek RTL8125B (2.5GbE) LAN ports.

The LE settings addon shows no available network devices in Connections.

I tried the "System and Kodi Backup" option in the addon to dump a backup to a removable drive to inspect on another system, but the function doesn't store any useful logs from Kodi or OS.

Given that there seems not to be any method to access a local console shell with attached keyboard in the 12.0 Generic builds I can't access any OS level logs at all to start digging into what exactly is failing.

Any suggestions ?

Was about to report this breaking Multi-Weather addon as trying to display downloaded map gave same _imaging.so error...

Good to see it's already in hand.

The GitHub pull #7891 [samba: samba-config: call smbpasswd with valid smb.conf] in the latest (20230619-a2c7d54) nightly looks like it's done the trick.

Thank you.

Nope - having 2 memory modules will help performance a *little* on low end/low power machines that have dual channel RAM capability, but Kodi will almost never use more than 2 GB of it.

mglae Thanks for the workaround suggestion.

Yes - the problem seems to be that at boot time the ExecStart=/usr/lib/samba/samba-config initiated from samba-config.service failes to create (or create in time ??) the /run/samba/smbpasswd that smbd is looking for during startsmbfilepwent_internal , so smbd recreates an empty smbpasswd file.

Executing /usr/lib/samba/samba-config later in an SSH session *does* create a proper /run/samba/smbpasswd

So, my question is ... how do I ensure that a populated smbpasswd file is created and|or created in time for smbd to find ?

I'm using LibreELEC-Generic.x86_64-12.0-nightly-20230522-794a8ad, and it's still an issue.

Seems entries in /run/samba/smbpasswd are not persisting after reboot.

I'm getting somewhat lost with the auto-assembly of the final samba config in /run/samba from various other files scattered around the install.

Between /storage/.config/samba.conf , /storage/.kodi/.smb/smb.conf , /storage/.cache/services/samba.conf (and any I've missed) where/what should I be doing so that the smbpasswd username/password entered via LibreELEC-Settings->Services is populated after next boot ?

Cheers,

--

kurai

It's back now - thank you Mysterious Masked Janitor for whatever it was you did.

This *does* normally work, but the server isn't offering up a download list at the moment.

It occasionally fills up it's diskspace and needs someone to check what it's done and tidy up, as and when they have time.

Never mind - booted from a some linux live OS USB stick and did it from console there.

Told you I was too tired - once I accepted that I had spent *waaaay* too long trying to futz around doing it with only LibreElec/Kodi things and dug out the bag of random USB stuff it took 2 minutes

Aaargh - after doing some work getting some new skin code to work on the LE Nightly, I used the restore function of the Backup plugin to quickly wipe/reset my changes.

Turns out the plugin doesn't (or can't ?) honour the permissions settings of /storage/.cache/ssh/

Now I can't get back into console as the SSHD bails after complaining the permissions are too open.

It's late, and my brain isn't working properly any more - is there *any* way or workaround to change the permissions via the UI/file-manager or local keyboard access ?

Or otherwise get a local console going, since there's a keyboard and mouse connected to the machine.

I'm on the Generic Nightly, & CTRL+ALT+F3 doesn't work, neither does the web-console from systemtools addon.

Any advice welcome as I'm clearly too tired to be thinking coherently

I have an N6005 device - pretty much the same thing but clocked a little higher and it works fine on Generic LE11 Kodi 20 (Nexus) - even HDR.

There were a lot of updates to the kernel for Jasper Lake series iGPU happening during the Kodi 19 (Matrix) development cycle.

Try the Generic-legacy version if you want to stay with LE10/Kodi19 (that worked fine from the start, only without HDR functionality)

Have you also added the mapping of the Harmony Clear button-send to the Kodi Delete function in .Kodi\userdata\keymaps\keymap.xml ?

In the Harmony software I have the Clear button set to send the Clear keypress and change it's function, once received, in the keymap instead.

e.g. snippets from my keymap.xml

...
  <MyFiles>
    <remote>
      <clear>Delete</clear>
      <zero>Highlight</zero>
      <star>Move</star>
      <hash>Rename</hash>
      <menu>ContextMenu</menu>
    </remote>
  </MyFiles>
...
  <MyMusicPlaylist>
    <remote>
      <clear>Delete</clear>
    </remote>
  </MyMusicPlaylist>
...
  <MyVideoLibrary>
    <remote>
      <zero>Queue</zero>
      <clear>Delete</clear>
      <menu>ContextMenu</menu>
     </remote>
  </MyVideoLibrary>
...
  <MyVideoPlaylist>
    <remote>
      <clear>Delete</clear>
      <zero>Delete</zero>
    </remote>
  </MyVideoPlaylist>
...
etc.

I'm using the Harmony Hub + RF remote + IR blaster to USB MCE receiver but the principle should be the same with Harmony 665 + Flirc IR receiver.

RSS 2.0 feed confirmed as working for me on Nightlies & Nexus 11 Beta 1 builds with the (now ancient) Kodi RSS ticker.

Nice one

Great news CvH

The ticker was usually the way I heard about significant updates/developments first, since I would often miss inbuilt updater notifications and I am otherwise not checking the site/forums all that often ... unless I encounter an issue or just randomly remember to check in, once in a while.

I am very much of the "if it Just Works[tm]" ... leave it alone until it doesn't ... mindset

There are downsides to this - I recently made a query in the Bug Report section about something and it turned out the root cause was me leaving in an old advancedsettings.xml entry that hasn't been relevant/useful for *at least* 3 hardware platform updates that I've gone through

Well ... that was quick, once I had my wrong-headed assumption challenged and re-calibrated my brain.

This was the culprit, in advancedsettings.xml

<gui>
   <algorithmdirtyregions>2</algorithmdirtyregions>
</gui>

That was a bit of left-over lint from at least 2 hardware upgrades back.

Thank you.