Control: reassign -1 grub-pc 1.99-26 Control: tag -1 moreinfo On Tue, 2013-01-15 at 11:51 +0100, Christopher Huhn, GSI wrote: > Package: src:linux > Version: 3.2.35-2 > Severity: important > > Hi everybody, > > I'm rather clueless on this error. Grub refuses to boot the current Wheezy kernel on this box. > The message is "cannot read the linux header". > 3.2.0-3-amd64 boots without problems. > > I reinstalled the kernel package as well as grub-pc and ran update-grub without problems. > "debsums -sa" does not report any modified files for the kernel package or any grub package installed. > > So I'm a bit clueless. > The box is an rather old Intel Core2 6300 box. Could that be the problem? > Could this kernel be incompatible with the processor? [...] This is Debian - we carry on supporting hardware until it's turned to rust (well almost). Anyway if GRUB is complaining then the kernel isn't running yet, is it? I'm reassigning this in the hope that GRUB maintainers can debug it. However, the bug reporting instructions for GRUB say: > MAKE SURE YOU ARE RUNNING THE LATEST VERSION > > The grub packages never update the installed version of GRUB > automatically, except if you choose a device in the debconf prompt > `GRUB install devices', which is currently only implemented for grub-pc. > > Because of this, you need to make sure you're running the LATEST VERSION of > GRUB before you report a bug. Use grub-install to update it, and then check > if the bug still applies. Debugging problems we already fixed makes us waste > valuable time, so please try to avoid it. They will also want to know: 1. The contents of /proc/mounts, /boot/grub/device.map, and /proc/mdstat (if present) 2. Listings (ls -l) of /dev/disk/by-id and /dev/disk/by-uuid 3. Output of 'debconf-show grub-pc' Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got.
Attachment:
signature.asc
Description: This is a digitally signed message part