Skip to main content
added 305 characters in body
Source Link

I'm working on kernel 2.6.37, in which i have made some loadable module instead of static to optimize kernel,

My task is to load some module after some application running, I'm able to all modules after that a application but coming to wifiwhich i'm doing successfully, it is not

In any embedded system, at initialization of file system it is loading, modutils.sh is file run by rcSa script to modprobe loadblemodpobe the modules from designated file such as etc/modules. so i have removed module name to not load at start of filesystem which I have removedinitialization rather need to be loaded after application starts. more like runlevel priority changed from 35 to 99.

Now my wifi kernel module takes 1-2sec to load so i tried to remove wifi module name and it's dependencies but still wifi modules is loading at file system initialization. After adding some debug log in allupon checking the rcS script. I have came across S03udev file in which, udev script is running a udevadm trigger which is initializing wifiloading the module to loadrather it should be done by modprobe.

/sbin/udevadm trigger --subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole --subsystem-nomatch=misc --subsystem-nomatch=dcon --subsystem-nomatch=pci_bus --subsystem-nomatch=graphics --subsystem-nomatch=backlight --subsystem-nomatch=video4linux --subsystem-nomatch=platform

can anyone suggest how to avoid wifi module loading ?

I'm working on kernel 2.6.37, in which i have to load module after some application running, I'm able to all modules after that application but coming to wifi, it is not at initialization of file system it is loading, modutils.sh is file run by rcS script to modprobe loadble module at start of filesystem which I have removed but still wifi is loading. After adding some debug log in all rcS script. I have came across S03udev file in which udevadm trigger is initializing wifi module to load.

/sbin/udevadm trigger --subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole --subsystem-nomatch=misc --subsystem-nomatch=dcon --subsystem-nomatch=pci_bus --subsystem-nomatch=graphics --subsystem-nomatch=backlight --subsystem-nomatch=video4linux --subsystem-nomatch=platform

can anyone suggest how to avoid wifi module loading ?

I'm working on kernel 2.6.37, i have made some loadable module instead of static to optimize kernel,

My task is to load some module after running a application which i'm doing successfully,

In any embedded system, at initialization of system a script modpobe the modules from designated file such as etc/modules. so i have removed module name to not load at filesystem initialization rather need to be loaded after application starts. more like runlevel priority changed from 35 to 99.

Now my wifi kernel module takes 1-2sec to load so i tried to remove wifi module name and it's dependencies but wifi modules is loading at file system initialization. upon checking the rcS script, udev script is running a udevadm trigger which is loading the module rather it should be done by modprobe.

/sbin/udevadm trigger --subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole --subsystem-nomatch=misc --subsystem-nomatch=dcon --subsystem-nomatch=pci_bus --subsystem-nomatch=graphics --subsystem-nomatch=backlight --subsystem-nomatch=video4linux --subsystem-nomatch=platform

can anyone suggest how to avoid wifi module loading ?

fixed typos
Source Link
Archemar
  • 32.3k
  • 18
  • 75
  • 107

i'mI'm working on kernel 2.6.37, in which i have to load module after some application running, i'mI'm able to all modules after that application but coming to wifi, it is not at initialization of file system it is loading, modutils.sh is file run by rcS script to modprobe loadble module at start of filesystem which iI have removed but still wifi is loading. afterAfter adding some debug log in all rcS script. iI have came across S03udev file in which udevadm trigger is initializing wifi module to load.

/sbin/udevadm trigger --subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole --subsystem-nomatch=misc --subsystem-nomatch=dcon --subsystem-nomatch=pci_bus --subsystem-nomatch=graphics --subsystem-nomatch=backlight --subsystem-nomatch=video4linux --subsystem-nomatch=platform

/sbin/udevadm trigger --subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole --subsystem-nomatch=misc --subsystem-nomatch=dcon --subsystem-nomatch=pci_bus --subsystem-nomatch=graphics --subsystem-nomatch=backlight --subsystem-nomatch=video4linux --subsystem-nomatch=platform

can anyone suggest how to avoid wifi module loading.

thanks & regards,

GBiradar ?

i'm working on kernel 2.6.37, in which i have to load module after some application running, i'm able to all modules after that application but coming to wifi, it is not at initialization of file system it is loading, modutils.sh is file run by rcS script to modprobe loadble module at start of filesystem which i have removed but still wifi is loading. after adding some debug log in all rcS script. i have came across S03udev file in which udevadm trigger is initializing wifi module to load.

/sbin/udevadm trigger --subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole --subsystem-nomatch=misc --subsystem-nomatch=dcon --subsystem-nomatch=pci_bus --subsystem-nomatch=graphics --subsystem-nomatch=backlight --subsystem-nomatch=video4linux --subsystem-nomatch=platform

can anyone suggest how to avoid wifi module loading.

thanks & regards,

GBiradar

I'm working on kernel 2.6.37, in which i have to load module after some application running, I'm able to all modules after that application but coming to wifi, it is not at initialization of file system it is loading, modutils.sh is file run by rcS script to modprobe loadble module at start of filesystem which I have removed but still wifi is loading. After adding some debug log in all rcS script. I have came across S03udev file in which udevadm trigger is initializing wifi module to load.

/sbin/udevadm trigger --subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole --subsystem-nomatch=misc --subsystem-nomatch=dcon --subsystem-nomatch=pci_bus --subsystem-nomatch=graphics --subsystem-nomatch=backlight --subsystem-nomatch=video4linux --subsystem-nomatch=platform

can anyone suggest how to avoid wifi module loading ?

Source Link

how to stop wifi module triggering from udevadm trigger?

i'm working on kernel 2.6.37, in which i have to load module after some application running, i'm able to all modules after that application but coming to wifi, it is not at initialization of file system it is loading, modutils.sh is file run by rcS script to modprobe loadble module at start of filesystem which i have removed but still wifi is loading. after adding some debug log in all rcS script. i have came across S03udev file in which udevadm trigger is initializing wifi module to load.

/sbin/udevadm trigger --subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole --subsystem-nomatch=misc --subsystem-nomatch=dcon --subsystem-nomatch=pci_bus --subsystem-nomatch=graphics --subsystem-nomatch=backlight --subsystem-nomatch=video4linux --subsystem-nomatch=platform

can anyone suggest how to avoid wifi module loading.

thanks & regards,

GBiradar