https://wiki.archlinux.org/api.php?action=feedcontributions&user=Wendell&feedformat=atomArchWiki - User contributions [en]2024-03-29T02:27:07ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Mathematica&diff=382145Mathematica2015-07-14T14:54:53Z<p>Wendell: Updated for Mathematica 10, with HiDPI section</p>
<hr />
<div>[[Category:Mathematics and science]]<br />
[[it:Mathematica]]<br />
{{stub}}<br />
{{out of date}}<br />
{{Related articles start}}<br />
{{Related|Scientific Applications}}<br />
{{Related|Sage-mathematics}}<br />
{{Related|Matlab}}<br />
{{Related articles end}}<br />
<br />
Mathematica is a commercial program used in scientific, engineering and mathematical fields. Here we explain how to install it.<br />
<br />
== Installation ==<br />
<br />
=== Mathematica 6 ===<br />
<br />
==== Mounting iso ====<br />
<br />
One way to mount the Mathematica .iso is to create ''/media/iso'' and add the following line to the fstab:<br />
/''location/of/mathematica.iso'' /media/iso iso9660 exec,ro,user,noauto,loop=/dev/loop0 0 0<br />
Now you can mount it with:<br />
mount /media/iso<br />
<br />
==== Running the Installer ====<br />
<br />
You can start the installer by navigating to:<br />
/Unix/Installer<br />
Run ''MathInstaller'' with:<br />
sh ./MathInstaller<br />
{{Note|If you do not place the "sh" in front, then you will get an error about a bad interpreter.}}<br />
<br />
==== Fonts ====<br />
<br />
Add the directories containing Type1 and BDF fonts to your FontPath.<br />
<br />
==== Troubleshooting ====<br />
<br />
If you have font rendering problems where certain symbols do not show up (i.e. "/" appears as a square), try uninstalling {{Pkg|font-mathematica}}.<br />
<br />
Also, try [http://mathematica.stackexchange.com/questions/1158/invisible-conjugate-glyph-in-the-linux-frontend this] solution.<br />
<br />
Try having applications use anti-aliasing. <br />
For KDE: System Settings > Application Appearance > Fonts > Use anti-aliasing (Enabled)<br />
<br />
=== Mathematica 7 ===<br />
<br />
Mathematica 7 is much easier to install.<br />
<br />
tar xf Mathematica-7.0.1.tar.gz<br />
cd Unix/Installer<br />
./MathInstaller<br />
<br />
Follow instructions.<br />
<br />
For KDE users, the Mathematica icon may appear in the ''Lost & Found'' category. To solve this, execute the following as root:<br />
<br />
# ln -s /etc/xdg/menus/applications-merged /etc/xdg/menus/kde-applications-merged<br />
<br />
=== Mathematica 8.0.4.0 ===<br />
<br />
On 64-bit machines, two known issues are present; but solutions are provided.<br />
The second issue is present on 64-bit installs: but not yet confirmed on a 32-bit arch setup.<br />
<br />
The first issue assumes you are trying to use nVidia, CUDA and OpenCL libraries within Mathematica.<br />
<br />
The 64-bit archlinux nVidia and opencl driver packages install libraries in {{ic|/usr/lib}}, not in {{ic|/usr/lib64}} as does nVidia's binary installer. This is not a problem: {{ic|/usr/lib}} is the correct location for 64-bit libraries on a 64-bit arch system. However, a 64-bit install of Mathematica will assume the drivers are installed in {{ic|/usr/lib64}}; other distributions that Mathematica has been tested on have their drivers in that location. The easiest method to overcome this is to make a symlink from {{ic|/usr/lib64}} to {{ic|/usr/lib}}. Mathematica will be able to find nVidia, CUDA, and OpenCL libraries this way without further tweaking.<br />
<br />
A second, separate but partial solution, is to set the following environment variables:<br />
<br />
export NVIDIA_DRIVER_LIBRARY_PATH=/usr/lib/libnvidia-tls.so<br />
<br />
export CUDA_LIBRARY_PATH=/usr/lib/libcuda.so<br />
<br />
This second method, however, still will not permit Mathematica to find the OpenCL libraries in {{ic|/usr/local}} as Mathematica seems hardwired to find them in {{ic|/usr/lib64}}.<br />
<br />
The second issue with Mathematica 8 in 64-bit archlinux (may also affect 32-bit environments; but not tested) is a reproducible crash when performing WolframAlpha[] functions. By default, Mathematica is configured to detect the system's proxy settings when configuring how to connect to the internet to fetch data. A "bug" exists that will eventually crash Mathematica when the calling library is used. A workaround is to avoid this library call altogether by configuring Mathematica to "directly connect" to the internet. (''Edit > Preferences > Internet Connectivity > Proxy Settings''). This bug has been reported to Wolfram.<br />
<br />
=== Mathematica 9 ===<br />
<br />
[[pacman|Install]] {{AUR|mathematica}} from the [[AUR]]. The ''Mathematica_9.0.1_LINUX.sh'' installation script is required.<br />
<br />
<br />
=== Mathematica 10 ===<br />
<br />
[[pacman|Install]] {{AUR|mathematica}} from the [[AUR]]. The ''Mathematica_10.XX.YY_LINUX.sh'' installation script is required; you will need to download this separately from Wolfram.com, your university, etc. You will also need an activation key.<br />
<br />
==== HiDPI / Retina Screens ====<br />
<br />
If you have a [[HiDPI|HiDPI]] screen, such as an Apple Retina display, and the main text in Mathematica looks small when you open it, this can be fixed:<br />
<br />
* Go to ''Edit → Preferences''<br />
* From the ''Advanced'' tab, click ''Open Option Inspector''<br />
* In the tree on the right, go to ''Formatting Options → Font Options → Font Properties''<br />
* Change the value for ''"ScreenResolution"'' to double its current setting, e.g. 72 → 144. You can also use <code>xdpyinfo | grep resolution</code> to get a more precise number (which will need to be doubled).<br />
<br />
== See also ==<br />
<br />
* [http://www.wolfram.com/mathematica/ Official site]<br />
* [http://www.wolfram.com/support/ Official Support]</div>Wendellhttps://wiki.archlinux.org/index.php?title=HiDPI&diff=377188HiDPI2015-06-02T22:17:53Z<p>Wendell: Xfce: fixed DPI setting summary</p>
<hr />
<div>[[Category:Graphics]]<br />
[[ja:HiDPI]]<br />
HiDPI (High Dots Per Inch) displays, also known by Apple's "[[wikipedia:Retina Display|Retina Display]]" marketing name, are screens with a high resolution in a relatively small format. They are mostly found in Apple products or high-end "ultrabooks", as well as in 4K (Ultra HD) or even 5K monitors.<br />
<br />
Not all software behaves well in high-resolution mode yet. Here are listed most common tweaks which make work on a HiDPI screen more pleasant.<br />
<br />
== Desktop environments ==<br />
<br />
=== GNOME ===<br />
<br />
To enable HiDPI, use gsettings:<br />
<br />
gsettings set org.gnome.desktop.interface scaling-factor 2<br />
<br />
=== KDE ===<br />
<br />
{{Out of date|Needs to be updated for KDE 5.}}<br />
KDE still has its share of HiDPI [https://community.kde.org/KDE/High-dpi_issues issues] but HiDPI support can be improved by changing the below settings:<br />
<br />
# Increase font dpi (System Settings → Application Appearance → Fonts → Force font dpi, enter a number such as 125, 144 or 150 etc)<br />
# Increase icon sizes (System Settings → Application Appearance → Icons → Advanced, here choose a higher icon size for all icons, eg. just increase each icon type by one step) <br />
<br />
=== Xfce ===<br />
<br />
Go to Settings Manager → Appearance → Fonts, and change the DPI parameter. The value of 180 or 192 seems to work well on Retina screens. To get a more precise number, you can use <code>xdpyinfo | grep resolution</code>, and then double it.<br />
<br />
To enlarge icons in system tray, right-click on it (aim for empty space / top pixels / bottom pixels, so that you will not activate icons themselves) → “Properties” → set “Maximum icon size” to 32, 48 or 64.<br />
<br />
=== Cinnamon ===<br />
<br />
Supports HiDPI since 2.2. Even without rebuilding GTK3, the support is pretty good (e.g. window borders are correctly sized, which is not the case under Xfce).<br />
<br />
=== Enlightenment ===<br />
<br />
For E18, go to the E Setting panel. In Look → Scaling, you can control the UI scaling ratios. A ratio of 1.2 seems to work well for the native resolution of the MBPr 15" screen.<br />
<br />
== X Server ==<br />
<br />
Some programs use the physical width to detect the DPI. Examples are i3 ([https://github.com/i3/i3/blob/next/libi3/dpi.c source]) and Chromium ([https://code.google.com/p/chromium/codesearch#chromium/src/ui/views/widget/desktop_aura/desktop_screen_x11.cc source]).<br />
<br />
To verify that the X Server has properly detected the physical dimensions of your monitor, run:<br />
<br />
$ xdpyinfo | grep -B 2 resolution<br />
screen #0:<br />
dimensions: 3200x1800 pixels (423x238 millimeters)<br />
resolution: 192x192 dots per inch<br />
<br />
This examples uses inaccurate dimensions (423mm x 328mm, even though the Dell XPS 9530 has 346mm x 194mm) to have a clean multiple of 96 dpi, in this case 192 dpi. This tends to work better than using the correct DPI — Pango renders fonts crisper in i3 for example.<br />
<br />
If the DPI displayed by xdpyinfo is not correct, see [[Xorg#Display size and DPI]] for how to fix it.<br />
<br />
== X Resources ==<br />
<br />
If you are not using a desktop environment such as GNOME, KDE, Xfce, or other that manipulates the X settings for you, you can set the desired Xft DPI setting manually in {{ic|~/.Xresources}}:<br />
<br />
{{hc|~/.Xresources|<nowiki><br />
Xft.dpi: 180<br />
Xft.autohint: 0<br />
Xft.lcdfilter: lcddefault<br />
Xft.hintstyle: hintfull<br />
Xft.hinting: 1<br />
Xft.antialias: 1<br />
Xft.rgba: rgb<br />
</nowiki>}}<br />
<br />
Make sure the settings are loaded properly when X starts, for instance in your {{ic|~/.xinitrc`}} with {{ic|xrdb -merge ~/.Xresources}} (see [[Xresources]] for more information).<br />
<br />
This will make the font render properly in most toolkits and applications, it will however not affect things such as icon size!<br />
<br />
== Browsers ==<br />
<br />
=== Firefox ===<br />
<br />
Open Firefox advanced preferences page ({{ic|about:config}}) and set parameter {{ic|layout.css.devPixelsPerPx}} to {{ic|2}} (or find the one that suits you better; {{ic|2}} is a good choice for Retina screens).<br />
<br />
If you use a HiDPI monitor such as Retina display together with another monitor, you can use [https://addons.mozilla.org/en-US/firefox/addon/autohidpi/ AutoHiDPI] add-on in order to automatically adjust {{ic|layout.css.devPixelsPerPx}} setting for the active screen.<br />
<br />
From Firefox version 38 onwards, your system (GTK+ 3.10) settings should be taken into account.[https://bugzilla.mozilla.org/show_bug.cgi?id=975919]<br />
<br />
=== Chromium / Google Chrome ===<br />
<br />
Full HiDPI support in Chrome is now available in the main branch {{AUR| google-chrome}} as of version 43.0.2357.2-1 and works out of the box as tested with Gnome and Cinnamon. Additionally, using older Chrome packages from AUR, and possibly chromium packages as well (not tested) the browser can be launched with the command line flag {{ic|--force-device-scale-factor}} and a scaling value. This will scale all content and ui, including tab and font size. For example:<br />
<br />
{{bc|1=google-chrome --force-device-scale-factor=2}}<br />
<br />
Using this option, a scaling factor of 1 would be normal scaling. Floating point values can be used.<br />
<br />
=== Opera ===<br />
<br />
Since version 24 one can alter Opera's DPI by starting it with the {{ic|1=--alt-high-dpi-setting=X}} command line option, where X is the desired DPI. For example, with {{ic|1=--alt-high-dpi-setting=144}} Opera will assume that DPI is 144. Newer versions of opera will auto detect the DPI using the font DPI setting (in KDE: the force font DPI setting.)<br />
<br />
Generally speaking, Opera's HiDPI support is excellent. Since it is also built using Chrome's blink renderer, and has an extension which runs most Chrome extensions, it is a very viable alternative to Chrome with much better HiDPI support.<br />
<br />
== Mail clients ==<br />
<br />
=== Thunderbird ===<br />
<br />
See [[#Firefox]]. To access {{ic|about:config}}, go to Edit → Preferences → Advanced → Config editor.<br />
<br />
=== Geary ===<br />
<br />
[https://wiki.gnome.org/Apps/Geary Geary]'s native UI elements are rendered by GTK3, so HiDPI works out of the box. However, the messages themselves are rendered by webkitgtk, which at the moment does not have HiDPI-support built-in, so the messages will appear blurry.<br />
<br />
There is a patched webkitgtk version, {{AUR|webkitgtk-hidpi}} in the [[AUR]], that will properly render webkit pages for HiDPI displays. Note that compilation of webkitgtk can take several hours. For a pre-built version you can install with pacman, see [https://github.com/hckr/webkitgtk-hidpi-bin here].<br />
<br />
== Skype ==<br />
<br />
Skype is a Qt program, and needs to be configured separately. You cannot change the DPI setting for it, but at least you can change font size. Install {{Pkg|qt4}} and run {{ic|qtconfig-qt4}} to do it.<br />
<br />
== IntelliJ IDEA ==<br />
<br />
If HiDPI support does not work, you have to add {{ic|1=-Dhidpi=true}} to your vmoptions file.[https://youtrack.jetbrains.com/issue/IDEA-114944]<br />
/usr/share/intellij-idea-ultimate-edition/bin/idea.vmoptions<br />
/usr/share/intellij-idea-ultimate-edition/bin/idea64.vmoptions<br />
<br />
== NetBeans ==<br />
<br />
NetBeans allows the font size of its interface to be controlled using the {{ic|1=--fontsize}} parameter during startup. To make this change permanent edit the {{ic|1=/usr/share/netbeans/etc/netbeans.conf}} file and append the {{ic|1=--fontsize}} parameter to the {{ic|1=netbeans_default_options}} property.[http://wiki.netbeans.org/FaqFontSize]<br />
<br />
The editor fontsize can be controlled from Tools → Option → Fonts & Colors.<br />
<br />
The output window fontsize can be controlled from Tools → Options → Miscelaneous → Output<br />
<br />
== Gimp 2.8 ==<br />
<br />
Use a high DPI theme, or [http://gimpforums.com/thread-increase-all-icons-on-hidpi-screen?pid=39113#pid39113 adjust] {{ic|1=gtkrc}} of an existing theme. For example set {{ic|1=GimpToolPalette::tool-icon-size}} to {{ic|1=dialog}}.<br />
<br />
== VLC ==<br />
<br />
The git vit version {{AUR|vlc-git}} on the AUR seems to solve some of the problems.<br />
<br />
== Other / Older applications ==<br />
<br />
One approach is to run the application full screen and without decoration in its own VNC desktop. Then scale the viewer. With Vncdesk ({{AUR|vncdesk-git}} from the [[AUR]]) you can set up a desktop per application, then start server and client with a simple command such as {{ic|vncdesk 2}}.<br />
<br />
[[x11vnc]] has an experimental option {{ic|-appshare}}, which opens one viewer per application window. Perhaps something could be hacked up with that.<br />
<br />
== GUI Toolkits ==<br />
<br />
=== Qt 5 ===<br />
<br />
Qt5 applications can often be run at higher dpi by setting the QT_DEVICE_PIXEL_RATIO environment variable. Note that the variable has to be set to a whole integer, so setting it to 1.5 will not work.<br />
<br />
This can for instance be enabled by creating a file {{ic|/etc/profile.d/qt-hidpi.sh}}<br />
<br />
export QT_DEVICE_PIXEL_RATIO=2<br />
<br />
And set the executable bit on it.<br />
<br />
=== GDK 3 (GTK+ 3) ===<br />
<br />
To scale UI elements by a factor of two:<br />
<br />
export GDK_SCALE=2<br />
<br />
To undo scaling of text:<br />
<br />
export GDK_DPI_SCALE=0.5<br />
<br />
== External displays ==<br />
The HiDPI setting is desktop-wide so that non-HiDPI external displays show everything too large. One workaround is to using [[xrandr]]'s scale option. To have a non-HiDPI monitor (on DP1) right of an internal HiDPI display (eDP1), one could run:<br />
<br />
xrandr --output eDP1 --auto --output DP1 --auto --scale 2x2 --right-of eDP1<br />
<br />
When extending above the internal display, you may see part of the internal display on the external monitor. In that case, specify the position manually, e.g. using [https://gist.github.com/wvengen/178642bbc8236c1bdb67 this script].<br />
<br />
You may run into problems with your mouse not being able to reach the whole screen. That is a [https://bugs.freedesktop.org/show_bug.cgi?id=39949 known bug] with an xserver-org patch (or try the panning option, but that might cause other problems).<br />
<br />
An example of the panning syntax for a 4k laptop with an external 1920x1080 monitor to the right:<br />
<br />
xrandr --output eDP1 --auto --output HDMI1 --auto --panning 3840x2160+3840+0 --scale 2x2 --right-of eDP1<br />
<br />
Generically if your hidpi monitor is AxB pixels and your regular monitor is CxD and you are scaling by [ExF], the commandline for right-of is:<br />
<br />
xrandr --output eDP1 --auto --output HDMI1 --auto --panning [C*E]x[D*F]+[A]+0 --scale [E]x[F] --right-of eDP1<br />
<br />
== Console ==<br />
<br />
The default console font will be very small on hidpi displays, the largest font is {{ic|sun12x22}}, to enable it (temporarily):<br />
<br />
$ setfont sun12x22<br />
<br />
See [[Fonts#Console fonts]] for more.<br />
<br />
== See also ==<br />
<br />
* [http://www.phoronix.com/scan.php?page=article&item=linux_uhd4k_gpus Ultra HD 4K Linux Graphics Card Testing] (Nov 2013)<br />
* [[Font configuration]]</div>Wendellhttps://wiki.archlinux.org/index.php?title=GNOME/Keyring&diff=198981GNOME/Keyring2012-04-25T15:34:55Z<p>Wendell: The location of the keyring changed in gnome 3.4</p>
<hr />
<div>[[Category:Daemons and system services]]<br />
[[Category:Desktop environments]]<br />
{{i18n|GNOME Keyring}}<br />
<br />
{{stub}}<br />
<br />
The GNOME Keyring stores passwords in an encrypted file that can be accessed by applications.<br />
<br />
== Manage using GUI ==<br />
pacman -S seahorse<br />
It is possible to leave the gnome keyring password blank. In seahorse, on the Passwords tab, right click on "Passwords: login" and pick "Change password." Enter the old password and leave empty the new password. You will be warned about using unencrypted storage; continue by pushing "Use Unsafe Storage."<br />
<br />
== Use Without Gnome ==<br />
It is possible to use GNOME Keyring without the rest of the gnome desktop. This can be accomplished by adding to your .xinitrc:<br />
# Start a dbus-session<br />
source /etc/X11/xinit/xinitrc.d/30-dbus<br />
# Start Gnome-Keyring<br />
eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)<br />
# You probably need to do this too:<br />
export SSH_AUTH_SOCK<br />
export GPG_AGENT_INFO<br />
export GNOME_KEYRING_CONTROL<br />
export GNOME_KEYRING_PID<br />
See [https://bugs.archlinux.org/task/13986 Bug #13986] for more info.<br />
<br />
== SSH Keys ==<br />
To add your SSH key:<br />
<br />
$ ssh-add ~/.ssh/id_dsa<br />
Enter passphrase for /home/mith/.ssh/id_dsa:<br />
<br />
To list automatically loaded keys:<br />
<br />
$ ssh-add -L<br />
<br />
To disable all keys;<br />
<br />
$ ssh-add -D<br />
<br />
Now when you connect to a server, the key will be found and a dialog will popup asking you for the passphrase. It has an option to automatically unlock the key when you login. If you check this you will not need to enter your passphrase again!<br />
<br />
== The gnome-keyring dialog does not appear in some terminals when connecting with SSH ==<br />
Solution:<br />
<br />
Add the following lines to your {{ic|~/.bashrc}}<br />
<br />
SSH_AUTH_SOCK=`netstat -xl | grep -o "$HOME"'/.cache/keyring-.*/ssh$'`<br />
[ -z "$SSH_AUTH_SOCK" ] || export SSH_AUTH_SOCK<br />
<br />
If you run on your terminal the following:<br />
<br />
echo $SSH_AUTH_SOCK<br />
<br />
will return something like the following:<br />
<br />
/home/USER/.cache/keyring-ABCDEF/ssh<br />
<br />
Now when you connect with ssh, gnome-keyring dialog will launch the "entry of the passphrase"<br />
<br />
== Unlock at Startup ==<br />
GNOME's login manager (gdm) will automatically unlock the keyring once you login, for others it is not so easy.<br />
<br />
For SLiM, see [[SLiM#SLiM_and_Gnome_Keyring]]<br />
<br />
If you are using automatic login, then you can disable the keyring manager by setting a blank password on the login keyring. '''Note''': your passwords will be stored unencrypted if you do this.<br />
<br />
== Useful Tools ==<br />
=== gnome-keyring-query ===<br />
{{ic|gnome-keyring-query}} from the AUR provides a simple command-line-tool for querying passwords from the password store of the Gnome Keyring.</div>Wendellhttps://wiki.archlinux.org/index.php?title=MacBookPro&diff=168190MacBookPro2011-10-31T01:09:51Z<p>Wendell: /* GRUB */</p>
<hr />
<div>[[Category:Apple (English)]]<br />
{{Out of date}}<br />
== WARNING OUTDATED ==<br />
Please see [[MacBook Aluminum]] for newest 5,1 and 5,2 unibody Macbook Pros or [[MacBook]] for general Macbook information.<br />
<br />
== Installing Arch Linux on MacbookPro ==<br />
<br />
These instructions could work for the most part for the regular MacBook.<br />
<br />
You will need Arch Linux 0.8 alpha3 or newer at least since GRUB and the kernel will work fine from this version.<br />
<br />
=== Arch Only System ===<br />
To install Arch and replace OSX you need to change the partition table type in Mac OS X from bootcamp. Download bootcamp, install and run. Change disk from GPT to MBR partition table.<br />
<br />
Reboot, hold down the "C" key to boot from CD.<br />
<br />
Install Arch as normal. Do not forget to set one partition as bootable.<br />
<br />
After install you need to configure a couple of things...<br />
<br />
=== Dual Boot (Arch & Mac OS X) ===<br />
<br />
Two possibilities:<br />
<br />
- Install Bootcamp, resize the Mac OS X partition<br />
<br />
When Mac OS X installation is finished. Go on http://refit.sourceforge.net and download rEFIT (Mac disk image)<br />
<br />
To install rEFIT, mount the rEFIT.dmg file (it is normally automatic).<br />
<br />
There is an other way (refer to rEFIT documentation) but you can open a terminal then you copy /Volumes/rEFIT/efi/ to /<br />
# cp -r /Volumes/rEFIT/efi /<br />
<br />
To install rEFIT :<br />
# cd /efi/refit/<br />
# ./enable.sh<br />
<br />
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.<br />
<br />
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.<br />
<br />
Now it is the typical Arch Linux installation.<br />
<br />
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.<br />
<br />
==== GRUB ====<br />
<br />
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.<br />
<br />
To install Arch Linux with GRUB as a dual-boot, follow these steps (tested on a Macbook Pro(6,2)):<br />
<br />
# 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.<br />
# Install rEFIt as above, reboot, and update the MBR (choose "Start Partitioning Tool" from the rEFIt menu on boot)<br />
# Insert the Arch Linux installation CD, reboot, and boot from the CD.<br />
# 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.<br />
# Reboot, update the MBR (same as step 1), and boot from the CD.<br />
# Now we install GRUB:<br />
# cd /<br />
# mount -t ext3 /dev/sdaN /mnt # where sdaN is the location you installed to.<br />
# mount -t ext3 /dev/sdaM /mnt/boot # where sdaM is the location of the /boot partition, if you have a separate one<br />
# mount -t proc proc /mnt/proc<br />
# mount -t sysfs sys /mnt/sys<br />
# mount -o bind /dev /mnt/dev<br />
# chroot /mnt /bin/bash<br />
# grub<br />
grub> root (hd0,M-1)<br />
grub> setup (hd0,M-1)<br />
grub> quit<br />
# reboot<br />
<ol start="7"><br />
<li>From the rEFIt menu on boot, choose "Boot Linux from Partition X"<\li><br />
<\ol><br />
<br />
Now you are at an Arch Linux command-line.<br />
<br />
== Configuration ==<br />
<br />
=== rc.conf ===<br />
Make sure your [[rc.conf]] at least has the following modules:<br />
MODULES=(sky2 fglrx speedstep_centrino)<br />
<br />
For CPU scaling use the [[powernowd]] package.<br />
<br />
=== Xorg ===<br />
Install:<br />
pacman -S ati-fglrx-utils<br />
<br />
A sample {{Filename|xorg.conf}} follows (Outdated! See [[Xorg Input Hotplugging]]):<br />
<br />
{{File<br />
|name=/etc/X11/xorg.conf<br />
|content=<nowiki><br />
Section "ServerLayout"<br />
Identifier "Simple Layout"<br />
Screen 0 "aticonfig-Screen[0]" 0 0<br />
InputDevice "Mouse1" "CorePointer"<br />
InputDevice "Keyboard1" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/75dpi"<br />
FontPath "/usr/share/fonts/100dpi"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "freetype"<br />
Load "xtt"<br />
Load "dbe" # Double buffer extension<br />
SubSection "extmod"<br />
Option "omit xfree86-dga" # do not initialize the DGA extension<br />
EndSubSection<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard1"<br />
Driver "kbd"<br />
Option "AutoRepeat" "500 30"<br />
Option "XkbRules" "xorg"<br />
Option "XkbModel" "pc105"<br />
Option "XkbLayout" "latam"<br />
Option "XkbOptions" "lv3:rwin_switch"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse1"<br />
Driver "mouse"<br />
Option "Protocol" "Auto" # Auto detect<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
Option "MinSpeed" "1.0"<br />
Option "MaxSpeed" "1.0"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "aticonfig-Monitor[0]"<br />
Option "VendorName" "ATI Proprietary Driver"<br />
Option "ModelName" "Generic Autodetecting Monitor"<br />
Option "DPMS" "true"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "aticonfig-Device[0]"<br />
Driver "fglrx"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "aticonfig-Screen[0]"<br />
Device "aticonfig-Device[0]"<br />
Monitor "aticonfig-Monitor[0]"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</nowiki>}}<br />
<br />
OR you can just make the necessary changes: (ADD these to your xorg.conf, do not replace)<br />
<br />
Configure Xorg using xorgconfig. Once done edit your "xorg.conf" and change the driver type to "fglrx".<br />
Section "Device"<br />
Driver "fglrx"<br />
EndSection <br />
<br />
Configure your keyboard: (make right "apple key" right ALT key)<br />
Section "InputDevice"<br />
Option "XkbOptions" "lv3:rwin_switch"<br />
EndSection<br />
<br />
Configure your trackpad:<br />
Section "InputDevice"<br />
Option "Protocol" "Auto"<br />
Option "MinSpeed" "1.0"<br />
Option "MaxSpeed" "1.0"<br />
EndSection<br />
<br />
OR you may want to use this, that emulates the Mac OS X behavior:<br />
<br />
Section "InputDevice"<br />
Identifier "Synaptics Touchpad"<br />
Driver "synaptics"<br />
Option "CorePointer"<br />
Option "Device" "/dev/input/mouse1"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "60"<br />
Option "RightEdge" "900"<br />
Option "BottomEdge" "511"<br />
Option "HorizScrollDelta" "0"<br />
Option "MinSpeed" "0.4"<br />
Option "MaxSpeed" "1"<br />
Option "AccelFactor" "0.08"<br />
Option "MaxTapTime" "0"<br />
Option "TapButton1" "0"<br />
#Two Finger Scroll<br />
Option "VertTwoFingerScroll" "1"<br />
Option "HorizTwoFingerScroll" "1"<br />
EndSection<br />
<br />
Configure modules:<br />
Section "Module"<br />
Load "dbe" # Double buffer extension<br />
SubSection "extmod"<br />
Option "omit xfree86-dga" # do not initialize the DGA extension<br />
EndSubSection<br />
EndSection<br />
<br />
=== Wireless ===<br />
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]. <br />
It is ugly, but it works. [http://ge.ubuntuforums.com/showpost.php?s=ca69b769276fb42cca3c591015993721&p=5141506&postcount=39 some ubuntu users]{{Linkrot|2011|09|07}} report it working with 64-bit too, albeit some have issues with WPA1/2.<br />
<br />
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.<br />
<br />
=== Pommed ===<br />
[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.<br />
<br />
Pommed is in [community], there is also a GUI built on GTK (gpomme)<br />
<br />
=== Suspend ===<br />
Suspend works most of the time (occasionally it dose not wake up) with the latest version of [[pm-utils]].<br />
<br />
sudo pacman -S pm-utils<br />
<br />
Run the following to test suspension. (Pressing the power button, plugging in a usb device, or closing/opening the lid will resume.)<br />
<br />
sudo pm-suspend<br />
<br />
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:<br />
<br />
button/lid)<br />
#echo "LID switched!">/dev/tty5<br />
if grep -q closed /proc/acpi/button/lid/LID0/state<br />
then pm-suspend<br />
fi<br />
;;<br />
<br />
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.<br />
<br />
== TODO ==<br />
I WILL get around to doing these! I promise! In the mean time I just put them here to remind me to do them.<br />
<br />
- make package for refit<br />
(EDIT: refit is actually in [community])<br />
<br />
- make section for isight</div>Wendellhttps://wiki.archlinux.org/index.php?title=MacBookPro&diff=168189MacBookPro2011-10-31T00:52:20Z<p>Wendell: /* GRUB */</p>
<hr />
<div>[[Category:Apple (English)]]<br />
{{Out of date}}<br />
== WARNING OUTDATED ==<br />
Please see [[MacBook Aluminum]] for newest 5,1 and 5,2 unibody Macbook Pros or [[MacBook]] for general Macbook information.<br />
<br />
== Installing Arch Linux on MacbookPro ==<br />
<br />
These instructions could work for the most part for the regular MacBook.<br />
<br />
You will need Arch Linux 0.8 alpha3 or newer at least since GRUB and the kernel will work fine from this version.<br />
<br />
=== Arch Only System ===<br />
To install Arch and replace OSX you need to change the partition table type in Mac OS X from bootcamp. Download bootcamp, install and run. Change disk from GPT to MBR partition table.<br />
<br />
Reboot, hold down the "C" key to boot from CD.<br />
<br />
Install Arch as normal. Do not forget to set one partition as bootable.<br />
<br />
After install you need to configure a couple of things...<br />
<br />
=== Dual Boot (Arch & Mac OS X) ===<br />
<br />
Two possibilities:<br />
<br />
- Install Bootcamp, resize the Mac OS X partition<br />
<br />
When Mac OS X installation is finished. Go on http://refit.sourceforge.net and download rEFIT (Mac disk image)<br />
<br />
To install rEFIT, mount the rEFIT.dmg file (it is normally automatic).<br />
<br />
There is an other way (refer to rEFIT documentation) but you can open a terminal then you copy /Volumes/rEFIT/efi/ to /<br />
# cp -r /Volumes/rEFIT/efi /<br />
<br />
To install rEFIT :<br />
# cd /efi/refit/<br />
# ./enable.sh<br />
<br />
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.<br />
<br />
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.<br />
<br />
Now it is the typical Arch Linux installation.<br />
<br />
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.<br />
<br />
==== GRUB ====<br />
<br />
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.<br />
<br />
To install Arch Linux with GRUB as a dual-boot, follow these steps (tested on a Macbook Pro(6,2)):<br />
<br />
# 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.<br />
# Install rEFIt as above, reboot, and update the MBR (choose "Start Partitioning Tool" from the rEFIt menu on boot)<br />
# Insert the Arch Linux installation CD, reboot, and boot from the CD.<br />
# 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.<br />
# Reboot, update the MBR (same as step 1), and boot from the CD.<br />
# Now we install GRUB:<br />
# cd /<br />
# mount -t ext3 /dev/sdaN /mnt # where sdaN is the location you installed to.<br />
# mount -t ext3 /dev/sdaM /mnt/boot # where sdaM is the location of the /boot partition, if you have a separate one<br />
# mount -t proc proc /mnt/proc<br />
# mount -t sysfs sys /mnt/sys<br />
# mount -o bind /dev /mnt/dev<br />
# chroot /mnt /bin/bash<br />
# grub<br />
grub> root (hd0,M-1)<br />
grub> setup (hd0,M-1)<br />
grub> quit<br />
# reboot<br />
# From the rEFIt menu on boot, choose "Boot Linux from Partition X"<br />
<br />
Now you are at an Arch Linux command-line.<br />
<br />
== Configuration ==<br />
<br />
=== rc.conf ===<br />
Make sure your [[rc.conf]] at least has the following modules:<br />
MODULES=(sky2 fglrx speedstep_centrino)<br />
<br />
For CPU scaling use the [[powernowd]] package.<br />
<br />
=== Xorg ===<br />
Install:<br />
pacman -S ati-fglrx-utils<br />
<br />
A sample {{Filename|xorg.conf}} follows (Outdated! See [[Xorg Input Hotplugging]]):<br />
<br />
{{File<br />
|name=/etc/X11/xorg.conf<br />
|content=<nowiki><br />
Section "ServerLayout"<br />
Identifier "Simple Layout"<br />
Screen 0 "aticonfig-Screen[0]" 0 0<br />
InputDevice "Mouse1" "CorePointer"<br />
InputDevice "Keyboard1" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/75dpi"<br />
FontPath "/usr/share/fonts/100dpi"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "freetype"<br />
Load "xtt"<br />
Load "dbe" # Double buffer extension<br />
SubSection "extmod"<br />
Option "omit xfree86-dga" # do not initialize the DGA extension<br />
EndSubSection<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard1"<br />
Driver "kbd"<br />
Option "AutoRepeat" "500 30"<br />
Option "XkbRules" "xorg"<br />
Option "XkbModel" "pc105"<br />
Option "XkbLayout" "latam"<br />
Option "XkbOptions" "lv3:rwin_switch"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse1"<br />
Driver "mouse"<br />
Option "Protocol" "Auto" # Auto detect<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
Option "MinSpeed" "1.0"<br />
Option "MaxSpeed" "1.0"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "aticonfig-Monitor[0]"<br />
Option "VendorName" "ATI Proprietary Driver"<br />
Option "ModelName" "Generic Autodetecting Monitor"<br />
Option "DPMS" "true"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "aticonfig-Device[0]"<br />
Driver "fglrx"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "aticonfig-Screen[0]"<br />
Device "aticonfig-Device[0]"<br />
Monitor "aticonfig-Monitor[0]"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</nowiki>}}<br />
<br />
OR you can just make the necessary changes: (ADD these to your xorg.conf, do not replace)<br />
<br />
Configure Xorg using xorgconfig. Once done edit your "xorg.conf" and change the driver type to "fglrx".<br />
Section "Device"<br />
Driver "fglrx"<br />
EndSection <br />
<br />
Configure your keyboard: (make right "apple key" right ALT key)<br />
Section "InputDevice"<br />
Option "XkbOptions" "lv3:rwin_switch"<br />
EndSection<br />
<br />
Configure your trackpad:<br />
Section "InputDevice"<br />
Option "Protocol" "Auto"<br />
Option "MinSpeed" "1.0"<br />
Option "MaxSpeed" "1.0"<br />
EndSection<br />
<br />
OR you may want to use this, that emulates the Mac OS X behavior:<br />
<br />
Section "InputDevice"<br />
Identifier "Synaptics Touchpad"<br />
Driver "synaptics"<br />
Option "CorePointer"<br />
Option "Device" "/dev/input/mouse1"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "60"<br />
Option "RightEdge" "900"<br />
Option "BottomEdge" "511"<br />
Option "HorizScrollDelta" "0"<br />
Option "MinSpeed" "0.4"<br />
Option "MaxSpeed" "1"<br />
Option "AccelFactor" "0.08"<br />
Option "MaxTapTime" "0"<br />
Option "TapButton1" "0"<br />
#Two Finger Scroll<br />
Option "VertTwoFingerScroll" "1"<br />
Option "HorizTwoFingerScroll" "1"<br />
EndSection<br />
<br />
Configure modules:<br />
Section "Module"<br />
Load "dbe" # Double buffer extension<br />
SubSection "extmod"<br />
Option "omit xfree86-dga" # do not initialize the DGA extension<br />
EndSubSection<br />
EndSection<br />
<br />
=== Wireless ===<br />
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]. <br />
It is ugly, but it works. [http://ge.ubuntuforums.com/showpost.php?s=ca69b769276fb42cca3c591015993721&p=5141506&postcount=39 some ubuntu users]{{Linkrot|2011|09|07}} report it working with 64-bit too, albeit some have issues with WPA1/2.<br />
<br />
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.<br />
<br />
=== Pommed ===<br />
[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.<br />
<br />
Pommed is in [community], there is also a GUI built on GTK (gpomme)<br />
<br />
=== Suspend ===<br />
Suspend works most of the time (occasionally it dose not wake up) with the latest version of [[pm-utils]].<br />
<br />
sudo pacman -S pm-utils<br />
<br />
Run the following to test suspension. (Pressing the power button, plugging in a usb device, or closing/opening the lid will resume.)<br />
<br />
sudo pm-suspend<br />
<br />
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:<br />
<br />
button/lid)<br />
#echo "LID switched!">/dev/tty5<br />
if grep -q closed /proc/acpi/button/lid/LID0/state<br />
then pm-suspend<br />
fi<br />
;;<br />
<br />
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.<br />
<br />
== TODO ==<br />
I WILL get around to doing these! I promise! In the mean time I just put them here to remind me to do them.<br />
<br />
- make package for refit<br />
(EDIT: refit is actually in [community])<br />
<br />
- make section for isight</div>Wendellhttps://wiki.archlinux.org/index.php?title=MacBookPro&diff=168188MacBookPro2011-10-31T00:48:22Z<p>Wendell: Putting in GRUB instructions</p>
<hr />
<div>[[Category:Apple (English)]]<br />
{{Out of date}}<br />
== WARNING OUTDATED ==<br />
Please see [[MacBook Aluminum]] for newest 5,1 and 5,2 unibody Macbook Pros or [[MacBook]] for general Macbook information.<br />
<br />
== Installing Arch Linux on MacbookPro ==<br />
<br />
These instructions could work for the most part for the regular MacBook.<br />
<br />
You will need Arch Linux 0.8 alpha3 or newer at least since GRUB and the kernel will work fine from this version.<br />
<br />
=== Arch Only System ===<br />
To install Arch and replace OSX you need to change the partition table type in Mac OS X from bootcamp. Download bootcamp, install and run. Change disk from GPT to MBR partition table.<br />
<br />
Reboot, hold down the "C" key to boot from CD.<br />
<br />
Install Arch as normal. Do not forget to set one partition as bootable.<br />
<br />
After install you need to configure a couple of things...<br />
<br />
=== Dual Boot (Arch & Mac OS X) ===<br />
<br />
Two possibilities:<br />
<br />
- Install Bootcamp, resize the Mac OS X partition<br />
<br />
When Mac OS X installation is finished. Go on http://refit.sourceforge.net and download rEFIT (Mac disk image)<br />
<br />
To install rEFIT, mount the rEFIT.dmg file (it is normally automatic).<br />
<br />
There is an other way (refer to rEFIT documentation) but you can open a terminal then you copy /Volumes/rEFIT/efi/ to /<br />
# cp -r /Volumes/rEFIT/efi /<br />
<br />
To install rEFIT :<br />
# cd /efi/refit/<br />
# ./enable.sh<br />
<br />
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.<br />
<br />
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.<br />
<br />
Now it is the typical Arch Linux installation.<br />
<br />
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.<br />
<br />
==== GRUB ====<br />
<br />
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.<br />
<br />
To install Arch Linux with GRUB as a dual-boot, follow these steps (tested on a Macbook Pro(6,2)):<br />
<br />
1) 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.<br />
2) Install rEFIt as above, reboot, and update the MBR (choose "Start Partitioning Tool" from the rEFIt menu on boot)<br />
3) Insert the Arch Linux installation CD, reboot, and boot from the CD.<br />
4) 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.<br />
5) Reboot, update the MBR (same as step 1), and boot from the CD.<br />
6) Now we install GRUB:<br />
# cd /<br />
# mount -t ext3 /dev/sdaN /mnt # where sdaN is the location you installed to.<br />
# mount -t ext3 /dev/sdaM /mnt/boot # where sdaM is the location of the /boot partition, if you have a separate one<br />
# mount -t proc proc /mnt/proc<br />
# mount -t sysfs sys /mnt/sys<br />
# mount -o bind /dev /mnt/dev<br />
# chroot /mnt /bin/bash<br />
# grub<br />
grub> root (hd0,M-1)<br />
grub> setup (hd0,M-1)<br />
grub> quit<br />
# reboot<br />
<br />
== Configuration ==<br />
<br />
=== rc.conf ===<br />
Make sure your [[rc.conf]] at least has the following modules:<br />
MODULES=(sky2 fglrx speedstep_centrino)<br />
<br />
For CPU scaling use the [[powernowd]] package.<br />
<br />
=== Xorg ===<br />
Install:<br />
pacman -S ati-fglrx-utils<br />
<br />
A sample {{Filename|xorg.conf}} follows (Outdated! See [[Xorg Input Hotplugging]]):<br />
<br />
{{File<br />
|name=/etc/X11/xorg.conf<br />
|content=<nowiki><br />
Section "ServerLayout"<br />
Identifier "Simple Layout"<br />
Screen 0 "aticonfig-Screen[0]" 0 0<br />
InputDevice "Mouse1" "CorePointer"<br />
InputDevice "Keyboard1" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/75dpi"<br />
FontPath "/usr/share/fonts/100dpi"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "freetype"<br />
Load "xtt"<br />
Load "dbe" # Double buffer extension<br />
SubSection "extmod"<br />
Option "omit xfree86-dga" # do not initialize the DGA extension<br />
EndSubSection<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard1"<br />
Driver "kbd"<br />
Option "AutoRepeat" "500 30"<br />
Option "XkbRules" "xorg"<br />
Option "XkbModel" "pc105"<br />
Option "XkbLayout" "latam"<br />
Option "XkbOptions" "lv3:rwin_switch"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse1"<br />
Driver "mouse"<br />
Option "Protocol" "Auto" # Auto detect<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
Option "MinSpeed" "1.0"<br />
Option "MaxSpeed" "1.0"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "aticonfig-Monitor[0]"<br />
Option "VendorName" "ATI Proprietary Driver"<br />
Option "ModelName" "Generic Autodetecting Monitor"<br />
Option "DPMS" "true"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "aticonfig-Device[0]"<br />
Driver "fglrx"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "aticonfig-Screen[0]"<br />
Device "aticonfig-Device[0]"<br />
Monitor "aticonfig-Monitor[0]"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</nowiki>}}<br />
<br />
OR you can just make the necessary changes: (ADD these to your xorg.conf, do not replace)<br />
<br />
Configure Xorg using xorgconfig. Once done edit your "xorg.conf" and change the driver type to "fglrx".<br />
Section "Device"<br />
Driver "fglrx"<br />
EndSection <br />
<br />
Configure your keyboard: (make right "apple key" right ALT key)<br />
Section "InputDevice"<br />
Option "XkbOptions" "lv3:rwin_switch"<br />
EndSection<br />
<br />
Configure your trackpad:<br />
Section "InputDevice"<br />
Option "Protocol" "Auto"<br />
Option "MinSpeed" "1.0"<br />
Option "MaxSpeed" "1.0"<br />
EndSection<br />
<br />
OR you may want to use this, that emulates the Mac OS X behavior:<br />
<br />
Section "InputDevice"<br />
Identifier "Synaptics Touchpad"<br />
Driver "synaptics"<br />
Option "CorePointer"<br />
Option "Device" "/dev/input/mouse1"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "60"<br />
Option "RightEdge" "900"<br />
Option "BottomEdge" "511"<br />
Option "HorizScrollDelta" "0"<br />
Option "MinSpeed" "0.4"<br />
Option "MaxSpeed" "1"<br />
Option "AccelFactor" "0.08"<br />
Option "MaxTapTime" "0"<br />
Option "TapButton1" "0"<br />
#Two Finger Scroll<br />
Option "VertTwoFingerScroll" "1"<br />
Option "HorizTwoFingerScroll" "1"<br />
EndSection<br />
<br />
Configure modules:<br />
Section "Module"<br />
Load "dbe" # Double buffer extension<br />
SubSection "extmod"<br />
Option "omit xfree86-dga" # do not initialize the DGA extension<br />
EndSubSection<br />
EndSection<br />
<br />
=== Wireless ===<br />
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]. <br />
It is ugly, but it works. [http://ge.ubuntuforums.com/showpost.php?s=ca69b769276fb42cca3c591015993721&p=5141506&postcount=39 some ubuntu users]{{Linkrot|2011|09|07}} report it working with 64-bit too, albeit some have issues with WPA1/2.<br />
<br />
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.<br />
<br />
=== Pommed ===<br />
[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.<br />
<br />
Pommed is in [community], there is also a GUI built on GTK (gpomme)<br />
<br />
=== Suspend ===<br />
Suspend works most of the time (occasionally it dose not wake up) with the latest version of [[pm-utils]].<br />
<br />
sudo pacman -S pm-utils<br />
<br />
Run the following to test suspension. (Pressing the power button, plugging in a usb device, or closing/opening the lid will resume.)<br />
<br />
sudo pm-suspend<br />
<br />
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:<br />
<br />
button/lid)<br />
#echo "LID switched!">/dev/tty5<br />
if grep -q closed /proc/acpi/button/lid/LID0/state<br />
then pm-suspend<br />
fi<br />
;;<br />
<br />
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.<br />
<br />
== TODO ==<br />
I WILL get around to doing these! I promise! In the mean time I just put them here to remind me to do them.<br />
<br />
- make package for refit<br />
(EDIT: refit is actually in [community])<br />
<br />
- make section for isight</div>Wendellhttps://wiki.archlinux.org/index.php?title=MacBookPro&diff=168187MacBookPro2011-10-31T00:30:28Z<p>Wendell: /* Dual Boot (Arch & Mac OS X) */</p>
<hr />
<div>[[Category:Apple (English)]]<br />
{{Out of date}}<br />
== WARNING OUTDATED ==<br />
Please see [[MacBook Aluminum]] for newest 5,1 and 5,2 unibody Macbook Pros or [[MacBook]] for general Macbook information.<br />
<br />
== Installing Arch Linux on MacbookPro ==<br />
<br />
These instructions could work for the most part for the regular MacBook.<br />
<br />
You will need Arch Linux 0.8 alpha3 or newer at least since GRUB and the kernel will work fine from this version.<br />
<br />
=== Arch Only System ===<br />
To install Arch and replace OSX you need to change the partition table type in Mac OS X from bootcamp. Download bootcamp, install and run. Change disk from GPT to MBR partition table.<br />
<br />
Reboot, hold down the "C" key to boot from CD.<br />
<br />
Install Arch as normal. Do not forget to set one partition as bootable.<br />
<br />
After install you need to configure a couple of things...<br />
<br />
=== Dual Boot (Arch & Mac OS X) ===<br />
<br />
Two possibilities:<br />
<br />
- Install Bootcamp, resize the Mac OS X partition<br />
<br />
When Mac OS X installation is finished. Go on http://refit.sourceforge.net and download rEFIT (Mac disk image)<br />
<br />
To install rEFIT, mount the rEFIT.dmg file (it is normally automatic).<br />
<br />
There is an other way (refer to rEFIT documentation) but you can open a terminal then you copy /Volumes/rEFIT/efi/ to /<br />
# cp -r /Volumes/rEFIT/efi /<br />
<br />
To install rEFIT :<br />
# cd /efi/refit/<br />
# ./enable.sh<br />
<br />
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.<br />
<br />
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.<br />
<br />
Now it is the typical Arch Linux installation.<br />
<br />
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.<br />
<br />
==== GRUB ====<br />
<br />
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]])<br />
<br />
== Configuration ==<br />
<br />
=== rc.conf ===<br />
Make sure your [[rc.conf]] at least has the following modules:<br />
MODULES=(sky2 fglrx speedstep_centrino)<br />
<br />
For CPU scaling use the [[powernowd]] package.<br />
<br />
=== Xorg ===<br />
Install:<br />
pacman -S ati-fglrx-utils<br />
<br />
A sample {{Filename|xorg.conf}} follows (Outdated! See [[Xorg Input Hotplugging]]):<br />
<br />
{{File<br />
|name=/etc/X11/xorg.conf<br />
|content=<nowiki><br />
Section "ServerLayout"<br />
Identifier "Simple Layout"<br />
Screen 0 "aticonfig-Screen[0]" 0 0<br />
InputDevice "Mouse1" "CorePointer"<br />
InputDevice "Keyboard1" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/75dpi"<br />
FontPath "/usr/share/fonts/100dpi"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "freetype"<br />
Load "xtt"<br />
Load "dbe" # Double buffer extension<br />
SubSection "extmod"<br />
Option "omit xfree86-dga" # do not initialize the DGA extension<br />
EndSubSection<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard1"<br />
Driver "kbd"<br />
Option "AutoRepeat" "500 30"<br />
Option "XkbRules" "xorg"<br />
Option "XkbModel" "pc105"<br />
Option "XkbLayout" "latam"<br />
Option "XkbOptions" "lv3:rwin_switch"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse1"<br />
Driver "mouse"<br />
Option "Protocol" "Auto" # Auto detect<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
Option "MinSpeed" "1.0"<br />
Option "MaxSpeed" "1.0"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "aticonfig-Monitor[0]"<br />
Option "VendorName" "ATI Proprietary Driver"<br />
Option "ModelName" "Generic Autodetecting Monitor"<br />
Option "DPMS" "true"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "aticonfig-Device[0]"<br />
Driver "fglrx"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "aticonfig-Screen[0]"<br />
Device "aticonfig-Device[0]"<br />
Monitor "aticonfig-Monitor[0]"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</nowiki>}}<br />
<br />
OR you can just make the necessary changes: (ADD these to your xorg.conf, do not replace)<br />
<br />
Configure Xorg using xorgconfig. Once done edit your "xorg.conf" and change the driver type to "fglrx".<br />
Section "Device"<br />
Driver "fglrx"<br />
EndSection <br />
<br />
Configure your keyboard: (make right "apple key" right ALT key)<br />
Section "InputDevice"<br />
Option "XkbOptions" "lv3:rwin_switch"<br />
EndSection<br />
<br />
Configure your trackpad:<br />
Section "InputDevice"<br />
Option "Protocol" "Auto"<br />
Option "MinSpeed" "1.0"<br />
Option "MaxSpeed" "1.0"<br />
EndSection<br />
<br />
OR you may want to use this, that emulates the Mac OS X behavior:<br />
<br />
Section "InputDevice"<br />
Identifier "Synaptics Touchpad"<br />
Driver "synaptics"<br />
Option "CorePointer"<br />
Option "Device" "/dev/input/mouse1"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "60"<br />
Option "RightEdge" "900"<br />
Option "BottomEdge" "511"<br />
Option "HorizScrollDelta" "0"<br />
Option "MinSpeed" "0.4"<br />
Option "MaxSpeed" "1"<br />
Option "AccelFactor" "0.08"<br />
Option "MaxTapTime" "0"<br />
Option "TapButton1" "0"<br />
#Two Finger Scroll<br />
Option "VertTwoFingerScroll" "1"<br />
Option "HorizTwoFingerScroll" "1"<br />
EndSection<br />
<br />
Configure modules:<br />
Section "Module"<br />
Load "dbe" # Double buffer extension<br />
SubSection "extmod"<br />
Option "omit xfree86-dga" # do not initialize the DGA extension<br />
EndSubSection<br />
EndSection<br />
<br />
=== Wireless ===<br />
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]. <br />
It is ugly, but it works. [http://ge.ubuntuforums.com/showpost.php?s=ca69b769276fb42cca3c591015993721&p=5141506&postcount=39 some ubuntu users]{{Linkrot|2011|09|07}} report it working with 64-bit too, albeit some have issues with WPA1/2.<br />
<br />
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.<br />
<br />
=== Pommed ===<br />
[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.<br />
<br />
Pommed is in [community], there is also a GUI built on GTK (gpomme)<br />
<br />
=== Suspend ===<br />
Suspend works most of the time (occasionally it dose not wake up) with the latest version of [[pm-utils]].<br />
<br />
sudo pacman -S pm-utils<br />
<br />
Run the following to test suspension. (Pressing the power button, plugging in a usb device, or closing/opening the lid will resume.)<br />
<br />
sudo pm-suspend<br />
<br />
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:<br />
<br />
button/lid)<br />
#echo "LID switched!">/dev/tty5<br />
if grep -q closed /proc/acpi/button/lid/LID0/state<br />
then pm-suspend<br />
fi<br />
;;<br />
<br />
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.<br />
<br />
== TODO ==<br />
I WILL get around to doing these! I promise! In the mean time I just put them here to remind me to do them.<br />
<br />
- make package for refit<br />
(EDIT: refit is actually in [community])<br />
<br />
- make section for isight</div>Wendellhttps://wiki.archlinux.org/index.php?title=Broadcom_wireless&diff=125267Broadcom wireless2010-12-14T06:24:56Z<p>Wendell: </p>
<hr />
<div>[[Category:Communication and network (English)]]<br />
[[Category:HOWTOs (English)]]<br />
= Introduction =<br />
<br />
Finally Broadcom has released a linux driver for most of its wireless chipsets. See the [http://ubuntuforums.org/showthread.php?t=914697 Ubuntu forums] and the [http://forums.debian.net/viewtopic.php?p=174719&sid=801a8f97aa7112c8c1c4f9294ad5d3e9 Debian forums]. It seems to work with all modern 43xx Broadcom cards. Up until recently the only way to get some of these working, such as 4328, was via [[ndiswrapper|ndiswrapper]]. Broadcom chipsets are used in most Dell laptops, among others.<br />
<br />
Unfortunately, the driver does not work with hidden ESSID's.<br />
<br />
= Determine whether you actually have one of these cards =<br />
<br />
Type in console (mind the letter case):<br />
$ lspci -nn | grep 14e4<br />
Look at the numbers at the end, in square brackets.<br />
<br />
Here is a list of cards which work with this driver:<br />
<br />
<pre><br />
[14e4:4311]<br />
[14e4:4312]<br />
[14e4:4313]<br />
[14e4:4315]<br />
[14e4:4727]<br />
[14e4:4328]<br />
[14e4:4328]<br />
[14e4:4329]<br />
[14e4:432a]<br />
[14e4:432b]<br />
[14e4:432c]<br />
[14e4:432d]<br />
[14e4:4353]<br />
[14e4:4357]<br />
</pre><br />
<br />
[http://www.broadcom.com/docs/linux_sta/README.txt This document] should have more up-to-date information.<br />
<br />
If you have some other Broadcom model you might try the [[Wireless#b43|b43]] driver. List of cards supported by b43 is [http://wireless.kernel.org/en/users/Drivers/b43 here], although other cards (e.g. 4727) may also work with this driver.<br />
<br />
= Driver installation =<br />
== Get the driver == <br />
There's a PKGBUILD in [http://aur.archlinux.org/packages.php?ID=19514 AUR].<br />
Or, you can download the driver from [http://www.broadcom.com/support/802.11/linux_sta.php here],<br />
where you will also find a README file.<br />
<br />
It is better to use the PKGBUILD, that way pacman will track all the files.<br />
<br />
== Load the kernel module ==<br />
Before loading the module, remove b43, or any other module you are using for your wireless card:<br />
# rmmod b43<br />
Load the module:<br />
# modprobe lib80211_crypt_tkip<br />
# modprobe wl<br />
<br />
You might also need to generate modules.dep and map file again by:<br />
# depmod -a<br />
<br />
Now you can make the change permanent by including lib80211_crypt_tkip in your MODULES array in {{Filename|/etc/rc.conf}}.<br />
<br />
MODULES=(lib80211_crypt_tkip ...<br />
<br />
Or if you installed module via AUR package you just need:<br />
# rmmod b43 # (or any other module you are using for your wireless card)<br />
# modprobe wl<br />
<br />
Now in iwconfig you should see a wireless device (for example eth1). You might need to restart your computer to see the device in iwconfig.<br />
<br />
To make the module load at boot just add in {{Filename|[[rc.conf]]}}:<br />
MODULES=(lib80211_crypt_tkip wl !b43 !ssb ...<br />
By blacklisting the 'b43' and 'ssb' modules, you will prevent the kernel from autoloading them instead of the desired modules.<br />
<br />
==Note on using multiple Broadcom kernel modules==<br />
<br />
In my Dell Inspiron Laptop, i have a Broadcom BCM4401 Ethernet card and a Broadcom BCM4328 Wireless card. If I just remove b43, I can load the wl driver, but no wireless card shows up. However, if i first remove the b44 (and ssb) driver for my ethernet card, and then load the wl driver, I get a wireless eth0. Afterwards, I can load b44 again, to have an ethernet eth1.<br />
<br />
Short version:<br />
* Put "lib80211_crypt_tkip" and "wl" at the BEFORE b44 (if you have it) position in MODULES= in /etc/rc.conf<br />
* Don't forget to blacklist b43<br />
* Your wireless card will be eth0<br />
* Your ethernet card will be eth1<br />
* Both will work fine<br />
<br />
<br />
= Troubleshooting =<br />
== Interfaces swapped every time == <br />
This is a common problem with this driver. And the next process works for me with the BCM4312 following the [http://wiki.archlinux.org/index.php/Udev#Mixed_Up_Devices.2C_Sound.2FNetwork_Cards_Changing_Order_Each_Boot udev post]:<br />
<br />
Create a file called <code>/etc/udev/rules.d/10-network.rules</code> and bind the MAC address of each of your cards to a certain interface name:<br />
<br />
<pre>SUBSYSTEM=="net", ATTR{address}=="aa:bb:cc:dd:ee:ff", NAME="eth0"<br />
SUBSYSTEM=="net", ATTR{address}=="ff:ee:dd:cc:bb:aa", NAME="eth1"</pre><br />
<br />
'''Where:'''<br />
* NAME="eth0" is the name of the interface that you want, for example the same name "eth0". You can use other names, for example "lan0" for eth0 or "wlan0" for eth1. <br />
* To get the MAC address of each card, use this command: <code>udevadm info -a -p /sys/class/net/<yourdevice> | grep address</code>. Please, note that this is case sensitive and you must use '''lower-case'''.<br />
But first you need know if eth0 isn't eth1 or vice versa, you can perform a scan: <code>iwlist scan</code> <br />
So if eth0 is really eth1 then the MAC of eth1 is that of eth0.<br />
<br />
Don't forget to update your /etc/rc.conf and other config files using the old ethX notation!<br />
<br />
== Module wl does not work after a kernel upgrade ==<br />
This is because the driver is compiled with the current kernel, you need recompile the driver with the new kernel for the module to function properly. Bear this in mind when doing kernel updates.<br />
<br />
== Device not showing up ==<br />
Be sure of trying "ifconfig -a", "ifconfig" only shows interfaces that are active.<br />
<br />
Here is one short script that helped me out, because I was loading modules incorrectly:<br />
<pre>#!/bin/bash<br />
<br />
rmmod b43 ssb wl lib80211_crypt_tkip lib80211<br />
<br />
modprobe lib80211_crypt_tkip<br />
modprobe wl<br />
<br />
depmod -a</pre><br />
<br />
This helped me when sometimes I couldn't get the interface to show up. Else, I recommend adding the modules in rc.conf:<br />
<pre>MODULES=([...] !b43 !ssb !lib80211 lib80211_crypt_tkip wl)</pre><br />
<br />
Worked for me in a Dell Latitude 2100 with Broadcom BCM5764M (eth) and BCM4312 (wifi). Also works in a HP Compaq 6715s with Broadcom BCM4311 (wifi).<br />
<br />
Also works on the HP Mini 110-1020LA netbook using BCM4312 chipset<br />
<br />
== Original b43, ssb, and lib80211 won't go away ==<br />
If you've followed the [[Speed_Up_udev]] advice, you'll see that the modules you try to prevent loading with a ! will load anyway. That's because the steps on that page (and I missed this reading it the first time) will effectively bypass the MODULES=() line in {{Filename|/etc/rc.conf}}.<br />
<br />
Yeah, there's a section that explains what you need to do if you're blacklisting modules, but honestly I didn't notice any boot-time savings so I reverted to the original {{Filename|/lib/udev/load-modules.sh}}.</div>Wendell