Re: can't partition disk?
I was about to initiate the "manual" installation using debootstrap as Harald
suggested when I read your message concerning the new image. I tried it and
the (successful) results are as follows:
1. The append=... line is still needed. If omitted, the kernel boots and the
initial messages can be seen, but the dialog-based installer interface never
2. Keyboard can now be correctly selected and configured.
3. Disks can be partitioned (installer simply invokes the fdisk command, I
don't know if this is the default behaviour for other MIPS machines).
4. Filesystems can be specified from the installer and are correctly
5. Package download and installation go fine. Arcboot is correctly installed.
After modifying PROM parameters, ended booting up a shiny new Debian in my
Thank you so much!!
On Tuesday 29 March 2005 01:21, Martin Michlmayr wrote:
> * Jiann-Ming Su <email@example.com> [2005-03-25 20:24]:
> > First, I get the following message:
> > This partitioner doesn't have information about the default type of
> > the partition tables on your architecture. Please send an e-mail
> I have a theory why this might have been broken, but I'm not exactly
> sure. Anyway, I just generated a new image and have done a successful
> installation with it. You can download it from
> > I just tried the older image (Dec 19, 2004) and partitioning seems to
> > work. The new image also complains about keyboard localization. I
> > seem to be able to safely skip through that part. And, your message
> > bootp(): append="debian-installer/framebuffer=false"
> > doesn't apply to the new (Feb 9) image. The older image would not
> > bring up the install interface without adding the "append=".
> I think this is no longer needed now. Can you please test the new
> image and let me know if it works without this append parameter? I
> don't have a monitor here so I can only test serial console installs.
> > Does the new install image allow me to use filesystems other than
> > ext?
> No, only ext2/ext3 for now. In theory, I could put other modules on
> the image but even then your root partition would have to be ext2/ext3
> so you can boot from it.
> Martin Michlmayr