mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: tytso@mit.edu, David Miller <davem@davemloft.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] X doesn't work with 2.6.33 (can't find any input  devices)
Date: Fri, 5 Mar 2010 15:11:53 +1000	[thread overview]
Message-ID: <21d7e9971003042111n5b5145c5sd9b62b53522cfd86@mail.gmail.com> (raw)
In-Reply-To: <20100305044054.GB5747@thunk.org>

On Fri, Mar 5, 2010 at 2:40 PM,  <tytso@mit.edu> wrote:
> On Wed, Mar 03, 2010 at 07:20:07AM -0800, David Miller wrote:
>> From: tytso@mit.edu
>> Date: Wed, 3 Mar 2010 10:17:20 -0500
>>
>> > It worked just *fine* using 2.6.33-rc4.  I have no xorg.conf file (X
>> > is autoconfiguring itself) and I'm using an Ubuntu 9.10 userspace.
>>
>> X uses udev events to find input devices these days, so it's probably
>> the same problem preventing your lvm devices from showing up correctly
>> from initramfs.
>
> It uses libhal, I believe to find input devices and I was finally able
> to work around the problem by configuring an manually recreated
> xorg.conf file with the magic option:
>
> Section "ServerFlags"
>        Option "AllowEmptyInput" "off"
> EndSection
>
> ... and then making sure that the kbd and mouse input drivers were
> installed.  There is definitely something wrong though if sometime
> between 2;6.33-rc4 and 2.6.33 we've made some incompatible sysfs
> change that breaks hal on Ubuntu 9.10 (which is still the latest
> Ubuntu community release), such that people can't test 2.6.33 kernels
> using it --- at least not easily.
>
> See Linus's complaints over the nouveau driver; it's the same
> principle; something is really broken.


Not really, this is just somebody doing something stupid one would hope,

does lshal on both kernels give similiar results?

Dave.

  reply	other threads:[~2010-03-05  5:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 15:17 tytso
2010-03-03 15:20 ` David Miller
2010-03-05  4:40   ` tytso
2010-03-05  5:11     ` Dave Airlie [this message]
2010-03-07  1:13       ` tytso
2010-03-05  5:18 ` Dave Airlie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21d7e9971003042111n5b5145c5sd9b62b53522cfd86@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®