Finally got it to work. I needed to tell the BIOS how to detect the CF 
Card and it boots up fine now. It was on Auto and I changed it to CHS.

sai

Chet Harvey wrote:
> your last sentence is probably the culprit....you see a lot of those errors 
> when one manufacturer see the same drive but uses different geometries...try 
> to see if ibase lets you manually select the geometry and set it based on what 
> asus thinks it is.
> 
> Chet Harvey
> Pitbull Technologies <http://www.pittech.com/> 
> Protecting your Digital Assets
> 703.407.7311
> 
> 
> Quoting sai <list at ebs dot net dot pk>:
> 
> 
>>Ok, this is a good one.
>>
>>Got a m0n0wall generic PC image on my PC and wrote it to a CF card 
>>(TwinMOS, 64 MB). I used an adaptor connected to the USB connector on 
>>the (Asus) motherboard. Had some problems writing to the CF card but 
>>managed it (tried Manuel's utility off WinXP and also dd off Knoppix and 
>>one of them worked).
>>
>>  I am using a new (an previously untested) board (ibase796, Taiwan) 
>>with the CF card. It boots up but then I get an error:
>>"hard error reading fsbn 125944 of 0-3 (ad0 bn 125944 cn983 an155n0 
>>std0:61mb"
>>
>>and then I get the m0n0 error "cannot find configure.xml".
>>
>>I take the CF card back to the original PC (where I wrote the image) and 
>>boot from that (ie boot from the usb adaptor for the CF card). The Card 
>>works fine. I get the m0n0 console.
>>
>>I try this several times - even tried with another ibase board in case 
>>the first one was damaged - but same result.
>>
>> From reading the mailing list I know that a lot of people get the 
>>configure.xml error when booting from  CF card.  Why does the card not 
>>work on the ibase board when it works on the Asus board?
>>
>>The freeBSD mailing lists seem to indicate that the 'hard error' means 
>>some sort of hard disk failure. Does that mean that the ibase bios is 
>>detecting the CF card wrong? Something to do with geometry?
>>
>>sai
>>
> 
> 
>