linux-kernel - Re: 3.5-rcX: USB support without udev?

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: <20120701232542.GA11680@gherkin.frus.com>
Date:	Sun, 1 Jul 2012 18:25:42 -0500
From:	Bob Tracy <rct@...rkin.frus.com>
To:	Henrik Rydberg <rydberg@...omail.se>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	Ming Lei <tom.leiming@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: 3.5-rcX: USB support without udev?

On Sun, Jul 01, 2012 at 10:41:18PM +0200, Henrik Rydberg wrote:
> > Kernel built from the standard kernel.org tree.  All
> > drivers needed at boot time are built-in, except now there's probably
> > something missing on the USB side of things.  No initrd.
> 
> Are modules turned off as well?

No.  The only drivers that are built-in are the ones I need at boot time
and/or continuously thereafter.  Everything else is modular.

> I cannot see your attached files, but is there any chance this is
> about HID, not USB?

Posted a follow-up message immediately when I realized I forgot to
include the config file :-(.  Yes, it very well *could* be a HID issue.
I was quick to blame it on a deprecated feature that finally got
removed, when this might well have been a "disguised" regression.

> > Per the syslog entries I included in my initial post on this thread, the
> > only difference between the pre- and post- usbfs removal cases seems to
> > be whatever is needed for the input subsystem to see the USB keyboard
> > and mouse.  I see the USB hubs and attached devices getting detected,
> > but whatever "glue" allows the keyboard and mouse to work isn't there,
> > and the input subsystem doesn't emit the expected messages at boot time.
> 
> If you did a 'make oldconfig' on anything prior to -rc5, chances are
> you do not have CONFIG_HID_GENERIC=y in your .config.

That might well be the missing "glue."  I'm building -rc5 as I type
this.  Should have an answer in a few hours.  Thanks for the clue!

--Bob
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/