#1 2025-10-07 12:02:18

MoeJoe

Member

Registered: 2020-09-13

Posts: 10

SOLVED: How to extract working drivers from Trixie and use on Boron

I have a new Lenovo Yoga 7i 2-in-1 16IML9 - Type 83DL. I installed Boron (dual boot with Win 11) on it and neither Wi-Fi nor the touchpad works (maybe other subsystems too).

I then installed Debian Trixie and both Wi-Fi and the touchpad do work.

Here is the output of lspci (this and the following output is under Boron):

00:00.0 Host bridge: Intel Corporation Device 7d02 (rev 04)
00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel Graphics] (rev 08)
00:04.0 Signal processing controller: Intel Corporation Meteor Lake-P Dynamic Tuning Technology (rev 04)
00:06.0 PCI bridge: Intel Corporation Device 7eca (rev 10)
00:07.0 PCI bridge: Intel Corporation Meteor Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 10)
00:07.2 PCI bridge: Intel Corporation Meteor Lake-P Thunderbolt 4 PCI Express Root Port #2 (rev 10)
00:08.0 System peripheral: Intel Corporation Meteor Lake-P Gaussian & Neural-Network Accelerator (rev 20)
00:0a.0 Signal processing controller: Intel Corporation Meteor Lake-P Platform Monitoring Technology (rev 01)
00:0b.0 Processing accelerators: Intel Corporation Meteor Lake NPU (rev 04)
00:0d.0 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 USB Controller (rev 10)
00:0d.2 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 NHI #0 (rev 10)
00:0d.3 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 NHI #1 (rev 10)
00:12.0 Serial controller: Intel Corporation Meteor Lake-P Integrated Sensor Hub (rev 20)
00:14.0 USB controller: Intel Corporation Meteor Lake-P USB 3.2 Gen 2x1 xHCI Host Controller (rev 20)
00:14.2 RAM memory: Intel Corporation Device 7e7f (rev 20)
00:14.3 Network controller: Intel Corporation Meteor Lake PCH CNVi WiFi (rev 20)
00:15.0 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO I2C Controller #0 (rev 20)
00:15.1 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO I2C Controller #1 (rev 20)
00:16.0 Communication controller: Intel Corporation Meteor Lake-P CSME HECI (rev 20)
00:1c.0 PCI bridge: Intel Corporation Device 7e3d (rev 20)
00:1f.0 ISA bridge: Intel Corporation Device 7e03 (rev 20)
00:1f.3 Multimedia audio controller: Intel Corporation Meteor Lake-P HD Audio Controller (rev 20)
00:1f.4 SMBus: Intel Corporation Meteor Lake-P SMBus Controller (rev 20)
00:1f.5 Serial bus controller: Intel Corporation Meteor Lake-P SPI Controller (rev 20)
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9C1a (DRAM-less)
56:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)

Here is the output of lsusb:

Bus 004 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 30c9:00c2 Luxvisions Innotech Limited Integrated RGB Camera
Bus 003 Device 002: ID 04f3:0c98 Elan Microelectronics Corp. ELAN:ARM-M4
Bus 003 Device 005: ID 0781:5530 SanDisk Corp. Cruzer
Bus 003 Device 004: ID 8087:0033 Intel Corp. AX211 Bluetooth
Bus 003 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 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Here is the output of lsusb -v 2>/dev/null | grep -E '\<(^Bus|iProduct|bDeviceClass|bDeviceProtocol)'

Bus 004 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
  bDeviceClass            0 
  bDeviceProtocol         0 
  iProduct                2 AX88179A
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  bDeviceClass            9 Hub
  bDeviceProtocol         3 
  iProduct                2 xHCI Host Controller
Bus 003 Device 003: ID 30c9:00c2 Luxvisions Innotech Limited Integrated RGB Camera
  bDeviceClass          239 Miscellaneous Device
  bDeviceProtocol         1 Interface Association
  iProduct                2 Integrated RGB Camera
Bus 003 Device 002: ID 04f3:0c98 Elan Microelectronics Corp. ELAN:ARM-M4
  bDeviceClass            0 
  bDeviceProtocol         0 
  iProduct                2 ELAN:ARM-M4
Bus 003 Device 005: ID 0781:5530 SanDisk Corp. Cruzer
  bDeviceClass            0 
  bDeviceProtocol         0 
  iProduct                2 Cruzer
Bus 003 Device 004: ID 8087:0033 Intel Corp. AX211 Bluetooth
  bDeviceClass          224 Wireless
  bDeviceProtocol         1 Bluetooth
  iProduct                0 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  bDeviceClass            9 Hub
  bDeviceProtocol         1 Single TT
  iProduct                2 xHCI Host Controller
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  bDeviceClass            9 Hub
  bDeviceProtocol         3 
  iProduct                2 xHCI Host Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  bDeviceClass            9 Hub
  bDeviceProtocol         1 Single TT
  iProduct                2 xHCI Host Controller

Is it possible for me to extract the Trixie drivers I need and use them when I reinstall Boron? If so, how?

Last edited by MoeJoe (2025-10-11 11:28:34)

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: SOLVED: How to extract working drivers from Trixie and use on Boron

The drivers are in the kernel so try the version from the bookworm-backports repository, that should be compatible with Boron.

Follow the instructions here to add the repository then install the linux-image-amd64 metapackge from bookworm-backports.

---

Para todos todo, para nosotros nada

MoeJoe

Member

Registered: 2020-09-13

Posts: 10

Re: SOLVED: How to extract working drivers from Trixie and use on Boron

Thanks much Head_on_a_Stick, that did it!