Posts by ekerose

Quote from chewitt

Please update it to something current and try again..

Hi.

I have updated to the latest version of putty, 0.78, and it gives the same error.

Quote from chewitt

Recent version of PuTTY?

No, it is old, the one I already had on my PC: Release 0.73.

Quote from chewitt

Random suggestion .. use Notepad++ to edit the file, not Notepad or Wordpad - if you're a Windows user?

Yes, i'm Windows user and my default text editor is notepad++, and the only diference between to clean installs was type ssh on uenv.

Tested again with 20221218 nightly, burn with libreelec sd creator and uenv edited with notepad++

adding ssh to unev -> ssh error connection

activate ssh from menu -> ssh works

Quote from chewitt

Code

Dec 08 22:01:19.029867 LibreELEC systemd-tmpfiles[372]: Failed to create directory or subvolume "/root", ignoring: Read-only file system
Dec 08 22:01:19.030097 LibreELEC systemd-tmpfiles[372]: Failed to open path '/root', ignoring: No such file or directory
Dec 08 22:01:19.042294 LibreELEC systemd-tmpfiles[372]: Detected unsafe path transition /storage (owned by 1023) → /storage/.cache (owned by root) during canonicalization of /storage/.cache.
Dec 08 22:01:19.042863 LibreELEC systemd-tmpfiles[372]: Detected unsafe path transition /storage (owned by 1023) → /storage/.cache (owned by root) during canonicalization of /storage/.cache.
Dec 08 22:01:19.043498 LibreELEC systemd-tmpfiles[372]: Detected unsafe path transition /storage (owned by 1023) → /storage/.cache (owned by root) during canonicalization of /storage/.cache.
Dec 08 22:01:19.045806 LibreELEC systemd-tmpfiles[372]: Detected unsafe path transition /storage (owned by 1023) → /storage/.cache (owned by root) during canonicalization of /storage/.cache.
Dec 08 22:01:19.046319 LibreELEC systemd-tmpfiles[372]: Detected unsafe path transition /storage (owned by 1023) → /storage/.cache (owned by root) during canonicalization of /storage/.cache.
Dec 08 22:01:19.047311 LibreELEC systemd-tmpfiles[372]: Detected unsafe path transition /storage (owned by 1023) → /storage/.cache (owned by root) during canonicalization of /storage/.cache.
Dec 08 22:01:19.048826 LibreELEC systemd-tmpfiles[372]: Detected unsafe path transition /storage (owned by 1023) → /storage/.cache (owned by root) during canonicalization of /storage/.cache.

ekerose ^ this makes me wonder if examining the SD card in another OS has borked ownership of /storage. I have a hunch sshd is preventing the creation of keys belonging to root (user 0) in folders owned by another user (1023, who doesn't exist in LE).

Hi

That log was from a clean install, I downloaded the image and burned it with rufus. The only access was to the fat32 partition to modify uenv.ini to assign the correct dtb and activate ssh.

I did a few tests

* clean install with LibreELEC.USB-SD.Creator.Win32 , add dtb and ssh to uenv -> ssh does not work

* clean install with LibreELEC.USB-SD.Creator.Win32 , add dtb and activate ssh from the libreelec interface -> ssh works

The problem I suspect appears when in uenv.ini you force ssh.

Quote from chewitt

The logs show this endlessly repeating:

Dec 11 16:06:02 LibreELEC-Penka systemd[1]: Starting sshd.service...

Dec 11 16:06:02 LibreELEC-Penka ssh-keygen[5065]: ssh-keygen: generating new host keys: RSA Could not save your private key in /storage/.cache/ssh/ssh_host_rsa_key.XXXXl8cxAN: No such file or directory

Dec 11 16:06:02 LibreELEC-Penka ssh-keygen[5065]: ssh-keygen: generating new host keys: ECDSA Could not save your private key in /storage/.cache/ssh/ssh_host_ecdsa_key.XXXXl7zlJv: No such file or directory

Dec 11 16:06:02 LibreELEC-Penka ssh-keygen[5065]: ssh-keygen: generating new host keys: ED25519 Could not save your private key in /storage/.cache/ssh/ssh_host_ed25519_key.XXXXAdmsHi: No such file or directory

The /storage/.cache/ssh directory should be created on first boot automatically so I've no idea how that can happen.

NB: I've not made any changes to Ethernet support in the 6.0.x kernel but perhaps there are general cleanups that improve things.

Display More

Hi.

Last week I commented that I could not access via SSH, I have recorded the latest nightly for the gt1 ultimate and I get the same error in the log.

I manually created the /storage/.cache/ssh folder by mounting the microSD on my pc and now the ssh works.

I add my log in case it helps:

http://ix.io/4iF3

Dec 15 11:46:59.645898 LibreELEC ssh-keygen[965]: ssh-keygen: generating new host keys: RSA Could not save your private key in /storage/.cache/ssh/ssh_host_rsa_key.XXXXCRjSRX: No such file or directory

Dec 15 11:46:59.647527 LibreELEC ssh-keygen[965]: ssh-keygen: generating new host keys: ECDSA Could not save your private key in /storage/.cache/ssh/ssh_host_ecdsa_key.XXXXEPqnNC: No such file or directory

Dec 15 11:46:59.647527 LibreELEC ssh-keygen[965]: ssh-keygen: generating new host keys: ED25519 Could not save your private key in /storage/.cache/ssh/ssh_host_ed25519_key.XXXXp1Gvap: No such file or directory

Hi all.

After a some time I have installed libreelec on a SD to see if I can use my Beelink GT1 ultimate with a more updated system.

I have put the dtb in the uenv.ini and activated the SSH from that same file. In Kodi options appears as active and let me modify the password, but when I try to connect from the pc with putty gives me connection refused error. Is there any other parameter to activate for the ssh to work.

I have also tried the tvheadend client; for 1080 video it works perfect, but for other resolutions I only get audio and no video. Is this a known bug in the drivers or should I attach a log?

I have used the latest beta available today:

regards

Thanks!

I will check nightlies from time to time to test it when it appears.

Regards

Quote from chewitt

FUSE was historically used in the OS for NTFS and exFAT drivers. From our perspective it is no longer required as recent kernels have native drivers for both. I don't recall it being removed, but it's quite plausible that it's been dropped - and I wouldn't expect it to return. NB: That distro has deliberate "native" support for features which are strongly associated with piracy use-cases. Users might not care but we do.

I understand the developers' point of view about pirate uses of LE, even though it implies limiting legitimate uses of the system.

I am not the right person for this discussion and I consider my question closed.

Thank you very much for answering so clearly.

Regards.

Quote from chewitt

I assume you're asking for help in here because the CE devs have no interest in supporting the piracy-ridden fork that rips off their efforts that you installed on your box. I'm equally disiniterested for a) the same reasons, b) because it's not even a fork of the modern-kernel codebase that LE uses today.

NB: As a random coincidence I created a device-tree for GT1-Ultimate earlier today for one of the Manjaro ARM devs to use, so support for the box should filter through to LE11 nightlies sometime soon.

Hi.

I use that fork because it has tvheadend as native service and gives better performance than with coreelec/libreelec.

Coreelec no longer supports S912 and libreelec does, that's why I was trying it.

Fuse is available in previous libreelec versions, but not in libreelec 20 and my question was if fusermount is going to be implemented.

I had no interest in getting into discussions about whether it is a pirate fork or simila,simply i was using becose it was giving better performance in my case,,

Sorry if the question has felt wrong.

P.S. I am not asking for support for any fork, the question was about LE and I was explaining my current installation. I think my low level of English has led to misunderstandings.

Regards

Hello.

I have a Beelink GT1 Ultimate (gxm_q200) currently running Alexelec(coreelec fork) on SD.

The system boots correctly with the LE nightly and tvheadend can play content sent from another box.

The problem is when trying to mount a rclone unit as a service since fuse/fusermount is not included in libreelec.

Copying the fusermount binary in the same folder as rclone I can mount the unit (from putty with the command ./rclone mount remote: /storage/rclone/) it works, but when creating a service it gives the error :Fatal error: failed to mount FUSE fs: fusermount: exec: "fusermount": executable file not found in $PATH.

Searching in the forum I found references to add folders to the PATH (PATH=$PATH:/usr/storage/fuse) in /storage/fuse is the fusermount binary, but the error continues.

I am a windows user and my linux knowledge is non-existent, any help is welcome.

Best regards.