the order of the modules when create core image

the order of the modules when create core image

[yue315012-grub2]

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

Hi, all,
I don't know which mail list should I send this question to, so I send to here. Hope somebody will help me.
I create a MD raid0 in my VirtualBox that has two virtual disks (I create the Virtual PC according to my old PC.) Each disk has 2 partitions, one for raid, one for swap. no LVM on the raid0. and I want to use grub2 on it.
I got the src from svn 2008-11-11. and compiled it successfully. But when I install it with 
grub-install --modules=mdraid /dev/hda, the grub2 can't enter into normal mode. With ls command, it don't show the md1 device.
So I changed the module order in grub-install when create core image, move the $module to after biosdisk, and install again, the it shows the md1device. 
I think that I made the change in the grub-install is not a good idea, I want to know whether there is a better way to change the order of the modules when create or load the core.img.
 
BTW, how to debug the main.c in kern directory? If use grub-dprintf, I can't see all the debug info because the text scrolls too fast. Do you have better method?
 
Thanks

From Cola


      ___________________________________________________________ 
  好玩贺卡等你发，邮箱贺卡全新上线！ 
http://card.mail.cn.yahoo.com/

[-- Attachment #2: Type: text/html, Size: 1521 bytes --]

Re: the order of the modules when create core image

[Robert Millan]

On Mon, Nov 17, 2008 at 03:22:19PM +0800, yue315012-grub2@yahoo.com.cn wrote:
> Hi, all,
> I don't know which mail list should I send this question to, so I send to here. Hope somebody will help me.
> I create a MD raid0 in my VirtualBox that has two virtual disks (I create the Virtual PC according to my old PC.) Each disk has 2 partitions, one for raid, one for swap. no LVM on the raid0. and I want to use grub2 on it.
> I got the src from svn 2008-11-11. and compiled it successfully. But when I install it with 
> grub-install --modules=mdraid /dev/hda, the grub2 can't enter into normal mode. With ls command, it don't show the md1 device.
> So I changed the module order in grub-install when create core image, move the $module to after biosdisk, and install again, the it shows the md1device. 

Supporting this from user input is quite tricky.  Would be much better if it
can be auto-detected, like we do for LVM, etc.

What does "grub-probe -t abstraction /boot/grub" print?

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."