[21:46] <melodie> hi
[21:47] <melodie> can someone help me to help someone who has trouble with USB 3 and usb_xhci_platform on a Trusty Ubuntu official install (appearantly up to date) ?
[21:47] <melodie> I also have a vm with a Trusty 14.04.2 install runnning and have done a research on the XHCI drivers in the config of the kernel and in the system and seeing the results I thought I'd come here for more insights.
[22:16] <melodie> funny, the kernel has USB_XHCI_PLATFORM enabled as "module" in the config-`uname -r` kernel, but not available in the /lib/modules/* directory
[22:17] <melodie> the default stock kernel 
[22:17] <melodie> I can provide the thread on the forum, if someone here reads French
[22:19] <apw> melodie, what module name are you looking for for that config item, on vivid at least i have xhci-plat-hcd.ko
[22:20] <melodie> apw I have seen it in vivid too
[22:20] <melodie> I am testing in vbox trusty installing vivid-lts kernel packages
[22:20] <melodie> I will reboot the vm very soon
[22:21] <apw> but do you have that module name in /lib/module, as that is the module that is made by that config item
[22:21] <melodie> it is not me who has usb 3 trouble, it's a buddy on a forum
[22:21] <melodie> in trusty /lib/module does not have ANY xhci module
[22:21] <melodie> whatsoever
[22:21] <melodie> of any kind
[22:22] <apw> what packages do they have installed
[22:22] <apw> for the kernel, linux-image ?  linux-image-extra?
[22:22] <melodie> http://forum.malekal.com/probleme-reconnaissance-cle-usb-32go-t51085.html
[22:22] <melodie>  yes I got him to install linux-image-extra-virtual
[22:24] <melodie> he has 3.13.0-52-generic x86_64
[22:24] <melodie> he said in Ubuntu 14.04 32 bits not problem and in Ubuntu 14.04 64bits he can't have USB3 32 GB stick work in the USB3 hub
[22:24] <melodie> but he can use it in usb2 hub
[22:25] <melodie> I think perhaps he did have linux-image-extra in 32bits, but not sure really.
[22:25] <melodie> he met with other issues meanwhile which we try to fix
[22:26] <apw> -rw-r--r-- root/root     11204 2015-05-20 11:41 ./lib/modules/3.19.0-18-generic/kernel/drivers/usb/host/xhci-plat-hcd.ko
[22:27] <apw> the module is in th linux-lts-vivid -extras package
[22:27] <apw> on 64bit packages
[22:27] <melodie> yes same here in Vivid, but in Trusty with some kernels 3.13.0-52-generic x86_64 and other 3.13.0* previously installed, none
[22:28] <melodie> apw so is that only in 64bits packages that it happens and in 32bits packages the stock kernel would provide the xhci modules?
[22:28] <melodie> (so I would understand the situation clearly)
[22:28] <apw> no they would be in the same split
[22:28] <melodie> but there is none at all
[22:29] <melodie> no xhci in Trusty with the default kernel
[22:30] <melodie> if they are compiled with the "y" option in the config-* file, it should still appear under /lib/modules/* but no *xhci* at all appears
[22:32] <apw> no it seems there is a special for that option on trusty
[22:32] <melodie> also: are we sure that xhci-plat-hcd.ko stands for USB_XHCI_PLATFORM ?
[22:32] <apw> ifneq ($(CONFIG_USB_XHCI_PLATFORM), )
[22:32] <apw>         xhci-hcd-y              += xhci-plat.o
[22:32] <apw> endif
[22:33] <apw> so it is part of xhci-hcd and builtin
[22:33] <melodie> which means what exactly? (in current words?)
[22:33] <apw> even if =m
[22:33] <melodie> =m but so far modprobe on the name returns "no such file"
[22:34] <melodie> I felt concerned about this issue because Trusty is a LTS, and because nowadays USB3 comes more and more used by the people 
[22:34] <apw> right, its a frig, =m does not make a module there
[22:35] <melodie> excuse me, English is not my native language. What does the word "frig" mean?
[22:35] <apw> bodge
[22:35] <melodie> a bug?
[22:35] <apw> not normal behavior
[22:35] <melodie> ok
[22:35] <melodie> so did we lift a bug here?
[22:36] <apw> not bug, just unexpected meaning of the option i think
[22:36] <melodie> do you have the possibility to talk about that to some people in charge with the kernels in Ubuntu Trusty LTS?
[22:38] <apw> i am saying that it is built, and builtin i believe even though =m
[22:38] <melodie> how is that possible? I have built some of my kernels in the paste times, and "y" is builtin and "m" needs to be loaded at boot
[22:39] <apw> yes that is what it means normally
[22:39] <apw> and in vivid, it does
[22:41] <melodie> and when checking with command lines, to have it loaded we can check either by a grep on the chain in the config file or by a find in the /lib/modules directory. Else, the module isn't available : which explains that this guy keeps hitting his bottom on the floor: the usb3 sticks (32gb) are detected only when plugged in a USB2 hub or direct connector. No USB3 hub or direct connector could see it so far (dmidecode, lshw and lspci checked)
[22:41] <apw> obj-$(CONFIG_USB_XHCI_PLATFORM) += xhci-plat-hcd.o
[22:41] <melodie> something must have gone wrong on the way
[22:42] <apw> is vivid, so it has normal behavior
[22:42] <melodie> I'll advice him to try with the vivid kernels
[22:42] <apw> but trusty has different code
[22:42] <apw> yep, do
[22:42] <melodie> kernel kernel headers and linux-image-extra from vivid
[22:43] <melodie> anyway it might be interesting to let the people in charge know about that, they might want to have a look into it
[22:43] <melodie> ?
[22:45] <apw> file a bug about it, it might be related to
[22:45] <apw> obj-$(CONFIG_USB_XHCI_HCD)      += xhci-hcd.o
[22:45] <apw> if that is =m as well
[22:50] <melodie> I can't file a but about it, I would need to have a similar usb3 32gb stick as this guy has which I don't have.
[22:50] <melodie> if I file a bug I need to be able to test what needs to be tested 
[22:50] <melodie> or it serves no purpose
[22:51] <melodie> this is why the persons in charge of those kernels should be called in so they can check.
[22:52] <melodie> if supposedly they do have usb sticks needing xhci_* modules
[23:04] <melodie> apw thanks for your help