Hello,
I discovered the issue with Memtest86+ stuck on my Thinkpad x230 on the
very first tests. Always on the same point, 52%. Every release since 4.8
works this way, coreboot 4.7 works fine. Is this a known bug?
___
coreboot mailing list -- coreboo
Yes, lets revert it.
The popups work again after reverting commit 03e81e1
(https://review.coreboot.org/#/c/13900).
The other one (https://review.coreboot.org/#/c/13901/) doesn't make a
difference on my board.
Probably because I have VGA. I suppose that one can stay.
On Wed, Mar 9, 2016 at 1:57 PM
Do you think we should revert those patches until we can get them fixed?
On Wed, Mar 9, 2016 at 11:56 AM, Ben Gardner wrote:
> FYI -
>
> I just tried memtest86 with the popup patches that were added to coreboot.
> I'm seeing issues with clearing the background before drawing the SPD popup.
>
> Wh
FYI -
I just tried memtest86 with the popup patches that were added to coreboot.
I'm seeing issues with clearing the background before drawing the SPD popup.
When I hit "c", the "settings" popup shows on both serial and VGA
properly. VGA has a black background and serial clears the area.
When I
On Thu, Aug 20, 2015 at 06:36:00PM +0800, Iru Cai wrote:
> Hi,
>
> I installed coreboot(4.1-315-gf58746b) on a ThinkPad X220, with factory VGA
> option ROM and SeaBIOS 1.7.5 as payload. When I run memtest86+ on this
> machine, it reports a fail at 3070.7MB. If I just install a 2GB memory
> module,
Hi,
I installed coreboot(4.1-315-gf58746b) on a ThinkPad X220, with factory VGA
option ROM and SeaBIOS 1.7.5 as payload. When I run memtest86+ on this
machine, it reports a fail at 3070.7MB. If I just install a 2GB memory
module, it passes the test. So what makes memtest86+ give a test failure?
I
On Thu, Apr 09, 2015 at 11:03:43AM -0600, Martin Roth wrote:
> In regards to other approaches, instead of removing coreboot's memory
> tables, would it be better if SeaBIOS updated the tables with what it had
> changed instead of deleting the tables?
It's technically possible, but I don't think it
On 04/08/2015 08:45 PM, Kevin O'Connor wrote:
On Wed, Apr 08, 2015 at 10:55:18PM +0200, Stefan Tauner wrote:
On Thu, 19 Feb 2015 10:43:44 -0500
"Kevin O'Connor" wrote:
On Wed, Feb 18, 2015 at 10:26:21PM +0100, Stefan Reinauer wrote:
* Timothy Pearson [150205 19:23]:
e820: BIOS-provided phy
On Wed, Apr 08, 2015 at 10:55:18PM +0200, Stefan Tauner wrote:
> On Thu, 19 Feb 2015 10:43:44 -0500
> "Kevin O'Connor" wrote:
>
> > On Wed, Feb 18, 2015 at 10:26:21PM +0100, Stefan Reinauer wrote:
> > > * Timothy Pearson [150205 19:23]:
> > > > e820: BIOS-provided physical RAM map:
> > > > BIOS-
On 08.04.2015 22:55, Stefan Tauner wrote:
> On Thu, 19 Feb 2015 10:43:44 -0500
> "Kevin O'Connor" wrote:
>
>> On Wed, Feb 18, 2015 at 10:26:21PM +0100, Stefan Reinauer wrote:
>>> * Timothy Pearson [150205 19:23]:
e820: BIOS-provided physical RAM map:
BIOS-e820: [mem 0x-0
On Thu, 19 Feb 2015 10:43:44 -0500
"Kevin O'Connor" wrote:
> On Wed, Feb 18, 2015 at 10:26:21PM +0100, Stefan Reinauer wrote:
> > * Timothy Pearson [150205 19:23]:
> > > e820: BIOS-provided physical RAM map:
> > > BIOS-e820: [mem 0x-0x0009fbff] usable
> > > BIOS-e820: [me
On Wed, Feb 18, 2015 at 10:26:21PM +0100, Stefan Reinauer wrote:
> * Timothy Pearson [150205 19:23]:
> > e820: BIOS-provided physical RAM map:
> > BIOS-e820: [mem 0x-0x0009fbff] usable
> > BIOS-e820: [mem 0x0009fc00-0x0009] reserved
> > BIOS-e820: [mem 0
* Timothy Pearson [150205 19:23]:
> e820: BIOS-provided physical RAM map:
> BIOS-e820: [mem 0x-0x0009fbff] usable
> BIOS-e820: [mem 0x0009fc00-0x0009] reserved
> BIOS-e820: [mem 0x000f-0x000f] reserved
> BIOS-e820: [mem 0x
On 02/05/2015 09:45 PM, Timothy Pearson wrote:
On 02/05/2015 09:13 PM, Scott Duplichan wrote:
Timothy Pearson [mailto:tpear...@raptorengineeringinc.com] wrote:
]Sent: Thursday, February 05, 2015 06:49 PM
]To: Coreboot
]Subject: Re: [coreboot] memtest86 reading 0k memory
]
]On 02/05/2015 06:42
On 02/05/2015 09:13 PM, Scott Duplichan wrote:
Timothy Pearson [mailto:tpear...@raptorengineeringinc.com] wrote:
]Sent: Thursday, February 05, 2015 06:49 PM
]To: Coreboot
]Subject: Re: [coreboot] memtest86 reading 0k memory
]
]On 02/05/2015 06:42 PM, Timothy Pearson wrote:
]> On 02/05/2015
Timothy Pearson [mailto:tpear...@raptorengineeringinc.com] wrote:
]Sent: Thursday, February 05, 2015 06:49 PM
]To: Coreboot
]Subject: Re: [coreboot] memtest86 reading 0k memory
]
]On 02/05/2015 06:42 PM, Timothy Pearson wrote:
]> On 02/05/2015 02:06 PM, Timothy Pearson wrote:
]>> On 02/0
On 02/05/2015 06:42 PM, Timothy Pearson wrote:
On 02/05/2015 02:06 PM, Timothy Pearson wrote:
On 02/05/2015 01:51 PM, Aaron Durbin wrote:
Do you have the coreboot console log? Looking at memtest86 it
constructs its own e820 when using linuxbios. Additionally, it also
has some concept of a "wind
On 02/05/2015 02:06 PM, Timothy Pearson wrote:
On 02/05/2015 01:51 PM, Aaron Durbin wrote:
Do you have the coreboot console log? Looking at memtest86 it
constructs its own e820 when using linuxbios. Additionally, it also
has some concept of a "window" to test as well as plim_lower and
plim_upper
On Thu, Feb 5, 2015 at 1:15 PM, Timothy Pearson
wrote:
> On 02/05/2015 12:59 PM, Aaron Durbin wrote:
>>
>> On Thu, Feb 5, 2015 at 12:48 PM, Timothy Pearson
>> wrote:
>>>
>>> On 02/05/2015 12:38 PM, Jonathan A. Kollasch wrote:
That's a pretty old memtest86+. Also, memtest86+ prefe
On 02/05/2015 12:59 PM, Aaron Durbin wrote:
On Thu, Feb 5, 2015 at 12:48 PM, Timothy Pearson
wrote:
On 02/05/2015 12:38 PM, Jonathan A. Kollasch wrote:
That's a pretty old memtest86+. Also, memtest86+ prefers
linuxbios/coreboot memory map to e820. This becomes a problem
when SeaBIOS sets u
On Thu, Feb 5, 2015 at 12:48 PM, Timothy Pearson
wrote:
> On 02/05/2015 12:38 PM, Jonathan A. Kollasch wrote:
>>
>> That's a pretty old memtest86+. Also, memtest86+ prefers
>> linuxbios/coreboot memory map to e820. This becomes a problem
>> when SeaBIOS sets up a USB controller to DMA to e820-re
On 02/05/2015 12:38 PM, Jonathan A. Kollasch wrote:
That's a pretty old memtest86+. Also, memtest86+ prefers
linuxbios/coreboot memory map to e820. This becomes a problem
when SeaBIOS sets up a USB controller to DMA to e820-reserved
memory that wasn't reserved by coreboot.
Try a modern memtest
On Thu, Feb 05, 2015 at 12:23:40PM -0600, Timothy Pearson wrote:
> All,
>
> I have a board here that loads memtest86 but won't actually test memory.
>
> This is the output:
>
> Memtest86+ v2.11
> AMD K10 CPU @ 2312 MHz
> L1 Cache: 64K 35028 MB/s
> L2 Cache: 512K 6963 MB/s
> L3 Cache:
All,
I have a board here that loads memtest86 but won't actually test memory.
This is the output:
Memtest86+ v2.11
AMD K10 CPU @ 2312 MHz
L1 Cache: 64K 35028 MB/s
L2 Cache: 512K 6963 MB/s
L3 Cache: 2048K 6052 MB/s
Memory :0K
|-
Patrick Georgi escribió:
> Am 25.01.2010 17:13, schrieb Knut Kujat:
>
>> - booting interrupts for about 4 minutes on "Stage: loading
>> fallback/coreboot_ram @ 0x20 (360448 bytes), entry @ 0x20"
>>
>>
> For this issue, the following change might help:
> --- src/cpu/amd/mtrr/amd_e
Am 25.01.2010 17:13, schrieb Knut Kujat:
> - booting interrupts for about 4 minutes on "Stage: loading
> fallback/coreboot_ram @ 0x20 (360448 bytes), entry @ 0x20"
>
For this issue, the following change might help:
--- src/cpu/amd/mtrr/amd_earlymtrr.c(revision 5054)
+++ src/cpu/amd/m
> Patrick Georgi escribió:
> > Am 25.01.2010 17:13, schrieb Knut Kujat:
> >
> >> Hi,
> >> I would love to send the new board to the list but there are several
> >> issues still remaining like:
> >> - SMBus gets irq 0 instead of 5
> >> - ACPI not working
> >>
> > We have lots of boards with (at best
Patrick Georgi escribió:
> Am 25.01.2010 17:13, schrieb Knut Kujat:
>
>> Hi,
>> I would love to send the new board to the list but there are several
>> issues still remaining like:
>> - SMBus gets irq 0 instead of 5
>> - ACPI not working
>>
>>
> We have lots of boards with (at best) inco
Am 25.01.2010 17:13, schrieb Knut Kujat:
> Hi,
> I would love to send the new board to the list but there are several
> issues still remaining like:
> - SMBus gets irq 0 instead of 5
> - ACPI not working
>
We have lots of boards with (at best) incomplete ACPI support. That
shouldn't stop you fro
Hi,
I would love to send the new board to the list but there are several
issues still remaining like:
- SMBus gets irq 0 instead of 5
- ACPI not working
- booting interrupts for about 4 minutes on "Stage: loading
fallback/coreboot_ram @ 0x20 (360448 bytes), entry @ 0x20"
and the strangest
> On 1/22/10 12:36 AM, Myles Watson wrote:
> > I modified SeaBIOS to destroy the
> > marker for the LinuxBIOS tables after reading them (since they are no
> longer
> > useful.)
> Unless you ever plan to change CMOS settings, or update your BIOS and
> want flashrom to know _reliably_ what mainboard
On 1/22/10 12:36 AM, Myles Watson wrote:
> I modified SeaBIOS to destroy the
> marker for the LinuxBIOS tables after reading them (since they are no longer
> useful.)
Unless you ever plan to change CMOS settings, or update your BIOS and
want flashrom to know _reliably_ what mainboard you're using
On Fri, Jan 22, 2010 at 12:09:59AM +0100, Knut Kujat wrote:
> sorry, of course. I did the necessary changes on the alrady existing
> supermicro h8dmr_fam10 board to make it work on a h8qme_fam10.
I'm interested in your port. It should go into the tree. Do you want to send
a patch to the list?
Tha
> I used the memtest that comes with the OPENSuse 11.2 installation CD I
> also installed memtest to my grub boot menu.
> Seems like memtest doesn't find any memory at all?! But linux boots fine
> and recognized the whole memory amount. I already did some benchmarks and
> they finished without any
Ah, ok! I'll try this.
At least now I know from you and ron that it isn't necessary my ram thats
failing.
thx a lot!
Knut.
>> I used the memtest that comes with the OPENSuse 11.2 installation CD I
>> also installed memtest to my grub boot menu.
>> Seems like memtest doesn't find any memory at a
OK, thx anyway. I found another one "memtester 4.1" usable from linux so
it won't test the whole amount but memtest86 doesn't either :P.
bye!
> memtest in many ways is not my favorite program. I would rather have a
> simple non-"GUI" tester, because in the past I've had trouble with it
> (it can f
memtest in many ways is not my favorite program. I would rather have a
simple non-"GUI" tester, because in the past I've had trouble with it
(it can fail) when it did not like the device it was trying to do its
"GUI" on.
Also, the way memtest finds top of memory can fail on some chipsets.
Have not
Hi,
sorry, of course. I did the necessary changes on the alrady existing
supermicro h8dmr_fam10 board to make it work on a h8qme_fam10.
Supermicro H8QME-2+
4 CPUs (Opterons)
16 GB ram
MCP55 PRO
AMD 8132
I used the memtest that comes with the OPENSuse 11.2 installation CD I
also installed memtest
Knut Kujat wrote:
> Now, when I'm trying to test my memory with Memtest86+ it doesn't
> starts!
How are you trying to start it?
> I know there is a payload with Memtest86+ I haven't tried yet
> but I just don't think it will make any difference, won't it?
Using memtest as payload is the only wa
can you remind us what hardware this is?
ron
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Hello,
I've finally got my board working with Coreboot now I started to stress
test the whole system to know if it is stable. Now, when I'm trying to
test my memory with Memtest86+ it doesn't starts! instead it shows correct
information about my cpus and caches but at "Memory" there is just a 0K
a
I would really like a memtest without the eye candy. In at least one
case on geode if I ran it in a non-80-column window it would fail --
honest!
One that did simple serial out would really make life simpler.
ron
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/li
On Thu, Aug 13, 2009 at 10:26 AM, Cristi Magherusan <
cristi.magheru...@net.utcluj.ro> wrote:
> On Thu, 2009-08-13 at 10:08 -0600, Myles Watson wrote:
> > Has anyone used memtest86 as a payload recently? I can't get it to work
>
> Do you use mkelfImage prior to adding the ELF in CBFS?
No I didn'
On Thu, 2009-08-13 at 10:08 -0600, Myles Watson wrote:
> Has anyone used memtest86 as a payload recently? I can't get it to work
> with qemu or Serengeti. On Qemu it executes outside of RAM, and on
> Serengeti it writes garbage to the screen.
>
> Thanks,
> Myles
>
Hello,
Do you use mkelfImage
Myles,
I've tried it with the serial output enabled as no VGA on the truxton so
far. It did segfault and I had
no time to dig further in.
Arnaud
Myles Watson wrote:
Has anyone used memtest86 as a payload recently? I can't get it to work
with qemu or Serengeti. On Qemu it executes outside o
On Thu, Aug 13, 2009 at 10:08:00AM -0600, Myles Watson wrote:
> Has anyone used memtest86 as a payload recently? I can't get it to work
> with qemu or Serengeti. On Qemu it executes outside of RAM, and on
> Serengeti it writes garbage to the screen.
I have gotten it to work 6 months or so ago ii
Has anyone used memtest86 as a payload recently? I can't get it to work
with qemu or Serengeti. On Qemu it executes outside of RAM, and on
Serengeti it writes garbage to the screen.
Thanks,
Myles
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
47 matches
Mail list logo
