GRUB fix for 1.1: Preferred approach for default grub version

DISCUSSION Darren Hart 3 participants 7 messages Oct 3, 2011

Share & tools

Darren Hart

author

2011-10-03 18:48 UTC #0 lore raw

When grub2 was merged int oe-core, it became the default (rather than being explicitly requested by the 64b meta-intel BSPs). This breaks the live install on 32b systems, like the n450 - installing grub v1.99 with a grub v1 config.

We have a couple options on how to fix this.

1) Set PREFERRED_PROVIDER_grub="0.97" in all 32b x86 machine configs
2) Set DEFAULT_PREFERENCE="-1" in the grub_1.99.bb recipe which would affect all of oe-core.
3) Some alternate approach which would be the equivalent of DEFAULT_PREFERENCE, but only for meta-yocto BSPs or the poky "distro".

Given the time frame, I'd prefer to agree on the approach before writing and testing patches. Preferences?

Thanks,

Signature · 3 lines

Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Richard Purdie

2011-10-03 19:02 UTC #1 lore raw

Quoted 14 lines · Darren Hart

When grub2 was merged int oe-core, it became the default (rather than being explicitly requested by the 64b meta-intel BSPs). This breaks the live install on 32b systems, like the n450 - installing grub v1.99 with a grub v1 config.
We have a couple options on how to fix this.
1) Set PREFERRED_PROVIDER_grub="0.97" in all 32b x86 machine configs
2) Set DEFAULT_PREFERENCE="-1" in the grub_1.99.bb recipe which would affect all of oe-core.
3) Some alternate approach which would be the equivalent of DEFAULT_PREFERENCE, but only for meta-yocto BSPs or the poky "distro".

Quoted 2 lines

Given the time frame, I'd prefer to agree on the approach before writing and testing patches. Preferences?

I thought I'd been assured grub2 worked fine for our 32 and 64 bit platforms? :/.

The correct question here is why doesn't grub2 work on 32 bit platforms?

The answer might be "we need for time than is available in the 1.1 release to fix it" but I'd at least like to see the answer to the question before we start with workarounds.

Cheers,

Richard

Tom Zanussi

2011-10-03 19:05 UTC #6 lore raw

In reply to Darren Hart

Quoted 14 lines · Darren Hart

When grub2 was merged int oe-core, it became the default (rather than being explicitly requested by the 64b meta-intel BSPs). This breaks the live install on 32b systems, like the n450 - installing grub v1.99 with a grub v1 config.
We have a couple options on how to fix this.
1) Set PREFERRED_PROVIDER_grub="0.97" in all 32b x86 machine configs
2) Set DEFAULT_PREFERENCE="-1" in the grub_1.99.bb recipe which would affect all of oe-core.
3) Some alternate approach which would be the equivalent of DEFAULT_PREFERENCE, but only for meta-yocto BSPs or the poky "distro".

Quoted 3 lines

Given the time frame, I'd prefer to agree on the approach before writing and testing patches. Preferences?

Not sure why it wouldn't work for the n450 - it worked for the other 32-bit BSPs in meta-intel. Let me take a look...

Tom

Quoted 2 lines

Thanks,

Tom Zanussi

2011-10-03 19:07 UTC #2 lore raw

In reply to Richard Purdie

Quoted 15 lines · Richard Purdie

Quoted 14 lines · Darren Hart
When grub2 was merged int oe-core, it became the default (rather than being explicitly requested by the 64b meta-intel BSPs). This breaks the live install on 32b systems, like the n450 - installing grub v1.99 with a grub v1 config.
We have a couple options on how to fix this.
1) Set PREFERRED_PROVIDER_grub="0.97" in all 32b x86 machine configs
2) Set DEFAULT_PREFERENCE="-1" in the grub_1.99.bb recipe which would affect all of oe-core.
3) Some alternate approach which would be the equivalent of DEFAULT_PREFERENCE, but only for meta-yocto BSPs or the poky "distro".

Quoted 8 lines

Quoted 2 lines
Given the time frame, I'd prefer to agree on the approach before writing and testing patches. Preferences?
I thought I'd been assured grub2 worked fine for our 32 and 64 bit platforms? :/.
The correct question here is why doesn't grub2 work on 32 bit platforms?

I did test it with both 32-bit and 64-bit BSPs in meta-intel, so it should work for the n450 too.

Tom

Quoted 8 lines

The answer might be "we need for time than is available in the 1.1 release to fix it" but I'd at least like to see the answer to the question before we start with workarounds.
Cheers,
Richard

Darren Hart

author

2011-10-03 20:40 UTC #3 lore raw

Quoted 19 lines · Tom Zanussi

Quoted 18 lines · Richard Purdie
Quoted 16 lines · Darren Hart
When grub2 was merged int oe-core, it became the default (rather than being explicitly requested by the 64b meta-intel BSPs). This breaks the live install on 32b systems, like the n450 - installing grub v1.99 with a grub v1 config.
We have a couple options on how to fix this.
1) Set PREFERRED_PROVIDER_grub="0.97" in all 32b x86 machine configs
2) Set DEFAULT_PREFERENCE="-1" in the grub_1.99.bb recipe which would affect all of oe-core.
3) Some alternate approach which would be the equivalent of DEFAULT_PREFERENCE, but only for meta-yocto BSPs or the poky "distro".
Given the time frame, I'd prefer to agree on the approach before writing and testing patches. Preferences?

Quoted 8 lines

Quoted 5 lines
I thought I'd been assured grub2 worked fine for our 32 and 64 bit platforms? :/.
The correct question here is why doesn't grub2 work on 32 bit platforms?
I did test it with both 32-bit and 64-bit BSPs in meta-intel, so it should work for the n450 too.

I checked out edison in poky in meta-intel and built core-image-minimal for n450. By default it builds GRUB 2, which after install boots to a GRUB prompt with no menu.

Using the PREFERRED_PROVIDER method above with the edison branches results in a GRUB 1 menu after install.

--
Darren

Quoted 13 lines

Tom
Quoted 8 lines
The answer might be "we need for time than is available in the 1.1 release to fix it" but I'd at least like to see the answer to the question before we start with workarounds.
Cheers,
Richard

Signature · 3 lines

Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Tom Zanussi

2011-10-03 23:18 UTC #4 lore raw

Quoted 27 lines · Darren Hart

Quoted 25 lines · Tom Zanussi
Quoted 23 lines · Richard Purdie
Quoted 14 lines · Darren Hart
When grub2 was merged int oe-core, it became the default (rather than being explicitly requested by the 64b meta-intel BSPs). This breaks the live install on 32b systems, like the n450 - installing grub v1.99 with a grub v1 config.
We have a couple options on how to fix this.
1) Set PREFERRED_PROVIDER_grub="0.97" in all 32b x86 machine configs
2) Set DEFAULT_PREFERENCE="-1" in the grub_1.99.bb recipe which would affect all of oe-core.
3) Some alternate approach which would be the equivalent of DEFAULT_PREFERENCE, but only for meta-yocto BSPs or the poky "distro".
Quoted 2 lines
Given the time frame, I'd prefer to agree on the approach before writing and testing patches. Preferences?
I thought I'd been assured grub2 worked fine for our 32 and 64 bit platforms? :/.
The correct question here is why doesn't grub2 work on 32 bit platforms?

Quoted 7 lines

Quoted 2 lines
I did test it with both 32-bit and 64-bit BSPs in meta-intel, so it should work for the n450 too.
I checked out edison in poky in meta-intel and built core-image-minimal for n450. By default it builds GRUB 2, which after install boots to a GRUB prompt with no menu.

I'm not even getting that far with edison - it fails at 'Searching for a hard drive'. I'd be happy to have it fail with no menu.

Can you send me the commit ids for meta-intel and poky that actually got you that far, and if you could a serial capture of the install?

Thanks,

Tom

Quoted 20 lines

Using the PREFERRED_PROVIDER method above with the edison branches results in a GRUB 1 menu after install.
--
Darren
Quoted 13 lines
Tom
Quoted 8 lines
The answer might be "we need for time than is available in the 1.1 release to fix it" but I'd at least like to see the answer to the question before we start with workarounds.
Cheers,
Richard

Tom Zanussi

2011-10-03 23:25 UTC #5 lore raw

Quoted 36 lines · Tom Zanussi

Quoted 27 lines · Darren Hart
Quoted 25 lines · Tom Zanussi
Quoted 23 lines · Richard Purdie
Quoted 14 lines · Darren Hart
When grub2 was merged int oe-core, it became the default (rather than being explicitly requested by the 64b meta-intel BSPs). This breaks the live install on 32b systems, like the n450 - installing grub v1.99 with a grub v1 config.
We have a couple options on how to fix this.
1) Set PREFERRED_PROVIDER_grub="0.97" in all 32b x86 machine configs
2) Set DEFAULT_PREFERENCE="-1" in the grub_1.99.bb recipe which would affect all of oe-core.
3) Some alternate approach which would be the equivalent of DEFAULT_PREFERENCE, but only for meta-yocto BSPs or the poky "distro".
Quoted 2 lines
Given the time frame, I'd prefer to agree on the approach before writing and testing patches. Preferences?
I thought I'd been assured grub2 worked fine for our 32 and 64 bit platforms? :/.
The correct question here is why doesn't grub2 work on 32 bit platforms?
Quoted 7 lines
Quoted 2 lines
I did test it with both 32-bit and 64-bit BSPs in meta-intel, so it should work for the n450 too.
I checked out edison in poky in meta-intel and built core-image-minimal for n450. By default it builds GRUB 2, which after install boots to a GRUB prompt with no menu.

Quoted 6 lines

I'm not even getting that far with edison - it fails at 'Searching for a hard drive'. I'd be happy to have it fail with no menu.
Can you send me the commit ids for meta-intel and poky that actually got you that far, and if you could a serial capture of the install?

Never mind, I actually didn't have a hard drive (wrong power source). Once I changed that, I got a good install (on crownbay).

It would still be useful to have the serial capture for the n450 though...

Tom

Quoted 30 lines

Thanks,
Tom
Quoted 20 lines
Using the PREFERRED_PROVIDER method above with the edison branches results in a GRUB 1 menu after install.
--
Darren
Quoted 13 lines
Tom
Quoted 8 lines
The answer might be "we need for time than is available in the 1.1 release to fix it" but I'd at least like to see the answer to the question before we start with workarounds.
Cheers,
Richard
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto