[ODM bug] the system stays at Boot Logo after the graphics/{index}_switch_card_{product_slug} is run

Bug #1923016 reported by StanleyHuang
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox Provider - Base
Expired
High
Sylvain Pineau
OEM Priority Project
Triaged
Critical
jeremyszu

Bug Description

Description:
Checkbox-ng would adjust the graphic mode from "Performance" to "Power Saving" during client-cert-20-04 testing, and then the screen would stays at Boot logo.

User need to re-connect the monitor to integrated GPU to switch the graphic mode to "Performance" mode to continue rest of testing.

My question is shall we test integrated GPU while a discrete GPU installed for a Desktop/Tower server/Rack server? If not, we should not list the test cases for integrated GPU.

Steps to reproduce:
1. Connect an external monitor to dGPU.
2. Power on system and boot into OS.
3. Make sure the graphic profile is in performance mode.
stanley@stanley-ThinkPad-T490:~$ prime-select query
nvidia
4. Run client-cert-20-04 test plan.
Note: the screen would stays at Boot logo after checkbox-ng switch the graphic mode to "power saving" mode.

Test environment:
A system w/ iGPU and nVidia GPU installed.

StanleyHuang (stanley31)
Changed in plainbox-provider-checkbox:
importance: Undecided → High
StanleyHuang (stanley31)
description: updated
StanleyHuang (stanley31)
Changed in plainbox-provider-checkbox:
assignee: nobody → Sylvain Pineau (sylvain-pineau)
Revision history for this message
Max Lee (max-lee) wrote :

@sylvain

Could you help to take a look and provide an update? The issue will impact upcoming the Alder Lake platforms. need fix it soon.

Revision history for this message
Jeff Lane  (bladernr) wrote :

Just to be clear, this is a desktop thing, Server does not test any graphics output as Ubuntu Server is intended to be run headless.

Revision history for this message
Sylvain Pineau (sylvain-pineau) wrote :

We can't ignore a video port. They all have to be tested per the certification guide.
If by switching to the integrated card the monitor has to be reconnected, I don't see a fix on checkbox side (or maybe a warning in the test desc, but that will be barely noticeable if the test if automated). I'd rather add a note in the ODM testing document to either have two monitors or a setup with a picture-in picture setup to avoid entering "power saving" mode.

Revision history for this message
Kent Lin (kent-jclin) wrote :

As discussed with Sylvain, base on comment#3, to mitigate the problem, the best approach will be connected 2 monitors, one on DIS card, the other on iGPU.
AI, have QA team to try it to see if the issue could be mitigated or not.

Revision history for this message
Erin Chen (iamerin-c) wrote (last edit ):

For Stella,
SKU: Z2 G8 (I+N)
in performance mode, both iGPU and dGPU works well
--
use command swtich to powersaving mode,
only connect display in iGPU then boot --> stuck on login page (can't login with correct password)
connect 1 monitor in iGPU and 1 monitor in dGPU --> stuck on login page (can't login with correct password)

create an issue to get the opinion from SE https://bugs.launchpad.net/stella/+bug/1931990

Revision history for this message
jeremyszu (os369510) wrote :

commented the bug that Erin mentioned in comment#5

Changed in oem-priority:
assignee: nobody → jeremyszu (os369510)
importance: Undecided → Critical
status: New → Triaged
Revision history for this message
Erin Chen (iamerin-c) wrote :

For Stella I+N system, Powersaving mode works well after set VGA boot device as Intel VGA on BIOS setting.
https://bugs.launchpad.net/stella/+bug/1931990/comments/7

Rex Tsai (chihchun)
tags: added: oem-priority
Matias Piipari (mz2)
tags: added: cbox-9
Revision history for this message
Maksim Beliaev (beliaev-maksim) wrote :

Bug was migrated to GitHub: https://github.com/canonical/checkbox/issues/83.
Bug is no more monitored here.

Changed in plainbox-provider-checkbox:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.