USB Mouse

madjid277

Lenovo ThinkPad X270 GhostBSD latest version as of the time of writing this post.
USB Mouse it has an on/off switch at it's bottom, my issue is after not using it while the laptop is on for several minutes it goes off even though the switch is still on, making me switch it off then on again every time.
also, after I shut the laptop down at night to sleep leaving the USB attached when I boot it again the next morning I have to detach it then attach it again and also do what I said before to the switch, for it to stat working again.
looking for a solution/fix to this problem.

vimanuelt

madjid277
Are you using a USB hub? If the hub isn't providing enough power to the connected devices, it could cause this issue. If you're plugged directly into an onboard port and still experiencing the problem, it might be a bug in the controller software. In that case, it would need to be addressed by the upstream FreeBSD developers, as GhostBSD developers do not manage driver development.

madjid277

It's plugged directly into an onboard port.
I coincidentally found a partial solution, to reactivate it again after both of the pauses as mentioned above (post) all I have to do is, click in one or both of the left/right buttons.
How to do that? addressed by the upstream FreeBSD developers?
Lastly thank you for your reply vimanuelt.

vimanuelt

madjid277
FreeBSD has a formal bug reporting system, and the developers generally expect problems to be reported there so they can track, assign, and fix them.

Here’s the process:

1. Search first
Before filing a report, check if the issue is already known.

Bugzilla Search: https://bugs.freebsd.org/bugzilla/query.cgi
Mailing list archives: https://lists.freebsd.org/archives/
Release errata: https://www.freebsd.org/releases/

2. Use the official bug tracker (Bugzilla)
FreeBSD uses Bugzilla for problem reports.
You’ll need a FreeBSD account to submit one:

3. Write a clear and complete report
Include:

Summary — concise title of the problem.
Component — base system, kernel, ports, docs, etc.
Version — uname -a output.
Environment — hardware, architecture, drivers, boot mode.
Description — what you expected vs. what happened.
Steps to reproduce — exact commands or sequence.
Logs / outputs — dmesg, crash dumps, relevant config files.

4. Choose the right audience
If it’s not a bug but a request for help or discussion:

FreeBSD Forums: https://forums.freebsd.org/
Mailing lists: freebsd-questions@freebsd.org (general help)
Developer lists for technical topics, e.g. freebsd-current@

5. Follow up
Developers may request additional info or patches.
If the problem is solved, close the report with a resolution.

madjid277

Thanks.