RE: EPIA-M startup times

[M. Renee Hopkins]

OK, I finally timed my ME-6000.  It takes about 20 seconds to get to the 
init scripts.  Even though I have the framebuffer support compiled into 
2.6.4, the kernel doesn't ever see the vesafb device.  Although the same 
kernel sees it from award bios boot.

I'm using Linuxbios V1, cvs 050504, filo 4.1, 2.6.4 with patches.

Is it possible something isn't set right in filo or LB?  I have

option HAVE_FRAMEBUFFER=1 in linuxbios config.

Any help is appreciated.  Thanks to all who contributed.

M.R.
> From: "Dmitry Borisov" 
> To: 
> Subject: EPIA-M startup times
> Date: Mon, 26 Apr 2004 19:34:00 -0700
>
> Guys,
> Just wanted to have your estimate about startup times for EPIA-M mobo.
> ATM it takes about 9 secs to go to payload. 7 secs to go to splash. Which 
> seems to be really high values.
> Does anyone can say what it would be if everything is "perfect" ?
> How much time at minimum the BIOS can take assuming RAM, VGA and PCI 
> initialized properly ?
>
> If the answer would be 4 secs in ideal case, I'll invest some time to 
> tighten it up... If 9 secs is a minimum, then...
>
> Any suggestions ?
> Dmitry/

_________________________________________________________________
Check out the coupons and bargains on MSN Offers! http://youroffers.msn.com

EPIA-M startup times

[John Laur]

If you have VGA correctly working with LinuxBIOS (Ie you see the
linuxbios logo on startup), then you have VGA working as best it does
with LinuxBIOS.

Then you can worry about the kernel. VESA Framebuffer does not work with
EPIA-M as the VGA bios doesn't initialize the video card up to where
vesafb can take over. You have to use viafb (part of the -epia patchset)
to get video on the console. Make sure you have it compiled into the
kernel and not as a module. Make sure vesafb is NOT compiled in either,
otherwise you'll need some commandline trickery to make it work. Also,
viafb doesn't work with bootsplash in silent mode on kernel 2.4 if you
are using that. I have not tested with kernel 2.6.

John
> -----Original Message-----
> From: [e-mail] [mailto:linuxbios-
> [e-mail]] On Behalf Of M. Renee Hopkins
> Sent: Thursday, May 06, 2004 4:58 PM
> To: [e-mail]; [e-mail]
> Subject: RE: EPIA-M startup times
>
> OK, I finally timed my ME-6000.  It takes about 20 seconds to get to

the
> init scripts.  Even though I have the framebuffer support compiled

into
> 2.6.4, the kernel doesn't ever see the vesafb device.  Although the

same
> kernel sees it from award bios boot.
>
> I'm using Linuxbios V1, cvs 050504, filo 4.1, 2.6.4 with patches.
>
> Is it possible something isn't set right in filo or LB?  I have
>
> option HAVE_FRAMEBUFFER=1 in linuxbios config.
>
> Any help is appreciated.  Thanks to all who contributed.
>
> M.R.
> > From: "Dmitry Borisov" 
> > To: 
> > Subject: EPIA-M startup times
> > Date: Mon, 26 Apr 2004 19:34:00 -0700
> >
> > Guys,
> > Just wanted to have your estimate about startup times for EPIA-M

mobo.
> > ATM it takes about 9 secs to go to payload. 7 secs to go to splash.

Which
> > seems to be really high values.
> > Does anyone can say what it would be if everything is "perfect" ?
> > How much time at minimum the BIOS can take assuming RAM, VGA and PCI
> > initialized properly ?
> >
> > If the answer would be 4 secs in ideal case, I'll invest some time to
> > tighten it up... If 9 secs is a minimum, then...
> >
> > Any suggestions ?
> > Dmitry/
>
> Check out the coupons and bargains on MSN Offers!
> http://youroffers.msn.com
>
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios

EPIA-M startup times

[Ignacio Verona]

20 sec to init scripts?? Isn't it very high times? I though using linuxbios I 
could get faster boot times...

El Jueves, 13 de Mayo de 2004 18:46, John Laur escribió:
> If you have VGA correctly working with LinuxBIOS (Ie you see the
> linuxbios logo on startup), then you have VGA working as best it does
> with LinuxBIOS.
>
> Then you can worry about the kernel. VESA Framebuffer does not work with
> EPIA-M as the VGA bios doesn't initialize the video card up to where
> vesafb can take over. You have to use viafb (part of the -epia patchset)
> to get video on the console. Make sure you have it compiled into the
> kernel and not as a module. Make sure vesafb is NOT compiled in either,
> otherwise you'll need some commandline trickery to make it work. Also,
> viafb doesn't work with bootsplash in silent mode on kernel 2.4 if you
> are using that. I have not tested with kernel 2.6.
>
> John
> > -----Original Message-----
> > From: [e-mail] [mailto:linuxbios-
> > [e-mail]] On Behalf Of M. Renee Hopkins
> > Sent: Thursday, May 06, 2004 4:58 PM
> > To: [e-mail]; [e-mail]
> > Subject: RE: EPIA-M startup times
> >
> > OK, I finally timed my ME-6000.  It takes about 20 seconds to get to
>
> the
> > init scripts.  Even though I have the framebuffer support compiled
>
> into
> > 2.6.4, the kernel doesn't ever see the vesafb device.  Although the
>
> same
> > kernel sees it from award bios boot.
> >
> > I'm using Linuxbios V1, cvs 050504, filo 4.1, 2.6.4 with patches.
> >
> > Is it possible something isn't set right in filo or LB?  I have
> >
> > option HAVE_FRAMEBUFFER=1 in linuxbios config.
> >
> > Any help is appreciated.  Thanks to all who contributed.
> >
> > M.R.
> > > From: "Dmitry Borisov" 
> > > To: 
> > > Subject: EPIA-M startup times
> > > Date: Mon, 26 Apr 2004 19:34:00 -0700
> > >
> > > Guys,
> > > Just wanted to have your estimate about startup times for EPIA-M
>
> mobo.
> > > ATM it takes about 9 secs to go to payload. 7 secs to go to splash.
>
> Which
> > > seems to be really high values.
> > > Does anyone can say what it would be if everything is "perfect" ?
> > > How much time at minimum the BIOS can take assuming RAM, VGA and PCI
> > > initialized properly ?
> > >
> > > If the answer would be 4 secs in ideal case, I'll invest some time to
> > > tighten it up... If 9 secs is a minimum, then...
> > >
> > > Any suggestions ?
> > > Dmitry/
> >
> > Check out the coupons and bargains on MSN Offers!
> > http://youroffers.msn.com
> >
> > Linuxbios mailing list
> > [e-mail]
> > http://www.clustermatic.org/mailman/listinfo/linuxbios
>
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios

EPIA-M startup times

[ron minnich]

On Thu, 13 May 2004, Ignacio Verona wrote:
> 20 sec to init scripts?? Isn't it very high times? I though using linuxbios I 
> could get faster boot times...

It is higher than I would like. I wonder what the delay is.

ron

Re[2]: EPIA-M startup times

["Dmitry Borisov=?koi8-r?Q?=22=20?=]

-----Original Message-----
From: "John Laur"
> otherwise you'll need some commandline trickery to make it work. Also,
> viafb doesn't work with bootsplash in silent mode on kernel 2.4 if you
> are using that. I have not tested with kernel 2.6.

John,
Were you able to understand the issue with the bootsplash ? I really want it implemented but just busy with something else now...
Dmitry/

EPIA-M startup times

[Stefan Reinauer]

* John Laur  [040513 20:46]:
> Then you can worry about the kernel. VESA Framebuffer does not work with
> EPIA-M as the VGA bios doesn't initialize the video card up to where
> vesafb can take over. You have to use viafb (part of the -epia patchset)
> to get video on the console. Make sure you have it compiled into the
> kernel and not as a module. Make sure vesafb is NOT compiled in either,
> otherwise you'll need some commandline trickery to make it work. Also,
> viafb doesn't work with bootsplash in silent mode on kernel 2.4 if you
> are using that. I have not tested with kernel 2.6.

Bootsplash as in www.bootsplash.org? Can you provide a log or some
details?

Stefan