Your message dated Sat, 31 Aug 2013 12:52:55 +0200 with message-id <201308311253.30231.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #692731, regarding Debian wheezy CD1 beta3 installation on Mac Pro Retina 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.) -- 692731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692731 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Debian wheezy CD1 beta3 installation on Mac Pro Retina
- From: Andrew Worsley <amworsley@gmail.com>
- Date: Thu, 8 Nov 2012 22:08:13 +1100
- Message-id: <CA+Y=x3mU--YzD2w6FzoftTzz_+QrwL47+Y7Om6vQhNWiqnnAhw@mail.gmail.com>
Package: installation-reports Boot method: CD in an external CD drive Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta3/amd64/jigdo-cd/ - CD1 used jigdo to build it Date: 8th Nov 2012 Machine: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS MBP101.88Z.00EE.B00.1205101839 05/10/2012 Processor: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz stepping 09 Memory: 16Gb Partitions: df -T Filesystem Type Size Used Avail Use% Mounted on rootfs rootfs 118G 98G 15G 88% / udev devtmpfs 10M 0 10M 0% /dev tmpfs tmpfs 1.6G 452K 1.6G 1% /run /dev/disk/by-uuid/9ad44c06-106c-40c8-b1fa-ff72043d760b ext4 118G 98G 15G 88% / tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 7.9G 0 7.9G 0% /run/shm tmpfs tmpfs 7.9G 2.9M 7.9G 1% /tmp sudo parted /dev/sda print Model: ATA APPLE SSD SM256E (scsi) Disk /dev/sda: 251GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Flags 1 20.5kB 210MB 210MB fat32 EFI system partition boot 2 210MB 99.2GB 99.0GB hfs+ Customer 3 100GB 101GB 650MB hfs+ Recovery HD 4 101GB 112GB 10.7GB ext4 5 112GB 123GB 11.6GB ext4 6 123GB 251GB 128GB ext4 Output of lspci -knn (or lspci -nn): lspci -knn 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09) Subsystem: Apple Inc. Device [106b:00f7] 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09) Kernel driver in use: pcieport 00:01.1 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0155] (rev 09) Kernel driver in use: pcieport 00:01.2 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0159] (rev 09) Kernel driver in use: pcieport 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) Subsystem: Intel Corporation Device [8086:7270] Kernel driver in use: xhci_hcd 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: Intel Corporation Device [8086:7270] 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) Subsystem: Intel Corporation Device [8086:7270] Kernel driver in use: ehci_hcd 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04) Subsystem: Intel Corporation Device [8086:7270] Kernel driver in use: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4) Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4) Kernel driver in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) Subsystem: Intel Corporation Device [8086:7270] Kernel driver in use: ehci_hcd 00:1f.0 ISA bridge [0601]: Intel Corporation HM77 Express Chipset LPC Controller [8086:1e57] (rev 04) Subsystem: Intel Corporation Device [8086:7270] Kernel driver in use: lpc_ich 00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04) Subsystem: Intel Corporation Device [8086:7270] Kernel driver in use: ahci 00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04) Subsystem: Intel Corporation Device [8086:7270] 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:0fd5] (rev a1) Subsystem: Apple Inc. Device [106b:00f2] 01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:0e1b] (rev a1) Subsystem: Apple Inc. Device [106b:00f2] Kernel driver in use: snd_hda_intel 03:00.0 Ethernet controller [0200]: Broadcom Corporation Device [14e4:16a3] (rev 10) Subsystem: Broadcom Corporation Device [14e4:16b4] 03:00.1 SD Host controller [0805]: Broadcom Corporation NetXtreme BCM57765 Memory Card Reader [14e4:16bc] (rev 10) Subsystem: Broadcom Corporation Device [14e4:96bc] Kernel driver in use: sdhci-pci 04:00.0 Network controller [0280]: Broadcom Corporation BCM4331 802.11a/b/g/n [14e4:4331] (rev 02) Subsystem: Apple Inc. Device [106b:00ef] Kernel driver in use: bcma-pci-bridge Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card: [ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system: [ ] Clock/timezone setup: [ ] User/password setup: [ ] Install tasks: [ ] Install boot loader: [ ] Overall install: [ ] Comments/Problems: Carefully let the external CD power up and and once it is spinning reboot the MAC at the EFI level. I had refind (see http://www.rodsbooks.com/refind/) as the boot loader which will boot Linux via BIOS mode (I can't get the EFI kernel to boot - it just hangs after complaining) Use Expert Mode and edit the boot options by pressing <Tab> when selecting the installation other wise it will hang on attempting the install. Add these options: acpi=none nomodeset nointremap It doesn't appear to recognise the wired Ethernet via the Thunderbold adaptor and the in built wireless card requires proprietary firmware I was able to check this in both BIOS mode booting and the EFI booting off the CD! That is all I was able to test so far. I thought I better send you this - I won't be able to test it more until this week end. If you can let me know if you are interested in hearing more. Andrew
--- End Message ---
--- Begin Message ---
- To: 695669-done@bugs.debian.org, 695476-done@bugs.debian.org, 695180-done@bugs.debian.org, 695058-done@bugs.debian.org, 695008-done@bugs.debian.org, 694934-done@bugs.debian.org, 694803-done@bugs.debian.org, 694788-done@bugs.debian.org, 694777-done@bugs.debian.org, 694771-done@bugs.debian.org, 694722-done@bugs.debian.org, 694247-done@bugs.debian.org, 694062-done@bugs.debian.org, 693891-done@bugs.debian.org, 693756-done@bugs.debian.org, 693756-done@bugs.debian.org, 692731-done@bugs.debian.org, 692475-done@bugs.debian.org, 692437-done@bugs.debian.org, 689849-done@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Sat, 31 Aug 2013 12:52:55 +0200
- Message-id: <201308311253.30231.holger@layer-acht.org>
Hi, thank you for submitting installation reports, much appreciated. I read through all the bugs mentioned here (and I'm sure they were read by several people at the time they were submitted) and am closing them now as/if - they (finally) indicated success and/or - I know from first hand experience that the functionality is working in Wheezy and/or - they only contained very little information and/or - they contained user errors and/or - they were caused by broken hardware and/or - they have been from a development phase where things were not stable and/or - they are quite old (and thus likely fixed today) and/or - moreinfo was asked and not given or - they are wishlist but rather special + exotic and not have been acted on for years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to close wishlist bugs.) If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll do if requested) or just file a new one - thats often better, as the bug log will be clearer and shorter and not contain cruft. cheers, HolgerAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---