Bug 210412 - UEFI boot and console problems on 2008 Mac Pro w/ 10.3-RELEASE
Summary: UEFI boot and console problems on 2008 Mac Pro w/ 10.3-RELEASE
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.3-RELEASE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: uefi
Depends on:
Blocks:
 
Reported: 2016-06-20 17:59 UTC by stephen
Modified: 2024-11-17 03:25 UTC (History)
3 users (show)

See Also:

Attachments
uga output (19.64 KB, image/jpeg)
2016-06-20 17:59 UTC, stephen 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description stephen 2016-06-20 17:59:44 UTC 
Created attachment 171619 [details]
uga output

First of all, I believe my problem is related to bug #202730.

I am trying to boot 10.3-RELEASE on a Mac Pro 2008. I boot the mac and hold down the ALT key to choose the memstick (flashed with FreeBSD-10.3-RELEASE-amd64-uefi-memstick.img).  I see the FreeBSD text boot loader and proceed to let the system boot in multi-user mode to get to the installer.

The problem I encounter is that once the kernel is loaded, the kernel console output is nonsense garbled data.  I believe the problem is due to potentially incorrect graphics settings?

Sorry I do not know all the correct terminology to describe what I'm seeing.

After reading bug #202730, I ran the `uga` command at the boot prompt.  See the attached image for the output.  Perhaps the errors can help diagnose the problem?
Comment 1 stephen 2016-06-20 18:04:12 UTC 
The graphics card in my systems is an ATI Radeon HD 2600 XT 256 MB.
Comment 2 maxj.cn 2021-09-21 17:20:57 UTC 
This issue happens to 10 and 11 also.
Comment 3 maxj.cn 2021-09-21 17:22:20 UTC 
(In reply to maxj.cn from comment #2)
I mean it happens to 11 and 12
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2024-11-17 03:25:45 UTC 
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of suppoprt.
Please re-open if it is still a problem on a supported version.