Loading kernel modules confusion about repo HOT 7 CLOSED

ALSO: my drandma said she does not like this operating system. My dreams for year of linux desktop 2021 were ruined.

from repo.

And also does the kernel option of building in firmware into it ever work? I have tried to embed the blobs I need, it worked, but it always fails to find firmware at boot, even though I have it compiled in. It makes no sense. I tried embeding blobs for gpu, realtek chip, and intel wifi, but it never works, snd kernel prints error of unable to load firmaware even if names %100 match. Also, all the drives were compiled into the kernel, not as a module.

from repo.

What device manager do you use?
How did you compile modules and embed firmware?

Please provide more useful info and logs 👍

from repo.

What device manager do you use?

Well, depends on the machine. I may be using udevd or mdev or nothing at all and just hardcode all the /dev/event*, doesn't matter. You guys start the device manager as a service? I don't cause I don't really need services to be honest. Unless I am setting up a public vps, that I would log into once a month. My rigs mine crypto and miner can restart itself anyways. It's also kinda bloat, if I need device manager for hotplug I can run it myself 'udevd -d' when I need it. The device manager is only run once here https://github.com/kiss-community/init/blob/master/lib/init/rc.boot#L36 and then it exits at the bottom of that file. That's why if you load the modules in /etc/rc.conf settings like sound, work because the realtek driver is already loaded and one of those commands actually works right after:

        udevd -d
        udevadm trigger -c add -t subsystems
        udevadm trigger -c add -t devices
        udevadm settle

but if modules are loaded in /etc/rc.d/mod.boot instead, those udev commands above would be run without driver loaded yet.

How did you compile modules and embed firmware?

Eh, I did mention that when I embed firmware I compile everything into the kernel; not a module. But it never works, that's why it makes no sense, the kernel should be self contained without any need to check into filesystem, but it seems like it's not possible to do? Does anybody here run their kernel as one single standalone vmlinuz executable ?

Please provide more useful info and logs +1

Nothing really to show yet, I want to get some feedback from the rest of the users to see how they actually handle this problem, and what might be the best way to configure the system. As of right now everythings works fine for me, for example if I modprobe from the /etc/rc.d/mod.boot I can work around the sound being muted by running some amixer commands directly, but I know that I technically don't have to do that if the driver is loaded first and udevd does it's thing.

from repo.

I think your kernel .config would clearify the "embedding driver does not work".

from repo.

Building firmwares into the kernel works just fine; I do it for my microcde and used to do it for my webcam.

All firmware files should be specified on a space-separated list with paths relative to what is set for CONFIG_EXTRA_FIRMWARE_DIR. The relevant lines of my .config for example.

You might find a few pages of the kernel's documentation useful, but probably not exhaustive.

Here is a short-and-sweet StackExchange QA that also explains it a little bit.

My only question is, IF putting the relevant lines in /etc/rc.conf has the desired effect (but a undesireable and ultimately nonfatal sideeffect), what is the actual problem?

If you actually want to avoid the undesired sideeffect you could probably add a check of some kind.

from repo.

Alright, thanks for the input everyone. I'll close this issue for now because I am not sure when will I have time to reconfigure the kernel and mess around with these things again. But everything works anyway I am happy as is.

from repo.