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

On Thu, Mar 4, 2010 at 1:17 AM,  <tytso@....edu> wrote:
> After working around lvm breakage so I could at least boot 2.6.33, I'm
> now finding the next problem --- X doesn't work.  If I let X come up,
> it doesn't find any mouse or keyboard devices, so my machine becomes
> useless and I have to power cycle it unless I can log in remotely and
> reboot it.
>
> 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.
>
> I've enclosed the dmesg output (which shows the input devices
> correctly being detected by the kernel) and the Xorg.0.log file from
> the previous boot, where X does not come up.
>
> At this point, I'm not going to be able to dogfood test my ext4
> patches I plan to push to Linus, since 2.6.33 is completely useless to
> me.  Hopefully running the regression tests under KVM is going to have
> to be good enough.
>

Are you using 32 on 64 or anything like that?

15e184afa83a45cf8bafdb9dc906b97a8fbc974f is the only thing I can
see that might be close to changing something.

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/