I'm asking this in relation to another question that was posted:    I posted an answer suggesting that built-in device drivers can't be blacklisted, as they are built-in to the kernel (and so by definition, are not loadable/un-loadable). The top answer to  on Ask Ubuntu seemed to back that up. However, Ignacio Vazquez-Abrams posted in the comments that he believes built-in modules can be blacklisted (although they can't be unloaded with modprobe).  Perhaps he's right and, seeing as this question doesn't seem to have been asked before, I think it would be good to clear this up. So, can built-in modules be blacklisted? If so, can anyone provide some insight into the details of how this works 'under the hood'? How is blacklisting different to using modprobe and why does one work and not the other?  Any links or references to back up either position would be appreciated too.
120482
I configured and compiled Linux kernel with nouveau driver built-into kernel, i.e. with &lt;*&gt; as opposed to &lt;M&gt; when doing make menuconfig inside Linux kernel source directory.   Now, I intend to use another driver rather than nouveau. If nouveau was a module, I would add a line like blacklist nouveau inside /etc/modprobe.d/blacklist.conf  What should I do now.
42371
This didn't start out as a problem with the login loop.  I was attempting a clean install of Ubuntu 16 and using the new feature that allows it to detect proprietary drivers for me.  I started off with   When I attempted to use the recommended Nvidia Drivers, it caused the laptop to become unstable and freeze.    I attempted the remedy from that post and it resulted in a login loop.  I have attempted   sudo mv ~/.config/dconf/user ~/.config/dconf/user.old   Tried   sudo mv ~/.Xauthority ~/.Xauthority.backup sudo service lightdm restart   I have tried locating and disabling secureboot, but there is no secureboot option in the bios.  This is an HP DV2000 series laptop.  Nothing is helping    Can someone help?  edit:  Guest session does the same loop.  /var/log/Xorg.0.log shows a lot of stuff, but I took a pic of what seems relevant   Thing is the driver I first tried that started this mess was 304 drivers and the 364 drivers were supposed to be the fix according to other posts.  More editing:  I purged the nvidia files and it came back to a blank desktop w/o the interfaces so I right clicked and restored a backup.. The sidebar came back and it was running gallium.  I restarted and its the blank purple screen again.  I am thinking of just reinstalling and not using nvidia drivers.  The software center is telling me I have a presario and i should use 304 drivers.  Its not a presario. =(  At least the software center provides a suggestion for the coprocessor driver which is nice.
64143
When installing 16.04, I was asked to turn off "Secure Boot" if I wanted to install 3rd party modules/drivers.  I did not comply.  And when I installed manually the only 3rd party drivers I use (bcmwl-kernel-source), I was asked again (during the installation of the package) to turn off "Secure Boot".  Using bcmwl-kernel-source was perfectly fine with Secure Boot in 15.10. This does not seem to be related to a bug to me.  So this does look like Ubuntu refuse to sign anymore the 3rd party drivers/modules to make it work (??) with "Secure Boot". Or seem to consider 3rd party modules as insecure and breaking "Secure Boot" hence inforcing to disable it to make it clear ?? Am I right ?
3457
During my attempt to upgrade my Xubuntu 14.04 installation with  sudo apt-get dist-upgrade   I made the mistake of interrupting the process by closing my laptop, which caused it to suspend to disk. After re-opening, the monitor remained black, so I was forced to reboot the system. I have since discovered many failures of drivers (wlan0 missing, USB memory stick cannot be mounted, USB mouse not recognised, and maybe more undiscovered problems with hardware).   My beginner's attempts to manually repair the single problems could have made it even worse. During the installation of the current distribution I chose to encrypt my whole hard disk.
101790
To start I should admit that I haven't done much work in Ubuntu in a few years.  I am wondering is if there is still a single, canonical source of the hardware supported by the newest distribution of Ubuntu.  In specific, I want to get a 17-inch HP dv7t Quad edition laptop.  But more generally, it is just bothering me how little luck I'm having finding an up-to-date support listing.
19483
There are those big green spiked things that my friends call viruses. I don't know what they do and I want to know. Do the viruses do something to the device you are playing on? Are they good or bad?
3827
As far as I know, the kernel detects hardware, adds information to sysfs creates a device in /dev and then generates a udev event. My question is, do device drivers do all of this or it is the kernel itself? If drivers do it, then they would know the device major and minor number to create the file in devtmps.   I also understand (maybe wrongly) that it is udev who calls modprobe to load the drivers that handle a device.   I was told that they do so with the contents of the MODALIAS uevent environment variable, thus loading all modules whose aliases match this string (the correct driver). In short: what are the steps of hardware detection in linux and WHO performs each step: the kernel itself, the driver inside the kernel or udev in userspace. Thanks.
5105
This is in continuation of my previous problem.   Here i have 2 usbserial hardware modules and it is provisionised that only one can be used at a time.   1. 0403:6014 2. 0403:6001   I also wanted to make sure device is R/W accesble to "plugdev" group  For device 0403:6014, I do not want to use inbuilt usbserial(ftdi_sio) driver. I want to access this device using FTD2XXX library. and for device  0403:6001, I want to use inbulit  usbserial(ftdi_sio) driver. I am trying to find a common way to acheive this.  Trails which I attempted so far. Since,  0403:6001 device uses inbuilt linux driver, I am trying to remove / blacklist ( 0403:6014 ) driver while loading    TRIAL 1  ACTION=="add", SUBSYSTEMS=="usb",  KERNEL=="ttyUSB*", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6014",  RUN+="/usr/local/bin/rmmod.sh 4", GROUP="plugdev"  This removes the loaded FTDI driver, but it does not change the device group from ROOT to PLUGDEV   So address that issue added one more rule line   TRIAL 2  SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0664", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6014", GROUP="plugdev" ACTION=="add", SUBSYSTEMS=="usb",  KERNEL=="ttyUSB*", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6014", RUN+="/usr/local/bin/rmmod.sh 4"  This trial sets my device GROUP as expected to "plugdev", but this does not remove the kernel usbserial module. TRIAL 3  SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0664", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6014", GROUP="plugdev"  Added ftdi_sio to  /etc/modprobe.d/blacklist.conf , but this blacklists my  0403:6001 completely.   This approach works well for 0403:6014 but this completely obseltes my 0403:6001 device   Request some guidance to fix this issue
86517
I'm trying to get a kernel module to load at boot.  If I run insmod /path/to/module.ko, it works fine. But this has to be repeated every time I reboot.  If I run modprobe /path/to/module.ko, it can't find the module. I know modprobe uses a configuration file, but I can't get it to load the module even after adding /path/to/module.ko to /etc/modules.  What is the proper configuration?
35636
Perhaps it's a silly question but I've recently purchased a new motherboard and of course it came with a CD with it's drivers only for Windows systems (you know, the Autorun cr@p and all that)  So, should I somehow try to obtain these drivers from the vendor for my Linux system or is that not necessary since the OS installation will take care of it by itself?
106561
I'm subscribed to the Ubuntu Security Notes, so everytime that I receive an e-mail, a new update is avalable.  But in the last update, they wrote something in the end that I coudn't undertand much, so can anyone please tell me what does that means?  ATTENTION: Due to an unavoidable ABI change the kernel updates have been given a new version number, which requires you to recompile and reinstall all third party kernel modules you might have installed. If you use linux-restricted-modules, you have to update that package as well to get modules which work with the new kernel version. Unless you manually uninstalled the standard kernel metapackages (e.g. linux-generic, linux-server, linux-powerpc), a standard system upgrade will automatically perform this as well.   I tried to ask to my friend (who also uses Linux), but he don't know much about kernel.
9040
I am buing assamble self PC for playing games.  I am wondering, all the drivers, which are most likely for Windows, can i just use them on Ubuntu?  So if i understand you right, it will automaticaly detect the drivers, no need for installs ? or it find custom drivers for ubuntu.  This is the setup, will there be any problem with it?
85830
I was reading about . How would this be done? The post talks about a 'looped mode' and comments suggest having a different controller to lie to the OS.  I went and bought one of these devices, tried it and it worked as advertized (overwriting data when it was full), although when I formatted it, it started showing its 'true' capacity.  How is this achieved?
54836
Under certain conditions, the Linux kernel may become tainted. For example, loading a proprietary video driver into the kernel taints the kernel. This condition may be visible in system logs, kernel error messages (oops and panics), and through tools such as lsmod, and remains until the system is rebooted.  What does this mean? Does it affect my ability to use the system, and how might it affect my support options?
50910
I need to know what hard disks are available, including ones that aren't mounted and possibly aren't formatted. I can't find them in dmesg or /var/log/messages (too much to scroll through). I'm hoping there's a way to use /dev or /proc to find out this information, but I don't know how. I am using Linux.
55682
I've installed Ubuntu 14.04 and I'm experiencing a fuzzy/blurry screen and bad support for multiple screens.  I realized that Ubuntu installs nouveau as default, but I need to install nvidia drivers, so I tried this:   sudo apt-add-repository ppa:ubuntu-x-swat/x-updates apt-get update apt-get install nvidia-current apt-get upgrade       Now that nvidia is installed, you need to blacklist the nouveau driver   so it don’t pop out when you will reboot. Create or edit the following   file:  nano /etc/modprobe.d/blacklist-nouveau.conf       …and add these lines at the end:  blacklist nouveau blacklist lbm-nouveau options nouveau modeset=0 alias nouveau off alias lbm-nouveau off    I checked via the software &amp; updates if nvidia driver got installed successfully, and it says the driver installed is nvidia 304.117  I then tried to run:  lshw -c video | grep 'configuration'   and the result is that the driver is still nouveau:  configuration: driver=nouveau latency=0   So how do I install and use the nvidia drivers?
91616
I came across this page which demonstrates that simply two lines need to be changed in order for Windows to detect the integrated gpu and use it:   Does the above work and if so is it possible to manually control whether the integrated or discrete gpu is in use? Also, would it automatically switch over from discrete to integrated and vis-a-versa when the load requirements change?