Bug#773732: marked as done (Success installing and booting Debian jessie on a Mac Pro

Bug#773732: marked as done (Success installing and booting Debian jessie on a Mac Pro - i386 and kfreebsd-amd64 architectures)

To: Holger Wansing <hwansing@mailbox.org>

Subject: Bug#773732: marked as done (Success installing and booting Debian jessie on a Mac Pro - i386 and kfreebsd-amd64 architectures)

From: "Debian Bug Tracking System" <owner@bugs.debian.org>

Date: Thu, 06 Aug 2020 07:51:26 +0000

Message-id: <[🔎] handler.773732.D773732.159670012030839.ackdone@bugs.debian.org>

Reply-to: 773732@bugs.debian.org

References: <[🔎] 20200806094807.1966cbbb91ce0f9e1b2dbf22@mailbox.org> <29DAA95D-622E-4EA3-920A-4CDC6100FD0E@its.caltech.edu>

Your message dated Thu, 6 Aug 2020 09:48:07 +0200 with message-id <[🔎] 20200806094807.1966cbbb91ce0f9e1b2dbf22@mailbox.org> and subject line Re: Mass-closing old installation-report bugs --- round 3 has caused the Debian Bug report #773732, regarding Success installing and booting Debian jessie on a Mac Pro - i386 and kfreebsd-amd64 architectures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 773732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773732 Debian Bug Tracking System Contact owner@bugs.debian.org with problems

--- Begin Message ---

To: submit@bugs.debian.org
Subject: Success installing and booting Debian jessie on a Mac Pro - i386 and kfreebsd-amd64 architectures
From: David Henderson <dgh@its.caltech.edu>
Date: Mon, 22 Dec 2014 10:25:11 -0800
Message-id: <29DAA95D-622E-4EA3-920A-4CDC6100FD0E@its.caltech.edu>

Package: installation-reports

Boot method: install from net using i386 and kfreebsd-amd64 netinst.iso; debian-jessie-DI-b2-kfreebsd-amd64-netinst.iso

Image version: i386: vmlinuz-3.16-2-686-pae, kfreebsd-amd64: kfreebsd-10.0-1-amd64.gz

Date: circa December 15, 2014

Machine: Mac Pro model 1,1, Apple EFI firmware, only one drive bay populated

Processor: Xeon amd64

Memory: 12 GB

Partitions: <df -Tl will do; the raw partition table is preferred>

GNU Parted 3.2

Using /dev/ada0

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) print

Model: ST3500418ASQ (scsi)

Disk /dev/ada0: 500GB

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Disk Flags:

Number Start End Size File system Name Flags

1 20.5kB 210MB 210MB fat32 EFI System Partition boot, esp

2 211MB 50.2GB 50.0GB ext2 commonext2 msftdata

3 50.2GB 100GB 50.0GB ext4 i386deb8xroot msftdata

4 100GB 110GB 10.0GB ext2 i386deb8xboot msftdata

5 110GB 116GB 6000MB linux-swap(v1) i386deb8xswap

6 116GB 116GB 99.6MB i386deb8xbios

7 116GB 166GB 50.0GB dkfrdeb8xroot

8 166GB 176GB 10.0GB ext2 dkfrdeb8xboot

9 176GB 182GB 6000MB ext2 dkfrdebswap

10 182GB 182GB 99.6MB dkfrdebbios bios_grub

11 182GB 236GB 53.6GB hfs+ darwin1

12 236GB 290GB 53.7GB hfs+ Apple_HFS_Untitled_3

13 290GB 343GB 53.7GB freebsd-ufs fbsd101root

14 343GB 350GB 6442MB fbsd101swap

15 350GB 354GB 4295MB fat32 DOS_FAT_32_Untitled_2 msftdata

Notes:

Partition 1 created by MacOS Disk Utility during initial format

Partition 2-6 created during Debian i386 install

Partition 7-10 created during Debian kfreebsd-amd64 install

Partition 11-12 created by MacOS to check Debian i386 mount of hfs+ (nonjournaled)

Partition 13-14 created by FreeBSD 10.1 install

Partition 15 created by MacOS to check Debian kfreebsd-amd64 mount of fat32

Further note: Linux parted could have created the EFI partition. MacOS was easier.

Output of lspci -knn (or lspci -nn):

00:00.0 Host bridge: Intel Corporation 5000X Chipset Memory Controller Hub (rev 30)

00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev 30)

00:03.0 Non-VGA unclassified device: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev 30)

00:04.0 PCI bridge: Intel Corporation 5000X Chipset PCI Express x16 Port 4-7 (rev 30)

00:05.0 Non-VGA unclassified device: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev 30)

00:06.0 Non-VGA unclassified device: Intel Corporation 5000 Series Chipset PCI Express x4 Port 6 (rev 30)

00:07.0 Non-VGA unclassified device: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev 30)

00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev 30)

00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 30)

00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 30)

00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 30)

00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 30)

00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 30)

00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 30)

00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 30)

00:1b.0 Audio device: Intel Corporation 631xESB/632xESB High Definition Audio Controller (rev 09)

00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)

00:1c.1 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 2 (rev 09)

00:1c.2 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 3 (rev 09)

00:1c.3 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 4 (rev 09)

00:1d.0 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)

00:1d.1 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)

00:1d.2 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)

00:1d.3 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09)

00:1d.7 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)

00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)

00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09)

00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller (rev 09)

00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)

01:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)

01:00.1 PIC: Intel Corporation 6311ESB/6321ESB I/OxAPIC Interrupt Controller (rev 01)

01:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)

02:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)

02:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01)

02:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01)

05:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)

05:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)

08:00.0 VGA compatible controller: NVIDIA Corporation G73 [GeForce 7300 GT] (rev a1)

0f:00.0 Network controller: Broadcom Corporation BCM4321 802.11a/b/g/n (rev 01)

10:0b.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 01)

Base System Installation Checklist:

[O] = OK, [E] = Error (please elaborate below), [O] = didn't try it

Initial boot: [O]

Detect network card: [E]

Configure network: [O]

Detect CD: [O]

Load installer modules: [O]

Detect hard drives: [O]

Partition hard drives: [O]

Install base system: [O]

Clock/timezone setup: [O]

User/password setup: [O]

Install tasks: [O]

Install boot loader: [O]

Overall install: [O]

Comments/Problems:

Both i386 and kfreebsd-amd64 installs were straightforward, both systems run well. Both systems play nicely with MacOS on the same drive.

Thankyou thankyou thankyou, for the grub2 changes that eliminate any need for rEFIt or any other helper program. Somebody did some great work to make this happen.

The two installed Debian architectures are i386 and kfreebsd-amd64. Debian jessie makes a biosgrub partition that shows up on the Mac Pro option-poweron (or option-reboot) sequence that actually starts up grub2 which then selects a system and boots either the i386 or kfreebsd-amd64 systems. I manually modified the installed kfreebsd-amd64 grub2 menu using the i386 /boot/grub/grub.cfg file to supply the parameters.

The i386 installer recognized the Intel Corporation 80003ES2LAN ethernet controller; the kfreebsd-amd64 did not recognize the controller but used it anyway with no apparent ill effects. As this is an installation report not a bug report, I'll generating a separate bug report for this unrecognized card.

I have been running Debian jessie i386 and kfreebsd-amd64 for a about a week, installing from their respective netinst CD's. I started by removing all working drives from the 4 bays, and inserting one for the installs. This one drive was formmated by booting MacOS from an external drive, then formatting it with MacOS Disk Utility. This leaves the single drive with only the EFI partition and a HFS+ partition named "Untitled".

The i386 system was installed first. I deleted the "Untitled" partition, created some ext4/ext2 partitions for commonext2, root/boot, added swap and biosgrub, and Debian i386 just installed cleanly. It booted cleanly, without needing any MacOS or rEFIt. Its /boot partition is specifically separate and is ext2 format to be readily accessible to and updatable by the kfreebsd-amd64 system.

I then installed kfreebsd-amd64. The installer wanted to reuse swap and biosgrub between the two architectures; I took great pains to make sure the kfreebsd-amd64 swap and biosgrub partitions were distinct from the i386 install. It also has a separate /boot partition that is also ext2 to make it readable/writable by any other Debian system that needs it. Now the kfreebsd-amd64 system is the default system, and i386 system has to be selected from a modified grub2 menu. See Appendix 1 for the final partition layout

See above for the final partition layout. There are some partitions not related to the installation process that are identified in the notes.

--- End Message ---

Reply to: