Compile succeeds, Install on NUC 7 succeeds, booting into Fuchsia: command prompt without keyboard input

[J U]

Hi Community,

I've configured:

```

fx metrics enable
fx set workbench_eng.x64 --with //bundles/tools,//bundles/tests,//bundles/kitchen_sink --release

```

and build:

```

fx build --log ./../4-fx-build.log

```

Fuchsia successfully.

I've created an installer via:

```

fx mkinstaller /dev/sdb

```

I succeeded in booting that usb-flash-drive.

I succeeded in installing via that usb-flash-drive.

When i boot my NUC 7 i do get a command prompt.

Unfortunatelly, the keyboard does not work.

In my youtube channel, i documented the last two steps:

https://www.youtube.com/watch?v=LTSogEfwyug

(Currently, I do not get any money of ads on this channel...).

-> I expected a graphical user interface (in which i could use chromium).

-> i kindly ask for hints, how to "achieve" a running environment (described in the last sentence)

Many thanks in advance.

Regards

ju

[Suraj Malhotra]

Hi,

The lack of a session UI is intentional for the workbench product. We've deprecated the workstation product and no longer have a default session for you to use. 

The easiest way to debug the keyboard issue is by connecting to the device via `ffx`. Is the device hooked up to your network? If not, could you add it to your network and then try running some of the commands from here:

https://fuchsia.dev/fuchsia-src/get-started/explore_fuchsia?hl=en. Logs you retrieve from the device may help diagnose the problem.

-Suraj

--
All posts must follow the Fuchsia Code of Conduct https://fuchsia.dev/fuchsia-src/CODE_OF_CONDUCT or may be removed.
---
You received this message because you are subscribed to the Google Groups "discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss+u...@fuchsia.dev.
To view this discussion on the web visit https://groups.google.com/a/fuchsia.dev/d/msgid/discuss/a60a7235-e5dc-4866-8110-562d0115ffb3n%40fuchsia.dev.

[J U]

Hi Suraj,

thanks a lot for pointing out the facts about the Fuchsia UI.

I've just tried to connect both my host PC and my NUC (with booted Fuchsia) via the local network:

```

ffx target list
NAME                      SERIAL       TYPE       STATE      ADDRS/IP                                 RCS
fuchsia-94c6-9119-5954    <unknown>    Unknown    Product    [192.168.178.61,                         N
                                                              fe80::a5a9:f1f9:1395:cb7c%enp0s31f6]

```

```

 ffx target show
BUG: An internal command error occurred.
Error: Failed to create remote control proxy
    1.  Failed to create remote control proxy
    2.  Timeout attempting to reach target "unspecified"
More information may be available in ffx host logs in directory:
    /home/ju/.local/share/Fuchsia/ffx/cache/logs

```

--> Other ffx-commands do not terminate..., Please compare the last two lines:

```

Sep 29 14:56:03.677 [08732999869035780052] INFO ffx_command: starting command: ["ffx", "target", "list"] Sep 29 14:56:03.701 [08732999869035780052] INFO ffx_daemon: no daemon found at /mnt/sda1/fuchsia/out/default/.ffx-daemon/daemon.sock Sep 29 14:56:03.701 [08732999869035780052] INFO ffx_daemon: Starting new background ffx daemon from "/mnt/sda1/fuchsia/out/default/host_x64/ffx" Sep 29 14:56:04.131 [08732999869035780052] INFO ffx_command::metrics: Command finished. success: true, command time: 0.28208947, analytics time: 0.15683371 Sep 29 14:56:54.379 [14898723877480598312] INFO ffx_command: starting command: ["ffx", "target", "list"] Sep 29 14:56:54.602 [14898723877480598312] INFO ffx_command::metrics: Command finished. success: true, command time: 0.027389068, analytics time: 0.18965793 Sep 29 14:57:14.734 [17130754583978855936] INFO ffx_command: starting command: ["ffx", "target", "show"] Sep 29 14:57:24.740 [17130754583978855936] WARN ffx_daemon_proxy: Timed out getting remote control proxy for: None Sep 29 14:57:24.913 [17130754583978855936] INFO ffx_command::metrics: Command finished. success: false, command time: 10.0009, analytics time: 0.17237714 Sep 29 14:57:24.936 [17130754583978855936] ERROR ffx_command: analytics failed to submit crash event: Value too long: Str("BUG: An internal command error occurred.\nError: Failed to create remote control proxy\n 1. Failed to create remote control proxy\n 2. Timeout attempting to reach target \"unspecified\"") Sep 29 15:00:22.820 [14174603572189934188] INFO ffx_command: starting command: ["ffx", "target", "reboot"] Sep 29 15:01:03.906 [14509303882402246996] INFO ffx_command: starting command: ["ffx", "log"]

```

```

Sep 29 14:56:03.924 [08878413645293176714] INFO ffx_daemon_target::target_collection: adding new target: Target { id: 13114474297556764291, ids: {13114474297556764291}, nodename: Some("fuchsia-94c6-9119-5954"), state: Mdns(Instant { tv_sec: 694, tv_nsec: 168655958 }), last_response: 2023-09-29T12:56:03.924476448Z, addrs: {TargetAddrEntry { addr: TargetAddr(192.168.178.61:0), timestamp: 2023-09-29T12:56:03.924478681Z, addr_type: Ssh }}, ssh_port: None, serial: None, boot_timestamp_nanos: None } Sep 29 14:56:04.105 [08878413645293176714] ERROR ffx_daemon_target::overnet::host_pipe: Failed to read ssh client address: reading ssh connection Caused by: Parse error: "No newline: []" Sep 29 14:56:04.105 [08878413645293176714] WARN ffx_daemon_target::target: Host pipe spawn creating host-pipe command to target Some("fuchsia-94c6-9119-5954") ```

I cannot configure anything on the NUC (with running Fuchsia), as the keyboard does not work.

-> Is it possible to configure the Fuchsia environment before creating the usb-flash-drive (``fx mkinstaller /dev/sdb``)

-> how is it possible to provide more information for you?

Many thanks in Advance.

Regards

JU

[Justin Mattson]

You might try running `ffx doctor` to see if that will get you to connect and/or reveal more information about the problem.

Cheers,

Justin

To view this discussion on the web visit https://groups.google.com/a/fuchsia.dev/d/msgid/discuss/964d2bad-eb44-4b16-a930-e56099813a36n%40fuchsia.dev.

[Sam Hansen]

Can you provide the output of:

- ffx doctor

- fx shell -vv

Also, what kind of machine is the host, and is it the same machine that was used to perform the build? If not, there's likely some ssh keys you'll need to fetch from the build host.

To view this discussion on the web visit https://groups.google.com/a/fuchsia.dev/d/msgid/discuss/CA%2BX8dX9jSDYhy2VN%2Bdj1Z0L6MDuyPcbtYYagyE3WW7AN_NaEgg%40mail.gmail.com.

[J U]

Hi

thanks a lot for these hints:

```

ffx doctor -v

[✓] Searching for targets
    [✓] 1 targets found

[✗] Verifying Targets
    [✗] Target: fuchsia-94c6-9119-5954
        [✓] Opened target handle
        [✗] Timeout while connecting to RCS

[✗] Doctor found issues in one or more categories.

```

```

fx shell -vv

OpenSSH_9.2p1 Debian-2, OpenSSL 3.0.9 30 May 2023
debug1: Reading configuration data /mnt/sda1/fuchsia/out/default/ssh-keys/ssh_config
debug1: /mnt/sda1/fuchsia/out/default/ssh-keys/ssh_config line 7: Applying options for *
debug2: resolve_canonicalize: hostname fe80::a5a9:f1f9:1395:cb7c%enp0s31f6 is address
debug1: auto-mux: Trying existing master
debug1: Control socket "/home/ju/.ssh/fx-5cd9e4d9643e98ab7455391cd45970355d0c3278" does not exist
debug1: Connecting to fe80::a5a9:f1f9:1395:cb7c%enp0s31f6 [fe80::a5a9:f1f9:1395:cb7c%enp0s31f6] port 22.
debug2: fd 3 setting O_NONBLOCK
debug1: fd 3 clearing O_NONBLOCK
debug1: Connection established.
debug1: identity file /home/ju/.ssh/fuchsia_ed25519 type 3
debug1: identity file /home/ju/.ssh/fuchsia_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.2p1 Debian-2
debug1: Remote protocol version 2.0, remote software version OpenSSH_9.1
debug1: compat_banner: match: OpenSSH_9.1 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to fe80::a5a9:f1f9:1395:cb7c%enp0s31f6:22 as 'ju'
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: sntrup761x2...@openssh.com,curve25519-sha256,curve255...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c
debug2: host key algorithms: ssh-ed2551...@openssh.com,ecdsa-sha2-nis...@openssh.com,ecdsa-sha2-nis...@openssh.com,ecdsa-sha2-nis...@openssh.com,sk-ssh-ed25...@openssh.com,sk-ecdsa-sha2-n...@openssh.com,rsa-sha2-5...@openssh.com,rsa-sha2-2...@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-...@openssh.com,sk-ecdsa-sh...@openssh.com,rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos: chacha20...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes12...@openssh.com,aes25...@openssh.com
debug2: ciphers stoc: chacha20...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes12...@openssh.com,aes25...@openssh.com
debug2: MACs ctos: umac-...@openssh.com,umac-1...@openssh.com,hmac-sha...@openssh.com,hmac-sha...@openssh.com,hmac-s...@openssh.com,uma...@openssh.com,umac...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-...@openssh.com,umac-1...@openssh.com,hmac-sha...@openssh.com,hmac-sha...@openssh.com,hmac-s...@openssh.com,uma...@openssh.com,umac...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zl...@openssh.com,zlib
debug2: compression stoc: none,zl...@openssh.com,zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: sntrup761x2...@openssh.com,curve25519-sha256,curve255...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256
debug2: host key algorithms: ssh-ed25519
debug2: ciphers ctos: chacha20...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes12...@openssh.com,aes25...@openssh.com
debug2: ciphers stoc: chacha20...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes12...@openssh.com,aes25...@openssh.com
debug2: MACs ctos: umac-...@openssh.com,umac-1...@openssh.com,hmac-sha...@openssh.com,hmac-sha...@openssh.com,hmac-s...@openssh.com,uma...@openssh.com,umac...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-...@openssh.com,umac-1...@openssh.com,hmac-sha...@openssh.com,hmac-sha...@openssh.com,hmac-s...@openssh.com,uma...@openssh.com,umac...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zl...@openssh.com
debug2: compression stoc: none,zl...@openssh.com
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: sntrup761x2...@openssh.com
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20...@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20...@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:K0a/9FzHvOXoKHqkNhWMJyCS4IPeu/52FvpCs60M6T4
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
Warning: Permanently added 'fe80::a5a9:f1f9:1395:cb7c%enp0s31f6' (ED25519) to the list of known hosts.
debug2: ssh_set_newkeys: mode 1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug2: ssh_set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /home/ju/.ssh/fuchsia_ed25519 ED25519 SHA256:fawjXdXtTViB8jfnakCZOejekCUZ1ONpayKDsJaahAc explicit
debug2: pubkey_prepare: done
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: kex_input_ext_info: publickey...@openssh.com=<0>
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering public key: /home/ju/.ssh/fuchsia_ed25519 ED25519 SHA256:fawjXdXtTViB8jfnakCZOejekCUZ1ONpayKDsJaahAc explicit
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,keyboard-interactive
debug2: we did not send a packet, disable method
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug1: Authentications that can continue: publickey,keyboard-interactive
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
ju@fe80::a5a9:f1f9:1395:cb7c%enp0s31f6: Permission denied (publickey,keyboard-interactive).

```

-> it seems to be an ssh issue: how is it possible to change the ssh-keys?

Many thanks in advance.

Regards

JU

[J U]

Hi,

the host - machine was not used to build fuchsia: i used a Debian 12 "bookworm" system to build Fuchsia.

the host - machine is a "Intel Desktop Board NUC7i3BNB".

Many thanks in advance.

Regards

JU

Sam Hansen schrieb am Freitag, 29. September 2023 um 18:50:18 UTC+2:

[J U]

Hi,

i've just found [0]: Create SSH keys for Fuchsia devices

So, i tried:

```

cat ~/.ssh/id_rsa.pub >> ~/.ssh/fuchsia_authorized_keys

```

I tried to re-install Fuchsia with this change:

```

fx mkinstaller /dev/sdb

```

Now i get:

```

fx target show

BUG: An internal command error occurred.
Error: Failed to create remote control proxy
    1.  Failed to create remote control proxy
    2.  Timeout attempting to reach target "unspecified"
More information may be available in ffx host logs in directory:

    /root/.local/share/Fuchsia/ffx/cache/logs

```

```

ffx doctor -v

[✗] Verifying Targets
    [✗] Target: fuchsia-94c6-9119-5954
        [✓] Opened target handle
        [✗] Timeout while connecting to RCS

[✗] Doctor found issues in one or more categories.

```

```

fx shell -vv

ju@fe80::3f65:a6aa:5f7d:64c%enp0s31f6: Permission denied (publickey,keyboard-interactive).

```

-->  is it necessary to re-compile Fuchsia in order to apply the changes ( ~/.ssh/fuchsia_authorized_keys)?

[0] https://fuchsia.dev/fuchsia-src/development/sdk/ffx/create-ssh-keys-for-devices

Many thanks in advance.

Regards

JU

[Justin Mattson]

Yes, I think you do need to rebuild Fuchsia. Note that by "host" here Sam was referring to the machine trying to connect to the machine running Fuchsia itself. Maybe this is already understood, but just in case.

We tend to talk about a "host" being the thing you are developing and building on and a "target" which is the thing running Fuchsia.

Cheers,

Justin

[J U]

Thanks a lot for these hints.

I am going to use the correct terminology:

* my host - system: Debian 12 "bookworm" (Linux debian 6.1.0-12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.52-1 (2023-09-07) x86_64 GNU/Linux)

* my target - system: Intel Desktop Board NUC7i3BNB

After extending "~/.ssh/fuchsia_authorized_keys" with all "*.pub - file - data" I did rebuild Fuchsia and deployed it:

https://youtu.be/muCvl6m0308?t=486

```

AddUartDriver: no spcr

GetGicDriver: unexpected interrupt controller type: 0x0

...

...

-> I am using a logitech keyboard: can you recommend a keyboard which will be detected?

 

Now the ssh keys match:

https://youtu.be/muCvl6m0308?t=651

Unfortunatelly, "could not establish connection" / "Timeout while connection to RCS"

-> I've seen that it is possible to crate an image of the Fuchsia - partition(s) via "dd" and "mount" this / that image(s)...

-> i expect that these "dd-images" will have the same structure as on the ssd -> do i need a special file system driver to read it via my host-system ("debian 12")?

Many thanks in advance.

Regards

JU

[Amit Uttamchandani]

Hi there,

Thanks for the link to the video. Let's try a couple of things:

 (1) After fixing the ssh keys issues, could you try `fx shell`? Does that bring up a shell prompt? If so, please try `log_listener` and dump out the logs. If would be useful to also get the output of `ps` to see if the remote_control process is running.

 (2) You could try running `ffx target list` and take the name of the target and try ffx target show: `ffx -t fuchsia-94c6-9119-5954 target show`. Here we are explicitly passing the target name to the tool.

To view this discussion on the web visit https://groups.google.com/a/fuchsia.dev/d/msgid/discuss/b7bf8928-a015-4324-b03a-843413ef9573n%40fuchsia.dev.

[Amit Uttamchandani]

@MJ Ramos fyi

@Steven Grady I noticed the ""No newline: []" issue here. Did we end up resolving that bug?

[Steven Grady]

The "No newline: []" entry in the daemon log simply indicates that the connection couldn't be made to the target device (specifically, it means that while reading the initial connection to the target, there were no bytes read before the connection closed). Note that the _network_ connection was established, but it couldn't establish an _ssh_ connection. While the other suggestions in this thread are more appropriate for now, it is possible to get (a lot) more information by running the daemon with the debug flag (`ffx config set log.level debug` and then stopping the daemon) -- among other things it will create an `ssh.log` file which shows the output of `ssh -v`.

But again, I wouldn't go that route initially.

The debug message is there to track down another bug we see occasionally, which is still under investigation.

-Steven

[J U]

Thanks a lot for these hints.

I've tried:

```

ffx config set log.level debug

fx shell -v

```

Unfortunately, I cannot connect to fuchsia:

Please, compare:

https://youtu.be/eDiuUNen6Dc

I figured out that my fuchsia_authorized_keys

contain two entries for

```

ssh-ed25519

```

(One is for my github account)

-> If this was a problem, how it will delete all entries 

```

~/.ssh/

```

and recompile Fuchsia?

-> Or is there a different reason for that:

```

Permission denied
```

?

Many thanks in advance.

Regards

JU

[Amit Uttamchandani]

Thanks for the additional details. Please try running `fx shell --check.` That will check if there are inconsistencies with your ssh keys.

Also, I'm unsure if you already ran this step. But I recommend to reflash again to correctly provision the keys: https://fuchsia.dev/fuchsia-src/development/hardware/intel_nuc?hl=en#flash-fuchsia