I use linuxbios to boot my mainboard tyan/s2881. But
I don't hope I'll use HD. I hope linux to mount
rootfs on ramdisk and run on it. How can I do that?
tks
zhu shi song
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Hey,
it is possible to change the LPT (Parport) Mode in LininuxBios for the
Epia-M.
I need only the standard Bios SPP Mode.
Currently, modprobe parport_pc detects following Modes
[PCSPP, Tristate, Compat, ECP] with LinuxBios
With SPP Mode from original Bios parport_pc detects
[PCSPP, Tristate, EPP] and that is what I need.
I think I must use EPP for a selfmade Printerport Interface.
I have tried to compile the Kernel without using FIFO, but it doesn't
work, also load the Module with DMA=none and several other options don't
work.
However , my LPT Interface does not work and therefor I will change the
Mode :D
regards chris
Hello @ all,
I have searched the MailingList for Epia, and there is another poster
which have the same problem as I have.
A slow boot Epia-M, which needs about 10 seconds for the first messages
over the com port.
Somebody means, it could be a problem at the northbridge, but has have
no solution :(
There is a second thing in the post, which compares to me.
It seems the poster has the same RAM, as I have.
Only the size differs. My RAM is a Single Sided 2100/3200 256MB with
Samsung Chips.
Could the RAM the reason for the slow boot. I think the first thing to
initialize is the RAM. Furthermore, the RAM is direct connected to the NB.
Chris
I'm thinking to make LinuxBIOS to run at 64 bit mode so
it can access 40 bit address in one instruction
we just need to
1. change entry32.inc to entry64.inc...
2. change secondary.S to support 64 bit
3. change most code32 to code64
The problem is that we may need make Etherboot and mkelfImage to support
64 bit too...
how do you think about it?
YH
I hate that in LinuxBIOS (CAR and RAM stage) I can not access the range
above 4G, esp the last 4G in 1T Range.
I could use fs base to access that, but that is quite slow...
YH
-----Original Message-----
From: Stefan Reinauer [mailto:stepan@openbios.org]
Sent: Friday, December 16, 2005 10:53 AM
To: Ronald G Minnich
Cc: Lu, Yinghai; Li-Ta Lo; Eric W. Biederman; LinuxBIOS
Subject: Re: about make LinuxBIOS 64bit for Opteron
* Ronald G Minnich <rminnich(a)lanl.gov> [051216 19:35]:
> I think we have to do it.
>
> That said, BEFORE this effort starts, I want to make sure that EVERY
> SINGLE OPTERON TARGET works as well as it did 6 months ago. And,
> currently, I don't think that is the case -- see ward's letter.
>
> We need to get this code base back to being more solid than it
currently is.
I fully agree. We should make a feature freeze and only let changes in
that fix something until we _verified_ that all (K8) mainboards are
working and on the same level (ie. equal cmos layouts, dual core, car
enabled, etc pp.)
One step at a time. We just recovered.
Besides that, 64bit is a must, no doubt.
Stefan
If it is quite slow, then I think there is something wrong
with the code.
You only need to write FS base or GS base MSR once per 4GB
assuming you can use 32-bit Protected non-paged mode.
I don't see why this should be slower than creating page tables
and populating them and doing the memory testing.
I'd like to get to the bottom of this one, but on offline
topic.
I personally agree with Ron, we should get AMD Opteron
squeaky clean first, before moving to 64-bit.
> -----Original Message-----
> From: linuxbios-bounces(a)openbios.org
> [mailto:linuxbios-bounces@openbios.org] On Behalf Of Lu, Yinghai
> Sent: Friday, December 16, 2005 11:02 AM
> To: Stefan Reinauer; Ronald G Minnich
> Cc: LinuxBIOS
> Subject: Re: [LinuxBIOS] about make LinuxBIOS 64bit for Opteron
>
> I hate that in LinuxBIOS (CAR and RAM stage) I can not access
> the range
> above 4G, esp the last 4G in 1T Range.
>
> I could use fs base to access that, but that is quite slow...
>
> YH
>
> -----Original Message-----
> From: Stefan Reinauer [mailto:stepan@openbios.org]
> Sent: Friday, December 16, 2005 10:53 AM
> To: Ronald G Minnich
> Cc: Lu, Yinghai; Li-Ta Lo; Eric W. Biederman; LinuxBIOS
> Subject: Re: about make LinuxBIOS 64bit for Opteron
>
> * Ronald G Minnich <rminnich(a)lanl.gov> [051216 19:35]:
> > I think we have to do it.
> >
> > That said, BEFORE this effort starts, I want to make sure
> that EVERY
> > SINGLE OPTERON TARGET works as well as it did 6 months ago. And,
> > currently, I don't think that is the case -- see ward's letter.
> >
> > We need to get this code base back to being more solid than it
> currently is.
>
> I fully agree. We should make a feature freeze and only let changes in
> that fix something until we _verified_ that all (K8) mainboards are
> working and on the same level (ie. equal cmos layouts, dual core, car
> enabled, etc pp.)
>
> One step at a time. We just recovered.
>
> Besides that, 64bit is a must, no doubt.
>
> Stefan
>
>
>
>
>
>
> --
> LinuxBIOS mailing list
> LinuxBIOS(a)openbios.org
> http://www.openbios.org/mailman/listinfo/linuxbios
>
>
Hello @ all,
I try to compile flashrom on my older Suse Distro 8.2 with Kernel 2.4.20
and gcc 3.3 Suse Prerelease, but it fails because of the -Werror Flag.
e.g flashrom_enable.c line 408 and 417
warning: comparison between signed and unsigned ... bla, bla
breaks the process.
If I delete -Werror in the makefile. flashrom is build, but with many
warnings shown below in mostly each file to compile.
Also, flashrom doesn't work for me, I get an error
"LinuxBios Table not found"
and then a
Segmention Fault
What goes wrong? Is my gcc version to old?
pciutils are installed.
regards Chris
