{{Note|This page was written for the i3 model but I'm sure the i5 model will not be much different}}

{{Note|This page was written for the i3 model but I'm sure the i5 model will not be much different}}

−

==What DOESN'T work out of the box==

+

== What does '''not''' work out of the box ==

+

*Sleep/Hibernate (see below)

*Sleep/Hibernate (see below)

*Nvidia GPU (Switchable GPU, see below)

*Nvidia GPU (Switchable GPU, see below)

−

*Disk optimization (!!!!, See GPT and GRUB2 guide below)

*Fn Volume Keys (see below)

*Fn Volume Keys (see below)

−

==What Works out of the Box / With default configuration==

+

== What works out of the box / with default configuration ==

+

*CPU (all cores detected)

*CPU (all cores detected)

*Wireless

*Wireless

Line 38:

Line 36:

*USB

*USB

−

==Not Tested==

+

== Not tested ==

+

*HDMI

*HDMI

−

==Installation==

+

== Input/touchpad ==

−

Before running the Arch installer, you MUST install and configure a GPT partition scheme. If you do not, you will get '''terrible''' performance when writing small files (which should effect most users).

+

−

===(Pre-install) Configuring GPT (Erasing the whole disk)===

+

The keyboard and touchpad work more or less without problems using the {{Pkg|xf86-input-keyboard}} and {{Pkg|xf86-input-synaptics}} modules, respectively. Right- and left-clicking works, as well as Two-Finger scroll. Tapping is enabled out of the box and can be disabled in {{bc| /etc/X/xorg.conf.d/10-synaptics.}}

−

You must install some tools that are not included in the installer (you do not have to upgrade pacman):

+

−

{{bc|$ dhcpcd eth0}}

+

−

Update `pacman` and install `gdisk`

+

−

{{bc|$ pacman -Syy }}

+

−

{{bc|$ pacman -S gdisk}}

+

−

Launch `gdisk`

+

−

{{bc|$ gdisk /dev/sda}}

+

−

Since you want to start a new GPT table, choose the option to create a new GPT table.

+

== Bluetooth ==

−

The partitioning scheme here is important(!). Since you have to use GRUB2 to boot from a GPT disk, you MUST create a 200MB blank partition that you will never touch again(!). This small partition will hold GRUB2's core.img used for booting.

+

−

+

−

Using `gdisk`, press `n` to create a new partition, keeping an eye that the start sector should be '''2048''' and for end sector, enter `+200M`. Do not change the partition type; it should default to 8300. '''Remember to not format this in the installer'''.

+

−

+

−

From here, you can create the rest of your partitions. We will use `parted` to make your drive bootable later. Don't forget to write the changes to disk using the `w` command in `gdisk`.

+

−

+

−

Here you should '''reboot'''. After you boot back into the installer ISO, reinstall `gdisk`.

+

−

+

−

Now we need to create an MBR for the GPT disk . This allows GRUB2 to be installed to disk.

+

−

+

−

Open `gdisk` and press `r`, then press `h`... A common looking process is below:

+

−

+

−

{{Note|Pay close attention the answers to the prompt. Partition 2 in this case is the partition that contains /boot.}}

+

−

{{Note|I gathered this output after the installation, some things might be different for you at this stage}}

+

−

+

−

{{bc|

+

−

+

−

Command (? for help): r

+

−

Recovery/transformation command (? for help): h

+

−

+

−

WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,

+

−

just hit the Enter key at the below prompt and your MBR partition table will

+

−

be untouched.

+

−

+

−

Type from one to three GPT partition numbers, separated by spaces, to be

+

−

added to the hybrid MBR, in sequence: 2

+

−

Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): N

+

−

+

−

+

−

Creating entry for GPT partition #2 (MBR partition #1)

+

−

Enter an MBR hex code (default 83):

+

−

Set the bootable flag? (Y/N): Y

+

−

+

−

Creating entry for GPT partition #1 (MBR partition #2)

+

−

Enter an MBR hex code (default 83):

+

−

...

+

−

Unused partition space(s) found. Use one to protect more partitions? (Y/N): N

+

−

+

−

Recovery/transformation command (? for help): o

+

−

+

−

Disk size is 1250263728 sectors (596.2 GiB)

+

−

MBR disk identifier: 0x00000000

+

−

MBR partitions:

+

−

+

−

Number Boot Start Sector End Sector Status Code

+

−

1 * 1 1250263727 primary 0xEF

+

−

+

−

+

−

Recovery/transformation command (? for help): p

+

−

+

−

Disk /dev/sda: 1250263728 sectors, 596.2 GiB

+

−

Logical sector size: 512 bytes

+

−

Disk identifier (GUID): 1E222B9C-CF97-474C-AE7A-DB4B71AB163B

+

−

Partition table holds up to 128 entries

+

−

First usable sector is 34, last usable sector is 1250263694

+

−

Partitions will be aligned on 2048-sector boundaries

+

−

Total free space is 201421421 sectors (96.0 GiB)

+

−

+

−

Number Start (sector) End (sector) Size Code Name

+

−

1 2048 6143 2.0 MiB 8300 GRUB2

+

−

2 6144 268287 128.0 MiB 8300 BOOT

+

−

3 268288 1048844287 500.0 GiB 8300 ROOT

+

−

+

−

+

−

Recovery/transformation command (? for help): w

+

−

}}

+

−

+

−

What you just did, was create a Hybrid MBR. You should read more about this if you want to understand it.

+

−

+

−

At this point, you should '''reboot''' again so the kernel is aware of the disk changes.

+

−

+

−

You do not need to reinstall `gdisk` at this point.

+

−

+

−

''' At this point, you should install archlinux with the installer. '''

+

−

+

−

===(Arch Installer) Installing===

+

−

*Assure that you do not install/configure anything on the first 200MB partition that you created. You should start modifying and configuring partitions starting after that partition; usually /dev/sda2

+

−

+

−

*Do '''NOT''' install GRUB or any bootloader via the installer.

+

−

+

−

===(Post-install) Installing GRUB2===

+

−

*CHROOT into your new installation

+

−

+

−

After you have exited the installer, mount the required data in order to use your new installation:

+

−

{{bc|$ mount -o bind /dev /mnt/dev}}

+

−

{{bc|$ mount -t proc /proc /mnt/proc}}

+

−

{{bc|$ mount -t sysfs /sys /mnt/sys}}

+

−

+

−

Now enter the chroot.

+

−

{{bc|$ chroot /mnt bash}}

+

−

+

−

You are now in your new installation.

+

−

From here, update pacman and install 'gdisk', 'parted', and 'grub2-bios'.

+

−

+

−

We need to do a few things here. We need change a '''bios_grub FLAG''' on that 200M partition, and we need to add a '''boot FLAG''' on the partition with your /boot partition.

Lastly, make a grub config. (also do this if you make changes /etc/default/grub)

+

−

{{bc|$ grub-mkconfig -o /boot/grub/grub.cfg}}

+

−

+

−

Follow the rest of the Sections below to get all of the hardware working.

+

−

+

−

==Input / Touchpad==

+

−

The keyboard and touchpad work more or less without problems using the {{Pkg|xf86-input-keyboard}} and {{Pkg|xf86-input-synaptics}} modules, respectively. Right- and left-clicking works, as well as Two-Finger scroll. Tapping is enabled out of the box and can be disabled in {{bc| /etc/X/xorg.conf.d/10-synaptics.}}

+

−

==Bluetooth==

Installing a tool like "blueman" from the AUR and starting the bluetooth DAEMON allowed communication to bluetooth keyboards and mice.

Installing a tool like "blueman" from the AUR and starting the bluetooth DAEMON allowed communication to bluetooth keyboards and mice.

Bluetooth speakers not tested. (*users feel free to add to this)

Bluetooth speakers not tested. (*users feel free to add to this)

−

==Nvidia GPU (Optimus)==

+

== Nvidia GPU (Optimus) ==

−

{{Note|Your best bet for this part is to install 'yaourt' from the AUR to ease in installing the following packages}}

+

−

Read the [https://wiki.archlinux.org/index.php/Bumblebee Bumblebee]/optimus page. I will only outline a few things...

+

−

You need to install the packages (and all of their dependencies) :

+

{{Tip|Your best bet for this part is to install {{AUR|yaourt}} from the AUR to ease in installing the following packages}}

−

*bumblebee

+

−

*nvidia-bumblebee

+

You need to install the packages {{Pkg|bumblebee}} and {{Pkg|bbswitch}}.

−

*nvidia-utils-bumblebee

+

−

*bbswitch

+

In short, Bumblebee allows you to use the switchable GPU and use it only when you want to via the 'optirun' application.

In short, Bumblebee allows you to use the switchable GPU and use it only when you want to via the 'optirun' application.

−

Be sure to add 'bumblebeed' to your DAEMONS array in '''rc.conf'''.

+

Be sure enable '''bumblebeed''' [[Systemd]] service to start Bumblebee at boot.

Once you reboot, you should start seeing huge power saving.

Once you reboot, you should start seeing huge power saving.

To check and make sure that you aren't using your GPU all the time:

To check and make sure that you aren't using your GPU all the time:

−

{{bc|<nowiki>$ lsmod | grep nv</nowiki>}}

+

$ lsmod | grep nv

Should return nothing, this means your GPU is off.

Should return nothing, this means your GPU is off.

You can check your GPU by running '''glxgears''' with and without the 'optirun' prefix and comparing the Frames Per Second.

You can check your GPU by running '''glxgears''' with and without the 'optirun' prefix and comparing the Frames Per Second.

−

==Sound==

+

Read the [[Bumblebee]] page for further informations.

−

Install the typical ALSA packages (libs, oss, plugins, utils).

+

−

After the installation, you need to launch alsamixer

+

−

{{bc|$ alsamixer}}

+

−

And raise the '''SPEAKER''' level, pressing '''ESC''' to save. You should now have (low quality) sound. This is a work in progress.

+

== Suspend/hibernate ==

−

==Suspend / Hibernate==

+

The USB unbind hook is no longer necessary as of [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=dbf0e4c7257f8d684ec1a3c919853464293de66e Linux 3.5].

−

Attempting to suspend will put your machine into a coma. The issue here is that you need to unload the EHCI module before sleeping.

+

−

{{ Note| ACPI by default doesn't call pm-suspend, if we want to customize the sleep process, we need pm-suspend }}

+

−

Create a script:

+

{{Note|ACPI by default doesn't call pm-suspend, if we want to customize the sleep process, we need pm-suspend }}

−

{{bc|$ nano /etc/pm/sleep.d/20-asus-u31sd}}

+

−

{{bc|<nowiki>

+

If you want sleep your machine when you '''close your lid''', you need to edit ACPI handler script {{ic|/etc/acpi/handler.sh}}

−

#!/bin/sh

+

−

+

−

BUSES="0000:00:1a.0 0000:00:1d.0"

+

−

+

−

case "${1}" in

+

−

hibernate|suspend)

+

−

# Switch USB buses off

+

−

for bus in $BUSES; do

+

−

echo -n $bus | tee /sys/bus/pci/drivers/ehci_hcd/unbind

+

−

done

+

−

;;

+

−

resume|thaw)

+

−

# Switch USB buses back on

+

−

for bus in $BUSES; do

+

−

echo -n $bus | tee /sys/bus/pci/drivers/ehci_hcd/bind

+

−

done

+

−

;;

+

−

esac

+

−

</nowiki>}}

+

−

+

−

Give it executable flag:

+

−

{{bc|$ chmod +x /etc/pm/sleep.d/20-asus-u31sd}}

+

−

+

−

If you want sleep your machine when you '''close your lid''', you need to edit ACPI handler script:

+

−

+

−

{{bc|$ nano /etc/acpi/handler.sh}}

+

Change line 20, to this:

Change line 20, to this:

−

{{bc|<nowiki> SLPB|SBTN) pm-suspend ;;</nowiki>}}

+

SLPB|SBTN) pm-suspend ;;

And Towards the bottom, make lines 58 and 59 look line like this:

And Towards the bottom, make lines 58 and 59 look line like this:

Line 241:

Line 85:

}}

}}

−

So now you can use the '''hotkey (F1)''' or close your lid and your laptop will sleep.

+

So now you can use the hotkey ({{ic|F1}}) or close your lid and your laptop will sleep.

−

==Fn Multimedia Keys==

+

== Fn multimedia keys ==

−

As with most Asus laptops/netbooks, this laptop sends its Multimedia events via ACPI. Using `acpi_listen`, I was able to discover the button commands the buttons sent to acpi. Add the following to your '''/etc/acpi/handler.sh''' file (make sure you add this after the ;; in the button/lid section):

+

+

As with most Asus laptops/netbooks, this laptop sends its Multimedia events via ACPI. Using '''acpi_listen''', I was able to discover the button commands the buttons sent to acpi. Add the following to your {{ic|/etc/acpi/handler.sh}} file (make sure you add this after the ;; in the button/lid section):

{{bc|

{{bc|

button/volumeup)

button/volumeup)

Line 258:

Line 103:

You can mess with these values to move your volume at different intervals, 5 seemed to work well for me.

You can mess with these values to move your volume at different intervals, 5 seemed to work well for me.

+

+

== Optimize power consumption ==

+

+

Add this to the kernel line of your bootloader[http://www.linlap.com/asus_u31sd]:

Note: This page was written for the i3 model but I'm sure the i5 model will not be much different

What does not work out of the box

Sleep/Hibernate (see below)

Nvidia GPU (Switchable GPU, see below)

Fn Volume Keys (see below)

What works out of the box / with default configuration

CPU (all cores detected)

Wireless

Ethernet

Framebuffer resolution (nouveau and intel xorg drivers provide this)

Intel GPU

Touchpad

Bluetooth

Hotkeys (Brightness / Monitor on-off / wifi / sleep)

USB

Not tested

HDMI

Input/touchpad

The keyboard and touchpad work more or less without problems using the xf86-input-keyboard and xf86-input-synaptics modules, respectively. Right- and left-clicking works, as well as Two-Finger scroll. Tapping is enabled out of the box and can be disabled in

/etc/X/xorg.conf.d/10-synaptics.

Bluetooth

Installing a tool like "blueman" from the AUR and starting the bluetooth DAEMON allowed communication to bluetooth keyboards and mice.
Bluetooth speakers not tested. (*users feel free to add to this)

Nvidia GPU (Optimus)

Tip: Your best bet for this part is to install yaourtAUR from the AUR to ease in installing the following packages

Suspend/hibernate

Note: ACPI by default doesn't call pm-suspend, if we want to customize the sleep process, we need pm-suspend

If you want sleep your machine when you close your lid, you need to edit ACPI handler script /etc/acpi/handler.sh

Change line 20, to this:

SLPB|SBTN) pm-suspend ;;

And Towards the bottom, make lines 58 and 59 look line like this:

close)
pm-suspend

So now you can use the hotkey (F1) or close your lid and your laptop will sleep.

Fn multimedia keys

As with most Asus laptops/netbooks, this laptop sends its Multimedia events via ACPI. Using acpi_listen, I was able to discover the button commands the buttons sent to acpi. Add the following to your /etc/acpi/handler.sh file (make sure you add this after the ;; in the button/lid section):