Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

No UI on NUC8i3BEHS

40 views
Skip to first unread message

Ron Even

unread,
Jun 26, 2021, 12:43:32 PM6/26/21
to discuss
Hi
I've installed the Workstation x64 version of Fuchsia on NUC8i3BEHS, and every shell-related function works.

When I try running the running web browser with:
tiles_ctl start
tiles_ctl add https://google.com

Nothing shows, and the logs say:
[00386.683828][30807][0][netstack, NUD] INFO: fuchsia_net_neighbor.go(85): MOD 2a0d:6fc0:2242:e200::1 (v6|L) NIC=2 LinkAddress=90:8d:78:54:bd:28 Delay
[00387.331228][22552][22555][pkg-resolver] INFO: AutoClient for "http://[fe80::145a:3119:b5e7:d78d%25ethxec]:8083/auto" connecting.
[00387.842466][22552][22555][pkg-resolver] INFO: updated local TUF metadata for "fuchsia-pkg://devhost" to version RepoVersions { root: 7, timestamp: Some(1624718735), snapshot: Some(1624718735), targets: Some(1624718735) } while getting merkle for TargetPath("tiles_ctl/0")
[00387.845821][22552][22555][pkg-resolver] INFO: Fetching blobs for fuchsia-pkg://devhost/tiles_ctl/0: []
[00387.845902][22552][22555][pkg-resolver] INFO: resolved fuchsia-pkg://fuchsia.com/tiles_ctl/0 as fuchsia-pkg://devhost/tiles_ctl/0 to b546a9627bdcbfd26daeca13edab41df7726d6664e2b235186d3f1fd7d39818e with TUF
[00387.853382][22552][22555][pkg-resolver] INFO: Fetching blobs for fuchsia-pkg://devhost/tiles/0: []
[00387.853509][22552][22555][pkg-resolver] INFO: resolved fuchsia-pkg://fuchsia.com/tiles/0 as fuchsia-pkg://devhost/tiles/0 to 0654971edf9332e93350e9160419cfcf802be6bc54ed9131f7d6aa2eb920df28 with TUF
[00387.863058][22552][22555][pkg-resolver] WARNING: error resolving fuchsia-pkg://fuchsia.com/root_presenter/0 as fuchsia-pkg://devhost/root_presenter/0: while caching the package: while looking up merkle root for package: the package was not found in the repository
[00387.863652][22655][22657][sysmgr.cmx] ERROR: [src/sys/sysmgr/app.cc(178)] Could not load package for service fuchsia.ui.policy.Presenter at fuchsia-pkg://fuchsia.com/root_presenter#meta/root_presenter.cmx
[00387.863680][22655][22657][sysmgr.cmx] ERROR: [src/sys/sysmgr/app.cc(184)] Singleton component fuchsia-pkg://fuchsia.com/root_presenter#meta/root_presenter.cmx died

I did find root_presenter.cmx at ./src/ui/bin/root_presenter/meta/root_presenter.cmx
But I don't understand how the resolution work and why it doesn't/

In addition, I'm not sure if it is related or normal, when booting, the GigaBoot screen persists, and when I Alt+Esc it moves to the terminal as it should, but again, can't run UI commands.

Thanks for the help
Ron

Yegor Pomortsev

unread,
Jun 28, 2021, 4:09:54 PM6/28/21
to Ron Even, discuss
Hi Ron,

The workstation product does not include the root_presenter that the tiles component requires to display its view, and tiles_ctl is not compatible with the workstation session.

If you'd like to run tiles, try launching it from the terminal product.

If you'd like to launch a web browser in workstation, try running `ffx session add https://google.com` from the host to add an element to the session.

Cheers,
Yegor



--
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/62c52a8a-260c-4fdf-8c8b-adcfc2e0fbb4n%40fuchsia.dev.

Ron Even

unread,
Aug 8, 2021, 2:49:57 AM8/8/21
to Yegor Pomortsev, discuss
Hey, sorry for the late reply. I tried building the terminal product, but I don't understand, should I see a real GUI?
I only see the regular CLI which can be moved between with Alt+Tab.
I tried building workstation on QEMU and there it had a real GUI (I did so in separate of building the terminal product on my NUC)

Thanks
Ron

Yegor Pomortsev

unread,
Aug 9, 2021, 2:03:31 PM8/9/21
to Ron Even, discuss
The terminal product does not have a GUI, only the virtcon terminal that you're seeing.

We are also planning on removing this product in favor of core, bringup, and workstation. Googlers, see issue issue 46964.


Ron Even

unread,
Aug 9, 2021, 2:16:32 PM8/9/21
to Yegor Pomortsev, discuss
So basically what you're saying is that there's no GUI currently? I can't have a browser with front end?

Filip Filmar

unread,
Aug 9, 2021, 2:21:41 PM8/9/21
to Yegor Pomortsev, Ron Even, discuss
On Mon, Aug 9, 2021 at 11:03 AM 'Yegor Pomortsev' via discuss <dis...@fuchsia.dev> wrote:
The terminal product does not have a GUI, only the virtcon terminal that you're seeing.

We are also planning on removing this product in favor of core, bringup, and workstation. Googlers, see issue issue 46964.

Thinking aloud: should this sort of a question in general be answerable by pasting a URL? 

F

Yegor Pomortsev

unread,
Aug 9, 2021, 2:32:27 PM8/9/21
to Filip Filmar, Ron Even, discuss
Going back to the original question, please use the workstation product. It will boot into a GUI and let you launch a web browser.

The simple answer I'd give is to just build and run Workstation. There seems to be some confusion here around tiles and the terminal product that exist but are not encouraged workflows.
 

F

Ron Even

unread,
Aug 14, 2021, 4:30:17 AM8/14/21
to discuss, Yegor Pomortsev, Ron Even, discuss, Filip Filmar
I did use the workstation product now, but when Fuchsia boots, it only shows the Gigaboot screen, and the keyboard doesn't respond.
These are the logs, extracted with `fx log`.

There is one entry that caught my eyes (and repeats 3 times):
[6535][6537][display_controller, driver_host:composite-device, driver] ERROR: [src/graphics/display/drivers/display/client.cc(1533)] GetSysmemConnection failed (continuing) - status: -2

Could it be the reason it won't go past Gigaboot screen? I am able to run commands via `fx shell`, but no GUI

Thanks

Yegor Pomortsev

unread,
Aug 18, 2021, 6:11:37 PM8/18/21
to Ron Even, discuss, Filip Filmar
It's hard to diagnose this without full logs. Could you please report the issue with an `fx snapshot` zip attached? Thanks!
Reply all
Reply to author
Forward
0 new messages