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

Add another compatible usb hub #406

Closed
Mr-Bossman opened this issue Mar 6, 2022 · 10 comments
Closed

Add another compatible usb hub #406

Mr-Bossman opened this issue Mar 6, 2022 · 10 comments

Comments

@Mr-Bossman
Copy link

P/N: juh377
product site: https://en.j5create.com/products/juh377
first port has its own power control(p4), then (2,3) are independent controlled by p2.
On the second 4 port controller (4,5) are controled by p1, and (6,7) are p3.

The 7th port has a sticker in-front which hides 2 screws to open the housing. On the board it seems to have over current protection and the pins for each ports power control are broken out to resistors.

The GL3523 QFN76 is the usb hub controller

@mvp mvp closed this as completed in 6f1c71d Mar 7, 2022
@mvp
Copy link
Owner

mvp commented Mar 7, 2022

Thanks for reporting, added to the list.

@Tbruno25
Copy link

This hub only removes the power for a brief time and does not maintain a non-powered state.

@mvp
Copy link
Owner

mvp commented Oct 21, 2022

@Tbruno25 , are you sure you are not hitting Linux kernel issue as described in FAQ?

@Tbruno25
Copy link

Great point. Although other hubs seem to function as expected I cannot be certain -- will revisit the faq to confirm and report back.

@Mr-Bossman
Copy link
Author

I can take a look in a couple of days if nessary.

@Tbruno25
Copy link

@mvp my fault -- should have paid closer attention to the faq! supplying the -r 1000 args seems to have fixed it for me 🤦

Interesting that this behavior only occurs with certain hubs...

@mvp
Copy link
Owner

mvp commented Oct 21, 2022

Thanks. This behavior should be linked not to the hub, but to device being connected - because Linux attaches different device drivers per each device type, and they may behave differently when they want to revive dead device.

Note that this issue is solved in Linux kernel 6.0 - uhubctl built from master has support for new Linux power off interface now.

@teamdoug
Copy link

Has anyone tested this when acting as a USB3 hub? Cutting power works when the hub is plugged into a USB2 port but not USB3 for me.

@Mr-Bossman
Copy link
Author

Will look into it. If I recall correctly I did test both

@Mr-Bossman
Copy link
Author

Mr-Bossman commented Apr 21, 2023

Has anyone tested this when acting as a USB3 hub? Cutting power works when the hub is plugged into a USB2 port but not USB3 for me.

This happens for me too. Not sure why it doesn't work on usb3 anymore. very odd that if you plug it in using a usb2 cable it works. @mvp any ideas.
I tried with -S and -e.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants