Your message dated Sat, 15 Aug 2009 19:21:08 +0100
with message-id <1250360468.21652.7.ca...@localhost>
and subject line Re: Bug#541702: linux-image-2.6.30-1-686: Kernel fails to
start networking because no e100 firmware
has caused the Debian Bug report #541702,
regarding linux-image-2.6.30-1-686: Kernel fails to start networking because no
e100 firmware
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.)
--
541702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541702
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-2.6.30-1-686
Version: 2.6.30-5
Severity: serious
Justification: Policy 2.2.1
On upgrade from 2.6.30-2-686 networking (on a remote machine) failed to
start, meaning that a support ticket had to be opened for KVM access.
Diagnosis revealed that the e100 driver in 2.6.26-2-686 required no
firmware, so the firmware-linux package wasn't installed. Apparently
2.6.30-1-686 was built with external firmware for the e100 so it now
depends on the firmware-linux package.
This is a serious policy violation because required hardware stops
working after the upgrade.
Fix suggested is to make 2.6.30-1-686 depend on linux-firmware so that
on upgrade the necessary firmware is present.
-- Package-specific info:
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.30-1-686 depends on:
ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy
ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs
ii module-init-tools 3.9-2 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.30-1-686 recommends:
ii libc6-i686 2.9-23 GNU C Library: Shared libraries [i
Versions of packages linux-image-2.6.30-1-686 suggests:
ii grub 0.97-55 GRand Unified Bootloader (dummy pa
ii grub-legacy [grub] 0.97-55 GRand Unified Bootloader (Legacy v
pn linux-doc-2.6.30 <none> (no description available)
-- debconf information:
linux-image-2.6.30-1-686/preinst/lilo-has-ramdisk:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.30-1-686/postinst/old-initrd-link-2.6.30-1-686: true
linux-image-2.6.30-1-686/postinst/create-kimage-link-2.6.30-1-686: true
linux-image-2.6.30-1-686/postinst/depmod-error-2.6.30-1-686: false
linux-image-2.6.30-1-686/postinst/old-system-map-link-2.6.30-1-686: true
linux-image-2.6.30-1-686/prerm/would-invalidate-boot-loader-2.6.30-1-686: true
linux-image-2.6.30-1-686/preinst/overwriting-modules-2.6.30-1-686: true
linux-image-2.6.30-1-686/preinst/lilo-initrd-2.6.30-1-686: true
linux-image-2.6.30-1-686/postinst/old-dir-initrd-link-2.6.30-1-686: true
linux-image-2.6.30-1-686/preinst/failed-to-move-modules-2.6.30-1-686:
linux-image-2.6.30-1-686/postinst/bootloader-test-error-2.6.30-1-686:
linux-image-2.6.30-1-686/preinst/abort-install-2.6.30-1-686:
linux-image-2.6.30-1-686/postinst/bootloader-error-2.6.30-1-686:
linux-image-2.6.30-1-686/preinst/initrd-2.6.30-1-686:
linux-image-2.6.30-1-686/prerm/removing-running-kernel-2.6.30-1-686: true
linux-image-2.6.30-1-686/postinst/kimage-is-a-directory:
linux-image-2.6.30-1-686/preinst/abort-overwrite-2.6.30-1-686:
linux-image-2.6.30-1-686/preinst/elilo-initrd-2.6.30-1-686: true
linux-image-2.6.30-1-686/preinst/bootloader-initrd-2.6.30-1-686: true
linux-image-2.6.30-1-686/postinst/depmod-error-initrd-2.6.30-1-686: false
--- End Message ---
--- Begin Message ---
On Sat, 2009-08-15 at 10:47 -0700, [email protected]
wrote:
> Package: linux-image-2.6.30-1-686
> Version: 2.6.30-5
> Severity: serious
> Justification: Policy 2.2.1
That very same section explains why we cannot do what you are
suggesting!
> On upgrade from 2.6.30-2-686 networking (on a remote machine) failed to
> start, meaning that a support ticket had to be opened for KVM access.
I don't recommend running unstable on production machines.
> Diagnosis revealed that the e100 driver in 2.6.26-2-686 required no
> firmware, so the firmware-linux package wasn't installed. Apparently
> 2.6.30-1-686 was built with external firmware for the e100 so it now
> depends on the firmware-linux package.
>
> This is a serious policy violation because required hardware stops
> working after the upgrade.
No, most systems do not require the firmware-linux package.
> Fix suggested is to make 2.6.30-1-686 depend on linux-firmware so that
> on upgrade the necessary firmware is present.
I intend to ensure that firmware-linux is mentioned in the release notes
for squeeze, but it cannot be recommended or made a dependency.
Ben.
--
Ben Hutchings
Never put off till tomorrow what you can avoid all together.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
