Check desktop and laptop hardware before installation

Synopsis #

A model name is not enough to establish whether a desktop or laptop is a good FreeBSD target. Manufacturers can ship the same model with different wireless adapters, graphics processors, audio codecs, and touchpads. Record the actual device identifiers, compare them with the hardware notes for the intended release, and test the behaviors that matter before changing a disk.

The FreeBSD installer provides a live command-line environment. It can establish whether the kernel attaches storage, network, USB, and audio devices without writing to disk. It does not include a complete graphical desktop or every package-based graphics driver, so a missing graphical session in the live environment is not evidence that the GPU is unsupported.

Define the required behaviors #

Write down the capabilities that would make the installation acceptable. A useful desktop or laptop preflight normally includes:

the internal storage controller and intended installation disk;
wired networking and the exact wireless chipset;
the integrated and discrete graphics processors, if both exist;
the internal audio device, microphone, and required HDMI or DisplayPort audio;
keyboard, touchpad, pointing devices, docking station, and required USB devices;
suspend, resume, lid, brightness, and battery reporting on a laptop;
external displays at the required resolution and refresh rate.

Support for one component does not imply that the complete machine will satisfy this list. In particular, graphics attachment, accelerated rendering, external displays, and suspend/resume are separate tests.

Check the release-specific sources #

Select a supported release first. Read its hardware notes and errata rather than relying on a report for another FreeBSD version:

Search by the vendor and device identifiers collected from the machine, not only by a marketing name. A listing in the hardware notes establishes the driver’s stated hardware coverage. It does not promise a particular Wi-Fi rate, power draw, display configuration, or suspend behavior.

Boot the live environment #

Download installation media for the selected release, verify its published checksum, and boot it. Select Live CD at the installer welcome screen. The live environment runs from installation media and is slower than an installed system, but it does not require a disk change.

Record the release and architecture:

$ freebsd-version -kru
$ uname -m

Inventory PCI and USB devices:

$ pciconf -lv
$ usbconfig list

Save the full output if possible. The lines containing vendor, device, and the numeric PCI identifiers are more useful in a support report than a shortened model description.

Check each subsystem #

List network interfaces and the wireless devices known to the 802.11 layer:

$ ifconfig -l
$ sysctl net.wlan.devices

No wireless device in the second command means that Wi-Fi is not ready yet. Determine whether the PCI or USB device attached to a driver before attempting network configuration. Continue with the laptop Wi-Fi and suspend preflight when a laptop depends on those capabilities.

Identify every display controller:

$ pciconf -lv | grep -B3 display

A hybrid-graphics laptop may report two controllers. Record both and determine which one drives the internal panel. Package-based DRM drivers are not necessarily present on installation media; use the graphics driver decision guide after identifying the hardware.

Inspect audio attachment without changing a default device:

$ dmesg | grep pcm
$ cat /dev/sndstat

Several pcm devices are normal when analog, HDMI, DisplayPort, and microphone paths are exposed separately. The audio diagnostic guide separates detection from device selection.

Inspect recent attachment messages and loaded modules:

$ dmesg
$ kldstat

Search the saved output for no driver attached, firmware errors, timeouts, and the device names identified earlier. Do not treat every warning as a failure; correlate it with a required behavior.

Reserve an installed-system test #

The live environment cannot establish a complete desktop result because graphics drivers, firmware packages, browsers, and desktop environments may need packages. Before replacing a working system, use one of these lower-risk tests:

Install FreeBSD on a spare internal disk or a separate test machine with the same components.
Install to external storage when the firmware and storage path support it reliably.
Keep another operating system and a verified backup until the FreeBSD installation passes the required-behavior list.

On the test installation, complete the graphics setup, choose Xorg or Wayland , and test audio, networking, suspend, resume, external displays, and required USB devices. Repeat suspend and resume more than once and test after disconnecting from AC power.

Record a decision, not an impression #

Classify every required behavior as working, working with a documented limitation, untested, or failing. Keep the FreeBSD release, package branch, firmware version, device identifiers, driver names, and relevant log lines with the result.

An untested item should not be converted into an assumption. For example, a detected wireless interface does not prove association with the intended access point, and a successful console boot does not prove accelerated graphics or reliable resume.