Updated: Jun 25, 2009
This is a continuation of my Fedora 11 Beta on MacBook Aluminum 5,1 notes. I am going to gear this one more specifically on how to get Fedora 11 behaving on a MacBook Aluminum. Here we go…
Note: You’ll notice that there are a lot of TBDs. Well, that’s because I just installed Fedora 11 on my MacBook and haven’t had the time to dive in yet. These will be filled in as I go along.
Gain internet access using a hardwired ethernet connection then install and enable the RPM Fusion repos for both the free and non-free packages:
su -c 'rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'
Apply all updates to the system:
Goto System -> Administration -> Software Updates and apply the updates if they exist.
Source: leigh123linux on the Fedora Forums
Install Nvidia Drivers then reboot:
su -c 'yum install akmod-nvidia xorg-x11-drv-nvidia-libs.i586 xorg-x11-drv-nvidia-libs.x86_64'
Blacklist the Nouveau Driver:
Then add the following to the bottom of the file:
# Video drivers
Backup the old initrd:
mv /boot/initrd-`uname -r`.img /boot/initrd-`uname -r`.img.backup
mkinitrd -v /boot/initrd-`uname -r`.img `uname -r`
Start with backing it up:
cp /etc/X11/xorg.conf /etc/X11/xorg.conf.bak
Edit the file:
Should look like this:
Option “AIGLX” “on”
Option “AddARGBGLXVisuals” “True”
Option “Composite” “Enable”
Tell livna-config-display to keep it’s hands off of xorg.conf:
shutdown -r now
If you have difficulties getting back to the GUI and you’re stuck at a blinking cursor, press fn+control+option+F2 to get to a terminal screen, and then edit the xorg.conf file using vi and change the ‘Driver “nvidia”‘ option to ‘Driver “nv”‘. Save, exit, and reboot.
Install the “akmod-wl” drivers then restart:
su -c 'yum install akmod-wl'
Update system to the latest kernel and packages. Simple as navigating in the main menu:
“System -> Administration -> Update System”
If you’d like to have two finger scrolling and such, navigate to the mouse settings in the main menu and select the “touchpad” tab:
“System -> Preferences -> Mouse”
Original bug information here: https://bugzilla.redhat.com/show_bug.cgi?id=504197
Exciting news on this subject… I was able to get the sound working both headphones and internal speakers using AlsaMixer v.1.0.20 (should already be installed). There’s a couple of catches though. When you plug your headphones in, you’ll hear sound both from the internal speaker as well as the headphones. Also, the “Mute” button doesn’t actually mute the sound, but if you turn down the sound all the way, it will shut off.
Add this line to the file and save:
options snd_hda_intel model=mbp3
Then, remove alsa-plugins-pulseaudio:
yum remove alsa-plugins-pulseaudio
Then, adjust the audio settings:
I’ve included the screenshot below for reference, but I believe the important parts are to turn up the volume to 100% on these lines (you can tweak this later while listening to something): Master, PCM, Front, Line, Line-Out. Then, set the “Channel” category to 6ch instead of 2ch. If you don’t see what’s in the screenshot below, try restarting.
Finally, store the settings and reboot:
Note: It is possible to turn down the internal volume all the way and listen to only the headphones, but it requires that you turn the “Line-Out” volume off within AlsaMixer. OR you can easily switch the speaker on an off by switching between 6ch and 2ch. The headphones will still work on 2ch but the internal speakers will not (thanks to Ben Pierce for pointing out this simple solution. I tend to over-analyse things sometimes.).
These are working out of the box.
If you’d like to customize the keys a little more to your liking (for example, swapping the command and control keys), please refer to this fedora forums post.
TBD (To Be Done)
Apparently, this should be working out of the box. In fact, if you type “lahal -m output” into the terminal, and then use the brightness keys, you’ll get some feedback from hal, but nothing happens. There has been a bug filed for this and we’re just kinda waiting for a fix. https://bugzilla.redhat.com/show_bug.cgi?id=505531
The closest fix that we’ve gotten so far is to add the “nomodeset” to the grub.conf file which will disable kernel mode settings. Apparently, there have been some people which this works for. I tried it and it didn’t work. If you’re having the same problem, please report it in the bug report above. To try to nomodeset fix, follow these instructions:
su -c 'gedit /boot/grub/grub.conf'
Within that file, add the option “nomodeset” on the same line as “kernel /boot”. When finished, the important lines should look like this:
title Fedora (188.8.131.52-167.fc11.i686.PAE)
kernel /boot/vmlinuz-184.108.40.206-167.fc11.i686.PAE ro root=UUID=820abdb8-dcb9-4a27-89c9-ad73f941fd73 rhgb quiet nomodeset
The other thing that may work, but sounds like it’s NOT the proper way (more of a bad band-aid solution and I’m only making it available here for reference purpose) is to install pommed. This is outlined below if you’d like to try it. I would probably advise against it (others have advised me not to). I had followed these steps and it didn’t work for me either.
Download it and then extract it:
Install the required packages:
su -c 'yum install libdbus-devel alsa-lib-devel audiofile-devel zlib-devel libconfuse libconfuse-devel pciutils-devel
“Make” pommed by typing this into the terminal while in the pommed-1.26 parent directory:
Become su and copy the files to the needed directories (one line at a time):
cp pommed/pommed /usr/bin
cp pommed/data/* /usr/share/pommed
cp pommed.conf.mactel /etc/pommed.conf
chmod +x pommed.init
cp pommed.init /etc/init.d/pommed
chkconfig --add pommed
cp dbus-policy.conf /etc/dbus-1/system.d/pommed.conf
After using the system for a few days, it seems that everything power related works just fine. The battery doesn’t last as long as it would within Mac OSX, but it still goes pretty long. It will be better once the backlight control works.
I’ve also noticed that the MacBook runs a little on the warmer side than in Mac OSX, especially when it’s unplugged and on a non-flat surface. Just an observation.
Also, when the laptop goes into a “sleep” mode after closing the lid, upon wake-up the wireless or network no longer work. I would recommend setting your computer’s screen to simply turn blank when shutting the lid and to shutdown after so much time. These settings can be found in the power management applet or in “System -> Preferences -> Power Management”.