-
Notifications
You must be signed in to change notification settings - Fork 90
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
xow.service does not alway launch properly at boot, LIBUSB_ERROR_ACCESS #153
Comments
Is there a way to get further logs than this? I used |
@StefanLobbenmeier Probably not. That error code is coming directly from |
I see, do you mean physically plugged in or „plugged in“ by the kernel~ Because it would be really nice if I could always leave the adapter plugged in. I am doing that at the moment. |
I noticed this issue too, I have to unplug and then plug the dongle to make it work |
@Hedronmx you have to plug out and plugin the dongle in addition to restarting the service? |
Nevermind!! I had some issues with usb hub bandwidth! Seems to be working fine just now |
Happening for me with latest source on Linux 5.11.7-arch1-1 x86_64. With dongle already inserted in PC, service fails to start at boot on a regular basis. Manually starting service after failure is always successful. Same log output as OP. I have tried the dongle on various USB buses and the issue still occurs. |
Your PR has resolved the issue for me. I performed 10 reboots and the Thanks so much for your PR and your advice! |
Is closing this issue the best decision? Until #156 gets merged, the error persists and I'd rather close this issue only if and when the PR gets merged. |
No it's not. It's better if the commit that fixes it has a "Closes" github tag. |
I encountered the `Mt76Exception: Failed to load firmware` error quite a few times. xow.service is stopped and needs a restart as stated in the Troubleshooting section of the README.md. To make my life easier i added a udev rule to do just that for me when i plugged the dongle back in after uplugging it. Should start/restart the xow.service if the service is not running or is in a `failed` state due to previous ABRT signal. I think it would be a simple change to the udev.rules to make that the default behaviour but maybe a manual restart is desired? Anyways, thanks a lot for your work! I'm quite happy with xow! Closes: medusalix#153 Signed-off-by: Kai Krakow <[email protected]>
Oh Sorry, will wait for the merge |
I am also experiencing the same error on kernel 5.11.16. #156 doesn't appear to fix this issue in my case although I only modified my current install with the udev and service file changes. EDIT: Looks like the patch does work. I forgot to run |
Today I had a different issue:
Is it related or should I open a new issue? |
I use the xow.service so that I do not have to worry about having to launch xow in the terminal everytime before I start a game.
Anyway, once or twice a week the xow service does not boot up. I checked the logs and I found this:
The text was updated successfully, but these errors were encountered: