On Fri, Nov 23, 2012 at 10:29:53AM +0100, Henrik Grindal Bakken wrote: > Thierry Reding <thierry.red...@avionic-design.de> writes: > > > Hi, > > > > Would anyone know why the latest releases no longer work on 3.1 kernels? > > I tried to update from 187 to 196 today and booting the system on a > > vendor kernel based on 3.1.10 no longer gets to the boot prompt. It > > hangs somewhere near where it should actually be spawning a getty on > > the serial port. > > > > Booting systemd 196 on a kernel based on linux-next doesn't have this > > issue. I've gone over the NEWS entries between 187 and 196, but nothing > > obvious stood out. > > > > Any ideas? > > I'm running 196 just fine on a 3.0 vendor kernel, so it's not a > universal problem. I also use getty on the serial port, with no local > modifications. > > I believe the requirement for a 3.4 (or something) kernel came in 188 > for some logging bits, although I'm not sure. systemd should work > just fine without it, though.
Okay, maybe there's an issue with this particular version of the kernel or something's odd with my configuration. I'll have to dig deeper. Thanks for the information. Thierry
pgpqfoyZHu51D.pgp
Description: PGP signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
