Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
-
roadie
- Full of knowledge

- Posts: 428
- Joined: 02 Jan 2011, 18:41
- Distribution: Porteus v5.01.....PorteuX v1.4
- Location: In the bush now
Post#1876
by roadie » 19 Aug 2023, 18:58
Ed_P wrote: ↑19 Aug 2023, 18:06
So apparently PorteuX kernels don't work with Porteu
S. Maybe we need a PorteuX Kernel Builder thread so we don't confuse users.
Ed_P,
As a user, I find your conclusion that PorteuX kernels don't work with Porteus to be very confusing. Of course they work, no reason they wouldn't unless a needed kernel module or firmware is not included.
As seen here:
Code: Select all
root@porteus:/home/guest# uname -a
Linux porteus.example.net 6.3.13-porteux #1 SMP PREEMPT_DYNAMIC Fri Aug 4 19:53:00 CEST 2023 x86_64 AMD A10-9620P RADEON R5, 10 COMPUTE CORES 4C+6G AuthenticAMD GNU/Linux
Porteus doesn't seem to care that it's been booted with a PorteuX kernel.
roadie
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#1877
by Ed_P » 19 Aug 2023, 22:15
roadie wrote: ↑19 Aug 2023, 18:58
no reason they wouldn't unless a needed kernel module or firmware is not included.
Yup. Or a different compression method. And thanks for pointing out the 6.3.13 ISO I boot's kernel is a porteuX one. I had not picked up on that.
Ed_P wrote: ↑19 Aug 2023, 14:59
fulalas's 6.3.13 works for me with no wifi module needed.
Ed_P wrote: ↑18 Aug 2023, 23:16
And this from the 6.3.13 system without the wifi module.
Code: Select all
Enter root's password
Password:
uname -a
Linux porteus.example.net 6.3.13-porteux #1 SMP PREEMPT_DYNAMIC Fri Aug 4 19:53:00 CEST 2023 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux
Added in 5 hours 27 minutes 41 seconds:
With
fulalas's 6.4.11 kernel.
Code: Select all
~# uname -a
Linux porteus.example.net 6.4.11-porteus #1 SMP PREEMPT_DYNAMIC Sat Aug 19 10:54:06 MSK 2023 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux
~# cat /etc/porteus/*
001-core.xzm:20230617
002-xorg.xzm:20230617
002-xtra.xzm:20221211
003-cinnamon.xzm:20220925
initrd.xz:20220928
~# ls -l /mnt/live/memory/images
000-kernel.xzm : Aug 19 04:02
001-core.xzm : Jun 14 00:42
002-xorg.xzm : Jun 17 01:18
002-xtra.xzm : Dec 11 2022
003-cinnamon.xzm : Sep 25 2022
011-slapt-get-0.11.6-x86_64-2gv.xzm : Oct 29 2022
06-crippled_sources-6.4.11-64bit.xzm : Aug 19 04:01
07-printing-x86_64-2023-02-04.xzm : Feb 4 2023
DellBlueTooth.xzm : Feb 20 13:38
GETMODtweaks.xzm : Feb 17 2023
firefox-110.0-x86_64-en-US.xzm : Feb 16 2023
mychanges.xzm : Aug 19 01:56
~# cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/Porteus-CINNAMON-v5.0-x86_64-230616-6.4.11-fulalas.iso volume=10 reboot=cold extramod=/porteus5.0/Modules noload=kde;jinn;lxqt;xfce;lxde;mate;open;dat.xzm;menu2
ISO: /ISOs/Porteus-CINNAMON-v5.0-x86_64-230616-6.4.11-fulalas.iso
And without my wifi module no wifi just like the other 6.4.** kernels and their "ucode failed with error -2" errors.
Code: Select all
uname -a
Linux porteus.example.net 6.4.11-porteus #1 SMP PREEMPT_DYNAMIC Sat Aug 19 10:54:06 MSK 2023 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux
modinfo -F firmware /lib/modules/6.4.11-porteus/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
iwlwifi-100-5.ucode
iwlwifi-1000-5.ucode
iwlwifi-135-6.ucode
iwlwifi-105-6.ucode
iwlwifi-2030-6.ucode
iwlwifi-2000-6.ucode
iwlwifi-5150-2.ucode
iwlwifi-5000-5.ucode
iwlwifi-6000g2b-6.ucode
iwlwifi-6000g2a-6.ucode
iwlwifi-6050-5.ucode
iwlwifi-6000-6.ucode
iwlwifi-7265D-29.ucode
iwlwifi-7265-17.ucode
iwlwifi-3168-29.ucode
iwlwifi-3160-17.ucode
iwlwifi-7260-17.ucode
iwlwifi-8265-36.ucode
iwlwifi-8000C-36.ucode
iwlwifi-9260-th-b0-jf-b0-46.ucode
iwlwifi-9000-pu-b0-jf-b0-46.ucode
iwlwifi-BzBnj-b0-fm-b0-78.ucode
iwlwifi-gl-b0-fm-b0-78.ucode
iwlwifi-bz-a0-fm4-b0-78.ucode
iwlwifi-bz-a0-fm4-a0-78.ucode
iwlwifi-BzBnj-b0-hr-b0-78.ucode
iwlwifi-BzBnj-b0-hr-b0-78.ucode
iwlwifi-BzBnj-a0-hr-b0-78.ucode
iwlwifi-BzBnj-b0-gf4-a0-78.ucode
iwlwifi-BzBnj-a0-gf4-a0-78.ucode
iwlwifi-BzBnj-b0-gf-a0-78.ucode
iwlwifi-BzBnj-a0-gf-a0-78.ucode
iwlwifi-BzBnj-b0-fm4-b0-78.ucode
iwlwifi-BzBnj-a0-fm4-a0-78.ucode
iwlwifi-BzBnj-a0-fm-a0-78.ucode
iwlwifi-gl-a0-fm-a0-78.ucode
iwlwifi-bz-a0-fm-b0-78.ucode
iwlwifi-bz-a0-fm-a0-78.ucode
iwlwifi-bz-a0-mr-a0-78.ucode
iwlwifi-bz-a0-gf4-a0-78.ucode
iwlwifi-bz-a0-gf-a0-78.ucode
iwlwifi-bz-a0-hr-b0-78.ucode
iwlwifi-bz-a0-hr-b0-78.ucode
iwlwifi-SoSnj-a0-mr-a0-78.ucode
iwlwifi-ma-b0-fm-a0-78.ucode
iwlwifi-ma-b0-mr-a0-78.ucode
iwlwifi-ma-b0-gf4-a0-78.ucode
iwlwifi-ma-b0-gf-a0-78.ucode
iwlwifi-ma-b0-hr-b0-78.ucode
iwlwifi-ma-a0-fm-a0-78.ucode
iwlwifi-ma-a0-mr-a0-78.ucode
iwlwifi-ma-a0-gf4-a0-78.ucode
iwlwifi-ma-a0-gf-a0-78.ucode
iwlwifi-ma-a0-hr-b0-78.ucode
iwlwifi-SoSnj-a0-jf-b0-78.ucode
iwlwifi-SoSnj-a0-hr-b0-78.ucode
iwlwifi-SoSnj-a0-gf-a0-78.ucode
iwlwifi-SoSnj-a0-gf4-a0-78.ucode
iwlwifi-ty-a0-gf-a0-78.ucode
iwlwifi-so-a0-gf-a0-78.ucode
iwlwifi-so-a0-hr-b0-78.ucode
iwlwifi-so-a0-jf-b0-78.ucode
iwlwifi-cc-a0-78.ucode
iwlwifi-QuQnj-b0-jf-b0-78.ucode
iwlwifi-QuZ-a0-jf-b0-78.ucode
iwlwifi-QuZ-a0-hr-b0-78.ucode
iwlwifi-Qu-b0-jf-b0-78.ucode
iwlwifi-Qu-c0-hr-b0-78.ucode
iwlwifi-QuQnj-b0-hr-b0-78.ucode
iwlwifi-Qu-b0-hr-b0-78.ucode
dmesg | egrep 'ucode|wifi'
[ 2.160057] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 2.179218] iwlwifi 0000:00:14.3: Detected crf-id 0x3617, cnv-id 0x20000302 wfpm id 0x80000000
[ 2.179242] iwlwifi 0000:00:14.3: PCI dev a0f0/4070, rev=0x351, rfid=0x10a100
[ 2.179353] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-78.ucode failed with error -2
[ 2.179396] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-77.ucode failed with error -2
[ 2.179438] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-76.ucode failed with error -2
[ 2.179479] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-75.ucode failed with error -2
[ 2.179521] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-74.ucode failed with error -2
[ 2.179563] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-73.ucode failed with error -2
[ 2.179602] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-72.ucode failed with error -2
[ 2.179643] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-71.ucode failed with error -2
[ 2.179684] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-70.ucode failed with error -2
[ 2.179724] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-69.ucode failed with error -2
[ 2.179763] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-68.ucode failed with error -2
[ 2.179803] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-67.ucode failed with error -2
[ 2.179845] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-66.ucode failed with error -2
[ 2.179885] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-65.ucode failed with error -2
[ 2.179925] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-64.ucode failed with error -2
[ 2.179965] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-63.ucode failed with error -2
[ 2.180004] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-62.ucode failed with error -2
[ 2.180044] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-61.ucode failed with error -2
[ 2.180083] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-60.ucode failed with error -2
[ 2.180124] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
[ 2.180163] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-58.ucode failed with error -2
[ 2.180205] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-57.ucode failed with error -2
[ 2.180244] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-56.ucode failed with error -2
[ 2.180287] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-55.ucode failed with error -2
[ 2.180327] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-54.ucode failed with error -2
[ 2.180367] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-53.ucode failed with error -2
[ 2.180406] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-52.ucode failed with error -2
[ 2.180444] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-51.ucode failed with error -2
[ 2.180483] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
[ 2.180524] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
[ 2.180563] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-48.ucode failed with error -2
[ 2.180603] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-47.ucode failed with error -2
[ 2.180642] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-46.ucode failed with error -2
[ 2.180690] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-45.ucode failed with error -2
[ 2.180733] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-44.ucode failed with error -2
[ 2.180773] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-43.ucode failed with error -2
[ 2.180813] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-42.ucode failed with error -2
[ 2.180851] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-41.ucode failed with error -2
[ 2.180889] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-40.ucode failed with error -2
[ 2.180927] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
[ 2.180929] iwlwifi 0000:00:14.3: no suitable firmware found!
[ 2.180931] iwlwifi 0000:00:14.3: minimum version required: iwlwifi-QuZ-a0-hr-b0-39
[ 2.180934] iwlwifi 0000:00:14.3: maximum version supported: iwlwifi-QuZ-a0-hr-b0-78
[ 2.180936] iwlwifi 0000:00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
Ed_P
-
rych
- Warlord

- Posts: 767
- Joined: 04 Jan 2014, 04:27
- Distribution: Porteus 5.0 x64 OpenBox
- Location: NZ
-
Contact:
Post#1878
by rych » 20 Aug 2023, 10:25
roadie wrote: ↑19 Aug 2023, 18:58
Of course they work...
root@porteus:/home/guest# uname -a
Linux porteus.example.net 6.3.13-porteux #1 SMP PREEMPT_DYNAMIC Fri Aug 4 19:53:00 CEST 2023 x86_64 AMD A10-9620P RADEON R5, 10 COMPUTE CORES 4C+6G AuthenticAMD GNU/Linux
Porteus doesn't seem to care that it's been booted with a PorteuX kernel.
That's nice. I assume the Nvidia driver bundled with PorteuX and built against its kernel can also be used in Porteus. Will test, should work! Thanks @porteux! I'll be
stealing your kernel+nvidia driver to upgrade my Porteus a little:) I think this means just the 3 files: vmlinuzX, 000-kernel-6.2.16.xzm, and 08-nvidia-525.85.05-k.6.2.16-porteux-x86_64.xzm
rych
-
roadie
- Full of knowledge

- Posts: 428
- Joined: 02 Jan 2011, 18:41
- Distribution: Porteus v5.01.....PorteuX v1.4
- Location: In the bush now
Post#1879
by roadie » 20 Aug 2023, 16:39
@Ed_P,
I'm not sure what you mean by "different compression method". Porteus and PorteuX can handle both xz and zstd kernel compression and these are the most common methods used these days. And, you're welcome, I'm happy to help in my own little way.
@rych,
You can definitely try the PorteuX kernel and 08-nvidia-525.85.05-k.6.2.16-porteux-x86_64.xzm......but I think that the nvidia .xzm has possibly been compiled with a different version of libraries, and you may run into a glibc mismatch.
roadie
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#1880
by Ed_P » 20 Aug 2023, 17:29
roadie wrote: ↑20 Aug 2023, 16:39
I'm not sure what you mean by "different compression method". Porteus and PorteuX can handle both xz and zstd kernel compression and these are the most common methods used these days.
I could be wrong but I relate the "error -2" error to the api flags index 2 flags msg below them which to me implies a compression issue.
[ 1.647776] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-73.ucode failed with error -2
[ 1.647805] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-72.ucode failed with error -2
[ 1.714449] iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
Ed_P
-
roadie
- Full of knowledge

- Posts: 428
- Joined: 02 Jan 2011, 18:41
- Distribution: Porteus v5.01.....PorteuX v1.4
- Location: In the bush now
Post#1881
by roadie » 20 Aug 2023, 18:46
Ed_P wrote: ↑20 Aug 2023, 17:29
roadie wrote: ↑20 Aug 2023, 16:39
I'm not sure what you mean by "different compression method". Porteus and PorteuX can handle both xz and zstd kernel compression and these are the most common methods used these days.
I could be wrong but I relate the "error -2" error to the api flags index 2 flags msg below them which to me implies a compression issue.
[ 1.647776] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-73.ucode failed with error -2
[ 1.647805] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-72.ucode failed with error -2
[ 1.714449] iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
I'm way out of my league here, but I see the errors as the kernel driver not being able to use the firmware supplied because of some mismatch in the file size it's expecting and what it's seeing. It could come from the kernel source files which determine that, or the firmware files.
Maybe it comes down to the version of firmware being used and the kernel source not playing nicely together. And iwlwifi seems to experience problems with kernel upgrades.
roadie
-
porteux
- Shogun

- Posts: 271
- Joined: 12 Mar 2023, 22:10
- Distribution: PorteuX
Post#1882
by porteux » 20 Aug 2023, 19:32
PorteuX compress all its modules using zstd (bigger and faster), while Porteus uses xz compression (smaller and slower).
If one wants to have a newer Nvidia driver, it's not that hard to compile it. Here's the step by step for both PorteuX and Porteus:
1- Boot into text mode
2- Make sure devel, crippled and blacklist modules are enabled
3- Install Nvidia driver by executing the .run (
https://www.nvidia.com/en-us/drivers/unix/) as sudo (install the 32 bit libraries if you don't know what to do)
4- Now execute createModule.sh script
5- In the end it will create the Nvidia driver module and copy it to your porteux/modules folder
6- Reboot into normal mode
Both blacklist module and createModule.sh script can be downloaded from the PorteuX repository:
https://github.com/porteux/porteux/tree ... dia-driver
porteux
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#1883
by Ed_P » 20 Aug 2023, 22:13
roadie wrote: ↑20 Aug 2023, 18:46
I see the errors as the kernel driver not being able to use the firmware supplied because of some mismatch in the file size it's expecting and what it's seeing. It could come from the kernel source files which determine that, or the firmware files.
Exactly. Since the kernel driver and firmware files are both in the 6.4.x kernel and the problem does not exist in the 6.3.13 kernel or any of the other kernels I've used over the past couple of years.
Code: Select all
guest@porteus:/mnt/nvme0n1p7/ISOs$ ls -ont Porteus*iso
-rwxrwxrwx 1 1000 441257984 Aug 19 21:09 Porteus-CINNAMON-v5.0-x86_64-230616-6.4.11-fulalas.iso*
-rwxrwxrwx 1 1000 430688256 Aug 18 13:19 Porteus-CINNAMON-v5.0-x86_64-230616-6.4.11.iso*
-rwxrwxrwx 1 1000 430700544 Aug 17 01:20 Porteus-CINNAMON-v5.0-x86_64-230616-6.4.10.iso*
-rwxrwxrwx 1 1000 409411584 Aug 6 00:34 Porteus-CINNAMON-v5.0-x86_64-230616-6.3.13.iso*
-rwxrwxrwx 1 1000 391520256 Jul 28 00:11 Porteus-CINNAMON-v5.0-x86_64-230616-6.4.6.iso*
-rwxrwxrwx 1 1000 396531712 Jun 24 13:54 Porteus-CINNAMON-v5.0-x86_64-230616-6.3.7.iso*
-rwxrwxrwx 1 1000 395929600 May 20 01:56 Porteus-CINNAMON-v5.0-x86_64-230430.iso*
-rwxrwxrwx 1 1000 395634688 Apr 22 13:11 Porteus-CINNAMON-v5.0-x86_64-230421.iso*
-rwxrwxrwx 1 1000 395055104 Apr 11 20:09 Porteus-CINNAMON-v5.0-x86_64-230406.iso*
-rwxrwxrwx 1 1000 375834624 Apr 10 17:58 Porteus-CINNAMON-v5.0-x86_64-230402.iso*
-rwxrwxrwx 1 1000 375834624 Mar 24 15:58 Porteus-CINNAMON-v5.0-x86_64-230217.iso*
-rwxrwxrwx 1 1000 375388160 Dec 15 2022 Porteus-CINNAMON-v5.0-x86_64-221210.iso*
-rwxrwxrwx 1 1000 375244800 Oct 11 2022 Porteus-CINNAMON-v5.0-x86_64-220924.iso*
-rwxrwxrwx 1 1000 376438784 Aug 23 2022 Porteus-CINNAMON-v5.0-x86_64.iso*
-rwxrwxrwx 1 1000 375463936 Aug 19 2022 Porteus-CINNAMON-v5.0-x86_64-220723.iso*
-rwxrwxrwx 1 1000 376438784 Aug 10 2022 Porteus-CINNAMON-v5.0-x86_64x.iso*
-rwxrwxrwx 1 1000 376522752 Aug 4 2022 Porteus-CINNAMON-v5.0-x86_64-220727.iso*
-rwxrwxrwx 1 1000 364095488 Apr 2 2022 Porteus-CINNAMON-v4.0-x86_64-5.17.1.iso*
Note the way around the 6.4.x problem is to provide the kernel with the same necessary firmware files in a separate module.
Ed_P
-
Blaze
- DEV Team

- Posts: 3994
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
-
Contact:
Post#1884
by Blaze » 21 Aug 2023, 04:20
This is zstd version of kernel
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
Blaze
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#1885
by Ed_P » 21 Aug 2023, 05:42
Blaze can you explain the "error -2" loading the wifi ucode?
Ed_P
-
rych
- Warlord

- Posts: 767
- Joined: 04 Jan 2014, 04:27
- Distribution: Porteus 5.0 x64 OpenBox
- Location: NZ
-
Contact:
Post#1886
by rych » 21 Aug 2023, 07:54
rych wrote: ↑20 Aug 2023, 10:25
I think this means just the 3 files: vmlinuzX, 000-kernel-6.2.16.xzm, and 08-nvidia-525.85.05-k.6.2.16-porteux-x86_64.xzm
OK, using PorteuX's kernel 000-kernel-6.2.16.xzm worked fine in Porteus. However, I forgot to replace
vmlinuz and it worked anyway. That is Porteus's vmlinuz (which came with 5.18 kernel) and the PorteuX's 000-kernel-6.2.16.xzm. Could it be that vmlinuz is kernel-agnostic?! I then replaced vmlinuz with vmlinuzX to match the new kernel -- still worked of course, although seemed a bit slower to start (subjective). Will test nvidia driver later.
rych
-
Blaze
- DEV Team

- Posts: 3994
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
-
Contact:
Post#1887
by Blaze » 21 Aug 2023, 17:16
Ed_P, create /etc/modprobe.d/iwl.conf
Code: Select all
options iwlwifi 11n_disable=1
options iwlwifi swcrypto=0
options iwlwifi bt_coex_active=0
options iwlwifi power_save=0
options iwlwifi uapsd_disable=1
options iwlmvm power_scheme=1
and reboot Porteus
I found this solution is here
https://bbs.archlinux.org/viewtopic.php ... 4#p1919564
Blaze
-
roadie
- Full of knowledge

- Posts: 428
- Joined: 02 Jan 2011, 18:41
- Distribution: Porteus v5.01.....PorteuX v1.4
- Location: In the bush now
Post#1888
by roadie » 21 Aug 2023, 18:36
rych wrote: ↑21 Aug 2023, 07:54
rych wrote: ↑20 Aug 2023, 10:25
I think this means just the 3 files: vmlinuzX, 000-kernel-6.2.16.xzm, and 08-nvidia-525.85.05-k.6.2.16-porteux-x86_64.xzm
OK, using PorteuX's kernel 000-kernel-6.2.16.xzm worked fine in Porteus. However, I forgot to replace
vmlinuz and it worked anyway. That is Porteus's vmlinuz (which came with 5.18 kernel) and the PorteuX's 000-kernel-6.2.16.xzm. Could it be that vmlinuz is kernel-agnostic?! I then replaced vmlinuz with vmlinuzX to match the new kernel -- still worked of course, although seemed a bit slower to start (subjective). Will test nvidia driver later.
rych,
If everything worked with that combination, I'm sure it would be because the 5.18 kernel modules were still available to the system. The 5.18 kernel would not work with 6.2.16 modules, or any version except 5.18. There would be no functioning devices, and usually not a working desktop. Anytime I've changed the kernel, but not included the matching 000-kernel.xzm, it has never worked out well. I've also seen where a kernel won't accept kernel modules of the same version, but not built at the same time that the kernel was........the kernel (vmlinuz) is actually quite fussy.
I'm thinking that this is getting off topic as it doesn't concern the Porteus Kernel Builder, maybe a new one should be started somewhere else to report the results of testing the PorteuX nvidia .xzm in Porteus. I really don't want to offend
neko. If a new thread is started in another section, possibly a mod or admin could move the relevant posts?
roadie
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#1889
by Ed_P » 21 Aug 2023, 19:07
Blaze wrote: ↑21 Aug 2023, 17:16
Ed_P, create /etc/modprobe.d/iwl.conf
Ok. Which system: 6.3.13, 6.4.10, 6.4.11 or 6.4.11.fulalas?
Added in 12 minutes 21 seconds:
Porteus-CINNAMON-v5.0-x86_64-230616-6.4.11-fulalas.iso
Code: Select all
guest@porteus:/etc/modprobe.d$ cat iwl.conf
options iwlwifi 11n_disable=1
options iwlwifi swcrypto=0
options iwlwifi bt_coex_active=0
options iwlwifi power_save=0
options iwlwifi uapsd_disable=1
options iwlmvm power_scheme=1
guest@porteus:/etc/modprobe.d$
Code: Select all
uname -a
Linux porteus.example.net 6.4.11-porteus #1 SMP PREEMPT_DYNAMIC Sat Aug 19 10:54:06 MSK 2023 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux
modinfo -F firmware /lib/modules/6.4.11-porteus/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
iwlwifi-100-5.ucode
:
iwlwifi-cc-a0-78.ucode
iwlwifi-QuQnj-b0-jf-b0-78.ucode
iwlwifi-QuZ-a0-jf-b0-78.ucode
iwlwifi-QuZ-a0-hr-b0-78.ucode
iwlwifi-Qu-b0-jf-b0-78.ucode
iwlwifi-Qu-c0-hr-b0-78.ucode
iwlwifi-QuQnj-b0-hr-b0-78.ucode
iwlwifi-Qu-b0-hr-b0-78.ucode
dmesg | egrep 'ucode|wifi'
[ 2.461685] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 2.464231] iwlwifi 0000:00:14.3: Detected crf-id 0x3617, cnv-id 0x20000302 wfpm id 0x80000000
[ 2.464252] iwlwifi 0000:00:14.3: PCI dev a0f0/4070, rev=0x351, rfid=0x10a100
[ 2.481823] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-78.ucode failed with error -2
[ 2.535130] iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
[ 2.535148] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[ 2.535429] iwlwifi 0000:00:14.3: loaded firmware version 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode op_mode iwlmvm
[ 2.619937] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351
[ 2.739226] iwlwifi 0000:00:14.3: Detected RF HR B5, rfid=0x10a100
[ 2.809508] iwlwifi 0000:00:14.3: base HW address: 94:e2:3c:46:53:1b
[
Ed_P
-
Blaze
- DEV Team

- Posts: 3994
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
-
Contact:
Post#1890
by Blaze » 22 Aug 2023, 04:13
Ed_P, all looks good

How about 6.4.11?
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
Blaze