Re: [epia] Unknown bootloader class

2003-03-31 Thread Eric W. Biederman
Jarmo Tulonen [EMAIL PROTECTED] writes: Hello If this problem is not solved yet, I would suggest trying a newer mkelfImage. I have been using version 2.2 from ftp://ftp.lnxi.com/pub/src/mkelfImage/ and that one works fine (I'm also using an Epia card.) I tried with the version in the

Re: [epia] Unknown bootloader class

2003-03-24 Thread Russell Gower
As for you second question, I'm not sure about the values in raminit being optimised. I think they are configured to 'work' for 64Mbytes of memory - any more just get's ignored. For my 128Mb system, I've changed to the following 5a = 0x08 5b-5f,56,57 = 0x10 as these are what

Re: [epia] Unknown bootloader class

2003-03-24 Thread Andrew Ip
I could'nt get any more than 64mb of ram recognised using the raminit.inc approach, and even that 64mb was showing lots of errors. So i reworked things to uses the generic spd stuff. I did intend on producing a patch to send in to Andrew IP, but i ran out of time then my linuxbios got out of

: [epia] Unknown bootloader class [mkelfImage]

2003-03-24 Thread NEWBELL7
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:[EMAIL PROTECTED] Sent: Sunday, March 23, 2003 7:07 PMTo: [EMAIL PROTECTED]Cc: [EMAIL PROTECTED]Subject: Re: [epia] Unknown

Re: [epia] Unknown bootloader class

2003-03-23 Thread Mark Wilkinson
Hello HyungJong Thanks for the config information. I can only see one difference between your config and my own. That is the CFLAGS32+= -DASK_BOOT=3 -DANS_DEFAULT=ANS_NETWORK line, which I don't have enabled, but I can't see that being the cause of your problem. Just for Information,

: [epia] Unknown bootloader class [mkelfImage]

2003-03-21 Thread NEWBELL7
As Mr. Mark and Mr. Andrew said, I got new kernel wich 2.4.19 from cwlinux.( kernel-source-linuxbios-2.4.19-CWLINUX_4.i386.rpm and also official linux-2.4.18.tar.gz )and, select C3 as the processor type and disabled SMP.Then I setPCI access to DIRECT, network card to VIA Rhine.But , Unknown

Re: [epia] Unknown bootloader class

2003-03-21 Thread Mark Wilkinson
Hello HyungJong, I'm beginning to wonder if the problem you are seeing lies with the configuration of etherboot you've used. My thinking is that etherboot thinks it's executing a different type of image (ie FreeBSD, Multiboot, etc) rather than an ELF image, and is thus passing some different

: [epia] Unknown bootloader class [mkelfImage]

2003-03-21 Thread NEWBELL7
2=# not needed # Support for PXE emulation. Works only with FreeBSD to load the kernel# via pxeboot, use only with DOWNLOAD_PROTO_NFS#CFLAGS32+= -DFREEBSD_PXEEMU -Original Message-From: Mark Wilkinson [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 9:31 PMTo: [EMAIL PROTECTED]; [EMAI

Re: [epia] Unknown bootloader class

2003-03-20 Thread Mark Wilkinson
Hello HyungJong Thanks for the configuration information. I'd first suggest using a more recent version of the kernel (2.4.18 or higher) as these have support for the Via C3 processor. Second, I'd also suggest configuring the kernel with the following options set/unset. If you go for a

Re: [epia] Unknown bootloader class

2003-03-20 Thread Andrew Ip
You can also try to set CPU to i386 or 586 first. # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set CONFIG_MPENTIUMIII=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set #

Re: [epia] Unknown bootloader class

2003-03-19 Thread Mark Wilkinson
Title: Message Hello ! looking through the debug messages you've supplied, the problem seems to be with the image that you've loaded. The linuxbios + etherboot seems to have worked fine - Etherboot hands over to your image just after the 'rhine disable' message. Have you tried booting