On 11/09/2011 03:15 AM, Martin Michlmayr wrote:
> You MUST use a serial connection to make this work, which is at least
inconvenient.
Why does it make netboot console impossible?
IIRC you should be able to login via SSH without any problems, and
later you'll get an option to choose additional modules to download.
At least this is how it should work (afaik).
I agree, however that did not happen. A reboot did not help either.
And I waited a long while hoping it will work.
Only a serial connection showed that the boot process failed and it
was looking for a disk.
Starting sshd should not depend on a disk, yet it did.
However, looking at the log of your original bug submissions, it seems
that the first screen that debian-installer shows is the error about
"No disk drive was detected." Was this really the first screen or do
the dots in your bug report imply there were other screens before?
I did not file the initial bug report, but the installer starts from top
of the
install process, and when it comes to the disk finding section, it
cannot find one.
In the meantime I bricked my GLANTANK slightly, so I cannot re-test this
right now.
But I'll try again with a new and empty disk and report here what went
wrong in as many details as I can imagine is needed to find the root cause.
Harald
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4eba78fd.6000...@gmx.net
