Camera can't work and boot failure with kernel >=6.17

[Shwen_Y]

The camera on Huawei Matebook E 2022 can't be recognized and can't work properly in cheese or gvcview.

I followed the solution in https://ask.csdn.net/questions/8803663 to load uvcvideo, but it can't work.

/dev/video0 can be seen, but there are many video files ,from video0 to video 63, and video7 ,video8 ,video9

command

Code: Select all

ffplay /dev/video0

reports errors:

[video4linux2,v4l2 @ 0x7f8cc0000c80] ioctl(VIDIOC_G_PARM): Inappropriate ioctl for device
[video4linux2,v4l2 @ 0x7f8cc0000c80] Time per frame unknown
[video4linux2,v4l2 @ 0x7f8cc0000c80] ioctl(VIDIOC_STREAMON): Link has been severed
/dev/video0: Link has been severed

command

Code: Select all

grep -r "Huawei.*camera" /usr/src/linux-headers-$(uname -r)/

reports error that the file can't be found.

system info :

Portage 3.0.72 (python 3.13.9-final-0, default/linux/amd64/23.0/desktop/gnome/systemd, gcc-15, glibc-2.41-r6, 6.12.58-gentoo-gentoo x86_64)
=================================================================
System uname: Linux-6.12.58-gentoo-gentoo-x86_64-11th_Gen_Intel-R-_Core-TM-_i7-1160G7_@_1.20GHz-with-glibc2.41
KiB Mem: 16142912 total, 11681584 free
KiB Swap: 8388600 total, 8388600 free
Timestamp of repository gentoo: Sat, 20 Dec 2025 13:15:57 +0000
Head commit of repository gentoo: 2d9029be3d06f2b17f6e7453a95a541e6b6f211e

Head commit of repository gentoo-zh: 102505eb617e4ea3ef060bb098628847ae47ef49

Timestamp of repository guru: Sat, 20 Dec 2025 21:46:06 +0000
Head commit of repository guru: 96083377892838828a91e38cc1464b7dc681ca50

sh bash 5.3_p3-r3
ld GNU ld (Gentoo 2.45.1 p1) 2.45.1
app-misc/pax-utils: 1.3.8::gentoo
app-shells/bash: 5.3_p3-r3::gentoo
dev-build/autoconf: 2.13-r8::gentoo, 2.72-r4::gentoo
dev-build/automake: 1.18.1::gentoo
dev-build/cmake: 4.1.2-r1::gentoo
dev-build/libtool: 2.5.4::gentoo
dev-build/make: 4.4.1-r102::gentoo
dev-build/meson: 1.9.1::gentoo
dev-lang/perl: 5.42.0-r1::gentoo
dev-lang/python: 3.13.9::gentoo, 3.14.0_p1::gentoo
dev-lang/rust: 1.89.0::gentoo
dev-lang/rust-bin: 1.86.0-r1::gentoo, 1.89.0::gentoo
llvm-core/clang: 20.1.8::gentoo
llvm-core/lld: 20.1.8::gentoo
llvm-core/llvm: 20.1.8::gentoo
sys-apps/baselayout: 2.18::gentoo
sys-apps/sandbox: 2.46::gentoo
sys-apps/systemd: 257.10::gentoo
sys-devel/binutils: 2.45.1::gentoo
sys-devel/binutils-config: 5.6::gentoo
sys-devel/gcc: 15.2.1_p20251122::gentoo
sys-devel/gcc-config: 2.12.2::gentoo
sys-kernel/linux-headers: 6.12::gentoo (virtual/os-headers)
sys-libs/glibc: 2.41-r6::gentoo
Repositories:

gentoo
location: /var/db/repos/gentoo
sync-type: git
sync-uri: https://mirror.nju.edu.cn/git/gentoo-portage.git
priority: -1000
volatile: False
sync-git-verify-commit-signature: true

gentoo-zh
location: /var/db/repos/gentoo-zh
sync-type: git
sync-uri: https://mirror.nju.edu.cn/git/gentoo-zh.git
masters: gentoo
volatile: False

guru
location: /var/db/repos/guru
sync-type: git
sync-uri: https://anongit.gentoo.org/git/repo/sync/guru.git
masters: gentoo
volatile: False

Binary Repositories:

gentoobinhost
priority: 99
sync-uri: https://mirror.nju.edu.cn/gentoo/releas ... 3.0/x86-64

ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="@FREE"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-march=native -O2 -pipe"
DISTDIR="/var/cache/distfiles"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GDK_PIXBUF_MODULE_FILE GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR XDG_STATE_HOME"
FCFLAGS="-march=native -O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs binpkg-multi-instance buildpkg-live config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync merge-wait multilib-strict network-sandbox news parallel-fetch pid-sandbox pkgdir-index-trusted preserve-libs protect-owned qa-unresolved-soname-deps sandbox strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-march=native -O2 -pipe"
GENTOO_MIRRORS="https://mirror.nju.edu.cn/gentoo/ https://mirrors.ustc.edu.cn/gentoo/"
LANG="zh_CN.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs"
LEX="flex"
LINGUAS="en zh_CN zh_TW"
MAKEOPTS="-j8"
PKGDIR="/var/cache/binpkgs"
PORTAGE_COMPRESS="bzip2"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
RUSTFLAGS=" -C target-cpu=native"
SHELL="/bin/bash"
USE="X a52 aac acl acpi alsa amd64 avif bluetooth branding bzip2 cairo cdda cdr cet colord crypt cups dbus dist-kernel dri dts dvd dvdr eds encode evo exif flac gdbm gdk-pixbuf gif git gnome gnome-keyring gnome-online-accounts gnome-shell gpm gstreamer gtk gtk3 gui iconv icu introspection ipv6 jpeg jpegxl keyring lcms libnotify libtirpc mad mng modules-sign mp3 mp4 mpeg multilib nautilus ncurses networkmanager nls ogg opengl openmp pam pango pcre pdf pipewire png policykit ppds pulseaudio qml qt6 readline screencast sdl seccomp secureboot sound spell ssl startup-notification svg sysprof systemd test-rust tiff tracker truetype udev udisks unicode upower usb vaapi vorbis vpx vulkan wayland webp wxwidgets x264 xattr xcb xft xml xv xvid zlib" ABI_X86="64" ADA_TARGET="gcc_15" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_anon authn_dbm authn_file authz_dbm authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir env expires ext_filter file_cache filter headers include info log_config logio mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2 aes avx avx2 avx512_bitalg avx512_vbmi2 avx512_vnni avx512_vp2intersect avx512_vpopcntdq avx512bw avx512cd avx512dq avx512f avx512ifma avx512vbmi avx512vl bmi1 bmi2 f16c fma3 pclmul popcnt rdrand sha sse3 sse4_1 sse4_2 ssse3 vpclmulqdq" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax navcom oceanserver oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 tsip tripmate tnt ublox" GRUB_PLATFORMS="efi-64" GUILE_SINGLE_TARGET="3-0" GUILE_TARGETS="3-0" INPUT_DEVICES="libinput" KERNEL="linux" L10N="en zh zh-CN zh-TW" LCD_DEVICES="bayrad cfontz glk hd44780 lb216 lcdm001 mtxorb text" LLVM_TARGETS="X86" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php8-3" POSTGRES_TARGETS="postgres17" PYTHON_SINGLE_TARGET="python3_13" PYTHON_TARGETS="python3_13" RUBY_TARGETS="ruby32 ruby33" VIDEO_CARDS="intel i965 iris" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipp2p iface geoip fuzzy condition tarpit sysrq proto logmark ipmark dhcpmac delude chaos account"
Unset: ADDR2LINE, AR, ARFLAGS, AS, ASFLAGS, CC, CCLD, CONFIG_SHELL, CPP, CPPFLAGS, CTARGET, CXX, CXXFILT, ELFEDIT, EMERGE_DEFAULT_OPTS, EXTRA_ECONF, F77FLAGS, FC, GCOV, GPROF, INSTALL_MASK, LC_ALL, LD, LFLAGS, LIBTOOL, MAKE, MAKEFLAGS, NM, OBJCOPY, OBJDUMP, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PYTHONPATH, RANLIB, READELF, SIZE, STRINGS, STRIP, YACC, YFLAGS

[NeddySeagoon]

Shwen_Y,

but there are many video files ,from video0 to video 63, and video7 ,video8 ,video9

That sounds wrong. You should only have /dev/videoX files for video devices the kernel has detected.

Install usbutils, if you don't have it and post the output of

Code: Select all

lsusb

.

UVC is a class driver, it has lots (hundreds?) of modules below it.
We need the vendor and device IDs for your particular camera to check the kernel. Your lsusb output will show that.

[dmpogo]

As I see your matebook has 2 cameras, front and rear ?

Google tells me that E2022 matebook cameras are not uvcvideo cameras (both ???) and you may need to go down IPU6 cameras hole to try to make it work.
Though your link seems to contradict it, and if you have a model with uvc camera, it should work more or less straight.
Whether IPU6 camera will work or not, is basically on a model by model basis. It's been a year effort to make them work on Lenovo Thinkpads, and still with limitations.
One thing you will need, is the latest kernel, 6.12 is too old.

[Shwen_Y]

lsusb output:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 12d1:10b8 Huawei Technologies Co., Ltd.
Bus 003 Device 003: ID 27c6:5105 Shenzhen Goodix Technology Co.,Ltd. Goodix Fingerprint Device
Bus 003 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

"ls /dev/video*" output:

/dev/video0 /dev/video18 /dev/video27 /dev/video36 /dev/video45 /dev/video54 /dev/video63
/dev/video1 /dev/video19 /dev/video28 /dev/video37 /dev/video46 /dev/video55 /dev/video7
/dev/video10 /dev/video2 /dev/video29 /dev/video38 /dev/video47 /dev/video56 /dev/video8
/dev/video11 /dev/video20 /dev/video3 /dev/video39 /dev/video48 /dev/video57 /dev/video9
/dev/video12 /dev/video21 /dev/video30 /dev/video4 /dev/video49 /dev/video58
/dev/video13 /dev/video22 /dev/video31 /dev/video40 /dev/video5 /dev/video59
/dev/video14 /dev/video23 /dev/video32 /dev/video41 /dev/video50 /dev/video6
/dev/video15 /dev/video24 /dev/video33 /dev/video42 /dev/video51 /dev/video60
/dev/video16 /dev/video25 /dev/video34 /dev/video43 /dev/video52 /dev/video61
/dev/video17 /dev/video26 /dev/video35 /dev/video44 /dev/video53 /dev/video62

Yes, it does have two camera on Huawei Matebook E 2022, one is front and another is back. Huawei MateBook E 2022 is a 2-in-1 laptop that combines the functions of a tablet and a notebook computer.

Thank you for NeddySeagoon and dmpogo's reply and advice , I'll try to learn about IPU6 cameras and the latest kernel.

[NeddySeagoon]

Shwen_Y,

Code: Select all

Bus 003 Device 002: ID 12d1:10b8 Huawei Technologies Co., Ltd. 

That was a suspect for your camera but says12d1:10b8 Huawei Techno... Keyboard. So its your keyboard.

From your other topic, lspci says

Code: Select all

00:05.0 Multimedia controller: Intel Corporation Tiger Lake IPU6 (rev 01) 

Searching for

Code: Select all

ipu6 site: cateee.net

gives CONFIG_VIDEO_INTEL_IPU6: Intel IPU6 driver as the first hit.
That says found in Linux kernels: 6.10–6.18, 6.19-rc+HEAD but I would try the testing kernel as your 6.12 has a very new version of the driver.

Code: Select all

zgrep  VIDEO_INTEL_IPU6 /proc/config.gz

will tell if the symbol is in your running kernel if /proc/config.gz exists.

[dmpogo]

for IPU6 support you need the latest kernel. Development was mostly driven within Fedora, and they claim that 6.17 Fefora patched kernel finally has a rather complete support. However, there are still issues with userland.

See, for instance, this discussion in Fedora bug

https://bugzilla.redhat.com/show_bug.cgi?id=2333387#c6

Hans de Goede is the guy who lead the development not only for Thinkpads


With this architecture the video processing is offloaded from dedicated hardware of UVCVIDEO cameras to the kernel drivers. So support depends on exactly what chips and sensors are used.
It is a pain

[Shwen_Y]

Code: Select all

zgrep  VIDEO_INTEL_IPU6 /proc/config.gz

gives an output:

CONFIG_VIDEO_INTEL_IPU6=m

Maybe it replies the camera support on Huawei Matebook E 2022 is still not complete and can't work very well.

I'll try the latest kernel as soon as I can.

[Shwen_Y]

I tried the latest kernel 6.18.2, but the computer cannot boot with it, either compiled by myself with the .config from 6.12.58, or distributed kernel "gentoo-kernel-bin".

I removed the USE flag "modules-sign secureboot" and updated all system, but it still does not worked.

When booting with kernel 6.18.2 , it stucked in the following stage: https://imgloc.com/image/C3Z1Lm

Maybe it is caused by the kernel bug.

[pietinger]

I tried the latest kernel 6.18.2, but the computer cannot boot with it, either compiled by myself with the .config from 6.12.58, [...]

Have you installed the package linux-firmware? (you need it for the i915 driver)

Maybe check your kernel .config with these two wiki articles:
https://wiki.gentoo.org/wiki/User:Pieti ... figuration ->
https://wiki.gentoo.org/wiki/User:Pieti ... ent_Kernel (because you use 6.18 )

[Shwen_Y]

Yes, I have installed linux-firmware.

The .config is copied from kernel 6.12.58, which I compiled and worked well. The new option from kernel 6.18.2 is basically adpoted default values, but it cannot boot successfully.

The distribution kernel 6.18.2 also have the same problem.

[pietinger]

Please try 6.18.2-r1 or - better - 6.18.3.

[pingtoo]

Shwen_Y,

Please do follow pietinger suggestion. As pietinger been on Gentoo forums help many kernel problem requests.

Just add a little bit of my observation in this thread.

You are now raise two different "problems" in this thread, first is your original quest camera not working and secondly you now facing kernel not able to bring up working system.

The two are very different problem if you peruse the kernel problem you might end up with a fixed boot sequence but still have exact same initial problem of camera not working.

I am not 100% sure if you tried with alternative LiveCD to observe if one can get it working or even using whatever OS that come with hardware to verify there is no hardware issue or BIOS configuration issue.

BTW, in my view you don't have "computer cannot boot" problem because kernel. the picture actually show kernel did boot up but in the OS startup sequence there is/are something waiting that suggest it is possible kernel might have missing something critical to your environment that lead to system is waiting. it is very possible the start sequence will eventually continue after timeout on whatever the system is waiting.

As your suspecting on the kernel bug, I almost certain it is not relevant for this case. Unless your reboot is cause by building golang package.

[Shwen_Y]

Thank you for your suggestions, pingtoo and pietinger.

Please try 6.18.2-r1 or - better - 6.18.3.

I tried the latest gentoo-kernel-bin-6.18.6, the boot problem is still existed and remains same.

The two are very different problem if you peruse the kernel problem you might end up with a fixed boot sequence but still have exact same initial problem of camera not working.

Yes, The two are really different problem. But tried a much more newer or latest kernel is might the solution to the first problem , as suggested by NeddySeagoon.

But I really didn't expect to encounter the problem that the new kernel couldn't boot on my HuaWei Matebook E 2022 computer.

BTW, in my view you don't have "computer cannot boot" problem because kernel.

Yes, I think you are right. But I think the problem is more or less kernel related.

[pietinger]

Yes, I think you are right. But I think the problem is more or less kernel related.

So, you cannot boot 6.18.6 (or 6.18.7 now)?

Please give us your kernel .config (use wgetpaste for this) ... and the output of "dmesg" when booting with a functional kernel ...
and the output of https://wiki.gentoo.org/wiki/User:Pieti ... lspci_-nnk

[Shwen_Y]

Yes, I cannot boot with kernel 6.18.12 or 6.19.6 on HUAWEI Matebook E 2022, it always stucks on the stage with the boot message "i915 : [drm] VT-d active for gfx acess".

I tried booting kernel with the parameter : i915.enable_guc=0 i915.enable_psr=0 intel_iommu=off i915.enable_gvt=0 i915.enable_vtd=0, but none of them works.

I used the gentoo-kernel-bin-6.19.6 , the same problem occurs.

I found I have no .config file for 6.18.12 because I use gentoo-kernel-bin-6.18.12.

Kernel 6.12.XX can boot successfully and dmesg output is here: https://bpa.st/KRFA.

"lspci -nnk" output is here: https://bpa.st/UJDQ .

The boot stuck stage image is here: https://imgbob.net/hQBAbgv0GRLrjZI, which booting with gentoo-kernel-bin-6.18.12.

After waiting for hundreds of seconds , a login image pops up but cannot login because it has no response to keystroke. The image is here: https://imgbob.net/mNiv4hQaR5025kR. And it boots with gentoo-kernel-bin-6.19.6

[pietinger]

1. Yes, you have an IPU6 ... which is ... problematic ... I dont know the current situation, but hope to get it working is small.

Code: Select all

00:05.0 Multimedia controller [0480]: Intel Corporation Tiger Lake IPU6 [8086:9a19] (rev 01)
	Subsystem: Wingtech Group(HongKong)Limited Device [1ec9:3e44]
	Kernel driver in use: intel-ipu6
	Kernel modules: intel_ipu6

2. If booting with our LiveCD version 6.18 or 6.19 is not possible ... then there is a serious problem. Looking into the output of 6.12 shows also a serious problem with the integrated GPU of your Intel CPU i7-1160G7 (driver for this is i915):

Code: Select all

[    0.000000] Linux version 6.12.74-gentoo-dist (root@devbox.amd64.dev.gentoo.org) (x86_64-pc-linux-gnu-gcc (Gentoo 15.2.1_p20251122 p3) 15.2.1 20251122, GNU ld (Gentoo 2.45.1 p1) 2.45.1) #1 SMP PREEMPT_DYNAMIC Thu Feb 19 18:37:16 -00 2026
[    0.000000] Command line: BOOT_IMAGE=/boot/kernel-6.12.74-gentoo-dist root=UUID=c662e347-52ff-4723-bef1-5ea245f99300 ro intel_idle.max_cstate=2

[    0.000000] SMBIOS 3.3.0 present.
[    0.000000] DMI: HUAWEI DRC-WXX/DRC-WXX-PCB, BIOS 1.35 10/26/2023

[    0.105831] smpboot: CPU0: 11th Gen Intel(R) Core(TM) i7-1160G7 @ 1.20GHz (family: 0x6, model: 0x8c, stepping: 0x1)

[    4.618214] i915 0000:00:02.0: [drm] Found TIGERLAKE/UY (device ID 9a40) display version 12.00 stepping C0
[    4.623194] i915 0000:00:02.0: [drm] VT-d active for gfx access
[    4.625675] Console: switching to colour dummy device 80x25
[    4.625918] i915 0000:00:02.0: vgaarb: deactivate vga console
[    4.626046] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[    4.628498] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    4.628563] Loading firmware: i915/tgl_dmc_ver2_12.bin
[    4.635008] Loading firmware: i915/tgl_guc_70.1.1.bin
[    4.652296] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_12.bin (v2.12)
[    4.652630] Loading firmware: i915/tgl_huc_7.9.3.bin
[    4.664527] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/tgl_guc_70.1.1.bin version 70.1.1
[    4.664536] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc_7.9.3.bin version 7.9.3
[    4.669511] i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
[    4.670507] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
[    4.670513] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
[    4.670930] i915 0000:00:02.0: [drm] GT0: GUC: RC enabled

[    4.755485] i915 0000:00:02.0: [drm] *ERROR* DSI trancoder not disabled

[    6.473685] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.pipe_mode.crtc_htotal (expected 2842, found 2720)
[    6.473689] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.pipe_mode.crtc_hblank_end (expected 2842, found 2720)
[    6.473690] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.pipe_mode.crtc_hsync_start (expected 2762, found 1380)
[    6.473691] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.pipe_mode.crtc_hsync_end (expected 2802, found 1400)
[    6.473692] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.pipe_mode.crtc_vtotal (expected 1710, found 1800)
[    6.473693] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.pipe_mode.crtc_vblank_end (expected 1710, found 1800)
[    6.473694] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.adjusted_mode.crtc_htotal (expected 2842, found 2720)
[    6.473695] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.adjusted_mode.crtc_hblank_end (expected 2842, found 2720)
[    6.473696] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.adjusted_mode.crtc_hsync_start (expected 2762, found 1380)
[    6.473697] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.adjusted_mode.crtc_hsync_end (expected 2802, found 1400)
[    6.473698] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.adjusted_mode.crtc_vtotal (expected 1710, found 1800)
[    6.473699] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.adjusted_mode.crtc_vblank_end (expected 1710, found 1800)
[    6.473700] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in pixel_rate (expected 291594, found 332418)
[    6.473702] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.pipe_mode.crtc_clock (expected 291594, found 332418)
[    6.473703] i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in hw.adjusted_mode.crtc_clock (expected 291594, found 332418)
[    6.473705] ------------[ cut here ]------------
[    6.473705] i915 0000:00:02.0: [drm] pipe state doesn't match!
[    6.473726] WARNING: CPU: 7 PID: 530 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:223 intel_modeset_verify_crtc+0x31c/0x500 [i915]

Is this notebook still under warranty? If yes, try to get another one ...

[Shwen_Y]

Thank you, pietinger, for your quickly reply, which is eventually confirmed the reason of the problem.

Booting with kernel 6.18 or 6.19 is not possible. I just tried booting with debian which is installed on a mobile hard drive and its kernel is 6.19.6, it stucks again even at a very early stage. And the error seems to be: SMBus is busy.

Unfortunately, the notebook is out of the warranty period for more than 2 years.

Even though it gets serious problem when booting with kernel 6.12, it can work, so I'll continue to use it with kernel 6.12. And that's the reason I ingnore the problem with the integrated GPU of Intel CPU i7-1160G7.

I'll keep trying new kernels to see if this problem is fixed.

[pietinger]

Maybe try to update the BIOS (as a last ressort)?

[Shwen_Y]

When there is an official update of BIOS, I'll try with the newest kernel to see the problem is still there or not.