The Lenovo IdeaPad Y580 started shipping in June 2012. It is a fairly powerful machine, but it has its own compatibility issues. The purpose of this article is to help with setting up Arch Linux on this machine.

−

The Lenovo IdeaPad Y580 started shipping in June 2012. It is a fairly powerful machine, but it has its own compatibility issues. Hopefully this will help someone who wants to set it up with Arch Linux (it may also work with other distros).

===Installation===

===Installation===

−

As of 09/01/2012, Arch Linux does not have an installer anymore. The official way to install the system is to download the latest image: 2012.08.04, the use the Arch install scripts. I have yet to try those, but you can always use this guide: https://wiki.archlinux.org/index.php/Install_from_Existing_Linux to install everything manually.

−

In theory this can be done from any distro, but it is much easier to do it from the Arch live cd since in this case you do not need to manually install Pacman.

−

If you cannot get wireless working, you can use an ethernet connection with the help of the driver alx. This driver is not yet part of the Linux kernel, and that is why your ethernet card is not recognized at first. You need to download the driver from the Linux Foundation's website:

+

Install Arch on the machine if you have not done it already. Read [[Installation Guide]] for more information.

If you cannot get wireless working, you can use an ethernet connection with the help of the driver alx. This driver is not yet part of the Linux kernel, and that is why your ethernet card is not recognized at first. The links from linux foundation doesn't build from sources for alx. Try this modified [http://dl.dropbox.com/u/106654446/compat-drivers-2013-02-03-modified.tar.gz alx source files]. This method works for current Feb 2013 Arch installation media for 3.7.x kernels.

+

This sources is found to work for both AR8161 and AR8162 ethernet devices.

Copy the tarball to a flash drive, boot the live cd, mount the flash drive, cd to the directory with the tarball and use:

Copy the tarball to a flash drive, boot the live cd, mount the flash drive, cd to the directory with the tarball and use:

Line 21:

Line 18:

After this, load the module (modprobe alx) and you should be able to get ethernet working easily.

After this, load the module (modprobe alx) and you should be able to get ethernet working easily.

−

My model has a 32GB SSD drive and a 1TB 5400 rpm drive. It comes with Windows 7 and some Lenovo partitions that may be important if you need to recover the Windows install. Since I was positive about only using Linux, I just deleted everything so that I could use the SSD drive to install Arch (and get a faster boot). But you may want to think twice before doing this, or at least backup the partition's contents before erasing them.

+

The machine comes with Windows 7 and some Lenovo partitions that may be important if you need to recover the Windows install.

+

+

In case you don't need to restore the machine to their original state, you can just delete the existing partition. Other way, backup the partions before erasing them

Also, this laptop can use UEFI. If you want to use it, you need to a GPT partition (see below).

Also, this laptop can use UEFI. If you want to use it, you need to a GPT partition (see below).

Line 27:

Line 26:

===UEFI===

===UEFI===

−

UPDATE: Grub 1 is not officially supported anymore, so if you do a fresh install now, you will get Grub 2 automatically. Thus you should not completely trust the instructions below. They probably still work, but you may have to change one or two things.

+

Even thought its easier to switch from UEFI to legacy mode BIOS in this laptop and install Arch Linux on mSATA SSD and without disturbing factory installed windows 8 located on the HDD, this section will guide you to install Arch Linux with UEFI. UEFI is complicated and so proper understanding is advised before you start.

−

At this point, I am not sure whether UEFI is actually necessary, but it seems to be the future, so I do suggest that you set it up. First read these pages: https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface and https://wiki.archlinux.org/index.php/GRUB2.

Among other things, you need a gpt partition and grub2. You can do these things when you are installing the system, but I suggest that you get a base system working with grub first, and then install grub2. To install Arch on the SSD drive, you need at least two partitions: one small (100 MB) boot partition, and another partition for /. To partition the drives, you can use cgdisk, which you can get by installing the package gpttools.

+

Among other things, you need a gpt partition and grub2.

−

I suggest that you partition both drives using gpt, but it is even possible to convert a MBR partition table to gpt, which is what I ended up doing. You should also create a third partition (with about 1GB) for EFI. This partition needs to be of EFI system type (code ef00 on gdisk) and it should be formatted as FAT32. If the partition is /dev/sda2, use:

+

To install Arch on the SSD drive, you need at least two partitions: one small (100 MB) boot partition, and another partition for /. To partition the drives, you can use cgdisk, which you can get by installing the package gpttools.

+

+

You should also create a third partition (with about 1GB) for EFI. This partition needs to be of EFI system type (code ef00 on gdisk) and it should be formatted as FAT32. If the partition is /dev/sda2, use:

mkfs.vfat -F32 /dev/sda3

mkfs.vfat -F32 /dev/sda3

Line 70:

Line 71:

The code creates a directory /efi/boot in the flash drive, downloads the shell, copies it to /efi/boot and renames it as bootx64.efi. The shell is downloaded from the link given here: https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#UEFI_Shell. Note that you need a 2.0 shell, otherwise you will not be able to add an entry to the menu.

The code creates a directory /efi/boot in the flash drive, downloads the shell, copies it to /efi/boot and renames it as bootx64.efi. The shell is downloaded from the link given here: https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#UEFI_Shell. Note that you need a 2.0 shell, otherwise you will not be able to add an entry to the menu.

+

+

Note that it is also possible to simply place the UEFI shell in your UEFI system partition if you do not have a flash drive at hand:

This will cause the ideapad UEFI firmware to automatically add a new boot option named "EFI HDD Device" which will by default come first.

Now reboot, go to the BIOS (press F2), enable UEFI and exit, then press F12 and the flash drive should show up in the menu (you want to choose the UEFI entry). Now you should be in the UEFI shell. There is quite a lot that you can do, but be careful because a mistake can seriously compromise the machine. This guide may be worth looking at: http://software.intel.com/en-us/articles/uefi-shell/

Now reboot, go to the BIOS (press F2), enable UEFI and exit, then press F12 and the flash drive should show up in the menu (you want to choose the UEFI entry). Now you should be in the UEFI shell. There is quite a lot that you can do, but be careful because a mistake can seriously compromise the machine. This guide may be worth looking at: http://software.intel.com/en-us/articles/uefi-shell/

Line 93:

Line 101:

To avoid problems with the Arch install, put Windows on the second drive (this means that the second drive should also have a GUID partition table, since Windows 8 only works with one).

To avoid problems with the Arch install, put Windows on the second drive (this means that the second drive should also have a GUID partition table, since Windows 8 only works with one).

−

Windows 8 uses UEFI, so you can press F12 to choose between Arch and Windows, or just adjust this at the BIOS. Another option is to use the Windows program EasyBCD and add Arch to the Windows boot loader. However, I decided to add Windows to grub2.

+

Windows 8 uses UEFI, so you can press F12 to choose between Arch and Windows, or just adjust this at the BIOS. Another option is to use the Windows program EasyBCD and add Arch to the Windows boot loader. In this example, Windows is going to be added to grub2.

To do this, from Arch, mount the Windows system partition and find its UUID:

To do this, from Arch, mount the Windows system partition and find its UUID:

Line 127:

Line 135:

===NVIDIA Card===

===NVIDIA Card===

−

The Y580 uses NVIDIA's Optimus technology, which is not officially supported on Linux. A possible solution is to install Bumblebee (https://wiki.archlinux.org/index.php/Bumblebee) and to access the card with optirun. As far as I know, this currently does not work with the Y580. However, you can still use CUDA, which is good if you use apps like Blender or if, like me, you develop CUDA C programs.

+

The Y580 uses NVIDIA's Optimus technology, which is not officially supported on Linux. A possible solution is to install Bumblebee (https://wiki.archlinux.org/index.php/Bumblebee) and to access the card with optirun. It seems this currently does not work with the Y580. However, you can still use CUDA, which is good if you use apps like Blender or if you develop CUDA C programs.

−

Lenovo machines (Y470, Y570, Y580) require a hack: https://github.com/Bumblebee-Project/bbswitch/tree/hack-lenovo created by https://github.com/Lekensteyn (thanks to him for helping me to figure this out). Without this, the system cannot even see your card. To compile the acpi-handle-hack module and install it, use:

+

Lenovo machines (Y470, Y570, Y580) require a kernel patch for the correct acpi handling if you are using 3.7.X kernel. The modified PKGBUILD with sources are located [http://dl.dropbox.com/u/106654446/linux.tar.gz here ].

+

Kernel 3.8 will need a [https://patchwork.kernel.org/patch/1917651/ different patch] than what is linked above. There is proposal from kernel developer Rafael J. Wysocki for kernel 3.9 for a proper fix in the kernel tree. Until then patching the kernel is necessary.

Change your settings so that the module acpi-handle-hack is loaded automatically at boot. With the standard init system, add the module to your /etc/rc.conf file. If you are using systemd, add a file to your /etc/modules-load.d directory. The following command will do it:

+

2.[https://bugzilla.kernel.org/show_bug.cgi?id=42696 kernel bugzilla]

−

echo "acpi-handle-hack" > /etc/modules-load.d/nvidia.conf

+

3.[https://patchwork.kernel.org/patch/1917651/ patch for 3.8 kernel]

−

Any file with extension .conf will work (something like hack.conf, for example).

+

===Nvidia Bumblebee support===

+

In Linux currently [https://wiki.archlinux.org/index.php/Bumblebee bumblebee ] is the easiest option for a optimus like solution. For this laptop you will need a patched kernel as given in NVIDIA Card section, [https://aur.archlinux.org/packages/dkms-bbswitch/ dkms-bbswitch], [https://aur.archlinux.org/packages/nvidia-bumblebee/ bumblee-nvidia], [https://aur.archlinux.org/packages/nvidia-utils-bumblebee/ bumblebee-nvidia-utils] package all available from AUR. After installation of these packages you will need to add your user name to bumblebee group.You have to start the bumblebeed service manually. A short guide given here [https://wiki.archlinux.org/index.php/Bumblebee#Start_Bumblebee to start bumblebee]. After this setup you will have to edit the {{ic|/etc/bumblebee/xorg.conf.nvidia}} Device option "ConnectedMonitor". You will have to switch from "FDP" to "CRT-0".

+

Make sure nouvea is blacklisted.

===Driver===

===Driver===

−

To compile and run CUDA programs, you need a NVIDIA driver and the cuda-toolkit. Any driver with version 295.59 or higher will work, with the only exception being the 302.17 that never worked for me (and that unfortunately was the default one on Linux distros when I first wrote this guide).

+

To compile and run CUDA programs, you need a NVIDIA driver and the cuda-toolkit. Any driver with version 295.59 or higher will work.

−

+

{{Note: The only exception being the 302.17}}

−

As of 09/01/2012, the newest driver is 304.43. To install it, you need modified versions of two packages from extra, nvidia-utils and nvidia. The easiest way to do this is to install my packages nvidia-custom and nvidia-utils-custom from the AUR: https://aur.archlinux.org/packages.php?ID=60991, https://aur.archlinux.org/packages.php?ID=60991.

−

Alternatively, you can use ABS and patch the packages yourself.If you are not familiar with the process, read the wiki: https://wiki.archlinux.org/index.php/Arch_Build_System. The exact way to rebuild a package depends on your own preferences, but I usually download the source code (in this case, the driver, obtained here: ftp://download.nvidia.com/XFree86/Linux-x86_64/304.43/NVIDIA-Linux-x86_64-304.43-no-compat32.run, copy it to the build directory, and then run makepkg. after editing the PKGBUILD.. In the current case, since you need the driver for both packages, nvidia and nvidia-utils, this saves a bit of time.

+

As of 10/24/2012, the newest driver is 304.60. To install it, you need a modified version of the package nvidia-utils from extra. The easiest way to do this is to install the package nvidia-utils-custom from the AUR: https://aur.archlinux.org/packages.php?ID=60991.

−

Edit the PKGBUILD of nvidia-utils. You need to change the pkgver, the source item, and the md5sum. Also, nividia-utils conflicts with libgl, but if you uninstall libgl, Gnome only starts in fallback mode (not sure about other DE). Because of this, you need to modify the PKGBUILD, so that it either does not install certain libraries (libglx.so, libGL.so) or that it installs them in another location.

+

Alternatively, you can use ABS and patch the package yourself. If you are not familiar with the process, read the wiki: https://wiki.archlinux.org/index.php/Arch_Build_System. The exact way to rebuild a package depends on your own preferences, one way is to download the source code (in this case, the driver, obtained here: ftp://download.nvidia.com/XFree86/Linux-x86_64/304.60/NVIDIA-Linux-x86_64-304.60-no-compat32.run), copy it to the build directory, edit the PKGBUILD, and then run makepkg.

−

For the nvidia package, you need to change the pkgver to 295.59, the source, the md5sum and a few other items. After changing the PKGBUILDs, run makepkg to build the packages, and makepkg -is to install them (you need to install nvidia-utils first). The PKGBUILDs that I used are listed below:

+

Edit the PKGBUILD of nvidia-utils. You may need to change the pkgver, the source item, and the md5sum. The most important thing is that nvidia-utils conflicts with libgl, but if you uninstall libgl, Gnome only starts in fallback mode (not sure about other DE). Because of this, you need to modify the PKGBUILD, so that it either does not install certain libraries (libglx.so, libGL.so) or that it installs them in another location. With the PKGBUILD below, those libraries are not installed (note the commented lines for the GLX extension module, and the empty 'conflicts' line).

If you rebuild the packages yourself, you may want to make sure that the next update does not break your customization. One way to do this is to add the following line to your /etc/pacman.conf:

+

It is not necessary to patch other packages. If you want, you can also install nvidia-custom (https://aur.archlinux.org/packages.php?ID=60981) and opencl-nvidia-custom (https://aur.archlinux.org/packages.php?ID=61443) from the AUR, but they are not much different from the official ones (nvidia and opencl-nvidia from extra).

−

IgnorePkg = nvidia nvidia-utils

+

If you rebuild nvidia-utils yourself, you may want to add it to the IgnorePkg line of your /etc/pacman.conf, so that the next system update does not break your system.

−

−

Another approach is to rename the packages and make them conflict with the official ones (that is how my AUR packages were born).

===CUDA Toolkit===

===CUDA Toolkit===

−

Install the package from community. If that does not work, rebuild the package so that it uses the ubuntu11.04 version from NVIDIA's website. As before, this can be accomplished by first downloading the executable, copying it to the build directory, and changing the pkgver, source and md5sum entries of the PKGBUILD. In this case you need to edit a few other entries (the official package uses the fedora toolkit), but it should be easy. If you prefer, you can use the version below:

+

Install the package from community (https://www.archlinux.org/packages/community/x86_64/cuda/).

This is not necessary, but you may want to install the community package cuda-sdk:

+

The cuda package includes both the cuda-toolkit and sdk. Before testing it, reboot and it should be working. To compile and run deviceQuery from the sdk:

−

−

pacman -S cuda-sdk

−

−

The package is installed to /opt/cuda-sdk. To compile the CUDA C samples, use:

−

cd /opt/cuda-sdk/C

+

cd /opt/cuda/samples/1_Utilities/deviceQuery

make

make

−

+

./deviceQuery

−

Now reboot and CUDA should be working. To test it, run deviceQuery from the sdk:

−

−

/opt/cuda-sdk/C/bin/linux/release/deviceQuery

Alternatively, you can compile your own code and run it. To compile, say hello.cu, use:

Alternatively, you can compile your own code and run it. To compile, say hello.cu, use:

Line 458:

Line 353:

===Other Distributions===

===Other Distributions===

−

The above setup does not work only with Arch, and it may be even easier with other distros. For example, with Ubuntu 12.04 or Linux Mint 13, install the acpi-handle-hack module and then get the official nvidia-current (no need to patch it) package:

+

1.The above setup not only works only with Arch Linux and it may be even easier with other distros. For example, with Ubuntu 12.04 or Linux Mint 13, install the acpi-handle-hack module and then get the official nvidia-current (no need to patch it) package:

apt-get install nvidia-current

apt-get install nvidia-current

+

+

2. For Debian wheezy you shall need the lenovo-hack as described above and additional packages from [http://suwako.nomanga.net/ suwako repos] which has dkms-bbswtich bumblebee and bumblebee-nvidia.The easiest option is available from Debian. No need to blacklist anything.

+

+

3. For Fedora, RHEL 6.X series and its clones the external repos from [http://techies.ncsu.edu/wiki/bumblebee ncsu.edu] with installation of non-free nvidia from their non-free repos at [http://techies.ncsu.edu/wiki/bumblebee-nvidia bumblebee-nvidia] is necessary. Installing nvidia from rpmfusion shall break your X. You will have to edit the connected monitor section to "CRT-0" from "FDP" in Fedora 18. You will have to blacklist nouvea drivers at kernel command line to (xdriver=vesa nouveau.modeset=0 rd.driver.blacklist=nouveau).

+

+

4. Starting from 3.7.X kernel you will need to patch the kernel for proper acpi handling for any distro. For 3.9 linux kernel it may not be necessary.

Revision as of 16:19, 13 February 2013

The Lenovo IdeaPad Y580 started shipping in June 2012. It is a fairly powerful machine, but it has its own compatibility issues. The purpose of this article is to help with setting up Arch Linux on this machine.

Contents

Installation

Install Arch on the machine if you have not done it already. Read Installation Guide for more information.

If you cannot get wireless working, you can use an ethernet connection with the help of the driver alx. This driver is not yet part of the Linux kernel, and that is why your ethernet card is not recognized at first. The links from linux foundation doesn't build from sources for alx. Try this modified alx source files. This method works for current Feb 2013 Arch installation media for 3.7.x kernels.
This sources is found to work for both AR8161 and AR8162 ethernet devices.
Copy the tarball to a flash drive, boot the live cd, mount the flash drive, cd to the directory with the tarball and use:

After this, load the module (modprobe alx) and you should be able to get ethernet working easily.

The machine comes with Windows 7 and some Lenovo partitions that may be important if you need to recover the Windows install.

In case you don't need to restore the machine to their original state, you can just delete the existing partition. Other way, backup the partions before erasing them

Also, this laptop can use UEFI. If you want to use it, you need to a GPT partition (see below).

UEFI

Even thought its easier to switch from UEFI to legacy mode BIOS in this laptop and install Arch Linux on mSATA SSD and without disturbing factory installed windows 8 located on the HDD, this section will guide you to install Arch Linux with UEFI. UEFI is complicated and so proper understanding is advised before you start.

To install Arch on the SSD drive, you need at least two partitions: one small (100 MB) boot partition, and another partition for /. To partition the drives, you can use cgdisk, which you can get by installing the package gpttools.

You should also create a third partition (with about 1GB) for EFI. This partition needs to be of EFI system type (code ef00 on gdisk) and it should be formatted as FAT32. If the partition is /dev/sda2, use:

mkfs.vfat -F32 /dev/sda3

After you have your base system up and running, install the grub 2 firmware:

pacman -S grub2-efi-x86_64

Mount the system partition at /boot/efi:

mkdir /boot/efi
mount -t vfat /dev/sda3 /boot/efi

Install grub2 efi app (grubx64.efi) to /boot/efi/EFI/arch_grub, and its modules to /boot/efi/EFI/grub/x86_64-efi:

Now comes the part where the grub2 page is not very clear. You need to add the system to the UEFI menu (the menu that shows up when you press F12 at boot). To do this, you need an UEFI shell. The Y580 does not come with a shell built in, but you can put one in a flash drive and boot from it. To do this, get a bootable flash drive, create a partition (1GB is enough) and format it as FAT32. Assuming that the partition is /dev/sdc1, type the following:

This will cause the ideapad UEFI firmware to automatically add a new boot option named "EFI HDD Device" which will by default come first.

Now reboot, go to the BIOS (press F2), enable UEFI and exit, then press F12 and the flash drive should show up in the menu (you want to choose the UEFI entry). Now you should be in the UEFI shell. There is quite a lot that you can do, but be careful because a mistake can seriously compromise the machine. This guide may be worth looking at: http://software.intel.com/en-us/articles/uefi-shell/

For now, you just need the command bcfg. To add Arch to the first entry of the menu, use:

bcfg boot add 0 fs1:\EFI\arch_grub\grubx64.efi "Arch Linux"

The command assumes that the system partition is installed on the first drive. This partition has the loader (grubx64.efi) and this little program is what loads grub2. If you add Arch to the first entry, you can boot to it without pressing F12.

To see the menu entries, use:

bcfg boot dump -v

To delete, say the 3rd entry:

bcfg boot rm 3

Once you are happy with the menu entries, reboot and you should be able to boot into Arch.

Dual-Boot With Windows 8

To avoid problems with the Arch install, put Windows on the second drive (this means that the second drive should also have a GUID partition table, since Windows 8 only works with one).

Windows 8 uses UEFI, so you can press F12 to choose between Arch and Windows, or just adjust this at the BIOS. Another option is to use the Windows program EasyBCD and add Arch to the Windows boot loader. In this example, Windows is going to be added to grub2.

To do this, from Arch, mount the Windows system partition and find its UUID:

The Y580 has a huge 1TB second drive, making it easy to install other OS. With grub2, you can install other distros, and then run grub-mkconfig to add the new entry. To make this easier, install os-prober so that grub2 can find other OS automatically (it does not work for Windows 8):

pacman -S os-prober

NVIDIA Card

The Y580 uses NVIDIA's Optimus technology, which is not officially supported on Linux. A possible solution is to install Bumblebee (https://wiki.archlinux.org/index.php/Bumblebee) and to access the card with optirun. It seems this currently does not work with the Y580. However, you can still use CUDA, which is good if you use apps like Blender or if you develop CUDA C programs.

Lenovo machines (Y470, Y570, Y580) require a kernel patch for the correct acpi handling if you are using 3.7.X kernel. The modified PKGBUILD with sources are located here .
Kernel 3.8 will need a different patch than what is linked above. There is proposal from kernel developer Rafael J. Wysocki for kernel 3.9 for a proper fix in the kernel tree. Until then patching the kernel is necessary.

Nvidia Bumblebee support

In Linux currently bumblebee is the easiest option for a optimus like solution. For this laptop you will need a patched kernel as given in NVIDIA Card section, dkms-bbswitch, bumblee-nvidia, bumblebee-nvidia-utils package all available from AUR. After installation of these packages you will need to add your user name to bumblebee group.You have to start the bumblebeed service manually. A short guide given here to start bumblebee. After this setup you will have to edit the /etc/bumblebee/xorg.conf.nvidia Device option "ConnectedMonitor". You will have to switch from "FDP" to "CRT-0".
Make sure nouvea is blacklisted.

Driver

As of 10/24/2012, the newest driver is 304.60. To install it, you need a modified version of the package nvidia-utils from extra. The easiest way to do this is to install the package nvidia-utils-custom from the AUR: https://aur.archlinux.org/packages.php?ID=60991.

Edit the PKGBUILD of nvidia-utils. You may need to change the pkgver, the source item, and the md5sum. The most important thing is that nvidia-utils conflicts with libgl, but if you uninstall libgl, Gnome only starts in fallback mode (not sure about other DE). Because of this, you need to modify the PKGBUILD, so that it either does not install certain libraries (libglx.so, libGL.so) or that it installs them in another location. With the PKGBUILD below, those libraries are not installed (note the commented lines for the GLX extension module, and the empty 'conflicts' line).

CUDA Toolkit

Configurations

You need to load the acpi-handle-hack module first, then the nvidia module. Depending on your system, this may be enough, but it may be necessary to create devices for CUDA. One way to accomplish this is to add the following to your /etc/rc.local:

Testing it

The cuda package includes both the cuda-toolkit and sdk. Before testing it, reboot and it should be working. To compile and run deviceQuery from the sdk:

cd /opt/cuda/samples/1_Utilities/deviceQuery
make
./deviceQuery

Alternatively, you can compile your own code and run it. To compile, say hello.cu, use:

nvcc hello.cu

Now you can run the executable:

./a.out

If this works without errors, you are all set!

Other Distributions

1.The above setup not only works only with Arch Linux and it may be even easier with other distros. For example, with Ubuntu 12.04 or Linux Mint 13, install the acpi-handle-hack module and then get the official nvidia-current (no need to patch it) package:

apt-get install nvidia-current

2. For Debian wheezy you shall need the lenovo-hack as described above and additional packages from suwako repos which has dkms-bbswtich bumblebee and bumblebee-nvidia.The easiest option is available from Debian. No need to blacklist anything.

3. For Fedora, RHEL 6.X series and its clones the external repos from ncsu.edu with installation of non-free nvidia from their non-free repos at bumblebee-nvidia is necessary. Installing nvidia from rpmfusion shall break your X. You will have to edit the connected monitor section to "CRT-0" from "FDP" in Fedora 18. You will have to blacklist nouvea drivers at kernel command line to (xdriver=vesa nouveau.modeset=0 rd.driver.blacklist=nouveau).

4. Starting from 3.7.X kernel you will need to patch the kernel for proper acpi handling for any distro. For 3.9 linux kernel it may not be necessary.