-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Black Screen when booting NUC with Hypervisor #663
Comments
Thanks for the workaround. It worked for me. One comment on this step:
I think |
I don't understand why you need to install the desktop bundle just to run a command line argument to find the IP address. /usr/bin/ip is installed with os-core, so you already have that with the most basic native install and you just have to run it in the virtual terminal |
@rustylynch , install the desktop bundle is to use the graphics tools, as the console is not visible when the system boots with the hypervisor and |
Currently Clear Linux support weston@user.service, thus we could add one user and run below commands to avoid create weston.service by self. Below is run in native Clear linux: |
1, remove Device Manager memory allocation mechanism because of no need set manually anymore 2, update the contents to meet the feedback from reviewer 3, add new user to SOS and enable weston to fix issue: projectacrn#663
add user and enable weston service to fix issue: projectacrn#663
verified again, with user name cl-sos. it doesn't work to fix projectacrn#663 but cl_sos is working, so update the user name to cl_sos. that means clear has naming rules for user name
verified again, with user name cl-sos. it doesn't work to fix #663 but cl_sos is working, so update the user name to cl_sos. that means clear has naming rules for user name
add user and enable weston service to fix issue: projectacrn#663
verified again, with user name cl-sos. it doesn't work to fix projectacrn#663 but cl_sos is working, so update the user name to cl_sos. that means clear has naming rules for user name
We found a black screen issue when boot up APL NUC with Hypervisor, After debugging we found it's ClearLinux issue. Here is the work around.
In order to successfully boot up SOS/UOS with their displays (otherwise there is NO display after boot up SOS), the following steps are needed before rebooting native Clear Linux to SOS,
After launching native Clear Linux, you MUST install the
desktop
bundle:$ swupd bundle-add desktop
Get the IP for clearlinux, record IP for ssh login to the SOS in case SOS display fails after the SOS is booted:
$ ip addr
Create the file
/lib/systemd/system/weston.service
with the following content:Run this command to start the weston service:
$ systemctl enable Weston
When booting up SOS:
After booting up the UOS, step 1)~4) are needed for the UOS display too.
The text was updated successfully, but these errors were encountered: