Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

2013 Mac Pro (6,1) AKA "Trashcan Mac"

Ask for help with issues regarding the Installations of the Debian O/S.
Post Reply
Message
Author
User avatar
bmc5311
Posts: 546
Joined: 2008-11-16 15:21
Location: lost in the vast machine

2013 Mac Pro (6,1) AKA "Trashcan Mac"

#1 Post by bmc5311 »

Has anyone successfully installed debian on a 2013 Mac Pro (6,1) AKA "Trashcan Mac"? As with all things Apple, this machine is nearing the end of software support, I'd like to load debian on it, but I haven't been able to find any real documentation as to installation issues. If anyone can point me to some, that'd be great. As an FYI - this would not be a dual boot, it'd be debian only.

chatGPT says this:
"Debian should run fairly well on a 2013 Mac Pro (6,1), as it is a compatible hardware platform for Debian. However, the level of performance you will get depends on the specific hardware configuration of your Mac Pro, as well as the software applications you plan to run.

That being said, Debian is known for its stability, security, and flexibility, and it can be a great choice for those who prioritize those features over flashy graphics or cutting-edge performance. Additionally, Debian has a large and active community of developers and users, so you can expect to find plenty of resources and support if you encounter any issues.

In summary, if you are looking for a stable and secure operating system for your 2013 Mac Pro, Debian is definitely worth considering."

I'm a little leary of UEFI installs, I have a dell optiplex 3040 that refuses to boot debian, so it makes me cautious regarding the Mac Pro.

Any and all insight appreciated.

User avatar
dashek
Posts: 48
Joined: 2022-12-03 20:59
Has thanked: 7 times
Been thanked: 5 times

Re: 2013 Mac Pro (6,1) AKA "Trashcan Mac"

#2 Post by dashek »

Hello!

You can just try booting Debian live from usb stick, right? This quick experiment will tell you, if the kernel is going to boot at all.

User avatar
bmc5311
Posts: 546
Joined: 2008-11-16 15:21
Location: lost in the vast machine

Re: 2013 Mac Pro (6,1) AKA "Trashcan Mac"

#3 Post by bmc5311 »

Thank you dashek, yes, I know it will boot. :)
Basically just asking to see if anyone has or is running debian on this particular model.

User avatar
Hallvor
Global Moderator
Global Moderator
Posts: 2046
Joined: 2009-04-16 18:35
Location: Kristiansand, Norway
Has thanked: 152 times
Been thanked: 213 times

Re: 2013 Mac Pro (6,1) AKA "Trashcan Mac"

#4 Post by Hallvor »

Check if there is a report on linux-hardware.org
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD

User avatar
bmc5311
Posts: 546
Joined: 2008-11-16 15:21
Location: lost in the vast machine

Re: 2013 Mac Pro (6,1) AKA "Trashcan Mac"

#5 Post by bmc5311 »

Thanks Hallvor - excellent suggestion, found a report for Bullseye, looks promising; MacPro 6,1 / Debian 11

User avatar
Hallvor
Global Moderator
Global Moderator
Posts: 2046
Joined: 2009-04-16 18:35
Location: Kristiansand, Norway
Has thanked: 152 times
Been thanked: 213 times

Re: 2013 Mac Pro (6,1) AKA "Trashcan Mac"

#6 Post by Hallvor »

You are welcome. It should be fine.
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD

User avatar
bmc5311
Posts: 546
Joined: 2008-11-16 15:21
Location: lost in the vast machine

Re: 2013 Mac Pro (6,1) AKA "Trashcan Mac"

#7 Post by bmc5311 »

Update -
Finally got around to installing Debian 12 (stable) on the Mac Pro, routine install with the exception of getting it to recognize my OWC Thunderbolt 2 Thunderbay drive enclosure, the solution was to authorize the device using boltctl (man boltctl).

Post Reply