when compiling my linux kernel i keep on recieving this message:
Warning: Clock Skew Detected Build May Be Incomplete
It seams to compile ok.
What does this error message mean?? and how can i fix it.
thanks
edwin
ps. I have only been getting this message since i upgraded to an AMD K6-2 500Mhz.
> ----------
> Von: Edwin Rhodes[SMTP:edwin_rhodes@hotmail.com]
> Antwort an: openbios(a)freiburg.linux.de
> Gesendet: Montag, 31. Januar 2000 02:26
> An: openbios(a)elvis.informatik.uni-freiburg.de
> Betreff: Re: [OpenBIOS] Fine.
>
> can i have a copy of this rom-emulator?
> thanks edwin
> ----- Original Message -----
> From: Winter Jörg <joerg.winter(a)disch-gmbh.de>
> To: <openbios(a)elvis.informatik.uni-freiburg.de>
> Sent: Friday, January 28, 2000 10:50 AM
> Subject: [OpenBIOS] Fine.
>
I´m sorry, but a copy of my ROM-Emulator would not be what you expext ...
I was not talking about Software. The Emulator is a little piece of Hardware
that I bought. It is intended to be inserted into a standard 32 Pin
Jedec-Memory Socket. Then you download a 64k image via the parallel port of
any PC into this Hardware. You press reset at the board and it boots ...
well sometimes ...
If you are interested in such an Hardware try th e following urls as a
start:
www.hed.de (they make tools for embedded and microcontrol. I once talked to
their Boss and got the impression that they are really good!)
www.embedded-tools.de (they have a modular Emulator called PromJet. Its able
to act like rom/ram/flash up to 16Mbit and 32Bit Words. Furthermore it can
handle operating voltages from 2 to 5V. It also has an ethernet plug ...)
Well this is not an advertisement ... I did not test these devices but they
seem interesting to me ...
> eMail: mailto:Joerg.Winter@Disch-GmbH.de
>
>
-
To unsubscribe: send mail to majordomo(a)freiburg.linux.de
with 'unsubscribe openbios' in the body of the message
I have read openBios mail for a while, and i want to know if there is any
kind of code to the ide chips and to irq handlers, cause it could be useful
for the AROS team (www.aros.org) , if anyone can help i would apreciate.
best regards,
Jaime Dias
then is OpenBIOS going to include a bootloader?
-----Original Message-----
From: Matthew Sullivan [mailto:matthew@netscape.com]
Sent: January 31, 2000 1:20 Pm
To: openbios(a)elvis.informatik.uni-freiburg.de
Subject: Re: [OpenBIOS] Starting Linux from the C environment
Hi,
"Stawnyczy, Evan" wrote:
> well this was my argument in the begining, we should allow this BIOS to
> support "REAL" bios calls like int 13 and int 10... if you include basic
> BIOS functionality, you can allow any "decent" operating system to
> startup... including LILO
Ahh but if I remember back at the beginning of the list the point of
openBIOS
was to get rid of the BIOS calls and boot 32bit OS's in 32bit mode, the
though
being that most OS's don't use the BIOS calls, except when first
booting.....
Of course that concept can deliver a whole new selection of problems...
I'll
leave the rest to you .. ;-)
--
Yours
Matthew
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
More Computer Terminology
-=-=-=-=-=-=-=-=-=-=-=-=-
Booting (as in: the computer): applying a size 16 Doc Martins to the system
unit after it keeps telling
you there is not enough memory to open the application.
-
To unsubscribe: send mail to majordomo(a)freiburg.linux.de
with 'unsubscribe openbios' in the body of the message
Ron,
No I am just running it in RAM (Shadow ROM) right now. This uses the
Loadbios (actually a modified version that checks the size and automatically
adapts to the various possible image sizes... I hope to post that here next
week after a little cleanup ).
I was going to look into just using one of the flash programs for our
chipset but someone had mentioned they had source for doing this.
I will be looking into that in the next week or so and will keep you posted.
Wallace
> -----Original Message-----
> From: Ronald G. Minnich [SMTP:rminnich@lanl.gov]
> Sent: Monday, January 31, 2000 8:10 AM
> To: 'openbios(a)freiburg.linux.de'
> Subject: RE: [OpenBIOS] where I'm at with the 440gx and reading nvram
>
> On Fri, 28 Jan 2000, Wallace I. Kroeker wrote:
> > I am working with the 440BX chipset and have it hobbling along.
> > I am having problems with the MDA getting any screen output.
> > I am able to get beeps out for different keys on the keyboard
> > but no character display. (Of course, this could be just the situation
> to
> > use Morse code :-).
>
> are you actually getting it to write the BIOS FLASH? what code are you
> using to do that?
>
> thanks
> ron
>
> -
> To unsubscribe: send mail to majordomo(a)freiburg.linux.de
> with 'unsubscribe openbios' in the body of the message
-
To unsubscribe: send mail to majordomo(a)freiburg.linux.de
with 'unsubscribe openbios' in the body of the message
well this was my argument in the begining, we should allow this BIOS to
support "REAL" bios calls like int 13 and int 10... if you include basic
BIOS functionality, you can allow any "decent" operating system to
startup... including LILO
-----Original Message-----
From: Winter Jörg [mailto:joerg.winter@disch-gmbh.de]
Sent: January 31, 2000 10:54 Am
To: openbios(a)elvis.informatik.uni-freiburg.de
Subject: [OpenBIOS] Starting Linux from the C environment
> ----------
> Von: Stawnyczy, Evan[SMTP:EStawnyczy@geo-logistics.com]
> Antwort an: openbios(a)freiburg.linux.de
> Gesendet: Montag, 31. Januar 2000 15:48
> An: openbios(a)elvis.informatik.uni-freiburg.de
> Betreff: RE: [OpenBIOS] Fine.
>
> my understanding of lilo is that if you place it on the boot sector, you
> can
> load the boot sector to a point in memory (I cannot recall exactly where
> right now, you can email me farther if you need to) and simply jmp to it.
> Actually all boot sectors work the same way...
>
Basicly you are right. But lilo makes extensive use of *real* BIOS
functions like int13, int10, int16, and some strange
int15-shift-this-memory-to-ems function that I forgot the functioncode of.
I´d rather do this in C and burn a barebone Kernel onto my Disk ...
But I´m not sure if I kill my own running environment by copying a
Kernel to mem at 0x10000. Furthermore I have no idea if the
segment-deskriptor-setup is suitable for an immediate start of a kernel
image ...
I´ll try this tomorrow and keep you up to date if I succeed on this
...
> eMail: mailto:Joerg.Winter@Disch-GmbH.de
>
>
-
To unsubscribe: send mail to majordomo(a)freiburg.linux.de
with 'unsubscribe openbios' in the body of the message
-
To unsubscribe: send mail to majordomo(a)freiburg.linux.de
with 'unsubscribe openbios' in the body of the message
the 64K limit... i'm not exactly sure what you mean, but I think you may
mean real mode... not protected mode. you can look up the source code for
p-mode on ftp://ftp.cdrom.com/pub/programming/pmode
<ftp://ftp.cdrom.com/pub/programming/pmode>
and look through the "jump to protected mode" portion.
-----Original Message-----
From: Ross [mailto:rossio@hoeftd.reno.nv.us]
Sent: January 31, 2000 10:55 Am
To: openbios(a)elvis.informatik.uni-freiburg.de
Subject: Re: [OpenBIOS] ROM-Emulators
Do anyone out there know how I can get around the 64k limit of
a self booting floopy disk? I know up to 40k of data on the floppy.
----------
> From: Winter Jörg <joerg.winter(a)disch-gmbh.de>
> To: openbios(a)elvis.informatik.uni-freiburg.de
> Subject: [OpenBIOS] ROM-Emulators
> Date: Monday, January 31, 2000 1:05 AM
>
>
>
> > ----------
> > Von: Edwin Rhodes[SMTP:edwin_rhodes@hotmail.com]
> > Antwort an: openbios(a)freiburg.linux.de
> > Gesendet: Montag, 31. Januar 2000 02:26
> > An: openbios(a)elvis.informatik.uni-freiburg.de
> > Betreff: Re: [OpenBIOS] Fine.
> >
> > can i have a copy of this rom-emulator?
> > thanks edwin
> > ----- Original Message -----
> > From: Winter Jörg <joerg.winter(a)disch-gmbh.de>
> > To: <openbios(a)elvis.informatik.uni-freiburg.de>
> > Sent: Friday, January 28, 2000 10:50 AM
> > Subject: [OpenBIOS] Fine.
> >
> I´m sorry, but a copy of my ROM-Emulator would not be what you expext ...
>
> I was not talking about Software. The Emulator is a little piece of
Hardware
> that I bought. It is intended to be inserted into a standard 32 Pin
> Jedec-Memory Socket. Then you download a 64k image via the parallel port
of
> any PC into this Hardware. You press reset at the board and it boots ...
> well sometimes ...
>
> If you are interested in such an Hardware try th e following urls as a
> start:
>
> www.hed.de (they make tools for embedded and microcontrol. I once talked
to
> their Boss and got the impression that they are really good!)
>
> www.embedded-tools.de (they have a modular Emulator called PromJet. Its
able
> to act like rom/ram/flash up to 16Mbit and 32Bit Words. Furthermore it can
> handle operating voltages from 2 to 5V. It also has an ethernet plug ...)
>
> Well this is not an advertisement ... I did not test these devices but
they
> seem interesting to me ...
>
> > eMail: mailto:Joerg.Winter@Disch-GmbH.de
> >
> >
> -
> To unsubscribe: send mail to majordomo(a)freiburg.linux.de
> with 'unsubscribe openbios' in the body of the message
Hi!
Did my sources arive to the list ?
--
Johan Rydberg johan.rydberg(a)netinsight.net
Net Insight AB, Sweden direct: +46-8-685 04 17
http://www.netinsight.net phone: +46-8-685 04 00
fax: +46-8-685 04 20
-
To unsubscribe: send mail to majordomo(a)freiburg.linux.de
with 'unsubscribe openbios' in the body of the message
I am working from the OpenBIOS-0.0.2. The beep code in
/Firmware/init/timer.c
I modified the print code to output a different number of beeps (2 of 'a'
and 6 for 'z'). The OpenBIOS code (as is) boots and then sits in a loop
waiting for a character of input. Once the character arrives it trys to
print it out.
I have some assembler code which also produces a beep. I used it for the
initial debugging of /boo/boot16/start.asm.
Are you interested in this?
I know someone else was asking earlier where to start in with this so here
is what I've found out so far (someone can correct me if I'm wrong):
1. Download OpenBIOS.0.0.2pre1
2. Make sure you have the nasm assembler (www.web-sites.co.uk/nasm
to get the latest) and Gnu C (this came with Linux)
3. At the root directory type "make config" this will make the
configuration and step you through the selections for Processor, Chipset,
etc. (if you go with the defaults it seems to come up for some 486 board ...
this sort of seemed to work for my machine to get things started)
4. Now type make and it should make everything. Leaving you with a
ROM.bin
So now that you can actually get it to build you can download the LoadBIOS
program and try out your BIOS from RAM (as has been discussed in other
messages).
The documentation directory has a very brief description of the internal
structure.
How about adding a new chipset?
1. Everything starts in /boot/boot16/start.asm. There is an
include of chipset.inc. When you ran the configuration make you specify
which chipset which is actually telling the make which directories to find
things such as chipset.inc
2. First create a new chipset directory in /drivers/chipset. ( I
copied ali_M1511 to create a new chipset (440BX) directory.) Comment
everything out as you will eventually have to modify this for your own
chipset.
3. Modify the .config to allow selection of your new chipset.
4. Modify /drivers/Config.mak and add your chipset for the make
process
5. Now run make .config and make to rebuild it. It should now be
using your new chipset definition. To confirm that you are compiling the
correct code put in a deliberate error in your chipset assembler file. If
everything is correct then you should get an error showing up in the build.
You follow the same approach for your superio.
Helpful books.
PC Intern by Michael Tischer, Brun
Jennrich
The Programmer's PC Sourcebook by Thom Hogan (Seems to be of print
but you might get your hands on a copy )
Hope this is of some use.
Wallace
> -----Original Message-----
> From: James [SMTP:jvh@uclink4.berkeley.edu]
> Sent: Friday, January 28, 2000 6:39 PM
> To: 'openbios(a)freiburg.linux.de'
> Subject: RE: [OpenBIOS] where I'm at with the 440gx and reading nvram
>
> > I am working with the 440BX chipset and have it hobbling along.
> > I am having problems with the MDA getting any screen output.
> > I am able to get beeps out for different keys on the keyboard
> > but no character display. (Of course, this could be just the situation
> to
> > use Morse code :-).
>
> What is the code to get it to beep?
> - James
>
>
> -
> To unsubscribe: send mail to majordomo(a)freiburg.linux.de
> with 'unsubscribe openbios' in the body of the message
-
To unsubscribe: send mail to majordomo(a)freiburg.linux.de
with 'unsubscribe openbios' in the body of the message
to my understanding, they're just using a rom emulator right now.
-----Original Message-----
From: Ronald G. Minnich [mailto:rminnich@lanl.gov]
Sent: January 31, 2000 10:10 Am
To: 'openbios(a)freiburg.linux.de'
Subject: RE: [OpenBIOS] where I'm at with the 440gx and reading nvram
On Fri, 28 Jan 2000, Wallace I. Kroeker wrote:
> I am working with the 440BX chipset and have it hobbling along.
> I am having problems with the MDA getting any screen output.
> I am able to get beeps out for different keys on the keyboard
> but no character display. (Of course, this could be just the situation to
> use Morse code :-).
are you actually getting it to write the BIOS FLASH? what code are you
using to do that?
thanks
ron
-
To unsubscribe: send mail to majordomo(a)freiburg.linux.de
with 'unsubscribe openbios' in the body of the message
-
To unsubscribe: send mail to majordomo(a)freiburg.linux.de
with 'unsubscribe openbios' in the body of the message
