On 26/12/2009 18:59, Martin Michlmayr wrote:
Except I can no more update my kernel because it use the mtdblock
devices => the bug is not fixed for me as it requires more than
providing a correct kernel. You need also to provide a way to reflash
it.
We told you already - you need a serial console.
And I told you already (BTW you did not answer)
1) I'm lucky I have one but some may not have one as it is not needed
to install debian on a DNS 323
2) before changing the config and providing a kernel, this could have
been checked! .31 works so the orion config has been voluntarilly changed,
Besides yesterday, you proposed to write a trick enabling to write in
the flash without using the mtdblock? I proposed you to wait until can
get a hand on 32.3 but that you still need to clarify how to create
correct image for uboot.
The question still are:
1) Will the <space> <1> work. Have not checked yet,
2) how do I recreate the right kernel and initrd from the content of
the package 32.3 package because the rescue procedure only speaks about
splitting .img image not creating the relevant uboot image from
/boot/vmlinuz-xxx and initrd-xxx packages,
Besides, from a phylisophical POV, the bug is in 32.1, 32.2 and cannot
be fixed simply by providing a new kernel as you agree.
-- eric
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org