Re: thecus n2100 armel lenny upgrade, won't boot

[Joost Yervante Damad <joost@damad.be>]

Hi All,

just something peculiar thing I noticed while doing another upgrade of my 
thecus:

-- start --
Setting up udev (0.125-6) ...
update-initramfs: deferring update (trigger activated)
Setting up initramfs-tools (0.92j) ...
Installing new version of config file /etc/initramfs-tools/initramfs.conf ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-2.6.26-1-iop32x (2.6.26-4) ...

 Hmm. The package shipped with a symbolic 
link /lib/modules/2.6.26-1-iop32x/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/2.6.26-1-iop32x/source

Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.26-3 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.26-3 was configured last, according to dpkg)
Running postinst hook script flash-kernel.
Flashing kernel... done.
Flashing initramfs... done.

...
...

Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.26-1-iop32x
-- end --

As you can see due to triggers the initramfs is only actually generated after
the kernel has already been flashed. I could imagine this not being what is 
wanted soo I ran flash-kernel again just to be sure.

Or am I seeing ghosts?

Thanks, Joost

On Sunday 31 August 2008 10:24:31 Joost Yervante Damad wrote:
> On Sunday 31 August 2008 10:16:32 Martin Michlmayr wrote:
> > * Joost Yervante Damad <joost@damad.be> [2008-08-31 10:09]:
> > > Thanks for the quick reply both.
> > > I just discovered however that the thecus was still running 2.6.25-7 ?!
> > > I tried chrooting in again and flash 2.6.24 initrd and vmlinuz and it
> > > said it did it, but after a reboot it is still running 2.6.25-7 again.
> > > Looks like flash-kernel is not working when still in an initramfs I
> > > guess...?
> >
> > Maybe you hit this bug:
> > #488565 - should check status of /dev/mtdblock* before trying to write to
> > it
> >
> > You have to make sure /dev/mtdbock* exists before using flash-kernel.
>
> I guess so!
>
> I just manually loaded my 2.6.26 initrd and kernel via tftp and the system
> boots fine!
>
> Thanks Martin, Tobias for helping me out.
>
> (Cc:-ing debian-arm again, so other people also know what was the issue)
>
> Joost
>
> --
> homepage: http://damad.be/joost
> photo/blog: http://damad.be/joost/blog



-- 
homepage: http://damad.be/joost
photo/blog: http://damad.be/joost/blog