Okay, this is mostly a shot in the dark, but it's the only thing I can
find that might cause something like this. I'm looking at the AGP size
register (APSIZE, 0xb4) in the datasheet, and the default value is 0x00,
which is 256MB (!!). I also don't see anywhere that AGP has to be
explicitly
Long story short, try setting the AGP aperture to 32MB and moving the
aperture base (APBASE, 0x10-13) to somewhere else, preferably wherever
the stock bios moves it to. Even if it's not the root cause, it'll get
it out of the way for later.
-Corey
It looks like the original bios alocates
Corey, After scatching my head for days (hair thinning even more) I
think you may be onto something. I have tried changing the values in
APBASE before with no luck and I think this is why:
1. APSIZE Bits[5:3] need to be set first to 111 too allow APBASE
Bits[27:25] to become R/W.
This
[EMAIL PROTECTED] wrote:
Here is my ram_check from 1-128MB. It appears to fill the ram ok. But
only returns a value of 0x. Does this mean the ram is WO
(write only) for some reason? Thanks again for your help.
Okay, this is mostly a shot in the dark, but it's the only thing I can
find
Quoting Corey Osgood [EMAIL PROTECTED]:
[EMAIL PROTECTED] wrote:
Here is my ram_check from 1-128MB. It appears to fill the ram ok. But
only returns a value of 0x. Does this mean the ram is WO
(write only) for some reason? Thanks again for your help.
Okay, this is mostly a shot in
Quoting Stefan Reinauer [EMAIL PROTECTED]:
* [EMAIL PROTECTED] [EMAIL PROTECTED] [071004 06:26]:
Here is my ram_check from 1-128MB. It appears to fill the ram ok. But
only returns a value of 0x. Does this mean the ram is WO
(write only) for some reason? Thanks again for your help.
Quoting [EMAIL PROTECTED]:
Quoting Stefan Reinauer [EMAIL PROTECTED]:
* [EMAIL PROTECTED] [EMAIL PROTECTED] [071004 06:26]:
Here is my ram_check from 1-128MB. It appears to fill the ram ok. But
only returns a value of 0x. Does this mean the ram is WO
(write only) for some reason?
How does ram check from 1 mb to 2 (not 128 -- 2) work? You need to
start searching in smaller numbers than 128 mb
ron
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
[EMAIL PROTECTED] wrote:
Quoting Corey Osgood [EMAIL PROTECTED]:
[EMAIL PROTECTED] wrote:
Quoting ron minnich [EMAIL PROTECTED]:
you might try forcing the size (in code) to 32M or some such in
hardwaremain.c and see if it works then. There's something odd with
your ram.
ron
It won't
Quoting Corey Osgood [EMAIL PROTECTED]:
[EMAIL PROTECTED] wrote:
Quoting Corey Osgood [EMAIL PROTECTED]:
[EMAIL PROTECTED] wrote:
Quoting ron minnich [EMAIL PROTECTED]:
you might try forcing the size (in code) to 32M or some such in
hardwaremain.c and see if it works then. There's
* [EMAIL PROTECTED] [EMAIL PROTECTED] [071004 06:26]:
Here is my ram_check from 1-128MB. It appears to fill the ram ok. But
only returns a value of 0x. Does this mean the ram is WO
(write only) for some reason? Thanks again for your help.
Do you have several banks? Do you send
Quoting Corey Osgood [EMAIL PROTECTED]:
[EMAIL PROTECTED] wrote:
Corey the onboard memory is 128MB. I have to set the video buffer to
something or it won't boot past raminit.c. I have it set to 512K.
Could this be causing the problem? I will test it with memtest.
In northbridge.c, you are
On Mon, Oct 01, 2007 at 09:50:04AM -0700, ron minnich wrote:
you might try forcing the size (in code) to 32M or some such in
hardwaremain.c and see if it works then.
And/or set very conservative memory timings.
//Peter
--
linuxbios mailing list
linuxbios@linuxbios.org
On Sun, Sep 30, 2007 at 04:20:24PM -0400, Corey Osgood wrote:
Just build memtest and use the resulting memtest (not memtest.bin) as
your payload. Way simpler then it's supposed to be.
That, and enable serial support in memtest, you'll need/want that to
get the output on the serial console.
[EMAIL PROTECTED] wrote:
Quoting ron minnich [EMAIL PROTECTED]:
you might try forcing the size (in code) to 32M or some such in
hardwaremain.c and see if it works then. There's something odd with
your ram.
ron
It won't have anything to do with the fact that:
a. It is onboard
Quoting Peter Stuge [EMAIL PROTECTED]:
On Mon, Oct 01, 2007 at 09:50:04AM -0700, ron minnich wrote:
you might try forcing the size (in code) to 32M or some such in
hardwaremain.c and see if it works then.
And/or set very conservative memory timings.
Not too sure how I can do this. Can you
On 10/1/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
c. It is located in the second slot not first.
hmm. could this second slot somehow have a different base physical
address? unlikely but this is getting confusing.
ron
--
linuxbios mailing list
linuxbios@linuxbios.org
Quoting ron minnich [EMAIL PROTECTED]:
On 10/1/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
c. It is located in the second slot not first.
hmm. could this second slot somehow have a different base physical
address? unlikely but this is getting confusing.
ron
I don't think so. Your
On 01/10/07 21:06 -0400, [EMAIL PROTECTED] wrote:
Quoting ron minnich [EMAIL PROTECTED]:
On 10/1/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
c. It is located in the second slot not first.
hmm. could this second slot somehow have a different base physical
address? unlikely but
Quoting Jordan Crouse [EMAIL PROTECTED]:
On 01/10/07 21:06 -0400, [EMAIL PROTECTED] wrote:
Quoting ron minnich [EMAIL PROTECTED]:
On 10/1/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
c. It is located in the second slot not first.
hmm. could this second slot somehow have a different
Quoting Peter Stuge [EMAIL PROTECTED]:
On Sat, Sep 29, 2007 at 05:02:45PM -0400, [EMAIL PROTECTED] wrote:
Did you succeed loading any other payloads? memtest?
I have just been using /etc/hosts so far. I tried filo and this is
what happens. Should I try memtest first?
Yes. Until memtest
Quoting Corey Osgood [EMAIL PROTECTED]:
[EMAIL PROTECTED] wrote:
I just wanted to report etherboot is doing the same thing. What could
be causing this?? Someone please help me.
Thanks - Joe
rom_stream: 0xfffd - 0xfffe
Found
yes, all -1 (fff) sure looks like you are somewhere where memory is not.
ron
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
Help me please. I have attached my bootlog. Filo gets this error, what
does it mean?
Thanks - Joe
-
Welcome to elfboot, the open sourced starter.
January 2002, Eric Biederman.
Version 1.3
rom_stream: 0xfffd - 0xfffe
Found ELF candidate
* [EMAIL PROTECTED] [EMAIL PROTECTED] [070929 22:51]:
Help me please. I have attached my bootlog. Filo gets this error, what does
it mean?
Did you succeed loading any other payloads? memtest?
Jumping to boot code at 0x10ea14
entry= 0x0010ea14
lb_start = 0x4000
lb_size =
Quoting Stefan Reinauer [EMAIL PROTECTED]:
* [EMAIL PROTECTED] [EMAIL PROTECTED] [070929 22:51]:
Help me please. I have attached my bootlog. Filo gets this error, what does
it mean?
Did you succeed loading any other payloads? memtest?
I have just been using /etc/hosts so far. I tried filo
On Sat, Sep 29, 2007 at 05:02:45PM -0400, [EMAIL PROTECTED] wrote:
Did you succeed loading any other payloads? memtest?
I have just been using /etc/hosts so far. I tried filo and this is
what happens. Should I try memtest first?
Yes. Until memtest works and finds no errors, RAM is not
Quoting [EMAIL PROTECTED]:
Quoting Stefan Reinauer [EMAIL PROTECTED]:
* [EMAIL PROTECTED] [EMAIL PROTECTED] [070929 22:51]:
Help me please. I have attached my bootlog. Filo gets this error, what does
it mean?
Did you succeed loading any other payloads? memtest?
I have just been using
[EMAIL PROTECTED] wrote:
I just wanted to report etherboot is doing the same thing. What could
be causing this?? Someone please help me.
Thanks - Joe
rom_stream: 0xfffd - 0xfffe
Found ELF candidate at offset 0
header_offset
29 matches
Mail list logo
