Project

General

Profile

Actions

Bug #13498

closed

Newer variant models within the PC Engines APU2 platform are not recognized, causing garbled early serial console output

Added by Brett Keller about 2 years ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Hardware / Drivers
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
24.03
Release Notes:
Default
Affected Version:
2.6.0
Affected Architecture:
All

Description

The PC Engines APU2 hardware platform has a dedicated entry in system_identify_specific_platform() in system.inc, but the existing detection code only correctly identifies the original "apu2" variant. Newer variants have been released over the years that all still fall under the "APU2" platform, but their model/variant names are different.

If these newer hardware variants are not properly detected by pfSense, they appear in the Dashboard with the generic "pfSense" system name instead of "PC Engines APU2".

More importantly, there is special-casing in place that changes pfSense from using dual serial/video console output to serial-only console output for the APU2 platform hardware. This is necessary to fix an issue where the bootloader is rendered unusable because the console output is garbled when dual serial/video console output is enabled. Since the newer hardware is not being detected by system_identify_specific_platform(), the special-casing is not being applied, and it is difficult or impossible to interact with the bootloader on these devices.

I have physical access to one of these newer hardware variants at the moment, so I have written and tested a patch that I will submit shortly.

Actions

Also available in: Atom PDF