chainloader problem

chainloader problem

[Marco Vega Trucillo]

Hi to all,   

I'm marco and I'm new to grub-devel maling list. Forgive me for my bad
English. I have a strange issue with chainloader both with 1.96 and last
csv version.
I've compiled grub2 and I installed it on a usb stick with

dd if=boot.img of=/dev/sdc 
dd if=mycore.img of=/dev/sdc seek=1

It boot and I got grub shell's prompt. From here I'm able to boot linux on
my primary harddisk that biosdisk driver see as (hd1). The usbstick is
(hd0).
But if I try to boot my first hard disk or windows with
chainloader (hd1)+1
boot

or for windows
chainloader (hd1,1)+1
boot

the screen became black and it hang...

but If I try to load the same grub2 image with grub-0.96 it work! i.e.: I
start with grub-0.96 cd... Now primary disk is (hd0) and usbpen is (hd1)
from grub-0.96 shell I run
kernel (hd1)1+125   <-this because my grub-1.96 core image is 125 blocks
boot

I got grub-1.96 shell... then 
chainloader (hd0)+1
boot
and my first disk start....

Have you some idea about this strange issues ?
 

Thanks in advance and forgive me again for my bat english
 

Re: chainloader problem

[Pavel Roskin]

On Sat, 2008-05-03 at 18:54 +0200, Marco Vega Trucillo wrote:

> I got grub-1.96 shell... then 
> chainloader (hd0)+1
> boot
> and my first disk start....
> 
> Have you some idea about this strange issues ?

I have a trouble understanding you, but anyway, the "chainloader"
command is broken in version 1.96.  Please try the current CVS version
of GRUB 2.

-- 
Regards,
Pavel Roskin

Re: chainloader problem

[Christoph Peltz]

[-- Attachment #1: Type: text/plain, Size: 558 bytes --]

Am Sat, 03 May 2008 19:03:04 -0400
schrieb Pavel Roskin <proski@gnu.org>:

> I have a trouble understanding you, but anyway, the "chainloader"
> command is broken in version 1.96.  Please try the current CVS version
> of GRUB 2.
> 

I think he has done that already (he just misspelled cvs as csv).
The problem seems to be, that the chainloader  does not work for him
with grub 2 alone. He has to use grub 1 to load grub2 and then he can
use chainloader with grub 2.
As me limited understanding goes: THAT is wierd.

Regards,
Christoph Peltz

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: chainloader problem

[Marco Vega Trucillo]

On Sun, 4 May 2008 01:58:39 +0200, Christoph Peltz <admin@keeg.de> wrote:
> I think he has done that already (he just misspelled cvs as csv).
> The problem seems to be, that the chainloader  does not work for him
> with grub 2 alone. He has to use grub 1 to load grub2 and then he can
> use chainloader with grub 2.


Yes. I'm using last CVS version fo grub 2 and Chainloader does not work if
I boot with it. But if I use grub1 to load grub2 (the same "core"), then
chainloader works.


> As me limited understanding goes: THAT is wierd.

oh..forgive me, I'll try to write better. 
Thanks 

Marco

Re: chainloader problem

[Vesa Jääskeläinen]

Marco Vega Trucillo wrote:
> Hi to all,   
> 
> I'm marco and I'm new to grub-devel maling list. Forgive me for my bad
> English. I have a strange issue with chainloader both with 1.96 and last
> csv version.
> I've compiled grub2 and I installed it on a usb stick with
> 
> dd if=boot.img of=/dev/sdc 
> dd if=mycore.img of=/dev/sdc seek=1

Use grub-setup/grub-install

Re: chainloader problem

[Marco Vega Trucillo]

On Sun, 04 May 2008 13:07:55 +0300, Vesa Jääskeläinen <chaac@nic.fi>
wrote:
> Marco Vega Trucillo wrote:
>> Hi to all,
>>
>> I'm marco and I'm new to grub-devel maling list. Forgive me for my bad
>> English. I have a strange issue with chainloader both with 1.96 and last
>> csv version.
>> I've compiled grub2 and I installed it on a usb stick with
>>
>> dd if=boot.img of=/dev/sdc
>> dd if=mycore.img of=/dev/sdc seek=1
> 
> Use grub-setup/grub-install

Ok thanks I will try this.
 
But actualy on my usb stick there isn't any partition table nor filesystem.
mycore.img is grub2 "core" with a memdisk embedded that contains linux's
kernel and few other files.
All the remaining space on the usb stick are raw data: this is the reason
because I boot grub in that way without use grub-setup/grub-install