CoreELEC 20.0-Nexus_alpha3 Discussion

Only through samba for latest nexus alpha 3 from oct 10?
Can you update CoreELEC git hub with image
Sept 22 is last date.

Or post in this thread

Okay
Tried 3 times samba
First time rookie mistakes
Where is tar file located?

Ive done something wrong
Srarts update
Found new Tar file

Missing system/kernel message
Then restarts in safe mode

Hard to tell what went wrong. Reboot again and it should be fine.

Nexus Nightly 20221006 - Setting ‘Force colour subsampling’ to ‘4:2:0’ causes loss of/no signal on video playback. All other options work fine.

20221006 is buggy and not usable, update to 20221007

Still broken in 20221007.

Also SSH is broken, when I connect it asks for my password and after I enter it it just closes the connection.

roidy@Roberts-MacBook-Air ~ % ssh root@192.168.0.13
root@192.168.0.13's password: 
##############################################
#                  CoreELEC                  #
#            https://coreelec.org            #
##############################################

CoreELEC (official): 20.0-Nexus_nightly_20221007 (Amlogic-ng.arm)
-sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Connection to 192.168.0.13 closed.
roidy@Roberts-MacBook-Air ~ %

SSH works fine after update with this build.
Try

ssh -v root@192.168.0.13

Definitely doesn’t work fine for me :frowning:

Tried from both Windows 11 and OSX

PS C:\Users\roidy> ssh -v root@192.168.0.13
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug1: Connecting to 192.168.0.13 [192.168.0.13] port 22.
debug1: Connection established.
debug1: identity file C:\\Users\\roidy/.ssh/id_rsa type -1
debug1: identity file C:\\Users\\roidy/.ssh/id_rsa-cert type -1
debug1: identity file C:\\Users\\roidy/.ssh/id_dsa type -1
debug1: identity file C:\\Users\\roidy/.ssh/id_dsa-cert type -1
debug1: identity file C:\\Users\\roidy/.ssh/id_ecdsa type -1
debug1: identity file C:\\Users\\roidy/.ssh/id_ecdsa-cert type -1
debug1: identity file C:\\Users\\roidy/.ssh/id_ed25519 type -1
debug1: identity file C:\\Users\\roidy/.ssh/id_ed25519-cert type -1
debug1: identity file C:\\Users\\roidy/.ssh/id_xmss type -1
debug1: identity file C:\\Users\\roidy/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_9.1
debug1: match: OpenSSH_9.1 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.0.13:22 as 'root'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:sQH43CHMAO8Y1UP9pycmX8N4NJE1QJnAKll6vVyDcZE
debug1: Host '192.168.0.13' is known and matches the ECDSA host key.
debug1: Found key in C:\\Users\\roidy/.ssh/known_hosts:14
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directory
debug1: Will attempt key: C:\\Users\\roidy/.ssh/id_rsa
debug1: Will attempt key: C:\\Users\\roidy/.ssh/id_dsa
debug1: Will attempt key: C:\\Users\\roidy/.ssh/id_ecdsa
debug1: Will attempt key: C:\\Users\\roidy/.ssh/id_ed25519
debug1: Will attempt key: C:\\Users\\roidy/.ssh/id_xmss
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,sk-ssh-ed25519@openssh.com,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com,webauthn-sk-ecdsa-sha2-nistp256@openssh.com>
debug1: kex_input_ext_info: publickey-hostbound@openssh.com (unrecognised)
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: C:\\Users\\roidy/.ssh/id_rsa
debug1: Trying private key: C:\\Users\\roidy/.ssh/id_dsa
debug1: Trying private key: C:\\Users\\roidy/.ssh/id_ecdsa
debug1: Trying private key: C:\\Users\\roidy/.ssh/id_ed25519
debug1: Trying private key: C:\\Users\\roidy/.ssh/id_xmss
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
debug1: read_passphrase: can't open /dev/tty: No such file or directory
root@192.168.0.13's password:
debug1: Authentication succeeded (password).
Authenticated to 192.168.0.13 ([192.168.0.13]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: ENABLE_VIRTUAL_TERMINAL_INPUT is supported. Reading the VTSequence from console
debug1: ENABLE_VIRTUAL_TERMINAL_PROCESSING is supported. Console supports the ansi parsing
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug1: client_input_channel_req: channel 0 rtype exit-signal reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
##############################################
#                  CoreELEC                  #
#            https://coreelec.org            #
##############################################

CoreELEC (official): 20.0-Nexus_nightly_20221007 (Amlogic-ng.arm)
-sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
debug1: channel 0: free: client-session, nchannels 1
Connection to 192.168.0.13 closed.
Transferred: sent 1976, received 3024 bytes, in 0.1 seconds
Bytes per second: sent 20231.0, received 30960.8
debug1: Exit status -1
PS C:\Users\roidy>

Then it must be something on your device and some script is run on login. Maybe from profile.

I use the N2 daily for skin development and I am always SSH’d into it with no problems.

The only thing to change on my device is the installation of 20221006 followed by the installation of 20221007.

Also ‘Force colour subsampling’ to ‘4:2:0’ is also still broken on 20221007

Is there a nightly before 20221006 I can roll back to for testing?

I updated back to 20221006 and SSH works. Updated again to 20221007 and SSH still works.

Try with

ssh root@192.168.0.13 "bash --noprofile"

Yep, that connects but I get no terminal prompt, just a flashing cursor. However it is connected and I can issue commands.

When I try to login normally I get this warning, could that be the reason?

-sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)

http://coreelec.relkai.org

Thanks, but they are all 19.5’s I need 20.0

Use the link at the bottom for the nightly web site

Thanks, but the nightly site only has the current and the one before, currently 7th Oct and 6th Oct, both of which I already have. I need an older Nexus nightly.

You need to update you ssh_config file. You have clearly set some environment variables that are passed to ssh. Drop them and it will work.

SendEnv
             Specifies what variables from the local environ(7) should
             be sent to the server.  The server must also support it,
             and the server must be configured to accept these
             environment variables.  Note that the TERM environment
             variable is always sent whenever a pseudo-terminal is
             requested as it is required by the protocol.  Refer to
             AcceptEnv in sshd_config(5) for how to configure the
             server.  Variables are specified by name, which may contain
             wildcard characters.  Multiple environment variables may be
             separated by whitespace or spread across multiple SendEnv
             directives.

             See PATTERNS for more information on patterns.

             It is possible to clear previously set SendEnv variable
             names by prefixing patterns with -.  The default is not to
             send any environment variables.

Where do I find the ssh_config file?

I wouldn’t even know how to set ssh enviroment variables :frowning:

SSH worked perfectly until I updated to 20221006 and 20221007, now I get a warning about setlocale and no conection.