Using ADLO with Linuxbios

[Shubhangi Jadhav]

Hi,

I have 512k bios, so the kernel should be put somewhere on the harddisk.
Hence I'm using ADLO with Linuxbios. However I'm not able to get linuxbios
working.
    I followed these steps :

Build the ADLO payload as per the instructions in the readme for ADLO.
Appended the following entry to the config file :
    USE_ELF_BOOT=0
    payload /home/shubhangi/freebios/util/ADLO/payload
Build the romimage using this config file.

Is this the correct way to use ADLO? Thanks for any help.

Regards,
Shubhangi

[bendany]

----- Original Message -----
From: "Shubhangi Jadhav" 
To: "LinuxBIOS" 
Sent: Friday, April 25, 2003 1:10 AM
Subject: Using ADLO with Linuxbios
> Hi,
>
> I have 512k bios, so the kernel should be put somewhere on the harddisk.
> Hence I'm using ADLO with Linuxbios. However I'm not able to get linuxbios
> working.
> I followed these steps :
>
> Build the ADLO payload as per the instructions in the readme for ADLO.
> Appended the following entry to the config file :
> USE_ELF_BOOT=0

why set it to 0? ADLO+BOCHS+VIDEOBIOS will be a ELF program.
so you can put the ADLO to the anywhere, such as rom/harddisk/tftp server/
first, you can test the LinuxBIOS , make sure that it can run on your mb
correctly.
Also make sure that the linuxbios can load the ELF kernel correctly.
and next you can replace the linux ELF kernel with the ADLO, patch the
rombios.c with
the serial patch. and try the next test.
BTW: what is your mb's type? sis630,or else?
> payload /home/shubhangi/freebios/util/ADLO/payload
> Build the romimage using this config file.
>
> Is this the correct way to use ADLO? Thanks for any help.
>
> Regards,
> Shubhangi
>
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios

[Shubhangi Jadhav]

Hi,

If I burn ADLO alongwith linuxbios on rom do we need to specify BOOT_IDE=1
?

Thanks,
Shubhangi

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]]On Behalf Of bendany
Sent: Saturday, April 26, 2003 9:01 AM
To: Shubhangi Jadhav
Cc: [e-mail]
Subject: Re: Using ADLO with Linuxbios

----- Original Message -----
From: "Shubhangi Jadhav" 
To: "LinuxBIOS" 
Sent: Friday, April 25, 2003 1:10 AM
Subject: Using ADLO with Linuxbios
> Hi,
>
> I have 512k bios, so the kernel should be put somewhere on the harddisk.
> Hence I'm using ADLO with Linuxbios. However I'm not able to get linuxbios
> working.
> I followed these steps :
>
> Build the ADLO payload as per the instructions in the readme for ADLO.
> Appended the following entry to the config file :
> USE_ELF_BOOT=0

why set it to 0? ADLO+BOCHS+VIDEOBIOS will be a ELF program.
so you can put the ADLO to the anywhere, such as rom/harddisk/tftp server/
first, you can test the LinuxBIOS , make sure that it can run on your mb
correctly.
Also make sure that the linuxbios can load the ELF kernel correctly.
and next you can replace the linux ELF kernel with the ADLO, patch the
rombios.c with
the serial patch. and try the next test.
BTW: what is your mb's type? sis630,or else?
> payload /home/shubhangi/freebios/util/ADLO/payload
> Build the romimage using this config file.
>
> Is this the correct way to use ADLO? Thanks for any help.
>
> Regards,
> Shubhangi
>
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

[Adam Agnew]

On Fri, 25 Apr 2003, Shubhangi Jadhav wrote:
> Hi,
>
> If I burn ADLO alongwith linuxbios on rom do we need to specify BOOT_IDE=1

Nope. BOOT_IDE is merely to use the ide support thats directly in
LinuxBIOS, in which case it would skip right over ADLO.

[Deepak Kotian]

So, if I want to boot from Compact Flash IDE which has Linux, would
LinuxBIOS directly boot it.
Do I really need ADLO for this purpose ? And also can one do away with
etherboot as
well ?
If ADLO is not needed, then would the kernel image be read by the LINUXBIOS
directly
from the IDE if we specific the path of the vmlinuz image.

I read a message from Ron, that one can just
do
cat vmlinux..gz > /dev/hda1 and etherboot would be OK.
Should it done something like this when BOOT_IDE is set.
Could you please elaborate.

Regards
Deepak

----- Original Message -----
From: "Adam Agnew" 
To: "Shubhangi Jadhav" 
Cc: "bendany" ; 
Sent: Friday, April 25, 2003 9:38 PM
Subject: RE: Using ADLO with Linuxbios
> On Fri, 25 Apr 2003, Shubhangi Jadhav wrote:
> > Hi,
> >
> > If I burn ADLO alongwith linuxbios on rom do we need to specify

BOOT_IDE=1
> Nope. BOOT_IDE is merely to use the ide support thats directly in
> LinuxBIOS, in which case it would skip right over ADLO.
>
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios

[ron minnich]

On Sat, 26 Apr 2003, Deepak Kotian wrote:
> So, if I want to boot from Compact Flash IDE which has Linux, would
> LinuxBIOS directly boot it.
> Do I really need ADLO for this purpose ? And also can one do away with
> etherboot as
> well ?
> If ADLO is not needed, then would the kernel image be read by the LINUXBIOS
> directly
> from the IDE if we specific the path of the vmlinuz image.
>
> I read a message from Ron, that one can just
> do
> cat vmlinux..gz > /dev/hda1 and etherboot would be OK.

cat elfImage > /dev/hda1

make sure it is a linuxbios-format elfImage

ron

[Deepak Kotian]

Sorry, did not quite get it.
What is this elfimage, I have my own kernel image which I would like
to boot from LinuxBIOS.
Can I convert my kernel image to LinuxBIOS format, what
would be procedure..

Could you Please elaborate..

----- Original Message -----
From: "ron minnich" 
To: "Deepak Kotian" 
Cc: "Adam Agnew" ; "Shubhangi Jadhav"
; "bendany" ;

Sent: Saturday, April 26, 2003 1:12 AM
Subject: Re: Using ADLO with Linuxbios
> On Sat, 26 Apr 2003, Deepak Kotian wrote:
> > So, if I want to boot from Compact Flash IDE which has Linux, would
> > LinuxBIOS directly boot it.
> > Do I really need ADLO for this purpose ? And also can one do away with
> > etherboot as
> > well ?
> > If ADLO is not needed, then would the kernel image be read by the

LINUXBIOS
> > directly
> > from the IDE if we specific the path of the vmlinuz image.
> >
> > I read a message from Ron, that one can just
> > do
> > cat vmlinux..gz > /dev/hda1 and etherboot would be OK.
>
> cat elfImage > /dev/hda1
>
> make sure it is a linuxbios-format elfImage
>
> ron

[Steve Gehlbach]

Deepak Kotian wrote:
> Sorry, did not quite get it.
> What is this elfimage, I have my own kernel image which I would like
> to boot from LinuxBIOS.
> Can I convert my kernel image to LinuxBIOS format, what
> would be procedure..
>
> Could you Please elaborate..

In the current linuxbios, you can also boot directly without an elf 
image file.  Look at the configuration 
freebios/util/config/pcchips787.config; this boots from CF on IDE device 
2 = /dev/hdc1 (cat linux.bin.gz > /dev/hdc1) and mounts /dev/hda2 as 
root.  linux.bin.gz is made in the build process by the linuxbios 
makefile, from vmlinux in your kernel source directory.

It is my understanding this direct mechanism will be removed, though, in 
linuxbios2, so that only elf images can be used in the future.

-Steve

[ron minnich]

On Fri, 25 Apr 2003, Steve Gehlbach wrote:
> It is my understanding this direct mechanism will be removed, though, in 
> linuxbios2, so that only elf images can be used in the future.

yes but booting elfimages direct from linuxbios will still be possible.

ron

ron minnich  writes:
> On Fri, 25 Apr 2003, Steve Gehlbach wrote:
> > It is my understanding this direct mechanism will be removed, though, in 
> > linuxbios2, so that only elf images can be used in the future.

Already done.

The basic rule so we have a line against code bloat is that:
LinuxBIOS will boot an ELF image non-interactively off of 1 device.
It can be any device you want, but it is one ELF image.
> yes but booting elfimages direct from linuxbios will still be possible.

Yep.  So far I only have the simple rom driver in the tree.
But moving some other ones over as well should not be a problem.

In building up the tree I am going back and forth between making the
Opteron port work (with everything hard coded I can boot linux now),
and simplifying and generalizing the generic code.

An interesting facet of how Hypertransport works even device numbers
are no longer fixed.  So our current interrupt code must be reworked.
When the bus and device number change copying static tables of static
information just does not work.

Eric

[Shubhangi Jadhav]

So now from what understand, if I want to use Linuxbios to directly boot my
elfimage how do I go about
    build linuxbios using the option BOOT_IDE in the config file
    build an elfimage from my kernel image setting OUTPUT_FORMAT="elf32-i386"
in mkelfimage
    cat elfimage > /dev/hda1
    burn linuxbios on the flash rom
Is that all I need to get going ?

Thanks,
Shubhangi

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]]On Behalf Of Eric W. Biederman
Sent: Saturday, April 26, 2003 6:35 AM
To: ron minnich
Cc: Steve Gehlbach; Deepak Kotian; Adam Agnew; Shubhangi Jadhav;
bendany; [e-mail]
Subject: Re: Using ADLO with Linuxbios

ron minnich  writes:
> On Fri, 25 Apr 2003, Steve Gehlbach wrote:
> > It is my understanding this direct mechanism will be removed, though, in
> > linuxbios2, so that only elf images can be used in the future.

Already done.

The basic rule so we have a line against code bloat is that:
LinuxBIOS will boot an ELF image non-interactively off of 1 device.
It can be any device you want, but it is one ELF image.
> yes but booting elfimages direct from linuxbios will still be possible.

Yep.  So far I only have the simple rom driver in the tree.
But moving some other ones over as well should not be a problem.

In building up the tree I am going back and forth between making the
Opteron port work (with everything hard coded I can boot linux now),
and simplifying and generalizing the generic code.

An interesting facet of how Hypertransport works even device numbers
are no longer fixed.  So our current interrupt code must be reworked.
When the bus and device number change copying static tables of static
information just does not work.

Eric

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

"Shubhangi Jadhav"  writes:
> So now from what understand, if I want to use Linuxbios to directly boot my
> elfimage how do I go about
>    build linuxbios using the option BOOT_IDE in the config file
>    build an elfimage from my kernel image setting
> OUTPUT_FORMAT="elf32-i386"
>
> in mkelfimage
>    cat elfimage > /dev/hda1
>    burn linuxbios on the flash rom
> Is that all I need to get going ?

Yes I think so.  The BOOT_IDE driver has been modified in strange
ways to find things in the first partition and I have not had a chance
to look over the code to see what is going on there yet.

Eric

[Steve Gehlbach]

Eric W. Biederman wrote:
> The BOOT_IDE driver has been modified in strange
> ways to find things in the first partition and I have not had a chance
> to look over the code to see what is going on there yet.

Not strange to me, by default it simply skips 63x512 bytes (0x7e00), 
which is normally for most disks today where partition 1 starts.  Of 
course, it should read and decode the partition table, but this is much 
harder.

-Steve

Steve Gehlbach  writes:
> Eric W. Biederman wrote:
> > The BOOT_IDE driver has been modified in strange
> > ways to find things in the first partition and I have not had a chance
> > to look over the code to see what is going on there yet.
>
> Not strange to me, by default it simply skips 63x512 bytes (0x7e00), which is
> normally for most disks today where partition 1 starts.  Of course, it should
> read and decode the partition table, but this is much harder.

No.  I very deliberately do not read partition tables.
And not because it is difficult, but more because there is not
a consensus (especially across architectures) on what partition
tables should look like.

The code used to work just like the etherboot code and read
the first 8K but that has obviously changed while I was not
looking.

Current x86 partition tables are limited to 2TB disks.  Not
an immediate problem I admit but with 120+GB drives today
it is a limit we are quickly approaching.

Eric

[ron minnich]

On Sat, 26 Apr 2003, Shubhangi Jadhav wrote:
> cat elfimage > /dev/hda1

I made a mistake. Sorry. This is what I had to do.

dd if=elfImage of=/dev/hda bs=4096 seek=1

This leaves partition tables, mbr, etc. intact.

ron

[Shubhangi Jadhav]

I give the following options in my config file

option BOOT_IDE=1
    option IDE_BOOT_DRIVE=2
    option ONE_TRACK=32
    commandline root=/dev/hda2 console=ttyS0,115200 console=tty0
    option USE_ELF_BOOT=1

Is this correct if I want Linuxbios to directly boot the elfimage?
However when I try to build linuxbios using these options I get an error-
file linux.bin not found. Now why does it look for this file.
    Do I need to specify some payload in the config file. what payload is it?

Regards,
Shubhangi

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]]On Behalf Of ron minnich
Sent: Sunday, April 27, 2003 8:26 AM
To: Shubhangi Jadhav
Cc: Eric W. Biederman; Steve Gehlbach; Deepak Kotian; Adam Agnew;
bendany; [e-mail]
Subject: RE: Using ADLO with Linuxbios

On Sat, 26 Apr 2003, Shubhangi Jadhav wrote:
> cat elfimage > /dev/hda1

I made a mistake. Sorry. This is what I had to do.

dd if=elfImage of=/dev/hda bs=4096 seek=1

This leaves partition tables, mbr, etc. intact.

ron

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

[ron minnich]

On Mon, 28 Apr 2003, Shubhangi Jadhav wrote:
> I give the following options in my config file
>
> option BOOT_IDE=1
>    option IDE_BOOT_DRIVE=2
>    option ONE_TRACK=32
>    commandline root=/dev/hda2 console=ttyS0,115200 console=tty0
>    option USE_ELF_BOOT=1
>
> Is this correct if I want Linuxbios to directly boot the elfimage?
> However when I try to build linuxbios using these options I get an error-
> file linux.bin not found. Now why does it look for this file.
>    Do I need to specify some payload in the config file. what payload is it?

you should look at the sample config files in the source tree. Try looking 
in util/config

ron

[Steve Gehlbach]

Shubhangi Jadhav wrote:
> I give the following options in my config file
>
> option BOOT_IDE=1
>    option IDE_BOOT_DRIVE=2
>    option ONE_TRACK=32
>    commandline root=/dev/hda2 console=ttyS0,115200 console=tty0
>    option USE_ELF_BOOT=1
>
> Is this correct if I want Linuxbios to directly boot the elfimage?
> However when I try to build linuxbios using these options I get an error-
> file linux.bin not found. Now why does it look for this file.
>    Do I need to specify some payload in the config file. what payload is it?

I believe you will see this error if you do not set "linux 
/usr/src/linux" or where ever your linux kernel source tree is.  Put 
this in, and I think this error will go away.

But I should mention that I have never gotten this to boot with 
USE_ELF_BOOT=1, though I am told it should.  It has only worked for me 
using vmlinux.gin.gz, ie, direct loading a non-elf image.

-Steve

[Deepak Kotian]

Good information.

Can someone please stick out the config file content over here for the
following situation,

Case 1:
1.  When LinuxBIOS in flash ROM and image is on compact flash without hdc1.

Case 2:
2. Any sample config file which uses ADLO payload with LinuxBIOS on
FLASHOMS.

Regards
Deepak

----- Original Message -----
From: "Steve Gehlbach" 
To: "Shubhangi Jadhav" 
Cc: "ron minnich" ; "Eric W. Biederman"
; "Deepak Kotian" ; "Adam Agnew"
; "bendany" ;

Sent: Monday, April 28, 2003 9:12 PM
Subject: Re: Using ADLO with Linuxbios
> Shubhangi Jadhav wrote:
> > I give the following options in my config file
> >
> > option BOOT_IDE=1
> > option IDE_BOOT_DRIVE=2
> > option ONE_TRACK=32
> > commandline root=/dev/hda2 console=ttyS0,115200 console=tty0
> > option USE_ELF_BOOT=1
> >
> > Is this correct if I want Linuxbios to directly boot the elfimage?
> > However when I try to build linuxbios using these options I get an

error-
> > file linux.bin not found. Now why does it look for this file.
> > Do I need to specify some payload in the config file. what payload is

it?
> >
>
> I believe you will see this error if you do not set "linux
> /usr/src/linux" or where ever your linux kernel source tree is.  Put
> this in, and I think this error will go away.
>
> But I should mention that I have never gotten this to boot with
> USE_ELF_BOOT=1, though I am told it should.  It has only worked for me
> using vmlinux.gin.gz, ie, direct loading a non-elf image.
>
> -Steve
>
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios

[Deepak Kotian]

Sorry, I meant
> Case 1:
> When LinuxBIOS in flash ROM and image is on compact flash with

/dev/hdc1 block device and no harddisk.
>

----- Original Message -----
From: "Deepak Kotian" 
To: "Steve Gehlbach" ; "Shubhangi Jadhav"

Cc: "ron minnich" ; "Eric W. Biederman"
; "Adam Agnew" ; "bendany"
; 
Sent: Monday, April 28, 2003 11:58 PM
Subject: Re: Using ADLO with Linuxbios
> Good information.
>
> Can someone please stick out the config file content over here for the
> following situation,
>
> Case 1:
> When LinuxBIOS in flash ROM and image is on compact flash without

hdc1.
> Case 2:
> 2. Any sample config file which uses ADLO payload with LinuxBIOS on
> FLASHOMS.
>
> Regards
> Deepak
>
> ----- Original Message -----
> From: "Steve Gehlbach" 
> To: "Shubhangi Jadhav" 
> Cc: "ron minnich" ; "Eric W. Biederman"
> ; "Deepak Kotian" ; "Adam Agnew"
> ; "bendany" ;
>
> Sent: Monday, April 28, 2003 9:12 PM
> Subject: Re: Using ADLO with Linuxbios
> > Shubhangi Jadhav wrote:
> > > I give the following options in my config file
> > >
> > > option BOOT_IDE=1
> > > option IDE_BOOT_DRIVE=2
> > > option ONE_TRACK=32
> > > commandline root=/dev/hda2 console=ttyS0,115200 console=tty0
> > > option USE_ELF_BOOT=1
> > >
> > > Is this correct if I want Linuxbios to directly boot the elfimage?
> > > However when I try to build linuxbios using these options I get an
>
> error-
> > > file linux.bin not found. Now why does it look for this file.
> > > Do I need to specify some payload in the config file. what payload is
>
> it?
> > >
> >
> > I believe you will see this error if you do not set "linux
> > /usr/src/linux" or where ever your linux kernel source tree is.  Put
> > this in, and I think this error will go away.
> >
> > But I should mention that I have never gotten this to boot with
> > USE_ELF_BOOT=1, though I am told it should.  It has only worked for me
> > using vmlinux.gin.gz, ie, direct loading a non-elf image.
> >
> > -Steve
> >
> > Linuxbios mailing list
> > [e-mail]
> > http://www.clustermatic.org/mailman/listinfo/linuxbios
>
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios

[Shubhangi Jadhav]

> I believe you will see this error if you do not set "linux
> /usr/src/linux" or where ever your linux kernel source tree is.  Put
> this in, and I think this error will go away.

Tried it and it got the following error -

make: *** No rule to make target `/usr/src/linux2.4.18-3/vmlinux', needed by
`linux.bin'.  Stop.

Another question, if I'm directly booting an elf image from linuxbios would
I need to set linux in the Config file?

-Shubhangi

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]]On Behalf Of Steve Gehlbach
Sent: Monday, April 28, 2003 9:12 PM
To: Shubhangi Jadhav
Cc: ron minnich; Eric W. Biederman; Deepak Kotian; Adam Agnew; bendany;
[e-mail]
Subject: Re: Using ADLO with Linuxbios

Shubhangi Jadhav wrote:
> I give the following options in my config file
>
> option BOOT_IDE=1
>    option IDE_BOOT_DRIVE=2
>    option ONE_TRACK=32
>    commandline root=/dev/hda2 console=ttyS0,115200 console=tty0
>    option USE_ELF_BOOT=1
>
> Is this correct if I want Linuxbios to directly boot the elfimage?
> However when I try to build linuxbios using these options I get an error-
> file linux.bin not found. Now why does it look for this file.
>    Do I need to specify some payload in the config file. what payload is it?

I believe you will see this error if you do not set "linux
/usr/src/linux" or where ever your linux kernel source tree is.  Put
this in, and I think this error will go away.

But I should mention that I have never gotten this to boot with
USE_ELF_BOOT=1, though I am told it should.  It has only worked for me
using vmlinux.gin.gz, ie, direct loading a non-elf image.

-Steve

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

[ron minnich]

On Tue, 29 Apr 2003, Shubhangi Jadhav wrote:
> > I believe you will see this error if you do not set "linux
> > /usr/src/linux" or where ever your linux kernel source tree is.  Put
> > this in, and I think this error will go away.
>
> Tried it and it got the following error -
>
> make: *** No rule to make target `/usr/src/linux2.4.18-3/vmlinux', needed by
> `linux.bin'.  Stop.

payload /usr/src/linux/arch/i386/boot/bzImage

the 'linux' command is deprecated
> Another question, if I'm directly booting an elf image from linuxbios would
> I need to set linux in the Config file?

payload, and yes you need to do that.

ron

[Shubhangi Jadhav]

> payload /usr/src/linux/arch/i386/boot/bzImage

Can this be the same kernel image from which I created my elf image?

-Shubhangi

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]]On Behalf Of ron minnich
Sent: Tuesday, April 29, 2003 7:48 PM
To: Shubhangi Jadhav
Cc: Steve Gehlbach; Eric W. Biederman; Deepak Kotian; Adam Agnew;
bendany; [e-mail]
Subject: RE: Using ADLO with Linuxbios

On Tue, 29 Apr 2003, Shubhangi Jadhav wrote:
> > I believe you will see this error if you do not set "linux
> > /usr/src/linux" or where ever your linux kernel source tree is.  Put
> > this in, and I think this error will go away.
>
> Tried it and it got the following error -
>
> make: *** No rule to make target `/usr/src/linux2.4.18-3/vmlinux', needed

by
> `linux.bin'.  Stop.

payload /usr/src/linux/arch/i386/boot/bzImage

the 'linux' command is deprecated
> Another question, if I'm directly booting an elf image from linuxbios

would
> I need to set linux in the Config file?

payload, and yes you need to do that.

ron

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

[ron minnich]

On Tue, 29 Apr 2003, Shubhangi Jadhav wrote:
> Can this be the same kernel image from which I created my elf image?

stupid me. Sorry.

you mkelfImage and then use that as the payload.

Memory glitch on my part.

ron

[Deepak Kotian]

I tried this a similar command on a Compact flash IDE after partioning.
Say.
> dd if=elfImage of=/dev/hdc1 bs=4096 seek=1

It said Invalid argument "/dev/hdc1"
Any inputs, must be simple..

Regards
Deepak

----- Original Message -----
From: "ron minnich" 
To: "Shubhangi Jadhav" 
Cc: "Eric W. Biederman" ; "Steve Gehlbach"
; "Deepak Kotian" ; "Adam Agnew"
; "bendany" ;

Sent: Sunday, April 27, 2003 8:25 AM
Subject: RE: Using ADLO with Linuxbios
> On Sat, 26 Apr 2003, Shubhangi Jadhav wrote:
> > cat elfimage > /dev/hda1
>
> I made a mistake. Sorry. This is what I had to do.
>
> dd if=elfImage of=/dev/hda bs=4096 seek=1
>
> This leaves partition tables, mbr, etc. intact.
>
> ron
>
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios

[Steve Gehlbach]

Deepak Kotian wrote:
> I tried this a similar command on a Compact flash IDE after partioning.
> Say.
> > dd if=elfImage of=/dev/hdc1 bs=4096 seek=1
> > --------------------------^^

What Ron used was /dev/hdc, ie, the drive from the beginning, not 
partition 1.  The 4096 and seek=1 skips over the partition table and 
puts the image into the last part of the MBR/partition table area 
overlapping into partition 1.  It's equivalent to seeking 8 sectors from 
the beginning when viewing the disk as linear sector addressing.

I wouldn't do this sort of thing on any drive you care about, easy to 
make typos and wipe out the disk (or another disk if your fingers type 
/dev/hda when your brain says hdc).

-Steve

[Richard Smith]

Steve Gehlbach wrote:
> > > dd if=elfImage of=/dev/hdc1 bs=4096 seek=1
> > > --------------------------^^
>
> What Ron used was /dev/hdc, ie, the drive from the beginning, not 
> partition 1.  The 4096 and seek=1 skips over the partition table and 
> puts the image into the last part of the MBR/partition table area

On my system if I add the seek option to dd it whines about /dev/hde 
being an invalid argument as well so I don't think its the partition 
number thats causing the issue.

'dd if=elfimage of=/dev/hde bs=4096 seek=1'

still generates and Invalid argument but appears to work anyway as I get 
the proper ammount of records in/out and the CF boots.

[ron minnich]

On Mon, 28 Apr 2003, Richard Smith wrote:
> On my system if I add the seek option to dd it whines about /dev/hde 
> being an invalid argument as well so I don't think its the partition 
> number thats causing the issue.
>
> 'dd if=elfimage of=/dev/hde bs=4096 seek=1'

I've never had that happen. Weird.

ron

[Shubhangi Jadhav]

Hi,

dd if=elfimage of=/dev/hdc bs=4096 seek=1
    gives me an error "/dev/hdc invalid argument".

But "dd if=elfimage of=/dev/hdc" works as in it shows me the in/out
records. However this is overwriting the partition table. when I do a
    fdisk -l /dev/hdc
it says "disk /dev/hdc doesn't contain a valid partition table"
    Any suggestions on what could be done??

Regards,
Shubhangi

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]]On Behalf Of ron minnich
Sent: Tuesday, April 29, 2003 2:00 AM
To: Richard Smith
Cc: [e-mail]
Subject: Re: Using ADLO with Linuxbios

On Mon, 28 Apr 2003, Richard Smith wrote:
> On my system if I add the seek option to dd it whines about /dev/hde
> being an invalid argument as well so I don't think its the partition
> number thats causing the issue.
>
> 'dd if=elfimage of=/dev/hde bs=4096 seek=1'

I've never had that happen. Weird.

ron

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

[ron minnich]

On Tue, 29 Apr 2003, Shubhangi Jadhav wrote:
> dd if=elfimage of=/dev/hdc bs=4096 seek=1
>    gives me an error "/dev/hdc invalid argument".

run it under strace and find the failing system call. Then let me know.

ron

[Shubhangi Jadhav]

Hi,

I got dd working for my CF, it was the buffer misalignment problem with
ext2. Now with ext3 it works.
    But I still have problem with Linuxbios,it detects the CF now but still
gives me the error:		Cannot Load ELF Image

Regards,
Shubhangi

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]]On Behalf Of Shubhangi Jadhav
Sent: Tuesday, April 29, 2003 5:52 PM
To: ron minnich; Richard Smith
Cc: [e-mail]
Subject: RE: Using ADLO with Linuxbios

Hi,

dd if=elfimage of=/dev/hdc bs=4096 seek=1
    gives me an error "/dev/hdc invalid argument".

But "dd if=elfimage of=/dev/hdc" works as in it shows me the in/out
records. However this is overwriting the partition table. when I do a
    fdisk -l /dev/hdc
it says "disk /dev/hdc doesn't contain a valid partition table"
    Any suggestions on what could be done??

Regards,
Shubhangi

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]]On Behalf Of ron minnich
Sent: Tuesday, April 29, 2003 2:00 AM
To: Richard Smith
Cc: [e-mail]
Subject: Re: Using ADLO with Linuxbios

On Mon, 28 Apr 2003, Richard Smith wrote:
> On my system if I add the seek option to dd it whines about /dev/hde
> being an invalid argument as well so I don't think its the partition
> number thats causing the issue.
>
> 'dd if=elfimage of=/dev/hde bs=4096 seek=1'

I've never had that happen. Weird.

ron

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

[Shubhangi Jadhav]

> But I still have problem with Linuxbios,it detects the CF now but still
> gives me the error:		Cannot Load ELF Image

I get the following messages :

**********************log**************************************************
I am now initializing the ide system
UQNAUT MIFERABLLcl1t 001
init_drive sectors_per_track=[63], num_heads=[16], num_cylinders=[16383]
IDE0 16/16383/63 cap: 0f00

init_drive sectors_per_track=[0], num_heads=[0], num_cylinders=[0]
OTHSBI AHTCN0F23BM A
init_drive sectors_per_track=[32], num_heads=[4], num_cylinders=[496]
IDE2 4/496/32 cap: 0200

init_drive sectors_per_track=[0], num_heads=[0], num_cylinders=[0]
Initialized controller...
IDE_BOOT_DRIVE = 2
.ide_read_sector drive[2], buffer[0000b820], block[00000020], offset[0],
n_bytes
[512]
ide_read_sector block(00000020) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[20], block[      20]
.ide_read_sector drive[2], buffer[0000b820], block[00000021], offset[0],
n_bytes
[512]
ide_read_sector block(00000021) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[21], block[      21]
.ide_read_sector drive[2], buffer[0000b820], block[00000022], offset[0],
n_bytes
[512]
ide_read_sector block(00000022) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[22], block[      22]
.ide_read_sector drive[2], buffer[0000b820], block[00000023], offset[0],
n_bytes
[512]
ide_read_sector block(00000023) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[23], block[      23]
.ide_read_sector drive[2], buffer[0000b820], block[00000024], offset[0],
n_bytes
[512]
ide_read_sector block(00000024) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[24], block[      24]
.ide_read_sector drive[2], buffer[0000b820], block[00000025], offset[0],
n_bytes
[512]
ide_read_sector block(00000025) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[25], block[      25]
.ide_read_sector drive[2], buffer[0000b820], block[00000026], offset[0],
n_bytes
[512]
ide_read_sector block(00000026) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[26], block[      26]
.ide_read_sector drive[2], buffer[0000b820], block[00000027], offset[0],
n_bytes
[512]
ide_read_sector block(00000027) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[27], block[      27]
.ide_read_sector drive[2], buffer[0000b820], block[00000028], offset[0],
n_bytes
[512]
ide_read_sector block(00000028) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[28], block[      28]
.ide_read_sector drive[2], buffer[0000b820], block[00000029], offset[0],
n_bytes
[512]
ide_read_sector block(00000029) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[29], block[      29]
.ide_read_sector drive[2], buffer[0000b820], block[0000002a], offset[0],
n_bytes
[512]
ide_read_sector block(0000002a) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[2a], block[      2a]
.ide_read_sector drive[2], buffer[0000b820], block[0000002b], offset[0],
n_bytes
[512]
ide_read_sector block(0000002b) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[2b], block[      2b]
.ide_read_sector drive[2], buffer[0000b820], block[0000002c], offset[0],
n_bytes
[512]
ide_read_sector block(0000002c) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[2c], block[      2c]
.ide_read_sector drive[2], buffer[0000b820], block[0000002d], offset[0],
n_bytes
[512]
ide_read_sector block(0000002d) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[2d], block[      2d]
.ide_read_sector drive[2], buffer[0000b820], block[0000002e], offset[0],
n_bytes
[512]
ide_read_sector block(0000002e) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[2e], block[      2e]
.ide_read_sector drive[2], buffer[0000b820], block[0000002f], offset[0],
n_bytes
[512]
ide_read_sector block(0000002f) to addr(0000b820)ide_read_sector LBA:
drivehead[e0], cylinder[0000], sector[2f], block[      2f]
header_offset is -1
Cannot Load ELF Image
*****************************************************************

-Shubhangi

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]]On Behalf Of Shubhangi Jadhav
Sent: Tuesday, April 29, 2003 7:30 PM
To: ron minnich; Richard Smith
Cc: [e-mail]
Subject: RE: Using ADLO with Linuxbios

Hi,

I got dd working for my CF, it was the buffer misalignment problem with
ext2. Now with ext3 it works.
    But I still have problem with Linuxbios,it detects the CF now but still
gives me the error:		Cannot Load ELF Image

Regards,
Shubhangi

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]]On Behalf Of Shubhangi Jadhav
Sent: Tuesday, April 29, 2003 5:52 PM
To: ron minnich; Richard Smith
Cc: [e-mail]
Subject: RE: Using ADLO with Linuxbios

Hi,

dd if=elfimage of=/dev/hdc bs=4096 seek=1
    gives me an error "/dev/hdc invalid argument".

But "dd if=elfimage of=/dev/hdc" works as in it shows me the in/out
records. However this is overwriting the partition table. when I do a
    fdisk -l /dev/hdc
it says "disk /dev/hdc doesn't contain a valid partition table"
    Any suggestions on what could be done??

Regards,
Shubhangi

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]]On Behalf Of ron minnich
Sent: Tuesday, April 29, 2003 2:00 AM
To: Richard Smith
Cc: [e-mail]
Subject: Re: Using ADLO with Linuxbios

On Mon, 28 Apr 2003, Richard Smith wrote:
> On my system if I add the seek option to dd it whines about /dev/hde
> being an invalid argument as well so I don't think its the partition
> number thats causing the issue.
>
> 'dd if=elfimage of=/dev/hde bs=4096 seek=1'

I've never had that happen. Weird.

ron

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

[ron minnich]

On Mon, 28 Apr 2003, Steve Gehlbach wrote:
> I wouldn't do this sort of thing on any drive you care about, easy to 
> make typos and wipe out the disk (or another disk if your fingers type 
> /dev/hda when your brain says hdc).

ah, yes, I've done that.

:-)

ron