On Sat, May 12, 2012 at 08:25:04AM -0600, Aaron Toponce wrote: > If it's a problem with the module, contact the module maintainers. If it's a > problem with the kernel, unload the module, and contact the kernel > maintainers. I don't see the problem.
Please read up on tainted mode. You can't just unload the module. You'd have to ensure you had a clean boot without the module to have an untainted kernel. The class of problems this prevents you from diagnosing are the ones which might, or might not be caused by the module: bad memory accesses in module code might result in misbehaviour elsewhere which is tricky to pin down. Of course you might never have a problem, and many people are happy to run a local module just like this. Hundreds if not thousands of people run the nvidia binary module with the same caveats. It's still worth point out, so people can make their own choice. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120512160006.GB4377@debian
