There is an other way (refer to rEFIT documentation) but you can open a terminal then you copy /Volumes/rEFIT/efi/ to /

+

# cp -r /Volumes/rEFIT/efi /

+

+

To install rEFIT :

+

# cd /efi/refit/

+

# ./enable.sh

+

+

Now we can synchronized MBR with GPT partition table thanks to rEFIT so you restart your computer. You can see rEFIT, you press down key to access to the Partitioning Tool. You press y to accept.

+

+

Put your Arch Linux CD in the CD-ROM drive first then restart the computer. You can press C to boot from the CD or you can choose it in the rEFIT menu.

+

+

Now it is the typical Arch Linux installation.

+

+

At the end of the installation DO NOT install the bootloader in the MBR, but in a partition (e.g. sda3). This may add complications; see below.

+

+

==== GRUB ====

+

+

Macs are partitioned using the EFI system, which GRUBv1 is not compatible with. Some versions of GRUB2 are compatible - however, GRUB2 is not on the installation CD as of the 2011.08.19 release. In order to work around this, rEFIt creates a MBR ([[Master Boot Record]]), which must be updated every time the partitions are modified or reformatted. However, only the first 4 partitions are put into the MBR; if you are dual booting, those first two will belong to the regular macbook installation.

+

+

To install Arch Linux with GRUB as a dual-boot, follow these steps (tested on a Macbook Pro(6,2)):

+

+

# Use the Disk Utility to resize your Mac partition, and create new partitions for your Linux installation. These can be formatted to anything - the Arch installation can reformat them as ext3 or ext4. Make sure that the / partition AND the /boot partition are BOTH in the first four partitions - or simply do not have a separate /boot partition, it isn't necessary.

+

# Install rEFIt as above, reboot, and update the MBR (choose "Start Partitioning Tool" from the rEFIt menu on boot)

+

# Insert the Arch Linux installation CD, reboot, and boot from the CD.

+

# Install Arch Linux, choosing a GRUB bootloader installation, but being careful to hit CANCEL when asked to install it to the MBR. The installation will consider this section 'FAILED', which is true, but we will take care of this.

OR you can just make the necessary changes: (ADD these to your xorg.conf, dont replace)

+

{{hc|/etc/X11/xorg.conf

+

|<nowiki>

+

Section "ServerLayout"

+

Identifier "Simple Layout"

+

Screen 0 "aticonfig-Screen[0]" 0 0

+

InputDevice "Mouse1" "CorePointer"

+

InputDevice "Keyboard1" "CoreKeyboard"

+

EndSection

+

+

Section "Files"

+

FontPath "/usr/share/fonts/misc"

+

FontPath "/usr/share/fonts/75dpi"

+

FontPath "/usr/share/fonts/100dpi"

+

FontPath "/usr/share/fonts/Type1"

+

EndSection

+

+

Section "Module"

+

Load "freetype"

+

Load "xtt"

+

Load "dbe" # Double buffer extension

+

SubSection "extmod"

+

Option "omit xfree86-dga" # do not initialize the DGA extension

+

EndSubSection

+

EndSection

+

+

Section "InputDevice"

+

Identifier "Keyboard1"

+

Driver "kbd"

+

Option "AutoRepeat" "500 30"

+

Option "XkbRules" "xorg"

+

Option "XkbModel" "pc105"

+

Option "XkbLayout" "latam"

+

Option "XkbOptions" "lv3:rwin_switch"

+

EndSection

+

+

Section "InputDevice"

+

Identifier "Mouse1"

+

Driver "mouse"

+

Option "Protocol" "Auto" # Auto detect

+

Option "Device" "/dev/input/mice"

+

Option "ZAxisMapping" "4 5 6 7"

+

Option "MinSpeed" "1.0"

+

Option "MaxSpeed" "1.0"

+

EndSection

+

+

Section "Monitor"

+

Identifier "aticonfig-Monitor[0]"

+

Option "VendorName" "ATI Proprietary Driver"

+

Option "ModelName" "Generic Autodetecting Monitor"

+

Option "DPMS" "true"

+

EndSection

+

+

Section "Device"

+

Identifier "aticonfig-Device[0]"

+

Driver "fglrx"

+

EndSection

+

+

Section "Screen"

+

Identifier "aticonfig-Screen[0]"

+

Device "aticonfig-Device[0]"

+

Monitor "aticonfig-Monitor[0]"

+

DefaultDepth 24

+

SubSection "Display"

+

Viewport 0 0

+

Depth 24

+

EndSubSection

+

EndSection

+

+

Section "DRI"

+

Mode 0666

+

EndSection

+

</nowiki>}}

+

+

OR you can just make the necessary changes: (ADD these to your xorg.conf, do not replace)

Configure Xorg using xorgconfig. Once done edit your "xorg.conf" and change the driver type to "fglrx".

Configure Xorg using xorgconfig. Once done edit your "xorg.conf" and change the driver type to "fglrx".

Line 55:

Line 221:

Option "MinSpeed" "1.0"

Option "MinSpeed" "1.0"

Option "MaxSpeed" "1.0"

Option "MaxSpeed" "1.0"

+

EndSection

+

+

OR you may want to use this, that emulates the Mac OS X behavior:

+

+

Section "InputDevice"

+

Identifier "Synaptics Touchpad"

+

Driver "synaptics"

+

Option "CorePointer"

+

Option "Device" "/dev/input/mouse1"

+

Option "Protocol" "auto-dev"

+

Option "LeftEdge" "60"

+

Option "RightEdge" "900"

+

Option "BottomEdge" "511"

+

Option "HorizScrollDelta" "0"

+

Option "MinSpeed" "0.4"

+

Option "MaxSpeed" "1"

+

Option "AccelFactor" "0.08"

+

Option "MaxTapTime" "0"

+

Option "TapButton1" "0"

+

#Two Finger Scroll

+

Option "VertTwoFingerScroll" "1"

+

Option "HorizTwoFingerScroll" "1"

EndSection

EndSection

Line 61:

Line 249:

Load "dbe" # Double buffer extension

Load "dbe" # Double buffer extension

SubSection "extmod"

SubSection "extmod"

−

Option "omit xfree86-dga" # don't initialise the DGA extension

+

Option "omit xfree86-dga" # do not initialize the DGA extension

EndSubSection

EndSubSection

EndSection

EndSection

−

== Wireless ==

+

=== Wireless ===

−

The airport card in the newest MacBook (PCI-ID 168c:0024) is not yet supported by Madwifi. In short: Madwifi does not yet have a version of the (binary-only) HAL (hardware-abstraction layer) for the new chipset and ETA is unknown. Workaround: If your kernel is 32-bit, you can use ndiswrapper in combination with the 2-bit windows driver for the D-Link DWA-645. It's ugly, but it works.

+

The airport card in the newest MacBook (PCI-ID 168c:0024) is not yet supported by Madwifi. In short: Madwifi does not yet have a version of the (binary-only) HAL (hardware-abstraction layer) for the new chipset and ETA is unknown. Workaround: If your kernel is 32-bit, you can use ndiswrapper in combination with the 32-bit windows driver for the [http://www.dlink.com/products/support.asp?pid=489&sec=0 D-Link DWA-645].

+

It is ugly, but it works. Some ubuntu users report it working with 64-bit too, albeit some have issues with WPA1/2.

−

== Pommed ==

+

Madwifi drivers work on my second generation MBP following [http://ubuntu-tutorials.com/2007/10/24/how-to-enable-wireless-networking-on-the-macbook-ubuntu-710/ these] instructions.

−

[http://technologeek.org/projects/pommed/ Pommed] handles the hotkeys and is able to adjusts the LCD backlight, sound volume, keyboard backlight or to ejects the CD-ROM drive.

+

−

There is a [http://aur.archlinux.org/packages.php?do_Details=1&ID=7984 PKGBUILD for pommed] in the AUR.

+

=== Pommed ===

−

There is also a [http://aur.archlinux.org/packages.php?do_Details=1&ID=7985 PKGBUILD of the GUI built on GTK] in the AUR.

+

[http://technologeek.org/projects/pommed/ Pommed] handles the hotkeys and is able to adjusts the LCD backlight, sound volume, keyboard backlight or to eject the CD-ROM drive.

−

If you like these packages, please vote for them!

+

−

= TODO =

+

Pommed is in [community], there is also a GUI built on GTK (gpomme)

−

I WILL get around to doing these! I promise! In the mean time I just put them here to remind me to do them.

+

−

- make package for mactel kernel

+

=== Suspend ===

+

Suspend works most of the time (occasionally it dose not wake up) with the latest version of [[pm-utils]].

+

+

sudo pacman -S pm-utils

+

+

Run the following to test suspension. (Pressing the power button, plugging in a usb device, or closing/opening the lid will resume.)

+

+

sudo pm-suspend

+

+

To suspend on closing of laptop lid, make sure you have acpi, and acpid installed with pacman, and that the acpid daemon is running. Then edit /etc/acpi/handler.sh and change the "button/lid)" section to look like the following:

+

+

button/lid)

+

#echo "LID switched!">/dev/tty5

+

if grep -q closed /proc/acpi/button/lid/LID0/state

+

then pm-suspend

+

fi

+

;;

+

+

Acpid calls the button/lid) section whenever the lid is opened or closed. If pm-suspend is just added to this section, it will suspend when the lid is opened, and when the lid is closed. Causing it to wake up, and then immediately suspend again when you open the lid. Checking to see if the lid is closed with grep and only running pm-suspend when the lid is closed fixes this issue.

+

+

== TODO ==

+

I WILL get around to doing these! I promise! In the mean time I just put them here to remind me to do them.

- make package for refit

- make package for refit

Revision as of 04:02, 11 April 2013

This article or section is out of date.

Reason:please use the first argument of the template to provide a brief explanation. (Discuss in Talk:MacBookPro#)

There is an other way (refer to rEFIT documentation) but you can open a terminal then you copy /Volumes/rEFIT/efi/ to /

# cp -r /Volumes/rEFIT/efi /

To install rEFIT :

# cd /efi/refit/
# ./enable.sh

Now we can synchronized MBR with GPT partition table thanks to rEFIT so you restart your computer. You can see rEFIT, you press down key to access to the Partitioning Tool. You press y to accept.

Put your Arch Linux CD in the CD-ROM drive first then restart the computer. You can press C to boot from the CD or you can choose it in the rEFIT menu.

Now it is the typical Arch Linux installation.

At the end of the installation DO NOT install the bootloader in the MBR, but in a partition (e.g. sda3). This may add complications; see below.

GRUB

Macs are partitioned using the EFI system, which GRUBv1 is not compatible with. Some versions of GRUB2 are compatible - however, GRUB2 is not on the installation CD as of the 2011.08.19 release. In order to work around this, rEFIt creates a MBR (Master Boot Record), which must be updated every time the partitions are modified or reformatted. However, only the first 4 partitions are put into the MBR; if you are dual booting, those first two will belong to the regular macbook installation.

To install Arch Linux with GRUB as a dual-boot, follow these steps (tested on a Macbook Pro(6,2)):

Use the Disk Utility to resize your Mac partition, and create new partitions for your Linux installation. These can be formatted to anything - the Arch installation can reformat them as ext3 or ext4. Make sure that the / partition AND the /boot partition are BOTH in the first four partitions - or simply do not have a separate /boot partition, it isn't necessary.

Install rEFIt as above, reboot, and update the MBR (choose "Start Partitioning Tool" from the rEFIt menu on boot)

Insert the Arch Linux installation CD, reboot, and boot from the CD.

Install Arch Linux, choosing a GRUB bootloader installation, but being careful to hit CANCEL when asked to install it to the MBR. The installation will consider this section 'FAILED', which is true, but we will take care of this.

Wireless

The airport card in the newest MacBook (PCI-ID 168c:0024) is not yet supported by Madwifi. In short: Madwifi does not yet have a version of the (binary-only) HAL (hardware-abstraction layer) for the new chipset and ETA is unknown. Workaround: If your kernel is 32-bit, you can use ndiswrapper in combination with the 32-bit windows driver for the D-Link DWA-645.
It is ugly, but it works. Some ubuntu users report it working with 64-bit too, albeit some have issues with WPA1/2.

Madwifi drivers work on my second generation MBP following these instructions.

Pommed

Pommed handles the hotkeys and is able to adjusts the LCD backlight, sound volume, keyboard backlight or to eject the CD-ROM drive.

Pommed is in [community], there is also a GUI built on GTK (gpomme)

Suspend

Suspend works most of the time (occasionally it dose not wake up) with the latest version of pm-utils.

sudo pacman -S pm-utils

Run the following to test suspension. (Pressing the power button, plugging in a usb device, or closing/opening the lid will resume.)

sudo pm-suspend

To suspend on closing of laptop lid, make sure you have acpi, and acpid installed with pacman, and that the acpid daemon is running. Then edit /etc/acpi/handler.sh and change the "button/lid)" section to look like the following:

Acpid calls the button/lid) section whenever the lid is opened or closed. If pm-suspend is just added to this section, it will suspend when the lid is opened, and when the lid is closed. Causing it to wake up, and then immediately suspend again when you open the lid. Checking to see if the lid is closed with grep and only running pm-suspend when the lid is closed fixes this issue.

TODO

I WILL get around to doing these! I promise! In the mean time I just put them here to remind me to do them.