Talk:ASUS Zenbook Prime UX31A

From ArchWiki
Latest comment: 18 January 2015 by Erkexzcx in topic Terminal commands for Function Keys

Clean up

I removed a lot of unnecessary information that only complicates things. For installation instructions simply look at the official Installation Guide. It is not needed to duplicate those information here. Legacy information are not needed. Who would run a new laptop with an old kernel? Since the newest kernels fix many problems we can remove these from this wiki page. Drenninghoff (talk)

Other function keys

I am writing from an UX31A with kernel 3.5.3-1-ARCH, and my function keys are not working out-of-the-box (except volume and display out). Is there any kernel module which is not mentioned in the text or is this information simply wrong?

Additionally the following info box says that since a newer kernel version a patch is no longer needed. A version that I don't need anyhow, because everything is supposed to work out-of-the-box. Seems a little bit contradictious...

  • "Working" means that you can see keycodes with xev when function keys are pressed. It does not means that — for example — when you press fn+f3 it will diminish keyboard luminosity : for that you must link the keycode to the functionality. I have the same kernel version than you and I can confirm you no longer needs the fix : All the keys except screen backlight are working. Bzhb (talk) 21:26, 31 August 2012 (UTC)Reply[reply]

Installation section

The additional information about encrypted partition is nice, but I think installation instructions should be more modular and better accomodate the different installation scenarios : standalone arch without encryption, arch with encryption, dual boot install keeping the original windows install...

So I think that all the additional steps about encryption should be clearly flagged at optional. Bzhb (talk) 10:12, 1 September 2012 (UTC)Reply[reply]

I completely agree Nihathrael (talk) 21:27, 14 September 2012 (UTC)Reply[reply]

HDMI Audio Sandbox

This is a sandbox for an HDMI Pulseaudio from the commandline module I'll move into the article once I have it right

HDMI Audio

The UX31A contains the following PCI souncard:

$ lspci -nnn -k | grep -i audio
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)

This device is capable of outputting both analog stereo (used to power the speaker and headphones) which uses the snd-audio-code-realtek module, and digital audio through the mini-hdmi port on the right side of the machine.

You will need the snd-hda-hdmi module:

$ lsmod | grep hda
snd_hda_codec_hdmi     21095  1 
snd_hda_codec_realtek    49734  1 
snd_hda_intel          22373  2 
snd_hda_codec          71565  3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_pcm                60543  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc          5921  2 snd_pcm,snd_hda_intel
snd_hwdep               5061  1 snd_hda_codec
snd                    48443  11 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel


Here is how udev sees plugging in the HDMI cable:

$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[96692.710767] change   /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)
UDEV  [96692.712940] change   /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)


To flip from analog (speakers/headphones) to digital (HDMI output), it is necessary to set the card's Pulseaudio profile.

Pulseaudio sees the soundcard as follows:

$ pacmd list-cards
Welcome to PulseAudio! Use "help" for usage information.
>>> 1 card(s) available.
    index: 0
	name: <alsa_card.pci-0000_00_1b.0>
	driver: <module-alsa-card.c>
	owner module: 4
		alsa.card = "0"
		alsa.card_name = "HDA Intel PCH"
		alsa.long_card_name = "HDA Intel PCH at 0xf7d18000 irq 47"
		alsa.driver_name = "snd_hda_intel"
		device.bus_path = "pci-0000:00:1b.0"
		sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0"
		device.bus = "pci" = "8086" = "Intel Corporation" = "7 Series/C210 Series Chipset Family High Definition Audio Controller"
		device.form_factor = "internal"
		device.string = "0"
		device.description = "Built-in Audio"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card-pci"
		output:analog-stereo: Analog Stereo Output (priority 6000)
		output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060)
		output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5400)
		output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5460)
		output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 300)
		output:hdmi-surround+input:analog-stereo: Digital Surround 5.1 (HDMI) Output + Analog Stereo Input (priority 360)
		input:analog-stereo: Analog Stereo Input (priority 60)
		off: Off (priority 0)
	active profile: <output:hdmi-stereo>
	sinks:To flip from analog (speakers/headphones) to digital (HDMI output), it is necessary to set the card's Pulseaudio profile. 
		alsa_output.pci-0000_00_1b.0.hdmi-stereo/#18: Built-in Audio Digital Stereo (HDMI)
		alsa_output.pci-0000_00_1b.0.hdmi-stereo.monitor/#19: Monitor of Built-in Audio Digital Stereo (HDMI)
		analog-output-speaker: Speakers (priority 10000, available: unknown)
		analog-output-headphones: Headphones (priority 9000, available: no)
		analog-input: Analog Input (priority 10000, available: unknown)
		analog-input-microphone: Microphone (priority 8700, available: unknown)
		hdmi-output-0: HDMI / DisplayPort (priority 5900, available: no)

The two important pieces of information here are the card's number ("index: 0") and the profiles for analog and HDMI digital stereo (output:analog-stereo and output:hdmi-stereo).

To change the profile, one can use the pactl command:

$ pacmd list-cards | grep "active profile"
	 active profile: <output:analog-stereo>
$ pactl set-card-profile 0 output:hdmi-stereo
$ pacmd list-cards | grep "active profile"
	active profile: <output:hdmi-stereo>

Terminal commands for Function Keys

Would it be useful to add to this table ASUS Zenbook Prime UX31A#Function keys
one more column with suggested terminal commands for the functions needing shortcuts?
I found them extremely useful in openbox, but not always easy to find.
Fn+F1 pm-suspend
Fn+F3 asus-kbd-backlight down
Fn-F4 asus-kbd-backlight up
Fn+F10 amixer sset Master toggle
Fn+F11 amixer sset Master 2dB-
Fn+F12 amixer sset Master 2dB+

[My first attempt at contributing to this Arch wiki]

First, this is not really necessarily, because it is not this hardware related :) -- Erkexzcx (talk) 22:10, 18 January 2015 (UTC)Reply[reply]

Backlight Issues/Cleanup

I had a good deal of trouble trying to get my backlight (keyboard and screen) working properly without AUR packages. Most of my trouble is documented in this post and I wanted to confirm with others to see if adding the Option "Backlight" "intel_backlight" line worked for other people (instead of the boot parameter acpi_osi="!Windows 2012") before adding it to the wiki. If it does, I propose we remove all those AUR package work-arounds because they needn't be necessary. Suggestions welcome, this is my first attempt to contribute to Arch's wonderful wiki. 0xtobit (talk)

That never worked for me, but as of late, I have working FN5+FN6 keys simply with using acpi_osi=intel. --Graydsl (talk) 09:44, 23 October 2013 (UTC)Reply[reply]

acpi_osi="!Windows 2012" has worked perfectly fine for me, Fn5+Fn6 and everything, that's why it's actually the default in Linux 3.12, you don't need that boot option any more. The intel_backlight will eventually be used by default, but not at the moment, so if you want to play along, we should tackle the issues with acpi_osi="!Windows 2012" first. As I said I don't have any problems with it, what problem do you have? Also it should mostly work without any option in Linux 3.11. -- FelipeC (talk) 14:18, 5 November 2013 (UTC)Reply[reply]

KDE and layouts

Hi. does anyone have any problems with layouts switching on KDE Desktop Environment? I use US and LT layouts, but seems that KDE doesn't switch layout to LT when I set to use it on ASUS N550JV laptop - shows that LT is currently active but still acts like it's US active. I am trying to figure out whether this is KDE problem or specific laptop problem. :P -- Erkexzcx (talk) 22:09, 18 January 2015 (UTC)Reply[reply]