From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Race condition between bcm5974 and usbmouse kernel modules
Date: Fri, 05 Feb 2021 04:07:23 +0100 [thread overview]
Message-ID: <20210205030723.O_g0kwaUbo9dObTczz_EDFtr5wrX1BMqgqM_7UTmbzE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27465@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/27465#issuecomment-773753294
Comment:
I have a MacBook and the usbmouse/bcm5974 conflict is non-obvious. It took a bit of digging to figure out why my trackpad was misbehaving (I can't remember now if it was totally dead or had limited range of motion). It also requires a new initramfs because, if you forget to do that, your initramfs tends to load usbmouse before your Void installation can blacklist it.
Nevertheless, I agree with @fosslinux that we shouldn't be arbitrarily disabling features just because one class of users runs into some non-obvious behavior. The kernel docs recommend not saying Y because compiling it in-kernel probably makes it a lot harder to preempt. That is not the case for modules, which can be trivially blocked from loading.
The best way to address this problem might be a page on docs.voidlinux.org.
next prev parent reply other threads:[~2021-02-05 3:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 1:07 [ISSUE] " ryanm00
2020-12-31 1:32 ` fosslinux
2020-12-31 1:33 ` fosslinux
2021-02-05 3:07 ` ahesford [this message]
2021-02-05 3:14 ` ericonr
2021-02-05 3:43 ` ahesford
2021-02-08 3:30 ` ryanm0
2021-02-08 3:34 ` ryanm0
2021-02-08 3:35 ` ryanm0
2022-05-01 2:14 ` github-actions
2022-05-16 2:07 ` [ISSUE] [CLOSED] " github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210205030723.O_g0kwaUbo9dObTczz_EDFtr5wrX1BMqgqM_7UTmbzE@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).