[Ubuntu-x-swat] [Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2015-02-15 Thread Christopher M. Penalver
Typhoe, could you please test for this via http://cdimage.ubuntu.com
/daily-live/current/ and advise to the results?

** Tags added: latest-bios-223

** Attachment removed: BootDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040593/+files/BootDmesg.txt

** Attachment removed: BootLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040594/+files/BootLog.txt

** Attachment removed: CurrentDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040595/+files/CurrentDmesg.txt

** Attachment removed: Dependencies.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040596/+files/Dependencies.txt

** Attachment removed: DpkgLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040597/+files/DpkgLog.txt

** Attachment removed: HookError_source_xorg.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040598/+files/HookError_source_xorg.txt

** Attachment removed: Lspci.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040599/+files/Lspci.txt

** Attachment removed: Lsusb.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040600/+files/Lsusb.txt

** Attachment removed: ProcCpuinfo.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040602/+files/ProcCpuinfo.txt

** Attachment removed: ProcInterrupts.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040603/+files/ProcInterrupts.txt

** Attachment removed: ProcModules.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040604/+files/ProcModules.txt

** Attachment removed: UdevDb.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040605/+files/UdevDb.txt

** Attachment removed: UdevLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040606/+files/UdevLog.txt

** Attachment removed: XorgLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040607/+files/XorgLog.txt

** Attachment removed: XorgLogOld.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040608/+files/XorgLogOld.txt

** Attachment removed: xdpyinfo.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040610/+files/xdpyinfo.txt

** Attachment removed: Xrandr.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040609/+files/Xrandr.txt

** Attachment removed: xserver.devices.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040611/+files/xserver.devices.txt

** Attachment removed: xserver.outputs.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040612/+files/xserver.outputs.txt

** Attachment removed: BootDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040616/+files/BootDmesg.txt

** Attachment removed: BootLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040617/+files/BootLog.txt

** Attachment removed: CurrentDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040618/+files/CurrentDmesg.txt

** Attachment removed: Dependencies.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040619/+files/Dependencies.txt

** Attachment removed: DpkgLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040620/+files/DpkgLog.txt

** Attachment removed: HookError_source_xorg.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040621/+files/HookError_source_xorg.txt

** Attachment removed: Lspci.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040622/+files/Lspci.txt

** Attachment removed: Lsusb.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040623/+files/Lsusb.txt

** Attachment removed: ProcCpuinfo.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040624/+files/ProcCpuinfo.txt

** Attachment removed: ProcInterrupts.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040625/+files/ProcInterrupts.txt

** Attachment removed: ProcModules.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040626/+files/ProcModules.txt

** Attachment removed: UdevDb.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040627/+files/UdevDb.txt

** Attachment removed: UdevLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040632/+files/UdevLog.txt

** Attachment removed: XorgLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+attachment/4040637/+files/XorgLog.txt

** Attachment removed: XorgLogOld.txt
   

[Ubuntu-x-swat] [Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2015-02-15 Thread Typhoe
Hi,

just tried the latest nightly of ubuntu (2015/02/15 iso)
lsb_release -d
Description:Ubuntu Vivid Vervet (development branch)

Still no change... The monitor is detected when plugged in (appears in
dmesg) but it is not recognized by the system and thus, can't be use...

Status of the problem is still unchanged so far...

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@ubuntu:~$ dmesg
[  167.366484] usb 2-3: new SuperSpeed USB device number 6 using xhci_hcd
[  167.383178] usb 2-3: New USB device found, idVendor=17e9, idProduct=ff03
[  167.383196] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  167.383199] usb 2-3: Product: MB168B+
[  167.383202] usb 2-3: Manufacturer: DisplayLink
[  167.383204] usb 2-3: SerialNumber: DALMTF151588

root@ubuntu:/home/ubuntu# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 382mm x 215mm
   1920x1080  60.0*+   60.0 40.0  
[...]
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)

root@ubuntu:/home/ubuntu# xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x65 cap: 0x1, Source Output crtcs: 2 outputs: 4 associated 
providers: 0 name:nouveau

root@ubuntu:/home/ubuntu# ls -l /dev/fb*
crw-rw 1 root video 29, 0 Feb 15 21:04 /dev/fb0

root@ubuntu:/home/ubuntu# dpkg -l | grep ^ii *xserver-xorg-video-modesetting
ii  xserver-xorg-video-modesetting   0.9.0-1build1  
amd64X.Org X server -- Generic modesetting driver

root@ubuntu:/home/ubuntu# grep udl /etc/modprobe.d/blacklist-framebuffer.conf 
blacklist udlfb



** Changed in: xorg (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1296315

Title:
  Displaylink and ASUS MB168B+ not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2015-02-15 Thread Christopher M. Penalver
Typhoe, could you please test the latest upstream kernel available from
the very top line at the top of the page (the release names are
irrelevant for testing, and please do not test the daily folder)
following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into 
the OS) please make a comment in your report about this, and continue to test 
the next most recent kernel version until you can test to the issue. Once 
you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this bug is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results.

Thank you for your understanding.

** Package changed: xorg (Ubuntu) = linux (Ubuntu)

** Summary changed:

- Displaylink and ASUS MB168B+ not working
+ 17e9:ff03 Displaylink and ASUS MB168B+ not working

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1296315

Title:
  17e9:ff03 Displaylink and ASUS MB168B+ not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296315/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2014-07-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xorg (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1296315

Title:
  Displaylink and ASUS MB168B+ not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2014-06-25 Thread Richard A Hofer
I just got an MB168B+ and discovered that it has no linux support.
Display LInk has no released a driver for their new USB 3 chipsets. See 
http://displaylink.org/forum/showthread.php?t=1748
However, there is a petition to get them to release a driver: 
https://www.change.org/petitions/displaylink-support-linux-with-dl-3000-series-chips

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1296315

Title:
  Displaylink and ASUS MB168B+ not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2014-04-04 Thread Typhoe
Hi,

I don't have any xorg.conf file in /etc/ and its sub dirs.

So far, I didn't manage to get any positive result...

Regards.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1296315

Title:
  Displaylink and ASUS MB168B+ not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2014-03-24 Thread Typhoe
Additional tests:

udlfb is blacklisted by default in trusty:
 grep udl /etc/modprobe.d/blacklist-framebuffer.conf 
blacklist udlfb

Generic modesetting driver is also present by default:
dpkg -l | grep ^ii *xserver-xorg-video-modesetting
ii  xserver-xorg-video-modesetting  0.8.1-1build1   
   amd64X.Org X server -- Generic modesetting driver

After reading the Kernel/MainlineBuilds page, I tried a mainline kernel
https://wiki.ubuntu.com/Kernel/MainlineBuilds

I didn't found my kernel version on the mapping page (Trusty not indicated)
http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html

uname -a
Linux g75vw 3.13.0-19-generic #39-Ubuntu SMP Fri Mar 21 14:18:44 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

So I tried the kernel v3.13.7 as it seems the last of my version 
(configs-based-on-Ubuntu-3.13.0-19.40.patch)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.7-trusty/ 
linux-headers-3.13.7-031307_3.13.7-031307.201403240156_all.deb
linux-headers-3.13.7-031307-generic_3.13.7-031307.201403240156_amd64.deb
linux-image-3.13.7-031307-generic_3.13.7-031307.201403240156_amd64.deb
(no linux-image-extra deb as it is mainline?)

After a dpkg -i *.deb and a reboot, I still don't get any progress...
(manually modprobe udl, and trying to unplug/plug again the monitor)

uname -a
Linux g75vw 3.13.7-031307-generic #201403240156 SMP Mon Mar 24 05:57:41 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

Mar 24 11:39:11 g75vw kernel: [   80.303538] usbcore: registered new interface 
driver udl
Mar 24 11:39:39 g75vw kernel: [  107.757943] usb 4-3: USB disconnect, device 
number 3
Mar 24 11:39:48 g75vw kernel: [  116.561490] usb 4-3: new SuperSpeed USB device 
number 6 using xhci_hcd
Mar 24 11:39:48 g75vw mtp-probe: checking bus 4, device 6: 
/sys/devices/pci:00/:00:14.0/usb4/4-3
Mar 24 11:39:48 g75vw mtp-probe: bus: 4, device: 6 was not an MTP device
Mar 24 11:39:48 g75vw kernel: [  116.577674] usb 4-3: New USB device found, 
idVendor=17e9, idProduct=ff03
Mar 24 11:39:48 g75vw kernel: [  116.577680] usb 4-3: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Mar 24 11:39:48 g75vw kernel: [  116.577683] usb 4-3: Product: MB168B+
Mar 24 11:39:48 g75vw kernel: [  116.577685] usb 4-3: Manufacturer: DisplayLink
Mar 24 11:39:48 g75vw kernel: [  116.577688] usb 4-3: SerialNumber: DALMTF151588


** Tags added: apport-collected reproducible single-occurrence

** Description changed:

  Hi,
  
  I'm trying to use an USB3 external monitor Asus MB168B+ with displaylink
  technology.
  
  The monitor is detected by the kernel upon plug, but no driver seems to
  be loaded...
  
  My notebook is an ASUS G75VW
  sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date
  G75VW.223
  01/07/2013
  
  lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  
  apt-cache policy xorg
  xorg:
Installé : 1:7.7+1ubuntu8
Candidat : 1:7.7+1ubuntu8
   Table de version :
   *** 1:7.7+1ubuntu8 0
  500 http://ubuntu-archive.mirrors.free.org/ubuntu/ trusty/main amd64 
Packages
  100 /var/lib/dpkg/status
  
  uname -a
  Linux g75vw 3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:40:06 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  
  Mar 23 16:15:31 g75vw kernel: [13264.796466] usb 4-3: new SuperSpeed USB 
device number 6 using xhci_hcd
  Mar 23 16:15:31 g75vw kernel: [13264.812773] usb 4-3: New USB device found, 
idVendor=17e9, idProduct=ff03
  Mar 23 16:15:31 g75vw kernel: [13264.812780] usb 4-3: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Mar 23 16:15:31 g75vw kernel: [13264.812784] usb 4-3: Product: MB168B+
  Mar 23 16:15:31 g75vw kernel: [13264.812787] usb 4-3: Manufacturer: 
DisplayLink
  Mar 23 16:15:31 g75vw kernel: [13264.812790] usb 4-3: SerialNumber: 
DALMTF151588
  Mar 23 16:15:31 g75vw mtp-probe: checking bus 4, device 6: 
/sys/devices/pci:00/:00:14.0/usb4/4-3
  Mar 23 16:15:31 g75vw mtp-probe: bus: 4, device: 6 was not an MTP device
  
  xrandr
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  LVDS-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 382mm x 215mm
 1920x1080 60.0*+ 60.0 40.0
  ...
  VGA-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1 disconnected (normal left inverted right x axis y axis)
  DP-1 disconnected (normal left inverted right x axis y axis)
  
  xrandr --listproviders
  Providers: number : 1
  Provider 0: id: 0x65 cap: 0x1, Source Output crtcs: 2 outputs: 4 associated 
providers: 0 name:nouveau
  
  ls -l /dev/fb*
  crw-rw 1 root video 29, 0 mars 23 12:34 /dev/fb0
  
  regards
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 

[Ubuntu-x-swat] [Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2014-03-24 Thread arrith
You might find this thread useful:
https://bbs.archlinux.org/viewtopic.php?pid=1342095

If you find a process that works please report back.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1296315

Title:
  Displaylink and ASUS MB168B+ not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2014-03-24 Thread arrith
Very good tests! Good to know about udlfb being blacklisted by default
and xserver-xorg-video-modesetting being present by default, both good.

I find it interesting that xrandr --listproviders doesn't list
anything. Just to make sure, do you have an xorg.conf file?

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1296315

Title:
  Displaylink and ASUS MB168B+ not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2014-03-23 Thread Typhoe
sudo lsusb -d17e9:ff03 -vvv

Bus 004 Device 006: ID 17e9:ff03 DisplayLink 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.00
  bDeviceClass  239 Miscellaneous Device
  bDeviceSubClass 2 ?
  bDeviceProtocol 1 Interface Association
  bMaxPacketSize0 9
  idVendor   0x17e9 DisplayLink
  idProduct  0xff03 
  bcdDevice1.70
  iManufacturer   1 DisplayLink
  iProduct2 MB168B+
  iSerial 3 DALMTF151588
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  116
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0x80
  (Bus Powered)
MaxPower  126mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   4
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  0 
  bInterfaceProtocol  3 
  iInterface  0 
  ** UNRECOGNIZED:  0c 5f 01 00 0a 00 04 04 01 00 04 00
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x08  EP 8 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84  EP 4 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85  EP 5 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval   5
bMaxBurst   0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   0
  bInterfaceClass   254 Application Specific Interface
  bInterfaceSubClass  1 Device Firmware Update
  bInterfaceProtocol  1 
  iInterface  0 
  Device Firmware Upgrade Interface Descriptor:
bLength 9
bDescriptorType33
bmAttributes1
  Will Not Detach
  Manifestation Intolerant
  Upload Unsupported
  Download Supported
wDetachTimeout200 milliseconds
wTransferSize1024 bytes
bcdDFUVersion   1.01
  ** UNRECOGNIZED:  10 40 08 06 0c 08 02 09 46 66 6c 79 4d 6f 6e 69
Binary Object Store Descriptor:
  bLength 5
  bDescriptorType15
  wTotalLength   42
  bNumDeviceCaps  3
  USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType16
bDevCapabilityType  2
bmAttributes   0x0002
  Link Power Management (LPM) Supported
  SuperSpeed USB Device Capability:
bLength10
bDescriptorType16
bDevCapabilityType  3
bmAttributes 0x00
wSpeedsSupported   0x000e
  Device can operate at Full Speed (12Mbps)
  Device can operate at High Speed (480Mbps)
  Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport   2
  Lowest fully-functional device speed is High Speed (480Mbps)
bU1DevExitLat  10 micro seconds
bU2DevExitLat 366 micro seconds
  Container ID Device Capability:
bLength20
bDescriptorType16
bDevCapabilityType  4
bReserved   0
ContainerID {30a29107-ae36-1349-6d97-f02a0eda5f4a}
Device Status: 0x000c
  (Bus Powered)
  U1 Enabled
  U2 Enabled

-- 
You received this bug