success booting hdt.c32 module with memdisk

success booting hdt.c32 module with memdisk

[J. Bakshi]

Hello list,

Finally I got success booting hdt.c32 module ( hdt = hardware detection tool) with the latest floppy image released by hdt team. hdt.c32 is a syslinux module. As per their suggestion the following config works for me from usb stick.

menuentry HDT {
linux16 /memdisk
initrd16 /<hdt_floppy_image>
}

Though it would be nice to see grub's power to directly load syslinux module like this one :-)

HDT is really a must to have collection in the tool collection. It does not need to load an OS to collect info of your H/W. you can know more from  http://syslinux.zytor.com/wiki/index.php/Hdt_(Hardware_Detection_Tool)

cheers 

Re: success booting hdt.c32 module with memdisk

[Vladimir 'phcoder' Serbinenko]

Hello
J. Bakshi wrote:
> Hello list,
>
> Finally I got success booting hdt.c32 module ( hdt = hardware detection tool) with the latest floppy image released by hdt team. hdt.c32 is a syslinux module. As per their suggestion the following config works for me from usb stick.
>
> menuentry HDT {
> linux16 /memdisk
> initrd16 /<hdt_floppy_image>
> }
>
> Though it would be nice to see grub's power to directly load syslinux module like this one :-)
>
>   
I would be happy to have syslinux com32 glue level. Are you willing to
code one?
> HDT is really a must to have collection in the tool collection. It does not need to load an OS to collect info of your H/W. you can know more from  http://syslinux.zytor.com/wiki/index.php/Hdt_(Hardware_Detection_Tool)
>
> cheers 
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>   


-- 
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git 

Re: success booting hdt.c32 module with memdisk

[J. Bakshi]

On Thu, 29 Oct 2009 16:41:17 +0100
Vladimir 'phcoder' Serbinenko <phcoder@gmail.com> wrote:

> Hello
> J. Bakshi wrote:
> > Hello list,
> >
> > Finally I got success booting hdt.c32 module ( hdt = hardware
> > detection tool) with the latest floppy image released by hdt team.
> > hdt.c32 is a syslinux module. As per their suggestion the following
> > config works for me from usb stick.
> >
> > menuentry HDT {
> > linux16 /memdisk
> > initrd16 /<hdt_floppy_image>
> > }
> >
> > Though it would be nice to see grub's power to directly load
> > syslinux module like this one :-)
> >
> >   
> I would be happy to have syslinux com32 glue level. Are you willing to
> code one?

I would Love to do so but as a Linux sysadmin my programming knowledge is restricted in shell-script :-(
If you permit me and show me the direction then I can ask the required info at hdt group.


> > HDT is really a must to have collection in the tool collection. It
> > does not need to load an OS to collect info of your H/W. you can
> > know more from
> > http://syslinux.zytor.com/wiki/index.php/Hdt_(Hardware_Detection_Tool)
> >
> > cheers 
> >
> >
> > _______________________________________________
> > Grub-devel mailing list
> > Grub-devel@gnu.org
> > http://lists.gnu.org/mailman/listinfo/grub-devel
> >
> >   
> 
> 

Re: success booting hdt.c32 module with memdisk

[Robert Millan]

On Thu, Oct 29, 2009 at 08:20:00PM +0530, J. Bakshi wrote:
> 
> Though it would be nice to see grub's power to directly load syslinux module like this one :-)

If this module is free software, we can adjust it to support a true boot
standard like Multiboot.  Then HDT would be useful in other setups (e.g.
GRUB Legacy or coreboot).

I think a patch that adds Multiboot support to HDT would be more useful
than another standalone loader.

(but failing that, we could have yet another loader, of course)

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

Re: success booting hdt.c32 module with memdisk

[Vladimir 'phcoder' Serbinenko]

Robert Millan wrote:
> On Thu, Oct 29, 2009 at 08:20:00PM +0530, J. Bakshi wrote:
>   
>> Though it would be nice to see grub's power to directly load syslinux module like this one :-)
>>     
>
> If this module is free software, we can adjust it to support a true boot
> standard like Multiboot.  Then HDT would be useful in other setups (e.g.
> GRUB Legacy or coreboot).
>
> I think a patch that adds Multiboot support to HDT would be more useful
> than another standalone loader.
>
> (but failing that, we could have yet another loader, of course)
>
>   
This isn't like a normal payload as far as I understand but more like
grub modules


-- 
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git 

Re: success booting hdt.c32 module with memdisk

[Vladimir 'phcoder' Serbinenko]

J. Bakshi wrote:
> On Thu, 29 Oct 2009 16:41:17 +0100
> Vladimir 'phcoder' Serbinenko <phcoder@gmail.com> wrote:
>
>   
>> Hello
>> J. Bakshi wrote:
>>     
>>> Hello list,
>>>
>>> Finally I got success booting hdt.c32 module ( hdt = hardware
>>> detection tool) with the latest floppy image released by hdt team.
>>> hdt.c32 is a syslinux module. As per their suggestion the following
>>> config works for me from usb stick.
>>>
>>> menuentry HDT {
>>> linux16 /memdisk
>>> initrd16 /<hdt_floppy_image>
>>> }
>>>
>>> Though it would be nice to see grub's power to directly load
>>> syslinux module like this one :-)
>>>
>>>   
>>>       
>> I would be happy to have syslinux com32 glue level. Are you willing to
>> code one?
>>     
>
> I would Love to do so but as a Linux sysadmin my programming knowledge is restricted in shell-script :-(
> If you permit me and show me the direction then I can ask the required info at hdt group.
>
>   
Basically you just need to get coding
1) Verify that the module is under compatible license
2) Put it into grub2 directory and add to rmk file
3) Fix all compile errors
Binary compatibility is more difficult to get binary compatibility but
is probably useless too as anyway you can't have non GPLv3+-compatible
modules so source compatibility is enough. Additionally having them as
source in grub-extras potentially makes it useful on non-pc as well

-- 
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git 

Re: success booting hdt.c32 module with memdisk

[Robert Millan]

On Fri, Oct 30, 2009 at 08:50:27PM +0100, Vladimir 'phcoder' Serbinenko wrote:
> This isn't like a normal payload as far as I understand but more like
> grub modules

Ah, I see.  In that case, we could have some glue code (similar to the
lib-linux branch I'm working on).

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

Re: success booting hdt.c32 module with memdisk

[J. Bakshi]

On Fri, 30 Oct 2009 20:54:28 +0100
Vladimir 'phcoder' Serbinenko <phcoder@gmail.com> wrote:

> J. Bakshi wrote:
> > On Thu, 29 Oct 2009 16:41:17 +0100
> > Vladimir 'phcoder' Serbinenko <phcoder@gmail.com> wrote:
> >
> >   
> >> Hello
> >> J. Bakshi wrote:
> >>     
> >>> Hello list,
> >>>
> >>> Finally I got success booting hdt.c32 module ( hdt = hardware
> >>> detection tool) with the latest floppy image released by hdt team.
> >>> hdt.c32 is a syslinux module. As per their suggestion the
> >>> following config works for me from usb stick.
> >>>
> >>> menuentry HDT {
> >>> linux16 /memdisk
> >>> initrd16 /<hdt_floppy_image>
> >>> }
> >>>
> >>> Though it would be nice to see grub's power to directly load
> >>> syslinux module like this one :-)
> >>>
> >>>   
> >>>       
> >> I would be happy to have syslinux com32 glue level. Are you
> >> willing to code one?
> >>     
> >
> > I would Love to do so but as a Linux sysadmin my programming
> > knowledge is restricted in shell-script :-( If you permit me and
> > show me the direction then I can ask the required info at hdt group.
> >
> >   
> Basically you just need to get coding
> 1) Verify that the module is under compatible license
> 2) Put it into grub2 directory and add to rmk file
> 3) Fix all compile errors
> Binary compatibility is more difficult to get binary compatibility but
> is probably useless too as anyway you can't have non GPLv3+-compatible
> modules so source compatibility is enough. Additionally having them as
> source in grub-extras potentially makes it useful on non-pc as well
> 

Ok, then let me collect the license info first and the required module dependency from hdt group. I am sure inclusion of hdt in grub2 will give it an extra potential :-)