usbhid bug

[Tuftec]

Hi,

I have been noticing some small issues with the current TC kernel 3.6.33.3.
On my system (eBox PC (x86) with usb mouse, usb keyboard and usb touch screen) I keep getting an error message reported in DMSEG.
drivers/hid/usbhid/hid-core.c: usb_submit_urb(ctrl) failed

I do not know what this means and whether or not it is significant but I have observed that it takes quite some time for my mouse to be recognised after boot.

Interestingly, the RT build of TC in the repository does not give the same symptom. It does not report the usbhid error.

I have also been struggling to get an eGalax touchcreen to work under TC. From what I have now learnt, I believe that this is a known issue in the Linux kernel and appears to have been resolved from kernels 3.3.34 onwards.

When is the next kernel release update likely to be included in TC (which one?) and if this is sometime off, is there some way to solve my problem in the short term?

Unfortunately my skills are limited and I do not know how to upgrade the kernel myself. Ideally I would like to be able to use an upgraded version of the RT version of TC.



Thanks

Peter.

[gerald_clark]

My eBox-2300 runs without a problem.

[curaga]

kernel 3.0, in TC 4.0.

[Tuftec]

How can I get hold of Tc 4.0 to test, even if an early alpha version at this stage?
Is the RT PREMPT patch in kernel 3.0?

Peter.

[curaga]

There are no alphas yet, and RT is not in mainline yet either.

[Tuftec]

I am still stuck then.
I love Tiny Core and want to persist with it for my application.
Can someone help me with some sort of short term patch then.
Here is a link to the proble with the touch screen
https://patchwork.kernel.org/patch/6107/

I have no idea how to apply this information to fix the issue.

On the other issue with the usbhib error message, I have done some more testing. It seems to be somehow connected to my usb mouse, keyboard and hub that I am using.
I will investigate further.


Thanks

Peter.

[maro]

Here is a link to the proble with the touch screen
https://patchwork.kernel.org/patch/6107/

I have no idea how to apply this information to fix the issue.

I had a quick look into the Linux 2.6.33.3 sources that were used to build the kernel for TC 3.x. It looks to me as if that one-line patch from 2009 had already been part of the respective file (i.e. 'drivers/input/touchscreen/usbtouchscreen.c'). So I'm not sure where that leaves your search for a different outcome.

[Tuftec]

Yeah.
Thanks for that, I had a bit of a search and found the same.
So it appears that I have a touch screen that is not supported under Linux but works on Windows.

I have tried the screen on other h/w with TC and I have tried the screen with different versions of Linux (Watt OS, Unbuntu, Mint and Puppy) but without any real success. I have just been trying to see if the kernel drivers recognise the screen at this point.

I will post elsewhere to see if I can find a solution.
I may have to try some alternate drivers.


Thanks

[Rich]

Hi Tuftec
Have you looked at these two links?
http://wiki.linuxmce.org/index.php/Egalax-Touchscreen
http://home.eeti.com.tw/web20/eGalaxTouchDriver/linuxDriver.htm
This note is from the second link

1.   If the kernel module "usbhid" , "touchkitusb" or "usbtouchscreen" is loaded for USB touch device, the user has to modify the mouse setting in the file "xorg.conf" as well to prevent from the mouse driver read the data from the specified device node.
For details, please see the driver guide in the driver package.

If you boot with the mouse unplugged, does that change anything?

[Tuftec]

I have tried booting with the mouse unplug. No joy!
I gather this note is to prevent the mouse and touch screen from interacting. I doubt that it would stop the driver from actually loading the hooks necessary to make the touchscreen actually work. No event device entry is created in /dev as I would expect.

[Tuftec]

I used the latest drivers off the EETI site.
I used the setup.sh script to do the install and then added what I thought were the appropriate directories/files to .filetool.lst to give persistence after boot.
I did find that I had to link /etc/X11/xorg.conf to my existing xorg.conf.vesa.
? I am not sure whether this is actually correct.
Maybe I have inadvertently set XVESA instead of XORG??? How do I check this???
If I have it wrong, how do I change it to XORG.
I have xorg7.5 loaded as a module.

Peter.

 

[maro]

A (simplistic) check which X server is running: ps | grep X , and to confirm which one is meant to be used for the next call of 'startx': cat /etc/sysconfig/Xserver

The '/etc/X11/xorg.conf.vesa' is a kind of sample file, on it's own it won't interfere with the default mode (i.e. confless) when using 'Xorg'. Therefore whenever I need a '/etc/X11/xorg.conf' file I just copy it accross (symlinking might also work, but as '/etc/X11/xorg.conf.vesa' is a symlink into a read-only file system you then won't be able to edit the content of '/etc/X11/xorg.conf').

[Rich]

Hi Tuftec
According to the documentation included with the driver package you downloaded, when using a
HID device you should blacklist the touchkitusb and usbtouchscreen modules and use the usbhid
module.

[Tuftec]

How do I blacklist these modules?
If I simply do not load the input-touchscreen module, would this not achieve the same thing.
I think the usbtouchscreen module is in this (but I might be wrong).

I have tried just using the basic TC core only which I thought might not have the usbtouchscreen module and would only have the hid components.

I will try blacklisting if someone can tell me how to do this.

Peter.

[Juanito]

How do I blacklist these modules?

boot code "blacklist=module_name"