Re: Ubuntu on Dell Xps 15 9550 new Infinity display (i7 6gen 16gbr UHD 4k touch

[everc]

Hello everyone, I hope you can offer me some guidance because I'm about to lose it!

After following this thread for the past months and seeing that things started to work fine I decided to get this machine for work, where I will mainly use Linux. The main specs:

6th Generation Intel(R) Core (TM) i7-6700HQ Quad Core (6M Cache, up to 3.5 GHz)
15.6" 4K Ultra HD (3840 x 2160) InfinityEdge touch
16GB (2x8GB) 2133MHz DDR4 Memory
Module,DD,1T,S3,5.4,7MM,SEAHAWK
NVIDIA GTX960M 2Go DDR5

So, first day, I arrived to the office and found this beautiful thing on my desk. I boot it up, enter the Windows 10 configuration, select English language, click next aaaand... Blue Screen Of Death!! (I kid you not) The machine restarts, and never goes beyond the Dell logo. Either freezes there (when some balls are going in circles), or simply enters a restart infinite loop.

I've got no desire to deal with Dell's technical support and, since I plan to exclusively use Linux, I want to completely delete Windows and install Ubuntu.

So, USB stick with Ubuntu 15.10. I configure the BIOS with: disabled Secure Boot, AHCI, and boot the live version with nomodeset (without it often freezes, as reported by others). When I enter the installation no device is found. With gparted I see:

• /dev/sda: unallocated 29.82GB
• /dev/sdb1: fat32 - ESP - 500MB
• /dev/sdb2: unknown - MS reserved partition - 128MB
• /dev/sdb3: ntfs - OS - 918.39 GB
• /dev/sdb4: ntfs - WINRETOOLS - 893MB
• /dev/sdb5: ntfs - image - 11.64GB
• /dev/sdc1: usb stick

My questions are:

• Can I delete all the sdb* partitions safely? Should I keep the Dell recovery partition? Which one is it btw?
• How can I get to see the partitions from the installer?

[bertusrex]

Hello everyone, I hope you can offer me some guidance because I'm about to lose it!

After following this thread for the past months and seeing that things started to work fine I decided to get this machine for work, where I will mainly use Linux. The main specs:

6th Generation Intel(R) Core (TM) i7-6700HQ Quad Core (6M Cache, up to 3.5 GHz)
15.6" 4K Ultra HD (3840 x 2160) InfinityEdge touch
16GB (2x8GB) 2133MHz DDR4 Memory
Module,DD,1T,S3,5.4,7MM,SEAHAWK
NVIDIA GTX960M 2Go DDR5

So, first day, I arrived to the office and found this beautiful thing on my desk. I boot it up, enter the Windows 10 configuration, select English language, click next aaaand... Blue Screen Of Death!! (I kid you not) The machine restarts, and never goes beyond the Dell logo. Either freezes there (when some balls are going in circles), or simply enters a restart infinite loop.

I've got no desire to deal with Dell's technical support and, since I plan to exclusively use Linux, I want to completely delete Windows and install Ubuntu.

So, USB stick with Ubuntu 15.10. I configure the BIOS with: disabled Secure Boot, AHCI, and boot the live version with nomodeset (without it often freezes, as reported by others). When I enter the installation no device is found. With gparted I see:

• /dev/sda: unallocated 29.82GB
• /dev/sdb1: fat32 - ESP - 500MB
• /dev/sdb2: unknown - MS reserved partition - 128MB
• /dev/sdb3: ntfs - OS - 918.39 GB
• /dev/sdb4: ntfs - WINRETOOLS - 893MB
• /dev/sdb5: ntfs - image - 11.64GB
• /dev/sdc1: usb stick

My questions are:

• Can I delete all the sdb* partitions safely? Should I keep the Dell recovery partition? Which one is it btw?
• How can I get to see the partitions from the installer?

If it's BSOD-ing right out of the box before Windows is even configured, I'd run diagnostics first (press F12 at Dell boot logo, then choose diagnostics from boot menu). If you've got a faulty laptop, running Ubuntu is not going to fix that.

[everc]

If it's BSOD-ing right out of the box before Windows is even configured, I'd run diagnostics first (press F12 at Dell boot logo, then choose diagnostics from boot menu). If you've got a faulty laptop, running Ubuntu is not going to fix that.

That's true. I did the test, everything seems to be ok

Did you disable the fast boot? http://www.tenforums.com/tutorials/4...dows-10-a.html
When fast boot is turned on, it does not even allow me to mount the windows partition from my ubuntu. Make sure it is turned off.

I wonder if this has something to do with it, but I cannot boot into windows.

I boot off usb stick using the UEFI option. After the ubuntu live launches, I can see my disks in gparted (/dev/sda /dev/sdb), partitions are correctly detected (/dev/sdb1, /dev/sdb2 and so on) and I can mount them, but the Ubuntu installer doesn't see them.

Did you manage to solve that?

[alberink-stampfini]

Did anyone get the Logitech MX Anywhere2 mouse to run on kernel 4.4? I'm trying to do this, but the guides posted before do not work for me. Which is sad, as I'm now blocking a precious USB port with a Unified Receiver dongle...

[bertusrex]

Did anyone get the Logitech MX Anywhere2 mouse to run on kernel 4.4? I'm trying to do this, but the guides posted before do not work for me. Which is sad, as I'm now blocking a precious USB port with a Unified Receiver dongle...

I'm using this mouse with kernel 4.4 (4.4 rc8, but also 4.2, 4.3, other 4.4 rc's). I suppose you already found this post? If you describe how far you got and have some logs I might be able to compare it to my setup.

[alberink-stampfini]

I'm using this mouse with kernel 4.4 (4.4 rc8, but also 4.2, 4.3, other 4.4 rc's). I suppose you already found this post? If you describe how far you got and have some logs I might be able to compare it to my setup.

Yeah, found that post as well... But this is what I see:

[bluetooth]# power on[CHG] Controller 18:4F:32:F7:FF:EE Class: 0x4c010c
Changing power on succeeded
[CHG] Controller 18:4F:32:F7:FF:EE Powered: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller 18:4F:32:F7:FF:EE Discovering: yes
[CHG] Device E0:33:3B:74:61:00 RSSI: -96
[CHG] Device E0:33:3B:74:61:00 TxPower: 4
[CHG] Device E0:33:3B:74:61:00 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[NEW] Device FB:C3:2A:4E:8D:FD One
[CHG] Device E0:33:3B:74:61:00 RSSI: -83
[CHG] Device FB:C3:2A:4E:8D:FD TxPower: -6
[bluetooth]# trust E0:33:3B:74:61:00 
Changing E0:33:3B:74:61:00 trust succeeded
[bluetooth]# pair E0:33:3B:74:61:00 
Attempting to pair with E0:33:3B:74:61:00
[CHG] Device E0:33:3B:74:61:00 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationTimeout
[CHG] Device E0:33:3B:74:61:00 Connected: no
[bluetooth]# pair E0:33:3B:74:61:00 
Attempting to pair with E0:33:3B:74:61:00
[CHG] Device E0:33:3B:74:61:00 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationFailed
[CHG] Device E0:33:3B:74:61:00 Connected: no
[CHG] Device E0:33:3B:74:61:00 RSSI: -73
[bluetooth]# pair E0:33:3B:74:61:00 
Attempting to pair with E0:33:3B:74:61:00
[CHG] Device E0:33:3B:74:61:00 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationFailed
[CHG] Device E0:33:3B:74:61:00 Connected: no

AS you can see, authentication fails... Bluetoothd is started with the -E parameter, but not via a hack in the init file. That won't work if you use systemd.

[bertusrex]

Yeah, found that post as well... But this is what I see:

[bluetooth]# power on[CHG] Controller 18:4F:32:F7:FF:EE Class: 0x4c010c
Changing power on succeeded
[CHG] Controller 18:4F:32:F7:FF:EE Powered: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller 18:4F:32:F7:FF:EE Discovering: yes
[CHG] Device E0:33:3B:74:61:00 RSSI: -96
[CHG] Device E0:33:3B:74:61:00 TxPower: 4
[CHG] Device E0:33:3B:74:61:00 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[NEW] Device FB:C3:2A:4E:8D:FD One
[CHG] Device E0:33:3B:74:61:00 RSSI: -83
[CHG] Device FB:C3:2A:4E:8D:FD TxPower: -6
[bluetooth]# trust E0:33:3B:74:61:00 
Changing E0:33:3B:74:61:00 trust succeeded
[bluetooth]# pair E0:33:3B:74:61:00 
Attempting to pair with E0:33:3B:74:61:00
[CHG] Device E0:33:3B:74:61:00 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationTimeout
[CHG] Device E0:33:3B:74:61:00 Connected: no
[bluetooth]# pair E0:33:3B:74:61:00 
Attempting to pair with E0:33:3B:74:61:00
[CHG] Device E0:33:3B:74:61:00 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationFailed
[CHG] Device E0:33:3B:74:61:00 Connected: no
[CHG] Device E0:33:3B:74:61:00 RSSI: -73
[bluetooth]# pair E0:33:3B:74:61:00 
Attempting to pair with E0:33:3B:74:61:00
[CHG] Device E0:33:3B:74:61:00 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationFailed
[CHG] Device E0:33:3B:74:61:00 Connected: no

AS you can see, authentication fails... Bluetoothd is started with the -E parameter, but not via a hack in the init file. That won't work if you use systemd.

Some quick suggestions:
- Did you put your mouse in pairing mode when trying to pair? (connect button at the bottom).
- I've had pairing problems under windows when wifi is enabled. Maybe try pairing with wifi disabled?

other options worth trying:
- update /lib/firmware from http://git.kernel.org/cgit/linux/ker...x-firmware.git
- reset bios to factory defaults

[ghostcode]

Any of you are having problem when press the space bar on the corner of the key? In my case it does not work (print the space) only when I press in the middle. I am not sure if it is a keyboard design problem or my key that is not working.

[bertusrex]

Any of you are having problem when press the space bar on the corner of the key? In my case it does not work (print the space) only when I press in the middle. I am not sure if it is a keyboard design problem or my key that is not working.

All 4 corners work on mine (although not all have the same 'feeling'). A 'sticky' spacebar is a common problem with XPS 15's, that might be related to yours. To see if anything is wrong underneath your spacebar you can remove it and put it back quite easily, see e.g. here for a video.

[maxweld]

Sorry - removed to correct part of this Topic