usb touchscreen breakage in 2.6.21-rc5-mm4 ?

usb touchscreen breakage in 2.6.21-rc5-mm4 ?

[Helge Hafting]

I have an usb  touchscreen (egalax variety) that works with
the 2.6.18 kernel supplied by debian.

It fails when I compile 2.6.21-rc5-mm4, tuned to the machine
in question.  Unlike the debian kernel, this kernel don't use
modules in order to save boot time.

The strange thing is, 2.6.21-rc5-mm4 recognizes the device.
dmesg says things like 
usb 3-2: Manufacturer: eGalac Inc.
usb 3-2: Product: USB TouchController

and a lot more. Unlike 2.6.18, it never gets around to say
"usbcore: registered new driver usbtouchscreen"
which seems to indicate a problem.
usbcore registers several other drivers, such as usbserial and pl2303
that makes the gps work. It also registers other drivers like
usb-storage,usbfs,hub,libusual,hiddev,usbhid.  But not usbtouchscreen.
I believe I have turned on every config option for usb touchscreen,
this should not be missing.

Is there something wrong, or could there be a seemingly unrelated option
that I need to turn on?

Helge Hafting

Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?

[Dmitry Torokhov]

On Friday 06 April 2007 20:54, Helge Hafting wrote:
> I have an usb  touchscreen (egalax variety) that works with
> the 2.6.18 kernel supplied by debian.
> 
> It fails when I compile 2.6.21-rc5-mm4, tuned to the machine
> in question.  Unlike the debian kernel, this kernel don't use
> modules in order to save boot time.
> 
> The strange thing is, 2.6.21-rc5-mm4 recognizes the device.
> dmesg says things like 
> usb 3-2: Manufacturer: eGalac Inc.
> usb 3-2: Product: USB TouchController
> 
> and a lot more. Unlike 2.6.18, it never gets around to say
> "usbcore: registered new driver usbtouchscreen"
> which seems to indicate a problem.
> usbcore registers several other drivers, such as usbserial and pl2303
> that makes the gps work. It also registers other drivers like
> usb-storage,usbfs,hub,libusual,hiddev,usbhid.  But not usbtouchscreen.
> I believe I have turned on every config option for usb touchscreen,
> this should not be missing.
> 
> Is there something wrong, or could there be a seemingly unrelated option
> that I need to turn on?

Please make sure that you have CONFIG_USB_TOUCHSCREEN turned on.

-- 
Dmitry

Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?

[Helge Hafting]

On Fri, Apr 06, 2007 at 10:37:12PM -0400, Dmitry Torokhov wrote:
> On Friday 06 April 2007 20:54, Helge Hafting wrote:
> > I have an usb  touchscreen (egalax variety) that works with
> > the 2.6.18 kernel supplied by debian.
> > 
> > It fails when I compile 2.6.21-rc5-mm4, tuned to the machine
> > in question.  Unlike the debian kernel, this kernel don't use
> > modules in order to save boot time.
> > 
> > The strange thing is, 2.6.21-rc5-mm4 recognizes the device.
> > dmesg says things like 
> > usb 3-2: Manufacturer: eGalac Inc.
> > usb 3-2: Product: USB TouchController
> > 
> > and a lot more. Unlike 2.6.18, it never gets around to say
> > "usbcore: registered new driver usbtouchscreen"
> > which seems to indicate a problem.
> > usbcore registers several other drivers, such as usbserial and pl2303
> > that makes the gps work. It also registers other drivers like
> > usb-storage,usbfs,hub,libusual,hiddev,usbhid.  But not usbtouchscreen.
> > I believe I have turned on every config option for usb touchscreen,
> > this should not be missing.
> > 
> > Is there something wrong, or could there be a seemingly unrelated option
> > that I need to turn on?
> 
> Please make sure that you have CONFIG_USB_TOUCHSCREEN turned on.
> 
Unfortunately, I have:
CONFIG_USB_TOUCHSCREEN=y
CONFIG_USB_TOUCHSCREEN_EGALAX=y

Anything else I may have missed?

Helge Hafting

Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?

[Andrew Morton]

On Tue, 10 Apr 2007 00:36:43 +0200
Helge Hafting <helgehaf@aitel.hist.no> wrote:

> On Fri, Apr 06, 2007 at 10:37:12PM -0400, Dmitry Torokhov wrote:
> > On Friday 06 April 2007 20:54, Helge Hafting wrote:
> > > I have an usb  touchscreen (egalax variety) that works with
> > > the 2.6.18 kernel supplied by debian.
> > > 
> > > It fails when I compile 2.6.21-rc5-mm4, tuned to the machine
> > > in question.  Unlike the debian kernel, this kernel don't use
> > > modules in order to save boot time.
> > > 
> > > The strange thing is, 2.6.21-rc5-mm4 recognizes the device.
> > > dmesg says things like 
> > > usb 3-2: Manufacturer: eGalac Inc.
> > > usb 3-2: Product: USB TouchController
> > > 
> > > and a lot more. Unlike 2.6.18, it never gets around to say
> > > "usbcore: registered new driver usbtouchscreen"
> > > which seems to indicate a problem.
> > > usbcore registers several other drivers, such as usbserial and pl2303
> > > that makes the gps work. It also registers other drivers like
> > > usb-storage,usbfs,hub,libusual,hiddev,usbhid.  But not usbtouchscreen.
> > > I believe I have turned on every config option for usb touchscreen,
> > > this should not be missing.
> > > 
> > > Is there something wrong, or could there be a seemingly unrelated option
> > > that I need to turn on?
> > 
> > Please make sure that you have CONFIG_USB_TOUCHSCREEN turned on.
> > 
> Unfortunately, I have:
> CONFIG_USB_TOUCHSCREEN=y
> CONFIG_USB_TOUCHSCREEN_EGALAX=y
> 
> Anything else I may have missed?
> 

Is 2.6.21-rc6 OK?

If so, please keep a close eye on 2.6.22-rcX, let us know if/when we've
moved this breakage into mainline :(

Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?

[Dmitry Torokhov]

On Monday 09 April 2007 18:36, Helge Hafting wrote:
> On Fri, Apr 06, 2007 at 10:37:12PM -0400, Dmitry Torokhov wrote:
> > On Friday 06 April 2007 20:54, Helge Hafting wrote:
> > > I have an usb  touchscreen (egalax variety) that works with
> > > the 2.6.18 kernel supplied by debian.
> > > 
> > > It fails when I compile 2.6.21-rc5-mm4, tuned to the machine
> > > in question.  Unlike the debian kernel, this kernel don't use
> > > modules in order to save boot time.
> > > 
> > > The strange thing is, 2.6.21-rc5-mm4 recognizes the device.
> > > dmesg says things like 
> > > usb 3-2: Manufacturer: eGalac Inc.
> > > usb 3-2: Product: USB TouchController
> > > 
> > > and a lot more. Unlike 2.6.18, it never gets around to say
> > > "usbcore: registered new driver usbtouchscreen"
> > > which seems to indicate a problem.
> > > usbcore registers several other drivers, such as usbserial and pl2303
> > > that makes the gps work. It also registers other drivers like
> > > usb-storage,usbfs,hub,libusual,hiddev,usbhid.  But not usbtouchscreen.
> > > I believe I have turned on every config option for usb touchscreen,
> > > this should not be missing.
> > > 
> > > Is there something wrong, or could there be a seemingly unrelated option
> > > that I need to turn on?
> > 
> > Please make sure that you have CONFIG_USB_TOUCHSCREEN turned on.
> > 
> Unfortunately, I have:
> CONFIG_USB_TOUCHSCREEN=y
> CONFIG_USB_TOUCHSCREEN_EGALAX=y
> 
> Anything else I may have missed?
>

Hmm, I am concerned because not only you don't have an input device created,
you don't even see the driver being registered with usbcore. Could you please
try booting with debug_initcall to see with what error code usbtouchscreen
initialization fails?


-- 
Dmitry

Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?

[Helge Hafting]

[-- Attachment #1: Type: text/plain, Size: 484 bytes --]

Dmitry Torokhov wrote:
> Hmm, I am concerned because not only you don't have an input device created,
> you don't even see the driver being registered with usbcore. Could you please
> try booting with debug_initcall to see with what error code usbtouchscreen
> initialization fails?
>   
Here is the dmesg from a boot with debug_initcall.
I can't see any messages from usbtouchscreen.
For me, it looks like the touchscreen is discovered and then
nothing happens to it.

Helge Hafting

[-- Attachment #2: debug_initcall.gz --]
[-- Type: application/gzip, Size: 7674 bytes --]

Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?

[Helge Hafting]

Andrew Morton wrote:
> Is 2.6.21-rc6 OK?
>
> If so, please keep a close eye on 2.6.22-rcX, let us know if/when we've
> moved this breakage into mainline :(
>   

2.6.21-rc6 is ok.
Here, I get messages from usbtouchscreen, something
rc5-mm4 failed to produce.
The egalax driver gets /class/input/input3,
usbcore registers usbtouchscreen, and the
touchscreen works. 

Well, it became /dev/input/event3 while
2.6.18 placed it at /dev/input/event1, but I think that
is more of a udev problem...

Helge Hafting

Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?

[Dmitry Torokhov]

On 4/10/07, Helge Hafting <helge.hafting@aitel.hist.no> wrote:
> Dmitry Torokhov wrote:
> > Hmm, I am concerned because not only you don't have an input device created,
> > you don't even see the driver being registered with usbcore. Could you please
> > try booting with debug_initcall to see with what error code usbtouchscreen
> > initialization fails?
> >
> Here is the dmesg from a boot with debug_initcall.
> I can't see any messages from usbtouchscreen.
> For me, it looks like the touchscreen is discovered and then
> nothing happens to it.
>

*sigh* When will I learn to spell names of kernel parameters
correctly? It is initcall_debug, not debug_initcall :( Could you try
again, please?

-- 
Dmitry

Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?

[Helge Hafting]

[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]

Dmitry Torokhov wrote:
>
> *sigh* When will I learn to spell names of kernel parameters
> correctly? It is initcall_debug, not debug_initcall :( Could you try
> again, please?
Here is the dmesg for rc5mm4 with initcall_debug, showing how
no usbtouch function is called at all.

I also attached a similiar dmesg for 2.6.21-rc6, where things work
normally. 

I also decompressed the rc5mm4 image, to check
that USB touchscreen really is compiled into this image. These
USB options are on:
CONFIG_USB_HID=y
CONFIG_USB_HIDDEV=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
CONFIG_USB_DEBUG=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_DEVICE_CLASS=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_UHCI_HCD=y
CONFIG_USB_STORAGE=y
CONFIG_USB_STORAGE_DEBUG=y
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_STORAGE_ALAUDA=y
CONFIG_USB_LIBUSUAL=y
CONFIG_USB_TOUCHSCREEN=y
CONFIG_USB_TOUCHSCREEN_EGALAX=y
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_PL2303=y

Helge Hafting

[-- Attachment #2: initcall_debugrc5mm4.gz --]
[-- Type: application/gzip, Size: 15606 bytes --]

[-- Attachment #3: initcall_debugrc6.gz --]
[-- Type: application/gzip, Size: 11044 bytes --]

Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?

[Dmitry Torokhov]

On 4/11/07, Helge Hafting <helge.hafting@aitel.hist.no> wrote:
> Dmitry Torokhov wrote:
> >
> > *sigh* When will I learn to spell names of kernel parameters
> > correctly? It is initcall_debug, not debug_initcall :( Could you try
> > again, please?
> Here is the dmesg for rc5mm4 with initcall_debug, showing how
> no usbtouch function is called at all.
>

Helge,

I don't have any explanation why we don't see usbtouch_init called at
all in -rc5-mm4. Could it be toolchain misbehaving? Do you see
references to usbtouch_init in the kernel image itself?

-- 
Dmitry

Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?

[Helge Hafting]

On Wed, Apr 11, 2007 at 10:37:11AM -0400, Dmitry Torokhov wrote:
> On 4/11/07, Helge Hafting <helge.hafting@aitel.hist.no> wrote:
> >Dmitry Torokhov wrote:
> >>
> >> *sigh* When will I learn to spell names of kernel parameters
> >> correctly? It is initcall_debug, not debug_initcall :( Could you try
> >> again, please?
> >Here is the dmesg for rc5mm4 with initcall_debug, showing how
> >no usbtouch function is called at all.
> >
> 
> Helge,
> 
> I don't have any explanation why we don't see usbtouch_init called at
> all in -rc5-mm4. Could it be toolchain misbehaving? Do you see
> references to usbtouch_init in the kernel image itself?
> 
I unpacked it, ran "strings" on it, and found no usbtouch in there.
There were plenty of other usb names, such as usbfs, usbserial, usbcore
and tons of messages that usb mass storage and usb serial might
need to produce.

Versions of some tools, I don't know if there are any
known issues:

$ gcc --version
gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
$ ld --version
GNU ld (GNU Binutils for Debian) 2.17.50.20070406
$ dpkg -l binutils
ii  binutils       2.17.20070406c The GNU assembler, linker and binary

Helge Hafting