Unsolved

This post is more than 5 years old

20 Posts

5966375

October 31st, 2015 01:00

XPS13 9350 skylake no wifi on Ubuntu 15.10

With Ubuntu 15.10 (default kernel 4.2), 9350 almost works out of box, except this DW1820A wireless card. It has been a few days, I still couldn't get the wireless card working. From what I have read on Linux Wireless, BCM4350 driver is queued to be included in kernel 4.4. That's a long wait. 

Could anyone help?

19 Posts

November 8th, 2015 16:00

This doesn't seem to work nor generate the 0001-* file, even with the suggested "--" added after the -1.

root@ubuntu:/usr/src/net-next# git format-patch -1 e3c92db
fatal: ambiguous argument 'e3c92db': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [ ...] -- [ ...]'

any idea?

19 Posts

November 8th, 2015 18:00

I confirm, that worked for me and, for the record, with full root encryption too (ie: it didn't screw up the complex boot process).
Thanks a lot, I can get rid of that cheap USB dongle... ;-)

Cheers!

November 9th, 2015 07:00

I've gotten the Dell D3100 Docking station working with the Dell XPS 13 9350. Here are the steps I took:

  1. Download DisplayLink Drivers: http://www.displaylink.com/downloads/ubuntu.php
  2. Install dkms: sudo apt-get install dkms
  3. Follow Steps below:

With the displaylink and monitor connected:

  • Extract the sources from the binarie
    • ./displaylink-driver-1.0.138.run --keep --noexec
    • cd displaylink-driver-1.0.138/
    • make the .run script executable before you try to run it:
      sudo chmod +x displaylink-driver-1.0.138.run 
  • Link Kbuild on Makefile (required to find headers) (Kbuild was already linked in Xubuntu 15.10)
    • cd /lib/modules/$(uname -r)/build
    • sudo ln -s Makefile Kbuild
  • Uninstall my previous installation (if already installed)
    • sudo ./displaylink-installer.sh uninstall
    • sudo rmmod evdi
  • edit the installer (displaylink-installer.sh) used in previous step and change
    • line 10: SYSTEMINITDAEMON=systemd
    • line 13:ATTR{idVendor}=="17e9" instead of ATTR{idVendor}=="179"
  • run the installer
    • sudo ./displaylink-installer.sh install

  • Then you should be able to see a new provider: xrandr --listproviders
  • The displaylink is the provider 1 named "modesetting"
    Connect it to provider 0: xrandr --setprovideroutputsource 1 0
  • Go to display settings and enable monitors
  • Or use xrandr to setup displays.

What may not work:
- unplug and plug again your monitor
- when removing the displaylink, xrandr still display the provider 1, need a reboot to make it disappear.

Directions from DisplayLink: 
http://support.displaylink.com/knowledgebase/articles/684649-how-to-install-displaylink-software-on-ubuntu

20 Posts

November 9th, 2015 08:00

I got stuck at:

make -j `getconf _NPROCESSORS_ONLN` deb-pkg LOCALVERSION=-custom

which returns:

HOSTCC scripts/sign-file
scripts/sign-file.c:23:30: fatal error: openssl/opensslv.h: No such file or directory
compilation terminated.
scripts/Makefile.host:91: recipe for target 'scripts/sign-file' failed

19 Posts

November 9th, 2015 10:00

From this page you should try and install those packages and start over :

sudo apt-get install git build-essential kernel-package fakeroot libncurses5-dev libssl-dev ccache

17 Posts

November 9th, 2015 10:00

I got stuck at:

make -j `getconf _NPROCESSORS_ONLN` deb-pkg LOCALVERSION=-custom

which returns:

HOSTCC scripts/sign-file
scripts/sign-file.c:23:30: fatal error: openssl/opensslv.h: No such file or directory
compilation terminated.
scripts/Makefile.host:91: recipe for target 'scripts/sign-file' failed

Do you have libssl-dev installed? If not, go ahead and install that.

17 Posts

November 9th, 2015 10:00

I've gotten the Dell D3100 Docking station working with the Dell XPS 13 9350. Here are the steps I took:

  1. Download DisplayLink Drivers: http://www.displaylink.com/downloads/ubuntu.php
  2. Install dkms: sudo apt-get install dkms
  3. Follow Steps below:

With the displaylink and monitor connected:

  • Extract the sources from the binarie
    • ./displaylink-driver-1.0.138.run --keep --noexec
    • cd displaylink-driver-1.0.138/
    • make the .run script executable before you try to run it:
      sudo chmod +x displaylink-driver-1.0.138.run 
  • Link Kbuild on Makefile (required to find headers) (Kbuild was already linked in Xubuntu 15.10)
    • cd /lib/modules/$(uname -r)/build
    • sudo ln -s Makefile Kbuild
  • Uninstall my previous installation (if already installed)
    • sudo ./displaylink-installer.sh uninstall
    • sudo rmmod evdi
  • edit the installer (displaylink-installer.sh) used in previous step and change
    • line 10: SYSTEMINITDAEMON=systemd
    • line 13:ATTR{idVendor}=="17e9" instead of ATTR{idVendor}=="179"
  • run the installer
    • sudo ./displaylink-installer.sh install

  • Then you should be able to see a new provider: xrandr --listproviders
  • The displaylink is the provider 1 named "modesetting"
    Connect it to provider 0: xrandr --setprovideroutputsource 1 0
  • Go to display settings and enable monitors
  • Or use xrandr to setup displays.

What may not work:
- unplug and plug again your monitor
- when removing the displaylink, xrandr still display the provider 1, need a reboot to make it disappear.

Directions from DisplayLink: 
http://support.displaylink.com/knowledgebase/articles/684649-how-to-install-displaylink-software-on-ubuntu

Yup, these are the instructions I followed and I get a hard crash (looks like it's related to a Null dereference in the kernel) with the D1000 when I set my display to extended in xrandr.


Would you mind providing more information about your computer:
- FHD/QHD
- Processor
- Kernel version (uname -r). If you're not on the 4.3-custom kernel that I outlined in my post, would you mind pointing to where/how you got yours?
- Xorg/xrandr configurations
- Monitor brand / size / resolution / input cable type

Sorry, I know that's a lot to ask, but I'd love to get the D1000 working and I refuse to believe it's any different from the D3100 under the hood.

17 Posts

November 9th, 2015 10:00

I've gotten the Dell D3100 Docking station working with the Dell XPS 13 9350. Here are the steps I took:

  1. Download DisplayLink Drivers: http://www.displaylink.com/downloads/ubuntu.php
  2. Install dkms: sudo apt-get install dkms
  3. Follow Steps below:

With the displaylink and monitor connected:

  • Extract the sources from the binarie
    • ./displaylink-driver-1.0.138.run --keep --noexec
    • cd displaylink-driver-1.0.138/
    • make the .run script executable before you try to run it:
      sudo chmod +x displaylink-driver-1.0.138.run 
  • Link Kbuild on Makefile (required to find headers) (Kbuild was already linked in Xubuntu 15.10)
    • cd /lib/modules/$(uname -r)/build
    • sudo ln -s Makefile Kbuild
  • Uninstall my previous installation (if already installed)
    • sudo ./displaylink-installer.sh uninstall
    • sudo rmmod evdi
  • edit the installer (displaylink-installer.sh) used in previous step and change
    • line 10: SYSTEMINITDAEMON=systemd
    • line 13:ATTR{idVendor}=="17e9" instead of ATTR{idVendor}=="179"
  • run the installer
    • sudo ./displaylink-installer.sh install

  • Then you should be able to see a new provider: xrandr --listproviders
  • The displaylink is the provider 1 named "modesetting"
    Connect it to provider 0: xrandr --setprovideroutputsource 1 0
  • Go to display settings and enable monitors
  • Or use xrandr to setup displays.

What may not work:
- unplug and plug again your monitor
- when removing the displaylink, xrandr still display the provider 1, need a reboot to make it disappear.

Directions from DisplayLink: 
http://support.displaylink.com/knowledgebase/articles/684649-how-to-install-displaylink-software-on-ubuntu


Yup, these are the instructions I followed and I get a hard crash (looks like it's related to a Null dereference in the kernel) with the D1000 when I set my display to extended in xrandr.


Would you mind providing more information about your computer:
- FHD/QHD
- Processor
- Kernel version (uname -r). If you're not on the 4.3-custom kernel that I outlined in my post, would you mind pointing to where/how you got yours?
- Xorg/xrandr configurations
- Monitor brand/size/res

Sorry, I know that's a lot to ask, but I'd love to get the D1000 working with my current configuration and refuse to believe that it's any different from the D3100 under the hood.

November 9th, 2015 10:00

I got the d3100 to work with the instructions on the dell xps 13 9350 (new one, +QHD, i7) with 2 dell e220h (i think that's what they are) running hdmi @ 1920x1080.

I ran through those instructions from a Xubuntu 15.10 install liveUSB, so the kernel was whatever comes with that. Haven't tried yet after updating the kernel to 4.3+

Hope this helps! 

20 Posts

November 9th, 2015 13:00

No. I didn't have libssl-dev installed. Then, I installed it, and compiling works. Now, I have installed the 4.3-custom kernel. But, I am not sure how can reboot into the new kernel. My uname -r still returns 4.2.0-17-generic after reboot.

17 Posts

November 10th, 2015 06:00

Skyred:

Try holding "Shift" during the Dell Logo (BIOS) and until a GRUB menu shows up, go then in advanced and choose the first custom kernel. If it doesn't work, reboot and try again, some times it seems to skip it...


As for me, it seems that custom kernel disabled touch screen (not that I really care but...) and so it seems to be the only thing I lost up till now, though I don't have the cable (yet) to test Type-C -> DisplayPort monitor, did anyone get to test an external monitor?

I believe that's only an intermittent issue. My touch screen works just fine 90% of the time.

It seems that the Type-C -> DisplayPort connector uses DisplayLink as well, so I'd guess we're out of luck until we fix our kernels.

17 Posts

November 10th, 2015 06:00

I can get in GRUB advanced boot options for Ubuntu. That's no problem. The problem is that under advanced options I don't see the custom kernel I compiled, following the previous instructions. 

I installed my custom kernel twice via dpkg. I don't see any error messages. But, still don't see the option to boot the custom kernel.

Make sure to pay close attention for warnings when you're building/loading your kernel image. It sounds like it's not being placed in the bootloader. Maybe try building from scratch and installing and post the output of the install here?

19 Posts

November 10th, 2015 06:00

Skyred:

Try holding "Shift" during the Dell Logo (BIOS) and until a GRUB menu shows up, go then in advanced and choose the first custom kernel. If it doesn't work, reboot and try again, some times it seems to skip it...


As for me, it seems that custom kernel disabled touch screen (not that I really care but...) and so it seems to be the only thing I lost up till now, though I don't have the cable (yet) to test Type-C -> DisplayPort monitor, did anyone get to test an external monitor?

20 Posts

November 10th, 2015 06:00

I can get in GRUB advanced boot options for Ubuntu. That's no problem. The problem is that under advanced options I don't see the custom kernel I compiled, following the previous instructions. 

I installed my custom kernel twice via dpkg. I don't see any error messages. But, still don't see the option to boot the custom kernel.

1 Message

November 11th, 2015 00:00

I can get in GRUB advanced boot options for Ubuntu. That's no problem. The problem is that under advanced options I don't see the custom kernel I compiled, following the previous instructions. 

I installed my custom kernel twice via dpkg. I don't see any error messages. But, still don't see the option to boot the custom kernel.

I had the same issue, no initrd being generated or placed in /boot.

The following worked perfectly for me and I saw dpkg generate the initrd and place it in /boot appropriately.

$ cd ~
$ wget en.community.dell.com/.../brcmfmac4350_2D00_pcie.zip
$ unzip brcmfmac4350_2D00_pcie.zip
$ sudo mv brcmfmac4350-pcie.bin /lib/firmware/brcm/
$ sudo chmod 600 /lib/firmware/brcm/brcmfmac4350-pcie.bin
$ sudo apt-get install git build-essential kernel-package fakeroot libncurses5-dev libssl-dev ccache
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd net-next
$ git format-patch -1 e3c92cb
$ cp 0001-brcmfmac-Add-support-for-the-BCM4350-PCIE-device.patch ../linux/
$ cd ../linux
$ git fetch git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack cod/tip/drm-intel-nightly/2015-11-05
$ git checkout FETCH_HEAD
$ git am --reject 0001-brcmfmac-Add-support-for-the-BCM4350-PCIE-device.patch
$ cp /boot/config-`uname -r` .config
$ make oldconfig
$ yes '' | make oldconfig
$ make clean
$ cd ../
$ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-wily.git
$ cp -a /usr/share/kernel-package ubuntu-package
$ cp ubuntu-wily/debian/control-scripts/{postinst,postrm,preinst,prerm} ubuntu-package/pkg/image/
$ cp ubuntu-wily/debian/control-scripts/headers-postinst ubuntu-package/pkg/headers/
$ cd linux
$ CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom --overlay-dir=$HOME/ubuntu-package kernel_image kernel_headers
$ cd ../
$ sudo dpkg -i linux-image-4.3.0-custom-dbg_4.3.0-custom-1_amd64.deb
$ sudo dpkg -i linux-headers-4.3.0-custom_4.3.0-custom-1_amd64.deb

No Events found!

Top