> For the complete documentation index, see [llms.txt](https://wiki.libreelec.tv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.libreelec.tv/how-to/blacklist-kernel-module.md). # Blacklist Kernel Module In most Linux distros modules are blacklisted by creating `/etc/modprobe.d/blacklist.conf` which contains the name of the module. In LibreELEC `/etc` is inside the read-only `SYSTEM` file so we provide an alternate location `/storage/.config/modprobe.d` which is overlaid onto the normal `/etc` location during boot. ### Example To blacklist the `rc-pinnacle-pctv-hd` module. Login to your LibreELEC box using SSH and confirm the module is loaded: ``` lsmod ``` If the module is loaded, append the module name to `blacklist.conf`: ``` echo "blacklist rc-pinnacle-pctv-hd" >> /storage/.config/modprobe.d/blacklist.conf ``` Now reboot to effect the change. ### Module vs Driver This approach to blacklisting only works with modules that are compiled with `=m` to create an independent module; meaning they are loaded via modprobe. If the module has been compiled directly into the kernel with `=y` modprobe is not used and this method has no effect. Drivers that are compiled-in are normally controlled via kernel boot params. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wiki.libreelec.tv/how-to/blacklist-kernel-module.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.