Dell XPS 9360 with Ubuntu 17.10 Artful Aardvark

Being first in an alphabetical sort isn’t everything, but this time it fits…

let’s throw in a baby Aardvark to pump up the cuteness…

Previously in this occasional series I had a look at Ubuntu 17.04 on the Dell XPS 9360

And in the following I summarised how happy I was with the operation of the Dell XPS 9360 with Windows / Ubuntu dual boot

Installing Ubuntu 17.10

Full Disclosure — given the issues last time, I took the easy route and accepted the upgrade manager’s request to update the distribution.

Ideally I would have gone for a full install from a live USB like last time, but this way I am assuming there is a higher success rate for upgrades than for installations as less changes need to made made and less assumptions would need to be put to the test. Hence there is perhaps chance to avoid having to rollback if the install fails to work.

Reading that back now tough, I see the reasoning is thin, as I know installing from scratch is cleaner and I have always avoided keeping important files / data on any machine without a backup. And in addition installations are super quick nowadays, especially on this kind of hardware.


Anyway, this time I seem to have got lucky (or upgrades work better than installations). Maybe I’ll try the full install some day once I’ve given the linux and Windows boots a full shakedown.

17.10 + neofetch output

In linux land

  • some dmesg output about firmware not downloadable — STILL THERE

in Windows land

Everything seems fine, if not better and switching between the two is not apparently causing issues.

But: problems

check kernel update leads to spamming in dmesg

This seems to be the result of recent kernel updates and is still there.

[ 883.763051] pcieport 0000:00:1c.4: AER: Corrected error received: id=00e4
[ 883.763068] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter IeD)
[ 883.763081] pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000
[ 883.763090] pcieport 0000:00:1c.4: [12] Replay Timer Timeout

This is “fixed” by adding pci=noaer (No Advanced Error Reporting) to the kernel parameters.

I’m not super happy about simply suppressing output I don’t want to see, but on the basis that the Windows partition has always run clean and journalctl -f shows a nice clean output I’m assuming this is a question of verbosity that has been exposed.

The bad: issues only on Zesty Zapus

Slow startup

FIXED Start-up from cold to login prompt is under 10 seconds; shutdown equally is quick and only a few seconds

Missing mouse cursor at sign-in screen!

FIXED (also different sign in screen look- me gusta)

Slow Wifi


OK, this is pretty good…

Video Glitch

There is a noticeable, quite lengthy video glitch upon every logon.


Trackpad fixes:

$ dpkg -l | grep libinput
ii libinput-bin 1.8.2-1ubuntu2 amd64 input device management and event handling library - udev quirks
ii libinput10:amd64 1.8.2-1ubuntu2 amd64 input device management and event handling library - shared library
ii xserver-xorg-input-libinput 0.25.0-0ubuntu1 amd64 X.Org X server -- libinput input driver

Again, no obvious input issues…

Audio Setup

Again, good!

$ dmesg | grep snd_hda
[ 3.617878] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[ 3.618134] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 3.692508] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3246: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 3.692511] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 3.692512] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 3.692513] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 3.692514] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 3.692515] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19
[ 3.692516] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a
[ 3.692518] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12


This is an excellent upgrade so far — the new desktop works absolutely fine and the test of the hardware seems good too.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.