Bug#299268: Netwinder latest daily success
* Kyle McMartin <kyle@debian.org> [2005-03-12 23:05]:
> Install base system: [O] (network failed once, and retried)
That's probably a problem with your network, though?
> Chose "multiuser system" and it partitioned things well.
> /boot was correctly ext2r0, excellent!
All of the standard schemes have a correct /boot partition and if you
manually partition your disk it will warn you if you don't have an
appropriate /boot.
> Was necessary to:
> setenv cmdappend console=ttyS0,115200,8n1
> setenv rootdev /dev/ram
> to get a serial console, and get the initrd going.
Yes, I know about this, but there's currently no good way to easily
figure out the serial settings. Someone wanted to add some generic
code to d-i in order to obtain this info, but this hasn't been done
yet. Anyway, the bug report is
#274695: Detect serial console on ARM and show console= entry
What about that rootdev parameter above? I suppose this is to boot
the installer rather than to boot Debian. (Just wondering since you
mention this after having installed Debian, so I wonder why you would
want to see /dev/ram instead of /dev/hda) Ah, right, I see you
mention initrd. Well, booting the initrd should be explained in the
installation manual (does it? I don't know for sure but I thought it
did), but you're right that the screen at the end of the 1st stage
should mention the console= parameter.
> Seemed to "hang" a bit at "Configuring the base system" before
> the "Debian Configuration" menus, some feedback would be nice, as these
> are very slow machines. Maybe a whirlygig would be appropriate...
This is a known problem with debootstrap, and really dpkg, which
doesn't supply the necessary details to display this information.
See
#244563: Please make "Installing base packages" progress more granual
--
Martin Michlmayr
http://www.cyrius.com/
Reply to: