Tag Info

New answers tagged


I may rephrase my question by asking what does Linux developers do to support hardware ? Do they rely on submitted issues ? Some of then, yes. Do hardware vendors like Dell, HP..etc, work with Linux developers to provide more compatible drivers ? Yes, the big players have Linux developers among their ranks. Intel for example has a very active ...


As for Fedora, both methods will work, there is no guarantee to chose which one is preferable. For Redhat/Centos, you should use /etc/sysconfig/modules, since when it's documented in Redhat documentation - Persistent Module Loading. Another way you can use /etc/modules.conf in Redhat/Centos base distro. If you use Debian base distro, use file /etc/modules ...


The columns in the output from /proc/modules are as follows. usb_storage 56610 0 - Live 0xffffffffa005d000 (F) (1) (2) (3) (4) (5) (6) (7) NOTE: I found no mention of what appears to be the 7th column, but I'm labeling it as such since the descriptions for the 6th column (see below) do not cover the information that's being ...


While you won't notice any performance improvement (assuming you build your kernel with the modules you actaully require), there is some benefit in removing unneeded modules: first, it can significantly reduce the compile time and secondly, it will reduce the size of the final kernel. Creating a .config with make localmodconfig is a good way to get your ...


The modules are loaded as needed: don't worry, as there's no slowdown.


Just run a simple command in your terminal window: $ sudo apt-get install virtualbox-guest-x11 After completion, reboot your virtual box.


Run sudo update-initramfs -u to get your module in the initial ramdisk for the current kernel. Otherwise it will not load on init.


Use an Upstart job for this: # Ensures that the device is up and filesystem is too start on filesystem and net-device-up IFACE=ib0 stop on runlevel [016] # Ensures that module is loaded pre-start exec modprobe -q knem exec /path/to/exec


I don't know specifically about an init.d file, but a udev rule for running a script upon device-add might look like: ACTION=="add", ATTRS{idVendor}=="VID", ATTRS{idProduct}=="PID", RUN+="/path/to/executable" You should do some digging in udevadm to learn more about the way the device is typically added and its modules loaded. You'll also find the correct ...

Top 50 recent answers are included