So I have ZorinOS installed on my ASUS ZenBook UX330UA-AH54, however, FingerprintGUI shows my fingerprint sensor (Elantech I think) as an unknown device. Is there any custom software or fixes that can be used to get my laptop to pickup the fingerprint sensor?

I have Arch and Asus zenbook ux431f with i7 and nvidia mx150. After install -> blank screen on my laptop monitor but hdmi monitor works. After many researches i've found this https://github.com/johnBerd/asus-blackscreen , and the result is the opposite -> blank hdmi monitor and internal laptop monitor works. I tried also popos, ubuntu and centos. The problem is not the distro. It's possible to have both monitor work?

I have an ASUS Zenbook UX433,on which ASUS decided to innovate by embedding a Numpad inside the touchpad (see picture ). Toggling between classic touchpad mode and numpad (also turns the touchpad LEDs on) can be done through the golden button in the top-right corner of the touchpad. However, on my Manjaro arch Linux config, this behavior does not work by default and I can only use the touchpad, no numpad. **Has anyone been able to configure the numpad to work on Linux, or have any idea how this could be achieved?** EDIT1: I have had a look at the [official Windows drivers for the UX433FA TouchPad](https://dlcdnets.asus.com/pub/ASUS/nb/DriversForWin10/TouchPad/Touchpad_ASUS_Win10_64_VER120014.zip) , but was not able to make anything of it. I tried installing them on Linux using tools like NDISWrapper, but they do not detect the TouchPad/Numpad hardware, and my understanding of drivers is too limited.

I am starting a new thread after one called "Debian 9 XFCE fresh install, nothing but wallpaper after login", because I misidentified the issue I was facing at first, as being related to the installation process, and, as it turns out it is more of a nvidia driver issue. I already made a few attempts to get the drivers to work, and I will describe what I observed here hoping someone will be able to make sense of it. To sum it up, after installing debian 9 on my Asus zenbook ux501 I was logging into a frozen system displaying a wallpaper, with no commands available at all. Once in while I would be able to log in into a normal Xfce session, and could not figure out why, but, when I could, the "lspci" command would just hang with no output as well as any attempt to install bumblebee, or nvidia drivers. My grapic card is Nvidia geforce gtx 960m, with Intel i7 processor. The InstallingDebianOn page about my laptop allowed me to boot reliably into a functioning system by changing the grub settings as follows: GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_osi=! acpi_osi=Linux acpi_backlight=native" Now, I can run lspci which outputs: > lspci -k | grep -iEA5 'vga|3d|display' > > > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 > (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 Kernel > driver in use: i915 Kernel modules: i915 00:04.0 Signal processing > controller: Intel Corporation Skylake Processor Thermal Subsystem (rev > 07) Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal > Subsystem > -- 01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2) Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] > Kernel driver in use: nouveau Kernel modules: nouveau 02:00.0 > Unassigned class [ff00]: Alcor Micro Device 6621 Subsystem: Alcor > Micro Device 6621 > -- 3d:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller (rev 01) Subsystem: Samsung Electronics Co Ltd > NVMe SSD Controller Kernel driver in use: nvme Kernel modules: nvme It also allowed me to successfully follow all the steps described in this tutorial about how to make optimus work on debian up untill the last command that just hangs for ever: > service bumblebeed restart Also note that the first check for nouveau drivers yields expected results, but the second about vga_switcheroo does not output anything.. > sudo modprobe -r nouveau > sudo modprobe -r vga_switcheroo A forced reboot gets me to a black screen with a block a error messages that I cannot remember as it was a few days ago, but no command available, I could not find any way to interact with the system. So I did a new clean install.. I do not understand much about "acpi" settings in the grub configuration, but the installation instructions for installing bumblebee on Debian I followed has a troubleshooting section where they recommend a different grub configuration for acpi_backlight with "=vendor" instead of the "=native" I previously set in order to be able to boot into the xfce session. Is the problem here? Should I update the grub configuration , and reboot instead of issuing "service bumblebeed restart" ? I had also previously tried this debian guide with no success. However, it was before finding out the tips about the grub config that fixed my log in primary issue.. Should I try it again?

**The System** This is a brand-new ASUS Zenbook UX430UAR dual booting the pre-installed Windows 10 and a minimal Debian, uname -a: Linux myhostname 4.9.0-7-amd64 #1 SMP Debian 4.9.110-3+deb9u2 (2018-08-13) x86_64 GNU/Linux **The Problem** When the touchpad (motion and tap) has been idle for about one second (definitely less than two), the next tap is ignored. The motion response also lags noticeably after being idle, and it seems that the longer I am idle, the more pronounced it is. The motion lag disappears after a moment of use. **Why It's A Problem** This is a bad situation because in order to safely execute a single click by tapping, you must wait at least one second, then double-tap. You can't just double-tap as a rule, since if there was a motion event within one second of the double-tap, it will be registered as two clicks. Or you could just single tap as a rule, and hope for visual feedback to tell you whether the tap worked or not. If it takes you more than one second to evaluate the visual feedback, the cycle will be repeated! **What I've Tried**

• I've scoured about two dozen pages for ideas
• "libinput Disable While Typing Enabled" was 1 by default, but I have set it 0 via xorg.conf.d and the setting does persist across reboots
• I tried various things to disable USB autosuspend, including disabling autosuspend on all devices using the "usbcore.autosuspend=-1" and/or "usbcore.autosuspend_delay_ms" kernel boot options -- these seem to take effect, to judge by the /sys/bus/usb/devices/*/power/autosuspend files, after rebooting. (I've removed the boot option now.)
• I ensured that none of the following are installed, since they are known to interfere with manual power management configuration: laptop-mode, powertop, pm-utils, tlp
• I tried installing the xserver-xorg-input-synaptics but libinput continued to be used (and I dare not remove libinput lest I be left without a keyboard)
• I tried two different window managers (my own hack of twm that I normally use, as well as stock fluxbox)

Unfortunately nothing I've tried has influenced this touchpad misbehaviour in any perceptible way. Is there some device file I could echo to in a once-per-second loop to keep the touchpad from being idle, yet without triggering actual events on the desktop? (This is probably what I'll try next, as I await answers or comments.) Can anyone suggest something else to test or try, so that the touchpad is as responsive after being idle as it is in the heat of action? These are popular notebooks and a pretty good value, so a solution to this stands to benefit many.

I'm using Debian 8, but my integrated graphics card does not seem to be used. This is on an Asus Zenbook UX303 which uses HD 5500 integrated graphics: $ sudo lspci -vnn | grep VGA -A 12 00:02.0 VGA compatible controller : Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:183d] Flags: bus master, fast devsel, latency 0, IRQ 64 Memory at f6000000 (64-bit, non-prefetchable) [size=16M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at [disabled] Capabilities: MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 It seems to say there is a driver in use, however, it doesn't seem the machine is actually using that graphics card: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 256 bits) OpenGL version string: 3.0 Mesa 10.3.2 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: **How do I get debian to actually use the integrated graphics card?** $ uname -a Linux zenbook 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) x86_64 GNU/Linux I've also tried the 4.0.2 kernel from unstable, which doesn't change anything; uname: $ uname -a Linux zenbook 4.0.0-1-amd64 #1 SMP Debian 4.0.2-1 (2015-05-11) x86_64 GNU/Linux

I tried to record the bug related to my typing but could not get Kazam work as root and as non-root, see following; I installed it by apt-get install kazam ffmpeg successfully but not properly because of the errors/warnings root@masi:/home/masi# kazam Traceback (most recent call last): File "/usr/bin/kazam", line 127, in bus = dbus.SessionBus() File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 211, in __new__ mainloop=mainloop) File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 100, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib/python3/dist-packages/dbus/bus.py", line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. root@masi:/home/masi# exit exit masi@masi:~$ kazam /usr/lib/python3/dist-packages/kazam/app.py:145: Warning: value "((GtkIconSize) 32)" of type 'GtkIconSize' is invalid or out of range for property 'icon-size' of type 'GtkIconSize' self.builder.add_from_file(os.path.join(prefs.datadir, "ui", "kazam.ui")) (kazam:5260): Gtk-WARNING **: Symbolic icon kazam-screencast-symbolic of size 24 is in an icon theme directory of size 16 (kazam:5260): Gtk-WARNING **: Symbolic icon kazam-screenshot-symbolic of size 24 is in an icon theme directory of size 16 (kazam:5260): Gtk-WARNING **: Can't set a parent on widget which has a parent (kazam:5260): Gtk-WARNING **: Symbolic icon kazam-fullscreen-symbolic of size 24 is in an icon theme directory of size 16 (kazam:5260): Gtk-WARNING **: Symbolic icon kazam-all-screens-symbolic of size 24 is in an icon theme directory of size 16 (kazam:5260): Gtk-WARNING **: Symbolic icon kazam-window-symbolic of size 24 is in an icon theme directory of size 16 (kazam:5260): Gtk-WARNING **: Symbolic icon kazam-area-symbolic of size 24 is in an icon theme directory of size 16 (kazam:5260): Gtk-WARNING **: Can't set a parent on widget which has a parent I did as root apt-get update and apt-get upgrade after that and iterated again but the problem persists. Debugging --- I run kazam --debug and get masi@masi:~$ kazam --debug DEBUG Kazam - Starting ... DEBUG Kazam - Running on: debian 8.5 DEBUG Kazam - Kazam version: 1.4.5 NCC-80102 DEBUG Kazam - Starting new instance ... DEBUG Prefs - XDG_PICTURES is a directory and accessible DEBUG Prefs-HW - Getting hardware specs DEBUG Prefs-HW - Getting Video sources. DEBUG Prefs-HW - Found 1 monitor(s). DEBUG Prefs-HW - Monitor 0 - X: 0, Y: 0, W: 1920, H: 1080 DEBUG Main - Gstreamer version detected: 1.4.4.0 DEBUG Main - Setting variables. DEBUG PulseAudio - Starting mainloop. DEBUG PulseAudio - Getting API. DEBUG PulseAudio - Setting context. DEBUG PulseAudio - Set state callback. DEBUG PulseAudio - Connecting to server. DEBUG PulseAudio - Start mainloop. DEBUG PulseAudio - State connected. DEBUG Main - Connecting indicator signals. DEBUG Main - Starting in silent mode: False DEBUG Indicator - Indicatior silent: False DEBUG Indicator - Trying to bind hotkeys. DEBUG Main - Main Window UI setup. /usr/lib/python3/dist-packages/kazam/app.py:145: Warning: value "((GtkIconSize) 32)" of type 'GtkIconSize' is invalid or out of range for property 'icon-size' of type 'GtkIconSize' self.builder.add_from_file(os.path.join(prefs.datadir, "ui", "kazam.ui")) DEBUG Main - Unable to get name for '' (kazam:3222): Gtk-WARNING **: Symbolic icon kazam-screencast-symbolic of size 24 is in an icon theme directory of size 16 (kazam:3222): Gtk-WARNING **: Symbolic icon kazam-screenshot-symbolic of size 24 is in an icon theme directory of size 16 (kazam:3222): Gtk-WARNING **: Can't set a parent on widget which has a parent (kazam:3222): Gtk-WARNING **: Symbolic icon kazam-fullscreen-symbolic of size 24 is in an icon theme directory of size 16 (kazam:3222): Gtk-WARNING **: Symbolic icon kazam-all-screens-symbolic of size 24 is in an icon theme directory of size 16 (kazam:3222): Gtk-WARNING **: Symbolic icon kazam-window-symbolic of size 24 is in an icon theme directory of size 16 (kazam:3222): Gtk-WARNING **: Symbolic icon kazam-area-symbolic of size 24 is in an icon theme directory of size 16 (kazam:3222): Gtk-WARNING **: Can't set a parent on widget which has a parent DEBUG Prefs - Getting Audio sources. DEBUG PulseAudio - get_audio_sources() called. DEBUG PulseAudio - pa_sourcelist_cb() DEBUG PulseAudio - IDX: 0 DEBUG PulseAudio - Name: b'alsa_output.pci-0000_00_1f.3.analog-stereo.monitor' DEBUG PulseAudio - Desc: b'Monitor of Built-in Audio Analog Stereo' DEBUG PulseAudio - pa_sourcelist_cb() DEBUG PulseAudio - IDX: 1 DEBUG PulseAudio - Name: b'alsa_input.pci-0000_00_1f.3.analog-stereo' DEBUG PulseAudio - Desc: b'Built-in Audio Analog Stereo' DEBUG PulseAudio - pa_sourcelist_cb() -- finished DEBUG Prefs - Device found: DEBUG Prefs - - 0 DEBUG Prefs - - alsa_output.pci-0000_00_1f.3.analog-stereo.monitor DEBUG Prefs - - Monitor of Built-in Audio Analog Stereo DEBUG Prefs - Device found: DEBUG Prefs - - 1 DEBUG Prefs - - alsa_input.pci-0000_00_1f.3.analog-stereo DEBUG Prefs - - Built-in Audio Analog Stereo DEBUG Main - Capture cursor: True. DEBUG Main - Capture cursor_pic: True. DEBUG Main - Capture borders_pic: True. Testing GAD3R's proposal --- I run apt-get build-dep kazam successfully, then again kazam but get the similar warnings/errors still /usr/lib/python3/dist-packages/kazam/app.py:145: Warning: value "((GtkIconSize) 32)" of type 'GtkIconSize' is invalid or out of range for property 'icon-size' of type 'GtkIconSize' self.builder.add_from_file(os.path.join(prefs.datadir, "ui", "kazam.ui")) (kazam:15470): Gtk-WARNING **: Symbolic icon kazam-screencast-symbolic of size 24 is in an icon theme directory of size 16 (kazam:15470): Gtk-WARNING **: Symbolic icon kazam-screenshot-symbolic of size 24 is in an icon theme directory of size 16 (kazam:15470): Gtk-WARNING **: Can't set a parent on widget which has a parent (kazam:15470): Gtk-WARNING **: Symbolic icon kazam-fullscreen-symbolic of size 24 is in an icon theme directory of size 16 (kazam:15470): Gtk-WARNING **: Symbolic icon kazam-all-screens-symbolic of size 24 is in an icon theme directory of size 16 (kazam:15470): Gtk-WARNING **: Symbolic icon kazam-window-symbolic of size 24 is in an icon theme directory of size 16 (kazam:15470): Gtk-WARNING **: Symbolic icon kazam-area-symbolic of size 24 is in an icon theme directory of size 16 (kazam:15470): Gtk-WARNING **: Can't set a parent on widget which has a parent I think this may be the problem that Kazam wants python3 but I have python 2.7.9 (python --version gives Python 2.7.9), so there can be a missing dependency. How to proceed? Hardware: Asus Zenbook UX303UA OS: Debian 8.5 Linux kernel: 4.6 (backports' one) Graphics: modesetting and non-free package for skylake CPU support Case in Kazam suppot: https://answers.launchpad.net/kazam/+question/378875

- Initial condition: brightness-control buttons do not work, no animation of brightness-control not seen on actions, but manual control of brightness work in Settings and at the top-bar. - Condition after test code 1: brightness-control buttons do not affect brightness but visual animation is shown after reboot; however, now, the manual control of brightness do not work anymore so the solution which works in Ubuntu does not work in Debian. - I have tried here both GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=" and GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_osi=" in /etc/default/grub unsuccessfully, where the option without splash is the default setting in Debian, in contrast to Ubuntu. The complete default option is only with quiet in Debian. Differential solutions --- 1. Use defaults. Undo changes of Test code 1. Weakness: brightness keys do not work but you can control brightness from the top-bar. 2. ? Test code 1 --- I can fix the brightness-control buttons (fn+f5, fn+f6 for brightness decrease and increase, respectively) in Ubuntu 16.04 as described in the thread How to Enable Brightness Buttons when acpi_osi of Grub not enough in 16.04 of Zenbook? but not in Debian 8.5. There is no directory /usr/share/xorg.conf.d/ in Debian, in contrast to Ubuntu, so possibly similar work flow does not work in Debian. Main points done in the following work flow in Debian 1. Add code in /etc/default/grub # guillaume-desclaux https://ubuntuforums.org/showthread.php?t=2243162 GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=" # I also tried here without splash, since it did # not exist by default in Debian, in contrast to Ubuntu. 2. Create directory /usr/share/xorg.conf.d/ 3. Add the following content in the file /usr/share/xorg.conf.d/20-intel.conf # https://askubuntu.com/a/536618/25388 Section "Device" Identifier "card0" Driver "intel" Option "Backlight" "intel_backlight" BusID "PCI:0:2:0" EndSection 4. Run as root update-grub My work flow in Debian root@masi:/home/masi# vim /etc/default/grub root@masi:/home/masi# vim /usr/share/x xfig/ xml/ xml-core/ xsessions/ root@masi:/home/masi# mkdir /usr/share/xorg.conf.d/ root@masi:/home/masi# vim /usr/share/xorg.conf.d/20-intel.conf root@masi:/home/masi# sudo update-grub bash: sudo: command not found root@masi:/home/masi# update-grub Generating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-4.6.0-0.bpo.1-amd64 Found initrd image: /boot/initrd.img-4.6.0-0.bpo.1-amd64 Found linux image: /boot/vmlinuz-3.16.0-4-amd64 Found initrd image: /boot/initrd.img-3.16.0-4-amd64 Adding boot menu entry for EFI firmware configuration done root@masi:/home/masi# Output: brightness keys not working after reboot; you now see the visual effect but no effect; after the changes, the brightness control also break if you try to manually change it. Hardware: Asus Zenbook UX303UA OS: Debian 8.5 64 bit Linux kernel 4.6

Examples of Alsa warnings got by many applications (etc Matlab 2016a), which naturally appear in many applications but which differentiation into important and non-important ones has been difficult for me; I keep all warnings important, once I get them so I really would like to silent non-important warnings ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map MathWorks' support service proposes to silent the warnings by Alsa config file /etc/asound.conf. However, I disagree with their policies of giving such warnings in the first place i.e. calling the function audiodevinfo each time when calling sound/soundsc/audioplayer/audiorecorder commands in Matlab 2016a. So I would like to understand how it is good to silent those warnings such that you do not miss any critical piece of information. Open - ignorance - application specific - ... Characteristics of the system - root@masi:/home/masi# less /proc/asound/cards 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf128000 irq 127 Rejected proposals --- 1. Edit /usr/share/alsa/alsa.conf and change # https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=129648 pcm.front cards.pcm.default # original pcm.front cards.pcm.front but issue with Matlab 2. Restart pulse pulseaudio -k 3. Output: unsuccessful, the errors keep coming Matlab 2016a's part --- Answer from MathWork's tech support > These warnings are generated when you execute the "audiodevinfo" function for the first time which is called internally when you execute the "sound/soundsc/audioplayer/audiorecorder" commands. The "audiodevinfo" tries to enumerate all the devices on the system. > > The warnings are generated by the ALSA system libraries and it does not affect the behavior of MATLAB. The cause of this issue is not related to MATLAB. I would like to suggest you to take a look at the ALSA config files such as "/etc/asound.conf" to resolve the warning messages. However, assisting you with editing the ALSA config files would be outside the scope of our Technical Support. I think Matlab should design their product such that you do not get those warnings. It can a mark of bad design if you call such an info function from another function. How to proceed with the design of /etc/asound.conf? Hardware: Asus Zenbook UX303UA OS: Debian 8.5 Linux kernel: 4.6 (backports) Matlab: 2016a, 2016b prerelease Related: How to Configure ALSA in Ubuntu 16.04 for Macbook and Matlab? but for Ubuntu 16.04

I am having too many artifacts when doing right click (second click) of mouse with the touchpad of UX303UA in Debian 8.5, which is problematic in inspection etc with Mathematica. **Goal to fix**: Default Shift+fn+f10 to bring the mouse second click does not work in my hardware (don_crissti) Characteristics of the system - Inspecting the keystroke Shift+fn+f10 with xev KeyPress event, serial 33, synthetic NO, window 0x2200001, root 0x19a, subw 0x0, time 60929622, (375,-9), root:(476,157), state 0x0, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 36, synthetic NO, window 0x2200001, root 0x19a, subw 0x0, time 60931790, (375,-9), root:(476,157), state 0x1, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 36, synthetic NO, window 0x2200001, root 0x19a, subw 0x0, time 60931880, (375,-9), root:(476,157), state 0x1, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False - *Settings > Mouse & Touchpad* does not have anything relevant about fn keys. Fig. 1 Pressing literally fn+F10 opens a tab in Google Chrome/Matlab/...; while pressing fn+shift+F10 does nothing OS: Debian 8.5 Window manager: Gnome 3.14 Hardware: Asus Zenbook UX303UA Linux kernel: 4.6 of backports Mathematica: 11

Trying to install a linux distro (CentOS/Ubuntu) on ASUS ZenBook Pro UX501VW-DS71T fails so far. I've used bootable usb, created by pendrive/unetbootin from range of iso files (centos-minimal/ubuntu-desktop/ubuntu-live). In CentOS setup menu, I have tried troubleshooting & selecting basic graphic mode. I also tried text mode. Booting process stops at some point and dracut terminal appears. I have copied dmesg , journalctl , rdsosreport . With ubuntu-live, it brings up the busybox built-in shell with the following prompt: > (initramfs) Unable to find a medium containing a live file system Any idea could help.

Situation: to improve the power management of the zenbook when I need computation power, especially when the zenbook is in AC I am experimenting about 3 hour battery life without any computation, without any firmware failures/issues and just typing in Stackexchange network in my new UX303UA. Expected battery time is up to 7 hours, here its Asus website. Arch Linux wiki confirms in the same series ultrabook > Battery has a design capacity of 4429mAh, and is able to provide just over 3 hours of autonomy under normal circumstances (average load of around 0.3 and WiFi enabled, brightness lowered to mid-range) without serious power saving tweaks. - - ACPI tools are able to correctly detect the battery state. They recommend Laptop mode tools , which I will be testing 1. apt-get install laptop-mode-tools 2. Enable laptop-mode.service, where the following command should return 2 cat /proc/sys/vm/laptop_mode 3. Actually, I do not understand why they propose to change to the laptop mode to 1 where I would like to keep 0 when in AC because I need power in computations # http://askubuntu.com/questions/180712/how-to-enable-laptop-mode # edit /etc/laptop-mode/laptop-mode.conf` ENABLE_LAPTOP_MODE_ON_AC=1 # where I want to have zero. Why they propose 1? 4. Restart laptop-mode as root by /etc/init.d/laptop-mode restart Default power saving states found by grep -command root@masi:/home/masi# grep -r '^\(CONTROL\|ENABLE\)_' /etc/laptop-mode/conf.d/etc/laptop-mode/conf.d/intel-sata-powermgmt.conf:CONTROL_INTEL_SATA_POWER="auto" /etc/laptop-mode/conf.d/radeon-dpm.conf:CONTROL_RADEON_DPM="auto" /etc/laptop-mode/conf.d/sched-smt-power-savings.conf:CONTROL_SCHED_SMT_POWER_SAVINGS="auto" /etc/laptop-mode/conf.d/start-stop-programs.conf:CONTROL_START_STOP=1 /etc/laptop-mode/conf.d/wireless-power.conf:CONTROL_WIRELESS_POWER_SAVING="auto" /etc/laptop-mode/conf.d/intel_pstate.conf:CONTROL_INTEL_PSTATE="auto" /etc/laptop-mode/conf.d/dpms-standby.conf:CONTROL_DPMS_STANDBY="auto" /etc/laptop-mode/conf.d/nmi-watchdog.conf:CONTROL_NMI_WATCHDOG="auto" /etc/laptop-mode/conf.d/sched-mc-power-savings.conf:CONTROL_SCHED_MC_POWER_SAVINGS="auto" /etc/laptop-mode/conf.d/intel-hda-powersave.conf:CONTROL_INTEL_HDA_POWER="auto" /etc/laptop-mode/conf.d/pcie-aspm.conf:CONTROL_PCIE_ASPM="auto" /etc/laptop-mode/conf.d/auto-hibernate.conf:ENABLE_AUTO_HIBERNATION=0 /etc/laptop-mode/conf.d/wireless-iwl-power.conf:CONTROL_IWL_POWER="auto" /etc/laptop-mode/conf.d/exec-commands.conf:CONTROL_EXEC_COMMANDS="auto" /etc/laptop-mode/conf.d/hal-polling.conf:CONTROL_HAL_POLLING="auto" /etc/laptop-mode/conf.d/ethernet.conf:CONTROL_ETHERNET="auto" /etc/laptop-mode/conf.d/runtime-pm.conf:CONTROL_RUNTIME_AUTOSUSPEND=1 /etc/laptop-mode/conf.d/configuration-file-control.conf:CONTROL_CONFIG_FILES=0 /etc/laptop-mode/conf.d/ac97-powersave.conf:CONTROL_AC97_POWER="auto" /etc/laptop-mode/conf.d/eee-superhe.conf:CONTROL_SUPERHE="auto" /etc/laptop-mode/conf.d/lcd-brightness.conf:CONTROL_BRIGHTNESS=0 /etc/laptop-mode/conf.d/terminal-blanking.conf:CONTROL_TERMINAL="auto" /etc/laptop-mode/conf.d/bluetooth.conf:CONTROL_BLUETOOTH=0 /etc/laptop-mode/conf.d/cpufreq.conf:CONTROL_CPU_FREQUENCY="auto" /etc/laptop-mode/conf.d/cpufreq.conf:CONTROL_CPU_THROTTLING=0 /etc/laptop-mode/conf.d/wireless-ipw-power.conf:CONTROL_IPW_POWER="auto" /etc/laptop-mode/conf.d/video-out.conf:CONTROL_VIDEO_OUTPUTS=0 /etc/laptop-mode/conf.d/battery-level-polling.conf:ENABLE_BATTERY_LEVEL_POLLING=0 I am not sure which files are relevant in the power management in the directory etc/laptop-mode/conf.d/, etc many authors ignore ac97-powersave.conf - - why? Iterating GAD3R's answer --- Installing the package (apt-get install laptop-mode-tools), rebooting and having just the default power options leads to significant increase in battery time. The 25% of battery is now about 2h 15 minutes -use so 100% of battery is about 10 hours of use i.e. about 3.5 times more battery time. There are only a few options off in the settings' file where I cannot find anything relevant to turn on root@masi:/home/masi# grep =0 /etc/laptop-mode/laptop-mode.conf # CONTROL_something=0/1 Determines whether Laptop Mode Tools controls VERBOSE_OUTPUT=0 DEBUG=0 ENABLE_LAPTOP_MODE_ON_AC=0 ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=0 DISABLE_BATTERY_ALARM_CHECK=0 CONTROL_NOATIME=0 CONTROL_HD_WRITECACHE=0 NOLM_BATT_HD_WRITECACHE=0 LM_HD_WRITECACHE=0 I do not want to change defaults much. Which settings would you change to accomplish the significant improvement in the power management? Hardware: Asus Zenbook UX303UA OS: Debian 8.5 64 bit Firmwares: updated and/or installed as described in the thread How Smooth is Upgrading Linux kernel in Debian 8.5? Linux kernel: 4.6 of backports Related: ASUS Zenbook UX303 in Arch Linux Other Asus Zenbooks of 2nd gen: UX301LA

Situation: I have only Debian 8.5 in my system without Windows 10, and I would like to update the Bios of Zenbook UX303UA R4028T Options 1. Update bios with Debian i.e. do the flashing somehow, since no code exists for it. 2. Install Windows-10 alongside the Debian installation, and update the bios with Windows 10 with the official software. Solving the thing with official Asus chat --- They point me to the thread here where you see that you need the flash utility to the update on Windows. However, I am still unsure how to replace it for Debian or if you can do the update directly in Bios. So there are only updates in Windows 10 section of the manufacturer here . 1. BIOS 208 Description BIOS 208 Update FW File Size 2.48 MBytesupdate 2016/05/05 2. Windows BIOS Flash Utility - not sure what to do with this - - TODO? BIOS-Utilities (1) Version V3.0.1 Description Windows BIOS Flash Utility File Size 888.63 KBytes 2015/08/14 update After Stephen's answer --- Final result: Bios was the latest (updated already on April 2016 to 208) which I saw in Easy Boot [Stephen], so I did not need to update. I just wonder why Asus support did not have proper knowledge of Bios update in Linux, and about Bios states in different systems when serial is known. Hardware: Asus Zenbook UX303UA R4028T OS: Debian 8.5 64 bit Linux kernel: 4.6 Keywords: bios firmware upgrade asus ux303ua R4028T download

This answer motivates me to find missing firmwares in my ultrabook, because I am experiencing difficult typing with many artifacts (here about unable to calibrate typing speed) and CPU up-downs now in one-day old Debian 8.5 with Dvorak. Stephen says that the kernel packages can tell you about missing firmware whenever they are installed or upgraded. However, I would like to get more complete review on it. Characteristics - Graphics lspci -nnk | egrep -iA3 "VGA" 00:02.0 VGA compatible controller : Intel Corporation Device [8086:1916] (rev 07) Subsystem: ASUSTeK Computer Inc. Device [1043:247a] Kernel driver in use: i915 00:04.0 Signal processing controller : Intel Corporation Device [8086:1903] (rev 08) - About failed firmwares where iwlwifi are old messages, I think masi@masi:~$ dmesg | grep firmware [ 1.878929] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-7265D-21.ucode (-2) [ 1.878967] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-21.ucode failed with error -2 [ 1.878985] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-7265D-20.ucode (-2) [ 1.879016] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-20.ucode failed with error -2 [ 1.879027] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-7265D-19.ucode (-2) [ 1.879060] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-19.ucode failed with error -2 [ 1.879070] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-7265D-18.ucode (-2) [ 1.879101] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-18.ucode failed with error -2 [ 1.879111] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-7265D-17.ucode (-2) [ 1.879142] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-17.ucode failed with error -2 [ 1.883577] iwlwifi 0000:01:00.0: firmware: direct-loading firmware iwlwifi-7265D-16.ucode [ 1.883896] iwlwifi 0000:01:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 1.916244] i915 0000:00:02.0: firmware: failed to load i915/skl_dmc_ver1.bin (-2) [ 1.916249] i915 0000:00:02.0: Direct firmware load for i915/skl_dmc_ver1.bin failed with error -2 [ 1.916251] i915 0000:00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares] , disabling runtime power management. [ 2.292574] bluetooth hci0: firmware: direct-loading firmware intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq [ 2.292579] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq [ 2.544000] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated Installed firmwares and removed packages in debian - apt-get -t jessie-backports install linux-image-amd64 - apt-get -t jessie-backports install firmware-iwlwifi - apt-get remove xserver-xorg-video-intel 2nd iteration after Stephen's answer --- The non-free package solves the graphical artifact in Matlab 2016a described here . My dmesg now where everything is ok [Stephen] because 17-21 of wifi firmware fail, but 16 iteration succeeds eventually; no other firmware failures visible masi@masi:~$ dmesg | grep firmware [ 1.897923] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-7265D-21.ucode (-2) [ 1.897961] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-21.ucode failed with error -2 [ 1.897973] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-7265D-20.ucode (-2) [ 1.898009] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-20.ucode failed with error -2 [ 1.898017] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-7265D-19.ucode (-2) [ 1.898121] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-19.ucode failed with error -2 [ 1.898129] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-7265D-18.ucode (-2) [ 1.898165] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-18.ucode failed with error -2 [ 1.898173] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-7265D-17.ucode (-2) [ 1.898209] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-17.ucode failed with error -2 [ 1.904430] iwlwifi 0000:01:00.0: firmware: direct-loading firmware iwlwifi-7265D-16.ucode [ 1.904726] iwlwifi 0000:01:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 1.917970] i915 0000:00:02.0: firmware: direct-loading firmware i915/skl_dmc_ver1.bin Hardware: Asus Zenbook UX303UA OS: Debian 8.5 64 bit Linux kernel: 4.6

I am trying to install Linux Debian 8.5 (dd'ed it successfully to USB stick) on SD card of Zenbook UX303UA. However, Grub is 1 version. I cannot boot from the USB and there exists no menu option for the fetaure in the ultrabook. I accessed the Bios by pressing esc at the login, since it does not start naturally by USB and does not give me a list boot options. I think the USB is at /dev/sdb1 now so one option is to configure Grub directly. Fig. 1 Bios and Boot, Fig. 2 Bios, USB configuration and Advanced Iterating GAD3R's proposal --- Disable successfully *Fastboot* in Bios Boot. Fig. 4 After pressing Esc at login when *Fastboot* disabled*, Fig. (5-7) are about unsuccessfully setting up boot by USB 1. first rename the option as *USB* or whatever, since just name (Fig. 5) 2. it requires the location of the boot there (Fig. 6) 3. I cannot find any other location than the current USB SSD (Fig. 7) Fig. 5 Renaming as *USB* in Boot , Fig. 6 You cannot Enable Legacy Boot for some reason (Why?), Fig. 7-10 You cannot find right location for new boot option I cannot find a way to boot from USB. 2nd Iteration --- I disable *Secure Boot* in Security > Boot. I enable CSM. I press Esc at the login. I get the list of items to boot from. - My test USB works - My Debian installer does not work so this confirms it is faulty. Problem solved! Hardware: Asus Zenbook UX303UA OS: Ubuntu 16.04 64 bit Linux kernel 4.7 Grub: version 1