I've got etherboot loading now.
I took a bzImage and turned it into a elfimage with
mkelfimage bzImage elfimage
using mkelfimage 2.5
then stuck that on my CF in the first partition ie 'cat elfimage > /dev/hde1' where hde is the pcmcia mount of my CF
Stick it in my target and boot.
I get:
< linux bios stuff snipped>
Etherboot 5.1.8 (GPL) Tagged ELF for [IDE] Relocating _text from: [00023d20,00032e30) to [07ff0ef0,08000000) Probing pci disk... [IDE]disk-1 7872k cap: 0200 Searching for image... ................................<abort> Probing pci disk... [IDE]Probing isa disk... <sleep> Probing pci disk... [IDE]disk0 7872k cap: 0200 Searching for image... ................................<abort> Probing pci disk... [IDE]Probing isa disk... <sleep> Probing pci disk... [IDE]disk1 7872k cap: 0200 Searching for image... ................................<abort> Probing pci disk... [IDE]Probing isa disk... <sleep>
And it just goes on and on checking different disks
Did I miss something? Is Tagged ELF different from the elf image that I created with mkelfimage?
PCMCIA mount? Etherboot wont look at pcmcia devices. If its going to find a compact flash card, it will be because there's a compact flash on IDE adapter. Then it will see it as a hard disk.
On Fri, 25 Apr 2003, Richard Smith wrote:
I've got etherboot loading now.
I took a bzImage and turned it into a elfimage with
mkelfimage bzImage elfimage
using mkelfimage 2.5
then stuck that on my CF in the first partition ie 'cat elfimage > /dev/hde1' where hde is the pcmcia mount of my CF
Stick it in my target and boot.
I get:
< linux bios stuff snipped>
Etherboot 5.1.8 (GPL) Tagged ELF for [IDE] Relocating _text from: [00023d20,00032e30) to [07ff0ef0,08000000) Probing pci disk... [IDE]disk-1 7872k cap: 0200 Searching for image... ................................<abort> Probing pci disk... [IDE]Probing isa disk...
<sleep> Probing pci disk... [IDE]disk0 7872k cap: 0200 Searching for image... ................................<abort> Probing pci disk... [IDE]Probing isa disk... <sleep> Probing pci disk... [IDE]disk1 7872k cap: 0200 Searching for image... ................................<abort> Probing pci disk... [IDE]Probing isa disk... <sleep>
And it just goes on and on checking different disks
Did I miss something? Is Tagged ELF different from the elf image that I created with mkelfimage?
-- Richard A. Smith rsmith@bitworks.com
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Richard Smith rsmith@bitworks.com writes:
I've got etherboot loading now.
I took a bzImage and turned it into a elfimage with
mkelfimage bzImage elfimage
using mkelfimage 2.5
Yeah. At least someone does not have broken binutils :)
then stuck that on my CF in the first partition ie 'cat elfimage > /dev/hde1' where hde is the pcmcia mount of my CF
Stick it in my target and boot.
I get:
< linux bios stuff snipped>
Etherboot 5.1.8 (GPL) Tagged ELF for [IDE] Relocating _text from: [00023d20,00032e30) to [07ff0ef0,08000000) Probing pci disk... [IDE]disk-1 7872k cap: 0200 Searching for image... ................................<abort> Probing pci disk... [IDE]Probing isa disk...
<sleep> Probing pci disk... [IDE]disk0 7872k cap: 0200 Searching for image... ................................<abort> Probing pci disk... [IDE]Probing isa disk... <sleep> Probing pci disk... [IDE]disk1 7872k cap: 0200 Searching for image... ................................<abort> Probing pci disk... [IDE]Probing isa disk... <sleep>
And it just goes on and on checking different disks
Did I miss something? Is Tagged ELF different from the elf image that I created with mkelfimage?
Nope. the file format is right.
Etherboot just works the way the LinuxBIOS code originally did.
In particular it scans the first 8K of disk for an ELF header. This means you don't have to be at the absolute start of the disk for your ELF image you do need to be close.
Think of what is happening as a super master boot record instead of a stupid bootloader. As there is a very strong reluctance to upgrade firmware I try to make the as simple as possible while still being powerful enough to be useful. Hopefully at some point there a bootloader I can read off of the disk.
With the appropriate tools it is possible to force your first partition early in the disk. By default the first partition is often aligned on a cylinder boundary, which is probably what you are running into.
The fact the IDE driver is reading your disk and not having problems is good.
Eric
Adam Agnew agnew@cs.umd.edu writes:
PCMCIA mount? Etherboot wont look at pcmcia devices. If its going to find a compact flash card, it will be because there's a compact flash on IDE adapter. Then it will see it as a hard disk.
You may have a point. Richard how many IDE disks do you have?
I guess I am wondering if it looks like the correct disk is being checked.
I still favor the partition is to late on the disk theory but, not checking the CF works as well.
For a pure test case it is possible to just dd the ELF image onto the start of the disk. If you don't need partitions. That is the way Ron is currently using the code.
Eric
Eric W. Biederman wrote:
PCMCIA mount?
Etherboot wont look at pcmcia devices. If its going to find a compact flash card, it will be because there's a compact flash on IDE adapter. Then it will see it as a hard disk.
You may have a point. Richard how many IDE disks do you have?
Slight miscommunication there. The CF is pcmcia mounted on my _developement_ system. I was just trying to clarify why my disk mount was /dev/hde for the 'cat >' rather than hda. Looks like I just confused things further. :(
On my _target_ device the CF is a connector on the PCB. Its hda and the only IDE device I have.
I still favor the partition is to late on the disk theory but, not checking the CF works as well.
For a pure test case it is possible to just dd the ELF image onto the start of the disk. If you don't need partitions. That is the way Ron is currently using the code.
Thanks I'll give that a try. I also see just where fdisk put the 1st partition.
Richard Smith wrote:
For a pure test case it is possible to just dd the ELF image onto the start of the disk. If you don't need partitions. That is the way Ron is currently using the code.
Thanks I'll give that a try. I also see just where fdisk put the 1st partition.
Ok... I'm booting now. Erik your hunch was correct. /dev/hda1 must have been outside the 8k section. I'm not really sure how to read fdisk's info and translate it into a physical offset on the disk but going directly to /dev/hda worked.
Although Ron's dd command gave me an "Invalid argument /dev/hde" it appears to have written the data on to the disk as I can boot and the partitition table is still intact.
Thanks for all the help.
Richard Smith rsmith@bitworks.com writes:
Richard Smith wrote:
For a pure test case it is possible to just dd the ELF image onto the start of the disk. If you don't need partitions. That is the way Ron is currently
using the code.
Thanks I'll give that a try. I also see just where fdisk put the 1st partition.
Ok... I'm booting now. Erik your hunch was correct. /dev/hda1 must have been outside the 8k section. I'm not really sure how to read fdisk's info and translate it into a physical offset on the disk but going directly to /dev/hda worked.
In the normal case just change the units to sectors. The 'u' command. A single sector is 512 bytes or 1/2 KiloByte.
Although Ron's dd command gave me an "Invalid argument /dev/hde" it appears to have written the data on to the disk as I can boot and the partitition table is still intact.
Good.
Eric
-
Adam Agnew -
ebiederman＠lnxi.com -
Richard Smith