[SOLVED] list and view built-in kernel drivers

Hi,

I'm looking for a way to list and view built-in kernel drivers to see if my target driver is working.

I'm using an arm64 ubuntu rootfs I found somewhere which is not official of my hardware (zynqMP). It runs with the kernel I built, not perfectly I think.

I found that a lot threads suggest to list kernel drivers with somefile in /lib/modules/:

https://www.thegeekstuff.com/2010/11...mand-examples/

https://superuser.com/questions/5773...-the-linux-ker

http://ask.xmodulo.com/find-informat...les-linux.html

But, this does not work for me, as I don't have the $(uname -r) folder inside /lib/modules/

Those threads says that /lib/modules is maintained by linux, but seems not my case.

I want to see the built-in drivers and find my targeted one, and see if it is loaded with the kernel successfully, How should I do that if the /lib/modules/ method not working ?

Thanks in advance!

hm. I don't really understand what do you mean by built-in driver. Usually this means a driver which is built into the kernel, so you cannot (and need not) modprobe it.
What kind of OS is it? (arm64 ubuntu rootfs is not an OS - at least I don't know about it).

Built-in drivers are not in lib modules, they are built into the kernel image. You can list all options configured into the kernel with

grep '=y' /boot/config-$(uname -r)

Originally Posted by pan64 hm. I don't really understand what do you mean by built-in driver. Usually this means a driver which is built into the kernel, so you cannot (and need not) modprobe it. What kind of OS is it? (arm64 ubuntu rootfs is not an OS - at least I don't know about it).

Hi,

You are right, the kernel is built into the kernel, I cannot modprobe it. In fact the rootfs I use is an nvidia rootfs provided for their TX2, It's like an OS with out the linux kernel for embeded systems.

The link I get all suggest to look the built-in kernel in /lib/modules/$(uname -r)/modules.builtin.

But the $(uname -r) folder (which is typically named with the kernel version, for me it's 4.14.0-xilinx-v2018.3) does not exist for my case.

I also want to know where the folder come from, is it maintained by the kernel or the rootfs vendor ?

Originally Posted by smallpond Built-in drivers are not in lib modules, they are built into the kernel image. You can list all options configured into the kernel with grep '=y' /boot/config-$(uname -r)

Unfortunately, the file /boot/config-$(uname -r) does not exist for my case either. There is only one folder named fw in /boot/, I got nothing there.

probably you still have *.ko files. can you check it?

Originally Posted by pan64 probably you still have *.ko files. can you check it?

Hi,

Yes, I have also configured the driver as 'M', aka module as .ko file, in my previous builds. it remains stayed somewhere in the project.

I configured it to 'Y',aka statically built into kernel, in my current builds, which should decoupled the kernel from the .ko file.

I thinks the solution for my case might not be finding the .ko file. It seem involves how the rootfs and kernel work together.

I don't know much about it.

See if you have a /sys/modules/<driver> directory for your driver. Many kernel drivers use the /sys filesystem to provide info to userspace.

Originally Posted by smallpond See if you have a /sys/modules/<driver> directory for your driver. Many kernel drivers use the /sys filesystem to provide info to userspace.

Hi
I think, maybe the /lib/modules/$(uname -r) directory is just a normal directory maintained by the one who provides the root filesystem.

I can now get an official sample ubuntu rootfs from xilinx, seems it have that directory in the image even before boot up.

I think this means the directory /lib/modules/$(uname -r) is a predefined directory.