Hello Mark !!


 My EPIA finally works. You are right!
 I saw on my EPIA what is the capture file attached on last mail.
 So as far, I have used mkelfImage-2.0, but it didn't work. By the  way, yesterday I just used mkelfImage-1.16 which is the same as you.
Then it worked. What's the problem ?
I don't know the reason why it differs. I am about to find it out.
And let me know it , if you know.

Thank you for your help.


-----Original Message-----
From: Mark Wilkinson [mailto:mwilkinson@ndirect.co.uk]
Sent: Sunday, March 23, 2003 7:07 PM
To: NEWBELL7@magicn.com
Cc: linuxbios@clustermatic.org
Subject: Re: [epia] Unknown bootloader class

 

Hi HyungJong,

       I've finally managed to get to the point where I can give the configs a try

(one with -DTAGGED_IMAGE enabled, one without)

 

in both cases, the boot sequence reported that the bootloader class was

unknown (Type = 0x00000000), but the system then went on to boot the loaded

kernel quite happily (see attached capture file)

 

I've also attached the romimages as well

file :-

lb+eb-elf = linuxbios + etherboot (elf images only)

lb+eb-tag+elf = linuxbios + etherboot (tagged and elf images)

 

if you still don't get any further, I think it time to look at the kernel

configuration once again.... the command line you specified did have the

correct disk partition listed as root didn't it ? I seem to recall that you'd

configured /dev/hda3 as the root partition, does this match with where /

really is ?

 

regards

Mark Wilkinson