All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Becker <scottb@bxwa.com>
To: grub-devel@gnu.org
Subject: Debugging
Date: Fri, 13 May 2005 17:05:23 -0700	[thread overview]
Message-ID: <428540C3.8090408@bxwa.com> (raw)

On the two servers I've installed RHEL 4 on, I've had trouble with grub. 
It's the combination of grub and the new I2O_block driver. I suspect the 
grub patch to support I2O is lacking.

I was wondering if Grub 0.95 or 2.0 has a facility to trace the changes 
being made when grub-install is being ran. After an install or an update 
I had to run grub-install to get it to boot again. In theory, this 
shouldn't be neccessary. Since it was, I thought it would be useful to 
be able to compare the areas of the disk written to during grub-install 
with what was written there before so that I could trace down the problem.

    thanks
    scottb




             reply	other threads:[~2005-05-14  0:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-14  0:05 Scott Becker [this message]
2005-05-17  2:11 ` Debugging Hollis Blanchard
2005-05-18 15:59   ` Debugging Scott Becker
2005-08-29 15:12     ` Debugging pjones
  -- strict thread matches above, loose matches on Subject: below --
2006-01-29  6:21 Debugging James Colannino
2006-01-29 16:21 ` Debugging Steve Graegert
2006-01-29 18:14 ` Debugging Glynn Clements
2006-01-30 19:09   ` Debugging James Colannino
     [not found] ` <20060129105131.6813f695.leslie.polzer@gmx.net>
2006-01-30 19:13   ` Debugging James Colannino
2006-01-30 19:21     ` Debugging James Colannino
2005-09-09 12:40 Debugging Lares Moreau
2005-09-09 15:30 ` Debugging Randy.Dunlap
     [not found] <09B04A55822EFF4DA48D2E0BB2941D4A15C51F@wardrive.citadelcomputer.com.au>
2003-10-19 23:26 ` Debugging techmail
2003-10-19 22:45 Debugging Daniel Chemko
2003-10-19 22:24 Debugging techmail
2003-10-09  7:23 debugging Ingo Flaschberger
2003-03-11 11:05 bug in asm-ppc/div64.h Bastien Nocera
2003-03-11 14:21 ` Debugging Giuliano Pochini
2003-03-11 19:28   ` Debugging Olaf Hering
2003-03-13  8:28     ` Debugging Giuliano Pochini
2003-03-13  8:52       ` Debugging Olaf Hering

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=428540C3.8090408@bxwa.com \
    --to=scottb@bxwa.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.