On Wed, Oct 02, 2002 at 07:52:13AM +1000, Jason Thomas wrote:
if this is almost the same as 'e' than why all the duplication?
It isn't. To change the kernel command line using 'e':
highlight the boot entry you want to change. press 'e'
arrow down to the kernel line, press 'e'
add what you
What brand BIOS do you have? What I've done to debug stage1 and
stage2 is to add simple 1 char output around places I think things are
going wrong. Of course having an In-target probe or in-circuit
emulator helps debug these things much easier.
Cheers,
Matt
On Mon, Sep 17, 2001 at
Even so, I've run into several problems with AMI BIOS. What SCSI card
do you have?
Most likely what's happening is that the stack is becoming corrupted
and when you return from an interrupt call you're jumping to a point
other than where you called the INT 13 from.
Cheers,
Matt
On Mon, Sep
On Sun, Sep 02, 2001 at 02:33:03PM +1000, Jason Thomas wrote:
so this is only needed on older kernels? and isn't this already
configurable using ./configure, my main concern was how many systems
will I break if I change it in the debian package?
Oh, right. Use --disable-auto-linux-mem-opt
On Sat, Sep 01, 2001 at 10:40:45PM -0600, Derrik Pates wrote:
Why is it hurting anything? I was having a problem with Grub getting a
0-length mem range at 4 GB passed from the BIOS, but I have submitted a
patch to the maintainers (now in CVS) to prevent that situation. It's
probably not the
:10PM -0400, Matt Wilson wrote:
Marc, I can confirm that another machine with an AMI BIOS core is
having exactly the same problem you're having. Placing GRUB totally
on a floppy works; you can boot GRUB on the floppy, access the disks
including the stage1.5 image that fails to load when start.S
Marc, I can confirm that another machine with an AMI BIOS core is
having exactly the same problem you're having. Placing GRUB totally
on a floppy works; you can boot GRUB on the floppy, access the disks
including the stage1.5 image that fails to load when start.S tries to
load it when booting
