Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quick workaround fix for issue when USB modules are not loaded automaticall #65

Conversation

Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
@maxsteciuk
Copy link
Contributor

@maxsteciuk maxsteciuk commented Jan 30, 2019

Please see the following ticket for more details: #63

@q5sys
Copy link
Member

@q5sys q5sys commented Jan 30, 2019

how many varied systems have you tested this on?

@q5sys
Copy link
Member

@q5sys q5sys commented Jan 30, 2019

Obviously we don't want to commit anything that fixes one systems problem, but breaks 5 other systems.

@maxsteciuk
Copy link
Contributor Author

@maxsteciuk maxsteciuk commented Jan 30, 2019

Yup I totally understand

Trident and legacy TrueOS desktop

TrueOS desktop had FreeBSD 12-CURRENT early March build and does not have this issue because the legacy /etc/devd/usb.conf is used there
Trident with later FreeBSD build where /etc/devd/usb.conf was replaced does have an issue where modules are not loaded automatically and devmatch does not pick them up.

But this loader.conf.local file is local to Trident as per this comment? What other variations should we account for?

This file is installed by Project Trident
Changes to this file will be lost during updates

Also here is what happens if USB device is selected as default and sysctl complains on startup:

 * Configuring kernel parameters ...
sysctl: hw.snd.default_unit=7: Invalid argument

So that is why I put "FIXME" comment to remove those when devmatch is confirmed to be working with USB devices (so far it is still being investigated as per reference bug issue)

@q5sys
Copy link
Member

@q5sys q5sys commented Jan 30, 2019

i see you've got the ticket upstream with FreeBSD, we'll probably want to hold off and see what their thoughts are on it, as they're way more knowledgeable about how that works than we are. And since we havent gotten reports of this from a bunch of other people; it seems isolated at this point.

@maxsteciuk
Copy link
Contributor Author

@maxsteciuk maxsteciuk commented Jan 30, 2019

In any case I decided to publish this for at least informational purpose so that whoever has issues with USB audio, WiFi dongles or serial adapters can use it as a hint

@q5sys
Copy link
Member

@q5sys q5sys commented Jan 30, 2019

👍 Yea this definitely needs to be documented so if anyone else runs into it, they can get the fix. I'd love to ship this, but we want to make sure that this is the actual problem and that your fix isn't masking the real issue which ultimately needs to be resolved.

@beanpole135
Copy link
Member

@beanpole135 beanpole135 commented Jun 4, 2019

Closing stale PR.
Appears to be getting worked on by upstream FreeBSD: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235257

@beanpole135 beanpole135 closed this Jun 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment