[SOLVED]Questions about some dmesg errors

[nurali]

Hello everyone
I am a new user to Gentoo,but also I am big fan of Gentoo,so I am trying many interesting things
I had compiled my first DIY kernel(sort of),then I can boot into system now
But there are some errors in dmesg log,I can not figure what they mean,so,hoping anyone can help me look at it and give me some advice
Here is dmesg outputs:
http://0x0.st/HrOz.txt
Here is my .config file:
http://0x0.st/HrO-.txt
Here is my hardware info:
https://linux-hardware.org/?probe=991db4f096

Please check(BY THE WAY:Sorry for my poor English,please don't mind if I said something uncorrect)

[pietinger]

nurali,

you have a pretty kernel configuration for your nice AMD notebook. Does something not work ?

Let me say in general: Most warnings or errors in your systemlog are okay. For example:

This is only a hint because of today module it is not able - completely normal:

Code: Select all

[    1.190440] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available

Also this is completly normal - this parameter IS FOR your initramfs and kernel MUST give it to it:

Code: Select all

[    0.046004] Unknown kernel command line parameters "BOOT_IMAGE=/vmlinuz-6.1.11-gentoo-ali", will be passed to user space.

What you can do better:
Try to give your wlan module a more actual firmware - iwlwifi-cc-a0-72.ucode (46 is rather old) is available in /lib/firmware:

Code: Select all

[    1.387868] Loading firmware: iwlwifi-cc-a0-72.ucode
[    1.387885] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-cc-a0-72.ucode failed with error -2
[...]
[    1.388127] Loading firmware: iwlwifi-cc-a0-47.ucode
[    1.388135] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-cc-a0-47.ucode failed with error -2
[    1.388137] Loading firmware: iwlwifi-cc-a0-46.ucode

=>

Code: Select all

CONFIG_EXTRA_FIRMWARE="amdgpu/green_sardine_asd.bin amdgpu/green_sardine_ce.bin amdgpu/green_sardine_dmcub.bin amdgpu/green_sardine_me.bin amdgpu/green_sardine_mec2.bin amdgpu/green_sardine_mec.bin amdgpu/green_sardine_pfp.bin amdgpu/green_sardine_rlc.bin amdgpu/green_sardine_sdma.bin amdgpu/green_sardine_ta.bin amdgpu/green_sardine_vcn.bin amd-ucode/microcode_amd_fam19h.bin regulatory.db regulatory.db.p7s iwlwifi-cc-a0-46.ucode"

Only two more:

Code: Select all

# CONFIG_PINCTRL_AMD is not set

I would enable it (but maybe you dont need it).

Code: Select all

CONFIG_AMD_IOMMU=y
CONFIG_AMD_IOMMU_V2=y
CONFIG_DMAR_TABLE=y
CONFIG_INTEL_IOMMU=y

You dont need Intel IOMMU.

If you dont use a firewall it is okay if you dont load any netfilter modules.

Because I am paranoid for security I must point to this article (costs some performance):
https://wiki.gentoo.org/wiki/User:Pieti ... _with_KSPP

[nurali]

nurali,

you have a pretty kernel configuration for your nice AMD notebook. Does something not work ?

Let me say in general: Most warnings or errors in your systemlog are okay. For example:

This is only a hint because of today module it is not able - completely normal:

Code: Select all

[    1.190440] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available

Also this is completly normal - this parameter IS FOR your initramfs and kernel MUST give it to it:

Code: Select all

[    0.046004] Unknown kernel command line parameters "BOOT_IMAGE=/vmlinuz-6.1.11-gentoo-ali", will be passed to user space.

What you can do better:
Try to give your wlan module a more actual firmware - iwlwifi-cc-a0-72.ucode (46 is rather old) is available in /lib/firmware:

Code: Select all

[    1.387868] Loading firmware: iwlwifi-cc-a0-72.ucode
[    1.387885] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-cc-a0-72.ucode failed with error -2
[...]
[    1.388127] Loading firmware: iwlwifi-cc-a0-47.ucode
[    1.388135] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-cc-a0-47.ucode failed with error -2
[    1.388137] Loading firmware: iwlwifi-cc-a0-46.ucode

=>

Code: Select all

CONFIG_EXTRA_FIRMWARE="amdgpu/green_sardine_asd.bin amdgpu/green_sardine_ce.bin amdgpu/green_sardine_dmcub.bin amdgpu/green_sardine_me.bin amdgpu/green_sardine_mec2.bin amdgpu/green_sardine_mec.bin amdgpu/green_sardine_pfp.bin amdgpu/green_sardine_rlc.bin amdgpu/green_sardine_sdma.bin amdgpu/green_sardine_ta.bin amdgpu/green_sardine_vcn.bin amd-ucode/microcode_amd_fam19h.bin regulatory.db regulatory.db.p7s iwlwifi-cc-a0-46.ucode"

Only two more:

Code: Select all

# CONFIG_PINCTRL_AMD is not set

I would enable it (but maybe you dont need it).

Code: Select all

CONFIG_AMD_IOMMU=y
CONFIG_AMD_IOMMU_V2=y
CONFIG_DMAR_TABLE=y
CONFIG_INTEL_IOMMU=y

You dont need Intel IOMMU.

If you dont use a firewall it is okay if you dont load any netfilter modules.

Because I am paranoid for security I must point to this article (costs some performance):
https://wiki.gentoo.org/wiki/User:Pieti ... _with_KSPP

I am outside now,and I am using phone to reply,it is a little difficult to quote messages,so,I am quoting all of it
My hardware are all working good for now,unless I did not use something that don't work
I am grateful and excited right now,thank you very much,I love this forum
Your suggessions are clear,understandable and helpful,thank you very much
I don't actually know if I need a firewall,I am a total outsider for all those,I am a bridge-road engeener,so,maybe I need to learn something about firewall
I'll correct my configuration as you told me,but I have to wait for my new AX210NGW
I'll read that artcle,wish that I can understand something
Thanks again

[NeddySeagoon]

nurali,

Code: Select all

[    1.388125] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-cc-a0-48.ucode failed with error -2
[    1.388127] Loading firmware: iwlwifi-cc-a0-47.ucode
[    1.388135] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-cc-a0-47.ucode failed with error -2
[    1.388137] Loading firmware: iwlwifi-cc-a0-46.ucode

The iwlwifi driver tries to load the newest firmware that it knows about.
Eventually revision -46 is found and in working.

I have

Code: Select all

ls /lib/firmware/iwlwifi-cc*
/lib/firmware/iwlwifi-cc-a0-46.ucode  /lib/firmware/iwlwifi-cc-a0-55.ucode  /lib/firmware/iwlwifi-cc-a0-66.ucode  /lib/firmware/iwlwifi-cc-a0-72.ucode
/lib/firmware/iwlwifi-cc-a0-48.ucode  /lib/firmware/iwlwifi-cc-a0-59.ucode  /lib/firmware/iwlwifi-cc-a0-67.ucode  /lib/firmware/iwlwifi-cc-a0-73.ucode
/lib/firmware/iwlwifi-cc-a0-50.ucode  /lib/firmware/iwlwifi-cc-a0-62.ucode  /lib/firmware/iwlwifi-cc-a0-68.ucode  /lib/firmware/iwlwifi-cc-a0-74.ucode
/lib/firmware/iwlwifi-cc-a0-53.ucode  /lib/firmware/iwlwifi-cc-a0-63.ucode  /lib/firmware/iwlwifi-cc-a0-71.ucode  /lib/firmware/iwlwifi-cc-a0-77.ucode

Where did you get the iwlwifi firmware from?
My list is from linux-firmware.

You should be using

Code: Select all

 [    1.387868] Loading firmware: iwlwifi-cc-a0-72.ucode
[    1.387885] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-cc-a0-72.ucode failed with error -2

but you don't have it.
You might, but its not in your

Code: Select all

CONFIG_EXTRA_FIRMWARE=

This illustrates one of the disadvantages of built in firmware. Its your problem to keep it up to date.
Every now and again, AMD adds a new firmware file for the GPUs. You build a new kernel and boot into it. The amdgpu driver now needs the missing firmware file and the console is blank.

As long as you don't mind the additional maintenance burden of built in firmware. Stick with it.
For an easy life, make things that need firmware as loadable modules.
You have

Code: Select all

CONFIG_MODULES=y

so you are not paranoid about

Code: Select all

modpobe <evil_module>

being an attack vector.

[nurali]

nurali,

Code: Select all

[    1.388125] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-cc-a0-48.ucode failed with error -2
[    1.388127] Loading firmware: iwlwifi-cc-a0-47.ucode
[    1.388135] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-cc-a0-47.ucode failed with error -2
[    1.388137] Loading firmware: iwlwifi-cc-a0-46.ucode

The iwlwifi driver tries to load the newest firmware that it knows about.
Eventually revision -46 is found and in working.

I have

Code: Select all

ls /lib/firmware/iwlwifi-cc*
/lib/firmware/iwlwifi-cc-a0-46.ucode  /lib/firmware/iwlwifi-cc-a0-55.ucode  /lib/firmware/iwlwifi-cc-a0-66.ucode  /lib/firmware/iwlwifi-cc-a0-72.ucode
/lib/firmware/iwlwifi-cc-a0-48.ucode  /lib/firmware/iwlwifi-cc-a0-59.ucode  /lib/firmware/iwlwifi-cc-a0-67.ucode  /lib/firmware/iwlwifi-cc-a0-73.ucode
/lib/firmware/iwlwifi-cc-a0-50.ucode  /lib/firmware/iwlwifi-cc-a0-62.ucode  /lib/firmware/iwlwifi-cc-a0-68.ucode  /lib/firmware/iwlwifi-cc-a0-74.ucode
/lib/firmware/iwlwifi-cc-a0-53.ucode  /lib/firmware/iwlwifi-cc-a0-63.ucode  /lib/firmware/iwlwifi-cc-a0-71.ucode  /lib/firmware/iwlwifi-cc-a0-77.ucode

Where did you get the iwlwifi firmware from?
My list is from linux-firmware.

You should be using

Code: Select all

 [    1.387868] Loading firmware: iwlwifi-cc-a0-72.ucode
[    1.387885] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-cc-a0-72.ucode failed with error -2

but you don't have it.
You might, but its not in your

Code: Select all

CONFIG_EXTRA_FIRMWARE=

This illustrates one of the disadvantages of built in firmware. Its your problem to keep it up to date.
Every now and again, AMD adds a new firmware file for the GPUs. You build a new kernel and boot into it. The amdgpu driver now needs the missing firmware file and the console is blank.

As long as you don't mind the additional maintenance burden of built in firmware. Stick with it.
For an easy life, make things that need firmware as loadable modules.
You have

Code: Select all

CONFIG_MODULES=y

so you are not paranoid about

Code: Select all

modpobe <evil_module>

being an attack vector.

Thanks for replying
That ucode comes from /lib/firmware
I wasn't sure which ucode I should build into kernel,so I downloaded firmware from Intel's website,extrackted it,then I found a '46' in extrackted folder,then I found it in /lib/firmware too,so I choose that,I thought that the '72' is for newer intel hardware,I understand now.
I wanted a kernel that without initramfs,so,I have to build them into kernel,I will look after the upgrade from now on
Thank you again

[NeddySeagoon]

nurali,

Does the PC Boot Process help your understanding?

The use of firmware and an initrd are not related.
The rule in that all the parts of the a driver must be available when the kernel initialises the driver.
There are three cases that work.
1, All the bits are in the kernel, which is what you have now.
2. All the bits are on the root filesystem. That happens when loadable modules need firmware.
The modules are in /lib/modules/ and the firmware is in /lib/firmware.
3. All the bits are in the initrd.

Any options that do not bring all the parts of a driver together when the kernel initialises the driver fail by design.

[pietinger]

nurali,

if you dont have a special need for an initramfs (e.g. encrypted root partition) AND you do your kernel configuration yourself THEN you are doing all right
... and you dont need this: https://wiki.gentoo.org/wiki/User:Pieti ... s_Overview

IF you want have a monolithic kernel (I have also for security reasons) THEN just disable module support in your kernel and DONT do this:
https://wiki.gentoo.org/wiki/Kernel_Mod ... le-less.22

Why ?

Because you can always enable module support back (if you want to test if some modules will load). A monolithic kernel is a very nice piece ... AND you can enable LOCKDOWN in your kernel without doing this:
https://wiki.gentoo.org/wiki/Signed_ker ... le_support

I have a monolithic, hardened, stub- (meaning: my UEFI boots directly my kernel without any other bootmanager like grub) kernel ... I can only recommend

Maybe you already know this article ... you dont need anymore because you have good kernel settings:
https://wiki.gentoo.org/wiki/User:Pieti ... figuration

[nurali]

nurali,

Does the PC Boot Process help your understanding?

The use of firmware and an initrd are not related.
The rule in that all the parts of the a driver must be available when the kernel initialises the driver.
There are three cases that work.
1, All the bits are in the kernel, which is what you have now.
2. All the bits are on the root filesystem. That happens when loadable modules need firmware.
The modules are in /lib/modules/ and the firmware is in /lib/firmware.
3. All the bits are in the initrd.

Any options that do not bring all the parts of a driver together when the kernel initialises the driver fail by design.

I was busy last night,sorry for took so long to reply
Quite understandable,thanks

[nurali]

nurali,

if you dont have a special need for an initramfs (e.g. encrypted root partition) AND you do your kernel configuration yourself THEN you are doing all right
... and you dont need this: https://wiki.gentoo.org/wiki/User:Pieti ... s_Overview

Yes,I don't need initramfs,it is my honor to get your approval,I,ll learn more and try to simplify my kernel as I want

IF you want have a monolithic kernel (I have also for security reasons) THEN just disable module support in your kernel and DONT do this:
https://wiki.gentoo.org/wiki/Kernel_Mod ... le-less.22

I am a total outsider,so I don't really understand what the word "monolithic kernel" means,I searched it via search engine,Linux kernel is a monolithic kernel,am I understanding correctly?Like the Hurd kernel is a micro kernel...

Why ?

Because you can always enable module support back (if you want to test if some modules will load). A monolithic kernel is a very nice piece ... AND you can enable LOCKDOWN in your kernel without doing this:
https://wiki.gentoo.org/wiki/Signed_ker ... le_support

Understood.

I have a monolithic, hardened, stub- (meaning: my UEFI boots directly my kernel without any other bootmanager like grub) kernel ... I can only recommend

Maybe you already know this article ... you dont need anymore because you have good kernel settings:
https://wiki.gentoo.org/wiki/User:Pieti ... figuration

Thank you brother,I need grub for now,I have to walk before I fly,so,maybe one day I can do what you can do now,I was learning how to install Arch linux January 2022,now I am using Gentoo
Oh yes,sorry for taking so long to reply,there was a family party last night(now is date in where I am)

[nurali]

if you dont have a special need for an initramfs (e.g. encrypted root partition) AND you do your kernel configuration yourself THEN you are doing all right

Kernel updated today,I changed few places as all you pointed,it's working fine,thank you
And there is another thing:
I got this error(maybe warning)

Code: Select all

[    2.041598] exfat: Unknown parameter 'subvol'
[    2.042363] fuseblk: Unknown parameter 'subvol'

and this too

Code: Select all

[    2.177246] systemd-gpt-auto-generator[352]: File system behind root file system is reported by btrfs to be backed by pseudo-device /dev/root, which is not a valid userspace accessible device node. Cannot determine correct backing block device.
[    2.181442] systemd[347]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator failed with exit status 1.

from dmesg
I am using BTRFS,am I missing something in kernel?
There are SUBVOL written in fstab,like this:

Code: Select all

# /dev/nvme0n1p3
UUID=7b448353-60de-4218-8368-2ec4f8de463d       /               btrfs           rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvolid=256,subvol=/@,subvol=@  0 0

# /dev/nvme0n1p1
UUID=5383-DB69          /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro        0 2

# /dev/nvme0n1p3
UUID=7b448353-60de-4218-8368-2ec4f8de463d       /home           btrfs           rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvolid=263,subvol=/@home,subvol=@home  0 0

# /dev/nvme0n1p3
UUID=7b448353-60de-4218-8368-2ec4f8de463d       /usr/local      btrfs           rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvolid=260,subvol=/@local,subvol=@local        0 0

# /dev/nvme0n1p3
UUID=7b448353-60de-4218-8368-2ec4f8de463d       /opt            btrfs           rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvolid=258,subvol=/@opt,subvol=@opt    0 0

# /dev/nvme0n1p3
UUID=7b448353-60de-4218-8368-2ec4f8de463d       /root           btrfs           rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvolid=257,subvol=/@root,subvol=@root  0 0

# /dev/nvme0n1p3
UUID=7b448353-60de-4218-8368-2ec4f8de463d       /.snapshots     btrfs           rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvolid=267,subvol=/@snapshots,subvol=@snapshots        0 0

# /dev/nvme0n1p3
UUID=7b448353-60de-4218-8368-2ec4f8de463d       /srv            btrfs           rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvolid=259,subvol=/@srv,subvol=@srv    0 0

# /dev/nvme0n1p3
UUID=7b448353-60de-4218-8368-2ec4f8de463d       /tmp            btrfs           rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvolid=262,subvol=/@tmp,subvol=@tmp    0 0

# /dev/nvme0n1p3
UUID=7b448353-60de-4218-8368-2ec4f8de463d       /var            btrfs           rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvolid=261,subvol=/@var,subvol=@var    0 0

# /dev/nvme0n1p2
UUID=9211f562-55cd-46ea-bec0-c77423166325       none            swap            defaults,pri=-2 0 0

Please check

[pietinger]

A monolithic linux kernel is when you disable module support and have all (what you need in kernel) static [*] enabled. This protects against rootkits which needs modules support (another way to protect you against these rootkits is: signing your kernel modules).

I am sorry I cannot help you with systemd and btrfs (I am a noob there) - but I am sure someone will jump in this thread

[nurali]

A monolithic linux kernel is when you disable module support and have all (what you need in kernel) static [*] enabled. This protects against rootkits which needs modules support (another way to protect you against these rootkits is: signing your kernel modules).

Understood

I am sorry I cannot help you with systemd and btrfs (I am a noob there) - but I am sure someone will jump in this thread

HAHA....Thank you

[NeddySeagoon]

nurali,

Response times don't matter. Gentoo is a hobby for all of us.
That means its fairly low down the list of lifestyle choices.

[nurali]

nurali,

Response times don't matter. Gentoo is a hobby for all of us.
That means its fairly low down the list of lifestyle choices.

The atmosphere is really nice here