(info) Problem Reporting Guidelines - Please Read Before Posting an Issue.

[morrownr]

When reporting problems, remember that the people that will attempt to help you do not know what Linux distro you are using and that can be very important to know. Painting a picture that includes the distro you are using and a brief description of the problem is important.

• If you are installing to a VM, see the note at the end.

Checklist regarding what to include in your report:

• The name and version of the Linux distro you are using.
• A brief description of the problem.
• Paste the screen output provided by the install-driver.sh script.
• The information obtained with the below command.

sudo lsusb; rfkill list all; dkms status; iw dev

Note: Historically, many reported problems have to do with installations in VM's. If you are installing to a VM, and you have a problem, the chances are extremely high that the problem is with the setup in the VM, not this driver. Please investigate the problem first with the maker of the VM. Our time is valuable. Please help us maintain this driver by directing VM problems to the VM makers. I have maintained this driver for a few years and I have yet to see a problem reported for a VM installation that turns out to be a problem with this driver.

Thank you and enjoy

@morrownr

[lafrenierejm]

@morrownr Now that we have a relevant issue template, what would you think about closing this?

[morrownr]

Now that we have a relevant issue template, what would you think about closing this?

Done. Now we can how well the template works. This driver is heavily used but it is very dependable for an out-of-kernel driver so it could take a while to see reports.

[lafrenierejm]

Hopefully the template reduces the amount of back-and-forth needed on future GitHub issues. And we can always iterate on the template as needed. 😀