in the net code when I boot a kernel).
Thanks,
Okuji
Derrik Pates | Sysadmin, Douglas School|_ #linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net) | | | and now OPN too!
Student @ South Dakota School of Mines | __| |___ _ _ _ ___ _ _
Technology
I have discovered that this was the issue with a system that I had
previously reported that GRUB would Oops the kernel on - this is the
reason. Using the --no-mem-option flag to the 'kernel' command at the
grub prompt causes this problem to go away.
Derrik Pates | Sysadmin, Douglas School
code as well, to compare.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug
.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
--- orig/grub-0.90/stage2/asm.S Tue Feb 27 05:59:00 2001
+++ grub-0.90/stage2/asm.S Thu Aug 2 00:25:42 2001
@@ -260,12 +260,19 @@
xorw%bx
to Oops on boot). It just checks the length of the memory
range in the check loop in common.c, and if it is zero bytes long, just
ignores the range.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
is worked around with a one-line fix.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman
it into CVS.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
, x86-only. A version for another
platform would have to be heavily rewritten, since large sections of Grub
are written in IA32 assembly.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
, to hopefully make it check for a 0-byte-long
usable range, and ignore it.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
___
Bug-grub mailing list
[EMAIL
'kernel
/kernel.elf'.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
On Thu, 9 Aug 2001, Frank Louwers wrote:
(hd0,0) /boot ext2
(hd0,1) / xfs
I recommend doing the following:
cd /boot
ln -s . boot
grub-install --root-directory=/boot /dev/hda1
See what happens then - it should probably work.
Derrik Pates | Sysadmin
what happens? That
completely bypasses any device-path parsing issues.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
___
Bug-grub mailing list
[EMAIL
.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
appreciate
that.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
(hd0) ar the grub
prompt. If you can see the disk, GRUB is working.
Well, I guess you could do that, if you hadn't returned it. I assume you
were using the grub shell? Or how were you installing GRUB to the disk?
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL
that start above 8.4 gig... can the latest version of
grub do this
GRUB uses the BIOS provided mechanisms for accessing disk devices. So, if
your BIOS can, it can - if your BIOS can't, well then, it can't.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED
in the right
place.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
-directory= flag at all. Only use that to specify the
root directory of the partition you're wishing to install GRUB to (like if
you had a separate /boot partition or something).
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net
card).
So, what other useful info can I provide? Does anyone know what's going
on? Is there maybe a newer driver in the netboot codebase? I'm open to
suggestions.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS
count, and
Windows talks directly to the BIOS during boot to get the memory total
(afaik). If it were Linux, *BSD, or a Mach-based kernel, then you could,
either by modifying GRUB's idea of the memory layout, or by just passing
an arg (like the Linux kernel's 'mem=' parameter).
Derrik Pates
/mbr'. That will regenerate a standard DOS MBR on your boot drive.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
___
Bug-grub mailing list
[EMAIL PROTECTED
On 5 Jan 2002, Adrian Phillips wrote:
I've got 0.90 (Debian); time to upgrade :-)
In his case, it shouldn't make a difference - only his root FS is Reiser,
the /boot is ext2 (according to the info he gave) - so Grub itself never
even touches that partition, only /boot.
Derrik Pates
before loading the OS,
but supposedly this issue is fixed in CVS. If that doesn't work for you,
then post again and make sure to mention that the CVS version still
doesn't work.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net
is going
to have to be able to see the kernel (and any files it has to chain-load)
in the first 1023 cylinders.
If you run 'geometry (hd0)' at the GRUB prompt, what do you get?
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net
, with the GRUB files
on a FAT-based partition, if you defrag that disk, GRUB may likely not
start anymore (due to the blocklists suddenly being invalid and all...),
so don't be surprised.
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net
. Can you please help me?
If there are any instances where you don't explicitly specify the root
device, and you have a custom-built kernel that hasn't been rebuilt since
the change, it'll try to boot from whatever the root device was when it
was built.
Derrik Pates | Sysadmin, Douglas School
On Wed, 30 Jan 2002, Richard M. Kreuter wrote:
Can GRUB read in automatically a menu.lst file on a fat formatted
partition?
It can, but you'll have to install it manually and specify the path to the
menu.lst file if you wish it to be somewhere besides \boot\grub.
Derrik Pates
(and eventually EHCI)
controller drivers, and an HID class driver in GRUB, which I think would
be an unnecessary pain in the ass.
In other words, it's not a bug, it's a Feature (TM).
--
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net
emulation for real mode (and maybe v86 mode). It would
explain why. Of course, if that's the case, I'm not sure there's a whole
lot that the GRUB guys can do about it.
--
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net
.
--
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
, will use that uncompressed image file, but x86 is NOT one of
those).
--
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN
___
Bug-grub mailing list
[EMAIL
in legacy keyboard emulation code
that only works in real mode, not protected mode. If LILO and the NT
boot manager both run in real mode, that would seem to confirm my
suspicion.
--
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net
to edit, press 'e' again, and make your changes.
Then once you've made the needed changes, press 'b' to boot (don't go
back to the root menu, your changes will be lost).
--
Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net
has started itself, I can then use a keyboard connected
via USB as usual. Anyone have any clues as to why this is? I think this
is the same problem as with other systems with USB keyboards, so maybe if
we can figure out why this is so, then it can be corrected on other
systems.
--
Derrik Pates
34 matches
Mail list logo