You are not logged in.

#1 2014-09-18 08:49:28

xedchou
Member
Registered: 2014-02-27
Posts: 23

Remove "unable to read config index 0 descriptor/start" once for all?

Hey guys, I know there are people in the forums posted the similar questions, and yes, "dmesg -n 1" works.

So I'm here to find answers for remove this printk messages once for all:). After googling for 3 days, there isn't
really a good answer. You know what, I don't given crap about touchscreen feature,it is totally a "Chicken rib".
Is there any way to prevent kernel to find "new devices" and give me that damn message.

usb 2-7: new full-speed USB device number 106 using xhci_hcd

I did my research, some guy from this linkhttp://superuser.com/questions/729894/l … ug-related
tried to remove the touchscreen modules and some other debug features from kernel. Well, I tried, it didn't work.

I also tried to write udev rules but that shouldn't be related to the problem.

So far the only method that proved works is to disable xhci_hcd module. But all the devices lost it's connection:(.

Since all the devices lost their connections after I disable the xhci_hcd module. Is there any way that I disable some
modules then kernel will not care about the touchscreen anymore? Or the only way I can do is to write a patch to Kernel:rolleyes

PS. I've seen someone complained and said "it is a hardware problem, there is little software can do", you mean my touch-
screen port just send a damaged "config head" to CPU every two bytes?  I really believe it is certainly the problem of module code.

Any help, please?

Last edited by xedchou (2014-09-18 14:23:58)

Offline

#2 2014-09-18 14:25:03

xedchou
Member
Registered: 2014-02-27
Posts: 23

Re: Remove "unable to read config index 0 descriptor/start" once for all?

I found removing usbhid module is  not helpful either, looks like writing patches is the only way...

Last edited by xedchou (2014-09-18 14:25:54)

Offline

Board footer

Powered by FluxBB