Re: Some issues in scripting support?

2006-03-10 Thread Marco Gerards
Vesa Jääskeläinen [EMAIL PROTECTED] writes:

Hi Vesa,

 I was playing a bit with grub.cfg and following crashes my vmware
 session... :)... I know I didn't remember first that there were
 syntaxtical changes in there, but even after correcting my mistake, it
 doesn't allow me move it with cursor keys, not in console or in video
 mode. Pressing enter correctly changes to video mode as it were first
 choice.

Yeah, error handling should be improved considerably.  I found some
other bugs related to this as well.  It's something I planned to work
on after my current networking code is in CVS.

--
Marco



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


Re: Status of UNDI Support

2006-03-10 Thread Marco Gerards
Martin Vogt [EMAIL PROTECTED] writes:

Hi Martin,

 I just tried pxegrub2, but I found out that the network support
 is missing. (can load pxegrub, but no menu.lst or kernel etc)

 My experience with grub1 and the etherboot based nic support,
 is that it does not work well, so I still use pxelinux.
 I always thought that grub2 wont use etheboot and only supports UNDI,
 like pxelinux.

At the moment GRUB 2 does not support networking.  But we are working
on that.

 Isnt it possible to re-use some UNDI support from pxelinux and put it
 into grub2?

I don't know.  I think it is better that we write it ourselves, it
does not appear too hard to implement...

--
Marco



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


Re: OF default catch on grub2 on 43p-260

2006-03-10 Thread Hollis Blanchard
On Tuesday 07 March 2006 14:29, Chris Abbey wrote:
 I just tried out grub2 on my ppc64 box, a 43p-260 using cvs as of 6 March. 
It 
 0  setenv debug all  ok
 0  0  0  printenv debug
 debugall
  ok

This part here won't work. GRUB doesn't look for an OF variable named 
debug (technically such a thing does not exist, according to IEEE1275), but 
rather a commandline argument. So you would do this:
0  boot debug=all
or even
0  boot floppy debug=all
... but in this particular case, the crash is very very early, and also we 
already got our helpful debugging message.

 0  boot Failed to claim heap at 0x4000, len 0x1fb000

This is telling us that GRUB attempted to claim some memory for its heap (at 
that address and that length), but some of it was already in use, so the 
request failed.

From the OF prompt, before you boot GRUB, could you do the following and send 
the output:
0  dev /[EMAIL PROTECTED]
0  .properties
In particular, the available property is the one I'm interested in. That 
will tell us what areas of memory are considered free...

-Hollis


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


mkfs command in grub

2006-03-10 Thread technologypages
Can someone please comment if adding filesystem creation support to grub 
is reasonable.


Please see the rationale at 
http://www.geocities.com/technologypages/grub-mkfs.txt


Will the developers consider adding this feature? It is rather easy to 
implement as far as I can see -- only glue for external filesystem 
creation code needs to be added.


Although the swap sharing use case discussed in the rationale is 
trivial, it is a common problem that may bring many multi-OS users over 
to GRUB 2 and create positive media coverage (if that feature will be 
added).



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


Re: Status of UNDI Support

2006-03-10 Thread vincent guffens

I am resending this mail, it looks that it didn't get through:


Martin Vogt wrote:


Hello grub2 developers,


I just tried pxegrub2, but I found out that the network support
is missing. (can load pxegrub, but no menu.lst or kernel etc)
 


hi,

i have been working on netboot support for grub2 for a while and even 
got it working once using code from etherboot.
I am now grubifying the work in order to submit a patch. The PCI support 
is on its way and is going to feature an abstract interface which should 
ease the merging of new implementations.



My experience with grub1 and the etherboot based nic support,
is that it does not work well, so I still use pxelinux.
I always thought that grub2 wont use etheboot and only supports UNDI,
like pxelinux.

 

As far as I know, a lot of  problems related to netboot in grub were 
linked to the fact that  the drivers could not easily be linked together 
as it could  result in grub freezing of behaving improperly. The idea in 
grub2 is still to use the etherboot drivers but not to be limited by 
them. There will be a glue layer in order to import the etherboot 
drivers, hopefully with as little modifications as possible, but it will 
be possible to extend that.



Isnt it possible to re-use some UNDI support from pxelinux and put it
into grub2?

 



I don't know very much about this UNDI support but this is certainly not 
incompatible with using the etherboot drivers for supported cards 
anyway. Grub is very flexible and we can certainly have both support if 
it is worth it.



regards,

Martin






--
Vincent Guffens
Intelligent Systems  Networks Group
		Research associate, Imperial College 




___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


Re: New patch for video subsystem...

2006-03-10 Thread Vesa Jääskeläinen
Vesa Jääskeläinen wrote:

 Is there a nice way to split vbe driver to
 more source files without causing generation of more modules. I was
 thinking that optimized versions of some blitting operations would be
 good to place on some other file as source might grow to quite large.

I should have sleeped before asking this question :) conf/*.rmk and just
adding source file to vbe.mod defs



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


Re: Status of UNDI Support

2006-03-10 Thread Martin Vogt
Marco Gerards wrote:
 Martin Vogt [EMAIL PROTECTED] writes:

 Hi Martin,

   
 I just tried pxegrub2, but I found out that the network support
 is missing. (can load pxegrub, but no menu.lst or kernel etc)

 My experience with grub1 and the etherboot based nic support,
 is that it does not work well, so I still use pxelinux.
 I always thought that grub2 wont use etheboot and only supports UNDI,
 like pxelinux.
 

 At the moment GRUB 2 does not support networking.  But we are working
 on that.

   
 Isnt it possible to re-use some UNDI support from pxelinux and put it
 into grub2?
 

 I don't know.  I think it is better that we write it ourselves, it
 does not appear too hard to implement...

   
Hi Marco,

thanks for your reply. I read a bit grub2-devel and found out that there
are some thoughts about linuxbios support.
I dont know if linuxbios has some abstraction for network access.
Usually (clusterenvironment) you get linuxbios with the right
etherboot  prom installed. The normal way for installing is
booting an .ebi installer.
The other way which somtimes is used, you go over pxe to
the right etherboot image and then load an ebi.
Only as an idea: It would be great if one grub binary could
work on then UNDI layer and the etherboot layer (if there is any).

But I dont know if this is possible at all.

regards,

Martin




___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


Re: Status of UNDI Support

2006-03-10 Thread Yedidyah Bar-David
On Fri, Mar 10, 2006 at 03:07:36PM +0100, Marco Gerards wrote:
 Martin Vogt [EMAIL PROTECTED] writes:
  Isnt it possible to re-use some UNDI support from pxelinux and put it
  into grub2?

While I do not know the internals of grub2, I guess some parts of it run
in protected mode, while pxelinux is realmode only. I think this means
it won't be easy to use parts of it.

 
 I don't know.  I think it is better that we write it ourselves, it
 does not appear too hard to implement...

Looking at the sources of pxelinux, it seems somewhat more complex than
what you can tell from reading the specs, mainly because you want, as
reasonably as possible, to support also buggy PXE stacks etc. So while
it's probably not that hard, it would make sense to look at pxelinux for
reference if not for the code.

I personally was a user of both etherboot, grub with etherboot drivers
and grub with undi (which indeed did not work well for me back then - I
did not try it recently), and I agree it would make more sense for grub2
to support undi only, unlike grub legacy which tried to support
everything etherboot supported, which was probably too much
synchronization work and therefore did not work well.
-- 
Didi



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


Re: Status of UNDI Support

2006-03-10 Thread Marco Gerards
[EMAIL PROTECTED] (Yedidyah Bar-David) writes:

 On Fri, Mar 10, 2006 at 03:07:36PM +0100, Marco Gerards wrote:
 Martin Vogt [EMAIL PROTECTED] writes:
  Isnt it possible to re-use some UNDI support from pxelinux and put it
  into grub2?

 While I do not know the internals of grub2, I guess some parts of it run
 in protected mode, while pxelinux is realmode only. I think this means
 it won't be easy to use parts of it.

GRUB is able to switch to realmode and back.  It's what's done when
accessing the BIOS to read from disk.

 
 I don't know.  I think it is better that we write it ourselves, it
 does not appear too hard to implement...

 Looking at the sources of pxelinux, it seems somewhat more complex than
 what you can tell from reading the specs, mainly because you want, as
 reasonably as possible, to support also buggy PXE stacks etc. So while
 it's probably not that hard, it would make sense to look at pxelinux for
 reference if not for the code.

 I personally was a user of both etherboot, grub with etherboot drivers
 and grub with undi (which indeed did not work well for me back then - I
 did not try it recently), and I agree it would make more sense for grub2
 to support undi only, unlike grub legacy which tried to support
 everything etherboot supported, which was probably too much
 synchronization work and therefore did not work well.

I prefer to support both.  The etherboot drivers usually work better
than UNDI, AFAIK.  But when etherboot does not support a card, people
can fall back to UNDI.  Don't forget that not all cards support UNDI,
so I don't want UNDI only.

--
Marco



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel