Puppy Linux Discussion Forum

Puppy cannot connect to the network,The driver should be missing,Please help.

Device information displayed in Puppy linux:

dmsg | grep 'irmware'
[ 0.840995] [Firmware Bug]: Invalid critical threshold (0)
[ 7.854042] [Firmware Bug]: ACPI(PXSX) defines _DOD but not _DOS
[ 7.858536] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[ 7.931683] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-50.ucode failed with error -2
[ 7.931738] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-49.ucode failed with error -2
[ 7.931791] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-48.ucode failed with error -2
[ 7.931845] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-47.ucode failed with error -2
[ 7.931897] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-46.ucode failed with error -2
[ 7.931950] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-45.ucode failed with error -2
[ 7.932003] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-44.ucode failed with error -2
[ 7.932053] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-43.ucode failed with error -2
[ 7.932106] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-42.ucode failed with error -2
[ 7.932158] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-41.ucode failed with error -2
[ 7.932209] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-40.ucode failed with error -2
[ 7.932261] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-39.ucode failed with error -2
[ 7.932263] iwlwifi 0000:00:14.3: no suitable firmware found!
[ 7.932267] iwlwifi 0000:00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
[ 9.446743] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 9.446825] bluetooth hci0: Direct firmware load for intel/ibt-19-0-1.sfi failed with error -2
[ 9.446827] Bluetooth: hci0: Failed to load Intel firmware file (-2)

spci -nn | grep 'Network'
00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9462 [8086:02f0]

Device information displayed in Windows system: Intel(R) Wireless-AC 9560 160MHz

Thank you very much！

@fhwuxue - you are missing a firmware file (see link below). Download the 1mb file & place it in /lib/firmware.
Should then be able to connect to network.
https://github.com/jwboyer/linux-firmwa ... 0-48.ucode

In the future, please tell us what specific Puppy Linux version, you are using.

The name of the Puppy ISO file is the best info.

There are many versions of Puppy, that people are still using, and they are all, slightly different.
Even the difference of 32bit or 64bit version is important.

Really, this information is best to provide:
viewtopic.php?t=218

ozsouth wrote: ↑Mon Jan 17, 2022 2:04 am

@fhwuxue - you are missing a firmware file (see link below). Download the 1mb file & place it in /lib/firmware.
Should then be able to connect to network.
https://github.com/jwboyer/linux-firmwa ... 0-48.ucode

@bigpup

Thank you for your reply!
Unfortunately, due to restrictions, I can't access the website you provided.
My email: fhwuxue@hotmail.com , if you can transfer the patch through it, I will be grateful!
Next, I will introduce my computer and puppy system in detail:

Puppy version: Ubuntu Focal, 64-bit, FossaPup64 9.5

Installation mode: frugal installation, copy files to directory: /dev/nvme0n1p5/boot/puppy, GRUB2 boot
menuentry "Puppy Linux" --unrestricted {
set root=(hd0,gpt5)
linux /boot/puppy/vmlinuz psubdir=/boot/puppy pfix=fsck,copy PMEDIA=atahd
initrd /boot/puppy/initrd.gz
}

uname -a
Linux puppy_matebookxpro 5.4.53 #1 SMP PREEMPT Sun Jul 26 12:11:02 BST 2020 x86_64 x86_64 x86_64 GNU/Linux

cat /proc/cpuinfo | grep "model name"
model name: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz

cat /proc/meminfo | grep "MemTotal"
MemTotal: 16139200 kB

lspci | grep -i 'VGA'
VGA compatible controller: Intel Corporation UHD Graphics (rev 02)

lspci | grep -i 'Network'
Network controller: Intel Corporation Wireless-AC 9462

dmidecode | grep -i 'serial number'
Serial Number: VMSBB20524800110
Serial Number: BBBX89205E002239

fdisk -l
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 616447 614400 300M EFI System, fat32
/dev/nvme0n1p2 616448 878591 262144 128M Microsoft reserved
/dev/nvme0n1p3 878592 208986111 208107520 99.2G Microsoft basic data, ntfs
/dev/nvme0n1p4 208986112 210593791 1607680 785M Windows recovery environmen
/dev/nvme0n1p5 210595840 420313087 209717248 100G Microsoft basic data, ntfs
/dev/nvme0n1p6 420313088 1000215182 579902095 276.5G Microsoft basic data, ntfs

dmesg | grep -i 'eth'
[ 4.700071] ACPI Error: Aborting method \_SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 7.539854] wmi_bus wmi_bus-PNP0C14:01: WQ data block query control method not found
[ 7.539857] wmi_bus wmi_bus-PNP0C14:01: WQ data block query control method not found
[ 7.539859] wmi_bus wmi_bus-PNP0C14:01: WQ data block query control method not found
[ 7.539861] wmi_bus wmi_bus-PNP0C14:01: WQ data block query control method not found
[ 8.408412] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.RP05.PXSX handle
[ 23.406473] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

lspci
00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem
00:14.0 USB controller: Intel Corporation Device 02ed
00:14.2 RAM memory: Intel Corporation Device 02ef
00:14.3 Network controller: Intel Corporation Wireless-AC 9462
00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller
00:15.1 Serial bus controller [0c80]: Intel Corporation Comet Lake Serial IO I2C Host Controller
00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface
00:19.0 Serial bus controller [0c80]: Intel Corporation Device 02c5
00:1c.0 PCI bridge: Intel Corporation Device 02bc (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device 0284
00:1f.3 Audio device: Intel Corporation Device 02c8
00:1f.4 SMBus: Intel Corporation Device 02a3
00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller
01:00.0 3D controller: NVIDIA Corporation GP108BM [GeForce MX250] (rev a1)
02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5006

If you need other information, I will provide it in detail.
Thank you again!

Did you try what ozsouth posted?
Adding the needed firmware.

bigpup wrote: ↑Mon Jan 17, 2022 7:45 pm

Did you try what ozsouth posted?
Adding the needed firmware.

＠ozsouth

I have downloaded the firmware and installed it successfully. Now I will reply to you through puppy!
This is a very pleasant experience!
Thank you again!