Re: keyboard dead with 45b5035

2008-02-18 Thread Pierre Ossman
On Mon, 18 Feb 2008 21:50:12 +0100 Pierre Ossman <[EMAIL PROTECTED]> wrote: > On Mon, 18 Feb 2008 20:50:01 +0100 > "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote: > > > On Monday, 18 of February 2008, Pierre Ossman wrote: > > > The patch "[RTNETLINK]: Send a single notification on device state >

Re: keyboard dead with 45b5035

2008-02-18 Thread Pierre Ossman
On Mon, 18 Feb 2008 20:50:01 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote: > On Monday, 18 of February 2008, Pierre Ossman wrote: > > The patch "[RTNETLINK]: Send a single notification on device state > > changes." kills (at least) > > the keyboard here. Everything seems to work fine in si

Re: keyboard dead with 45b5035

2008-02-18 Thread Rafael J. Wysocki
On Monday, 18 of February 2008, Pierre Ossman wrote: > The patch "[RTNETLINK]: Send a single notification on device state changes." > kills (at least) > the keyboard here. Everything seems to work fine in single user mode, but > when init starts > spawning of logins, the keyboard goes bye-bye. Ev

Re: keyboard dead with 45b5035 - Regression in 2.6.25-rc2

2008-02-18 Thread Larry Finger
> The patch "[RTNETLINK]: Send a single notification on device state changes." kills (at least) the > keyboard here. Everything seems to work fine in single user mode, but when init starts spawning of > logins, the keyboard goes bye-bye. Even the power button is ignored. :/ > > I've tried just c

keyboard dead with 45b5035

2008-02-18 Thread Pierre Ossman
The patch "[RTNETLINK]: Send a single notification on device state changes." kills (at least) the keyboard here. Everything seems to work fine in single user mode, but when init starts spawning of logins, the keyboard goes bye-bye. Even the power button is ignored. :/ I've tried just creating a