On Sat, Jul 18, 2015 at 10:41:17AM +0300, Michael Tokarev wrote: > Just did as you wrote, installing a jessie-amd64 system into a newly > created image (had to create efi boot partition too). Not 2, about > 15 minutes in total.
Is it pristine base system only, installed with debootstrap, or You used standard Debian installer? > Here the system works just fine after booting in ovmf. I also installed > 4.1 kernel, it too works just fine. Well, it boots and I can login and > run some basic apt-get commands, I didn't test further. We don't need any tests after booting. The problem is that it stop booting apt some point while init scripts execution. > As I suggested before, please try to find out WHAT is failing, exactly. > Which part of the system startup makes it stop. It should be easier > with sysvinit as usually a startup script prints an action BEFORE > actually running it, so you'll see "Starting foo.." right before > the stall. The problem is that with different installation, or after installing/removing some additional packages, it stop booting at different points. The constant is only fact, that with any configuration it is don't reach login point. I suppose the most likely suspect is udev. But some times boot process stops late after udev successfully started. Some times I tried to boot with init=/bin/bash, It was successful, but when I start udev it hangs. ******************************* ### Vladimir Stavrinov ### vstavri...@gmail.com ******************************* -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
