Linux Hardware Acceptance Checklist Before Removing Windows

A live Linux USB should not be treated only as a demo.

Before removing Windows, use it as a hardware acceptance test.

The question is not "Does Linux boot?"

The question is "Does this computer perform the specific hardware and workflow tasks the owner needs?"

Networking: pass or fail

Test:

• Wi-Fi;
• Ethernet if available;
• reconnection after sleep;
• access to the local network;
• stable browsing for more than a few minutes.

A machine that sees the Wi-Fi network once but repeatedly drops it has not passed.

Audio: test both directions

Play audio through the expected speakers or headphones.

Then test microphone input.

If the machine is used for meetings, test the actual conferencing workflow rather than only the system sound panel.

Graphics and displays

Check:

• native screen resolution;
• brightness controls;
• external monitor output;
• expected refresh rate;
• multi-monitor arrangement if used.

A laptop that boots at a usable resolution may still fail the owner's dock or external display workflow.

Keyboard, touchpad and special keys

Test ordinary typing and pointer behavior.

On laptops also check:

• touchpad gestures that matter;
• function keys;
• keyboard backlight;
• media keys;
• lid behavior.

Small hardware failures become large annoyances after a migration.

Bluetooth

Pair at least one device of the type actually used.

That might be:

• mouse;
• keyboard;
• headphones;
• game controller.

Seeing a Bluetooth icon is not the same as a successful pairing and reconnect.

Camera and microphone

Open an application that can use the webcam and microphone.

For remote-work machines, this is a required test, not a bonus.

Suspend and resume

Put the computer to sleep.

Wake it again.

Then verify:

• Wi-Fi returned;
• audio still works;
• external displays return;
• the system does not freeze.

Suspend failures are easy to miss during a five-minute live-USB tour.

Printers and scanners

Where the migration depends on a local printer or scanner, test the exact device.

Printing and scanning should be evaluated independently.

For specialized peripherals, check the exact model against OpenPrinting, SANE or vendor information in addition to the live test.

Removable and external storage

Connect the USB drives, SD cards or external disks the user actually uses.

Confirm they mount and that required files can be read.

Do not test write operations on irreplaceable media without a backup.

Test the real workflow

Finally, do one normal session.

Open the browser.

Sign into the required web apps.

Open representative documents.

Use the external monitor.

Join a test call.

Print or scan if needed.

The point is to uncover blockers while Windows still exists.

Know the limitation of a live session

A live environment is strong evidence, not perfect proof.

Some proprietary drivers may be installed only after a full installation.

Performance from USB can also be slower than an installed system.

And one Linux distribution's behavior does not guarantee another's.

Define acceptance before you test

A migration should have an explicit pass/fail list.

If Wi-Fi, audio and the browser work but the owner's essential scanner does not, the machine has not passed that owner's migration test.

That is the value of treating the live session as acceptance testing rather than a tour.

You discover the bad news while the old operating system is still intact.