latest GRUB stuff

[Daniel Robbins]

Here's the latest GRUB stuff:

grub-1.97.1-r3.ebuild contains the following changes:

1) /etc/conf.d/grub -> /etc/grub.conf
2) /etc/grub.d/* -> /usr/share/grub/templates/*
3) specifying a single kernel (non-glob) now works
4) added slightly modified color support from Jochums Johannes

The new features are shown in the new default config file, /etc/grub.conf.

I also added a new ebuild - sys-boot/grub-legacy, for the GRUB 0.97 series.
And I moved sys-boot/grub-static to grub-legacy-static for consistency.

-Daniel

[netcelli]

I've got sync problem:
!!! Missing ebuild: sys-boot/grub-static-0.97
!!! Missing ebuild: sys-boot/grub-static-0.97-r9
!!! Missing ebuild: sys-boot/grub-static-0.96-r1
!!! Missing ebuild: sys-boot/grub-static-0.97-r6

:)

[Víctor Orozco]

I got the same messages. Hwclock is in local

Now also exist a new grub package \o/

sys-boot/grub-legacy

Maybe it's a normal git message :)


--
Victor Leonel Orozco (tuxtor)
http://tuxtor.shekalug.org
"Those who don't understand UNIX are condemned to reinvent it,
poorly." - Henry Spencer

[Erick Michau]

On Wed, Dec 9, 2009 at 2:56 AM, Daniel Robbins <drob...@funtoo.org> wrote:

Here's the latest GRUB stuff:

grub-1.97.1-r3.ebuild contains the following changes:

   1) /etc/conf.d/grub -> /etc/grub.conf
   2) /etc/grub.d/* -> /usr/share/grub/templates/*
   3) specifying a single kernel (non-glob) now works
   4) added slightly modified color support from Jochums Johannes

The new features are shown in the new default config file, /etc/grub.conf.

Hi Daniel, Hi List,

It works like a charm on my netbook:

[ebuild   R   ] sys-boot/grub-1.97.1-r3  USE="custom-cflags -debug -mkfont -static" 0 kB

I've added the custom-cflags to spice up my day though it is more a curiosity rather than a real need.

I still have the same grub.cfg

"""

set timeout=10

menuentry "Funtoo Linux - /boot/kernel-genkernel-x86-2.6.32-git1" {

insmod ext2

set root=(hd0,1)

search --no-floppy --fs-uuid --set 56e7d503-b084-49e9-8c76-1fcda47a717b

linux /kernel-genkernel-x86-2.6.32-git1 root=/dev/ram0 real_root=/dev/mapper/root crypt_root=/dev/sda3 init=/linuxrc ramdisk=8192

initrd /initramfs-genkernel-x86-2.6.32-git1

}

"""

Thanks for the good work!

Erick

PS:

As a side note, I've recently took possession of a sony vaio VGN series (core2 duo 64b) and I will install ~funtoo on it as soon as I have some 'solitude' to work that out. It will dual boot with win7 (I'm keeping it for a while as I'm curious to tackle with the new beast).

I quickly tried last weekend to install ~funtoo (core2) using Kicktoo (a more featured -and maintained - version of Quickstart) but then the install failed due a Glib compilation error and I had to put it aside until I can find some time to troubleshoot (probably in a couple of weeks).

 

I also added a new ebuild - sys-boot/grub-legacy, for the GRUB 0.97 series.
And I moved sys-boot/grub-static to grub-legacy-static for consistency.

-Daniel

--

You received this message because you are subscribed to the Google Groups "Funtoo" group.
To post to this group, send email to funto...@googlegroups.com.
To unsubscribe from this group, send email to funtoo-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/funtoo-dev?hl=en.

[Martin Scholz]

> --
>
> You received this message because you are subscribed to the Google Groups "Funtoo" group.
> To post to this group, send email to funto...@googlegroups.com.
> To unsubscribe from this group, send email to funtoo-dev+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/funtoo-dev?hl=en.
>
>

Hi Daniel,

is there something special to do I didn't figure out correctly after
upgrading from r2?
The following happens on my system:

# grub-update

* grub-update 1.0
* Copyright 2009-2010 Funtoo Technologies.
* Distributed under the terms of the GNU General Public License v3

* /boot already mounted.
Loading extension linux

* Warning: No kernels found -- system not ready to boot.
Please specify a valid GRUB_SEARCH value
in /etc/default/grub
and ensure that you have a valid kernel in /boot.

Greetings

Martin

[Erick Michau]

On Wed, Dec 9, 2009 at 10:35 AM, Martin Scholz <schol...@googlemail.com> wrote:

On Tue, 2009-12-08 at 19:56 -0700, Daniel Robbins wrote:
> Here's the latest GRUB stuff:
>
> grub-1.97.1-r3.ebuild contains the following changes:
>
>     1) /etc/conf.d/grub -> /etc/grub.conf
>     2) /etc/grub.d/* -> /usr/share/grub/templates/*
>     3) specifying a single kernel (non-glob) now works
>     4) added slightly modified color support from Jochums Johannes
>
> The new features are shown in the new default config file, /etc/grub.conf.
>
> I also added a new ebuild - sys-boot/grub-legacy, for the GRUB 0.97 series.
> And I moved sys-boot/grub-static to grub-legacy-static for consistency.
>
> -Daniel
>
> --
>
> You received this message because you are subscribed to the Google Groups "Funtoo" group.
> To post to this group, send email to funto...@googlegroups.com.
> To unsubscribe from this group, send email to funtoo-dev+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/funtoo-dev?hl=en.
>
>

Hi Daniel,

is there something special to do I didn't figure out correctly after
upgrading from r2?

given what I did to update, I would say no but I have a very basic configuration.

 

The following happens on my system:

# grub-update

* grub-update 1.0
 * Copyright 2009-2010 Funtoo Technologies.
 * Distributed under the terms of the GNU General Public License v3

 * /boot already mounted.
Loading extension linux

 * Warning: No kernels found -- system not ready to boot.
           Please specify a valid GRUB_SEARCH value
in /etc/default/grub
           and ensure that you have a valid kernel in /boot.

after I merged the new grub, I just ran # grub-install /dev/sda (given my setup).

I never ran grub-update and grub-install always did the job for me.

Do you have the same problems running grub-install? Is there any reason why you prefer grub-update over grub-install?

I've just tried running grub-update and here is what I get:

pong pacgen-1.10 # grub-update -h

 * grub-update 1.0

 * Copyright 2009-2010 Funtoo Technologies.

 * Distributed under the terms of the GNU General Public License v3

 * /boot already mounted.

Loading extension linux

sh: -c: line 0: unexpected EOF while looking for matching ``'

sh: -c: line 2: syntax error: unexpected end of file

 * Error: grub-mkconfig failed.

pong pacgen-1.10 # 

and then my grub.cfg looks like:

# Header

set timeout=10

# Theme

error: guppy fail! fail bad!

grub-probe  --device error: cannot open `/dev/sdb' while attempting to get disk size

/dev/sda1 --target=abstraction

I'm not sure why it is looking for sdb as it is my android phone. If unplugged, rerun I get:

pong pacgen-1.10 # grub-update --help

 * grub-update 1.0

 * Copyright 2009-2010 Funtoo Technologies.

 * Distributed under the terms of the GNU General Public License v3

 * /boot already mounted.

Loading extension linux

 * Warning: No kernels found -- system not ready to boot.

            Please specify a valid GRUB_SEARCH value in /etc/default/grub

            and ensure that you have a valid kernel in /boot.

and makes grub.cfg look like:

# Header

set timeout=10

# Theme

insmod ext2

set root=(hd0,1)

search --no-floppy --fs-uuid --set 56e7d503-b084-49e9-8c76-1fcda47a717b

if loadfont /grub/unifont.pf2; then

set gfxmode=1440x900

insmod gfxterm

insmod vbe

terminal_output gfxterm

fi

set menu_color_normal=cyan/blue

set menu_color_highlight=blue/cyan

# GRUB Linux Section

which is still not reflecting my setup but it is fine with me as my / is luksified.

try the good ol' grub-install it should do the trick. 

Good luck

ps: reverting to my working grub.cfg, rerunning grub-install and rebooting just to be sure :)

 

Greetings

Martin

[Erick Michau]

reverting + rebooting went ok ;)

[Martin 'golodhrim' Scholz]

On Wed, 09 Dec 2009 10:54:16 +0000, Erick Michau wrote:

Hi Erick,

I just installed a new kernel image and as supposed grub-update should
find it automatically and include it to the list of used images. so that
was what I wished to do by grub-update. so for the first I will go back,
and downgrade to the r2 version and create a nice config, before
upgrading again so would be only nice to know what is missing and how to
solve it, as someone might get the same error and then here is a solution
or a place where to start. as it is in my eyes easier to solve a problem
in an early development state than in a nearly finished one.

[Piotr Karbowski]

Broken _new_ grub-legacy.

[Erick Michau]

Martin,

Indeed, I totally agree and understand the motivation for using grub-update. 

My bad if I made wrong suggestions sorry.

Best luck

Erick

[Martin Scholz]

> +unsub...@googlegroups.com.

> For more options, visit this group at
> http://groups.google.com/group/funtoo-dev?hl=en.
>
>
>
>
>
>

> --
>
> You received this message because you are subscribed to the Google
> Groups "Funtoo" group.
> To post to this group, send email to funto...@googlegroups.com.
> To unsubscribe from this group, send email to funtoo-dev

> +unsub...@googlegroups.com.

> For more options, visit this group at
> http://groups.google.com/group/funtoo-dev?hl=en.

Hi Erick

not your fault. you gave me a good hint, switching back and updating and
upgrading after works ok now, but that shouldn't be the solution for
later, so hope there is some hint here how to get it working later...

Thanks a lot Erick

Greetings
Martin

[Rajat Vig]

I got into the same issue.

The problem you've got is that the /etc/conf.d/grub moved to /etc/grub.conf.

Do a diff/merge/edit and it should work post that.

-Rajat

To unsubscribe from this group, send email to funtoo-dev+...@googlegroups.com.

[Daniel Robbins]

On Dec 9, 2009, at 12:57 AM, Víctor Orozco wrote:

> On Wed, Dec 9, 2009 at 12:53 AM, netcelli <netc...@gmail.com> wrote:
>> I've got sync problem:
>> !!! Missing ebuild: sys-boot/grub-static-0.97
>> !!! Missing ebuild: sys-boot/grub-static-0.97-r9
>> !!! Missing ebuild: sys-boot/grub-static-0.96-r1
>> !!! Missing ebuild: sys-boot/grub-static-0.97-r6
>>
>> :)
>>
>
> I got the same messages. Hwclock is in local
>
> Now also exist a new grub package \o/
>
> sys-boot/grub-legacy

The "!!! missing ebuild" message is kind of an incorrect error message -- it means there is metadata for an ebuild that doesn't exist. In this case, the metadata is the error, not the missing ebuild. This is because I forgot to "rm" the grub-static metadata after moving it to grub-legacy-static. It should go away when Jeff does his next merge (might have happened already :)

-Daniel

[Jacob Todd]

Can I install it without a separate /boot? I thought there was some problems
with that.

[Oleg]

Hello!
There is a problem on my comp. I getting a new fancy blue stuff with
kernel list to boot , then
it stuck with black screen and Linux-bzImage message. It seems that
kernel is booting I can blindly type my login and password and get
into linux but still no promt or else just black screen with grub
message. I tested also on GUI-based laptop, typing startx blindly get
me to DE. This is really a pain for me as I working with GUI-less comp
mainly.


2009/12/9, Jacob Todd <jaket...@gmail.com>:

[Daniel Robbins]

On Dec 9, 2009, at 7:59 AM, Oleg wrote:

> Hello!
> There is a problem on my comp. I getting a new fancy blue stuff with
> kernel list to boot , then
> it stuck with black screen and Linux-bzImage message. It seems that
> kernel is booting I can blindly type my login and password and get
> into linux but still no promt or else just black screen with grub
> message. I tested also on GUI-based laptop, typing startx blindly get
> me to DE. This is really a pain for me as I working with GUI-less comp
> mainly.

Hi Oleg,

The default config may be putting you into vesafb or uvesafb, or an unsupported graphics mode. Check the config and adjust as necessary.

Note: the config file is now in /etc/grub.conf.

-Daniel

[Daniel Robbins]

On Wed, Dec 9, 2009 at 2:47 AM, Jacob Todd <jaket...@gmail.com> wrote:
> Can I install it without a separate /boot? I thought there was some problems
> with that.

Please try it; it should work. If it doesn't work, please report it here.

-Daniel

[Daniel Robbins]

On Wed, Dec 9, 2009 at 3:35 AM, Martin Scholz <schol...@googlemail.com> wrote:
> Hi Daniel,
>
> is there something special to do I didn't figure out correctly after
> upgrading from r2?
> The following happens on my system:
>
> # grub-update
>
> * grub-update 1.0
>  * Copyright 2009-2010 Funtoo Technologies.
>  * Distributed under the terms of the GNU General Public License v3
>
>  * /boot already mounted.
> Loading extension linux
>
>  * Warning: No kernels found -- system not ready to boot.
>            Please specify a valid GRUB_SEARCH value
> in /etc/default/grub
>            and ensure that you have a valid kernel in /boot.

There error message is incorrect - the config file is now at
/etc/grub.conf instead of /etc/conf.d/grub.

-Daniel

[Daniel Robbins]

On Wed, Dec 9, 2009 at 4:09 AM, Piotr Karbowski <jabbe...@gmail.com> wrote:
> Broken _new_ grub-legacy.

Just fixed this. Please sync and give it another shot, let me know how it goes.

-Daniel

[Jeff Mitchell]

Daniel Robbins wrote:
> The "!!! missing ebuild" message is kind of an incorrect error message -- it means there is metadata for an ebuild that doesn't exist. In this case, the metadata is the error, not the missing ebuild. This is because I forgot to "rm" the grub-static metadata after moving it to grub-legacy-static. It should go away when Jeff does his next merge (might have happened already :)
>

Nah, you jumped the gun by 20 minutes :-)

--Jeff

[Ryan Holt]

Hi All -

I'm running into the same issue as listed above; fresh install of
Gentoo/Funtoo. Never used anything other than grub-1.97.1-r3.

grub-install /dev/sda works fine, but when I try to do a grub-update I
get a message indicating that there are no valid kernels in my /boot
directory. Here's an ls of /boot:

sysresccd grub # ls /boot
bzImage-2.6.32 grub initramfs-2.6.32 lost+found

And here's my /etc/grub.conf:

grub {
extensions *
parse header theme linux
timeout 10
default bzImage-new
}

display {
gfxmode 1024x600
}

color {
normal cyan/blue
highlight blue/cyan
}

default {
scan /boot
kernel bzImage[-v] kernel[-v] vmlinuz[-v] vmlinux[-v]
initrd initramfs[-v]

# root=auto will cause the parameter for the root= option to
be grabbed
# from your /etc/fstab. rootfstype= works in much the same
way.

params root=auto rootfstype=auto

# an alternate graphics mode can be set here for kernels,
otherwise the
# default is inherited from display:

# gfxmode 1440x900
}

"Funtoo Linux" {
kernel bzImage
}

"Funtoo Linux vesafb" {
params += video=vesafb
kernel bzImage-vesafb
}

"Funtoo Linux uvesafb" {

# to enable uvesafb, you will need to add /usr/share/v86d/
initramfs to
# your CONFIG_INITRAMFS_SOURCE for your kernel, and then
recompile.

params += video=uvesafb:1024x600-8,mtrr:2
kernel bzImage-uvesafb
}

/etc/fstab:

sysresccd grub # cat /etc/fstab
# /etc/fstab: static file system information.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than
1.
#
# NOTE: If your BOOT partition is ReiserFS, add the notail option to
opts.
#
# See the manpage fstab(5) for more information.
#
# <fs> <mountpoint> <type>
<opts> <dump/pass>

/dev/sda3 /boot ext2
noauto,noatime 1 2
/dev/vg/swap none swap
sw 0 0
/dev/vg/FT-root / ext4
noatime 0 1
sysresccd grub #

Any ideas?

Thanks,
Ryan

[Ryan Holt]

Looks like removing any version info from the end fixes the problem...

/boot shows just bzImage and initramfs. Now it's able to find the
kernel and generate the config file.

[Daniel Robbins]

On Dec 26, 2009, at 11:46 AM, Ryan Holt wrote:

> Hi All -
>
> I'm running into the same issue as listed above; fresh install of
> Gentoo/Funtoo. Never used anything other than grub-1.97.1-r3.
>
> grub-install /dev/sda works fine, but when I try to do a grub-update I
> get a message indicating that there are no valid kernels in my /boot
> directory. Here's an ls of /boot:

Yep, it's just doing what the config says.

You have 3 boot menu entries, and each entry specifies a specific kernel image that doesn't exist, namely "bzImage", "bzImage-vesafb" and "bzImage-uvesafb".

You will need to create your own menu entry, like this:

"Ryan's Menu Entry" {
}

I've never tried a blank menu entry before, but it should work. The settings in "default" will work for you as long as you don't override them by specifying "kernel bzImage", etc.

Hope that makes sense.

Give this a read - although it describes a future version of core-boot, it should explain to you how the default section works:

http://www.funtoo.org/en/funtoo/core/boot/

-Daniel

[Ryan Holt]

Ahhh! That makes sense. Is it documented somewhere how to chain load
Windows and OSX in grub2?

Thanks!