On 25/06/14 14:38, Ben Caradoc-Davies wrote:
The only changes that were made to udev in 204-11 are [1] and [2]
If so, could you both try to revert those two patches one by one,
rebuild the initrd and see if that makes a change
I will try this next.

Michael, manually reverting your [1] and running "update-initramfs -u" allowed me to boot with udev 204-11:

[1] http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=f11a2ddeb6a43f99179f2f9d322ee08cb41db5b0

I did not test your [2] as I do not think we are that unlucky.  :-)

Kind regards,
Ben.


# dpkg -l udev libudev1
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
ii  libudev1:amd64 204-11       amd64        libudev shared library
ii  libudev1:i386  204-11       i386         libudev shared library
ii udev 204-11 amd64 /dev/ and hotplug management daem


# diff -Naur udev/80-drivers.rules /lib/udev/rules.d/80-drivers.rules
--- udev/80-drivers.rules       2014-06-25 14:43:18.856941146 +0800
+++ /lib/udev/rules.d/80-drivers.rules  2014-06-25 14:44:15.002258945 +0800
@@ -9,6 +9,6 @@
 SUBSYSTEM=="i2o", RUN{builtin}="kmod load i2o_block"
 SUBSYSTEM=="module", KERNEL=="parport_pc", RUN{builtin}="kmod load ppdev"
KERNEL=="mtd*ro", ENV{MTD_FTL}=="smartmedia", RUN{builtin}="kmod load sm_ftl" -SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST!="[module/sg]", RUN{builtin}="kmod load sg" +SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST!="[module/sg]", RUN+="kmod sg"

 LABEL="drivers_end"


--
Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to