PCIe expansion card causes a blinking cursor before BIOS: how to troubleshoot POST freezes

Sun, 24 May 2026 00:46:52 +0800

If a PCIe expansion card is installed and the machine cannot even reach the BIOS screen, stopping at a black screen or blinking cursor before the motherboard finishes booting, this is usually not a Linux driver issue. It is an earlier hardware-level freeze.

At this stage, the operating system has not loaded yet, so Linux kernel parameters such as pci=nomsi and pcie_aspm=off cannot help. The problem happens during POST, the power-on self-test stage. Common failure points include PCIe link training, PCIe resource allocation, Option ROM loading, Legacy / UEFI compatibility conflicts, or a faulty expansion card.

In short: if you cannot even enter BIOS, do not start by changing Linux. First make the motherboard complete POST.

What this failure means

During a normal boot, the motherboard scans PCIe devices, assigns bus, I/O, MMIO, and other resources, and decides whether to load any Option ROM provided by the device. Some SATA expansion cards, HBAs, NICs, capture cards, or adapters include firmware for boot support or device initialization, and the motherboard firmware may try to read it.

If the expansion card, motherboard BIOS, PCIe slot, power, attached device, or Option ROM is incompatible, the system may freeze during motherboard self-test. Typical symptoms include:

Black screen with only a blinking cursor.
Stuck before or after the motherboard logo.
Del, F2, F11, or F12 cannot enter BIOS or the boot menu.
Everything works after removing the PCIe expansion card.
NVMe, GPU, NIC, or existing boot device works normally when the card is removed.

This means the motherboard has not had a chance to hand control to the operating system; the card has already blocked the boot process.

Which PCIe expansion cards commonly trigger this

This POST freeze does not only happen with JMB585 SATA cards. Any PCIe device that the motherboard needs to initialize, allocate resources for, or load Option ROM from can trigger similar problems.

Common examples include:

JMB585, ASM1166, and similar PCIe SATA expansion cards.
LSI / Broadcom HBA or RAID cards.
2.5G, 10G, copper, or fiber NICs.
PCIe to M.2 / U.2 / SATA adapters.
Video capture cards.
USB 3.x expansion cards.
Older GPUs, RAID cards, or server pull cards with Option ROM.
Cheap PCIe cards with poor build quality, modified firmware, or broken EEPROM.

The device may not be “dead.” It may simply be incompatible with the current motherboard BIOS, PCIe lane routing, PCIe speed, boot mode, or address resource allocation.

Why Linux kernel parameters do not work yet

Parameters such as pci=nomsi, pcie_aspm=off, and libata.force are Linux kernel boot parameters. They only take effect after the kernel has loaded.

A blinking cursor before BIOS, a freeze before the motherboard logo, or a keyboard that cannot enter BIOS means the system is still in POST. The code running is motherboard firmware, not the Linux kernel. Linux has not started yet, so it cannot read those parameters.

For this class of failure, do not start by editing /etc/default/grub. Focus first on:

BIOS / UEFI boot mode.
CSM / Legacy compatibility layer.
PCIe Option ROM.
PCIe link training.
PCIe address space and resource allocation.
Expansion card, slot, power, and attached devices.

Step 1: disconnect devices attached to the expansion card

Start with the lowest-risk test. Leave the PCIe expansion card installed, but disconnect SATA data cables, attached device cables, or disk power from whatever is connected to it. Let the card sit in the motherboard with no attached devices.

Then boot and test:

If the system can enter BIOS after disconnecting disks or devices, the expansion card itself probably did not hard-lock the motherboard. The problem may be one disk, cable, power path, or boot-device detection.
If it still freezes, the problem is more likely between the expansion card and the motherboard PCIe / BIOS compatibility.

Why can attached disks cause POST freezes? Common reasons include:

A disk has a damaged boot sector or partition table, and the BIOS misidentifies it as a boot device and hangs while reading it.
Multiple HDDs spin up at once and the power supply cannot handle the transient current.
A SATA cable has poor contact, causing controller initialization to time out.
A disk is in poor health and slows down initialization.

If it boots after disconnecting disks, reconnect them one by one to find the specific disk or cable that triggers the problem.

Step 2: remove the card and disable CSM in BIOS

Many PCIe expansion cards freeze during POST because of the CSM / Legacy boot compatibility layer.

CSM stands for Compatibility Support Module. It lets UEFI motherboards support old Legacy boot behavior. The problem is that some cheap SATA expansion cards or modified cards include old Option ROMs. When the motherboard runs in CSM mode, it may try to load those old boot firmwares, which can conflict with modern UEFI firmware.

Why CSM and Option ROM can freeze POST

During POST, the motherboard enumerates PCIe devices and checks whether they provide boot firmware. Older storage cards, RAID cards, HBAs, NICs, and SATA expansion cards may provide Option ROM so the motherboard can recognize the device before the operating system starts, or even boot from it.

The problem is that Option ROM depends heavily on BIOS implementation. Some expansion cards have outdated, modified, damaged, or server-specific Option ROMs. When a modern consumer motherboard tries to load them under CSM / Legacy mode, it may enter an initialization loop, black screen, blinking cursor, or keyboard lock.

Disabling CSM and Storage OpROM prevents the motherboard from executing the card’s own pre-boot firmware. If your system disk is not connected to that expansion card, most NAS and data-disk scenarios do not need to boot from it. Letting Linux or Windows recognize it after boot is usually more stable.

Steps:

Shut down and remove power, then remove the PCIe expansion card.
Boot with the original GPU, iGPU, or existing boot device and enter BIOS.
Find CSM, Compatibility Support Module, or Legacy Boot.
Set CSM to Disabled.
Use UEFI Only boot mode if possible.
Save BIOS settings and shut down.
Reinstall the PCIe expansion card and test again.

If disabling CSM lets the machine pass POST, the likely cause was Legacy Option ROM or boot compatibility conflict.

Step 3: disable PCIe / Storage Option ROM

Some BIOS menus provide more detailed Option ROM controls, such as:

PCIe Option ROM
Storage OpROM
Mass Storage Controller Option ROM
Launch Storage OpROM Policy
Option ROM Messages

If you find a similar option, set the expansion card slot or storage-controller Option ROM to:

`1`	`Disabled`

or:

`1`	`Do Not Launch`

This tells the motherboard not to load boot firmware from the card, and to leave it as an ordinary PCIe device for the operating system to detect later.

If the system disk is not attached to this expansion card and the card is only used for data disks, NAS disks, warehouse disks, NICs, or capture devices, you usually do not need to boot from it. Disabling its Option ROM is often safer.

Step 4: force PCIe speed to Gen2 or Gen1

Many cards advertise PCIe Gen3 links, but the motherboard, adapter, cabling, slot, or card build quality may not be good enough. PCIe link training may fail at Gen3 speed, leaving the motherboard waiting for device initialization.

What PCIe Gen3 link-training failure looks like

When a PCIe device is installed, the motherboard and device negotiate link width and speed, such as x1, x2, x4, and Gen1, Gen2, Gen3. This process is called Link Training.

If the device, slot, adapter, motherboard traces, or power is unstable, both sides may fail to negotiate at higher speeds. Common symptoms include:

Black screen or blinking cursor before BIOS after installing the card.
Motherboard logo hangs for a long time and keyboard input does not respond.
Sometimes it boots, sometimes it hard-freezes.
Forcing PCIe Gen2 makes it stable.
Moving to another slot makes it stable.
The card works in a chipset slot but not a CPU-connected slot, or the opposite.

This is not an operating-system disk-drop issue. The motherboard and device have not finished PCIe link initialization yet. Forcing Gen2 / Gen1 lowers signal rate and trades theoretical bandwidth for stable boot.

Steps:

Remove the PCIe expansion card.
Enter BIOS.
Find the speed setting for the target PCIe slot, such as PCIe Speed, PCIe Link Speed, or Max Link Speed.
Change Auto or Gen3 to Gen2.
If Gen2 is still unstable, try Gen1.
Save, shut down, reinstall the card, and test.

For SATA HDDs, Gen2 x1 or Gen2 x2 is often enough. When stability matters, do not insist on Gen3.

If BIOS does not provide a PCIe speed setting, only then consider physical down-training methods. Some users tape selected gold-finger pins to force a card into x1 mode and test whether the second PCIe lane or high-speed signal quality is the problem. This is risky and easy to do wrong, so it should not be the first choice. Prefer BIOS speed limiting.

Step 5: enable Above 4G Decoding

If the motherboard has NVMe, GPU, wireless card, HBA, capture card, or multiple PCIe devices, BIOS must assign address space and MMIO resources during POST. Older boards or conservative BIOS resource allocation may freeze because of insufficient resources or address conflicts.

Try enabling:

`1`	`Above 4G Decoding`

It is often under Advanced, PCIe Settings, PCI Subsystem Settings, Chipset, or similar menus.

This option allows PCIe devices to use address space above 4GB, helping reduce resource allocation problems in multi-device systems. Although it is often mentioned for GPU passthrough, mining cards, HBAs, and multi-PCIe setups, it is also worth trying for SATA expansion cards that freeze during POST.

Step 6: change PCIe slots

Do not test only one slot. Different PCIe slots may be wired differently:

The long slot near the CPU is often CPU-connected and intended for GPUs.
Some short slots or secondary long slots may come from the chipset PCH.
Some slots share lanes with NVMe, SATA, Wi-Fi, or other devices.

If the expansion card freezes in a CPU-connected slot, try a chipset slot or lower-bandwidth slot. If the PCH slot is unstable, try another slot.

Also check the motherboard manual for lane-sharing rules, such as “this PCIe slot is disabled when this M.2 slot is populated.”

Recommended fast troubleshooting path

If you want to restore boot quickly, try this order:

Disconnect all devices attached to the expansion card, such as SATA disks, U.2 disks, or external cables.
If it still freezes, remove the card and enter BIOS.
Disable CSM and switch to UEFI Only.
Disable Storage OpROM or related PCIe Option ROM.
Enable Above 4G Decoding.
Force the target PCIe slot to Gen2; if that fails, try Gen1.
Save, shut down, reinstall the PCIe expansion card, and test.
If it passes POST, reconnect disks or devices one by one.

This path prioritizes the two most common causes: Legacy / Option ROM conflicts and PCIe Gen3 link-training incompatibility.

How to tell whether the card is bad or the motherboard is incompatible

If all steps above still end with a blinking cursor, do two cross-checks:

Test the same expansion card in another computer.
Test a known-good similar PCIe expansion card in the current motherboard.

Use this logic:

The same card freezes multiple computers: the card likely has a hardware or firmware problem.
The card freezes only on this motherboard but works elsewhere: motherboard BIOS, slot wiring, PCIe speed, or resource allocation is more likely.
Other similar expansion cards work in this motherboard: the original card is more suspicious.
Other PCIe devices are also unstable in this motherboard: suspect the slot, power, BIOS settings, or PCIe lane sharing.

If this card freezes multiple computers while other cards work on the current board, possible causes include:

Damaged expansion-card EEPROM / Option ROM data.
Short circuit or power problem on the card.
Gold-finger, solder joint, crystal, or power-chip hardware issue.
Firmware incompatible with many motherboard BIOS implementations.

If it freezes only on one motherboard, suspect BIOS, slot lanes, PCIe speed, CSM, or resource allocation.

Do not treat OS parameters as BIOS-stage fixes

Again, if the machine has not entered Linux, kernel parameters such as pci=nomsi, pcie_aspm=off, and libata.force do not take effect.

They only handle problems after the operating system takes over the hardware, such as disk drops, interrupt errors, and PCIe ASPM wake failures under Linux. They cannot help with a blinking cursor before BIOS or a POST-stage freeze because they never get a chance to run.

For this class of failure, focus on:

BIOS settings.
PCIe link training.
Option ROM.
Slot and resource allocation.
Physical condition of the expansion card and attached devices.

Summary

When a PCIe expansion card causes a blinking cursor before BIOS, the system is stuck during POST. The most common fixes are:

Disconnect all attached devices to rule out disk or power triggers.
Disable CSM and use pure UEFI.
Disable Storage / PCIe Option ROM.
Lower PCIe speed from Auto / Gen3 to Gen2 or Gen1.
Enable Above 4G Decoding.
Try another PCIe slot.

If none of these works and the card also freezes other computers, strongly suspect hardware or firmware damage on the card itself. For NAS and storage servers, stability matters more than attractive specs. With POST-level freezes, first make the motherboard pass self-test reliably, then troubleshoot Linux kernel parameters and drivers.

Hardware Troubleshooting on KnightLi Blog