# Clevo W840SU

The W840SU is a device by the taiwanese OEM manufacturer Clevo. It is sold as Schenker S403, Tuxedo Book UC1402 and Nexoc B401. A touch version exists as W840SU-T or UT1402. The hardware is configurable and includes an Intel Haswell Core i3/i5/i7, Intel HD 4400 graphics, a 7 mm harddrive, a mSATA device (storage, 3g/LTE modem) and a HDMI output.

# Installation

Installing Archlinux is straightforward and most of the hardware works out of the box.

## Airplane Mode

To make use of the flightmode button, install tuxedo-wmi from the AUR and load the tuxedo-wmi module. Use xbindkeys to map the key 255 (NoSymbol) to some script that disables wifi and bluetooth and enables the airplane mode LED.

    $ cat ~/.xbindkeysrc
    "sudo /home/user/bin/setAirplane.sh"
       m:0x0 + c:255
       NoSymbol

Enable the LED with:

    echo 1 > /sys/class/leds/tuxedo::airplane/brightness

You can automate this by installing the AUR package clevo-airplane-mode.

## Webcam

The webcam needs to be activated by pressing FN+F10, otherwise you do not see the device.

    $ lsusb
    Bus 001 Device 002: ID 8087:8000 Intel Corp.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 002 Device 003: ID 5986:0536 Acer, Inc
    Bus 002 Device 002: ID 8087:07da Intel Corp.
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

## Brightness Keys

Only the dimming key works properly by default. This can be resolved by adjusting the keybindings either manually or automatically by a desktop environment like KDE.

To do it manually, ensure that `<XF86MonBrightnessUp>` is mapped to e. g. `xbacklight -inc 10` (from xorg-xbacklight), resp. `<XF86MonBrightnessDown>` to `xbacklight -dec 10`.

## Sound

Sound mostly works out of the box. Unfortunately, the Haswell Intel HD Audio has a strange device list:

    $ aplay -l
    **** Liste der Hardware-Geräte (PLAYBACK) ****
    Karte 0: HDMI [HDA Intel HDMI], Gerät 3: HDMI 0 [HDMI 0]
     Sub-Geräte: 1/1
     Sub-Gerät #0: subdevice #0
    Karte 0: HDMI [HDA Intel HDMI], Gerät 7: HDMI 1 [HDMI 1]
     Sub-Geräte: 1/1
     Sub-Gerät #0: subdevice #0
    Karte 0: HDMI [HDA Intel HDMI], Gerät 8: HDMI 2 [HDMI 2]
     Sub-Geräte: 1/1
     Sub-Gerät #0: subdevice #0
    Karte 1: PCH [HDA Intel PCH], Gerät 0: ALC282 Analog [ALC282 Analog]
     Sub-Geräte: 1/1
     Sub-Gerät #0: subdevice #0

The first three devices on the first card are HDMI devices, whereas only number 7 works for HDMI audio. The second card is the Analog output including the speakers and the output jack. PulseAudio, as described on PulseAudio/Examples has a bug with more than 1 HDMI audio output, but the described workaround by editing default.pa did not help for this device.

Instead, the following `~/.asoundrc` resp. `/etc/asound.conf` works by setting the default ALSA device to either HDMI or analog:

    pcm.!default {
     type plug
     slave {
       pcm "hw:1,0" # 1,0 is analog
    #    pcm "hw:0,7" # 1,0 is HDMI
    #    pcm "dmix:1,0" # Use this for dmix
     }
    }
    ctl.!default {
     type hw
     card 1
    }

Or alternatively:

    defaults.pcm {
    	card 1
    	device 0
    }
    defaults.ctl {
    	card 1
    	device 0
    }

You have to restart all ALSA devices for this to work. Including DMIX is necessary for multiple sound sources, as it is not loaded by default for digital devices. This may degrade sound quality.

Microphone

The volume control for the microphone is mislabeled and reads Digital.

## Touchpad

The touchpad works out of the box with the synaptics driver. All current features are supported including two finger scroll, two- and three finger click and optional mouse buttons for the edges. Use synclient for configuration. Four finger recognition and three finger swipe gestures do not seem to work, though.

# Problems

## Suspend/Hibernate/Resume

Resuming with an inserted SD stops after reading the image. This is most likely a problem with the cardreader driver and is still investigated.

## Brightness Keys

The brightness keys stop working after an external display was connected. This may be due to the fact, that the device exposes two brightness controls:

    $ ls /sys/class/backlight/
    acpi_video0  intel_backlight

Changing the brightness is still possible via the inte_backlight control but not via ACPI, which is used by KDE.

Category:

- Clevo