linux-kernel - [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-next>] [day] [month] [year] [list]

Date:	Wed, 3 Mar 2010 10:17:20 -0500
From:	tytso@....edu
To:	linux-kernel@...r.kernel.org
Subject: [REGRESSION] X doesn't work with 2.6.33 (can't find any input
 devices)

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.

Grumble.

						- Ted

View attachment "dmesg.busted" of type "text/plain" (64141 bytes)

View attachment "Xorg.0.log-busted" of type "text/plain" (42308 bytes)