On Sat, 10 Mar 2007 21:53:30 +0100, Paul de Weerd <[EMAIL PROTECTED]> wrote:
> On Sat, Mar 10, 2007 at 02:24:13PM -0500, Gordon Turner wrote:
> | --SNIP from biosboot--
> | ERR R Read error. The BIOS returned an error indication when
> biosboot
> | attempted to read a disk sector. This might be any media
> error,
> | including bad sectors (common on floppy disks), and
> invalid
> sec-
> | tors (can occur with bad geometry translations).
> | --SNIP from biosboot--
>
> I'm not sure, but it looks like you missed this part, may be of
> significance :
>
>> If this error occurs during an LBA boot (no `;' after
>> ``Loading''), then a CHS boot may succeed. To do this, you
>> should reboot, then hold down either Shift key before biosboot
>> starts. You should see a `!' before ``Loading'' as confirmation
>> that your override was accepted.
The rest of the page reads:
... If biosboot detects this, it will
force itself to use CHS calls, ignoring any LBA capability. This will of
course prevent booting if /boot lies above the 8 GB CHS limit. There is
an exported symbol ``force_chs'' of type u_int8_t which may be set to 1
to force CHS reads always. (However, no tool is currently provided to
set this flag.)
I don't know if this is an option for me, the soekris box that I am using does
not have a keyboard I can use to hold the shift key down on :-)
So the comment about "no tool" seems to suggest that I am unable to set this
option on this piece of hardware any other way.
The things that puzzles me the most is this, with the previous 128mb cards, the
soekris reported different CHS values then disklabel run on the usb-cf adapter.
Using the values from the soekris device to create the image provided a
bootable image. The new 512mb cards have the same values in both the usb-cf
reader and the soekris device, yet using those values do not yield a working
image.
I am not sure what other things I can tweak, can anyone throw me a bone? :-)
Gord Turner.
