Re: time to test Sarge mipsel cd images?
On Tue, Jun 01, 2004 at 08:54:41PM +0200, Santiago Garcia Mantinan wrote:
> You can find the images at
> http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/mipsel/current/
> you try whichever you prefer, or even better, both.
Installation results for
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/mipsel/current/sarge-mipsel-netinst.iso,
dated 2004/06/01, on a DECstation 5000/150 (mipsel, R4000, 128MB RAM):
Installation was done on serial console. This required manual entry
of all parameters in the form of
boot 3/rz2 1/linux-kn04 console=ttyS2 initrd=/boot/initrd.gz ramdisk_size=8192
as delo currently cannot merge parameters. This means
a) you can boot a predefined config from delo.conf without any
additional parameters
b) if you want to add a specific parameter (console=ttyS2 in this
case) you have to provide _all_ parameters on the commandline,
even those which are already in the delo.conf
This could be circumvented by adding additional sections in the delo.conf
for booting on serial console (like "linux-kn04-ttyS2"). Unfortunately
depending on the machine type, the serial port can be ttyS0, ttyS2 or ttyS3,
so this would mean generating _many_ entries. The Linux/MIPS kernel cannot
autodetect the system console but instead always assumes fbcon, if no
console parameter is passed, so we have to supply some form of console
parameter for using serial console.
After start of d-i, an error message is displayed:
??????????????????? [!!] Select a keyboard layout ???????????????????
? Installation step failed ?
? An installation step failed. You can try to run the failing item ?
? again from the menu, or skip it and choose something else. The ?
? failing step is: Select a keyboard layout ?
? ?
? <Continue> ?
? ?
?????????????????????????????????????????????????????????????????????
I have not had that problem with kbd-chooser in the past. It seems that
something with the serial console detection went wrong.
Configuring the network via dhcp failed on the first attempt and
succeeded on the second. Aside from that, the installation proceeds
normally.
The progress bar from prebaseconfig ends at 93%, then the system is
rebooted. On reboot into the second stage, the following messages
appear:
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
So it seems that there is a a problem with umounting the root
filesystem before reboot.
Regards,
Karsten
--
#include <standard_disclaimer>
Nach Paragraph 28 Abs. 3 Bundesdatenschutzgesetz widerspreche ich der Nutzung
oder Uebermittlung meiner Daten fuer Werbezwecke oder fuer die Markt- oder
Meinungsforschung.
Reply to: