| View previous topic :: View next topic |
| Author |
Message |
luckySimba
n00b
Joined: 23 Dec 2022
Posts: 59
|
 Posted: Mon Jan 02, 2023 9:58 pm Post subject: |
 |
|
| NeddySeagoon wrote: | luckySimba,
A long time ago udev used to do firmware loading, rather than the kernel.
Then udev dropped firmware loading which lead to a heated exchange between Linus and Lennart.
Only the kernel does firmware loading now.
The kernel module will only load the firmware its told to look for. |
That’s a pretty cool piece of history. With the little I know I feel like the kernel is the way to do it. More organized. |
|
| Back to top |
|
 |
luckySimba
n00b
Joined: 23 Dec 2022
Posts: 59
|
| Posted: Mon Jan 02, 2023 10:00 pm Post subject: |
|
|
| Hu wrote: | | Firmware loading is handled by the kernel. If it is not working, then it is not yet configured correctly. On a kernel where it failed to load the firmware, and dmesg says so, what is the output of dmesg | grep so-a0-hr-b0-6 ; namei -l /lib/firmware/iwlwifi-so-a0-hr-b0-6{6,5,4}.ucode ; emerge --pretend --verbose sys-kernel/linux-firmware? As I read your dmesg output, those are the only files your kernel tries to load. If Intel is showing something else, they may be thinking of a different kernel version than the one you are using. What files is Intel reporting, and where did you see them recommend that? |
Thanks for the input Hu,
I’m gonna have to do those commands in a little bit but this is where I get the info from intel
https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html
It seems Intel is designating firmware vers based on kernel version
I did do the sys/kernel-firmware package and I have multiple firmwares for iwlwifi. |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4152
Location: Bavaria
|
| Posted: Tue Jan 03, 2023 12:26 am Post subject: |
|
|
luckySimba,
I would like to see (again) your actual kernel config. (dont hurry; I will see it at earliest tomorrow) |
|
| Back to top |
|
|
luckySimba
n00b
Joined: 23 Dec 2022
Posts: 59
|
| Posted: Tue Jan 03, 2023 8:34 am Post subject: |
|
|
| Hu wrote: | | Firmware loading is handled by the kernel. If it is not working, then it is not yet configured correctly. On a kernel where it failed to load the firmware, and dmesg says so, what is the output of dmesg | grep so-a0-hr-b0-6 ; namei -l /lib/firmware/iwlwifi-so-a0-hr-b0-6{6,5,4}.ucode ; emerge --pretend --verbose sys-kernel/linux-firmware? As I read your dmesg output, those are the only files your kernel tries to load. If Intel is showing something else, they may be thinking of a different kernel version than the one you are using. What files is Intel reporting, and where did you see them recommend that? |
| Code: |
# dmesg | grep so-a0-hr-b0-6 ; namei -l /lib/firmware/iwlwifi-so-a0-hr-b0-6{6,5,4}.ucode
[ 2.830549] Loading firmware: iwlwifi-so-a0-hr-b0-66.ucode
[ 2.830587] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-hr-b0-66.ucode failed with error -2
[ 2.830628] iwlwifi 0000:00:14.3: Falling back to sysfs fallback for: iwlwifi-so-a0-hr-b0-66.ucode
[ 66.760355] Loading firmware: iwlwifi-so-a0-hr-b0-65.ucode
[ 66.760410] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-hr-b0-65.ucode failed with error -2
[ 66.760417] iwlwifi 0000:00:14.3: Falling back to sysfs fallback for: iwlwifi-so-a0-hr-b0-65.ucode
[ 128.202334] Loading firmware: iwlwifi-so-a0-hr-b0-64.ucode
[ 128.208466] iwlwifi 0000:00:14.3: loaded firmware version 64.97bbee0a.0 so-a0-hr-b0-64.ucode op_mode iwlmvm
[ 1778.940456] Loading firmware: iwlwifi-so-a0-hr-b0-64.ucode
f: /lib/firmware/iwlwifi-so-a0-hr-b0-66.ucode
drwxr-xr-x root root /
drwxr-xr-x root root lib
drwxr-xr-x root root firmware
iwlwifi-so-a0-hr-b0-66.ucode - No such file or directory
f: /lib/firmware/iwlwifi-so-a0-hr-b0-65.ucode
drwxr-xr-x root root /
drwxr-xr-x root root lib
drwxr-xr-x root root firmware
iwlwifi-so-a0-hr-b0-65.ucode - No such file or directory
f: /lib/firmware/iwlwifi-so-a0-hr-b0-64.ucode
drwxr-xr-x root root /
drwxr-xr-x root root lib
drwxr-xr-x root root firmware
-rw-r--r-- root root iwlwifi-so-a0-hr-b0-64.ucode
galagoPro /home/luckysimba # sudo emerge --pretend --verbose sys-kernel/linux-firmware
--- Invalid atom in /etc/portage/package.use/xorg-server: elogind
* IMPORTANT: config file '/etc/portage/package.use/00cpu-flags' needs updating.
* See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
* sections of the emerge man page to learn how to update config files.
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] sys-kernel/linux-firmware-20221214::gentoo USE="redistributable -compress -initramfs -savedconfig (-unknown-license)" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
* IMPORTANT: 13 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items. |
|
|
| Back to top |
|
|
luckySimba
n00b
Joined: 23 Dec 2022
Posts: 59
|
| Posted: Tue Jan 03, 2023 8:42 am Post subject: |
|
|
| pietinger wrote: | luckySimba,
I would like to see (again) your actual kernel config. (dont hurry; I will see it at earliest tomorrow) |
https://pastebin.com/SBNA0cFc
here it is my brother |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4152
Location: Bavaria
|
| Posted: Tue Jan 03, 2023 11:08 am Post subject: |
|
|
As far as I understand, IWLWIFI from kernel version 5.15.80 wants iwlwifi-so-a0-hr-b0-66.ucode or some version below. When I look into my /lib/firmware I see:
| Code: | # ls -l iwlwifi-so-a0-hr*
-rw-r--r-- 1 root root 1427384 16. Dez 16:42 iwlwifi-so-a0-hr-b0-64.ucode
-rw-r--r-- 1 root root 1429192 16. Dez 16:42 iwlwifi-so-a0-hr-b0-68.ucode
-rw-r--r-- 1 root root 1456960 16. Dez 16:42 iwlwifi-so-a0-hr-b0-71.ucode
-rw-r--r-- 1 root root 1470384 16. Dez 16:42 iwlwifi-so-a0-hr-b0-72.ucode
-rw-r--r-- 1 root root 1465208 16. Dez 16:42 iwlwifi-so-a0-hr-b0-73.ucode
-rw-r--r-- 1 root root 1475876 16. Dez 16:42 iwlwifi-so-a0-hr-b0-74.ucode
-rw-r--r-- 1 root root 1500532 16. Dez 16:42 iwlwifi-so-a0-hr-b0-77.ucode |
There exists no version 66 or version 65. So your log entries are quite normal. Another question I cannot answer (=I dont know) is WHY it needs 1 minute to check there is no version 66 and 65.
But as you can see there exists version 68 and above ... this means: It could be possible (=I dont know) that IWLWIFI from a higher kernel version (e.g. actual version 6.1.2) wants a higher version of its firmware.
I only dont understand why you have tried to use iwlwifi-ty-a0-gf-a0-59.ucode
| Code: | CONFIG_EXTRA_FIRMWARE="i915/adlp_dmc_ver2_10.bin i915/adlp_guc_62.0.3.bin i915/tgl_huc_7.9.3.bin intel-ucode/06-9a-03 iwlwifi-ty-a0-gf-a0-59.ucode"
...
CONFIG_IWLWIFI=y |
You have only two choices (for kernel 5.15.80):
| Code: | CONFIG_EXTRA_FIRMWARE="i915/adlp_dmc_ver2_10.bin i915/adlp_guc_62.0.3.bin i915/tgl_huc_7.9.3.bin intel-ucode/06-9a-03 iwlwifi-so-a0-hr-b0-64.ucode"
...
CONFIG_IWLWIFI=y |
or
| Code: | CONFIG_EXTRA_FIRMWARE="i915/adlp_dmc_ver2_10.bin i915/adlp_guc_62.0.3.bin i915/tgl_huc_7.9.3.bin intel-ucode/06-9a-03"
...
CONFIG_IWLWIFI=m |
|
|
| Back to top |
|
|
luckySimba
n00b
Joined: 23 Dec 2022
Posts: 59
|
| Posted: Tue Jan 03, 2023 11:11 am Post subject: |
|
|
| pietinger wrote: | As far as I understand, IWLWIFI from kernel version 5.15.80 wants iwlwifi-so-a0-hr-b0-66.ucode or some version below. When I look into my /lib/firmware I see:
| Code: | # ls -l iwlwifi-so-a0-hr*
-rw-r--r-- 1 root root 1427384 16. Dez 16:42 iwlwifi-so-a0-hr-b0-64.ucode
-rw-r--r-- 1 root root 1429192 16. Dez 16:42 iwlwifi-so-a0-hr-b0-68.ucode
-rw-r--r-- 1 root root 1456960 16. Dez 16:42 iwlwifi-so-a0-hr-b0-71.ucode
-rw-r--r-- 1 root root 1470384 16. Dez 16:42 iwlwifi-so-a0-hr-b0-72.ucode
-rw-r--r-- 1 root root 1465208 16. Dez 16:42 iwlwifi-so-a0-hr-b0-73.ucode
-rw-r--r-- 1 root root 1475876 16. Dez 16:42 iwlwifi-so-a0-hr-b0-74.ucode
-rw-r--r-- 1 root root 1500532 16. Dez 16:42 iwlwifi-so-a0-hr-b0-77.ucode |
There exists no version 66 or version 65. So your log entries are quite normal. Another question I cannot answer (=I dont know) is WHY it needs 1 minute to check there is no version 66 and 65.
But as you can see there exists version 68 and above ... this means: It could be possible (=I dont know) that IWLWIFI from a higher kernel version (e.g. actual version 6.1.2) wants a higher version of its firmware.
I only dont understand why you have tried to use iwlwifi-ty-a0-gf-a0-59.ucode
| Code: | CONFIG_EXTRA_FIRMWARE="i915/adlp_dmc_ver2_10.bin i915/adlp_guc_62.0.3.bin i915/tgl_huc_7.9.3.bin intel-ucode/06-9a-03 iwlwifi-ty-a0-gf-a0-59.ucode"
...
CONFIG_IWLWIFI=y |
You have only two choices (for kernel 5.15.80):
| Code: | CONFIG_EXTRA_FIRMWARE="i915/adlp_dmc_ver2_10.bin i915/adlp_guc_62.0.3.bin i915/tgl_huc_7.9.3.bin intel-ucode/06-9a-03 iwlwifi-so-a0-hr-b0-64.ucode"
...
CONFIG_IWLWIFI=y |
or
| Code: | CONFIG_EXTRA_FIRMWARE="i915/adlp_dmc_ver2_10.bin i915/adlp_guc_62.0.3.bin i915/tgl_huc_7.9.3.bin intel-ucode/06-9a-03"
...
CONFIG_IWLWIFI=m |
|
it was due to this link from intel
https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html
it also did served as an experiment. despite doing that explicit declaration it had no downstream effect whatsoever, quiet peculiar if you ask my n00b brain
also why is it searching for 66 and 65 at all, particularly when i previously declared 64 in kernel blobs? |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4152
Location: Bavaria
|
| Posted: Tue Jan 03, 2023 11:19 am Post subject: |
|
|
| luckySimba wrote: | | also why is it searching for 66 and 65 at all, particularly when i previously declared 64 in kernel blobs? |
Because it is coded IN this module (remember what I have told you about "tactics" from some modules; iwlwifi is this sort of modules). |
|
| Back to top |
|
|
luckySimba
n00b
Joined: 23 Dec 2022
Posts: 59
|
| Posted: Tue Jan 03, 2023 11:24 am Post subject: |
|
|
| pietinger wrote: | | luckySimba wrote: | | also why is it searching for 66 and 65 at all, particularly when i previously declared 64 in kernel blobs? |
Because it is coded IN this module (remember what I have told you about "tactics" from some modules; iwlwifi is this sort of modules). |
i see i see.
they coded it in the module, despite the firmware, from my searching seems to not exist at all  |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54237
Location: 56N 3W
|
| Posted: Tue Jan 03, 2023 11:41 am Post subject: |
|
|
luckySimba,
That allows the firmware to be updated (twice) with no change to the driver and if the driver is configured as <M>, not even a kernel rebuild.
The driver has to be restarted to load the new firmware, once linux-firmware has been updated.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
luckySimba
n00b
Joined: 23 Dec 2022
Posts: 59
|
| Posted: Tue Jan 03, 2023 11:43 am Post subject: |
|
|
| NeddySeagoon wrote: | luckySimba,
That allows the firmware to be updated (twice) with no change to the driver and if the driver is configured as <M>, not even a kernel rebuild.
The driver has to be restarted to load the new firmware, once linux-firmware has been updated. |
so it should be more beneficial (w respect to time) to load it into kernel and not module? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54237
Location: 56N 3W
|
| Posted: Tue Jan 03, 2023 12:59 pm Post subject: |
|
|
luckySimba,
The other way round. Make in a loadable module.
When you build it in, you must give the firmware file name explicitly, in the kernel configuration.
One day, the file you are using may be removed from linux-firmware because it old and out of date.
Then your kernel build will fail.
As a loadable module. iwlwifi searches for the newest file(s) it knows about and if they are not found, tries earlier versions
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
luckySimba
n00b
Joined: 23 Dec 2022
Posts: 59
|
| Posted: Tue Jan 03, 2023 6:32 pm Post subject: |
|
|
| NeddySeagoon wrote: | luckySimba,
The other way round. Make in a loadable module.
When you build it in, you must give the firmware file name explicitly, in the kernel configuration.
One day, the file you are using may be removed from linux-firmware because it old and out of date.
Then your kernel build will fail.
As a loadable module. iwlwifi searches for the newest file(s) it knows about and if they are not found, tries earlier versions |
Ok will do. I was just trying to do anything to avoid waiting so long for it to
load |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54237
Location: 56N 3W
|
| Posted: Tue Jan 03, 2023 6:47 pm Post subject: |
|
|
luckySimba,
There is something else wrong. It should only be a fraction of a second to load.
No long pauses.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Networking & Security
