Dell XPS 13 9350 Late 2015

Phacops · 2015-12-24 03:03:18

Yes, the speakers are working. I'm on Arch Linux 4.4-rc6, pulseaudio + alsa-utils installed, I unmutted the speakers in alsamixer and I was able to blast music with firefox!

danielkza · 2015-12-25 10:21:05

Has anyone tried fiddling with the ACPI OSI name (the acpi_osi kernel parameter) to see if it enables ASPM?

Last edited by danielkza (2015-12-27 14:09:47)

kgizdov · 2015-12-25 22:25:43

danielkza wrote:

Has anyone tried faking fiddling with the ACPI OSI name (the acpi_osi kernel parameter) to see if it enables ASPM?

No luck with that for me...

Also, I just got the Dell DA200 Adaptor and can confirm it works. Ethernet and USB work fine. The only thing is you need to have the adaptor plugged in and do a reboot so the kernel can initialise it. This is all good news.

The only thing that bothers me now is that my Nexus 6P will connect fine with the USB-C to USB-A cable through the adaptor, but will not connect with the USB-C to USB-C cable into the port on the laptop directly. And if I plug it in directly, then the laptop cannot shutdown or reboot afterwards - I have to shut it down by holding the power button. I have not been able to find a workaround.

rschell · 2015-12-27 14:08:08

I have issues with color banding on my FHD, I7-6500U, 9350unit.
It seems that the colors are badly limited.
This is for all 4.4 RC, all bios versions until now and with or without the newest intel fw for Skylake.
Even the color picker color ramp in Gimp is not smooth and the output is useless for any photo editing.

[EDIT:] SOLVED

I installed DisplayLink before as an external video output and had 2 screens in xorg. It caused the problem.
Now set both to depth 24 manually and it works like a charm.

Last edited by rschell (2016-01-04 00:21:07)

frank604 · 2015-12-27 20:53:39

kgizdov wrote:

The only thing that bothers me now is that my Nexus 6P will connect fine with the USB-C to USB-A cable through the adaptor, but will not connect with the USB-C to USB-C cable into the port on the laptop directly. And if I plug it in directly, then the laptop cannot shutdown or reboot afterwards - I have to shut it down by holding the power button. I have not been able to find a workaround.

I just bought a nexus 6p. Once my Dell xps returns I'd be happy to debug with you

angelo · 2015-12-28 07:17:24

I'm installing arch on a new Dell XPS 9350, and while it is coming along, I have a problem that I couldn't find in the forum (or elsewhere). I can presently boot with kernel 4.2.5, but not 4.4.0-rc6. I am new to UEFI and systemd-boot, so I am probably missing something stupid. Overview of the main things done so far below.

I started by following very useful tips from http://oli.me.uk/2015/11/06/installing- … s-13-9350/ and http://frankshin.com/installing-archlin … lake-9350/ , and of course the wiki and this thread.

I am going for a dual-boot setup with the existing Windows 10. I changed SATA from raid to AHCI, and got Windows to accept this by booting it to safemode.

Arch install seemed to go smoothly (using USB-ethernet adaptor, since I have the broadcom chip), but could not boot into Arch. I tried setting up PreLoader, but that didn't work, so I turned off Safe Boot. Now I would get an error "Unable to find root device /dev/nvme0n1p6" and dropped to recovery shell. Several places suggested running mkinitcpio again, but this had no effect. mkinitcpio runs cleanly, except for warnings for the fallback image about two missing modules (which it seems are not needed).

This was eventually resolved when I changed the options in the loader entry from the device label to "root=PARTUUID=XXXX.....", and Arch with 4.2.5 now boots and seems to work. (I include this here in case anyone else has this problem, and to help differential diagnosis.) However a problem remains. At an earlier stage I also installed linux-mainline 4.4.0-rc6. This was installed from AUR with makepkg, with no config changes. Installation went smoothly, but I still cannot boot into Arch with 4.4.0. Three differences from 4.2.5:
1. Changing the root from label to partuuid made no difference (except that it now complains about not finding a device with that partuuid).
2. Even before that, there is a "Warning: /lib/modules/4.2.5-1-ARCH/ not found - ignoring". It is vexing that 4.4.0 is looking for a 4.2.5 module in the first place.
3. In the recovery shell, the keyboard is not responding, so it seems there is nothing to do except a hard reboot.

I'd be happy to supply any specific information if anyone can help me figure this out.

zetxx · 2015-12-28 11:33:57

angelo wrote:

I'm installing arch on a new Dell XPS 9350, and while it is coming along, I have a problem that I couldn't find in the forum (or elsewhere). I can presently boot with kernel 4.2.5, but not 4.4.0-rc6. I am new to UEFI and systemd-boot, so I am probably missing something stupid. Overview of the main things done so far below.
I started by following very useful tips from http://oli.me.uk/2015/11/06/installing- … s-13-9350/ and http://frankshin.com/installing-archlin … lake-9350/ , and of course the wiki and this thread.
I am going for a dual-boot setup with the existing Windows 10. I changed SATA from raid to AHCI, and got Windows to accept this by booting it to safemode.
Arch install seemed to go smoothly (using USB-ethernet adaptor, since I have the broadcom chip), but could not boot into Arch. I tried setting up PreLoader, but that didn't work, so I turned off Safe Boot. Now I would get an error "Unable to find root device /dev/nvme0n1p6" and dropped to recovery shell. Several places suggested running mkinitcpio again, but this had no effect. mkinitcpio runs cleanly, except for warnings for the fallback image about two missing modules (which it seems are not needed).
This was eventually resolved when I changed the options in the loader entry from the device label to "root=PARTUUID=XXXX.....", and Arch with 4.2.5 now boots and seems to work. (I include this here in case anyone else has this problem, and to help differential diagnosis.) However a problem remains. At an earlier stage I also installed linux-mainline 4.4.0-rc6. This was installed from AUR with makepkg, with no config changes. Installation went smoothly, but I still cannot boot into Arch with 4.4.0. Three differences from 4.2.5:
1. Changing the root from label to partuuid made no difference (except that it now complains about not finding a device with that partuuid).
2. Even before that, there is a "Warning: /lib/modules/4.2.5-1-ARCH/ not found - ignoring". It is vexing that 4.4.0 is looking for a 4.2.5 module in the first place.
3. In the recovery shell, the keyboard is not responding, so it seems there is nothing to do except a hard reboot.
I'd be happy to supply any specific information if anyone can help me figure this out.

please take a look @ https://bbs.archlinux.org/viewtopic.php … 4#p1579594

angelo · 2015-12-28 20:27:53

zetxx wrote:

angelo wrote:
...
I still cannot boot into Arch with 4.4.0. Three differences from 4.2.5:
1. Changing the root from label to partuuid made no difference (except that it now complains about not finding a device with that partuuid).
2. Even before that, there is a "Warning: /lib/modules/4.2.5-1-ARCH/modules.devname not found - ignoring". It is vexing that 4.4.0 is looking for a 4.2.5 module in the first place.
3. In the recovery shell, the keyboard is not responding, so it seems there is nothing to do except a hard reboot.
please take a look @ https://bbs.archlinux.org/viewtopic.php … 4#p1579594

Thanks for the pointer! I actually saw this earlier, and already have MODULES "nvme intel_AGP i915". I'll try removing intel_agp and/or i915, though I would not have guessed including redundant modules could cause boot failure (if they are not needed, not finding them will do no harm).

[EDIT:] /lib/modules/4.2.5-1-ARCH/modules.devname does exist, but the partition seemingly can't be mounted.

Could this be a btrfs issue? It does mount with 4.2.5, so I'm doubtful that is the issue.

[EDIT:] I tried various subsets of nvme, i915, intel_agp for MODULES, and re-running mkinitcpio. Nothing seems to work.

Last edited by angelo (2015-12-29 07:13:40)

kgizdov · 2015-12-29 14:46:51

angelo wrote:

zetxx wrote:
angelo wrote:
...
I still cannot boot into Arch with 4.4.0. Three differences from 4.2.5:
1. Changing the root from label to partuuid made no difference (except that it now complains about not finding a device with that partuuid).
2. Even before that, there is a "Warning: /lib/modules/4.2.5-1-ARCH/modules.devname not found - ignoring". It is vexing that 4.4.0 is looking for a 4.2.5 module in the first place.
3. In the recovery shell, the keyboard is not responding, so it seems there is nothing to do except a hard reboot.
please take a look @ https://bbs.archlinux.org/viewtopic.php … 4#p1579594
Thanks for the pointer! I actually saw this earlier, and already have MODULES "nvme intel_AGP i915". I'll try removing intel_agp and/or i915, though I would not have guessed including redundant modules could cause boot failure (if they are not needed, not finding them will do no harm).
[EDIT:] /lib/modules/4.2.5-1-ARCH/modules.devname does exist, but the partition seemingly can't be mounted.
Could this be a btrfs issue? It does mount with 4.2.5, so I'm doubtful that is the issue.
[EDIT:] I tried various subsets of nvme, i915, intel_agp for MODULES, and re-running mkinitcpio. Nothing seems to work.

First, I do hope you did not follow the guide and enable Legacy mode and booted this way. This is wrong. Instead, you can boot from a USB by setting USB security to off in the BIOS (System Configuration->). If you can't see your USB this way, then it is not UEFI compliant. Booting this way ensures you are booting your USB stick in UEFI and prevents any partitions not being created properly.

To address your most recent issue - Did you change your boot config from:

initrd         /initramfs-linux.img

to:

initrd         /initramfs-linux-mainline.img

If you did not, then the bootloader would not be able to find your latest installed kernel.

angelo · 2015-12-29 19:20:45

kgizdov wrote:

First, I do hope you did not follow the guide and enable Legacy mode and booted this way. This is wrong. Instead, you can boot from a USB by setting USB security to off in the BIOS (System Configuration->). If you can't see your USB this way, then it is not UEFI compliant. Booting this way ensures you are booting your USB stick in UEFI and prevents any partitions not being created properly.

I was indeed in UEFI mode all along.

kgizdov wrote:

To address your most recent issue - Did you change your boot config from:
initrd         /initramfs-linux.img
to:
initrd         /initramfs-linux-mainline.img
If you did not, then the bootloader would not be able to find your latest installed kernel.

I am completely stupid. The boot config had the correct initramfs, but pointed to the wrong kernel. I was somehow blind to this error, and only noticed as I was copying the files to post here. Many thanks to all who tried to help, and for the many tips in this thread.

bart_vv · 2015-12-31 01:19:20

Anyone knows if support for monitor, ap and/or ad-hoc mode is planned for broadcom driver for our chip?

kgizdov · 2016-01-02 18:07:41

bart_vv wrote:

Anyone knows if support for monitor, ap and/or ad-hoc mode is planned for broadcom driver for our chip?

Broadcom usually only deal with OEMs and make very little effort in terms of satisfying individual users. If Dell decide to have a developer edition with good support in Linux, you might be in luck. However, the Intel 8260AC is like £20-30, so it might be worth it to just invest in that. Seems there is already support.

In the mean time - has anyone made bug reports for these?

➜  ~  dmesg -l alert
[   15.385002] BUG: unable to handle kernel paging request at ffffc9000194cf8f
[   15.388763] IP: [<ffffffffa07330b3>] dell_wmi_init+0x94/0xfe1 [dell_wmi]
[   15.388847] RIP  [<ffffffffa07330b3>] dell_wmi_init+0x94/0xfe1 [dell_wmi]

dmesg says alert level events need immediate action to be taken. These are above error and critical and only below system unusable

.:B:. · 2016-01-03 14:35:52

Well, Broadcom has been helping out OpenWrt devs lately, to the point that e.g. the Netgear R8000 (an AC router) has full wireless support in OpenWrt (and Linux in general). They have a bad rep, and they worked hard for that . But things are changing.

Last edited by .:B:. (2016-01-03 14:37:43)

kgizdov · 2016-01-04 20:52:11

.:B:. wrote:

Well, Broadcom has been helping out OpenWrt devs lately, to the point that e.g. the Netgear R8000 (an AC router) has full wireless support in OpenWrt (and Linux in general). They have a bad rep, and they worked hard for that . But things are changing.

Sorry, but I fail to see how that helps people with Broadcom chips that have been ordered and made according to Dell's specifications. OpenWRT is the most popular vendor for custom router software and supporting it is probably to compete with the new Linksys WRT1900ACS. I do hope Broadcom comes to they're senses, but there is no indication that they have. In the end it comes down to when this support will come to XPS users and I think the best chance is for Dell to ask (by which I mean "pay") Broadcom for this job.

I have good news, kernel 4.4-rc8 fixes all critical and alert events for me. Now, there are only a few minor errors and warnings. The worst of which, I think is this:

➜  ~  dmesg -l err 
[    2.320615] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* 5.4 Gbps link rate without HBR2/TPS3 support

We are almost there guys. We just need to settle this awful power consumption that's hogging us down.

altoyr · 2016-01-05 12:02:30

Hello,

I tried to install the newest kernel from linux-mainline (4.4.0-rc8) but I get following errro while booting.

    ERROR: device '/dev/nvme0n1p2' not found. skip fsck.
    ERROR: unable to find root device '/dev/nvme0n1p2'

I did following steps:

#download mainline-kernel with curl
tar xzf linux-mainline.tar.gz
cd linux-mainline
makepkg -s

sudo pacman -U linux.headers-4.4.0-rc8.x86_64.tar.xz
sudo pacman -U linux.4.4.0-rc8.x86_64.tar.xz

cd /boot/loader/entries
cp arch.conf linux-mainline.conf

nano linux-mainline #edited the 2 lines from vmlinuz-linux to vmlinuz-linux-mainline
cd ..
nano loader.config #set linux-mainline as default in /boot/loader/loader.config
reboot

Did I miss something?

Thanks in Advance

EDIT:

I also booted into the default-kernel and tried

mkinitcpio -p linux-mainline

without success

EDIT2:
I found, that i have to add nvme to MODULES

But I have no idea what that means

Last edited by altoyr (2016-01-05 12:19:05)

mkey · 2016-01-05 12:31:40

altoyr wrote:

EDIT2:
I found, that i have to add nvme to MODULES
But I have no idea what that means

You got it.
This is done by editing /etc/mkinitcpio.conf

MODULES="nvme"

altoyr · 2016-01-05 12:40:48

And you have to run

 
mkinitcpio -p linux-mainline

Afterwards...

Thanks for the help

kgizdov · 2016-01-05 18:52:49

These questions seem to get asked a lot over and over again. So I added some stuff to the wiki.

altoyr · 2016-01-06 10:02:00

Hey Guys, me again.

I run 4.4.0-rc-8 and everything is working fine so far.

I only experience problems when my notebook suspends, I have read through the thread again and I haven't found any post describing the same problems:

1) Leaving the laptop open -> screen goes black -> enter login credentials -> everything is incredible slow and laggy
2) Close the lid -> laptop reboots

Is anyone having similar issues?

Thanks in advance.

kgizdov · 2016-01-06 17:15:02

altoyr wrote:

Hey Guys, me again.
I run 4.4.0-rc-8 and everything is working fine so far.
I only experience problems when my notebook suspends, I have read through the thread again and I haven't found any post describing the same problems:
1) Leaving the laptop open -> screen goes black -> enter login credentials -> everything is incredible slow and laggy
2) Close the lid -> laptop reboots
Is anyone having similar issues?
Thanks in advance.

I had that issue myself, but now it's fine. I couldn't be sure what caused it, but here's what I did. I first had the suspend button extension in Gnome installed. I removed it and now press Alt on the menu to invoke suspend when I need it. I also, downgraded networkmanager-openvpn plugin to 10.0.8-1, as the last update to 10.0.10 was removed from the repos for some reason without notification (this is currently the latest version). Then I tried invoking suspend manually with sustemctl suspend. This was still unsuccessful for some time. Then after a restart it all was fine and I've had no issues. Still not sure what was the problem, but maybe this helps for you.

sender · 2016-01-08 10:19:57

What are the correct fstab options for our NVMe storage?

I was going to set 'discard' but

# hdparm -I /dev/nvme0n1p1 |grep TRIM

yields no output.

Then I found this: https://communities.intel.com/thread/75 … 0&tstart=0

We reviewed your inquiry and have confirmed that with Intel® NVMe SSDs, the discard option when making your Linux filesystem should be turned off. The default extended option is not to discard blocks at filesystem level, retain this. The discard option is not needed an may actually have a performance impact.

What options to set in fstab?

Should this be added to the wiki(s)?

Thanks.

kgizdov · 2016-01-08 12:40:38

sender wrote:

What are the correct fstab options for our NVMe storage?
I was going to set 'discard' but
# hdparm -I /dev/nvme0n1p1 |grep TRIM
yields no output.
Then I found this: https://communities.intel.com/thread/75 … 0&tstart=0
We reviewed your inquiry and have confirmed that with Intel® NVMe SSDs, the discard option when making your Linux filesystem should be turned off. The default extended option is not to discard blocks at filesystem level, retain this. The discard option is not needed an may actually have a performance impact.
What options to set in fstab?
Should this be added to the wiki(s)?
Thanks.

By definition NVMe does not have a TRIM command. It has deallocate. That said, in most cases deallocate is managed internally on firmware level and manufacturers discourage using it manually in your file system options. See this doc from Intel. Moreover, the Dell XPS comes with a Samsung NVMe and Samsung has had very bad rep with TRIM in the past. Many people lost lots of data because of their firmware bugs relating to TRIM in Linux. So I would not recommend trying any of this on your NVMe unless you feel adventurous and want to let us know how it turned out.

sender · 2016-01-08 15:46:53

@kgizdov thanks for the clarification!

zyth88 · 2016-01-09 00:02:56

I got the 9350 fhd model and everything is working well with the linux-mainline kernel except for audio.
There's constant static/white noise until audio plays and loud pop noises between audio starting and stopping.

altoyr · 2016-01-09 07:42:49

To get rid of the white-noise install alsamixer then start it -> press F6 -> select 0 HDA Intel PCH -> go to the third lever from left stating "Headphones" and set this one to 22

To get rid of the poping noises I deactivated sound-standby in tlp SOUND_POWER_SAVE_ON_BAT = 0 in /etc/default/tlp

EDIT: I added this to the Wiki, this was my first Wiki-edit so if someone could check it syntax and expression are adequate I would be delighted.

Last edited by altoyr (2016-01-09 08:08:58)

Arch Linux

#201 2015-12-24 03:03:18

Re: Dell XPS 13 9350 Late 2015

#202 2015-12-25 10:21:05

Re: Dell XPS 13 9350 Late 2015

#203 2015-12-25 22:25:43

Re: Dell XPS 13 9350 Late 2015

#204 2015-12-27 14:08:08

Re: Dell XPS 13 9350 Late 2015

#205 2015-12-27 20:53:39

Re: Dell XPS 13 9350 Late 2015

#206 2015-12-28 07:17:24

Re: Dell XPS 13 9350 Late 2015

#207 2015-12-28 11:33:57

Re: Dell XPS 13 9350 Late 2015

#208 2015-12-28 20:27:53

Re: Dell XPS 13 9350 Late 2015

#209 2015-12-29 14:46:51

Re: Dell XPS 13 9350 Late 2015

#210 2015-12-29 19:20:45

Re: Dell XPS 13 9350 Late 2015

#211 2015-12-31 01:19:20

Re: Dell XPS 13 9350 Late 2015

#212 2016-01-02 18:07:41

Re: Dell XPS 13 9350 Late 2015

#213 2016-01-03 14:35:52

Re: Dell XPS 13 9350 Late 2015

#214 2016-01-04 20:52:11

Re: Dell XPS 13 9350 Late 2015

#215 2016-01-05 12:02:30

Re: Dell XPS 13 9350 Late 2015

#216 2016-01-05 12:31:40

Re: Dell XPS 13 9350 Late 2015

#217 2016-01-05 12:40:48

Re: Dell XPS 13 9350 Late 2015

#218 2016-01-05 18:52:49

Re: Dell XPS 13 9350 Late 2015

#219 2016-01-06 10:02:00

Re: Dell XPS 13 9350 Late 2015

#220 2016-01-06 17:15:02

Re: Dell XPS 13 9350 Late 2015

#221 2016-01-08 10:19:57

Re: Dell XPS 13 9350 Late 2015

#222 2016-01-08 12:40:38

Re: Dell XPS 13 9350 Late 2015

#223 2016-01-08 15:46:53

Re: Dell XPS 13 9350 Late 2015

#224 2016-01-09 00:02:56

Re: Dell XPS 13 9350 Late 2015

#225 2016-01-09 07:42:49

Re: Dell XPS 13 9350 Late 2015

Board footer