Hi,
For normal boot, the root device is passed to core.img in preloader.
However, if we load grub2 using linux header, there is no way to know
the root device. This patch add a new module findroot that can be used
to scan the root directory at startup.
One important usage is to create a grub2 boo
On Mon, May 12, 2008 at 10:16 PM, Isaac M. Marcos
<[EMAIL PROTECTED]> wrote:
> On Thursday 08 May 2008 17:45:27 Pavel Roskin wrote:
>> On Thu, 2008-05-08 at 11:53 -0430, Isaac M. Marcos wrote:
>> > > Try the CVS version. Try debugging the codedump.
>> >
>
> Done, same segfault.
I'm seeing a simi
On Sun, 18 May 2008 19:27:05 +0300
Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:
> Colin D Bennett wrote:
> > I think that using the TSC (w/ RDTSC instruction) and calibrating it
> > with a quick 2-3 RTC tick loop at startup might be the easiest
> > option.
>
> Hi Colin,
>
> What kind of accuracy
On Mon, 12 May 2008 09:33:54 -0700
Colin D Bennett <[EMAIL PROTECTED]> wrote:
> I think that using the TSC (w/ RDTSC instruction) and calibrating it
> with a quick 2-3 RTC tick loop at startup might be the easiest option.
Just wondered if something like this would be a practical way to go:
/
On Wed, 2008-05-21 at 00:37 +0800, Jeff Chua wrote:
> I'm seeing a similar segmentation fault today on a new Dell R200
> (quad-core). The same version (everything the same) works on my
> dual-core X60s.
>
> Command is 'grub-probe -d /dev/sda14'
>
> Using an older CVS version from February works
On Wed, May 21, 2008 at 3:53 AM, Pavel Roskin <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-05-21 at 00:37 +0800, Jeff Chua wrote:
>
>> I'm seeing a similar segmentation fault today on a new Dell R200
>> (quad-core). The same version (everything the same) works on my
>> dual-core X60s.
>>
>> Command is
