It has a problem getting to flash, but it actually got worse. It doesn't see the flash disk at all in this version.
To sum up: fallback + rc4.eb5 -- finds disk, boots it automatically normal + rc4.eb5 -- type 'D' to it, then it finds disk and boots normal + rc5 -- never finds the disk, although BBOT_FIRST is to to BOOT_DISK
I bet there's some other config thing I've missed.
ron
Ronald G Minnich rminnich@lanl.gov writes:
It has a problem getting to flash, but it actually got worse. It doesn't see the flash disk at all in this version.
To sum up: fallback + rc4.eb5 -- finds disk, boots it automatically normal + rc4.eb5 -- type 'D' to it, then it finds disk and boots normal + rc5 -- never finds the disk, although BBOT_FIRST is to to BOOT_DISK
I bet there's some other config thing I've missed.
make ide_disk.elf Or in the normal case of wanting the nic driver as well. make eepro100--ide_disk.nrv2belf (nrv2b is the upx compression algorithm)
Oops I forget to hit send yesterday...
Eric
On 24 Oct 2002, Eric W. Biederman wrote:
make ide_disk.elf Or in the normal case of wanting the nic driver as well. make eepro100--ide_disk.nrv2belf (nrv2b is the upx compression algorithm)
no target like that exists in the latest cvs for the 5.1 tree.
Also, it seems to me that if I set up BOOT_xyz to be BOOT_DISK, that stuff should get turned on, so that the Principle of Least Surprise is honored.
ron ron
Ronald G Minnich rminnich@lanl.gov writes:
On 24 Oct 2002, Eric W. Biederman wrote:
make ide_disk.elf Or in the normal case of wanting the nic driver as well. make eepro100--ide_disk.nrv2belf (nrv2b is the upx compression algorithm)
no target like that exists in the latest cvs for the 5.1 tree.
Try it. It is there.
Also, it seems to me that if I set up BOOT_xyz to be BOOT_DISK, that stuff should get turned on, so that the Principle of Least Surprise is honored.
It is honoured you don't have the IDE driver compiled in.
Eric
On 28 Oct 2002, Eric W. Biederman wrote:
make ide_disk.elf Or in the normal case of wanting the nic driver as well. make eepro100--ide_disk.nrv2belf (nrv2b is the upx compression algorithm)
no target like that exists in the latest cvs for the 5.1 tree.
Try it. It is there.
[rminnich@brain src]$ pwd /home/rminnich/src/etherboot/etherboot-5.1/src [rminnich@brain src]$ make ide_disk.elf make: *** No rule to make target `ide_disk.elf'. Stop. [rminnich@brain src]$ make eepro100--ide_disk.nrv2belf make: *** No rule to make target `eepro100--ide_disk.nrv2belf'. Stop. [rminnich@brain src]$
??
Also, it seems to me that if I set up BOOT_xyz to be BOOT_DISK, that stuff should get turned on, so that the Principle of Least Surprise is honored.
It is honoured you don't have the IDE driver compiled in.
I'll look at how to do this, but IMHO if you set BOOT_DISK it should force the IDE driver to get compiled in. Is there a reason not to do this (i.e you're going to support all kinds of non-IDE disks).
ron
Ronald G Minnich rminnich@lanl.gov writes:
On 28 Oct 2002, Eric W. Biederman wrote:
make ide_disk.elf Or in the normal case of wanting the nic driver as well. make eepro100--ide_disk.nrv2belf (nrv2b is the upx compression algorithm)
no target like that exists in the latest cvs for the 5.1 tree.
Try it. It is there.
[rminnich@brain src]$ pwd /home/rminnich/src/etherboot/etherboot-5.1/src [rminnich@brain src]$ make ide_disk.elf make: *** No rule to make target `ide_disk.elf'. Stop.
Hmm. Very strange. I just did a fresh check out and it worked without error.
Oh, duh. The difference is: make bin32/ide_disk.elf ^^^^^^
[rminnich@brain src]$ make eepro100--ide_disk.nrv2belf make: *** No rule to make target `eepro100--ide_disk.nrv2belf'. Stop. [rminnich@brain src]$
Do make bin32/eepro100--ide_disk.nrv2belf
Should also work.
Also, it seems to me that if I set up BOOT_xyz to be BOOT_DISK, that stuff should get turned on, so that the Principle of Least Surprise is honored.
It is honoured you don't have the IDE driver compiled in.
I'll look at how to do this, but IMHO if you set BOOT_DISK it should force the IDE driver to get compiled in. Is there a reason not to do this (i.e you're going to support all kinds of non-IDE disks).
The BOOT_FIRST etc options just control the boot order.
And yes the code structure is such that putting in a non-ide disk driver should be straight forward. I just have not done anything except the floppy driver yet. The driver structure for disks, and nics is the same there is just a different tag indicating which kind of device they are. There is a distinction made between floppies and ide disk in the boot order code simply because you normall want to distiguish between them. The code to boot from disk is the same in both cases.
I do admit having a better way to specify drivers than: make bin32/driver1--driver2--driver3--driver4--driver5--driver6--driver7.elf make bin32/etherboot.elf would be nice, but no one has implemented anything better yet.
Eric
On 28 Oct 2002, Eric W. Biederman wrote:
Oh, duh. The difference is: make bin32/ide_disk.elf
Sorry! Should have tried that :-(
thanks
ron
-
ebiederman＠lnxi.com -
Ronald G Minnich