Summary: | sys-boot/grub-2.00_beta1 - system reboots after "Loading Linux x.x.x-gentoo" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Casper Ti. Vector <CasperVector> |
Component: | [OLD] Core system | Assignee: | Mike Gilbert <floppym> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | base-system, CasperVector, jlec, kaikaikai, kuba.iluvatar, limanski, Magnus.Kessler, martin, mh, polar88bear, pyxlcy, tibor.vago, uzytkownik2 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Casper Ti. Vector
2012-03-08 09:10:29 UTC
Exactly same situation here. As a workaround: 1. downgrade to _beta0 2. grub2-install 3) upgrade back to _beta1 It seems that the "linux" command is broken in beta1. Using "linux16" instead of "linux" works here. (In reply to comment #1) > Exactly same situation here. > > As a workaround: > 1. downgrade to _beta0 > 2. grub2-install > 3) upgrade back to _beta1 This workaround worked for me (I forgot to mention this when writing the report). Thanks anyway :) Same with efi-64 platform I don't seem to be having this problem myself with the pc platform. Could someone experiencing the problem report it upstream please? http://www.gnu.org/software/grub/grub-bugs.html (In reply to comment #2) > It seems that the "linux" command is broken in beta1. > Using "linux16" instead of "linux" works here. Thanks, that fixed it for me, too. Beta1 is b0rked. I am also affected (In reply to comment #1) > Exactly same situation here. > > As a workaround: > 1. downgrade to _beta0 > 2. grub2-install > 3) upgrade back to _beta1 As I understend I should not call grub2-install for beta1? (In reply to comment #7) > I am also affected > > (In reply to comment #1) > > Exactly same situation here. > > > > As a workaround: > > 1. downgrade to _beta0 > > 2. grub2-install > > 3) upgrade back to _beta1 > > As I understend I should not call grub2-install for beta1? That's exactly the point. (In reply to comment #8) > (In reply to comment #7) > > As I understend I should not call grub2-install for beta1? > > That's exactly the point. There is really no point in upgrading back to beta1 in that case. Again, this issue is much more likely to be resolved if someone would work with the upstream developers. I can't produce the problem, so I won't be able to perform any testing they may request. (In reply to comment #8) > That's exactly the point. So it means that an old bootloader will be used with new scripts? I expect same problem on and64 system. linux16 command fixes the issue for me. I can confirm this bug on x86_64 in UEFI mode, downgrading to beta0 solved the issue. So who is up to give a report to upstream? (In reply to comment #12) > So who is up to give a report to upstream? BTW, could you clarify, is it's an official grub builds, because I cannot find it on GNU FTP server: ftp://ftp.gnu.org/gnu/grub/ ? Same problem here. More info. I have GPT partition table on PC platform with hibrid MBR for Windows shit: $ sudo gdisk /dev/sda GPT fdisk (gdisk) version 0.6.13 Partition table scan: MBR: hybrid BSD: not present APM: not present GPT: present Found valid GPT with hybrid MBR; using GPT. Command (? for help): r Recovery/transformation command (? for help): o MBR disk identifier: 0xCA4B4C51 MBR partitions: Number Boot Start (sector) Length (sectors) Type 1 1 159380927 0xEE 2 * 159380928 134223012 0x07 Disk size is 976773168 sectors (465.8 GiB) Recovery/transformation command (? for help): p Disk /dev/sda: 976773168 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): 0FBA7D64-E9D6-4B9E-A7E1-E04F0AD7B575 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 976773134 Partitions will be aligned on 1-sector boundaries Total free space is 28 sectors (14.0 KiB) Number Start (sector) End (sector) Size Code Name 1 40 4096 2.0 MiB EF02 BIOS boot partition 2 4104 135175 64.0 MiB FFFF Linux filesystem 3 135176 16771859 7.9 GiB FFFF Linux filesystem 4 16771860 150994934 64.0 GiB A500 5 150994935 159380927 4.0 GiB 8200 Linux swap 6 159380928 293603939 64.0 GiB 0700 Microsoft basic data 7 293603940 310375799 8.0 GiB FFFF Linux filesystem 8 310375800 976773119 317.8 GiB FFFF Linux filesystem Recovery/transformation command (? for help): Maybe this help to reproduce the problem to anyone. (In reply to comment #13) > (In reply to comment #12) > > So who is up to give a report to upstream? > > BTW, could you clarify, is it's an official grub builds, because I cannot > find it on GNU FTP server: ftp://ftp.gnu.org/gnu/grub/ ? It is an alpha/beta release and U can find here: ftp://alpha.gnu.org/gnu/grub/ Workaround: build kernel with CONFIG_RELOCATABLE (In reply to comment #16) > Workaround: build kernel with CONFIG_RELOCATABLE doesn't work here. (In reply to comment #17) > (In reply to comment #16) > > Workaround: build kernel with CONFIG_RELOCATABLE > > doesn't work here. Your part table is GPT or MBR? (In reply to comment #18) > (In reply to comment #17) > > (In reply to comment #16) > > > Workaround: build kernel with CONFIG_RELOCATABLE > > > > doesn't work here. > > Your part table is GPT or MBR? GPT, I am using UEFI/GPT/GRUB2 setups. And this is reproduced on two amd64 systems. (In reply to comment #19) > (In reply to comment #18) > > (In reply to comment #17) > > > (In reply to comment #16) > > > > Workaround: build kernel with CONFIG_RELOCATABLE > > > > > > doesn't work here. > > > > Your part table is GPT or MBR? > > GPT, I am using UEFI/GPT/GRUB2 setups. And this is reproduced on two amd64 > systems. If I right your system platform is not PC but UEFI. Are you set GRUB_PLATFORMS="efi-64" at emerge grub? That's right. (In reply to comment #21) > That's right. I inspect the differences between beta0 and beta1. Your grub2 setup was works well with beta0? yes it does. Did you find any meaningful changes? (In reply to comment #23) > yes it does. Did you find any meaningful changes? I don't think so.(In reply to comment #23) > yes it does. Did you find any meaningful changes? I don't think so. Can U please try the trunk version of grub2? I see some relevant commits in trunk: ---------------------------------------------------------- 2012-03-07 Vladimir Serbinenko <phcoder@gmail.com> * grub-core/loader/i386/linux.c (prot_init_space): New variable. (allocate_pages): Improve dprintf. (grub_cmd_linux): Fill prot_init_space. Fix improper usage of code32_start. Fill code32_start and kernel_alignment in params. (grub_cmd_initrd): Use prot_init_space. ---------------------------------------------------------- and: ---------------------------------------------------------- 2012-03-10 Vladimir Serbinenko <phcoder@gmail.com> * grub-core/loader/efi/chainloader.c (grub_cmd_chainloader): Use "out of memory" error messagge. ---------------------------------------------------------- =grub-9999 works for me now. Mike, did you backport the fixes or removed the version in question? Beta 2 is now in the tree. Please test. (In reply to comment #27) > Beta 2 is now in the tree. Please test. Beta 2 solved the issue for me. Did the grub2-install and rebooted with no problems at all. Thanks. If anyone else still experiences this bug with beta 2, please speak up and I will reopen this. (In reply to comment #26) this version isn't keyworded, so fixes upstream qualify as fixed here |