Dell XPS 13 9350 Late 2015

halka · 2016-01-30 11:58:44

Yeah, pointing devices aren't suspended by default, if you don't use it you have to whitelist it in tlp:

- get the device id from `lsusb` (mine is 04f3:20d0)
- put the id in USB_WHITELIST option

zetxx · 2016-01-30 14:55:46

halka wrote:

Yeah, pointing devices aren't suspended by default, if you don't use it you have to whitelist it in tlp:
- get the device id from `lsusb` (mine is 04f3:20d0)
- put the id in USB_WHITELIST option

thanks a lot

diraimondo · 2016-01-30 16:19:28

halka wrote:

Yeah, pointing devices aren't suspended by default, if you don't use it you have to whitelist it in tlp:
- get the device id from `lsusb` (mine is 04f3:20d0)
- put the id in USB_WHITELIST option

It is true that tlp will not set powersave mode on the touchscreen if you don't use the usb whitelist. I use it so powertop reports "Good" state on it but it is still usable (no problem with interaction like with usb mouses). I've to say that I'm not sure if this is effective in the powersave economy.

Last edited by diraimondo (2016-01-30 16:39:04)

halka · 2016-01-30 23:00:21

Setting the touchscreen into 'Good' powersave mode makes it non-responsive for me, so that's the reason I've formulated my response in that way. It's not really a big deal for me (I can't stand fingerprints on that gorgeous display ). ATM I'm using kernel 4.5 RC1.

Last edited by halka (2016-01-31 13:51:33)

zetxx · 2016-01-31 08:17:30

halka wrote:

Setting the touchscreen into 'Good' powersave mode makes it non-responsive for me, so that's the reason I've formulated my response in that way. It's not really a big deal for me (I can't stand fingerprints on that gorgeous display ). ATM I'm using kernel 4.5.

rc1 ? i cannot use it at all, it constantly freezes and stops working ..

altoyr · 2016-01-31 08:27:30

Regarding the BIOS, is there any list with changes and a download-location of the older versions?
I only found the current Version without any exact information about the changes on the official HP site.

sender · 2016-01-31 10:57:44

halka wrote:

...
e: oh yeah, one other thing. do the media keys work for you? I mean player control ones, like play/pause.

Yes. Using the keys with Spotify and zero trouble so far.

turnip · 2016-02-01 14:54:47

kgizdov wrote:

turnip wrote:
Thanks. Yes, turns out it does work if plugged in before powering of. Though that kind of removes the point of having one of these hubs in the first place. Oh well, hopefully support will improve.
The external display works fine. I will try a friend's USB-C charger with it and find out if that works.
That is strange. The Dell hub I got didn't work at first as you mentioned. However, after I rebooted with the hub plugged in, it now works fine every time regardless of the situation. Maybe it has something to do with Dell's BIOS or the hub itself. I also remember that Dell flagged BIOS 1.1.7 the first version to support their hub. So maybe check if your BIOS is up to date or if it has any effect.

To follow up on this: I upgraded to the latest BIOS at the weekend, but it makes no difference (I was on 1.1.7 anyway).

sender · 2016-02-02 10:25:46

I guess I'll call it bad luck :-/

The only writing on the wall was that on every other reboot everything was very slow (navigating bios, bootloading, DE, etc).

Just upgraded to BIOS v1.2.3 + 4.5-rc2 but had successful boots since.

Dell: in 3-4 weeks you'll hear about the swap.

diraimondo · 2016-02-02 10:52:03

sender wrote:

I guess I'll call it bad luck :-/
http://i.imgur.com/07Knbm3.jpg
The only writing on the wall was that on every other reboot everything was very slow (navigating bios, bootloading, DE, etc).
Just upgraded to BIOS v1.2.3 + 4.5-rc2 but had successful boots since.
Dell: in 3-4 weeks you'll hear about the swap.

I can't understand: was the cause the upgrade to the bios? Could you explain what is happened?

Sorry for the RMA. :-(

sender · 2016-02-02 11:22:14

diraimondo wrote:

... was the cause the upgrade to the bios? Could you explain what is happened? ...

I don't think the problem is bios 1.2.3. I had successful boots since the upgrade and had expected a lot of similar posts.

No other clues really, only that everything was on-and-off very slow. The Dell rep said he never saw something like this before (..?).

Hope that this is an accidental case and no one else encounters this!

halka · 2016-02-02 17:57:22

zetxx wrote:

halka wrote:
Setting the touchscreen into 'Good' powersave mode makes it non-responsive for me, so that's the reason I've formulated my response in that way. It's not really a big deal for me (I can't stand fingerprints on that gorgeous display ). ATM I'm using kernel 4.5.
rc1 ? i cannot use it at all, it constantly freezes and stops working ..

4.5 rc1, then later rc2, but had rolled back to this release today, since supend/resume was spotty at best. I experienced no crashes or other instability running on 4.5, however.

Last edited by halka (2016-02-02 19:03:33)

zetxx · 2016-02-02 18:20:30

halka wrote:

zetxx wrote:
halka wrote:
Setting the touchscreen into 'Good' powersave mode makes it non-responsive for me, so that's the reason I've formulated my response in that way. It's not really a big deal for me (I can't stand fingerprints on that gorgeous display ). ATM I'm using kernel 4.5.
rc1 ? i cannot use it at all, it constantly freezes and stops working ..
rc1, then later rc2, but had rolled back to this release today, since supend/resume was spotty at best. I experienced no crashes or other instability running on 4.5, however.

so you are running intel's .. im on mineline

zetxx · 2016-02-02 18:22:35

sender wrote:

I guess I'll call it bad luck :-/
http://i.imgur.com/07Knbm3.jpg
The only writing on the wall was that on every other reboot everything was very slow (navigating bios, bootloading, DE, etc).
Just upgraded to BIOS v1.2.3 + 4.5-rc2 but had successful boots since.
Dell: in 3-4 weeks you'll hear about the swap.

you are second one with similar problem ..... i don't know what to think anymore, is this hardware is a peace of sh** or what ....

halka · 2016-02-02 19:07:54

OT: Maybe just quality control issues. Thankfully the hardware is still new; a buddy of mine is still doing the replacement dance after his 5th LCD panel came with same issues as the previous ones, and Dell's only sending refurbished HW.

diraimondo · 2016-02-03 07:23:21

Yesterday I used a kernel 4.5rc2 compiled by myself. My impressions:
- good: multimedia keys started to work, suspend continues to work as in my previous configuration (4.4);
- bad: touchscreen continues to stop after some suspend/resume cycle by lid and, very annoying, the touchpad sporadically stops to work for few seconds... nothing on the log!

I temporary switched back on 4.4: I'll try again in few days.

Tommylefunk · 2016-02-03 13:09:42

With BIOS update 1.2.3 and stock 4.4.1-1-ARCH I now get the following ACPI errors:

[ 240.210541] INFO: task kworker/0:2:64 blocked for more than 120 seconds.
[ 240.210552] Not tainted 4.4.1-1-ARCH #1
[ 240.210555] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.210561] kworker/0:2 D ffff880275b13b58 0 64 2 0x00000000
[ 240.210580] Workqueue: kacpid acpi_os_execute_deferred
[ 240.210585] ffff880275b13b58 ffffffff8137774a ffffffff81810500 ffff880275b9ac40
[ 240.210591] ffff880275b14000 ffff880271451700 ffff880275b9ac40 ffff880276966820
[ 240.210597] ffff88007628b050 ffff880275b13b70 ffffffff8158e03c 7fffffffffffffff
[ 240.210603] Call Trace:
[ 240.210612] [<ffffffff8137774a>] ? acpi_ut_repair_name+0x2a/0x74
[ 240.210622] [<ffffffff8158e03c>] schedule+0x3c/0x90
[ 240.210629] [<ffffffff81590ab3>] schedule_timeout+0x1b3/0x240
[ 240.210633] [<ffffffff8137774a>] ? acpi_ut_repair_name+0x2a/0x74
[ 240.210642] [<ffffffff8136c0c6>] ? acpi_ns_search_one_scope+0x25/0x45
[ 240.210649] [<ffffffff8136c235>] ? acpi_ns_search_and_enter+0x14f/0x1ab
[ 240.210656] [<ffffffff8158fd34>] __down_timeout+0x74/0xd0
[ 240.210662] [<ffffffff810bdb87>] ? down_timeout+0x37/0x60
[ 240.210666] [<ffffffff810bdb9c>] down_timeout+0x4c/0x60
[ 240.210673] [<ffffffff813478bf>] acpi_os_wait_semaphore+0x4c/0x67
[ 240.210679] [<ffffffff81367243>] acpi_ex_system_wait_mutex+0x3c/0x4d
[ 240.210686] [<ffffffff81359b28>] acpi_ds_begin_method_execution+0x13f/0x1d8
[ 240.210693] [<ffffffff81359db4>] acpi_ds_call_control_method+0x54/0x17b
[ 240.210698] [<ffffffff8136f3ab>] acpi_ps_parse_aml+0xaf/0x26f
[ 240.210703] [<ffffffff8136fc11>] acpi_ps_execute_method+0x14b/0x186
[ 240.210710] [<ffffffff8136a151>] acpi_ns_evaluate+0x1bb/0x247
[ 240.210717] [<ffffffff8135d6f9>] acpi_ev_asynch_execute_gpe_method+0xa0/0x105
[ 240.210723] [<ffffffff81346bce>] acpi_os_execute_deferred+0x14/0x20
[ 240.210731] [<ffffffff8108e21b>] process_one_work+0x14b/0x440
[ 240.210737] [<ffffffff8108e558>] worker_thread+0x48/0x4a0
[ 240.210744] [<ffffffff8108e510>] ? process_one_work+0x440/0x440
[ 240.210750] [<ffffffff8108e510>] ? process_one_work+0x440/0x440
[ 240.210755] [<ffffffff81093ff8>] kthread+0xd8/0xf0
[ 240.210761] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170
[ 240.210766] [<ffffffff81591e8f>] ret_from_fork+0x3f/0x70
[ 240.210771] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170

Additionally I still get the intel gpu drm error that was present in 4.3. I'm using the intel_agp and i915 in the initramfs:

[ 8200.818355] WARNING: CPU: 0 PID: 663 at drivers/gpu/drm/i915/intel_pm.c:3597 skl_update_other_pipe_wm+0x1e7/0x1f0 [i915]()
[ 8200.818357] WARN_ON(!wm_changed)
[ 8200.818359] Modules linked in:
[ 8200.818361] ...
[ 8200.818462] intel_gtt
[ 8200.818466] CPU: 0 PID: 663 Comm: Xorg Tainted: G W 4.4.1-1-ARCH #1
[ 8200.818468] Hardware name: Dell Inc. XPS 13 9350/0PWNCR, BIOS 1.2.3 01/08/2016
[ 8200.818470] 0000000000000000 00000000c1d62b7d ffff88007631f750 ffffffff812c7f39
[ 8200.818474] ffff88007631f798 ffff88007631f788 ffffffff810765b2 ffff880276862000
[ 8200.818477] ffff88007631f8bc ffff880276867000 0000000000000000 ffff88007631f828
[ 8200.818480] Call Trace:
[ 8200.818486] [<ffffffff812c7f39>] dump_stack+0x4b/0x72
[ 8200.818491] [<ffffffff810765b2>] warn_slowpath_common+0x82/0xc0
[ 8200.818495] [<ffffffff8107664c>] warn_slowpath_fmt+0x5c/0x80
[ 8200.818505] [<ffffffffa00f1f37>] skl_update_other_pipe_wm+0x1e7/0x1f0 [i915]
[ 8200.818515] [<ffffffffa00f219a>] skl_update_wm+0x25a/0x750 [i915]
[ 8200.818526] [<ffffffffa00f64de>] intel_update_watermarks+0x1e/0x30 [i915]
[ 8200.818539] [<ffffffffa015ed70>] haswell_crtc_enable+0x370/0x870 [i915]
[ 8200.818553] [<ffffffffa015a992>] intel_atomic_commit+0x492/0x1430 [i915]
[ 8200.818561] [<ffffffffa003339e>] ? drm_atomic_check_only+0x18e/0x590 [drm]
[ 8200.818567] [<ffffffffa00337d7>] drm_atomic_commit+0x37/0x60 [drm]
[ 8200.818572] [<ffffffffa00a3fb6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
[ 8200.818580] [<ffffffffa0021ea2>] drm_mode_set_config_internal+0x62/0x100 [drm]
[ 8200.818589] [<ffffffffa0026d92>] drm_mode_setcrtc+0x3d2/0x4f0 [drm]
[ 8200.818595] [<ffffffffa00187b2>] drm_ioctl+0x152/0x540 [drm]
[ 8200.818603] [<ffffffffa00269c0>] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
[ 8200.818613] [<ffffffff811f0b68>] do_vfs_ioctl+0x298/0x480
[ 8200.818620] [<ffffffff810824e1>] ? __set_task_blocked+0x41/0xa0
[ 8200.818627] [<ffffffff811fabe7>] ? __fget+0x77/0xb0
[ 8200.818630] [<ffffffff811f0dc9>] SyS_ioctl+0x79/0x90
[ 8200.818634] [<ffffffff81084fde>] ? SyS_rt_sigprocmask+0x8e/0xc0
[ 8200.818637] [<ffffffff81591b2e>] entry_SYSCALL_64_fastpath+0x12/0x71
[ 8200.818640] ---[ end trace 0e9f223c58ecdab8 ]---

Everything, including the graphics works fine, however I am having trouble to rewake up the system when the laptop lid was closed.
The system then does not come back and I have to hard reboot it.

Any ideas?

kgizdov · 2016-02-05 16:14:20

Tommylefunk, seems like you're trying to enable semaphores through the kernel boot parameters. If that's the case, you should know that's this feature is experimental if not completely broken at the moment. If that's not the case then the only thing I can suggest doing is to reflash your BIOS, reinstall your kernel and re-run mkinitcpio. Make sure you have the correct modules loaded in /etc/mkinitcpio.conf and don't put extra boot flags before making sure it all works. Then start adding one by one to identify the problem. I don't think this is an XPS 13 problem specifically, but a misconfiguration.

Make sure to read the wiki thoroughly and apply the fixes that are mentioned.

altoyr · 2016-02-06 08:17:08

Does somebody else have problems with his/her speakers?
The quality is awful, especially when there is more base involved or the volume is turned up more than 1/3.
It is this typical base *brrrbbrbrbrbrbrbbr* (I am sorry i do not know if there is an english word for this, in german it is "Boxen prellen")

I do not remember having this problem with win10

Tommylefunk · 2016-02-06 11:55:14

kgizdov wrote:

Tommylefunk, seems like you're trying to enable semaphores through the kernel boot parameters. If that's the case, you should know that's this feature is experimental if not completely broken at the moment. If that's not the case then the only thing I can suggest doing is to reflash your BIOS, reinstall your kernel and re-run mkinitcpio. Make sure you have the correct modules loaded in /etc/mkinitcpio.conf and don't put extra boot flags before making sure it all works. Then start adding one by one to identify the problem. I don't think this is an XPS 13 problem specifically, but a misconfiguration.
Make sure to read the wiki thoroughly and apply the fixes that are mentioned.

Thanks for the response.
However, I currently do not use any special kernel parameters. In the initcpio I load "nvme intel_agp i915".

I found out that the skl bug got reopened: https://bugs.freedesktop.org/show_bug.cgi?id=89055.

The other bug is probably due to issues in the new 1.2.3 firmware. I notice with the new firmware I get boot errors regarding an ACPI namespace lookup failure:

[ 6.314747] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[ 6.314751] ACPI Error: Method parse/execution failed [\_TZ.TZ00._TMP] (Node ffff88027810f730), AE_NOT_FOUND (20150930/psparse-542)
[ 6.314815] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[ 6.314817] ACPI Error: Method parse/execution failed [\_TZ.TZ00._TMP] (Node ffff88027810f730), AE_NOT_FOUND (20150930/psparse-542)
[ 6.314845] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[ 6.314847] ACPI Error: Method parse/execution failed [\_TZ.TZ01._TMP] (Node ffff88027810f7f8), AE_NOT_FOUND (20150930/psparse-542)
[ 6.314871] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[ 6.314872] ACPI Error: Method parse/execution failed [\_TZ.TZ01._TMP] (Node ffff88027810f7f8), AE_NOT_FOUND (20150930/psparse-542)
[ 6.316687] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[ 6.316691] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)
[ 6.316696] ACPI Error: Method parse/execution failed [\_TZ.FN00._ON] (Node ffff8802780deed8), AE_NOT_FOUND (20150930/psparse-542)
[ 6.316701] acpi PNP0C0B:00: Failed to change power state to D0
[ 6.323143] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[ 6.323147] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)
[ 6.323153] ACPI Error: Method parse/execution failed [\_TZ.FN00._ON] (Node ffff8802780deed8), AE_NOT_FOUND (20150930/psparse-542)

I assume this could be connected to the errors during runtime and not properly working sleep/suspend functionality.
Does anybody else have similar issues with the new firmware?

zetxx · 2016-02-06 12:17:46

Tommylefunk wrote:

kgizdov wrote:
Tommylefunk, seems like you're trying to enable semaphores through the kernel boot parameters. If that's the case, you should know that's this feature is experimental if not completely broken at the moment. If that's not the case then the only thing I can suggest doing is to reflash your BIOS, reinstall your kernel and re-run mkinitcpio. Make sure you have the correct modules loaded in /etc/mkinitcpio.conf and don't put extra boot flags before making sure it all works. Then start adding one by one to identify the problem. I don't think this is an XPS 13 problem specifically, but a misconfiguration.
Make sure to read the wiki thoroughly and apply the fixes that are mentioned.
Thanks for the response.
However, I currently do not use any special kernel parameters. In the initcpio I load "nvme intel_agp i915".
I found out that the skl bug got reopened: https://bugs.freedesktop.org/show_bug.cgi?id=89055.
The other bug is probably due to issues in the new 1.2.3 firmware. I notice with the new firmware I get boot errors regarding an ACPI namespace lookup failure:
[ 6.314747] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[ 6.314751] ACPI Error: Method parse/execution failed [\_TZ.TZ00._TMP] (Node ffff88027810f730), AE_NOT_FOUND (20150930/psparse-542)
[ 6.314815] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[ 6.314817] ACPI Error: Method parse/execution failed [\_TZ.TZ00._TMP] (Node ffff88027810f730), AE_NOT_FOUND (20150930/psparse-542)
[ 6.314845] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[ 6.314847] ACPI Error: Method parse/execution failed [\_TZ.TZ01._TMP] (Node ffff88027810f7f8), AE_NOT_FOUND (20150930/psparse-542)
[ 6.314871] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[ 6.314872] ACPI Error: Method parse/execution failed [\_TZ.TZ01._TMP] (Node ffff88027810f7f8), AE_NOT_FOUND (20150930/psparse-542)
[ 6.316687] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[ 6.316691] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)
[ 6.316696] ACPI Error: Method parse/execution failed [\_TZ.FN00._ON] (Node ffff8802780deed8), AE_NOT_FOUND (20150930/psparse-542)
[ 6.316701] acpi PNP0C0B:00: Failed to change power state to D0
[ 6.323143] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[ 6.323147] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)
[ 6.323153] ACPI Error: Method parse/execution failed [\_TZ.FN00._ON] (Node ffff8802780deed8), AE_NOT_FOUND (20150930/psparse-542)
I assume this could be connected to the errors during runtime and not properly working sleep/suspend functionality.
Does anybody else have similar issues with the new firmware?

yep, i think that everyone are experiencing acpi error which is due badly written bios

thenn42 · 2016-02-06 12:28:03

Tommylefunk wrote:

Does anybody else have similar issues with the new firmware?

I received my Dell xps 13 9350 QHD i7 16Gb 512ssd the other day.

I run BIOS firmware 1.2.3 and 4.4.1-2-ARCH and I don't use the intel_agp kernel parameter.
I have the same ACPI errors but I don't seem to get the same intel gpu drm errors however.

Well except for this error:
[drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* 5.4 Gbps link rate without HBR2/TPS3 support

Suspend works fine except for the touchscreen.

I also have a new issue since this morning but I'm not sure what changed (if anyone has any hints, I'm still looking into it):
[ 7.346178] ata3: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe
[ 7.346191] ata3: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
[ 7.346205] ata3: hard resetting link
[ 7.346224] ata2: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe
[ 7.346235] ata2: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
[ 7.346246] ata2: hard resetting link
[ 7.349518] ata1: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe
[ 7.349535] ata1: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }

Also, I can't seem to get my power usage lower than 6.5W with screen brightness at minimum and only i3 and a terminal running. (and more around 8-11W when actually using the computer).
Did anyone manage to reduce the power consumption more than that?

Thank you.

Last edited by thenn42 (2016-02-06 12:47:17)

diraimondo · 2016-02-06 16:05:02

thenn42 wrote:

I run BIOS firmware 1.2.3 and 4.4.1-2-ARCH and I don't use the intel_agp kernel parameter.

intel_agp is not a kernel parameter but a module that some suggest to load into the initramfs (see field MODULES in /etc/mkinitcpio.conf).

Suspend works fine except for the touchscreen.

touchscreen works for me but it stops on suspend/resume by lid.

Also, I can't seem to get my power usage lower than 6.5W with screen brightness at minimum and only i3 and a terminal running. (and more around 8-11W when actually using the computer).
Did anyone manage to reduce the power consumption more than that?

Have you tried kernel parameters "pcie_aspm=force i915.enable_rc6=7" in /etc/default/grub?

thenn42 · 2016-02-06 16:56:07

diraimondo wrote:

intel_agp is not a kernel parameter but a module that some suggest to load into the initramfs (see field MODULES in /etc/mkinitcpio.conf).

Thank you, I didn't notice the difference and had i915 in both my mkinitcpio.conf file and as a kernel parameter.

diraimondo wrote:

touchscreen works for me but it stops on suspend/resume by lid.

That's what I meant, the touchscreen stops working after closing the lid.

diraimondo wrote:

Have you tried kernel parameters "pcie_aspm=force i915.enable_rc6=7" in /etc/default/grub?

I'm currently running with those parameters but I didn't really notice a difference. (but I'm only glancing at powertop from time to time so I didn't do any rigorous testing yet).
As I'm typing on Chrome my computer is using about 12.2W.

Last edited by thenn42 (2016-02-06 16:57:30)

bart_vv · 2016-02-06 17:26:44

altoyr wrote:

Does somebody else have problems with his/her speakers?
The quality is awful, especially when there is more base involved or the volume is turned up more than 1/3.
It is this typical base *brrrbbrbrbrbrbrbbr* (I am sorry i do not know if there is an english word for this, in german it is "Boxen prellen")
I do not remember having this problem with win10

I think some of folks here encountered a similar problem, including me, but for me it was more noticeable with headphones. For me, it disappeared after upgrading to 4.4 few days ago (have been using linux-bcm4350 4.3-1 for quite some time). I have never updated my bios yet, and have audio controller powersave enabled in tlp.

Arch Linux

#276 2016-01-30 11:58:44

Re: Dell XPS 13 9350 Late 2015

#277 2016-01-30 14:55:46

Re: Dell XPS 13 9350 Late 2015

#278 2016-01-30 16:19:28

Re: Dell XPS 13 9350 Late 2015

#279 2016-01-30 23:00:21

Re: Dell XPS 13 9350 Late 2015

#280 2016-01-31 08:17:30

Re: Dell XPS 13 9350 Late 2015

#281 2016-01-31 08:27:30

Re: Dell XPS 13 9350 Late 2015

#282 2016-01-31 10:57:44

Re: Dell XPS 13 9350 Late 2015

#283 2016-02-01 14:54:47

Re: Dell XPS 13 9350 Late 2015

#284 2016-02-02 10:25:46

Re: Dell XPS 13 9350 Late 2015

#285 2016-02-02 10:52:03

Re: Dell XPS 13 9350 Late 2015

#286 2016-02-02 11:22:14

Re: Dell XPS 13 9350 Late 2015

#287 2016-02-02 17:57:22

Re: Dell XPS 13 9350 Late 2015

#288 2016-02-02 18:20:30

Re: Dell XPS 13 9350 Late 2015

#289 2016-02-02 18:22:35

Re: Dell XPS 13 9350 Late 2015

#290 2016-02-02 19:07:54

Re: Dell XPS 13 9350 Late 2015

#291 2016-02-03 07:23:21

Re: Dell XPS 13 9350 Late 2015

#292 2016-02-03 13:09:42

Re: Dell XPS 13 9350 Late 2015

#293 2016-02-05 16:14:20

Re: Dell XPS 13 9350 Late 2015

#294 2016-02-06 08:17:08

Re: Dell XPS 13 9350 Late 2015

#295 2016-02-06 11:55:14

Re: Dell XPS 13 9350 Late 2015

#296 2016-02-06 12:17:46

Re: Dell XPS 13 9350 Late 2015

#297 2016-02-06 12:28:03

Re: Dell XPS 13 9350 Late 2015

#298 2016-02-06 16:05:02

Re: Dell XPS 13 9350 Late 2015

#299 2016-02-06 16:56:07

Re: Dell XPS 13 9350 Late 2015

#300 2016-02-06 17:26:44

Re: Dell XPS 13 9350 Late 2015

Board footer