Hi,
I had a peek at the ML lately and saw a few messages reporting some
success in using GRUB2 as a bootloader in a root-on-lvm setup.
I decided to give it a try, so I grabbed it from CVS, but unfortunately
it didn't work, just as in my previous tries :(
I can't get why but grub-setup insists on
Le samedi 12 janvier 2008 à 16:12 +0100, Robert Millan a écrit :
> Try latest CVS.
Done, but no success.
> You'll still have to add "pc" (or "gpt") module manually (--modules
> parameter).
These modules are for grub itself, right ? My problems seem to be
caused by the installer. I can boot my
Le dimanche 13 janvier 2008 à 00:26 +0100, Robert Millan a écrit :
> Try re-running grub-setup with verbose flag on, and see what it prints.
orion:/test/grub2# /usr/local/sbin/grub-setup --verbose '(hd1)'
grub-setup: info: prefix = /grub
grub-setup: info: changing current directory to /dev/mapper
Le dimanche 13 janvier 2008 à 11:57 +0100, Robert Millan a écrit :
> LVM doesn't reserve any space at the beginning of its partitions? Most
> filesystems do.
I created a new empty volume group with an empty disk to do some
testing. The lvm label identifying physical disks can be put in
sector 0
Le dimanche 13 janvier 2008 à 14:52 +0100, Robert Millan a écrit :
> What happens if you comment out the "must_embed = 1" line?
orion:/test/grub2# /usr/local/sbin/grub-setup --verbose '(hd1)'
grub-setup: info: prefix = /grub
grub-setup: info: changing current directory to /dev/mapper
grub-setup:
Le dimanche 13 janvier 2008 à 21:09 +0100, Jean-Christophe Haessig a
écrit :
> Le dimanche 13 janvier 2008 à 14:52 +0100, Robert Millan a écrit :
>
> > What happens if you comment out the "must_embed = 1" line?
>
> orion:/test/grub2# /usr/local/sbin/grub-setup --verb
Hello,
I'm still trying to build and use the latest GRUB cvs version when there
seems to be some movement in the LVM field. There was a thread in the ML
three weeks ago and I tried it again, but I still get the same errors as
I got, back in January.
The system can be booted with a floppy where th
Le lundi 07 juillet 2008 à 13:46 -0400, Pavel Roskin a écrit :
> If the first partition starts on cylinder 0 (which is the most common),
> it starts on head 1. All space on head 0, cylinder 0 is available. The
> maximal number on sectors per track is 63, and that's what is normally
> used (old d
Le mardi 08 juillet 2008 à 07:32 +0200, Yoshinori K. Okuji a écrit :
In fact, you want to write a GRUB module which deciphers a partition
when given a key. That's no DRM in any way. In the DRM world, users
don't (and can't) get the real keys.
JC
--
AVIS : Falsifier le contenu et usurper l'ide
Hi,
I have an unusual LVM setup where GRUB cannot be installed (see last
Threads on LVM) because there is no room for core.img.
The only place where boot data can be put is on a logical volume, but
the bootsector (one of diskboot.S or boot.S, I assume) isn't smart
enough to understand LVM or file
Le dimanche 20 juillet 2008 à 17:06 +0200, Javier Martín a écrit :
Hi,
> This should have been fixed by the transition to LZMA as the compression
> algorithm for PC - core.img should now be under 32K and embeddable in
> the 32256 bytes available before the first MBR partition.
As I stated earlier
Le mardi 22 juillet 2008 à 23:47 +0200, Robert Millan a écrit :
>
> > As I stated earlier my disks are not DOS-partitioned (e.g.
> > pvcreate /dev/hda). I didn't want to have one useless level
>
> Turns out it wasn't as useless as you thought :-)
heh :)
> > since LVM already does the job (bett
Hello,
I used Grub for a long time, but I switched to LVM some months
ago and I realized I couldn't use grub anymore so I switched
back to Lilo.
Since then, I followed Grub development and tried to return to a
Grub-and-full-LVM setup. When installed on a floppy disk, the
latest Grub can boot my m
> On Wed, Jun 06, 2007 at 08:04:43PM +0200, adrian15 wrote:
> OTOH, if you replace:
>
> "GRUB loading kernel"
>
> with:
>
> "Loading GRUB kernel"
Why not "Loading GRUB core" ? It's already called that name in the files
anyway.
JC
___
Grub-devel m
14 matches
Mail list logo