I am trying to ask a question about getting my hardware to work but I don't know what information to add to my question to get help, what do I need to do?
The most important information you can give is what you've done, what you expected to happen, and what you observe has happened.
This question is a particularly fine example of a hardware-detection problem with a USB device.
Other examples of this could be:
After this general problem description, what other information is interesting depends on what sort of hardware you're having problems with, and what problems you're having.
For Video problems:
For Audio problems:
Wireless connectivity issues are fortunately becoming rarer with each Ubuntu release. However problems still occur.
The following information will help diagnose wireless connectivity issues in questions posted on Ask Ubuntu, you can open a terminal by hitting Ctrl-Alt-T and typing in one of these commands, then edit your question to add the information.
How the kernel recognises your network cards
Details of your USB wireless card
This can give a long list depending upon how many USB devices are connected. If in doubt, post the entire list.
Details of your PCI wireless card
This can give a long list depending upon how many PCI devices are fitted. If in doubt, post the entire list.
How to see if a wireless card is soft-blocked or hard-blocked:
Errors whilst connecting
Often you can see useful errors by looking at your kernel logs.
If you attempt to connect via network manager you can see what errors are produced by looking at
Suggested procedure - type
Another useful output is
Searching on Google will sometimes bring results suggesting using NDISWrapper. This is an old technique where obtaining a Windows XP driver can be made to work in Ubuntu.
Generally, this should be avoided in current versions of Ubuntu since the drivers in the kernel have less compatibility issues.
If you have any wireless issues post the results of the four command-line entries above into your question BEFORE trying NDISWrapper.
https://wiki.ubuntu.com/DebuggingProcedures is usually a good starting point if you want to know what information is useful for a bug report.
The following logs will contain details about hardware as it was seen by various system services (kernel, udev, etc) at boot time:
Execute these following commandline tool:
One of the most useful things you can do when describing a hardware issue, is describe what you did, what is connection you are using.
This kind of information may seem very simple, but it can help to pin point where common problems come from, or if you question may be off topic.
A general problem-solving hint
I've noticed that I often collect data to diagnose a problem by:
First, identifying the problem - what did I do, what did I expect to happen, and what seemed to happen? Can I repeat the problem?
Then, causing the problem to happen, and listing the system's logs in reverse order of modification time:
protected by Community♦ Jul 2 '12 at 17:27
This question is protected to prevent "thanks!", "me too!", or spam answers by new users. To answer it, you must have earned at least 10 reputation on this site.