1. http://d-i.pascal.at/ suggest to use
append initrd=initrd.gz ramdisk_size=10240 root=/dev/rd/0
devfs=mount,dall rw DEBCONF_PRIORITY=medium
(line broken here for readability)
Since I have a seperate initrd directive in my syslinux.cfg, I added
to the append directive:
vga=791 ramdisk_size=10240 root=/dev/rd/0 devfs=mount,dall rw
With this addition, I can boot into the installer.
2. I then tried the linux and initrd.gz of 23-Feb-2013 from the
netboot section. Both what I believe is the text (newt) version,
and the GTK one. The machine reboots itself with nothing seen on
the display. This happens with an append line of
vga=791
as well as with an append line of
vga=791 ramdisk_size=10240 root=/dev/rd/0 devfs=mount,dall rw
3. With the current, 23-Feb-2013, hd-media/gtk vmlinuz and initrd.gz,
and an append line of
vga=791 ramdisk_size=10240 root=/dev/rd/0 devfs=mount,dall rw
I got a kernel panic that looks to me similar to the one in the
post that open #701149.
Now I wonder where are the kernel and initrd.gz that do work came
from? The kernel size is 2503264 bytes. The initrd.gz is 28524879
bytes. I think they boot into a GTK version of the installer. I
also think they were put on the archive on 11-Feb-2013.
--
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/20130317221221.ge2...@nt1.in
