Display upper_mem_limit and its rounded-down value in MiB.
Signed-off-by: Stefan Berger
---
grub-core/kern/ieee1275/init.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/grub-core/kern/ieee1275/init.c b/grub-core/kern/ieee1275/init.c
index 0f420d5b4..a3cb2a11a 100644
--- a/grub-core/kern
Display upper_mem_limit and its rounded-down value in MiB.
Signed-off-by: Stefan Berger
---
grub-core/kern/ieee1275/init.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/grub-core/kern/ieee1275/init.c b/grub-core/kern/ieee1275/init.c
index 0f420d5b4..a3cb2a11a 100644
--- a/grub-core/kern
On Mon, Nov 20, 2023 at 09:50:07AM -0500, Stefan Berger wrote:
> Display upper_mem_limit and its rounded-down value in MiB.
>
> Signed-off-by: Stefan Berger
Reviewed-by: Daniel Kiper
I will push this patch set together with other patches this week.
Thanks,
Daniel
Display upper_mem_limit and its rounded-down value in MiB.
Signed-off-by: Stefan Berger
---
grub-core/kern/ieee1275/init.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/grub-core/kern/ieee1275/init.c b/grub-core/kern/ieee1275/init.c
index 164cccb2a..72e0292a3 100644
--- a/grub-core/kern
Display upper_mem_limit and its rounded-down value in MiB.
Signed-off-by: Stefan Berger
---
grub-core/kern/ieee1275/init.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/grub-core/kern/ieee1275/init.c b/grub-core/kern/ieee1275/init.c
index 164cccb2a..72e0292a3 100644
--- a/grub-core/kern
Display upper_mem_limit and its rounded-down value in MiB.
Signed-off-by: Stefan Berger
---
grub-core/kern/ieee1275/init.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/grub-core/kern/ieee1275/init.c b/grub-core/kern/ieee1275/init.c
index 164cccb2a..72e0292a3 100644
--- a/grub-core/kern
Display upper_mem_limit and its rounded-down value in MiB.
Signed-off-by: Stefan Berger
---
grub-core/kern/ieee1275/init.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/grub-core/kern/ieee1275/init.c b/grub-core/kern/ieee1275/init.c
index a128a314e..a18d74092 100644
--- a/grub-core/kern
On Mon, Aug 14, 2023 at 03:00:10PM -0500, Glenn Washburn wrote:
> Signed-off-by: Glenn Washburn
Reviewed-by: Daniel Kiper
Daniel
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
Wed, 16 Aug 2023 12:53:48 -0500 Glenn Washburn :
> I specifically wanted these two sections to be subsections of
> x86_64-efi and not at the same level as i386-pc, hence why I have them
> as subsections. I suspect that the issue could be fixed by adding a
> @menu in the x86_64-efi section with the
On Wed, 16 Aug 2023 10:41:40 +0200
Olaf Hering wrote:
> Wed, 16 Aug 2023 00:29:28 -0500 Glenn Washburn :
>
> > Anyway, since you're the first and *so far* only person seeing this,
> > could you submit a patch that fixes this for you? It would be great to
> > support older makeinfos (if that is i
Wed, 16 Aug 2023 00:29:28 -0500 Glenn Washburn :
> Anyway, since you're the first and *so far* only person seeing this,
> could you submit a patch that fixes this for you? It would be great to
> support older makeinfos (if that is indeed the issue) in the upcoming
> release.
The change below fixe
On Tue, 15 Aug 2023 22:37:08 +0200
Olaf Hering wrote:
> Tue, 15 Aug 2023 12:31:29 -0500 Glenn Washburn :
>
> > I'm not seeing this issue when building on Debian 11. I'm successfully
> > building the info, html, and pdf documentation from the texi files
> > using debians texinfo package at versio
Tue, 15 Aug 2023 12:31:29 -0500 Glenn Washburn :
> I'm not seeing this issue when building on Debian 11. I'm successfully
> building the info, html, and pdf documentation from the texi files
> using debians texinfo package at version 6.7.0.dfsg.2-6. Are you sure
> you are building from clean sourc
On Tue, 15 Aug 2023 10:14:07 +0200
Olaf Hering wrote:
> Thu, 15 Jun 2023 13:06:09 +0200 Daniel Kiper :
>
> > Right now patch is in the git repo. If you want to improve that part of
> > doc please send a fix to grub-devel and CC interested folks.
>
> Yeah, that is very unfortunate, because it br
Thu, 15 Jun 2023 13:06:09 +0200 Daniel Kiper :
> Right now patch is in the git repo. If you want to improve that part of
> doc please send a fix to grub-devel and CC interested folks.
Yeah, that is very unfortunate, because it breaks the build:
https://lists.gnu.org/archive/html/bug-grub/2023-06/
Signed-off-by: Glenn Washburn
---
tests/util/grub-shell-luks-tester.in | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/tests/util/grub-shell-luks-tester.in
b/tests/util/grub-shell-luks-tester.in
index 850a20d6a7a8..3f9d1be17644 100644
--- a/tests/util/grub-shell-luks-teste
On Mon, Jul 10, 2023 at 10:01:15PM -0500, Glenn Washburn wrote:
> These are fairly trivial patches making it easier to turn on debugging
> when running tests.
>
> Glenn
>
> Glenn Washburn (4):
> grub-shell: Add --verbose to mkrescue when $debug is greater than 2
> g
These are fairly trivial patches making it easier to turn on debugging
when running tests.
Glenn
Glenn Washburn (4):
grub-shell: Add --verbose to mkrescue when $debug is greater than 2
grub-shell: Allow setting default timeout via
GRUB_SHELL_DEFAULT_TIMEOUT envvar
grub-shell: Allow
On Mon, Jun 26, 2023 at 12:12:33PM -0500, Glenn Washburn wrote:
> On Sun, 25 Jun 2023 14:27:57 -0500
> Oskari Pirhonen wrote:
>
> > Small set of wording and grammatical edits which did not make it in time
> > for the original review of the chapter.
>
> LGTM.
>
> Reviewed-by: Glenn Washburn
Revie
tions is taken care of automatically
> +when loading the kernel symbols via the user-defined GDB command
> +@command{dynamic_load_kernel_exec_symbols}, which takes one argument, the
> +address where the text section is loaded as determined by one of the methods
> +above. Alternatively,
d by one of the methods
+above. Alternatively, the command @command{dynamic_load_symbols} with the text
+section address as an agrument can be called to load the kernel symbols and set
+up loading the module symbols as they are loaded at runtime.
In the author's experience, when debugging wi
of the
> > methods
> > +above. Alternatively, the command @command{dynamic_load_symbols} with the
> > text
> > +section address as an agrument can be called to load the kernel symbols
> > and set
> > +up loading the module symbols as they are loaded at runtime.
Alternatively, the command @command{dynamic_load_symbols} with the
> text
> +section address as an agrument can be called to load the kernel symbols and
> set
> +up loading the module symbols as they are loaded at runtime.
>
> In the author's experience, when debuggin
above. Alternatively, the command @command{dynamic_load_symbols} with the text
+section address as an agrument can be called to load the kernel symbols and set
+up loading the module symbols as they are loaded at runtime.
In the author's experience, when debugging with QEMU and OVMF, to have
On Thu, Jun 15, 2023 at 13:06:09 +0200, Daniel Kiper wrote:
> On Thu, Jun 15, 2023 at 01:21:57AM -0500, Oskari Pirhonen wrote:
> > Oops, apologies for the late reply. Reading through it again, I found a
> > few more small nits:
>
> Right now patch is in the git repo. If you want to improve that pa
On Thu, Jun 15, 2023 at 01:21:57AM -0500, Oskari Pirhonen wrote:
> Oops, apologies for the late reply. Reading through it again, I found a
> few more small nits:
Right now patch is in the git repo. If you want to improve that part of
doc please send a fix to grub-devel and CC interested folks.
Da
Oops, apologies for the late reply. Reading through it again, I found a
few more small nits:
On Tue, Jun 06, 2023 at 00:48:39 -0500, Glenn Washburn wrote:
> Debugging GRUB can be tricky and require arcane knowledge. This will
> help those unfamiliar with the process to get started debuggin
On Tue, Jun 06, 2023 at 12:48:39AM -0500, Glenn Washburn wrote:
> Debugging GRUB can be tricky and require arcane knowledge. This will
> help those unfamiliar with the process to get started debugging GRUB
> with less effort.
>
> Signed-off-by: Glenn Washburn
Reviewed-by: Danie
Debugging GRUB can be tricky and require arcane knowledge. This will
help those unfamiliar with the process to get started debugging GRUB
with less effort.
Signed-off-by: Glenn Washburn
---
Changes from v1:
* Add gdbinfo section
---
Interdiff against v2:
diff --git a/docs/grub-dev.texi b/docs
w. I
will change it to "it has" as you suggested anyway because it can
prevent confusion.
Glenn
>
> On Fri, Jun 02, 2023 at 15:15:52 -0500, Glenn Washburn wrote:
> > Debugging GRUB can be tricky and require arcane knowledge. This will
> > help those unfamiliar with
This looks useful, thanks!
Some minor things I found when (quickly) reading through it:
On Fri, Jun 02, 2023 at 15:15:52 -0500, Glenn Washburn wrote:
> Debugging GRUB can be tricky and require arcane knowledge. This will
> help those unfamiliar with the process to get started debuggin
Debugging GRUB can be tricky and require arcane knowledge. This will
help those unfamiliar with the process to get started debugging GRUB
with less effort.
Signed-off-by: Glenn Washburn
---
Range-diff against v1:
1: 24680ea61004 ! 1: e602b68f4ee8 docs: Add debugging chapter to development
Signed-off-by: Renaud Métrich
---
grub-core/net/dns.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/grub-core/net/dns.c b/grub-core/net/dns.c
index f28d1099f..6993a4aba 100644
--- a/grub-core/net/dns.c
+++ b/grub-core/net/dns.c
@@ -355,6 +355,7 @@ recv_hook (grub_net_udp_socket_t sock
Debugging GRUB can be tricky and require arcane knowledge. This will
help those unfamiliar with the process to get started debugging GRUB
with less effort.
Signed-off-by: Glenn Washburn
---
docs/grub-dev.texi | 217 +
1 file changed, 217 insertions
On 3/16/23 21:05, Robbie Harwood wrote:
Glenn Washburn writes:
On 3/9/23 23:00, Robbie Harwood wrote:
Glenn Washburn writes:
If the configure option --enable-efi-debug is given, then enable the
printing early in EFI startup of the command needed to load symbols for
the GRUB EFI kernel. Thi
Glenn Washburn writes:
> On 3/9/23 23:00, Robbie Harwood wrote:
>> Glenn Washburn writes:
>>
>>> If the configure option --enable-efi-debug is given, then enable the
>>> printing early in EFI startup of the command needed to load symbols for
>>> the GRUB EFI kernel. This is needed because EFI f
On Wed, Mar 15, 2023 at 03:11:05AM +, Glenn Washburn wrote:
> On 3/13/23 12:27, Daniel Kiper wrote:
> > On Fri, Mar 10, 2023 at 03:27:13PM -0500, Peter Jones wrote:
> > > On Thu, Mar 09, 2023 at 06:00:04PM -0500, Robbie Harwood wrote:
> > > > Glenn Washburn writes:
> > > > > 2. Why should th
On 3/13/23 12:27, Daniel Kiper wrote:
On Fri, Mar 10, 2023 at 03:27:13PM -0500, Peter Jones wrote:
On Thu, Mar 09, 2023 at 06:00:04PM -0500, Robbie Harwood wrote:
Glenn Washburn writes:
2. Why should the load command not be printed when secure boot is enabled?
* This was also requested
On 3/9/23 23:00, Robbie Harwood wrote:
Glenn Washburn writes:
If the configure option --enable-efi-debug is given, then enable the
printing early in EFI startup of the command needed to load symbols for
the GRUB EFI kernel. This is needed because EFI firmware determines where
to load the GRUB
On Fri, Mar 10, 2023 at 03:27:13PM -0500, Peter Jones wrote:
> On Thu, Mar 09, 2023 at 06:00:04PM -0500, Robbie Harwood wrote:
> > Glenn Washburn writes:
> > > 2. Why should the load command not be printed when secure boot is
> > > enabled?
> > >* This was also requested by Daniel, I assume
On Thu, Mar 09, 2023 at 06:00:04PM -0500, Robbie Harwood wrote:
> Glenn Washburn writes:
> > 2. Why should the load command not be printed when secure boot is enabled?
> >* This was also requested by Daniel, I assume because of infomation
> > leakage
> > that may be a security concern.
Glenn Washburn writes:
> If the configure option --enable-efi-debug is given, then enable the
> printing early in EFI startup of the command needed to load symbols for
> the GRUB EFI kernel. This is needed because EFI firmware determines where
> to load the GRUB EFI at runtime, and so the relevan
t. How does this
> affect things for you?
>
> > > This is not printed when secure boot is enabled.
> >
> > This will mean that any debugging first requires disabling secureboot.
> > That's potentially annoying and I'm not sure I see a security benefit
> >
onfigure.ac
index 93626b7982d4..4bf477b0729a 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1521,6 +1521,17 @@ else
fi
AC_SUBST([MM_DEBUG])
+# EFI debugging.
+AC_ARG_ENABLE([efi-debug],
+ AS_HELP_STRING([--enable-efi-debug],
+ [include aides for debuggin
odule configurable, it should always be enabled (which it
isn't currently).
Also, Daniel was concerned about this breaking silent boot. How does this
affect things for you?
> > This is not printed when secure boot is enabled.
>
> This will mean that any debugging first requires disab
will mean that any debugging first requires disabling secureboot.
That's potentially annoying and I'm not sure I see a security benefit to
doing so.
Be well,
--Robbie
signature.asc
Description: PGP signature
___
Grub-devel mailing l
/
#define DISK_CACHE_STATS @DISK_CACHE_STATS@
#define BOOT_TIME_STATS @BOOT_TIME_STATS@
diff --git a/configure.ac b/configure.ac
index 93626b7982..4bf477b072 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1521,6 +1521,17 @@ else
fi
AC_SUBST([MM_DEBUG])
+# EFI debugging.
+AC_ARG_ENABLE(
Debugging GRUB can be tricky and require arcane knowledge. This will
help those unfamiliar with the process to get started debugging GRUB
with less effort.
Signed-off-by: Glenn Washburn
---
docs/grub-dev.texi | 233 +
1 file changed, 233 insertions
/
#define DISK_CACHE_STATS @DISK_CACHE_STATS@
#define BOOT_TIME_STATS @BOOT_TIME_STATS@
diff --git a/configure.ac b/configure.ac
index 93626b7982..4bf477b072 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1521,6 +1521,17 @@ else
fi
AC_SUBST([MM_DEBUG])
+# EFI debugging.
+AC_ARG_ENABLE(
Debugging GRUB can be tricky and require arcane knowledge. This will
help those unfamiliar with the process to get started debugging GRUB
with less effort.
Signed-off-by: Glenn Washburn
---
docs/grub-dev.texi | 233 +
1 file changed, 233 insertions
* Contributing Changes::
> > * Setting up and running test suite::
> > * Updating External Code::
> > +* Debugging::
> > * Porting::
> > * Error Handling::
> > * Stack and heap size::
> > @@ -595,6 +596,196 @@ cp minilzo-2.10/*.[hc] grub-core/lib/minilzo
> index f76fc658bf..8171e91c33 100644
> --- a/docs/grub-dev.texi
> +++ b/docs/grub-dev.texi
> @@ -79,6 +79,7 @@ This edition documents version @value{VERSION}.
> * Contributing Changes::
> * Setting up and running test suite::
> * Updating External Code::
> +* Debugging::
> * P
x f76fc658bf..8171e91c33 100644
> --- a/docs/grub-dev.texi
> +++ b/docs/grub-dev.texi
> @@ -79,6 +79,7 @@ This edition documents version @value{VERSION}.
> * Contributing Changes::
> * Setting up and running test suite::
> * Updating External Code::
> +* Debugging::
> * Por
@@ This edition documents version @value{VERSION}.
* Contributing Changes::
* Setting up and running test suite::
* Updating External Code::
+* Debugging::
* Porting::
* Error Handling::
* Stack and heap size::
@@ -595,6 +596,196 @@ cp minilzo-2.10/*.[hc] grub-core/lib/minilzo
rm -r minilzo
@@ This edition documents version @value{VERSION}.
* Contributing Changes::
* Setting up and running test suite::
* Updating External Code::
+* Debugging::
* Porting::
* Error Handling::
* Stack and heap size::
@@ -595,6 +596,196 @@ cp minilzo-2.10/*.[hc] grub-core/lib/minilzo
rm -r minilzo
@@ This edition documents version @value{VERSION}.
* Contributing Changes::
* Setting up and running test suite::
* Updating External Code::
+* Debugging::
* Porting::
* Error Handling::
* Stack and heap size::
@@ -595,6 +596,196 @@ cp minilzo-2.10/*.[hc] grub-core/lib/minilzo
rm -r minilzo-2.10
The first patch supercedes a patch sent earlier of the same subject. I've
removed the #undef if --mm-debug is not passwed to configure. The idea is
that even if --mm-debug is not passed to configure, the user should still
be able to enable memory debugging by passing -DMM_DEBUG in CFLAGS.
This is also handy for debugging.
Signed-off-by: Daniel Axtens
---
grub-core/kern/ieee1275/init.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/grub-core/kern/ieee1275/init.c b/grub-core/kern/ieee1275/init.c
index 0fb7bae280df..f70cb134178b 100644
--- a/grub
On Mon, Mar 09, 2020 at 01:22:34PM +0100, Patrick Steinhardt wrote:
> On Mon, Mar 09, 2020 at 12:18:41PM +0100, Paul Menzel wrote:
> > Dear Patrick,
> >
> > On 2020-03-07 17:29, Patrick Steinhardt wrote:
> > > The memory management system supports a debug mode that can be enabled
> > > at build tim
On Mon, Mar 09, 2020 at 12:18:41PM +0100, Paul Menzel wrote:
> Dear Patrick,
>
>
> On 2020-03-07 17:29, Patrick Steinhardt wrote:
> > The memory management system supports a debug mode that can be enabled
> > at build time by passing "--enable-mm-debug" to the configure script.
> > Passing the op
On Mon, Mar 09, 2020 at 01:01:51PM +0100, Patrick Steinhardt wrote:
> On Mon, Mar 09, 2020 at 12:19:15PM +0100, Daniel Kiper wrote:
> > On Sat, Mar 07, 2020 at 05:29:09PM +0100, Patrick Steinhardt wrote:
> > > When building GRUB with memory management debugging enabled, then the
On Mon, Mar 09, 2020 at 12:19:15PM +0100, Daniel Kiper wrote:
> On Sat, Mar 07, 2020 at 05:29:09PM +0100, Patrick Steinhardt wrote:
> > When building GRUB with memory management debugging enabled, then the
> > build fails because of `grub_debug_malloc()` and `grub_debug_free()`
>
k, similar to how other defines work.
>
> Signed-off-by: Patrick Steinhardt
> ---
> configure.ac | 8 +---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index f19489418..9eeec2d76 100644
> --- a/configure.ac
> ++
On Sat, Mar 07, 2020 at 05:29:09PM +0100, Patrick Steinhardt wrote:
> When building GRUB with memory management debugging enabled, then the
> build fails because of `grub_debug_malloc()` and `grub_debug_free()`
> being undefined in the luks2 module. The cause is that we patch
> &
On Sat, Mar 07, 2020 at 05:29:08PM +0100, Patrick Steinhardt wrote:
> The memory management system supports a debug mode that can be enabled
> at build time by passing "--enable-mm-debug" to the configure script.
> Passing the option will cause us define MM_DEBUG as expected, but in
> fact the reve
eletions(-)
diff --git a/configure.ac b/configure.ac
index f19489418..9eeec2d76 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1448,9 +1448,11 @@ LIBS="$tmp_LIBS"
# Memory manager debugging.
AC_ARG_ENABLE([mm-debug],
AS_HELP_STRING([--enable-mm-debug],
-
isabling memory debugging enables memory
debugging while it would've been disabled if just passing no
option at all.
These patches fix both issues so that GRUB now builds correctly with and
without memory debugging on my system.
Patrick
Patrick Steinhardt (2):
build: Fix option t
When building GRUB with memory management debugging enabled, then the
build fails because of `grub_debug_malloc()` and `grub_debug_free()`
being undefined in the luks2 module. The cause is that we patch
"base64.h" to unconditionaly include "config-util.h", which shouldn'
29.11.2016 17:38, Stanislav Kholmanskikh пишет:
>
>
> On 11/29/2016 05:17 PM, Andrei Borzenkov wrote:
>> On Tue, Nov 29, 2016 at 4:52 PM, Stanislav Kholmanskikh
>> wrote:
>>> Hi!
>>>
>>> Does anybody use MM debugging? If so, what is the recommend
On 11/29/2016 05:17 PM, Andrei Borzenkov wrote:
> On Tue, Nov 29, 2016 at 4:52 PM, Stanislav Kholmanskikh
> wrote:
>> Hi!
>>
>> Does anybody use MM debugging? If so, what is the recommended/working
>> way of enabling it?
>>
>> These steps do not work:
On Tue, Nov 29, 2016 at 4:52 PM, Stanislav Kholmanskikh
wrote:
> Hi!
>
> Does anybody use MM debugging? If so, what is the recommended/working
> way of enabling it?
>
> These steps do not work:
>
> 1. Run ./configure with '--enable-mm-debug'. It reports:
>
>
Hi!
Does anybody use MM debugging? If so, what is the recommended/working
way of enabling it?
These steps do not work:
1. Run ./configure with '--enable-mm-debug'. It reports:
With memory debugging: Yes
2. Then build and install the binaries, and install the boot loader
3
Howdy --
I'm trying to track down an issue encountered wherein a grub.cfg on a
memdisk is only successfully loaded with check_signatures=no, despite
grub_pubkey_open containing code which appears to explicitly exempt the
case where io->device->disk->id == GRUB_DISK_DEVICE_MEMDISK_ID from
enforceme
Hi,
it seems there are some problems in USB serial driver PL2303 and I want
to debug it.
I need to send and receive some data to see what happened, i.e. I need
to enable remote debug via classic serial interface by e.g.
"serial;terminal_output console serial;debug=xxx" and then do something
like
thank you.
but what i need also is the gdb stub to debug over serial. do you know where
i could find the right one to apply onlatest svn?
thx
-jf
On Fri, Jun 19, 2009 at 10:41 AM, wangji wrote:
> I have put the L Kundrak 's patches for grub2-gdb adjusted to svn
> revision -due to genmk.rb chang
I have put the L Kundrak 's patches for grub2-gdb adjusted to svn
revision -due to genmk.rb changes. It works well with qemu -s , for
stepping into modules ...hello !
http://wjhowto.googlepages.com/grub2-r2300-2340-elfgdb.patch
older svn are there too
http://wjhowto.googlepages.com/grub2-r1742-2
hi
i need to add a few commands/modules to grub2 for our systems.
i am trying to debug grub2 with gdb to ease the development cycle. for that
purpose i have followed this excellent doc
http://v3.sk/~lkundrak/grub2-gdb/howto.html
after i applied the procedure described in the note, for some reason
breakpoint if it haunts you
del 1
; where 1 is being breakpoint number use 'info break' to see numbers if
you lost that.
11. Setup automatic symbol loading
break_load
12. Happy debugging!
If you want to debug boot code that can be done also... but its a bit
more tricky... and I leave that
Hi All,
I was debugging some problem lately and felt that I need to use
debugger. As I like how JTAG debugging works I wanted to have similar
feeling :). Obivious choice is to use QEMU.
QEMU provides a GDB stub that can be used to debug code running on its
virtual session. I also found out that
Hello all,
In follow-up to my last post. I have been talking with daChaac in the IRC
channel. (Thanks daChaac again for all you help!!)
With debug on, the system hangs initing the module. I originally had this with
the "apple" module, but I rebuilt the efi image without the "apple" module and
Hello all,
I am attempting to boot an xserve with the EFI build of grub2.
I can get success on my macbook with the build, but the xserve hangs at
"Welcome to Grub!"
I would like to help debug this to get it going. Anyone?
Thanks! -Cheers, Peter
_
On Tue, 2008-05-06 at 17:10 +0200, Robert Millan wrote:
> On Tue, May 06, 2008 at 01:10:17PM +0200, Lubomir Rintel wrote:
> > +# GRUB -- GRand Unified Bootloader
> > +# Copyright (C) 2003,2004,2005,2006,2007,2008 Free Software Foundation,
> > Inc.
>
> Where does this code originate? I don't r
On Tue, 2008-05-06 at 17:02 +0200, Robert Millan wrote:
> On Thu, May 01, 2008 at 03:12:25PM +0200, Lubomir Rintel wrote:
> > --- grub2/gdb/cstub.c 1970-01-01 01:00:00.0 +0100
> > +++ grub2-gdb/gdb/cstub.c 2008-05-01 10:57:57.0 +0200
> > @@ -0,0 +1,362 @@
> > +/* cstub.c - m
Robert Millan wrote:
/* The size of the first region which won't be compressed. */
-#define GRUB_KERNEL_MACHINE_RAW_SIZE 0x4A0
+#define GRUB_KERNEL_MACHINE_RAW_SIZE 0x4BC
What caused this? Any way we can have this dynamically calculated?
More code before compression
On Tue, May 06, 2008 at 01:10:17PM +0200, Lubomir Rintel wrote:
> +# GRUB -- GRand Unified Bootloader
> +# Copyright (C) 2003,2004,2005,2006,2007,2008 Free Software Foundation, Inc.
Where does this code originate? I don't recall seeing any perl in GRUB
before. GDB maybe?
--
Robert Millan
On Thu, May 01, 2008 at 03:12:25PM +0200, Lubomir Rintel wrote:
> --- grub2/gdb/cstub.c 1970-01-01 01:00:00.0 +0100
> +++ grub2-gdb/gdb/cstub.c 2008-05-01 10:57:57.0 +0200
> @@ -0,0 +1,362 @@
> +/* cstub.c - machine independent portion of remote GDB stub */
> +/*
> + * Copyrigh
09:18:25.380014078 +0200
+++ grub.gdb 2008-05-06 12:51:33.0 +0200
@@ -0,0 +1,109 @@
+# grub.gdb - Macros to ease debugging of GRUB and its modules with GDB
+
+# GRUB -- GRand Unified Bootloader
+# Copyright (C) 2003,2004,2005,2006,2007,2008 Free Software Foundation, Inc.
+#
+# GRUB is free
Re-sending the GDB stub patch. The GDB protocol part, though being
largely rewritten, originates from GDB source tarball, which refers to
it as a Public Domain code.
Applies against today's CVS.
Is not much of use without debugging symbols, part 2 of patch [1]
preserves those. Neither is
Bean confirmed it works. Committed without changing jmp to call, since it
wasn't clear whether we want it or not.
On Fri, Apr 18, 2008 at 01:32:59PM +0200, Robert Millan wrote:
> On Thu, Apr 17, 2008 at 10:21:14PM -0400, Pavel Roskin wrote:
> > Quoting Robert Millan <[EMAIL PROTECTED]>:
> >
> >
On Fri, Apr 18, 2008 at 11:38:48PM +0800, Bean wrote:
> >
> > "exit" in open firmware based systems would probably mean returning
> > control to open firmware.
> >
> > By the way, it would be nice to have "exit" in both grub for PC and
> > grub-emu, and not only in the rescue mode. "exit" on P
On Fri, Apr 18, 2008 at 11:16 PM, Pavel Roskin <[EMAIL PROTECTED]> wrote:
>
> On Fri, 2008-04-18 at 14:13 +0200, Robert Millan wrote:
>
> > On Fri, Apr 18, 2008 at 01:32:59PM +0200, Robert Millan wrote:
> > > - jmp EXT_C(cmain)
> > > + jmp EXT_C(grub_main)
> >
> > Or maybe that should be a
On Fri, Apr 18, 2008 at 11:16:43AM -0400, Pavel Roskin wrote:
>
> On Fri, 2008-04-18 at 14:13 +0200, Robert Millan wrote:
> > On Fri, Apr 18, 2008 at 01:32:59PM +0200, Robert Millan wrote:
> > > - jmp EXT_C(cmain)
> > > + jmp EXT_C(grub_main)
> >
> > Or maybe that should be a "call" instead..
>
On Fri, 2008-04-18 at 14:13 +0200, Robert Millan wrote:
> On Fri, Apr 18, 2008 at 01:32:59PM +0200, Robert Millan wrote:
> > - jmp EXT_C(cmain)
> > + jmp EXT_C(grub_main)
>
> Or maybe that should be a "call" instead..
Only if there is any chance of return, and we can handle it.
"exit" in op
On Fri, 2008-04-18 at 13:32 +0200, Robert Millan wrote:
> On Thu, Apr 17, 2008 at 10:21:14PM -0400, Pavel Roskin wrote:
> > Quoting Robert Millan <[EMAIL PROTECTED]>:
> >
> > >Now that I think of it, is there any reason for doing all the cmain()
> > >cruft before grub_main() ? Getting to grub_ma
On Fri, Apr 18, 2008 at 01:32:59PM +0200, Robert Millan wrote:
> - jmp EXT_C(cmain)
> + jmp EXT_C(grub_main)
Or maybe that should be a "call" instead..
--
Robert Millan
I know my rights; I want my phone call!
What use is a phone call… if you are unable to speak?
(as seen on /.)
On Thu, Apr 17, 2008 at 10:21:14PM -0400, Pavel Roskin wrote:
> Quoting Robert Millan <[EMAIL PROTECTED]>:
>
> >Now that I think of it, is there any reason for doing all the cmain()
> >cruft before grub_main() ? Getting to grub_main() only requires a working
> >stack, which we have, and grub_main
Quoting Robert Millan <[EMAIL PROTECTED]>:
Now that I think of it, is there any reason for doing all the cmain()
cruft before grub_main() ? Getting to grub_main() only requires a working
stack, which we have, and grub_main() inmediately returns control back to
architecture-specific code in grub
On Thu, Apr 17, 2008 at 01:53:21PM +0200, Lubomir Kundrak wrote:
>
> On Tue, 2008-04-15 at 15:38 +0200, Robert Millan wrote:
> > On Tue, Apr 15, 2008 at 12:30:40AM +0200, Lubomir Kundrak wrote:
> > > diff -rup grub-1.95.orig/kern/main.c grub-1.95/kern/main.c
> > > --- grub-1.95.orig/kern/main.c
On Tue, 2008-04-15 at 15:01 -0400, Pavel Roskin wrote:
> On Tue, 2008-04-15 at 00:30 +0200, Lubomir Kundrak wrote:
> > These are pretty self-explainable. I think I tried to sumbit these
> > changes with the serial debugging patch year and some months ago and I
> > was told
On Tue, 2008-04-15 at 15:38 +0200, Robert Millan wrote:
> On Tue, Apr 15, 2008 at 12:30:40AM +0200, Lubomir Kundrak wrote:
> > diff -rup grub-1.95.orig/kern/main.c grub-1.95/kern/main.c
> > --- grub-1.95.orig/kern/main.c 2007-01-29 15:31:36.0 +0100
> > +++ grub-1.95/kern/main.c 2007
1 - 100 of 130 matches
Mail list logo
