Now I 'fused ... what is etherboot? that payload "ebi" file, is that just a driver ... or is it an ipl for that card? or and ipl for the cpu, with a driver for that card?
hmmm ... why would you try etherboot b4 DoC ? Wouldn't DoC be less prone to problems than getting memory and networking running? ----- Original Message ----- >From: "Ronald G Minnich" <[EMAIL PROTECTED]> >To: "Ian" <[EMAIL PROTECTED]> >Subject: Re: RAM Init >Date: Wed, 20 Feb 2002 10:07:48 -0700 > > On Wed, 20 Feb 2002, Ian wrote: > > > In that directory, however, there is a (mainboard/asus/cua/) there is > > "config.DoC" that says to set "docipl" to; northbridge/acer/m1631/ipl.S > > > > Which of these is the right one for the m1631? (there are a few diffs > > in there) > > asus in their infinite wisdom did some things differently than a basic > m1631-based card would do. So you have to use the IPL from the mainboard > directory for the asus cua. > > Here is a "known good" for the CUA for etherboot: > > # Sample config file for ASUS CUA with DoC Millennium (as root) > target asus_cua.etherboot > > # Asus CUA > mainboard asus/cua > > # Enable Serial Console for debugging > option SERIAL_CONSOLE=1 > > # Enable MicroCode update and L2 Cache init for PII and PIII > option UPDATE_MICROCODE=1 > option CONFIGURE_L2_CACHE=1 > > # use DOC MIL > option USE_DOC_MIL=1 > docipl mainboard/asus/cua/ipl.S > > # Use the internal VGA frame buffer device > # option HAVE_FRAMEBUFFER > > # we don't have PIRQ tables yet. > option HAVE_PIRQ_TABLE=1 > > # Path to your kernel (vmlinux) > option USE_ELF_BOOT=1 > payload ../rtl8139.ebi > >
