On Tue, Jan 08, 2008 at 06:52:36PM -0500, Pavel Roskin wrote:
> [...]. It gets too complicated to
> bother without having a very good incentive to save those 2 bytes.
Heh, you have a point here.
--
Robert Millan
I know my rights; I want my phone call!
What use is a phone call, if you are una
On Wed, 2008-01-09 at 00:37 +0100, Robert Millan wrote:
> On Tue, Jan 08, 2008 at 05:57:16PM -0500, Pavel Roskin wrote:
> >
> > We can save 4 more bytes if we do "orb $0x80, %dl" unconditionally for
> > the hard drives. However, I'm not sure if there are BIOSes that pass 1
> > in %dl and how cri
On Jan 9, 2008 12:48 AM, Vincent Pelletier <[EMAIL PROTECTED]> wrote:
> within the next 2 months
Gah. "next 2 weeks".
Vincent Pelletier
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
On Jan 9, 2008 12:37 AM, Robert Millan <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 08, 2008 at 05:57:16PM -0500, Pavel Roskin wrote:
> > That's
> > something I'll rather not do without seeing the original bug reports.
>
> Same here. Maybe Okuji will know..
I have a box with this bug - sadly, I will
On Tue, Jan 08, 2008 at 05:57:16PM -0500, Pavel Roskin wrote:
>
> We can save 4 more bytes if we do "orb $0x80, %dl" unconditionally for
> the hard drives. However, I'm not sure if there are BIOSes that pass 1
> in %dl and how critical it would be if it becomes 0x81.
I think the assumption is th
On Tue, Jan 08, 2008 at 11:52:57PM +0100, Martin Braure de Calignon wrote:
>
> With your second patch, executing :
>
> grub-probe --target=type /usr/share/grub/unicode.pff
> output :
> lvm
>
> So it seems to gives correct output (but I have only unicode.pff not
> unifont.pff)
>
> So I think it
On Tue, Jan 08, 2008 at 11:18:28PM +0100, Jan Nieuwenhuizen wrote:
> Robert Millan writes:
>
> > Try this one.
>
> That's better, grub-install now does
>
>grub-mkimage --output=/tmp/boot/grub/core.img --prefix=/tmp/boot/grub ext2
> lvm biosdisk _chain
Try putting lvm after biosdisk (I ment
On Tue, 2008-01-08 at 21:24 +0100, Robert Millan wrote:
> On Tue, Jan 08, 2008 at 01:24:25PM -0500, Pavel Roskin wrote:
> > On Tue, 2008-01-08 at 11:50 +0100, Robert Millan wrote:
> > > boot_drive_check:
> > > jmp 1f /* grub-setup may overwrite this jump */
> > > testb $
With your second patch, executing :
grub-probe --target=type /usr/share/grub/unicode.pff
output :
lvm
So it seems to gives correct output (but I have only unicode.pff not
unifont.pff)
So I think it's great :-)
--
Martin Braure de Calignon
signature.asc
Description: Ceci est une partie de me
Robert Millan writes:
> Try this one.
That's better, grub-install now does
grub-mkimage --output=/tmp/boot/grub/core.img --prefix=/tmp/boot/grub ext2
lvm biosdisk _chain
I haven't tested yet, but this won't work, gpt (or pc?) is also needed, right?
I remember having seen
grub rescue> l
On Tue, Jan 08, 2008 at 10:05:59PM +0100, Jan Nieuwenhuizen wrote:
>
> grub-mkimage --output=/boot/grub/core.img --prefix=/boot/grub ext2 lvm pc
> gpt biosdisk _chain
> grub-setup '(hd0)'
>
> but that again gave me a grub rescue> prompt with exactly the same
> problems as before: erro
On Tue, Jan 08, 2008 at 10:05:59PM +0100, Jan Nieuwenhuizen wrote:
> Robert Millan writes:
>
> > Ok, so I fixed lvm/raid handling in core.img (by grub-install). This will
> > help
> > those who (unlike you) have their /boot under LVM or software RAID.
>
> I applied both pathces, but lvm does no
Robert Millan writes:
> Ok, so I fixed lvm/raid handling in core.img (by grub-install). This will
> help
> those who (unlike you) have their /boot under LVM or software RAID.
I applied both pathces, but lvm does not work for me yet. The second
patch has
+devtype_module=`$grub_probe --tar
On Tue, Jan 08, 2008 at 05:07:10PM +0100, Martin Braure de Calignon wrote:
> >
> > Please try attached patch and report (note: this is unrelated to the parser
> > error Bean fixed; the parser error simply makes the real problem in your
> > setup go away unnoticed).
>
> my previous post was for t
On Tue, Jan 08, 2008 at 04:08:35PM +, Oleg Strikov wrote:
> Good Day!
> I'm gonna create some grub2 security extensions to make fully functional High
> Assurance Bootloader. Now a have some pre-alpha code, but it seems to be
> functional in short time.
> I'm exporting some code from gnupg (gpl
On Tue, Jan 08, 2008 at 01:24:25PM -0500, Pavel Roskin wrote:
> On Tue, 2008-01-08 at 11:50 +0100, Robert Millan wrote:
> > boot_drive_check:
> > jmp 1f /* grub-setup may overwrite this jump */
> > testb $0x80, %dl
> > jnz 1f
> > movb$0x80, %dl
> >
On Tue, 2008-01-08 at 11:50 +0100, Robert Millan wrote:
> boot_drive_check:
> jmp 1f /* grub-setup may overwrite this jump */
> testb $0x80, %dl
> jnz 1f
> movb$0x80, %dl
> 1:
>
> However, if 0x80 is really "the only possible boot drive", that mea
On Tue, 2008-01-08 at 11:50 +0100, Robert Millan wrote:
> However, if 0x80 is really "the only possible boot drive", that means the
> test is pointless and can be replaced with:
>
> boot_drive_check:
> jmp 1f /* grub-setup may overwrite this jump */
> movb$0x80, %dl
>
Good Day!
I'm gonna create some grub2 security extensions to make fully functional High
Assurance Bootloader. Now a have some pre-alpha code, but it seems to be
functional in short time.
I'm exporting some code from gnupg (gpl v.3) project (RSA and MD5 impl). Is
it correct?
Will it be usable for g
On mar, 2008-01-08 at 16:01 +0100, Robert Millan wrote:
> On Tue, Jan 08, 2008 at 02:20:53PM +0100, Martin Braure de Calignon wrote:
> >
> > On mar, 2008-01-08 at 21:11 +0800, Bean wrote:
> > > I think the most likely command to cause the error is
> > >
> > > font (mainvg-usr)/share/grub/unicode
On mar, 2008-01-08 at 16:21 +0100, Robert Millan wrote:
> On Tue, Jan 08, 2008 at 04:01:40PM +0100, Robert Millan wrote:
> >
> > It's a bit funny. I tried to fix your problem, and at some point I realized
> > I was fixing something else.
>
> Ok, so I fixed lvm/raid handling in core.img (by grub
On Tue, Jan 08, 2008 at 04:25:28PM +0100, Jan Nieuwenhuizen wrote:
> Robert Millan writes:
>
> > It's a bit funny. I tried to fix your problem, and at some point I realized
> > I was fixing something else. Then got back at your problem, and turned out
> > we just need to force load of "lvm" and
Robert Millan writes:
> It's a bit funny. I tried to fix your problem, and at some point I realized
> I was fixing something else. Then got back at your problem, and turned out
> we just need to force load of "lvm" and "raid" before entering normal mode.
Ah, but this looks promising form my lvm
On Tue, Jan 08, 2008 at 04:05:35PM +0100, Jan Nieuwenhuizen wrote:
> Robert Millan writes:
>
> > > It looks as if the lvm module is defunct when it is loaded
> > > from core.img: ls shows no lvm devices.
>
> > It's a known bug, but nobody has time to fix it.
>
> Ah, that's a pity. Booting from
On Tue, Jan 08, 2008 at 04:01:40PM +0100, Robert Millan wrote:
>
> It's a bit funny. I tried to fix your problem, and at some point I realized
> I was fixing something else.
Ok, so I fixed lvm/raid handling in core.img (by grub-install). This will help
those who (unlike you) have their /boot un
Robert Millan writes:
> > It looks as if the lvm module is defunct when it is loaded
> > from core.img: ls shows no lvm devices.
> It's a known bug, but nobody has time to fix it.
Ah, that's a pity. Booting from lvm that's one of grub2's major
features from my point of view...
Any hints on ho
On Tue, Jan 08, 2008 at 02:20:53PM +0100, Martin Braure de Calignon wrote:
>
> On mar, 2008-01-08 at 21:11 +0800, Bean wrote:
> > I think the most likely command to cause the error is
> >
> > font (mainvg-usr)/share/grub/unicode.pff
> > or
> > terminal gfxterm
>
> I think 'font' line can't work
Robert Millan writes:
> > grub-mkimage --output=/boot/grub/core.img lvm ext2 pc gpt biosdisk
>
> To be more specific, grub-install already knows how to figure out that
> you need `ext2', and whether you need `pc' or `gpt' (you don't need both),
> but it needs to learn how to detect that lvm i
On Tue, Jan 08, 2008 at 03:01:12PM +0100, Martin Braure de Calignon wrote:
>
> On mar, 2008-01-08 at 14:13 +0100, Robert Millan wrote:
> >
> > Does your empty menu look exactly like this one?
> >
> > http://aybabtu.com/tmp/screenshot.png
>
> Not exactly, it looks like this one, but I have a r
On Tue, Jan 08, 2008 at 09:18:47PM +0800, Bean wrote:
> On Jan 8, 2008 9:14 PM, Robert Millan <[EMAIL PROTECTED]> wrote:
> >
> > On Tue, Jan 08, 2008 at 09:06:41PM +0800, Bean wrote:
> > > On Jan 8, 2008 9:00 PM, Martin Braure de Calignon <[EMAIL PROTECTED]>
> > > wrote:
> > > >
> > > > On mar, 20
On Tue, Jan 08, 2008 at 02:20:53PM +0100, Martin Braure de Calignon wrote:
>
> On mar, 2008-01-08 at 21:11 +0800, Bean wrote:
> > I think the most likely command to cause the error is
> >
> > font (mainvg-usr)/share/grub/unicode.pff
> > or
> > terminal gfxterm
>
> I think 'font' line can't work
On mar, 2008-01-08 at 15:01 +0100, Martin Braure de Calignon wrote:
> On mar, 2008-01-08 at 14:13 +0100, Robert Millan wrote:
> >
> > Does your empty menu look exactly like this one?
> >
> > http://aybabtu.com/tmp/screenshot.png
>
> Not exactly, it looks like this one, but I have a rectangula
On mar, 2008-01-08 at 14:13 +0100, Robert Millan wrote:
>
> Does your empty menu look exactly like this one?
>
> http://aybabtu.com/tmp/screenshot.png
Not exactly, it looks like this one, but I have a rectangular zone and a
highlighted blank line where the menu should be
Cheers,
--
Martin B
On Jan 8, 2008 9:20 PM, Martin Braure de Calignon <[EMAIL PROTECTED]> wrote:
>
> On mar, 2008-01-08 at 21:11 +0800, Bean wrote:
> > I think the most likely command to cause the error is
> >
> > font (mainvg-usr)/share/grub/unicode.pff
> > or
> > terminal gfxterm
>
> I think 'font' line can't work b
On mar, 2008-01-08 at 21:11 +0800, Bean wrote:
> I think the most likely command to cause the error is
>
> font (mainvg-usr)/share/grub/unicode.pff
> or
> terminal gfxterm
I think 'font' line can't work because font are on my /usr, and /usr is
LVM and lvm module is not loaded... But I though gru
On Jan 8, 2008 9:14 PM, Robert Millan <[EMAIL PROTECTED]> wrote:
>
> On Tue, Jan 08, 2008 at 09:06:41PM +0800, Bean wrote:
> > On Jan 8, 2008 9:00 PM, Martin Braure de Calignon <[EMAIL PROTECTED]> wrote:
> > >
> > > On mar, 2008-01-08 at 13:13 +0100, Robert Millan wrote:
> > > > Ok, so you have fon
On Tue, Jan 08, 2008 at 09:06:41PM +0800, Bean wrote:
> On Jan 8, 2008 9:00 PM, Martin Braure de Calignon <[EMAIL PROTECTED]> wrote:
> >
> > On mar, 2008-01-08 at 13:13 +0100, Robert Millan wrote:
> > > Ok, so you have fonts. What are the color settings? (run "set" and check
> > > for menu_color_
On Tue, Jan 08, 2008 at 02:00:10PM +0100, Martin Braure de Calignon wrote:
>
> On mar, 2008-01-08 at 13:13 +0100, Robert Millan wrote:
> > Ok, so you have fonts. What are the color settings? (run "set" and check
> > for menu_color_* variables)
> set gives the following output :
> ?=1
> color_hig
On Jan 8, 2008 9:06 PM, Bean <[EMAIL PROTECTED]> wrote:
> On Jan 8, 2008 9:00 PM, Martin Braure de Calignon <[EMAIL PROTECTED]> wrote:
> >
> > On mar, 2008-01-08 at 13:13 +0100, Robert Millan wrote:
> > > Ok, so you have fonts. What are the color settings? (run "set" and check
> > > for menu_colo
On Jan 8, 2008 9:00 PM, Martin Braure de Calignon <[EMAIL PROTECTED]> wrote:
>
> On mar, 2008-01-08 at 13:13 +0100, Robert Millan wrote:
> > Ok, so you have fonts. What are the color settings? (run "set" and check
> > for menu_color_* variables)
> set gives the following output :
> ?=1
Here is t
On mar, 2008-01-08 at 13:13 +0100, Robert Millan wrote:
> Ok, so you have fonts. What are the color settings? (run "set" and check
> for menu_color_* variables)
set gives the following output :
?=1
color_highlight=
color_normal=
default=0
prefix=(hd0,9)/boot/grub
root=(hd0,9)
so no menu_color*
On Tue, Jan 08, 2008 at 11:21:43AM +0100, Martin Braure de Calignon wrote:
> > Yes, but first I need to understand better what you saw. Does "graphical"
> > mean it was in VESA mode? You can tell that because "terminal" command
> > would
> > return "gfxterm" rather than "console". Or does it si
On Tue, Jan 08, 2008 at 11:21:43AM +0100, Martin Braure de Calignon wrote:
>
> Ok it makes sense to not include all the variables in /etc/default/grub
> because of course, /etc/default/grub should only contains variable that
> do not really depends on script. But a kernel command line
> personaliz
http://cvs.savannah.gnu.org/viewvc/grub2/configure?root=grub&view=log
Does it make sense to keep `configure' under revision control? Almost every
commit for unrelated things tends to change the whole thing.
--
Robert Millan
I know my rights; I want my phone call!
What use is a phone call,
boot/i386/pc/boot.S reads:
/*
* This is a workaround for buggy BIOSes which don't pass boot
* drive correctly. If GRUB is installed into a HDD, check if
* DL is masked correctly. If not, assume that the BIOS passed
* a bogus value and set DL to 0x80, si
On mar, 2008-01-08 at 10:24 +0100, Robert Millan wrote:
> On Mon, Jan 07, 2008 at 11:31:17PM +0100, Martin Braure de Calignon wrote:
> > Of course. One possible temporary solution would be to insert all
> > customization variables in 10_linux and other files in /etc/default/grub
> > with no value
On Tue, Jan 08, 2008 at 10:48:41AM +0100, Jan Nieuwenhuizen wrote:
>
> Here is what I do
>
> grub-mkimage --output=/boot/grub/core.img lvm ext2 pc gpt biosdisk
To be more specific, grub-install already knows how to figure out that
you need `ext2', and whether you need `pc' or `gpt' (you don'
On Tue, Jan 08, 2008 at 10:48:41AM +0100, Jan Nieuwenhuizen wrote:
> [resend from 2007-12-08]
>
> Hi,
>
> I'm trying out Grub2 to for a setup with root on lvm, and it
> almost works :-) (grub2 looks great, btw!) If I install grub on a
> non-lvm partition without lvm preloaded in core.img, it wor
On Mon, Jan 07, 2008 at 11:54:04PM +0100, Yoshinori K. Okuji wrote:
> On Monday 07 January 2008 10:19, Robert Millan wrote:
> > Great! I see that you fixed the endianess issues.
> >
> > I'll push this to Debian sid ASAP.
>
> I hope I have fixed all the endianness issues, but I am not sure yet. Pe
[resend from 2007-12-08]
Hi,
I'm trying out Grub2 to for a setup with root on lvm, and it
almost works :-) (grub2 looks great, btw!) If I install grub on a
non-lvm partition without lvm preloaded in core.img, it works
fine. It looks as if the lvm module is defunct when it is loaded
from core.im
On Mon, Jan 07, 2008 at 11:31:17PM +0100, Martin Braure de Calignon wrote:
>
> Of course. One possible temporary solution would be to insert all
> customization variables in 10_linux and other files in /etc/default/grub
> with no value no and a simple comment over it (all the common used
> variabl
On Tue, Jan 08, 2008 at 11:26:13AM +1300, Centurion Computer Technology (2005)
Ltd wrote:
> On Mon, 2008-01-07 at 23:13 +0100, Robert Millan wrote:
> > That's a mirror of our CVS, right? You mean that you want me to add the
> > debian
> > stuff to CVS, or... ?
>
> Hopefully Pavel can enlighten
52 matches
Mail list logo
