So there are two issues: a) DOS isn't supported and b) the floppy as a boot device isn't supported. That will make it a very difficult sell for mobo manufacturers. Can you imagine me buying a Linux PC with LinuxBIOS and it crashing. How am I going to repair it then?
----- Original Message -----
From: Adam Sulmicki <adam(a)cfar.umd.edu>
Date: Fri, 6 Dec 2002 12:50:07 -0500 (EST)
To: "Ronald G. Minnich" <rminnich(a)lanl.gov>
Subject: Re: Booting from floppy
> > the u. md. guys will chime in here with an explanation :-)
> I'm trying to use it as the opportunity to improve the FAQ :-)
> From what I saw during the coverage of announcement there were quite a bit
> of folks unfamilar with the BIOS projects, an and this FAQ hopes to clear
> up the confusion.
> Big Pilot, if I may call you that, does this FAQ answers tose questions?
> The way I see, the part below is answered by Q5. Since I assume you are
> asking about LinuxBIOS. If you are really asking about linux kernel, then
> it is definitely wrong mailing list.
> > > if Linux fails, how is one supposed to repair it? Or is the only
> > > option booting Linux off a floppy and repairing using that?
> > > I'm wondering whether it is still possible to boot DOS (or a free
> > > equivalent) from a floppy if LinuxBIOS is installed on the mobo.
> As for above. We had limited success with Win98 which is DOS based (we can
> get as far as desktop screen, but there are issues), but as the Q6 says it
> is still long way to go.
> As for the particular susbsystem -- floppy, it has not been tested at all,
> and is presumed not working at the moment.
> Adam Sulmicki
> http://www.eax.com The Supreme Headquarters of the 32 bit registers
Now with POP3/IMAP access for only US$19.95/yr
Powered by Outblaze
So I've been following the developments of this board a little. If I'm
not mistaken, the board now works right?
If that is the case then I only have a few questions. I have a project
where it would be nice to not have to get LinuxBIOS working on our own
boards (which we are in the process of doing). Though we need a flash
root directory, I guess I can have a CF in an IDE connector but was
hoping that with this board it was possible to use a DoC type solution.
4604 Monterey Ave NW
I have just subscribed to this mailing list.
I am new to linuxbios and this project seems to have good prospectives.
I have just built romimage for Intel Clearwater motherboard and tried to
flash it into the bios, but Intel flash utility (phlash) refused to do
I failed to find any procedure or documentation for this motherboard on
how to make this motherboard work with linuxbios.
All i have right now is sources, which i have been examining during the
past several days. They seem to compile ok, so i want to flash at this
I know that common practice is to use disk on chip, but this motherboard
has zif flash socket instead of dip one.
Please, tell me how to flash romimage into flash.
Thank you in advance.
Yaroslav Klyukin, Linux Systems Administrator - slava(a)microway.com
Microway Inc., High Performance Computing - http://www.microway.com/
On Wednesday 08 January 2003 9:37 pm, Alessio Sangalli wrote:
> what about that disc on chip device: how much does it cost more or less?
In the UK they cost about GBP20 - so I guess that's about EUR30 / USD30 in
the rest of the world...
> Why can't we use a normal FLASH memory like the ones used to store a
> standard BIOS?
Because they do not have a large enough capacity. Standard BIOS chips are
2megabits (= 32 kilobytes), which is not neough to hold a Linux kernel.
> I can think those chips provide particular features, but
> which ones exactly?
The main thing which DoC does which you can't do with standard Flash Roms is
to format them as a Silicon Disc, and put a file system into them.
> Aren't common flash/eeprom chips much easier to find
> and cheaper to buy?
Yes, but they're too small.
> An external programmer could be needed (like for the
> eproms of etherboot) but most people could have access to such a device.
You can program a Flash Rom chip on your motherboard - no external programmer
needed - that's how you upgrade the BIOS even if you're not doing anything
If you want to be happy for an hour, get drunk.
If you want to be happy for a year, get married.
If you want to be happy for a lifetime, get a garden.
I own a via EPIA mobo that I use for GPS/music playing in my car.
It currently takes about 50 seconds to boot into my program
I am wondering if linux bios would help me in accelerating the boot time
Hi, I was wondering if there were avaiable prepackaged binaries for
Linuxbios ROMs. I don't want rpm of course (!) but I think that a
linuxbios image configured to boot from hda(1?) for a specific
motherboard (the pcchips one seems to be quite popular) may be very
useful; perhaps there are many configuration parameters, but I guess
resoanable defaults can be set and one would recompile everything only
if specific customizations are needed.
bye, thank you
Thanks a lot! I will try it! :)
From: Eric W. Biederman [mailto:firstname.lastname@example.org]
Sent: 2003?1?10? 15:38
Cc: Lawrence LL. Dai
Subject: Re: Boot from etherboot - blocked by INT 10
"Lawrence LL. Dai" <lawrence(a)tyanchina.com> writes:
> Hi, Eric
> I suppose that mknbi and mkelf would also cause this problem.Because
> they both tag a kernel, but the kernel must be the one like vmlinuz and vmlinux
> needs BIOS functions such as INT 10. (I know vmlinux does not need INT X, but
> vmlinux can not be tagged by mknbi and mkelf. Or I have missed something else?)
The difference is mknbi/mkelf that come standard with etherboot when
the process the linux kernel start the kernel in 16bit mode and run
it's BIOS code, mkelfImage simulates the effect of the 16bit BIOS
code by reading LinuxBIOS tables or making the needed BIOS calls
itself, and then it enters Linux at it's unofficial 32bit entry
mkelfImage can take either a bzImage or a vmlinux.