Hello all,
I like to keep some backup of my grub.cfg between each change.
I could obvioulsy do it manualy but may be something like:
# diff -Nau grub-mkconfig.orig grub-mkconfig
--- grub-mkconfig.orig 2010-01-24 14:43:52.0 +
+++ grub-mkconfig 2010-01-24 14:48:16.0 +000
Colin Watson wrote:
On Sat, Nov 28, 2009 at 06:21:20PM +, rubisher wrote:
Robert Millan wrote:
On Sun, Nov 22, 2009 at 01:10:11PM +, rubisher wrote:
But as far as the 1st parameter of grub_vsprintf is a pointer,
wouldn't it be better to write:
--- kern/misc.c.orig2009-11-22
Robert Millan wrote:
On Sun, Nov 22, 2009 at 01:10:11PM +, rubisher wrote:
But as far as the 1st parameter of grub_vsprintf is a pointer,
wouldn't it be better to write:
--- kern/misc.c.orig2009-11-22 13:07:22.0 +
+++ kern/misc.c 2009-11-22 13:07:51.0 +
@@ -
Hello all,
I am just reading kernel/misc.c file and read grub_vsprintf() definition as:
int
grub_vsprintf (char *str, const char *fmt, va_list args)
which is used by:
int
grub_vprintf (const char *fmt, va_list args)
{
int ret;
ret = grub_vsprintf (0, fmt, args);
return ret;
}
But as far
Hello all,
Is some off you could advise me at some starting point to investigate this
issue encountered to boot a lpar.
(I just take the opportunity to still have access to such platform to help
comunity)
Bean wrote:
On Sun, Oct 25, 2009 at 11:22 PM, rubisher wrote:
[snip]
Hi,
You
Hello all,
In another thread, I was annoying by strange and annoying messages
"cursor-on cursor-on word unknown" when booting any grub2 trunk, branch or
what ever release >= 1.97~beta3 on my lpar
After few reading on OpenFirmware, I figure out that's just because those
'word' (in forth's terms of
On Wed, 04 Nov 2009 12:07:29 +0100, Felix Zielcke
wrote:
> Am Mittwoch, den 04.11.2009, 10:55 +0100 schrieb rubisher:
>
>> > Right trunk contains my -I($srcdir)/include fix.
>> > merged now.
>> Sorry I don't agree with your fix:
>
> As you might have th
Felix,
On Tue, 03 Nov 2009 15:09:33 +0100, Felix Zielcke
wrote:
> Am Dienstag, den 03.11.2009, 14:51 +0100 schrieb rubisher:
>> On Tue, 03 Nov 2009 11:33:42 +0100, Felix Zielcke
>> wrote:
>> > Am Dienstag, den 03.11.2009, 11:21 +0100 schrieb rubisher:
>> >>
On Tue, 03 Nov 2009 11:33:42 +0100, Felix Zielcke
wrote:
> Am Dienstag, den 03.11.2009, 11:21 +0100 schrieb rubisher:
>> Hello Felix,
>>
>> On Mon, 02 Nov 2009 09:54:43 +0100, Felix Zielcke
>> wrote:
>> > Am Sonntag, den 01.11.2009, 23:04 +0100 schrieb Rober
Hello Felix,
On Mon, 02 Nov 2009 09:54:43 +0100, Felix Zielcke
wrote:
> Am Sonntag, den 01.11.2009, 23:04 +0100 schrieb Robert Millan:
>> On Sun, Nov 01, 2009 at 04:39:42PM +0100, Felix Zielcke wrote:
>> >
>> > I added now a comment that this shouldn't ever happen.
>> >
>> > New version avaible
Hello Felix,
Felix Zielcke wrote:
Am Samstag, den 31.10.2009, 02:44 -0400 schrieb Andrew Clausen:
Hi,
2009/10/30 Robert Millan :
What about probing in the boot-loader?
It's too late then. grub-install needs to know which filesystem module has
to be included in core.img.
What if the core.im
Bean wrote:
On Sun, Oct 25, 2009 at 11:22 PM, rubisher wrote:
[snip]
Hi,
You shouldn't need scsi, which is used by ata module to access pci
bus, but openfirmware would export the boot disk for you.
Use these command:
set debug=disk
ls
This should print some debug information in
Bean wrote:
On Sat, Oct 24, 2009 at 4:34 AM, rubisher wrote:
[snip]
As it seems that you have some experience with powerpc, may be can you
advise me with some your tips (how did you build your image, a sample of one
your menuentry?): I also tried to follow recipe of
<http://grub.enbug.
Bean wrote:
On Thu, Oct 22, 2009 at 5:12 PM, rubisher wrote:
On Thu, Oct 22, 2009 at 12:03 AM, rubisher wrote:
Bean wrote:
On Mon, Oct 12, 2009 at 4:55 PM, Felix Zielcke wrote:
David are you still there?
And also anyone who has access to a powerpc machine (and experience)?
In Debian we the
Hello Vladimir,
Vladimir 'phcoder' Serbinenko wrote:
rubisher wrote:
Vladimir 'phcoder' Serbinenko wrote:
Robert Millan wrote:
This should be a much cleaner option than maintaining libgcc.h by
hand. Only
tested on sparc, but it should also cast out the build problem
> On Thu, Oct 22, 2009 at 12:03 AM, rubisher wrote:
> > Bean wrote:
> >>
> >> On Mon, Oct 12, 2009 at 4:55 PM, Felix Zielcke wrote:
> >>>
> >>> David are you still there?
> >>> And also anyone who has access to a powerpc machine
Bean wrote:
On Mon, Oct 12, 2009 at 4:55 PM, Felix Zielcke wrote:
David are you still there?
And also anyone who has access to a powerpc machine (and experience)?
In Debian we the problem that the `__ashldi3' and `__bswapsi2' symbols
can't be found in the grub-ieee1275 build on powerpc and als
Hello Vladimir,
Vladimir 'phcoder' Serbinenko wrote:
rubisher wrote:
Felix Zielcke wrote:
Am Montag, den 12.10.2009, 10:55 +0200 schrieb Felix Zielcke:
And also anyone who has access to a powerpc machine (and experience)?
Oh and I forgot to mention, that the powerpc version doe
Vladimir 'phcoder' Serbinenko wrote:
Robert Millan wrote:
This should be a much cleaner option than maintaining libgcc.h by hand. Only
tested on sparc, but it should also cast out the build problems on powerpc.
1) Doesn't work in cross-compiler environment. You confused CC and TARGET_CC
Felix Zielcke wrote:
Am Montag, den 12.10.2009, 10:55 +0200 schrieb Felix Zielcke:
And also anyone who has access to a powerpc machine (and experience)?
Oh and I forgot to mention, that the powerpc version doestn't even build
now with 1.97~beta4:
_restgpr_31_x in boot is not defined
Full bu
Hello all,
Some time ago, I tried to install a debian distro (iirc 5.0) with net-install
cd on a IBM p510 lpar.
All works fine, but the yaboot which cd installed failed to boot this installation :_(. I well reported the issue but never
get feedback :_(
On the other hand I reach to install an
-- Initial header ---
>From : [EMAIL PROTECTED]
To : "Manoel" [EMAIL PROTECTED]
CC : "The development of GRUB 2" grub-devel@gnu.org,"Carlos Roberto
do Nascimento Costa" [EMAIL PROTECTED]
Date : Thu, 23 Oct 2008 14:08:55 -0500
Subject : Re: PPC64
> On Th
Hello Pavel,
Well I am totaly new here (grub2), because I am trying to boot a debian install
on a virtual partion of a p510.
This use a yaboot which failed to boot my install and even thought I reported in deep details the issue, I surprisingly got
any feedback? I so have to find another boot l
23 matches
Mail list logo