hi!
and instead of the usual cryptsetup password prompt, it prints a
message about starting dropbear and then stuck.
I should add that it printed "IP-Config: eth0 ..." and apparently tried
to configure eth0 with DHCP, but that interface is not connected to any
network. (Perhaps that would eventually time out but my patience with a
non-booting laptop is not long.)
when your initramdisk is built, you should get the following warning:
Dropbear has ben added to your initramfs. Don't forget to check your
"ip=" kernel bootparameter to match your desired initramfs ip
configuration.
i guess your choices are:
- disable remote cryptroot unlocking completely by adding
DROPBEAR=n
to /etc/initramfs-tools/initramfs.conf. without dropbear, ip config
won't be forced. (don't forget to update-initramfs afterwards to
actually make it effective)
- configure your kernel's ip setup on boot (probably in
/boot/grub/menu.lst if you're using grub: either add it to the
respective 'kernel' line(s) or the '# kopt=' lines) which is done
with a kernel boot parameter 'ip='. e.g.:
ip=none
(i haven't tested that, but i guess it should do the obvious:
prevent any ip configuration on bootup, so you won't be able to
connect to your dropbear even if it's being started), or:
ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
to configure a static ip setup (see Documentation/nfsroot.txt in the
kernel source tree).
i'll put 'see if/how we can push initrd ip config into background'
on my 2do list (but don't wait for it).
regards,
Chris
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
