Bug 1206977 - On boot hangs on fbo:switching to i915 from EFI VGA
Summary: On boot hangs on fbo:switching to i915 from EFI VGA
Status: RESOLVED DUPLICATE of bug 1209436
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Leap 15.4
Hardware: x86-64 openSUSE Leap 15.4
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: openSUSE Kernel Bugs
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-09 15:03 UTC by Jürg Coucou
Modified: 2023-03-18 16:10 UTC (History)
5 users (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jürg Coucou 2023-01-09 15:03:24 UTC
HW: ASUS Prime Z790-P with iCore5 CPU with integrated GPU, M2 NVMe SSD
Installation was not possible without grub linux parameter nomodeset. Of course with this parameter only the basic resolution of 1024x768 is available. Every successive boot hangs on log entry fbo:switching to i915 from EFI VGA.
As I could not find any solution I tried first to install Windows 10. Worked without any Problem Intel drivers were installed properly and I got full resolution of 2560x1440.
I tried openSUSE-Tumbleweed-GNOME-Live-x86_64-Current.iso starting form USB. Worked as expected with full resolution.
I tried to install openSUSE-Tumbleweed-DVD-x86_64-Current.iso. Didn't hang and I could start the installation. I interromped the installation to try Leap 15.4 again first getting the updated version i.e. openSUSE-Leap-15.4-CR-DVD-x86_64-Build31.38-Media.iso. No chance, without nomodeset parameter no installation possible. I'll install tumbleweed now, but this is not exactly what I wanted.
Comment 1 Takashi Iwai 2023-01-09 15:18:31 UTC
Please don't touch the Bugzilla Priority field; it's the one adjusted only in developer side.

After installing the Leap 15.4 and upgrade to the latest maintenance kernel, does the boot still hang if you omit nomodeset option?
Comment 2 Don Hughes 2023-03-17 21:30:21 UTC
Same problem on an ASUS Strix G512 with an Nvidia GeForce GTX 1660Ti.

This was an existing Leap 15.4 installation.  yast did a kernal update from 5.14.21-150400.24.46.1 to 24.49.3 and the system froze as above on re-boot.  Only way to regain control was power cycle the system.  Re-booted and used grub to add nomodset and was able to boot the system.  I downgraded back to the 24.46.1 kernel and the system is again working as expected.  Kernels were installed from download.opensuse.org/update/leap/15.4/sle
Comment 3 Nick Dordea 2023-03-18 00:56:54 UTC
Same problem as Don Hughes [ comment#2 ]
yast maintenance include new kernel-default 5.14.21-150400.24.49.3  
the old kernel kernel-default 5.14.21-150400.24.46,1
The boot stopped 
last message :
[4.198071 ][  T364] fb0: switching to i915 from EFI VGA

Rebooting with kernel-default 5.14.21-150400.24.46,1  is fine ?

While waiting for suse solution/fix, I'm going to  reboot with nomodset then downgrade the kernel back to 46.1
Comment 4 Takashi Iwai 2023-03-18 06:43:43 UTC
This must be the bug in i915 patch backport.

*** This bug has been marked as a duplicate of bug 1209436 ***
Comment 5 Nick Dordea 2023-03-18 14:43:37 UTC
(In reply to Nick Dordea from comment #3)
> Same problem as Don Hughes [ comment#2 ]
> yast maintenance include new kernel-default 5.14.21-150400.24.49.3  
> the old kernel kernel-default 5.14.21-150400.24.46,1
> The boot stopped 
> last message :
> [4.198071 ][  T364] fb0: switching to i915 from EFI VGA
> 
> Rebooting with kernel-default 5.14.21-150400.24.46,1  is fine ?
> 
> While waiting for suse solution/fix, I'm going to  reboot with nomodset then
> downgrade the kernel back to 46.1

1. Tried to boot with nomodset .... the boot hangs as before .
2. reboot with 24.46.1  kernel
3. yast2 remove 
kernel-default-5.14.21-150400.24.49.3
kernel-default-devel-5.14.21-150400.24.49.3
kernel-default-extra-5.14.21-150400.24.49.3
kernel-default-optimal-5.14.21-150400.24.49.3
3.a check dependencies ===> asks to uninstall 
kernel-syms-5.14.21-150400.24.49.4

Why is that kernel 24.49.4  used and NOT 24,49,3 ????
It might be cause !!!

4. Try to simulate yast2 maintenance .....

The following 5 NEW packages are going to be installed:
  kernel-default
    5.14.21-150400.24.49.3  x86_64  Update repository with updates from SUSE Linux Enterprise 15  SUSE LLC <https://www.suse.com/>
  kernel-default-devel
    5.14.21-150400.24.49.3  x86_64  Update repository with updates from SUSE Linux Enterprise 15  SUSE LLC <https://www.suse.com/>
  kernel-default-extra
    5.14.21-150400.24.49.3  x86_64  Update repository with updates from SUSE Linux Enterprise 15  SUSE LLC <https://www.suse.com/>
  kernel-default-optional
    5.14.21-150400.24.49.3  x86_64  Update repository with updates from SUSE Linux Enterprise 15  SUSE LLC <https://www.suse.com/>
  kernel-syms
    5.14.21-150400.24.49.4  x86_64  Update repository with updates from SUSE Linux Enterprise 15  SUSE LLC <https://www.suse.com/>

The following package requires a system reboot:
  kernel-default
    5.14.21-150400.24.49.3  x86_64  Update repository with updates from SUSE Linux Enterprise 15  SUSE LLC <https://www.suse.com/>

Is kernel-syms-5.14.21-150400.24.49.4 really needed  OR should be 
kernel-syms-5.14.21-150400.24.49.3 ????