Re: Grub-1.97 problems
On 11/12/09, Bruce Dubbs bruce.du...@gmail.com wrote: Bruce Dubbs wrote: I just had an aha! Try rebuilding grub without the --disable-largefile switch. Your partition is 11G and that probably is causing it to fail. I don't know what the threshold is. I'll investigate. man 2 open O_LARGEFILE (LFS) Allow files whose sizes cannot be represented in an off_t (but can be represented in an off64_t) to be opened. ... AHA! r...@lfs:/# grub-install --grub-setup=/bin/true /dev/sda Installation finished. No error reported. This is the contents of the device map /boot/grub/device.map. Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script `grub-install'. (fd0) /dev/fd0 (hd0) /dev/sda (hd1) /dev/sdb In this case LFS stands for Large File Support. Doing some Googling, it looks like the limit is 2G without Large File Support. I've always used a standalone /boot partition of 100M or so and haven't run into this before. I used to use the standalone /boot, but I would get confused and have /boot/boot/grub. I started making a symlink at the root of the /boot partition like this: ln -s boot/grub grub Then I could always say /boot/grub ... mounted or not I kept building kernels, and /boot partition kept filling up, and eventually I switched to just using a /boot directory on the root /. Now I still make that symlink on the root / ln -s boot/grub grub so I can be really lazy and type /grub/menu.lst ... er, uh /grub/grub.cfg ... I'm going to reboot and try it now. Thanks! -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Grub-1.97 problems
On 11/12/09, Bruce Dubbs bruce.du...@gmail.com wrote:
Bruce Dubbs wrote:
I just had an aha!
Try rebuilding grub without the --disable-largefile switch.
That worked!
Now some more things.
.. I needed to suppress probing the ancient mobo ide drive that is not
connected to avoid a 2 minute wait for it not to find a drive
connected ...
cat /etc/default/grub
GRUB_CMDLINE_LINUX=ide_core.noprobe=0.0 ide_core.noprobe=0.1
... Grub2 ..hardcoded.. what your kernel basname must be like vmlinu[zx]...
ln -s lfskernel-2.6.31.4-noremap vmlinux-2.6.31.4-noremap
ls -l vmlinux-2.6.31.4-noremap
lrwxrwxrwx 1 root root 26 2009-11-12 09:34 vmlinux-2.6.31.4-noremap -
lfskernel-2.6.31.4-noremap
... Make a cfg
grub-mkconfig -o /boot/grub/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinux-2.6.31.4-noremap
done
cat /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry GNU/Linux, with Linux 2.6.31.4-noremap {
insmod ext2
set root=(hd0,11)
search --no-floppy --fs-uuid --set 6e97d350-d12d-49d9-954c-169e328ba062
linux /boot/vmlinux-2.6.31.4-noremap root=/dev/sda11 ro
ide_core.noprobe=0.0 ide_core.noprobe=0.1
}
menuentry GNU/Linux, with Linux 2.6.31.4-noremap (recovery mode) {
insmod ext2
set root=(hd0,11)
search --no-floppy --fs-uuid --set 6e97d350-d12d-49d9-954c-169e328ba062
linux /boot/vmlinux-2.6.31.4-noremap root=/dev/sda11 ro
single ide_core.noprobe=0.0 ide_core.noprobe=0.1
}
Now 2 questions:
1 - In the GNU GRUB version 1.97 screen, when you type 'help', how to
keep it from scrolling so that you cannot read it?
2 - When editing an entry in GNU GRUB version 1.97 screen (in emacs
like ..), can it use a different editing mode that has a cursor and
works like it did in grub-legacy?
I have had many occasions when I needed to edit an entry on-the-fly to
get things going.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: Grub-1.97 problems
On 11/11/09, Bruce Dubbs bruce.du...@gmail.com wrote: # grub-install --grub-setup=/bin/true /dev/sda11 This should be /dev/sda, but I see you tried that too. Now I really _want_ to install grub on individual partitions so that I can chainloader to different installations like grub-legacy has let me do for years. grub-install /dev/sdb8 grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea. grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged. grub-setup: error: If you really want blocklists, use --force. USE THE FORCE, LUKE ... grub-setup --force /dev/sdb8 grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea. grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged. It didn't ... It it didn't put grub on /dev/sdb8 ... the grub-legacy is still there GNU Grub 0.97 Plus, grub-legacy used to let you setup grub from the grub command line is you had booted from a floppy, or a cd, or some other way. I think that is a major function loss. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Grub-1.97 problems
linux fan wrote: On 11/11/09, Bruce Dubbsbruce.du...@gmail.com wrote: # grub-install --grub-setup=/bin/true /dev/sda11 This should be /dev/sda, but I see you tried that too. Now I really _want_ to install grub on individual partitions so that I can chainloader to different installations like grub-legacy has let me do for years. grub-install /dev/sdb8 grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea. grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged. grub-setup: error: If you really want blocklists, use --force. USE THE FORCE, LUKE ... grub-setup --force /dev/sdb8 grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea. grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged. It didn't ... It it didn't put grub on /dev/sdb8 ... the grub-legacy is still there GNU Grub 0.97 Plus, grub-legacy used to let you setup grub from the grub command line is you had booted from a floppy, or a cd, or some other way. I think that is a major function loss. I usually do grub-setup on the main partition /dev/sda then on the os partition /dev/sda* (still uncertain which it should be though). Justin P. Mattock -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Grub-1.97 problems
I usually put grub on the mbr, then use around 100mb /boot as kernels bed. From there it is possible to boot to any system/partition with any kernel. AFAICS, this seems to be the most popular way to do. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Grub-1.97 problems
linux fan wrote: On 11/11/09, Bruce Dubbs bruce.du...@gmail.com wrote: # grub-install --grub-setup=/bin/true /dev/sda11 This should be /dev/sda, but I see you tried that too. Now I really _want_ to install grub on individual partitions so that I can chainloader to different installations like grub-legacy has let me do for years. grub-install /dev/sdb8 grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea. grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged. grub-setup: error: If you really want blocklists, use --force. USE THE FORCE, LUKE ... grub-setup --force /dev/sdb8 grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea. grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged. It didn't ... It it didn't put grub on /dev/sdb8 ... the grub-legacy is still there GNU Grub 0.97 Plus, grub-legacy used to let you setup grub from the grub command line is you had booted from a floppy, or a cd, or some other way. I think that is a major function loss. The problem with GRUB Legacy is that it didn't support 64-bit systems -- at least it have to be built from a 32-bit system. This is a major drawback in that virtually every new Intel/AMD system is 64-bit capable. You might want to discuss options about how to do what you want with the GRUB developers: http://lists.gnu.org/mailman/listinfo/grub-devel but I believe they would like install/usage problems to first be discussed on IRC: irc.freenode.org#grub -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Grub-1.97 problems
On 11/12/09, Bruce Dubbs bruce.du...@gmail.com wrote: The problem with GRUB Legacy is that it didn't support 64-bit systems -- at least it have to be built from a 32-bit system. This is a major drawback in that virtually every new Intel/AMD system is 64-bit capable. Ok, maybe I just keep this in my back pocket: URL=ftp://alpha.gnu.org/gnu/grub/grub-0.97.tar.gz; patch -Np1 -i ../grub-0.97-disk_geometry-1.patch patch -Np1 -i ../grub-0.97-256byte_inode-1.patch ./configure --prefix=/opt/grub1 make make install and be so.. careful.. to be the 'grub-install' I want at the time. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
