Re: Silent GRUB Menu
On -1 xxx -1, [EMAIL PROTECTED] wrote: How can I make GRUB not to display the Menu? This is to avoid the users not to play around with GRUB options/configuration. I think that if you set the delay to 0 it will not show anything at all. (Maybe now 0 will cause this feature to be disabled) Mark Lundeberg [EMAIL PROTECTED] http://www.pgfn.bc.ca/~aa026/
Re: Installation documentation
On Thu, 23 Sep 1999, OKUJI Yoshinori wrote: I have already suggested the same idea in this list, but some persons told me that using Stage 1.5 would be enough. And, I agreed with them. So, I'd like to say to you, just like they said to me, "Why do you want to change the mechanism, though you can use Stage 1.5 and that's enough for you?" Yes, but wouldn't it be nice to have LBA support and other devices to be supported all integrated into a single stage1? Only keeping track of 1 block would free up (comparatively) a lot of space for code.
Re: stage1_lba trouble
On Wed, 11 Aug 1999, OKUJI Yoshinori wrote: Really? LBA should allow to access 2TB. My manual says there is a 1024 cyl max. Not 65536, which you must be thinking of. My bios is from around 1995 (I think). It is an Award Software bios. I wouldn't be suprised if it's the bios' fault. I'll try to put some extra code in stage1_lba so I can find out which part it fails at. (It fails with carry set on the first LBA probe) I can imagine three possible causes. The first is a bug in GRUB. The second is a bug in your BIOS. The third is just because your drive does not support LBA. I think the third is plausible, since old and relatively small hard disk drives don't support LBA normally, and some hard disk drives have jumpers for switching the access mode. To me, 2.5 G isn't relatively small. Maybe my drive really doesn't support it. Maybe my manual is talking about something that doesn't apply here. Is there any way I can check that normal stage1 can access all of my drive, so I don't have to bother with all this trouble?
Re: stage1_lba trouble
On Wed, 11 Aug 1999, OKUJI Yoshinori wrote: You misunderstood something. LBA does not use CHS information but uses linear addresses. So GRUB does not depend on what number of cylinders is reported. In LBA mode, CHS information is used just for compatibility with some OSes, such as DOS. Ah. I'm starting to get all this now. I thought it was a real bug or something. Look at the output from the command "geometry". In CHS mode, the limitation can be calculated easily by this: (the number of cylinders) * (the number of heads) * (the number of sectors) * 512 bytes It looks like it can access all of the drive. I assume that this applies to reading and writing calls as well?
Re: stage1_lba trouble
On Tue, 10 Aug 1999, OKUJI Yoshinori wrote: The real problem is not to detect LBA. Have you turned on LBA mode for your drive really? Absolutely sure. I have 2 drives, my old 210 Mb on hd0, and a 2.5 G on hd1. My bios gives me 3 choices for access: Normal, large, and LBA. hd0 is normal, and hd1 is LBA. Large mode is some weird hack to normal mode that allows for 1 Gb access (by allowing 32 heads). The manual mentions a 528 Mb limit for normal mode, and of course 8.4 G for LBA. That is not correct. Modern BIOSes allow heads up to 255. This method is called "logical geometry" and "Large mode". The name "logical geometry" is incorrect, because C/H/S is "logical" anyway, though. So recent BIOSes should be able to access 8GB regions, perhaps your BIOS can do. My bios is from around 1995 (I think). It is an Award Software bios. I wouldn't be suprised if it's the bios' fault. I'll try to put some extra code in stage1_lba so I can find out which part it fails at.
stage1_lba trouble
Sorry to bother you again, but I am having more problems with grub. I am getting the error "LBA error" from stage1_lba when it is booted from my LBA drive. I used root= (hd1,0) install= /boot/grub/stage1_lba (hd1) /boot/grub/stage2 0x8000 p from the shell to install. From stage1_lba.S I can clearly see that the error that I got refers to a failed LBA probe. However, hd1 is set up as LBA. It is a 2.4Gb hard drive. Linux and stage2 read the drive ok, but I'm not sure if stage2 uses LBA. I've looked through the docs, but I can't find any solution in them. PS: try color= 0x1e 0x70 kinda reminds me of the borland IDEs :) Off-topic somewhat: Also, does anyone know what the byte at 0x80:0x87 does? I fiddle with it with assembly at the beginning of stage1 and it gives me color (my video card is confused). Don't ask where I found this :) -- it's a long story. Linux gives me color anyways without it, though. I just use it so my nice colored menu is actually colored. :)
Re: stage1_lba trouble
On Mon, 9 Aug 1999, OKUJI Yoshinori wrote: Could you check out the current version from the CVS? The current version has "geometry" command, and it shows the information about the geometry of a drive that you specify. Try to run a command like this: geometry= (hd0) Actually, geometry= (hd1) :) I used the patch from the list archives, actually, but I got a fuzz factor of 1 (it works anyways). from shell: drive 0x81: C/H/S = 621/128/63, The number of sectors = 5007744, LBA from native: drive 0x81: C/H/S = 620/128/63, The number of sectors = 4999680, CHS Ugh. CHS access, and 1 less cyl. My drive is only 23% full, though. My bios setup says the same as the shell, but it says landz=4969, also (whatever that is). Linux definetly treats it as LBA, because I wrote a 100Mb file and it brought me way past the 528Mb limit of CHS. But, AFAIK, CHS only allows heads to get up to 16. Maybe this could be used as a check of whether to use LBA or not. Maybe we should check the Linux source to see how they detect LBA.
Re: GRUB 0.5.92 problem
On Sun, 8 Aug 1999, OKUJI Yoshinori wrote:
From: Mark Lundeberg [EMAIL PROTECTED]
Subject: Re: GRUB 0.5.92 problem
Date: Sat, 7 Aug 1999 18:34:52 -0700 (PDT)
am having trouble with getting grub to use passwords. I type in the
correct password, but it gives me a "Failed!" message. I tried running the
simulator under gdb, and the password variable is correctly set to
"my password (hd0,1)/boot/grub/menup.lst"
Thanks for your report. Can you try this patch?
--- grub-0.5.92.orig/stage2/stage2.c Thu Jun 24 09:03:29 1999
+++ grub-0.5.92/stage2/stage2.c Sun Aug 8 12:37:09 1999
@@ -377,6 +377,10 @@
while (! isspace (*pptr))
pptr ++;
+
+ /* terminate PASSWORD. */
+ *pptr++ = 0;
+
if (! strcmp (password, entered))
{
char *new_file = config_file;
That works for the first try at the password, but I'd hate to see what
happens if the user failed the password check and tried again. AFAIK,
isspace() doesn't return 1 for null chars, so change
while (! isspace (*pptr))
to
while (! isspace (*pptr) *pptr)
Also, I am having trouble booting up other bootloaders off floppies from
grub (with chainloader command). I tried to boot up a grub boot disk from
the grub on my harddrive, and it gave me a Hard Disk Error when I typed in
boot. I tried to boot up my redhat install disk, and that didn't word
either. When I tried to boot up my master bootloader (lilo), from grub, it
worked fine, and lilo is able to boot these 2 floppies with no problems.
Your information is too ambiguous to understand what happened. We
need to know what you did exactly.
Sorry, stupid me forgot to do root=(fd0)
Re: GRUB 0.5.92 problem
On Sat, 7 Aug 1999, OKUJI Yoshinori wrote: Perhaps RedHat has an old and buggy version of binutils. You can examine what version you use by "ld -v". See the requirement in the file README. Ah. I thought my old version (2.9.1.0.4) was fine, as no compiler errors occured. It works nicely now that I have the new 2.9.1.0.25 . However, I am having trouble with getting grub to use passwords. I type in the correct password, but it gives me a "Failed!" message. I tried running the simulator under gdb, and the password variable is correctly set to "my password (hd0,1)/boot/grub/menup.lst" Also, I am having trouble booting up other bootloaders off floppies from grub (with chainloader command). I tried to boot up a grub boot disk from the grub on my harddrive, and it gave me a Hard Disk Error when I typed in boot. I tried to boot up my redhat install disk, and that didn't word either. When I tried to boot up my master bootloader (lilo), from grub, it worked fine, and lilo is able to boot these 2 floppies with no problems.
