On Fri, Aug 8, 2008 at 3:12 AM, Robert Millan <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 07, 2008 at 11:17:14AM -0700, Colin D Bennett wrote:
>> I just have a couple of suggestions:
>>
>> On Fri, 8 Aug 2008 01:52:07 +0800
>> Bean <[EMAIL PROTECTED]> wrote:
>>
>> > On Thu, Aug 7, 2008 at 7:19 PM, Bean
This patch prevents the install of grub.d/10_windows on other OS.
grub-pe2elf is only installed if requested by --enable-grub-pe2elf. Even
on Cygwin, grub-pe2elf is only required during build.
Christian
2008-08-08 Christian Franke <[EMAIL PROTECTED]>
* Makefile.in: Add `target_os'
Felix Zielcke wrote:
Hello,
Am Freitag, den 08.08.2008, 14:59 +0200 schrieb Christian Franke:
No, grub-pe2elf is build and installed even if is not necessary for the
build process. This should be no problem.
Well it's the same as with that --enable-debug thingy ;)
In our Debian tru
Hello,
I have a brand new server: A Dell PowerEdge T105 Quad Core AMD64. I
installed it with Debian Lenny, which installed Lilo as a bootloader. I
installed grub2 manually:
grub-install /dev/sda
update-grub
When I boot I get dropped into a rescue shell because grub can't find
fd1. The output of
- 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
Hello,
Am Freitag, den 08.08.2008, 14:59 +0200 schrieb Christian Franke:
>
> No, grub-pe2elf is build and installed even if is not necessary for the
> build process. This should be no problem.
>
Well it's the same as with that --enable-debug thingy ;)
In our Debian trunk SVN I already commite
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 th
Robert Millan wrote:
On Fri, Aug 08, 2008 at 11:03:49AM +0200, Patrick Georgi wrote:
Hi,
I used cygwin to build grub2/i386-coreboot using an i386-elf cross
compiler. unfortunately the test in configure only looks for the host
platform and enables pe2elf in that case, even though my compile
On Fri, Aug 08, 2008 at 11:03:49AM +0200, Patrick Georgi wrote:
> Hi,
>
> I used cygwin to build grub2/i386-coreboot using an i386-elf cross
> compiler. unfortunately the test in configure only looks for the host
> platform and enables pe2elf in that case, even though my compiler emits
> ELF al
Patrick Georgi wrote:
Hi,
I used cygwin to build grub2/i386-coreboot using an i386-elf cross
compiler. unfortunately the test in configure only looks for the host
platform and enables pe2elf in that case, even though my compiler
emits ELF already.
my workaround is to just change that test (
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 (gr
On Fri, Aug 8, 2008 at 5:03 PM, Patrick Georgi <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I used cygwin to build grub2/i386-coreboot using an i386-elf cross compiler.
> unfortunately the test in configure only looks for the host platform and
> enables pe2elf in that case, even though my compiler emits EL
Am Freitag, den 08.08.2008, 11:55 +0200 schrieb Marco Gerards:
>
> Can't raid.mod be used for this, somehow?
I had this talk already with Bean on IRC.
At least the Nvidia nForce chipsets RAIDs have stored their 512 byte
superblock in (end of disks) - 1024 bytes.
The last 512 Bytes of both disks
Felix Zielcke <[EMAIL PROTECTED]> writes:
>> I currently always boot directly from my Raid 0
>> GRUB + Vista bootmgr + Vista \Windows\ is on Raid 0
>> my Linux / and so /boot is on my PATA disk.
>> This works totally fine for booting Vista and Linux.
>
> Oh and I forgot the Vista bootmgr file is
>
> I currently always boot directly from my Raid 0
> GRUB + Vista bootmgr + Vista \Windows\ is on Raid 0
> my Linux / and so /boot is on my PATA disk.
> This works totally fine for booting Vista and Linux.
>
Oh and I forgot the Vista bootmgr file is 326 KB big,
so even with my (probable big)
Hello Marco,
Am Freitag, den 08.08.2008, 11:17 +0200 schrieb Marco Gerards:
> Hi Felix,
>
> Most likely something failed in grub_ata_identify. you might want to
> add more debugging information there.
Ok I try.
> > ls (ata8) shows partition table
> > ls (ata8,1) or (ata8,2) unknown filesystem
Hi Felix,
Felix Zielcke <[EMAIL PROTECTED]> writes:
>> One minute ago I committed a patch to improve ATA support.
>>
> Probable better if I just send you know a mail instead of telling on
> IRC:
>
> This is shown for device 4,0 and 4,1
> PCI Dev (0,8,0) compat=1 rega=0x9e0=regb=0xbe0
>
> My firs
Hi,
I used cygwin to build grub2/i386-coreboot using an i386-elf cross
compiler. unfortunately the test in configure only looks for the host
platform and enables pe2elf in that case, even though my compiler emits
ELF already.
my workaround is to just change that test (there's no OS cyg_win),
- 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]>
>
Hello,
Am Freitag, den 08.08.2008, 01:46 +0200 schrieb Marco Gerards:
> Hi,
>
> One minute ago I committed a patch to improve ATA support.
>
Probable better if I just send you know a mail instead of telling on
IRC:
This is shown for device 4,0 and 4,1
PCI Dev (0,8,0) compat=1 rega=0x9e0=regb=0x
20 matches
Mail list logo
