Hi,

one of the upgrades I did yesterday disabled the keyboard of my smartbook (Debian SID).

I think it was the udev upgrade which complained that udev would need a kernel > 2.6.32. I tried to solve the problem by downgrading udev from 175-5 to 175-3.1, but I didn't get the keyboard to work again. As I still have a SD-card without the update I have access to the broken installation on the internal disk and can chroot it. Any help is very much appreciated. The list with the updates I made yesterday follows.

===============================================================================
[UPGRADE] bind9-host:armhf 1:9.8.1.dfsg.P1-4.1 -> 1:9.8.1.dfsg.P1-4.2
[UPGRADE] bzip2:armhf 1.0.6-3 -> 1.0.6-4
[UPGRADE] consolekit:armhf 0.4.5-3 -> 0.4.5-3.1
[UPGRADE] debianutils:armhf 4.3.2 -> 4.3.3
[UPGRADE] e2fslibs:armhf 1.42.4-3 -> 1.42.5-1
[UPGRADE] e2fsprogs:armhf 1.42.4-3 -> 1.42.5-1
[UPGRADE] host:armhf 1:9.8.1.dfsg.P1-4.1 -> 1:9.8.1.dfsg.P1-4.2
[UPGRADE] imagemagick:armhf 8:6.7.7.10-2 -> 8:6.7.7.10-3
[UPGRADE] imagemagick-common:armhf 8:6.7.7.10-2 -> 8:6.7.7.10-3
[UPGRADE] iptables:armhf 1.4.14-2 -> 1.4.14-3
[UPGRADE] libbind9-80:armhf 1:9.8.1.dfsg.P1-4.1 -> 1:9.8.1.dfsg.P1-4.2
[UPGRADE] libbz2-1.0:armhf 1.0.6-3 -> 1.0.6-4
[UPGRADE] libck-connector0:armhf 0.4.5-3 -> 0.4.5-3.1
[UPGRADE] libcomerr2:armhf 1.42.4-3 -> 1.42.5-1
[UPGRADE] libdns81:armhf 1:9.8.1.dfsg.P1-4.1 -> 1:9.8.1.dfsg.P1-4.2
[UPGRADE] libgl1-mesa-dri:armhf 8.0.3-1 -> 8.0.4-1
[UPGRADE] libgl1-mesa-glx:armhf 8.0.3-1 -> 8.0.4-1
[UPGRADE] libglapi-mesa:armhf 8.0.3-1 -> 8.0.4-1
[UPGRADE] libglu1-mesa:armhf 8.0.3-1 -> 8.0.4-1
[UPGRADE] libgudev-1.0-0:armhf 175-3.1 -> 175-5
[UPGRADE] libisc83:armhf 1:9.8.1.dfsg.P1-4.1 -> 1:9.8.1.dfsg.P1-4.2
[UPGRADE] libisccc80:armhf 1:9.8.1.dfsg.P1-4.1 -> 1:9.8.1.dfsg.P1-4.2
[UPGRADE] libisccfg82:armhf 1:9.8.1.dfsg.P1-4.1 -> 1:9.8.1.dfsg.P1-4.2
[UPGRADE] liblwres80:armhf 1:9.8.1.dfsg.P1-4.1 -> 1:9.8.1.dfsg.P1-4.2
[UPGRADE] libmagickcore5:armhf 8:6.7.7.10-2 -> 8:6.7.7.10-3
[UPGRADE] libmagickwand5:armhf 8:6.7.7.10-2 -> 8:6.7.7.10-3
[UPGRADE] libpam-ck-connector:armhf 0.4.5-3 -> 0.4.5-3.1
[UPGRADE] libss2:armhf 1.42.4-3 -> 1.42.5-1
[UPGRADE] libssl1.0.0:armhf 1.0.1c-3 -> 1.0.1c-4
[UPGRADE] libudev0:armhf 175-3.1 -> 175-5
[UPGRADE] libwrap0:armhf 7.6.q-23 -> 7.6.q-24
[UPGRADE] openssl:armhf 1.0.1c-3 -> 1.0.1c-4
[UPGRADE] tcpd:armhf 7.6.q-23 -> 7.6.q-24
[UPGRADE] udev:armhf 175-3.1 -> 175-5
===============================================================================

Robert

Yeah, that's why it's called unstable :) it's been like that since the beginning on unstable. markos's script just edits a udev script to get around that. you will want to boot from some working image and then mount the root fs of the broken image and run this sed command:


where $TARGETROOT is the path to the mounted root filesystem for the broken image.

the new kernel is on it's way soon and then we won't have to worry about doing things like this anymore.

also if you don't want to mess around with sed and are comfortable with shell scripts just edit /etc/init.d/udev directly and make sure your version of the kernel doesn't cause the supported_kernel() shell function to return 1.

the sed script should work though.

Let me know if this doesn't work.

Yeah, but it happens also with testing, wait... ;-)
It is very much anticipated.
It worked, thank you very much.