lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <461B9DFF.9080704@aitel.hist.no>
Date:	Tue, 10 Apr 2007 16:23:59 +0200
From:	Helge Hafting <helge.hafting@...el.hist.no>
To:	Dmitry Torokhov <dtor@...ightbb.com>
CC:	Helge Hafting <helgehaf@...el.hist.no>,
	linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net
Subject: Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?

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

Download attachment "debug_initcall.gz" of type "application/gzip" (7674 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ