Your message dated Wed, 10 Dec 2008 08:12:32 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Suggested image
has caused the Debian Bug report #508302,
regarding linux-image-2.6.26-1-ixp4xx: flash-kernel fails with kernel doesn't
fit
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
508302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508302
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: linux-image-2.6.26-1-ixp4xx
Version: 2.6.26-11
Severity: normal
The reportbug script downgraded this to normal. I believe this is not correct
and should be severe. The kernel flash simply will not work. This is probably
good as the machine will not break, but it also means a NSLU2 user cannot
follow lenny on the NSLU2. As lenny is approacing release and, the NSLU2 is
officially supported, how can we assist in the request to please test the new
2.6.26 kernel if it won't install?
full failre message from apt-get follows
%< ------ snip start ------->%
Setting up linux-image-2.6.26-1-ixp4xx (2.6.26-11) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
initrd.img(/boot/initrd.img-2.6.26-1-ixp4xx
) points to /boot/initrd.img-2.6.26-1-ixp4xx
(/boot/initrd.img-2.6.26-1-ixp4xx) -- doing nothing at
/var/lib/dpkg/info/linux-image-2.6.26-1-ixp4xx.postinst line 588.
vmlinuz(/boot/vmlinuz-2.6.26-1-ixp4xx
) points to /boot/vmlinuz-2.6.26-1-ixp4xx
(/boot/vmlinuz-2.6.26-1-ixp4xx) -- doing nothing at
/var/lib/dpkg/info/linux-image-2.6.26-1-ixp4xx.postinst line 588.
Running postinst hook script flash-kernel.
The kernel doesn't fit in flash.
User postinst hook script [flash-kernel] exited with value 1
dpkg: error processing linux-image-2.6.26-1-ixp4xx (--configure):
subprocess post-installation script returned error exit status 1
Setting up python-urwid (0.9.8.3-1) ...
Processing triggers for python-support ...
Errors were encountered while processing:
linux-image-2.6.26-1-ixp4xx
E: Sub-process /usr/bin/dpkg returned an error code (1)
%< ------ snip end ------->%
Regards
Serge Rijkers
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: arm (armv5tel)
Kernel: Linux 2.6.18-6-ixp4xx
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-1-ixp4xx depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92j tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
linux-image-2.6.26-1-ixp4xx recommends no packages.
Versions of packages linux-image-2.6.26-1-ixp4xx suggests:
pn fdutils <none> (no description available)
pn linux-doc-2.6.26 <none> (no description available)
-- debconf information:
linux-image-2.6.26-1-ixp4xx/preinst/failed-to-move-modules-2.6.26-1-ixp4xx:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.26-1-ixp4xx/preinst/already-running-this-2.6.26-1-ixp4xx:
linux-image-2.6.26-1-ixp4xx/preinst/abort-overwrite-2.6.26-1-ixp4xx:
linux-image-2.6.26-1-ixp4xx/prerm/would-invalidate-boot-loader-2.6.26-1-ixp4xx:
true
linux-image-2.6.26-1-ixp4xx/preinst/lilo-initrd-2.6.26-1-ixp4xx: true
linux-image-2.6.26-1-ixp4xx/preinst/abort-install-2.6.26-1-ixp4xx:
linux-image-2.6.26-1-ixp4xx/preinst/elilo-initrd-2.6.26-1-ixp4xx: true
linux-image-2.6.26-1-ixp4xx/prerm/removing-running-kernel-2.6.26-1-ixp4xx:
true
linux-image-2.6.26-1-ixp4xx/preinst/lilo-has-ramdisk:
linux-image-2.6.26-1-ixp4xx/postinst/old-system-map-link-2.6.26-1-ixp4xx: true
linux-image-2.6.26-1-ixp4xx/postinst/old-initrd-link-2.6.26-1-ixp4xx: true
linux-image-2.6.26-1-ixp4xx/postinst/create-kimage-link-2.6.26-1-ixp4xx: true
linux-image-2.6.26-1-ixp4xx/postinst/bootloader-error-2.6.26-1-ixp4xx:
linux-image-2.6.26-1-ixp4xx/preinst/overwriting-modules-2.6.26-1-ixp4xx: true
linux-image-2.6.26-1-ixp4xx/postinst/old-dir-initrd-link-2.6.26-1-ixp4xx: true
linux-image-2.6.26-1-ixp4xx/postinst/bootloader-test-error-2.6.26-1-ixp4xx:
linux-image-2.6.26-1-ixp4xx/postinst/depmod-error-2.6.26-1-ixp4xx: false
linux-image-2.6.26-1-ixp4xx/postinst/depmod-error-initrd-2.6.26-1-ixp4xx:
false
linux-image-2.6.26-1-ixp4xx/preinst/bootloader-initrd-2.6.26-1-ixp4xx: true
linux-image-2.6.26-1-ixp4xx/postinst/kimage-is-a-directory:
linux-image-2.6.26-1-ixp4xx/preinst/initrd-2.6.26-1-ixp4xx:
--- End Message ---
--- Begin Message ---
* Serge Rijkers <[EMAIL PROTECTED]> [2008-12-10 00:07]:
> I have just reflashed as per you suggestion. Yes, the link you offered
> worked! I now have a 2.6.26 kernel running on my NSLU2. That means in
> effect that the base installer image I ran at the time had a too small
> root partition for a modern kernel.
OK great, closing the bug report.
> Thank you for supplying me with a running image that works. I guess the
> bug can be closed now. If there are any steps that I can take to assist in
> narrowing the users with this problem and therby aking your excellent
> suggestion available to them please let me know!
I don't think many people are affected, buuut if this turns out to be
wrong, I guess I'll have to think of something.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
