Skylake Platform Validation

[reynhout]

Tracking validation tests and bug reports for GalliumOS support for Skylake models.

Please add observations for any Skylake model in comments!

Current Skylake status

• [X] Boots from USB ISO
• [X] Boots from internal storage (eMMC)
  • OK after install via chrx on stock firmware (see #273)
• [X] Internal keyboard
• [X] Trackpad
• [X] WiFi
• [X] Bluetooth
• [X] Touchscreen
• [X] Media keys
  • [X] Volume control
  • [X] LCD backlight control
  • [ ] Keyboard backlight control
    • NG (CHELL)
• [X] Suspend/resume
  • OK (CAVE, LARS)
  • reports vary, see comments
• [ ] Internal audio (see also #379)
  • nau88l25_ssm4567 (CAROLINE, CHELL)
    • [X] speakers
    • [ ] microphone, headphones, jack detection
  • nau88l25_max98357a (LARS, SENTRY, CAVE?)
    • [ ] speakers, microphone, headphones, jack detection
  • (tbd) (ASUKA)
    • [ ] speakers, microphone, headphones, jack detection
  • workarounds USB audio or Bluetooth audio
• [x] galliumos-skylake package created

[kmishra9]

Suspend/resume also seems to work just fine.

Some other problems I've noticed:

Display backlighting control doesn't work. Right-Alt + Brightness keys do nothing. Upon booting, there's a display backlight at full power always on and to turn it off, I just close the screen and then open it back up again. At that point, the display backlight is turned off but nothing I do allows me to turn it back on.

Full-screen works, refresh works, back and forward works, power and escape work, however the "show all things on desktop" F5 button only opens up the Display menu.

Audio input also doesn't seem to work (no options given).

Finally, just curious but Is there an ETA on a fix or update for something like this? Roughly 1 month? 6 months? 1 year? etc.

[reynhout]

@kmishra9: by default, the LCD backlight is controlled by unmodified media keys: F6, F7. This is configurable though: https://wiki.galliumos.org/Media_keys_and_default_keybindings .

When the lid is opened, the screensaver kicks in, and captures all keypresses (including backlight controls). You need to enter your password (sometimes blind) to dismiss the screensaver, then keypresses will reach their usual destinations. This is awkward, and I'd like to find a way to set a minimum backlight level when resuming after suspend...or to allow media keypresses to pass though the screensaver.

F5 is configured to open the display menu, but I don't recall why. It might be a side effect of using modified-F5 for screenshots?

Audio in and out are on the same chip, which isn't inited properly at all yet. Hopefully the config necessary for one to work will fix both.

We do not have an ETA on any of the open issues. We will build some test kernels with some experimental configs, but we will probably also need to purchase suitable test hardware.

[reynhout]

lsmod | grep snd, ChromeOS kernel 3.18 on CHELL (thanks @MattDevo)

snd_soc_skl_nau88l25_ssm4567    20544  0 
snd_soc_hdac_hdmi      16492  1 snd_soc_skl_nau88l25_ssm4567
snd_soc_dmic           12352  0 
snd_soc_skl            33897  0 
snd_soc_skl_ipc        22007  1 snd_soc_skl
snd_soc_sst_acpi       12398  1 snd_soc_skl
snd_soc_sst_ipc        12627  1 snd_soc_skl_ipc
snd_soc_sst_dsp        27573  1 snd_soc_skl_ipc
snd_hda_ext_core       18454  2 snd_soc_hdac_hdmi,snd_soc_skl
snd_hda_core           36706  3 snd_hda_ext_core,snd_soc_hdac_hdmi,snd_soc_skl
snd_soc_nau8825        32883  1 snd_soc_skl_nau88l25_ssm4567
snd_soc_ssm4567        12352  0 
snd_seq_midi           12352  0 
snd_seq_midi_event     12735  1 snd_seq_midi
snd_rawmidi            21355  1 snd_seq_midi
snd_seq                49644  2 snd_seq_midi_event,snd_seq_midi
snd_seq_device         12653  3 snd_seq,snd_rawmidi,snd_seq_midi

[kmishra9]

^Sorry, what is this?

Also my bad, yeah DISPLAY backlighting works, KEYBOARD backlighting doesn't. That was a typo.

[thoughtchad]

LARS, Acer CB 14 for Work Issues Suspend mode turns fan on high speed indefinitely No internal audio hardware available (output or input) Various keyboard mappings not working (Delete, Home, End, LCD +-, Volume +-, Search (nothing), etc No keyboard backlighting

[phelpsw]

Using a HP Chromebook 13 G1

Suspend appears to mostly work for me with the following two issues:

• XScreensaver login window coming out of restore is functional but the base texture of the window looks like there is a video memory corruption issue.
• Wifi broke when coming out of restore (dmesg shows "wlp1s0: link not ready" messages)

Other stuff:

• Touchpad is slightly unresponsive on first touch, maybe just a characteristic of the hardware (new unfamiliar laptop).
• Sound / Mic don't work as mentioned above.
• Keyboard backlighting doesn't work
• 3200x1800 resolution on this laptop requires some UI fiddling to make text readable / buttons clickable

[reynhout]

@thoughtchad, @phelpsw Thanks for the reports.

There might be some reusable HiDPI config in the galliumos-samus pkg: https://github.com/GalliumOS/galliumos-samus/tree/master/etc/skel/.config

[phelpsw]

Installing galliumos-samus package fixed my hidpi problems. It looks excellent now. I followed the directions here: https://wiki.galliumos.org/Installing/Samus specifically:

sudo galliumos-repodist --enable testing
galliumos-update
sudo apt-get install galliumos-samus
cp -r /etc/skel/.config $HOME

Followed by a logout.

Before: http://i.imgur.com/5hmWWE7.png After: http://i.imgur.com/BNMZThP.png

My keyboard backlight also appears to be working now although I haven't figured out how to adjust brightness yet.

[reynhout]

@phelpsw Key mappings (on the default keyboard layout) for keyboard backlight decrease/increase are RightAlt + - and RightAlt + =. Do those work for you?

[ghost]

Confirming the samus steps above do enable keyboard backlighting, however:

1. Backlighting switches off after suspend/resume
2. Key mappings for enable/disable/adjust brightness do not function

[phelpsw]

@reynhout no those buttons don't work.

I agree with KFriedCode

[reynhout]

@phelpsw OK, it sounds like we'll need new keycode mappings for that model (CHELL?)

[kmishra9]

Yup I'm on Chell.

Something also just recently occurred where the trackpad requires a lot of pressure to move the mouse pointer (a light finger on it won't move it) and tap-to-click stopped working. Ive recently had to fsck my sd card a couple of times so I'm afraid I may have done something to the mouse driver. This issue also cropped up after I had booted the Linux partition via SD on another Chromebook as well (Toshiba Chromebook 2) where the pointer was working fine but.... Yeah.

Any suggestions? Or ways to update the mouse driver?

[coolstar]

Just a heads up, I'll be getting a chell in a few days to build firmware for. If there's anything of interest I can take a look at it here.

[fizal619]

@kmishra9 https://github.com/dnschneid/crouton/issues/214 Might shed some light. This is probably too late, but it helped me on crouton may help you figure out why the touchpad is weird on Chell.

[polarimetric]

I'm dual booting GalliumOS (installed through chrx) on a Cave (Asus Chromebook Flip C302CA), my experiences (most echo what is said above):

• Touchscreen works completely (tapping, dragging, two-finger tap to right click, etc)
• Keyboard backlight works but can't be adjusted
• No internal audio
• Suspend/resume works, both manually and from closing the lid
• Display brightness keys don't work, but automatic display brightness adjustments (e.g. after x seconds inactive) do work

[reynhout]

@polarimetric Thanks for the report!

I think you're the first person to test the touchscreen, so I will mark that as "working". Hopefully it applies to all models (it probably does).

If you are dual-booting, would you mind pastebin'ing a system log from ChromeOS? I'd like to check some hardware info from the ChromeOS side, could help with getting internal audio working:

• Log in like you did to run chrx, get a ChromeOS terminal and shell
• Run dmesg | curl -sF c=@- https://ptpb.pw | grep url:
• Post the URL here

You seem to be having trouble with the media keys. Do the others work (volume control, etc)? They should pop a notification overlay window even though internal audio itself does not work. Keyboard and LCD backlight should pop a window as well.

• RightAlt + - / RightAlt + =: Keyboard backlight down / up
• F6 / F7 (no modifier key): LCD backlight down / up
• F8 / F9 / F10: Volume mute / down / up

Good news about suspend/resume. I'll mark that as well, at least for CAVE.

Thanks again!

[polarimetric]

Here's the requested log: https://ptpb.pw/0T2s

No, I'm not getting any popups when pressing any of the function keys--keyboard backlight, display backlight, or volume control. There is no visual response to the key presses anywhere that I can discern.

[reynhout]

@polarimetric Thanks for the logfile.

You're on the default keyboard layout, right? It sounds like we will need new maps for all of the Skylake models.

[polarimetric]

No problem. Yeah, default keyboard.

[thoughtchad]

@reynhout here's another dmesg, acre cb 4 work 14 https://ptpb.pw/CYHB

[reynhout]

@thoughtchad Cool, thanks. It looks like CAVE and LARS have the same audio chip, which is different from CHELL.

[polarimetric]

On Cave, installing the Chromebook keyboard backlight driver after adding Cave to the model list in chromebook_kb_backlight.c enables adjustment of the keyboard backlight. Default keyboard shortcuts still don't work so I mapped my own with the provided script, but the adjustment is available at /sys/class/leds/chromeos as it is on Samus and Lulu.

(edit: removed incorrect information about powertop and battery bug, see comments below)

[polarimetric]

Bizarrely, disabling "Use system default" and changing my keyboard model to "Chromebook (most models) | Right alt overlay | F keys mapped to media keys" in the keyboard setting, and then re-enabling "Use system default" fixed all of the default keyboard shortcuts except for XF86KbdLightOnOff, which is not doing anything even though xev shows the correct mapping. (Keyboard light up/down works.) Before I did this (default out-of-the-box behavior), xev did not show right alt as Overlay and Overlay + function key just registered as the regular function key; now all bindings are being reported correctly. This behavior is equivalent to what I see if I enable the Chromebook Falco/Pixel/Pixel2 keyboard model so I think it's just a matter of changing what model is used by default on Cave.

[reynhout]

@polarimetric That's interesting.

Keyboard layout Chromebook (most models) | Right alt overlay | F keys mapped to media keys should be the default for most models, and Use system defaults should be unchecked. I wonder what's different for CAVE (and possibly the other Skylake models?).

[polarimetric]

@reynhout I just created a fresh user account to verify that Use system defaults is checked by default on Cave and it is.

[polarimetric]

Update on the supposed powertop issue: It had nothing to do with powertop, that was just a coincidence. I ran into the same problem again today--the battery says that it will take 10 hours to charge and the charge comes in at a very slow trickle. Restarting does not fix it; the only way to fix it is a hard reset. It's identical to the bug this user on reddit encountered with Ubuntu, but annoyingly, they don't mention what threads on Ubuntu forums referenced the problem and I can't find them. Not sure how to go about debugging this.

[polarimetric]

Figured out what causes it--it's suspend while on battery power, so even though suspend itself technically works fine, I'd revoke "ok" status from suspend/resume on Cave. Steps to reproduce:

1. Run the laptop on battery power in GalliumOS.
2. Suspend and then resume the laptop.
3. Plug in, see charge time to full estimate >7 hours, battery charging at a rate of about 0.1% per minute.
4. Restart normally into Gallium; see that battery is still charging at extremely slow rate.
5. Hard-reset the laptop by holding power button and boot back into Gallium; see expected charge rate/time to full (~60 minutes from 0 to 100%).

Here's a thread from Ubuntu forums for reference. Looks like this is a long-standing Ubuntu bug that has affected various devices.

(Also, I've verified this does not occur in Chrome OS, so it's not a hardware issue.)

EDIT: This is also occurring with the mainline 4.10rc3 kernel. Suspending and resuming while on battery power and then plugging in the device again cuts the wattage supplied while charging at 93% from ~9w to anywhere from 0.6w-2.5w, resulting in the slow charge time.

[polarimetric]

The rotation script in the Braswell validation tracker also works without modification on Cave.

[polarimetric]

More information on the Cave battery suspend/resume issue (documenting what I said in IRC here): If the device is plugged in while suspended, i.e.:

1. Unplug the device if it is plugged in
2. Suspend
3. Plug in the device while suspended
4. Resume while plugged in;

the charge rate is appropriate. The issue occurs when the laptop is plugged in while awake on battery power following a suspend on battery power. This leads me to believe it has something to do with hardware reinitialization on resume, but I can't find a way to confirm this--no errors are showing up in any logs. (I have a hunch it has something to do with xhci/the USB controller but I'm not knowledgeable enough to explore this further independently.)