[Librem-5-dev] queries with dev kit environment set up

Sat May 25 16:15:41 PDT 2019

I think this is the last couple of questions from me on this page.

I have successfully reflashed the eMMC and that has all worked. Setting
up the HDMI does not appear to work though.

 * I have performed the change at [1] but this does not bring up the
   HDMI connection and the on-board display remains on.
 * The second issue is how to get rsi_sdio to load at boot. I have
   added rsi_sdio to /etc/modules, but it remains unloaded, leaving wi-
   fi off without manual intervention. The wi-fi switch is correctly
   positioned and wi-fi works fine after modprobing rsi_sdio.

thanks
Dan

[1]
https://developer.puri.sm/Librem5/Development_Environment/Boards/imx8.html#hdmi

On Sun, 2019-05-26 at 07:39 +0930, Dan Kortschak wrote:
> Hi Angus,
> 
> Yes, I've been sudoing to do admin tasks.
> 
> I have just tried removing the ssh_host* keys and that has fixed the
> problem. Thank you.
> 
> cheer
> Dan
> 
> On Sat, 2019-05-25 at 06:49 -0700, Angus Ainslie wrote:
> > Hi Dan,
> > 
> > On 2019-05-25 4:00 a.m., Dan Kortschak via Librem-5-dev wrote:
> > > Thanks Darota,
> > > 
> > > Yes, I am talking about the USB serial as described in the linked
> > > page[1]. There is says that root can login. This is not the case
> > > with
> > > my board.
> > > 
> > > > Debian GNU/Linux 10 pureos ttyGS0
> > > > 
> > > > pureos login: root
> > > > 
> > > > Login incorrect
> > > > pureos login: purism
> > > > Password: 
> > > > Last login: Sat May 25 07:51:32 UTC 2019 on ttyGS0
> > > > Linux pureos 4.18.11-gee84b30c #1 SMP PREEMPT Mon Mar 18
> > > > 11:29:53
> > > > PDT
> > > > 2019 aarch64
> > > > 
> > > > The programs included with the Debian GNU/Linux system are free
> > > > software;
> > > > the exact distribution terms for each program are described in
> > > > the
> > > > individual files in /usr/share/doc/*/copyright.
> > > > 
> > > > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the
> > > > extent
> > > > permitted by applicable law.
> > > > purism at pureos:~$ 
> > 
> > You can login as purism and then sudo for root tasks.
> > > 
> > > I have not yet got to the reflashing step. I will likely get to
> > > that
> > > tomorrow. The ssh login checks appear prior to that on the page
> > > and
> > > I
> > > am assuming that there is a sequence to the instructions (also
> > > note
> > > that DHCP appears to be set up on my board since the IP specified
> > > did
> > > not work and the IP that it did have fits within my local
> > > network's
> > > DHCP allocation range).
> > > 
> > > The ssh session does not complain about key mismatch when given
> > > -vvv
> > > (ssh to localhost after logging in via USB serial conn).
> > > 
> > > > purism at pureos:~$ ssh -vvv localhost
> > > > OpenSSH_7.9p1 Debian-10, OpenSSL 1.1.1b  26 Feb 2019
> > > > debug1: Reading configuration data /etc/ssh/ssh_config
> > > > debug1: /etc/ssh/ssh_config line 19: Applying options for *
> > > > debug2: resolving "localhost" port 22
> > > > debug2: ssh_connect_direct
> > > > debug1: Connecting to localhost [::1] port 22.
> > > > debug1: Connection established.
> > > > debug1: identity file /home/purism/.ssh/id_rsa type -1
> > > > debug1: identity file /home/purism/.ssh/id_rsa-cert type -1
> > > > debug1: identity file /home/purism/.ssh/id_dsa type -1
> > > > debug1: identity file /home/purism/.ssh/id_dsa-cert type -1
> > > > debug1: identity file /home/purism/.ssh/id_ecdsa type -1
> > > > debug1: identity file /home/purism/.ssh/id_ecdsa-cert type -1
> > > > debug1: identity file /home/purism/.ssh/id_ed25519 type -1
> > > > debug1: identity file /home/purism/.ssh/id_ed25519-cert type -1
> > > > debug1: identity file /home/purism/.ssh/id_xmss type -1
> > > > debug1: identity file /home/purism/.ssh/id_xmss-cert type -1
> > > > debug1: Local version string SSH-2.0-OpenSSH_7.9p1 Debian-10
> > > > debug1: Remote protocol version 2.0, remote software version
> > > > OpenSSH_7.9p1 Debian-10
> > > > debug1: match: OpenSSH_7.9p1 Debian-10 pat OpenSSH* compat
> > > > 0x04000000
> > > > debug2: fd 3 setting O_NONBLOCK
> > > > debug1: Authenticating to localhost:22 as 'purism'
> > > > debug3: send packet: type 20
> > > > debug1: SSH2_MSG_KEXINIT sent
> > > > Connection reset by ::1 port 22
> > 
> > Did you try deleting the host keys for the devkit ?
> > 
> > Cheers
> > 
> > Angus
> > 
> > > 
> > > thanks
> > > Dan
> > > 
> > > [1]
> > > 
> 
> 
https://developer.puri.sm/Librem5/Development_Environment/Boards/imx8.html#usb-console
> > > [2]
> > > 
> 
> 
https://developer.puri.sm/Librem5/Development_Environment/Boards/imx8.html#ethernet-connection
> > > 
> > > 
> > > On Sat, 2019-05-25 at 12:28 +0200, Dorota Czaplejewicz wrote:
> > > > Hi Dan,
> > > > 
> > > > I'll answer inline.
> > > > 
> > > > On Sat, 25 May 2019 17:38:04 +0930
> > > > Dan Kortschak via Librem-5-dev <
> > > > librem-5-dev at lists.community.puri.sm>
> > > > wrote:
> > > > 
> > > > > Apologies if this is not the correct place.
> > > > > 
> > > > > I received my dev kit very late due to shipping oversights
> > > > > and
> > > > > have
> > > > > only just started being able to get the device set up.
> > > > > 
> > > > > So far it is working, though there are discrepancies between
> > > > > what
> > > > > I'm
> > > > > seeing and the instructions at [1]. Both the serial
> > > > > connection
> > > > > and
> > > > > the
> > > > > ethernet conn communicate however:
> > > > > 
> > > > > 1. With the serial, the docs say that root can login. This is
> > > > > not
> > > > > the
> > > > > case failing at username entry (I imagine this is a policy
> > > > > change).
> > > > 
> > > > There are two serials; I assume you're talking about the USB
> > > > one,
> > > > since that's where we're waiting for the correct policy
> > > > upstream.
> > > > Either way, if you're confused, that's an oversight, and thanks
> > > > for
> > > > mentioning it!
> > > > > 2. More significantly, while I can use the ethernet conn to
> > > > > see
> > > > > out, I
> > > > > cannot ssh into the device; the connection is closed by the
> > > > > host.
> > > > > The
> > > > > same thing happens ssh localhost from the device. I've looked
> > > > > at
> > > > > sshd_config and I don't see any difference between it there
> > > > > and
> > > > > on
> > > > > my
> > > > > laptop which is working fine. It's been a long time since
> > > > > I've
> > > > > manually
> > > > > set up a sshd so I'm a little lost as to what I'm missing.
> > > > > 
> > > > 
> > > > There's an issue in that if the dev kit reboots early during
> > > > the
> > > > first boot after reflashing, ssh keys will not get generated.
> > > > You
> > > > can
> > > > either:
> > > > 
> > > > - reflash and make sure the dev kit boots fully for the first
> > > > time,
> > > > - or remove the keys in /etc/sshd (they should be empty
> > > > anyway),
> > > > restart and let it fully boot.
> > > > 
> > > > > Can someone point me in the right direction to sort this out?
> > > > > 
> > > > 
> > > > Hope the above helps!
> > > > 
> > > > Cheers,
> > > > Dorota
> > > > 
> > > > > thanks
> > > > > Dan
> > > > > 
> > > > > [1]
> > > > > 
> > > 
> > > 
> 
> 
https://developer.puri.sm/Librem5/Development_Environment/Boards/imx8.html
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > Librem-5-dev mailing list
> > > > > Librem-5-dev at lists.community.puri.sm
> > > > > https://lists.community.puri.sm/listinfo/librem-5-dev
> > > 
> > > _______________________________________________
> > > Librem-5-dev mailing list
> > > Librem-5-dev at lists.community.puri.sm
> > > https://lists.community.puri.sm/listinfo/librem-5-dev