Re: configure fail for grub

2008-12-08 Thread Viswesh S 




- Original Message 
> From: Pavel Roskin <[EMAIL PROTECTED]>
> To: The development of GRUB 2 
> Sent: Tuesday, 9 December, 2008 6:22:36 AM
> Subject: RE: configure fail for grub
> 
> On Mon, 2008-12-08 at 07:39 -0500, James Shewey wrote:
> 
> > When I configure grub-1.96, I got following error message:
> > 
> > configure: error: neither start nor _start is defined
> > 
> > Could anybody give me some ideas for it?
> 
> This happens if tools for 32-bit compilation are not available.
> Compiling on x86_64 defaults to 32-bit PC platform.  It's possible to
> compile for 64-bit EFI platform by specifying:
> 
> ./configure --with-platform=efi
> 
> -- 
> Regards,
> Pavel Roskin
> 
> 

Hi,

As mentioned above, it is because of the 32 bit compilation tools not 
available.I have faced the same problem in which my compiler was gcc-4.2.1 and 
to compile this I installed gcc-3.4.3 and made the CC point to the proper 
compiler and it worked.

Viswesh


  Connect with friends all over the world. Get Yahoo! India Messenger at 
http://in.messenger.yahoo.com/?wm=n/


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: device.map

2008-12-02 Thread Viswesh S 


- Original Message 
> From: Manoel Rebelo Abranches <[EMAIL PROTECTED]>
> To: The development of GRUB 2 
> Sent: Tuesday, 2 December, 2008 9:39:20 PM
> Subject: device.map
> 
> Can someone show me where grub2 uses device.map? I'm having a hard time
> finding it in source.
> 
> Thanks.
> -- 
> Best Regards,
> 
> Manoel Abranches 
> IBM Linux Technology Center Brazil
> 
> 
> 
> ___
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel

Please have a look at the grub-install script or grub-mkdevice map scripts 
present in /usr/local/sbin/grub- * .

To get this you might have to do grub-install "boot disk" 

if ide drives , then boot disk = /dev/hda  (or) hdb .based on which ide 
hard drive
if sata drives use sda, sdb ...similarly

Viswesh


  Did you know? You can CHAT without downloading messenger. Go to 
http://in.webmessenger.yahoo.com/


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: I'm a newb, looking for guidance

2008-12-02 Thread Viswesh S 
Hi Jay,

After make install , you may proceed with grub-install "boot disk" and then do 
update grub so as to update the files in /boot/grub in accordance with grub2.

grub-install will change the /usr/local/bin/grub and other binaries to grub2.

Regards,

Viswesh


 




From: Jay Sullivan <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Tuesday, 2 December, 2008 8:49:45 PM
Subject: Re: I'm a newb, looking for guidance

Okay! I realized now that I would like to install the newest version of grub2 
to a USB drive.  Can anyone recommend to me the best way to do this?  This 
seems like a good idea since if it fails to boot, I can easily fallback to my 
harddrive's bootloader.  

I'd like to point out that I'm currently having trouble getting started with 
grub2 development.  The reason is that I currently have grub-legacy installed 
to my system, and I can't figure out how to get grub2 working properly and I 
have a feeling that they are conflicting.  I have downloaded GRUB-1.96, and 
configured and successfully ran makefile, but if I run make-install will I 
overwrite grub-legacy? If not, how can I access the grub2 shell?  I've 
attempted to install it but /usr/local/bin/grub still holds grub-legacy.  Do I 
chainload core.img? Am I doing this whole thing wrong?  Thanks and I'm sorry if 
I'm asking stupid questions =)


On Mon, Dec 1, 2008 at 3:31 AM, Jay Sullivan <[EMAIL PROTECTED]> wrote:

Thank you for responding in such detail, it helps a lot.  
Right now I'm not sure what I'm interested in -- I'm interested in everything.  
I'm going to try to install the current svn of grub2 to an test computer that I 
have, and see what works and what doesn't. 




On Sun, Nov 30, 2008 at 5:29 AM, Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:

Hi Jay,

Welcome on the board!


Jay Sullivan wrote:
> Hi, I'm very interested in helping out with the grub project, but I don't
> know where to begin!  I've been interested in the project for a long time,
> but I try to respect people's time and I don't like to ask stupid questions
> until I've searched hard for the answers by myself.  I've tried very hard to
> find good documentation for GRUB, but, erm..all of the decent tutorials
> out there are incomplete at best, and many of them make too many assumptions
> to be very helpful.  I've read many tutorials but it seems like each one
> conflicts with the others.

I assume you are wanting to help with GRUB 2.

Well we have wiki.

http://grub.enbug.org/
http://grub.enbug.org/ContributingChangesToGrub

This is supposed to be central point for developer oriented information.
There are parts that are outdated. So if you see something weird or
would like to know something better, please ask so we can improve the wiki.


> First of all, I'm having trouble even understanding the grub architecture,
> and most of that is because I am constantly seeing conflicting information
> all over the internet due to the common fact that many people are ambiguous
> with which branch of grub they are referring to. Also, there seems to be a
> plague of broken and outdated links.

For GRUB 2 there exists only one official development branch (there are
others but basically we want to keep it as one branch). Idea for GRUB 2
is to promote other people to contribute patches to upstream.


> In general, though, I've found that grub is extremely underdocumented; but
> of the reading material which I have found to be at all helpful, there is a
> MAJOR tendency to overcomplicate things.  I have a background in C and x86
> assembly programming, and have had my fair share of device driving
> programming.  I enjoy helping others track down bugs in their code, and I
> love writing idiot-proof tutorials (being the idiot that I am).
>
> I'm not afraid to sit down and read thousands of lines of code if that's
> what it takes to be up to date with the project. I just want to make sure
> I'm not headed in the wrong direction or anything.

Ask what you want to know :)


> I remember reading a LONG time ago that the ETA for GRUB-2.0 was "November
> 2008," and so I expected to start seeing a lot more tutorials devoted to
> helping people prepare for it, but this hasn't happened as quickly as I'd
> hoped.  So I figured I would try to delve into the project and see what's
> REALLY going on.

I would assume 2006 but hey :). So basically there are things to be
done. There are different roles of developers. Some of them are
developing specific features, and some of them are trying to catch up
with features of GRUB legacy, and some just trying to follow the
"roadmap" for GRUB 2. Which is kinda zapped at this time.

Keypoint here is, what are your interests? What do you want to work on.

Some pointers that we see missing:

https://savannah.gnu.org/task/?group=grub
http://grub.enbug.org/TodoList

Oh.. before you start coding. Better start discussion on this list
because there might be others working on the same thing, or there might
be so

Re: Windows,grub and grub2

2008-11-08 Thread Viswesh S 
Hi,



- Original Message 
> From: Viswesh S <[EMAIL PROTECTED]>
> To: The development of GRUB 2 
> Sent: Tuesday, 14 October, 2008 5:04:53 PM
> Subject: Re: Windows,grub and grub2
> 
> Hi,
> 
> 
> 
> - Original Message 
> > From: Bean 
> > To: The development of GRUB 2 
> > Sent: Monday, 29 September, 2008 4:20:57 PM
> > Subject: Re: Windows,grub and grub2
> > 
> > On Mon, Sep 29, 2008 at 1:18 PM, Viswesh S wrote:
> > > Hi,
> > >
> > >
> > >
> > > - Original Message 
> > >> From: Bean 
> > >> To: The development of GRUB 2 
> > >> Sent: Tuesday, 23 September, 2008 7:20:49 PM
> > >> Subject: Re: Windows,grub and grub2
> > >>
> > >> On Tue, Sep 23, 2008 at 4:23 PM, Viswesh S wrote:
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > - Original Message 
> > >> >> From: Bean
> > >> >> To: The development of GRUB 2
> > >> >> Sent: Monday, 22 September, 2008 9:10:26 AM
> > >> >> Subject: Re: Windows,grub and grub2
> > >> >>
> > >> >> On Tue, Sep 9, 2008 at 2:00 PM, Viswesh S wrote:
> > >> >> > Below is the dump of screen output while chainloading the ntfsnew 
> file.
> > >> >> > ***
> > >> >> > DI=CFF0 SI=07EE BP=1FF0 SP=1FE8 BX= DX= CX= AX=
> > >> >> > CS= SS= DS= ES= FG=0246 IP=7C57
> > >> >> >
> > >> >> > DI=7FF0 SI=07EE BP=1FF0 SP=7BF4 BX=55AA DX= CX= AX=0100 
> CX=07C0
> > >> >> > DS=07C0 ES= FG=0007 IP=0082
> > >> >> > **
> > >> >> > Could you please let me know the way to disassemble the binary file 
> > without
> > >> >> > any header.The way in which you decoded the boot record.
> > >> >> >
> > >> >> > Also one more thing to let you know is that,
> > >> >> >
> > >> >> > with the grub-1.96 ( without the chainloader patch of 
> disk->dev->read() 
> > ) ,
> > >> >> > with windows2003 in partition 1 and linux in partition 3, when we
> > >> chainload,
> > >> >> > if we look at the partition table passed to another bootloader ie 
> > location
> > >> >> > 0x7be - we can see that it is junk, but the surprising point is 
> > >> >> > that, 
> in
> > >> >> > this case as I have mentioned in my first mail, windows boots up 
> > >> >> > from
> > >> >> > grub2.So it is that the partition table is not required for the 
> > chainloader
> > >> >> > thing and just the boot record is sufficient
> > >> >>
> > >> >> Hi,
> > >> >>
> > >> >> Oh, sorry for another long delay. I disassemble the file with ida,
> > >> >> which is an amazing tool. I don't know if there is open source
> > >> >> alternative, please let me know if you find one.
> > >> >>
> > >> >> The output from ida is in masm format, I modify it a bit so that it
> > >> >> can be compiled using nasm. Please note that nasm doesn't generate the
> > >> >> same binary file as original one, but you can get an idea what it
> > >> >> does.
> > >> >>
> > >> >> From the output, the program fails at the second int 13 call, int
> > >> >> 13/ah = 48h. Although I notice that DL=0, which is not supposed to
> > >> >> happen. Perhaps you can add a grub_printf in grub_chainloader_boot to
> > >> >> show the value of boot drive:
> > >> >>
> > >> >> static grub_err_t
> > >> >> grub_chainloader_boot (void)
> > >> >> {
> > >> >>  grub_printf ("boot_drive=%d\n", boot_drive);
> > >> >>  grub_chainloader_real_boot (boot_drive, boot_part_addr);
> > >> >>
> > >> >>  /* Never reach here.  */
> > >> >>  return GRUB_ERR_NONE;
> > >> >> }
> > >> >>
> > >> >> --
> > >> >> Bean
> > >> >>
> > >> >>
> > >>

USB support

2008-11-04 Thread Viswesh S 
Hi,

Is the USB support for grub2 completed or still in progress ?

Is it possible to know,if incomplete, till what level we have reached ?

Thanks,

Viswesh


  Add more friends to your messenger and enjoy! Go to 
http://messenger.yahoo.com/invite/


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows,grub and grub2

2008-10-14 Thread Viswesh S 
Hi,



- Original Message 
> From: Bean <[EMAIL PROTECTED]>
> To: The development of GRUB 2 
> Sent: Monday, 29 September, 2008 4:20:57 PM
> Subject: Re: Windows,grub and grub2
> 
> On Mon, Sep 29, 2008 at 1:18 PM, Viswesh S wrote:
> > Hi,
> >
> >
> >
> > - Original Message 
> >> From: Bean 
> >> To: The development of GRUB 2 
> >> Sent: Tuesday, 23 September, 2008 7:20:49 PM
> >> Subject: Re: Windows,grub and grub2
> >>
> >> On Tue, Sep 23, 2008 at 4:23 PM, Viswesh S wrote:
> >> >
> >> >
> >> >
> >> >
> >> > - Original Message 
> >> >> From: Bean
> >> >> To: The development of GRUB 2
> >> >> Sent: Monday, 22 September, 2008 9:10:26 AM
> >> >> Subject: Re: Windows,grub and grub2
> >> >>
> >> >> On Tue, Sep 9, 2008 at 2:00 PM, Viswesh S wrote:
> >> >> > Below is the dump of screen output while chainloading the ntfsnew 
> >> >> > file.
> >> >> > ***
> >> >> > DI=CFF0 SI=07EE BP=1FF0 SP=1FE8 BX= DX= CX= AX=
> >> >> > CS= SS= DS= ES= FG=0246 IP=7C57
> >> >> >
> >> >> > DI=7FF0 SI=07EE BP=1FF0 SP=7BF4 BX=55AA DX= CX= AX=0100 
> >> >> > CX=07C0
> >> >> > DS=07C0 ES= FG=0007 IP=0082
> >> >> > **
> >> >> > Could you please let me know the way to disassemble the binary file 
> without
> >> >> > any header.The way in which you decoded the boot record.
> >> >> >
> >> >> > Also one more thing to let you know is that,
> >> >> >
> >> >> > with the grub-1.96 ( without the chainloader patch of 
> >> >> > disk->dev->read() 
> ) ,
> >> >> > with windows2003 in partition 1 and linux in partition 3, when we
> >> chainload,
> >> >> > if we look at the partition table passed to another bootloader ie 
> location
> >> >> > 0x7be - we can see that it is junk, but the surprising point is that, 
> >> >> > in
> >> >> > this case as I have mentioned in my first mail, windows boots up from
> >> >> > grub2.So it is that the partition table is not required for the 
> chainloader
> >> >> > thing and just the boot record is sufficient
> >> >>
> >> >> Hi,
> >> >>
> >> >> Oh, sorry for another long delay. I disassemble the file with ida,
> >> >> which is an amazing tool. I don't know if there is open source
> >> >> alternative, please let me know if you find one.
> >> >>
> >> >> The output from ida is in masm format, I modify it a bit so that it
> >> >> can be compiled using nasm. Please note that nasm doesn't generate the
> >> >> same binary file as original one, but you can get an idea what it
> >> >> does.
> >> >>
> >> >> From the output, the program fails at the second int 13 call, int
> >> >> 13/ah = 48h. Although I notice that DL=0, which is not supposed to
> >> >> happen. Perhaps you can add a grub_printf in grub_chainloader_boot to
> >> >> show the value of boot drive:
> >> >>
> >> >> static grub_err_t
> >> >> grub_chainloader_boot (void)
> >> >> {
> >> >>   grub_printf ("boot_drive=%d\n", boot_drive);
> >> >>   grub_chainloader_real_boot (boot_drive, boot_part_addr);
> >> >>
> >> >>   /* Never reach here.  */
> >> >>   return GRUB_ERR_NONE;
> >> >> }
> >> >>
> >> >> --
> >> >> Bean
> >> >>
> >> >>
> >> >
> >> > Hi,
> >> >
> >> > The value of boot drive is 0x80.
> >> >
> >> > This was the same value in disk->drive also.
> >>
> >> Hi,
> >>
> >> Interesting, perhaps %dx is changed somewhere. Please try the
> >> following patch, it dumps the value of %dx just before jumping to the
> >> boot sector.
> >>
> >> --
> >> Bean
> >
> > The patch works and now Windows is booting perfectly fine from Grub2.
> >
> > I will go through the

Re: Windows,grub and grub2

2008-09-28 Thread Viswesh S 
Hi,



- Original Message 
> From: Bean <[EMAIL PROTECTED]>
> To: The development of GRUB 2 
> Sent: Tuesday, 23 September, 2008 7:20:49 PM
> Subject: Re: Windows,grub and grub2
> 
> On Tue, Sep 23, 2008 at 4:23 PM, Viswesh S wrote:
> >
> >
> >
> >
> > - Original Message 
> >> From: Bean 
> >> To: The development of GRUB 2 
> >> Sent: Monday, 22 September, 2008 9:10:26 AM
> >> Subject: Re: Windows,grub and grub2
> >>
> >> On Tue, Sep 9, 2008 at 2:00 PM, Viswesh S wrote:
> >> > Below is the dump of screen output while chainloading the ntfsnew file.
> >> > ***
> >> > DI=CFF0 SI=07EE BP=1FF0 SP=1FE8 BX= DX= CX= AX=
> >> > CS= SS= DS= ES= FG=0246 IP=7C57
> >> >
> >> > DI=7FF0 SI=07EE BP=1FF0 SP=7BF4 BX=55AA DX= CX= AX=0100 CX=07C0
> >> > DS=07C0 ES= FG=0007 IP=0082
> >> > **
> >> > Could you please let me know the way to disassemble the binary file 
> >> > without
> >> > any header.The way in which you decoded the boot record.
> >> >
> >> > Also one more thing to let you know is that,
> >> >
> >> > with the grub-1.96 ( without the chainloader patch of disk->dev->read() 
> >> > ) ,
> >> > with windows2003 in partition 1 and linux in partition 3, when we 
> chainload,
> >> > if we look at the partition table passed to another bootloader ie 
> >> > location
> >> > 0x7be - we can see that it is junk, but the surprising point is that, in
> >> > this case as I have mentioned in my first mail, windows boots up from
> >> > grub2.So it is that the partition table is not required for the 
> >> > chainloader
> >> > thing and just the boot record is sufficient
> >>
> >> Hi,
> >>
> >> Oh, sorry for another long delay. I disassemble the file with ida,
> >> which is an amazing tool. I don't know if there is open source
> >> alternative, please let me know if you find one.
> >>
> >> The output from ida is in masm format, I modify it a bit so that it
> >> can be compiled using nasm. Please note that nasm doesn't generate the
> >> same binary file as original one, but you can get an idea what it
> >> does.
> >>
> >> From the output, the program fails at the second int 13 call, int
> >> 13/ah = 48h. Although I notice that DL=0, which is not supposed to
> >> happen. Perhaps you can add a grub_printf in grub_chainloader_boot to
> >> show the value of boot drive:
> >>
> >> static grub_err_t
> >> grub_chainloader_boot (void)
> >> {
> >>   grub_printf ("boot_drive=%d\n", boot_drive);
> >>   grub_chainloader_real_boot (boot_drive, boot_part_addr);
> >>
> >>   /* Never reach here.  */
> >>   return GRUB_ERR_NONE;
> >> }
> >>
> >> --
> >> Bean
> >>
> >>
> >
> > Hi,
> >
> > The value of boot drive is 0x80.
> >
> > This was the same value in disk->drive also.
> 
> Hi,
> 
> Interesting, perhaps %dx is changed somewhere. Please try the
> following patch, it dumps the value of %dx just before jumping to the
> boot sector.
> 
> -- 
> Bean

The patch works and now Windows is booting perfectly fine from Grub2. 

I will go through the assembly and try to understand what modifications you 
have done.So there is a problem in Grub2 code, which needs to be fixed ?

Till this point, I was chainloading grub from Grub2 and then chainloading 
Windows2008 from it.

Thanks for the consistent help till this point and for the future also.

Viswesh



  Connect with friends all over the world. Get Yahoo! India Messenger at 
http://in.messenger.yahoo.com/?wm=n/


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows,grub and grub2

2008-09-23 Thread Viswesh S 




- Original Message 
> From: Bean <[EMAIL PROTECTED]>
> To: The development of GRUB 2 
> Sent: Monday, 22 September, 2008 9:10:26 AM
> Subject: Re: Windows,grub and grub2
> 
> On Tue, Sep 9, 2008 at 2:00 PM, Viswesh S wrote:
> > Below is the dump of screen output while chainloading the ntfsnew file.
> > ***
> > DI=CFF0 SI=07EE BP=1FF0 SP=1FE8 BX= DX= CX= AX=
> > CS= SS= DS= ES= FG=0246 IP=7C57
> >
> > DI=7FF0 SI=07EE BP=1FF0 SP=7BF4 BX=55AA DX= CX= AX=0100 CX=07C0
> > DS=07C0 ES= FG=0007 IP=0082
> > **
> > Could you please let me know the way to disassemble the binary file without
> > any header.The way in which you decoded the boot record.
> >
> > Also one more thing to let you know is that,
> >
> > with the grub-1.96 ( without the chainloader patch of disk->dev->read() ) ,
> > with windows2003 in partition 1 and linux in partition 3, when we chainload,
> > if we look at the partition table passed to another bootloader ie location
> > 0x7be - we can see that it is junk, but the surprising point is that, in
> > this case as I have mentioned in my first mail, windows boots up from
> > grub2.So it is that the partition table is not required for the chainloader
> > thing and just the boot record is sufficient
> 
> Hi,
> 
> Oh, sorry for another long delay. I disassemble the file with ida,
> which is an amazing tool. I don't know if there is open source
> alternative, please let me know if you find one.
> 
> The output from ida is in masm format, I modify it a bit so that it
> can be compiled using nasm. Please note that nasm doesn't generate the
> same binary file as original one, but you can get an idea what it
> does.
> 
> From the output, the program fails at the second int 13 call, int
> 13/ah = 48h. Although I notice that DL=0, which is not supposed to
> happen. Perhaps you can add a grub_printf in grub_chainloader_boot to
> show the value of boot drive:
> 
> static grub_err_t
> grub_chainloader_boot (void)
> {
>   grub_printf ("boot_drive=%d\n", boot_drive);
>   grub_chainloader_real_boot (boot_drive, boot_part_addr);
> 
>   /* Never reach here.  */
>   return GRUB_ERR_NONE;
> }
> 
> -- 
> Bean
> 
> 

Hi,

The value of boot drive is 0x80.

This was the same value in disk->drive also.

Viswesh


  Be the first one to try the new Messenger 9 Beta! Go to 
http://in.messenger.yahoo.com/win/


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows,grub and grub2

2008-09-08 Thread Viswesh S 




- Original Message 
From: Bean <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Thursday, 4 September, 2008 11:07:46 PM
Subject: Re: Windows,grub and grub2

On Tue, Sep 2, 2008 at 1:01 AM, Viswesh S <[EMAIL PROTECTED]> wrote:
>
>
> - Original Message 
> From: Bean <[EMAIL PROTECTED]>
> To: The development of GRUB 2 
> Sent: Monday, 1 September, 2008 9:05:48 PM
> Subject: Re: Windows,grub and grub2
>
> On Mon, Sep 1, 2008 at 11:27 PM, Viswesh S <[EMAIL PROTECTED]> wrote:
>>
>>
>
> Hi,
>
> Perhaps you can upload the boot sector file ? I can dissemble it to
> see where the error is printed.
>
> --
> Bean
> Hi,
>
>
> I was just trying out a way to disassemble it, as objdump didnt give it to
> me.I think I am not giving the right option,I suppose for binary.Let me know
> how to disassemble the binary.
>
>
>
> I have attached the boot record.

>Hi,
>
>I'm sorry for the delay, I'm a little busy in the last few days.
>
>I have disassemble the boot sector, there are three places where the
>error could occur, please chain load the file in the attachment and
>write down the screen output:
>
>chainloader /ntfsnew
>boot
>
>-- 
>Bean


Hi,

Below is the dump of screen output while chainloading the ntfsnew file.
***
DI=CFF0 SI=07EE BP=1FF0 SP=1FE8 BX= DX= CX= AX=
CS= SS= DS= ES= FG=0246 IP=7C57

DI=7FF0 SI=07EE BP=1FF0 SP=7BF4 BX=55AA DX= CX= AX=0100 CX=07C0
DS=07C0 ES= FG=0007 IP=0082
**
Could you please let me know the way to disassemble the binary file without any 
header.The way in which you decoded the boot record.

Also one more thing to let you know is that,

with the grub-1.96 ( without the chainloader patch of disk->dev->read() ) , 
with windows2003 in partition 1 and linux in partition 3, when we chainload, if 
we look at the partition table passed to another bootloader ie location 0x7be - 
we can see that it is junk, but the surprising point is that, in this case as I 
have mentioned in my first mail, windows boots up from grub2.So it is that the 
partition table is not required for the chainloader thing and just the boot 
record is sufficient

Viswesh



  Add more friends to your messenger and enjoy! Go to 
http://in.messenger.yahoo.com/invite/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows,grub and grub2

2008-09-01 Thread Viswesh S 




- Original Message 
From: Bean <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Monday, 1 September, 2008 9:05:48 PM
Subject: Re: Windows,grub and grub2

On Mon, Sep 1, 2008 at 11:27 PM, Viswesh S <[EMAIL PROTECTED]> wrote:
>
>

Hi,

Perhaps you can upload the boot sector file ? I can dissemble it to
see where the error is printed.

-- 
Bean

Hi, 

I was just trying out a way to disassemble it, as objdump didnt give it to me.I 
think I am not giving the right option,I suppose for binary.Let me know how to 
disassemble the binary.
 
I have attached the boot record.
 
Viswesh

___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Unlimited freedom, unlimited storage. Get it now, on 
http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/ëRNTFSø?ÿ?€€ëíá
ÞNöèv{·{´ú3ÀŽÐ¼|ûhÀhfˈf>NTFSu´A»ªUÍr
ûUªu÷ÁuéÒƒìh´HŠ‹ôÍŸƒÄžXrá;uÛ£Á.Z3Û¹ [EMAIL 
PROTECTED] 
fSfSfUh¸faÍéjf`f¡ffhfPShh´BŠ‹ôÍfY[ZfYfY‚fÿŽÂÿu¼faàøè ûèëþ´‹ð¬<t
 ´»ÍëòÃ
A disk read error occurred
BOOTMGR is missing
BOOTMGR is compressed
Press Ctrl+Alt+Del to restart
€²ÊUªBOOTMGR$I30Ô$ë"NTLDRf·f¶
[EMAIL PROTECTED]&fff‰*fff‰.fff‰>fff‰Ff¸f‹&èƒ
fÀ„Sþf£2f¸ f‹*èjf£6f¸°f‹.èX   f£:f¡2fÀ„ 
þg€x…þgfPgBgf¶H
f‰rgf‹Hf‰nf¡nf·f3Òf÷ñf£vf¡Ffnf£Jfƒ>6„fƒ>:„Äýf‹:f‹>Jf¡.èàf·f¸è"fÀ…f·Zf¸\è
fÀ„Bgf‹f‹>>è?f¡>f» 
f¹fºèäf…À…#f¡>f»€f¹fºèÄfÀ…
Déñf3Òf¹€f¡>èÊfÀ„Úf‹>>èÛf¡>f»€f¹fºè€fÀ„°gf·X
fãÿ…¥f‹Øh f+ÿf¡>èh f+ÿf¡>è¬
Š¸èŽÀ6+Àh PËf`f‹Úf¶
[EMAIL PROTECTED]
g€x…#Ãg:H   …f‹ðgp
[EMAIL PROTECTED]@…4gfPg:[EMAIL PROTECTED]@ëÂf3ÀÃg€{…f`gfSgf‹
f‹ógró¤faÃfPgfSf…À…
gf‹JfAëgf‹Bf3Òf÷6Rf‹Èf+Àf^èÃf`g€{„ékûfƒù…faÃfSfPfQfVfWè‘f‹Ñf_f^fYf…À„4f;ʍf‹Ñè‚þf+Êf‹Úf‹Âf¶
f÷âf·f÷âføfXfÃf[ëŸf…ö„ûfQfWgf¶C  f…À„ fÑàf+àf‹üfTfVgf·s
fóf‹Èó¤f^ëfPfPgf‹fPgf‹CfPgf‹V f…
Ò„f‹þf‹Âèqf‹ÆfZfYfBfQfVè?f…À„’úf^fYf‹þèNf‹Æf‹ÙfYfZfQfVfÑéèøýf…À„kúf^fYfáf_fYf‹ÐfXf[f‹Úéõþf`&gf·_&gf·Of
É„9úfßfƒÃfÇþfIfÉ„&g‹&g‰fƒÃfÇfIëâfaÃf`f¸f£"f¡fff£jfff£Nf¡0f¶
f÷ãf‹Nf‰f£ƒÃf¡Vf‰£ƒÃf‰Nf‹è\ùf‹ûèQÿf¡f» 
f¹fºèýfÀ„f‹Øf‹>f3Àè¢ýf‹f?€„ë_ëðfSf‹Gf÷&VfPf3Òf¶
f÷ófRèÜfÀ„9ùf‹Vf¶
f÷ãfZfÂf‹Nf‰ƒÃf¶
f+Âf;Á†f‹Áf‰f+ÈfZ„ufÂfPf3Òf¶
f÷ófQè‚fYfÀ„Ýøf¶
f÷ãf‹Nf‹ƒÃff;Ð…f¶
f;Á†f‹Áf륃Ãf‰Nf‰ƒÃf¶
f;Á†f‹Áf‰낃Ãfÿ"f‰Nf[_f?€„
ÿfaÃf‹Ðf‹"f‹6jf6ffRfQfRf‹jf‹>Vf‹f£ƒÆf‹£ƒÆèÝ÷f+ø„÷&ØëÙf‹>jè¿ýf¡jf»€f¹f‹ÑèûfÀ„ô÷f‹ØfXfVè,f^fÀ„f[f[ÃfYfZâ„f3ÀÃf`fPfQf3Òf¶
f÷ófRfWèSÿf_fÀ„®÷f¶
f÷ãfZfÂf£fYf¶
f;ËŽ‰f+ËfXfÃfPfQëfXfÁfP‰f¹fQfW‹ßƒãŒÀfÁïÇPè÷f_f>RfYfXfƒùpÿfaÃf`f÷&Vf‹VèUÿèÒüfaÃf`f÷&rf‹6f‹rf‹6*f‹>Fèûè§üfaÃfPfSfQf‹Jf‹ÈfÁèfƒáfØf¸fÓàg„„øëùfYf[fXÃg€{„f+ÀÃgfsgf‹Vf;‡gf‹f;ƒf+ÀÃg^f+ög€;„>èfñè9fÊf;ÁŒ!f‹ÑfPgf¶f‹ÁfƒàfÁéfÙfØfCfXëÄf+Èf+ÂfÆÃf+ÀÃf+ÉgŠ€áfƒù…f+ÉÃfSfRfÙgf¾fIfKfƒù„
fÁâgŠfKfIëëf‹ÊfZf[ÃfSfRf+ÒgŠfƒâf+ÉgŠÀéfƒù…f+ÉfZf[ÃfÚfÙgf¾fIfKfƒù„
fÁâgŠfKfIëëf‹ÊfZf[ÃfÉ…ÃfQfVgƒ>aŒgƒ>zgƒ. [EMAIL 
PROTECTED];Æ„:[EMAIL 
PROTECTED]@èÐøfÀtÄfYfYfYfYÃfYfYf3ÀÃfQfPf¸f‹ùèýf‹Áf» 
f¹fºè3øf[fYf…À…
f‹Áf·fºèøë3f3Òf‹Áf‹ËfPfSè#f[f_fÀ„è5ýf‹Çf·fºèá÷ÃfRfQf»
 f¹fºèÇ÷fÀ„cf‹Øf‹>f3ÀèYøf‹fYfZ&f9…
&f9W„1ë&fƒ?ÿ„/&ƒ„&&f·G؋Ã%€tˌÀŽÀãÿë¾&f‹GÃfYfZf3ÀÃfPfQf‹ÇfÁèYÈQfƒçfYfXÃ`¾½
¿ ¹
ó¥aÃ#Eg‰«Íïþܺ˜vT2ðáÒà  `‹6 &ŠˆGFfÿ þ` uè[¾  âæ‰6 aÃf`‹6 
°€ˆF2Àþ` uè:¾  þX uéf3Àf£X f¡ fÁàfÈf£\ è» f‹fÈf‰ƒÃû4 uîfaÃf`»  
f‹fÈf‰ƒÃû` uî» f‹f‹Wf‹wf‹f‹o»  Ç 0Æ S‹ 
ÿfG[fèf/f‹ÁfÁÀfÅf‹ïf‹þf‹òfÁÆf‹Ñf‹Èf‹f3Gf3G [EMAIL PROTECTED] u²ƒ 
> HuŸ» ffWfwf
fofaÃf‹Æf3Çf#Âf3ÇÃf‹Âf3Æf3ÇÃfSf‹Âf#Æf‹Úf#ßfÃf‹Þf#ßfÃf[Ãü™y‚Z
¡ëÙnܼ ÖÁbÊf`f3Û¸»Íf#À…»fûTCPA…°ù‚¨faf`g€{…
gfSgf‹
ë%gfSgf‹J(fùƒ
gf‹B,f#À„f3Éèõýf#É„2fº€f;ʆf+ÊfQfWfRf‹Êè·ýèûýfZf_fYfúëÚè¥ýèéýèþf»TCPAf¿
 f___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows,grub and grub2

2008-09-01 Thread Viswesh S 




- Original Message 
From: Bean <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Monday, 1 September, 2008 8:05:29 PM
Subject: Re: Windows,grub and grub2


Hi,

Perhaps you can dump the biosdisk information as well

#include 

...

struct grub_biosdisk_data *data = (struct grub_biosdisk_data *) dev->disk->data

then print its members (drive, cylinders, heads, sectors, flags).
Also, please try copy the boot sector to a file and chainload it.


-- 
Bean

Hi,

I have dumped the biosdisk information also

data->drive=0x80
data->cylinders=0x3ff
data->heads=0xff
data->sectors=0x3f
data->flag=0x1

Chainloading from a file doesnt help either

dd if=/dev/hda1 of=chainload.txt bs=512 count=1

In the grub2 command:

set root=(hd0,1)
chainloader (hd0,4)/boot/chainload.txt

No effect :( same error

Viswesh



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Unlimited freedom, unlimited storage. Get it now, on 
http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows,grub and grub2

2008-09-01 Thread Viswesh S 




- Original Message 
From: Bean <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Monday, 1 September, 2008 6:32:28 PM
Subject: Re: Windows,grub and grub2

On Mon, Sep 1, 2008 at 6:48 PM, Viswesh S <[EMAIL PROTECTED]> wrote:
>
>

Hi,

I doubt that this is caused by int 13, as grub2 doesn't change it.
Besides, the boot sector is read properly in grub2, so int 13 should
be working.

I have thought of another possible reason for this. In grub2, %dh is
0, perhaps it should be set to the partition number. Please test if
the new patch works.

-- 
Bean


Hi,

To get more insight and see whether the values are proper,I dumped the 
structure members.

So for the commands:

set root=(hd0,1)
chainloader +1

This is disk and partition strucure member values.

disk->name=(hd0,1)
disk->has_partitions=1
disk->id=0x80

For the partition p,

p->offset=0
p->index=0
p->data=0
p->start=0x3f
p->len = 0x0
p->offset=0x4e1edec
p->partmap->name=(null)
part_addr=0x7be

And this is the dump from the mbr:

01b0   00 00 00 00 00 00 00 00 81 eb 09 00 00 00 80 01  
||
01c0   01 00 07 fe  ff ff 3f 00  00 00 ec ed e1 04 00 fe  
|..?.|
01d0   ff ff 07 fe ff ff 00 f0   e1 04 00 18 30 0b 00 fe  
|0...|
01e0   ff ff 82 fe ff ff cf 0e   12 10 33 91 3b 00 00 fe  
|..3.;...|
01f0    ff ff 83 fe ff ff 02 a0  4d 10 bf ea 53 02 55 aa  
|M...S.U.|

Viswesh

ps:-The previous patch also didnt work :-(


  Download prohibited? No problem. CHAT from any browser, without download. 
Go to http://in.webmessenger.yahoo.com/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows,grub and grub2

2008-09-01 Thread Viswesh S 
 
- Original Message 
From: Bean <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Monday, 1 September, 2008 6:32:28 PM
Subject: Re: Windows,grub and grub2

On Mon, Sep 1, 2008 at 6:48 PM, Viswesh S <[EMAIL PROTECTED]> wrote:
>
>

Hi,

I doubt that this is caused by int 13, as grub2 doesn't change it.
Besides, the boot sector is read properly in grub2, so int 13 should
be working.

I have thought of another possible reason for this. In grub2, %dh is
0, perhaps it should be set to the partition number. Please test if
the new patch works.

-- 
Bean

Hi,
 
The index in this case is 0,Hence will it really affect it ?
 
Thanks,
Viswesh


  Add more friends to your messenger and enjoy! Go to 
http://in.messenger.yahoo.com/invite/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows,grub and grub2

2008-09-01 Thread Viswesh S 




- Original Message 
From: Bean <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Monday, 1 September, 2008 3:46:32 PM
Subject: Re: Windows,grub and grub2

On Mon, Sep 1, 2008 at 5:08 PM, Viswesh S <[EMAIL PROTECTED]> wrote:
>
>

Hi,

Do you mean the result is still the same after you apply my patch ? I
check the source code of grub legacy, the handling should be exactly
the same. Are you using the official branch grub 0.96, or some package
with modification ?

You can also check memory at 0x7be, this should be the partition table
in mbr, %esi would point to the boot partition.

-- 
Bean

Hi,

The result is still the same after the patch.

I am using the official grub2 released package 1.96.

In that the chainloader patch wasnt there.Hence applied that according to your 
inputs as in the mail.

I checked the memory at 0x7be, which is the same as 0x1be in the mbr.

The first partition was already active also.

Also as I mentioned,what about the code for the int 13 extension and and their 
functionalities for 2,41,42.

Is there any change there.

Otherwise I am not really sure, why grub is able to boot,but grub2 not.

Viswesh
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Unlimited freedom, unlimited storage. Get it now, on 
http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows,grub and grub2

2008-09-01 Thread Viswesh S 




- Original Message 
From: Bean <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Saturday, 30 August, 2008 11:01:18 AM
Subject: Re: Windows,grub and grub2

> Hi,
>
> I thinks it's caused by partition entry pointer %esi which isn't
> correct in grub2, please see if this patch fixes the problem.
>
> --
> Bean
>

Hi,

BTW, you should use the following command:

set root=(hd0,1)
chainloader +1

It's not the same as chainloader (hd0,1)+1, as chainloader command
would use the value of root to decide the boot partition index.

-- 
Bean

Hi,

There was no need for the initial partition to me made active, as it was 
already active.So trying that didnt help out anyway.

Initially I was not calling set root=(hd0,1).

But even after I use it, the results were the same.

The location 7c00 was good, so the boot record is getting copied correctly.

I am repeating my earlier doubt, are we sure that,the assembly part of both 
grub-legacy and grub2 doesnt have any changes with respect to grub2, especially 
in th

I still feel, there might be a problem with that, as I feel we are jumping into 
boot record of windows and then going to an infinite after dumping the error :A 
disk read error occurred'

Viswesh


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Download prohibited? No problem. CHAT from any browser, without download. 
Go to http://in.webmessenger.yahoo.com/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Windows,grub and grub2

2008-08-29 Thread Viswesh S 
Hi,

I am back with my Windows boot up question using grub and grub2.Sorry for 
making the question a bit long.

Some experiments and results which I did.

Scenario: One hard disk,different partitions.

Case 1: 

Partition 1 -> Windows Server 2003
Partition 2 -> Swap
Partition 3 -> Linux

Boot loader : Grub2.

Windows boots up successfully from grub2 using chainloading (hd0,1) +1

Case 2:

Installed server 2008 in the free space in between Server 2003 and swap.

Partition 1 : Windows server 2003
Partition 2: Windows server 2008
Partition 3 :Swap
Partition 4:Linux

Grub2 doesnt boot up windows with the command chainloader (hd0,1) +1, with 
error 

A disk read error occurred 
Ctrl+Alt +del to restart.

But Grub legacy boots up with no issues , with the same command, prefixed with 
rootnoverify hd0

Case 3:

Partition 1 :Boot
Partition 2:Windows
Partition 3: Linux

Same behaviour : Grub2 doesnt boot Windows with chainloader command (hd0,2) +1

Same error as before.

Not surprisingly grub boots with the same command.

I had a look at the boot sector code of Windows, which gets copied, by dumping 
the partition using dd.

For me, it looked the same.

Also another hunch is that,as the error ( A disk read error occurred ),, 
happened in Windows boot sector, find the areas in boot sector code of Windows 
where it calls this error and goes into an infinite loop.

So in the different cases, I could see that it is something to do with the INT 
13 call, with functions 41 and 42.

Can anyone let me know the differences here, with respect to grub2 and grub.

Also,on more thing is the way chainloader command is written in grub and 
grub2.I was finding it difficult to decode the assembly parts in both and find 
out the differences.

Can anyone pour some advice and directions on these.

Thanks in advance,

Viswesh


  Unlimited freedom, unlimited storage. Get it now, on 
http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows boot

2008-08-10 Thread Viswesh S 




- Original Message 
From: Bean <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Friday, 8 August, 2008 4:00:41 PM
Subject: Re: Windows boot

On Fri, Aug 8, 2008 at 2:50 PM, Viswesh S <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Thanks,let me have a look at the chainloader command in grub2 and in legacy
> grub.
>
> Could you let me know the issue which you faced in the chainloader command.

Hi,

The problem is in loader/i386/pc/chainloader.c (grub_chainloader_cmd):

  /* Obtain the partition table from the root device.  */
  dev = grub_device_open (0);
  if (dev)
    {
      grub_disk_t disk = dev->disk;

      if (disk)
    {
      grub_partition_t p = disk->partition;
    
      /* In i386-pc, the id is equal to the BIOS drive number.  */
      drive = (int) disk->id;

      if (p)
        {
          grub_disk_read (disk, p->offset, 446, 64,
                  (char *) GRUB_MEMORY_MACHINE_PART_TABLE_ADDR);
          part_addr = (void *) (GRUB_MEMORY_MACHINE_PART_TABLE_ADDR
                    + (p->index << 4));
        }
    }

      grub_device_close (dev);
    }

p->offset is the offset of the start of the partition, but actually,
we need to read the sector that contain the partition table, which is
the mbr for primary. But replace p->offset with 0 doesn't fix this, as
grub_disk_read is related to the beginning of partition, not the disk.
You need to use the low level api:

disk->dev->read (disk, 0, 1, (char *) GRUB_MEMORY_MACHINE_PART_TABLE_ADDR);

But this fix only apply to primary partition, for logical partition,
the partition table is not in mbr, and this quick patch doesn't work.
But I remember someone send a patch to allow for loading of syslinux
in logical partition, you can search the list if you're interested.

BTW, if this doesn't work, you can try loadbin. It can be used to
chainload ntldr/bootmgr directly.

Hi,
I tried the loadbin,according to the instructions which you had given in 
osdir.com
" 
linux loadbin.bin
initrd ntldr

This method is not limited to grub2, it can also be used in boot
loaders which support the linux kernel format, such as
syslinux/lilo/grub.

To compile loadbin.bin, use the following commands:

gcc -nostdlib -DLOADBIN -Wl,-N -o lnxhdr lnxhdr.S
objcopy -O binary lnxhdr lnxhdr.bin
"
Are you sure, this is the procedure ? Dont we need to generate loadbin ?
Could you please confirm ?
Regards,
Viswesh

-- 
Bean


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Add more friends to your messenger and enjoy! Go to 
http://in.messenger.yahoo.com/invite/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: [PATCH] Drivemap module

2008-08-08 Thread Viswesh S 




- Original Message 
From: Felix Zielcke <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Friday, 8 August, 2008 6:50:12 PM
Subject: Re: [PATCH] Drivemap module

Am Mittwoch, den 06.08.2008, 19:31 +0200 schrieb Javier Martín:

> This will work on Windows, because no matter where it tries to boot from
> it will find the same disk: both the first and second BIOS disks point
> to hd1 now. 
> ...
> This is the setup I have
> extensively tested in QEMU, while the Windows boot has been tested in
> both QEMU (with ReactOS) and some random computers including mine (with
> Windows XP Home and Windows XP Pro x64).
> 

Even though I don't need your drivemap at all (see one of my replies to
Marco's ATA topic) I was so kind to try this out with my Vista x64
SP1 ;)

I haven't remembered exactly the 2 menuentrys you wrote in your mail so
I used a mixture of both :)

drivemap (hd1) (hd0)
set root=(hd0)
chainloader (hd1,1)+1

This booted fine for me, GRUB loaded from IDE disk and Vista chainloaded
from my SATA RAID 0.

I really hope that you get this commited, then there's one feature less
missing from grub-legacy ;)

Hi,
Nice to know that the patch is working..for others also.meanwhile I am not too 
much sure,why the same is not happening to me.
The only difference in this case is that , my linux is in sata and my windows 
is in IDE.
Viswesh

___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Unlimited freedom, unlimited storage. Get it now, on 
http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows boot

2008-08-08 Thread Viswesh S 




- Original Message 
From: Bean <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Friday, 8 August, 2008 12:10:24 PM
Subject: Re: Windows boot

On Fri, Aug 8, 2008 at 2:22 PM, Viswesh S <[EMAIL PROTECTED]> wrote:
>
>
> - Original Message 
> From: Bean <[EMAIL PROTECTED]>
> To: The development of GRUB 2 
> Sent: Friday, 8 August, 2008 9:13:09 AM
> Subject: Re: Windows boot
>
> On Fri, Aug 8, 2008 at 9:58 AM, Viswesh S <[EMAIL PROTECTED]> wrote:
>>
>>
>> - Original Message 
>> From: Javier Martín <[EMAIL PROTECTED]>
>> To: The development of GRUB 2 
>> Sent: Friday, 8 August, 2008 3:56:35 AM
>> Subject: Re: Windows boot
>>
>> Hi again,
>>
>> 2008/8/7 Viswesh S <[EMAIL PROTECTED]>:
>>> Hi,
>>>
>>> I installed ubuntu in the same harddisk(hda) as windows.
>>>
>>> After installing ubuntu, using grub legacy, I was able to log in to
>>> windows,
>>> using the entries, rootnoverify and chainloader +1.
>>>
>>> But when I install grub2 and then modify the grub.cfg with the following,
>>> statements, it is not working, says ...A disk read error occurred ,Press
>>> Ctrl+Alt+Del .
>>>
>>> This is my grub.cfg
>>>
>>> menuentry "Windows" {
>>>    set root=(hd0,3)
>>>    chainloader +1
>>>
>>> }
>>>
>>> My windows file sytem is in NTFS and not vfat
>>>
>>> One more thing to check with is, the need of ntfs mod present as part of
>>> grub2.So where exactly that is getting used,though I have tried to load
>>> the
>>> module ntfs and ntfscomp in grub using insmod in grub menu,...but no
>>> positive results.
>> The FS only matters if you try to access files on the volume, but
>> chainloader just reads raw sectors from disk, so the FS module does
>> not matter: you could have an SFS partition for the sake of it and it
>> would work if the superblock was executable.
>>>
>>> What might be in grub2, which prevents windows to boot.
>> Hmm... you could try booting (hd1) instead of (hd1,1), i.e. Windows'
>> MBR instead of its boot sector directly. I'll be back in town tomorrow
>> night and then I'll be able to look at my own GRUB config file, but
>> Windows has always been a wild beast to master. For the record, my
>> tests were with Windows XP Home in an Athlon X2 and with Windows XP
>> x64 on an Athlon 64. Thus, I don't know if Intel CPUs triple-fault on
>> my code (improbable, because it runs on QEMU) or if Windows Vista
>> (which has a changed boot process) works with it.
>>
>>
>> Hi,
>>
>> Windows I am trying to boot is Windows Server 2003, but anyway that doesnt
>> matter, as from legacy grub,I am able to boot.This makes it more
>> interesting, as I feel we are missing some small intricacy in grub2 in
>> this
>> case.
>>
>> Let me also have a look.
>
> Hi,
>
> What's the command you use in grub legacy ?
>
> BTW, you should know that device number of grub2 is not the same as
> grub legacy, the first partition is (hd0,1) instead of (hd0,0).
> Anyway, you can use ls to list the current devices.
>
> --
> Bean
> Hi,
>
> The partition number difference I am aware of.That difference was taken into
> account.
>
> In the case of grub legacy,the grub.cfg was in this way.
>
> menuentry "Windows" {
>
> rootnoverify
> chainloader +1
> }
>
> As windows is in the 3 partition, using ls (hd0,3) I could see windows
> files.
>
> so the grub.cfg
>
> menuentry "Win" {
>
> chainloader (hd0,3)+1
> }
>
> (or)
>
> menuentry "Win" {
> set root=(hd0,3)
> chainloader +1
> }
>
> Tried both the combinations.But not working, getting the message ." A disk
> read Error occurred
>
>                        Press Ctrl+Alt+Del to restart.
>
> I am not sure whether this is a filesystem issue (ntfs) which grub2 is not
> able to identify as such (or) Grub2 is not able to read the boot sector
> correctly.( As  legacy grub was able to boot quite easily the same thing)
>
> I am badly stuck and I dont want to go back to legacy grub also.

Hi,

I think it's not related to ntfs, chainloader command read the first
sector, it doesn't matter what file system is used.

But I do remember a small issue with chainloader command of grub2, the
partition entry pointed to by %esi is not correct, I wonder if this
have something to do with your problem.

Hi,
Thanks,let me have a look at the chainloader command in grub2 and in legacy 
grub.
Could you let me know the issue which you faced in the chainloader command.
Viswesh

-- 
Bean



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Unlimited freedom, unlimited storage. Get it now, on 
http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows boot

2008-08-07 Thread Viswesh S 




- Original Message 
From: Bean <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Friday, 8 August, 2008 9:13:09 AM
Subject: Re: Windows boot

On Fri, Aug 8, 2008 at 9:58 AM, Viswesh S <[EMAIL PROTECTED]> wrote:
>
>
> - Original Message 
> From: Javier Martín <[EMAIL PROTECTED]>
> To: The development of GRUB 2 
> Sent: Friday, 8 August, 2008 3:56:35 AM
> Subject: Re: Windows boot
>
> Hi again,
>
> 2008/8/7 Viswesh S <[EMAIL PROTECTED]>:
>> Hi,
>>
>> I installed ubuntu in the same harddisk(hda) as windows.
>>
>> After installing ubuntu, using grub legacy, I was able to log in to
>> windows,
>> using the entries, rootnoverify and chainloader +1.
>>
>> But when I install grub2 and then modify the grub.cfg with the following,
>> statements, it is not working, says ...A disk read error occurred ,Press
>> Ctrl+Alt+Del .
>>
>> This is my grub.cfg
>>
>> menuentry "Windows" {
>>    set root=(hd0,3)
>>    chainloader +1
>>
>> }
>>
>> My windows file sytem is in NTFS and not vfat
>>
>> One more thing to check with is, the need of ntfs mod present as part of
>> grub2.So where exactly that is getting used,though I have tried to load
>> the
>> module ntfs and ntfscomp in grub using insmod in grub menu,...but no
>> positive results.
> The FS only matters if you try to access files on the volume, but
> chainloader just reads raw sectors from disk, so the FS module does
> not matter: you could have an SFS partition for the sake of it and it
> would work if the superblock was executable.
>>
>> What might be in grub2, which prevents windows to boot.
> Hmm... you could try booting (hd1) instead of (hd1,1), i.e. Windows'
> MBR instead of its boot sector directly. I'll be back in town tomorrow
> night and then I'll be able to look at my own GRUB config file, but
> Windows has always been a wild beast to master. For the record, my
> tests were with Windows XP Home in an Athlon X2 and with Windows XP
> x64 on an Athlon 64. Thus, I don't know if Intel CPUs triple-fault on
> my code (improbable, because it runs on QEMU) or if Windows Vista
> (which has a changed boot process) works with it.
>
>
> Hi,
>
> Windows I am trying to boot is Windows Server 2003, but anyway that doesnt
> matter, as from legacy grub,I am able to boot.This makes it more
> interesting, as I feel we are missing some small intricacy in grub2 in this
> case.
>
> Let me also have a look.

Hi,

What's the command you use in grub legacy ?

BTW, you should know that device number of grub2 is not the same as
grub legacy, the first partition is (hd0,1) instead of (hd0,0).
Anyway, you can use ls to list the current devices.

-- 
Bean

Hi,
The partition number difference I am aware of.That difference was taken into 
account.
In the case of grub legacy,the grub.cfg was in this way.
menuentry "Windows" {
rootnoverify
chainloader +1
}
As windows is in the 3 partition, using ls (hd0,3) I could see windows files.
so the grub.cfg 
menuentry "Win" {
chainloader (hd0,3)+1
}
(or) 
menuentry "Win" {
set root=(hd0,3)
chainloader +1
}
Tried both the combinations.But not working, getting the message ." A disk read 
Error occurred
                                                                                
                    Press Ctrl+Alt+Del to restart.
I am not sure whether this is a filesystem issue (ntfs) which grub2 is not able 
to identify as such (or) Grub2 is not able to read the boot sector correctly.( 
As  legacy grub was able to boot quite easily the same thing)
I am badly stuck and I dont want to go back to legacy grub also.
Viswesh


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Did you know? You can CHAT without downloading messenger. Go to 
http://in.webmessenger.yahoo.com/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows boot

2008-08-07 Thread Viswesh S 




- Original Message 
From: Javier Martín <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Friday, 8 August, 2008 3:56:35 AM
Subject: Re: Windows boot

Hi again,

2008/8/7 Viswesh S <[EMAIL PROTECTED]>:
> Hi,
>
> I installed ubuntu in the same harddisk(hda) as windows.
>
> After installing ubuntu, using grub legacy, I was able to log in to windows,
> using the entries, rootnoverify and chainloader +1.
>
> But when I install grub2 and then modify the grub.cfg with the following,
> statements, it is not working, says ...A disk read error occurred ,Press
> Ctrl+Alt+Del .
>
> This is my grub.cfg
>
> menuentry "Windows" {
>    set root=(hd0,3)
>    chainloader +1
>
> }
>
> My windows file sytem is in NTFS and not vfat
>
> One more thing to check with is, the need of ntfs mod present as part of
> grub2.So where exactly that is getting used,though I have tried to load the
> module ntfs and ntfscomp in grub using insmod in grub menu,...but no
> positive results.
The FS only matters if you try to access files on the volume, but
chainloader just reads raw sectors from disk, so the FS module does
not matter: you could have an SFS partition for the sake of it and it
would work if the superblock was executable.
>
> What might be in grub2, which prevents windows to boot.
Hmm... you could try booting (hd1) instead of (hd1,1), i.e. Windows'
MBR instead of its boot sector directly. I'll be back in town tomorrow
night and then I'll be able to look at my own GRUB config file, but
Windows has always been a wild beast to master. For the record, my
tests were with Windows XP Home in an Athlon X2 and with Windows XP
x64 on an Athlon 64. Thus, I don't know if Intel CPUs triple-fault on
my code (improbable, because it runs on QEMU) or if Windows Vista
(which has a changed boot process) works with it.
Hi,
Windows I am trying to boot is Windows Server 2003, but anyway that doesnt 
matter, as from legacy grub,I am able to boot.This makes it more interesting, 
as I feel we are missing some small intricacy in grub2 in this case.
Let me also have a look.
Viswesh

>
> Viswesh
>
>
> 
> Unlimited freedom, unlimited storage. Get it now
> ___
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Check out the all-new face of Yahoo! India. Go to http://in.yahoo.com/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Windows boot

2008-08-07 Thread Viswesh S 
Hi,
I installed ubuntu in the same harddisk(hda) as windows.
After installing ubuntu, using grub legacy, I was able to log in to windows, 
using the entries, rootnoverify and chainloader +1.
But when I install grub2 and then modify the grub.cfg with the following, 
statements, it is not working, says ...A disk read error occurred ,Press 
Ctrl+Alt+Del .
This is my grub.cfg
menuentry "Windows" {
    set root=(hd0,3)
    chainloader +1
}
My windows file sytem is in NTFS and not vfat
One more thing to check with is, the need of ntfs mod present as part of 
grub2.So where exactly that is getting used,though I have tried to load the 
module ntfs and ntfscomp in grub using insmod in grub menu,...but no positive 
results.
What might be in grub2, which prevents windows to boot.
Viswesh


  Add more friends to your messenger and enjoy! Go to 
http://in.messenger.yahoo.com/invite/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: [PATCH] Drivemap module

2008-08-07 Thread Viswesh S 




From: Javier Martín <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Wednesday, 6 August, 2008 11:01:19 PM
Subject: Re: [PATCH] Drivemap module

El mié, 06-08-2008 a las 07:43 -0700, Viswesh S escribió:
> Hi,
> 
>  
> 
> Could you let all know how to use your drivemap command.Is it similar
> to the map command in legacy grub.

Hi there. Information about the use of a command is better placed in the
wiki than in this list, however this command is not merged in yet, and I
reckon its "help" feature could be quite better.

Currently, the "safe" GRUB2 commands for booting from (hd1,1) is:

drivemap (hd0) (hd1)
drivemap (hd1) (hd0)
set root=(hd0)
chainloader (hd1,1)+1
boot

Maybe an explanation of what "drivemap" does would put a bit of light
here:

    * The BIOS hard disks are numbered from 0 to 128 (actually from 0x80 to
0xFF because the lower numbers are reserved for floppy disks). These
numbers are used to select the target drive when issuing I/O requests
through the BIOS routines (INT 13h)
    * When the BIOS loads a boot sector and transfers control to it, the DL
register contains the "boot disk number", i.e. the disk from which the
bootsector was loaded. This allows the bootsector to load its OS from
the same disk it was run, instead of having to probe every single disk
in the system.
    * The "chainloader" command works like the BIOS: it loads a bootsector
into memory and jumps to it. In this case, the value in DL corresponds
to the disk that was set as "root drive" to GRUB. If no root drive is
set, the OS receives 0xFF, which should be recognized as an impossible
drive. Some OSes will just trust this and fail (i.e. FreeDOS) while
others will try to boot from the first hard disk (0x80).
    * The "drivemap" command acts as the old TSRs from the DOS times: when
the "boot" command is issued, it installs its own handler for INT 13h
requests, which performs the requested mappings and then call the old
(usually BIOS) handler with the changed parameters. Thus, an OS
accessing the drive through the BIOS routines will see the drives moved,
duplicated or whatever the mappings provided. Again: drivemap does NOT
modify the "live" drive mappings within GRUB; its changes only affect
the booted OS.

The strange root=(hd0) line that appears to contradict the chainloader
line is there because drivemap has no communication with the particular
loader. If you set root to (hd1,1) and then issue chainloader and boot,
the OS will receive 0x81 in DL because hd1 was the second hard drive
when chainloader was issued (remember that drivemap doesn't act until
"boot"). Thus, the target OS will try to boot from what _it_ sees as the
second hard disk, which will now be the old hd0 - wrong.

If the target OS does not need to access the old hd0 or it only uses the
BIOS routines for the boot process (i.e. it later uses ATA drivers and
will redetect everything from scratch), you can leave the second
drivemap line out and use a more compact script like this:

drivemap (hd0) (hd1)
set root=(hd1,1)
chainloader +1
boot

This will work on Windows, because no matter where it tries to boot from
it will find the same disk: both the first and second BIOS disks point
to hd1 now. However, if you use a DOS-like system which uses the BIOS
routines exclusively (i.e. FreeDOS) then your hd0 disk would have
disappeared to it and you'd have D: to be a mirror of C:. In order to
have hd0 as D:, hd1 as C: and everything working, you need the first
script I posted, which makes the complete swap and then makes FreeDOS
load from the "first" hard drive (i.e. hd1). This is the setup I have
extensively tested in QEMU, while the Windows boot has been tested in
both QEMU (with ReactOS) and some random computers including mine (with
Windows XP Home and Windows XP Pro x64).

I'm looking forward to streamline the drivemap syntax, so that the two
drivemap lines can be fused into one like "drivemap --swap (hd0) (hd1)".
However, given that it's not a bug and that GRUB is still in heavy
development (and thus syntax changes are acceptable), I'd prefer to have
the patch integrated as it is - so we have the functionality - and then
modify what's needed - so we have it pretty.

-Habbit

Hi,
I have tried the same and different combinations,but still the machine is going 
for reset after I execute the boot command.
As nothing gets displayed also,I am not sure where exactly this is going wrong 
also.
What all might be the details in which I might have to look on, if I have to 
boot windows using grub2 only.
Viswesh


  Connect with friends all over the world. Get Yahoo! India Messenger at 
http://in.messenger.yahoo.com/?wm=n/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Remove conf/*.mk from svn

2008-08-05 Thread Viswesh S 
Hi,
I have a small suggestion.
Why cant we document in a small file, the procedures, or the dont's while 
adding modules or modifying grub2.A FAQ file may be.
That will help us in the long run.
Viswesh


- Original Message 
From: Felix Zielcke <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Tuesday, 5 August, 2008 9:25:43 PM
Subject: Re: Remove conf/*.mk from svn

Am Dienstag, den 05.08.2008, 17:48 +0200 schrieb Marco Gerards:

> 
> Actually, since ruby is required to generate these files, I guess we
> can better keep the .mk files.
> 

Just a little note from me:

The Debian package build depends already on ruby so this won't be a
problem for all Debian guys and especially not for Robert or me.

On Debian/Ubuntu you can just use 'apt-get build-dep grub2' and it
installs every package for you which you need to build grub2 so ruby
will be always needed/installed for the Debian package.

But well Debian isn't the only distribution and I don't know how others
deal with grub2 :)



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Download prohibited? No problem. CHAT from any browser, without download. 
Go to http://in.webmessenger.yahoo.com/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows

2008-07-30 Thread Viswesh S 
I had tried the grub configuration which you have suggested before, from the 
wiki.
But still there wasnt any use :(
Viswesh



- Original Message 
From: Javier Martín <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Wednesday, 30 July, 2008 11:59:34 PM
Subject: Re: Windows

2008/7/30 Viswesh S <[EMAIL PROTECTED]>:
> The problem is that, I am not able to boot windows by this configuration.
>
>
>
> I am getting the error
>
>
>
> "A disk read Error Occurred"
>
>
>
> If I make the windows disk as the first boot device,then windows is coming
> up properly.
Drivemap module to the rescue!! ^^
Hoping to resurrect the discussion about it, I developed the module
for just that purpose: I have a similar configuration, in which
Windows refuses to boot if its drive is not "the first BIOS drive".

In some cases and versions of Windows you can make it work without the
drivemap module with:
menuentry "Windows" {
    set root=(hd1,1)
    chainloader +1
}
But not all versions of NTLDR obey the "boot drive" parameter passed
in DL: in GRUB legacy, this was solved by the "map" command which made
Windows believed it was booting from the first BIOS drive by
intercepting all BIOS I/O calls and mapping the drive numbers - the
proposed "drivemap" module does the same in GRUB2, but it's not been
accepted yet (ahem xD).

>
>
>
> Hence I feel this is something to do with the grub2 configuration which is
> missing.
>
>
>
> If any needs any information(about my machine) to configure grub2 for
> windows,please let me know.
>
>
>
> Regards,
>
>
>
> Viswesh
>
> - Original Message 
> From: Pavel Roskin <[EMAIL PROTECTED]>
> To: The development of GRUB 2 
> Sent: Wednesday, 30 July, 2008 11:39:56 PM
> Subject: Re: Windows
>
> On Wed, 2008-07-30 at 11:00 -0700, Viswesh S wrote:
>> menuentry "Windows" {
>>    chainloader (hd1,1)+1
>> }
>>
>> Is all this is sufficient or is there anything else I should add.
>
> I think you are better off describing the problem, not asking others to
> guess what could be wrong without knowing what the problem is.
>
> --
> Regards,
> Pavel Roskin
>
>
> ___
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
> 
> Add more friends to your messenger and enjoy! Invite them now.
> ___
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Did you know? You can CHAT without downloading messenger. Go to 
http://in.webmessenger.yahoo.com/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Windows

2008-07-30 Thread Viswesh S 
The problem is that, I am not able to boot windows by this configuration.
I am getting the error
"A disk read Error Occurred"
If I make the windows disk as the first boot device,then windows is coming up 
properly.
Hence I feel this is something to do with the grub2 configuration which is 
missing.
If any needs any information(about my machine) to configure grub2 for 
windows,please let me know.
Regards,
Viswesh



- Original Message 
From: Pavel Roskin <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Wednesday, 30 July, 2008 11:39:56 PM
Subject: Re: Windows

On Wed, 2008-07-30 at 11:00 -0700, Viswesh S wrote:
> menuentry "Windows" {
>    chainloader (hd1,1)+1
> }
>  
> Is all this is sufficient or is there anything else I should add.

I think you are better off describing the problem, not asking others to
guess what could be wrong without knowing what the problem is.

-- 
Regards,
Pavel Roskin


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Unlimited freedom, unlimited storage. Get it now, on 
http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Windows

2008-07-30 Thread Viswesh S 
Hi,
With grub2,what are the things I should take care, if I have another hard disk 
(ide , primary) with windows.
My initial boot device is a sata one with linux.
This is my device map 
(hd0)   /dev/sda
(hd1)   /dev/hda

My fdisk
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot  Start End  Blocks   Id  System
/dev/sda1   *   1    3647    29294496   83  Linux
/dev/sda2    3648    4133 3903795   82  Linux swap / Solaris
/dev/sda3    4134   10322    49713142+  83  Linux
/dev/sda4   10323   19457    73376887+   5  Extended
/dev/sda5   10323   19457    73376856   83  Linux
Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot  Start End  Blocks   Id  System
/dev/hda1   *   1    9729    78148161    7  HPFS/NTFS
/dev/hda2    9730   19458    78140416    7  HPFS/NTFS

This is my grub.cfg for windows
menuentry "GNU/Linux, linux 2.6.15-51-amd64-k8" {
    linux   (hd0,1)/boot/vmlinuz-2.6.15-51-amd64-k8 root=/dev/sda1 ro
    initrd  (hd0,1)/boot/initrd.img-2.6.15-51-amd64-k8
}
menuentry "GNU/Linux, linux 2.6.15-51-amd64-k8 (single-user mode)" {
    linux   (hd0,1)/boot/vmlinuz-2.6.15-51-amd64-k8 root=/dev/sda1 ro single
    initrd  (hd0,1)/boot/initrd.img-2.6.15-51-amd64-k8
}
menuentry "Windows" {
    chainloader (hd1,1)+1
}
Is all this is sufficient or is there anything else I should add.
Viswesh


  Connect with friends all over the world. Get Yahoo! India Messenger at 
http://in.messenger.yahoo.com/?wm=n/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

atoi

2008-07-26 Thread Viswesh S 
Hi,
Just a confirmation, 
Is there an implementation for atoi or similar conversion implemented in grub2 
already.
I suppose, I need to implement it myself.
I am planning to implement a setpci command in grub2.Hence the question
Viswesh


  Did you know? You can CHAT without downloading messenger. Go to 
http://in.webmessenger.yahoo.com/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Linking

2008-07-25 Thread Viswesh S 
Suppose I am adding a new command,so should I create a new file for that 
command and modify only the command,rmk accordingly?
All the other files get autogenerated by autogen.sh ?
Is this sufficient ?
Viswesh



- Original Message 
From: Colin D Bennett <[EMAIL PROTECTED]>
To: grub-devel@gnu.org
Sent: Friday, 25 July, 2008 7:31:28 PM
Subject: Re: Linking

On Fri, 25 Jul 2008 03:22:57 -0700 (PDT)
Viswesh S <[EMAIL PROTECTED]> wrote:

> The reason for hello to be put in a directory because it is a module
> and not a simple command.Understood myself

Actually, no.  Every C source file in the 'commands' directory is
currently a module itself.

I think the reason that 'hello.mod' is separated out is to make it
easier to see that there is only one source file as part of 'hello.mod'.

Regards,
Colin


> - Original Message 
> From: Viswesh S <[EMAIL PROTECTED]>
> To: The development of GRUB 2 
> Sent: Friday, 25 July, 2008 3:44:48 PM
> Subject: Re: Linking
> 
> 
> Hi,
>  
> So if I add a module or add a new command,which are the files which I
> should modify in general and which all gets generated automatically. 
> Is this somewhere documented ?
>  
> Why is it that hello command is put in a separate directory, while
> lspci is put inside the commands directory. 
> Is there a specific reason for this.
>  
>  
> Viswesh
> 
> 
> 
> - Original Message 
> From: Pavel Roskin <[EMAIL PROTECTED]>
> To: grub-devel@gnu.org
> Sent: Friday, 25 July, 2008 11:59:21 AM
> Subject: Re: Linking
> 
> Quoting Viswesh S <[EMAIL PROTECTED]>:
> 
> > Hi Pavel,
> > Could you please attach the modified file ?
> > Viswesh
> 
> No, I'm just giving you an idea what you may be doing wrong.
> 


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Share files, take polls, and make new friends - all under one roof. Go to 
http://in.promos.yahoo.com/groups/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Linking

2008-07-25 Thread Viswesh S 
The reason for hello to be put in a directory because it is a module and not a 
simple command.Understood myself



- Original Message 
From: Viswesh S <[EMAIL PROTECTED]>
To: The development of GRUB 2 
Sent: Friday, 25 July, 2008 3:44:48 PM
Subject: Re: Linking


Hi,
 
So if I add a module or add a new command,which are the files which I should 
modify in general and which all gets generated automatically.
 
Is this somewhere documented ?
 
Why is it that hello command is put in a separate directory, while lspci is put 
inside the commands directory.
 
Is there a specific reason for this.
 
 
Viswesh



- Original Message 
From: Pavel Roskin <[EMAIL PROTECTED]>
To: grub-devel@gnu.org
Sent: Friday, 25 July, 2008 11:59:21 AM
Subject: Re: Linking

Quoting Viswesh S <[EMAIL PROTECTED]>:

> Hi Pavel,
> Could you please attach the modified file ?
> Viswesh

No, I'm just giving you an idea what you may be doing wrong.

-- 
Regards,
Pavel Roskin


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


Bring your gang together. Do your thing. Find your favourite Yahoo! Group.


  Forgot the famous last words? Access your message archive online at 
http://in.webmessenger.yahoo.com/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Linking

2008-07-25 Thread Viswesh S 
Hi,
So if I add a module or add a new command,which are the files which I should 
modify in general and which all gets generated automatically.
Is this somewhere documented ?
Why is it that hello command is put in a separate directory, while lspci is put 
inside the commands directory.
Is there a specific reason for this.
Viswesh



- Original Message 
From: Pavel Roskin <[EMAIL PROTECTED]>
To: grub-devel@gnu.org
Sent: Friday, 25 July, 2008 11:59:21 AM
Subject: Re: Linking

Quoting Viswesh S <[EMAIL PROTECTED]>:

> Hi Pavel,
> Could you please attach the modified file ?
> Viswesh

No, I'm just giving you an idea what you may be doing wrong.

-- 
Regards,
Pavel Roskin


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Unlimited freedom, unlimited storage. Get it now, on 
http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Linking

2008-07-24 Thread Viswesh S 
Hi Pavel,
Could you please attach the modified file ?
Viswesh



- Original Message 
From: Pavel Roskin <[EMAIL PROTECTED]>
To: grub-devel@gnu.org
Sent: Friday, 25 July, 2008 11:05:49 AM
Subject: Re: Linking

Quoting Viswesh S <[EMAIL PROTECTED]>:

> I have modified the conf/common.mk accordingly as shown below.

It's a generated file.  Please modify conf/common.rmk instead and run  
autogen.sh.

-- 
Regards,
Pavel Roskin


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



  Explore your hobbies and interests. Go to 
http://in.promos.yahoo.com/groups/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Linking

2008-07-24 Thread Viswesh S 
Hi,
I am quite new to grub2 anf I find some issue in make of grub2
I modify the hello module by adding a new file a.c, with a function test() in 
it.
I call the function test from hello entry point - grub_cmd_hello()
When I do a make, I get the error that 
test in hello is not defined
make: *** [moddep.lst] Error 1

I have modified the conf/common.mk accordingly as shown below.
# For hello.mod.
hello_mod_SOURCES = hello/hello.c hello/a.c
CLEANFILES += hello.mod mod-hello.o mod-hello.c pre-hello.o 
hello_mod-hello_hello.o hello_mod-hello_a.o und-hello.lst
ifneq ($(hello_mod_EXPORTS),no)
CLEANFILES += def-hello.lst
DEFSYMFILES += def-hello.lst
endif
MOSTLYCLEANFILES += hello_mod-hello_hello.d  hello_mod-hello_a.d
UNDSYMFILES += und-hello.lst
hello.mod: pre-hello.o mod-hello.o
    -rm -f $@
    $(TARGET_CC) $(hello_mod_LDFLAGS) $(TARGET_LDFLAGS) -Wl,-r,-d -o $@ $^
    $(STRIP) --strip-unneeded -K grub_mod_init -K grub_mod_fini -R .note -R 
.comment $@
pre-hello.o: $(hello_mod_DEPENDENCIES) 
hello_mod-hello_hello.o hello_mod-hello_a.o
    -rm -f $@
    $(TARGET_CC) $(hello_mod_LDFLAGS) $(TARGET_LDFLAGS) -Wl,-r,-d -o $@ 
hello_mod-hello_hello.o
mod-hello.o: mod-hello.c
    $(TARGET_CC) $(TARGET_CPPFLAGS) $(TARGET_CFLAGS) $(hello_mod_CFLAGS) -c 
-o $@ $<
mod-hello.c: moddep.lst genmodsrc.sh
    sh $(srcdir)/genmodsrc.sh 'hello' $< > $@ || (rm -f $@; exit 1)
ifneq ($(hello_mod_EXPORTS),no)
def-hello.lst: pre-hello.o
    $(NM) -g --defined-only -P -p $< | sed 's/^\([^ ]*\).*/\1 hello/' > $@
endif
und-hello.lst: pre-hello.o
    echo 'hello' > $@
    $(NM) -u -P -p $< | cut -f1 -d' ' >> $@
hello_mod-hello_hello.o: hello/hello.c $(hello/hello.c_DEPENDENCIES)
    $(TARGET_CC) -Ihello -I$(srcdir)/hello $(TARGET_CPPFLAGS)  
$(TARGET_CFLAGS) $(hello_mod_CFLAGS) -MD -c -o $@ $<
-include hello_mod-hello_hello.d
hello_mod-hello_a.o: hello/a.c $(hello/a.c_DEPENDENCIES)
    $(TARGET_CC) -Ihello -I$(srcdir)/hello $(TARGET_CPPFLAGS)  
$(TARGET_CFLAGS) $(hello_mod_CFLAGS) -MD -c -o $@ $<
-include hello_mod-hello_a.d

CLEANFILES += cmd-hello_mod-hello_hello.lst fs-hello_mod-hello_hello.lst
COMMANDFILES += cmd-hello_mod-hello_hello.lst
FSFILES += fs-hello_mod-hello_hello.lst
cmd-hello_mod-hello_hello.lst: hello/hello.c $(hello/hello.c_DEPENDENCIES) 
gencmdlist.sh
    set -e;   $(TARGET_CC) -Ihello -I$(srcdir)/hello 
$(TARGET_CPPFLAGS) $(TARGET_CFLAGS) $(hello_mod_CFLAGS) -E $<    | sh 
$(srcdir)/gencmdlist.sh hello > $@ || (rm -f $@; exit 1)
cmd-hello_mod-hello_a.lst: hello/a.c $(hello/a.c_DEPENDENCIES) gencmdlist.sh
    set -e;   $(TARGET_CC) -Ihello -I$(srcdir)/hello 
$(TARGET_CPPFLAGS) $(TARGET_CFLAGS) $(hello_mod_CFLAGS) -E $<    | sh 
$(srcdir)/gencmdlist.sh hello > $@ || (rm -f $@; exit 1)

fs-hello_mod-hello_hello.lst: hello/hello.c $(hello/hello.c_DEPENDENCIES) 
genfslist.sh
    set -e;   $(TARGET_CC) -Ihello -I$(srcdir)/hello 
$(TARGET_CPPFLAGS) $(TARGET_CFLAGS) $(hello_mod_CFLAGS) -E $<    | sh 
$(srcdir)/genfslist.sh hello > $@ || (rm -f $@; exit 1)
fs-hello_mod-hello_a.lst: hello/a.c $(hello/a.c_DEPENDENCIES) genfslist.sh
    set -e;   $(TARGET_CC) -Ihello -I$(srcdir)/hello 
$(TARGET_CPPFLAGS) $(TARGET_CFLAGS) $(hello_mod_CFLAGS) -E $<    | sh 
$(srcdir)/genfslist.sh hello > $@ || (rm -f $@; exit 1)

Could anyone let me know whether I need to do anything more.
Viswesh


  Explore your hobbies and interests. Go to 
http://in.promos.yahoo.com/groups/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Traces Scrolling - Grub2

2008-07-22 Thread Viswesh S 
Hi,
 
Enabling more traces in Grub2 doesnt help too much, as the screen will have 
only the last certain traces.
 
Is there anyway I can see all the traces.
 
Thanks,
 
Viswesh.
 
ps:- If there is a previous thread on this,let me know.
 

Explore your hobbies and interests. Click here to begin.


  From Chandigarh to Chennai - find friends all over India. Go to 
http://in.promos.yahoo.com/groups/citygroups/___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel