The Definitive Guide to Installing Ubuntu on a MacBook 13” (white ...
17 Pages
English
Downloading requires you to have access to the YouScribe library
Learn all about the services we offer

The Definitive Guide to Installing Ubuntu on a MacBook 13” (white ...

-

Downloading requires you to have access to the YouScribe library
Learn all about the services we offer
17 Pages
English

Description

The Definitive Guide to Installing Ubuntu on a MacBook 13” (white ...

Subjects

Informations

Published by
Reads 111
Language English
Document size 1 MB

Exrait

The Definitive Guide to Installing Ubuntu on a MacBook 13” (white) Rev2.
by Trevelyn.
late 2007 Ubuntu 7.10 Gutsy.
Some people need more out of their machines and strive with grandeur to improve something that, to other people, may be just fine. Without these people, everything would be just fine and nothing, technologically speaking, would ever advance. So, with that said, I would like to take a minute to say I am sorry to my machine for all the verbal abuse it has endured during the many installations of this new, beautiful operating system. Once it's up, it's great. Getting there, is another story...
Note:  Before you go through with any of this MAKE SURE you back up the file /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBVideoSupport.kext/Contents/M acOS/AppleUSBVideoSupport onto a USB external drive or a local LAN SMB share! This is extremely important to use the iSight with your Linux System.
Firstly, put in the CD and reboot. Using Gutsy, you do not have to hold down any keys to boot from the CD, the CD will eventually boot itself. I have found that, even after the install, you should hold down the “Option” key during boot and select the boot device that way. It proves to be much faster this way. Eventually the boot process will finish and you can check to make sure things are working right. The resolution via the “915Reolution” intel drivers should have initialized correctly. The sound should be working, and your ethernet card should be working too. If not, it's no big deal really, you just have extra configuring to do later. If not try rerunning the Live CD by rebooting. Ping google.com in xterm and make sure your inet is up. If not, check your connection cables etc, and run dhclient. Dhclient is usually good at setting up your inet settings but if not you will have to add your name server to /etc/resolv.conf etc.
Now that you have made sure you are connected to the internet, double click on the install icon on the Gnome desktop. This will ask you a few questions like, your locale, your keyboard (please choose Macintosh so your “num lock” and “caps lock” lights work correctly), your name, your nick, your password and where you want to install it (please choose guided use entire disk). Then once finished click the “Restart Now” button in the information box that pops up. Pull out the CD, and press enter when prompted.
Note:  Make sure you get the disk out! If you don't and the computer reboots it will try to reboot the CD ignoring your most excessive attempts to tell it not to with the  eject button. Once the system has started up with the CD in the bay, the only thing you can do is hold down the  option key to select the HDD. (which, yes, will say  Windows. ) Chapter 0: getting started!! Once the system is back up and running, log into Gnome. Now, you will need to be Root for a lot of things so it's easiest to issue either a:
trevelyn@Celeritas:/$ sudo su
or a:
trevelyn@Celeritas:/$ sudo passwd root The decision is up to you. The first thing you want to do is uncomment any sources in your sources.list file located in /etc/apt/ so they can be used with the Apt package manager.
root@Celeritas:/# nano /etc/apt/sources.list
Remove the “#” from any lines that start with “#deb.” Now exit, and run the   updater for Apt package manager:
root@Celeritas:/# apt-get update Chapter 1: The Touchy Touch TouchPad Mouse Thing
Once finished, you are ready to begin configuring and installing things on your system. Firstly you can “fix the glitch” with the Touchpad. Open /etc/X11/xorg.conf and under the section that says [synaptics] add this:
Section "InputDevice"  Identifier "Synaptics Touchpad"  Driver "synaptics"  Option "SendCoreEvents" "true"          Option "Device" "/dev/psaux"  Option "Protocol" "auto-dev"  Option "HorizEdgeScroll" "0"  Option "TapButton1" "0"  Option "TapButton2" "0"   Option "TapButton3" 0" " Option "VertScrollDelta" "50"                  Option "VertTwoFingerScroll" "1" EndSection As you can see, the last five lines have been amended to the section. These make the Touchpad not so sensitive, and add a scroll feature to the very right edge of the pad. This is all preference though, you can add anything you want here that fits the syntax of xorg.conf. Being accustomed to OS X's behavior with the pad, has made me choose this over any other configuration I have found in any other tutorial. Now you can set up the “right click” button, which I have found to be very efficient when assigned to the “lower enter key.” To do this simply do:
_ _ root@Celeritas:/#sudo sed -i~ 's/KP Enter/Pointer Button3, Pointer_Button2/' /etc/X11/xkb/symbols/keypad
Then in “System->Preferences->Universal Access->Keyboard Accessibility click “Enable Keyboard Accessibility features.” Then under the “Mouse Keys” tab click “Enable Mouse Keys.” Now, restart X with “alt+ctrl+del” for the effects to take place.
Note: sometimes I have found that after rebooting my machine I have to re click the two radio buttons in the Keyboard Accessibility settings window as if the system  forgot my settings. It's no big deal really and doesn't happen all the time. If you hit the  lower enter key and nothing happens that's pretty much how to fix it.
Added 11.28.07 The scroll wheel simulation on the right side of the trackpad also acts as a “right mouse click” if tapped. So, be careful because sometimes it gets sensitive and can screw with your windows/etc.
Chapter 2: Fonts and the ALSA Sound System!
The mouse is settled, now lets fix the fonts! Fire up xterm and login as root again. for some reason the fonts in the title bars, information boxes, and even input boxes seem to be bold, and too big! Well to fix this open /etc/gdm/gdm.conf and change: [server-Standard] name=Standard server -command=/usr/bin/X -br -audit 0
to:
[server-Standard] name=Standard server -command=/usr/bin/X -br -audit 0 -dpi 96 And this usually requires a full reboot to fully take effect, but to have the title bars fixed you can simply restart X with “Ctrl+alt+del.” Now let's move right along to the Sound. Sound is okay at first but the Volume buttons on the keyboard don't really change anything so open xterm, and run:
root@Celeritas:/# alsamixer Turn up all the levels by pressing the up arrow and by moving to the next set by pressing either left or right. Once up, go to System->Preferences->Sound. And click on “PCM” in the bottom of the menu here:
Then, there's a second setting in the Volume applet in the top right side of the menu bar. Use your newly configured “Lower enter key” and right-click on it and go to preferences. Then again, click on “PCM” here:
Now that that is out of the way, add this line to /etc/modprobe.d/alsa-base:
install snd-hda-intel position_fix=1 /sbin/modprobe --ignore-install snd-hda-intel $CMDLINE_OPTS && /lib/alsa/modprobe-post-install snd-hda-intel Set it anywhere in the beginning of the file. That's it, the sound is taken care of. Amarok, Exaile and Sox will, when running, be lowered and raised in volume with the buttons on the keyboard, or the volume applet. If you choose xmms, the volume won't change at all, it will need configured through xmms first.
Added 11.28.07 : After running Ubuntu for a few days, my sound system dropped its kernel modules completely for no reason at all. So If this happens to you add this to /etc/rc.local 
“rmmod snd hda intel _ _ modprobe snd_hda_intel”
This script is run by “root” at each boot. you can really add anything you want that would run as a daemon, exempli gratia: Beryl, or smbd, nmbd. The syntax is just like any regular shell script, for rc.local. What a relief! - once again Google to the rescue!
Chapter 3: The Quantum iSight Driver.
As stated in the beginning of this tutorial you need a brand spanking new “AppleUSBVideoSupport” file from your latest OS X install. This particular file is very special. It almost reminds me of John Bells Quantum Entanglement theory. Once used in an install/configuration it changes. Even if you copy the file somewhere else too, on another keydrive and put it in a vault 300 miles away, that file changes too! Sometimes, it doesn't and you get lucky. So it has an all around chance Quantum Theory feel to it. If you ever have to reinstall and you find that you have followed this tutorial exactly the same way you did before, but for some reason the iSight does not
work, then that's why. So plug in your USB drive, which hopefully, shows up auto-mounted to the desktop. (I haven't had any problems with any USB drives so far, except for the 500GB drive RBCP loaned me) in xterm su, and do this:
root@Celeritas:/# cp /path/to/USBDrive/AppleUSBVideoSupport /lib/firmware/2.6.22-14-generic/
Then, in the file /etc/default/acpi-services add the string “isight_usb” into the quotes just after the word MODULE like so:
Then reboot. Fire up Ekiga, and set up your account, or not, and check these settings:
Once finished click on the webcam icon in Ekiga. If the iSight Driver “AppleUSBVideoSupport” file doesn't work you will know right off the bat. The fourth screen will say “Device not found.” Note:  as of 11.24.07 I haven't gotten the iSight to work with  Cheese or  Gstreamer-properties. But I am saving this pdf as an .odt file for future updates, so let's cross our fingers! Chapter 4: Wireless Driver's Drive You Up a Wall!
I am a wireless phreak. I have many wireless cards, from back when BackTrack was called Whax!, Whoppix, Auditor, etc. So I am pleased when I can use iwconfig or airmon.sh to put a card into monitor mode. I can't complain because, The first issue of madwifi-ng for the MacBooks internal WLAN card, was really bad. You couldn't use a WEP AP. In fact I made a second DMZ at Weak-Net Labs without WEP just to use my internal card. And, I found a work around! Here is the error received when trying to put “Ath0” into monitor mode:
  Well, as I said before, I have many cards and can use one of those for scanning or wireless security testing. Sadly, once I installed the second card and probed the kernel modules, the Atheros based internal WLAN card disappeared from the iwconfig list. But, here is the weird part; after a few installations of Ubuntu I found that I don't need to install the wireless drivers for the ralink chipset based card. Nope, Ubuntu thinks it's a prism2 chipset based card! And monitor mode works perfectly with it!