Your message dated Tue, 23 Oct 2012 13:58:44 -0400 with message-id <CANTw=mpkttc9v8ua8dqg54ie7lbsvnydk9crdvxroqepopa...@mail.gmail.com> and subject line re: grub-efi-amd64: fails to boot linux with initrd has caused the Debian Bug report #666018, regarding grub-efi-amd64: fails to boot linux with initrd 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 ow...@bugs.debian.org immediately.) -- 666018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: grub-efi-amd64 Version: 1.98+20100804-14+squeeze1 Severity: critical Tags: squeeze Justification: breaks the whole system Hi, this my first bug report, so I'd appreciate any hints, how I can do better. BTW sorry for my english. I installed squeeze on a computer with an uefi firmware. An ArchLinux was already installed on this computer, so I installed squeeze on a separate partition. For booting I used the already installed grub2 of ArchLinux, which worked fine also for squeeze. The time I was satisfied with my setup of squeeze, I wanted to get rid of ArchLinux. This included installing the squeeze package grub-efi-amd64. But booting with grub 1.98+20100804-14+squeeze1 failed with a kernel panic, something like: not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I found out, that this problem is somehow known: http://william.shallum.net/random-notes/windows-7-linux-uefi-dual-boot "Install grub-efi-amd64 from wheezy, not squeeze. Squeeze version doesn't properly pass initrd to the kernel, resulting in the error Kernel Panic ..." But I couldn't find any bug report on this topic, so here it is. Because I have no clue what the problem is, I worked around. I somehow managed, to backport the grub2-source-package of wheezy (1.99-17 at the time of this writing), and build my own grub2. (My version is called 1.99-17hinki, as you can see in the system information below.) This one works fine. For testing purpose I installed it in parallel to the non-working squeeze-grub-efi-amd64. So I could run some tests, if I knew which. In my current setup, the squeeze-grub and the wheezy-backported-grub are using the same configs. -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (990, 'stable'), (700, 'testing'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages grub-efi-amd64 depends on: ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii grub-common 1.99-17hinki GRand Unified Bootloader (common f ii grub-efi-amd64-bin 1.99-17hinki GRand Unified Bootloader, version ii grub2-common 1.99-17hinki GRand Unified Bootloader (common f ii ucf 3.0025+nmu1 Update Configuration File: preserv grub-efi-amd64 recommends no packages. grub-efi-amd64 suggests no packages. -- debconf information excluded
--- End Message ---
--- Begin Message ---version: 1.99-1 Fixed upstream, and doesn't affect wheezy. Still affects squeeze, but it's unlikely to be backported there unless someone has really strong interest. Best wishes, Mike
--- End Message ---
