linux-kernel - Re: [REGRESSION] X doesn't work with 2.6.33 (can't find any input devices)

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: <21d7e9971003042111n5b5145c5sd9b62b53522cfd86@mail.gmail.com>
Date:	Fri, 5 Mar 2010 15:11:53 +1000
From:	Dave Airlie <airlied@...il.com>
To:	tytso@....edu, David Miller <davem@...emloft.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [REGRESSION] X doesn't work with 2.6.33 (can't find any input 
	devices)

On Fri, Mar 5, 2010 at 2:40 PM,  <tytso@....edu> wrote:
> On Wed, Mar 03, 2010 at 07:20:07AM -0800, David Miller wrote:
>> From: tytso@....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.
--
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/