[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#601450: marked as done (linux-image-2.6.32-5-686 does not load correctly on an Intel Mac Mini)



Your message dated Sat, 8 Jun 2013 12:17:54 +0200
with message-id <20130608101754.GG4796@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #601450,
regarding linux-image-2.6.32-5-686 does not load correctly on an Intel Mac Mini
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 owner@bugs.debian.org
immediately.)


-- 
601450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601450
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.32-5-686
Version: 2.6.32-26

I have a 32-bit Intel Core Mac Mini (Late 2006). It is using grub-efi to boot (not the BIOS emulation mode). I've loaded the above kernel package onto it, and it does not boot correctly. Grub detects the kernel, but before any of the usual kernel bootup messages, it blanks the screen and reboots - i.e. gets stuck in a reboot loop.

An alternative kernel (2.6.26-2-686, version 2.6.26-25lenny1) from stable boots perfectly fine using the same grub setup.

My grub config file is below, although I've tried going to a grub command line and doing this:

  set root=(hd0,4)
  linux /vmlinuz-2.6.32-5-686 root=/dev/sda5 ro
  boot

and the same thing happens. The above process works correctly with the lenny kernel (until it tries to load the initrd, obviously). I don't think I'm doing anything wrong - the only thing that's changed is the kernel version / package. This is before it loads any of the rest of the OS, so it's only really the kernel image that can be causing this!

/boot is on an hfsplus partition (as that's necessary for the EFI stuff to work properly). I can provide any further debugging information as required.


Thanks

Phil


Grub config:

=================================================================
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, Linux 2.6.32-bpo.5-686" {
	insmod hfsplus
	set root=(hd0,4)
	search --no-floppy --fs-uuid --set 0000000000000000
linux /vmlinuz-2.6.32-bpo.5-686 root=UUID=6f61ce4b-4a47-45de-a897-b19fab3820c3 ro
	initrd	/initrd.img-2.6.32-bpo.5-686
}
menuentry "Debian GNU/Linux, Linux 2.6.32-bpo.5-686 (recovery mode)" {
	insmod hfsplus
	set root=(hd0,4)
	search --no-floppy --fs-uuid --set 0000000000000000
linux /vmlinuz-2.6.32-bpo.5-686 root=UUID=6f61ce4b-4a47-45de-a897-b19fab3820c3 ro single
	initrd	/initrd.img-2.6.32-bpo.5-686
}
menuentry "Debian GNU/Linux, Linux 2.6.32-5-686" {
	insmod hfsplus
	set root=(hd0,4)
	search --no-floppy --fs-uuid --set 0000000000000000
linux /vmlinuz-2.6.32-5-686 root=UUID=6f61ce4b-4a47-45de-a897-b19fab3820c3 ro
	initrd	/initrd.img-2.6.32-5-686
}
menuentry "Debian GNU/Linux, Linux 2.6.32-5-686 (recovery mode)" {
	insmod hfsplus
	set root=(hd0,4)
	search --no-floppy --fs-uuid --set 0000000000000000
linux /vmlinuz-2.6.32-5-686 root=UUID=6f61ce4b-4a47-45de-a897-b19fab3820c3 ro single
	initrd	/initrd.img-2.6.32-5-686
}
menuentry "Debian GNU/Linux, Linux 2.6.26-2-686" {
	insmod hfsplus
	set root=(hd0,4)
	search --no-floppy --fs-uuid --set 0000000000000000
linux /vmlinuz-2.6.26-2-686 root=UUID=6f61ce4b-4a47-45de-a897-b19fab3820c3 ro
	initrd	/initrd.img-2.6.26-2-686
}
menuentry "Debian GNU/Linux, Linux 2.6.26-2-686 (recovery mode)" {
	insmod hfsplus
	set root=(hd0,4)
	search --no-floppy --fs-uuid --set 0000000000000000
linux /vmlinuz-2.6.26-2-686 root=UUID=6f61ce4b-4a47-45de-a897-b19fab3820c3 ro single
	initrd	/initrd.img-2.6.26-2-686
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
=================================================================



--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---

Reply to: