New hardware for performance testing BareMetal app

194 views
Skip to first unread message

lavapatch

unread,
May 15, 2012, 4:29:05 AM5/15/12
to bareme...@googlegroups.com
Hi all,

I've have a HP DC7700 I used for testing my BM applications on physical hardware but it has now reached its End Of Life. I am looking to build a replacement and I am considering the following components:

My main concern is the Motherboard, as the other components should just work ... Is there any reason anyone can think of why I shouldn't go for it?


David

Ian Seyler

unread,
May 16, 2012, 11:45:50 AM5/16/12
to bareme...@googlegroups.com
Those specs look fine to me. The integrated network on that ASUS board is a Realtek 8111E so it may be supported as well.

-Ian

lavapatch

unread,
May 17, 2012, 2:11:15 AM5/17/12
to bareme...@googlegroups.com
Thanks,

I should have everything by the end of today so I'll let you know how it goes

David

lavapatch

unread,
May 18, 2012, 9:36:23 PM5/18/12
to bareme...@googlegroups.com
Hi Ian,

I've assembled the machine and tried running BareMetal OS 0.5.3 but experienced a few problems:

  • Just after boot up 3 of the 4 CPU indicators are almost constantly on and the same holds for the RTC indicator
  • The hardware address of the nic is displayed but the prompt is only visible after hitting the return key.. even then some weird characters appear and the system is unable to find or run any command successfully.
I don't experience any of the above problems when running in a Virtual Box VM.

I've had a go at running both 0.5.2 and 0.5.1 on the physical machine and they seem fine except for one thing. When running smp tests both occasionally display  CPU id values which are higher than the number of available cores. 
In these two versions however, the correct parameter is printed out by whichever CPU executes the queued task.

Is there anything I can/should do to get 0.5.3 running properly on physical hardware?

David

Ian Seyler

unread,
May 22, 2012, 2:15:52 PM5/22/12
to bareme...@googlegroups.com
I believe the issues you are having with 0.5.3 are due to the IO-APIC. Basic support was added to use the IO-APIC instead of the legacy PIC to control interrupts. I'm looking into fixing it as Pure64 has similar issues.

-Ian

lavapatch

unread,
Nov 4, 2012, 8:18:46 AM11/4/12
to bareme...@googlegroups.com
Hi Ian,

You are probably quite busy but, do you have any idea when you will be able to look into this?  Unfortunately, my skillset does not cover assembly programming so I am not able to make any contributions here and I am unable to get any performance measurements on physical hardware until this is addressed.

David

Ian Seyler

unread,
Nov 6, 2012, 2:09:07 PM11/6/12
to bareme...@googlegroups.com
I'm working on getting a new stable release out. There hasn't been an official release since February 2012 now..

-Ian

Daniel Cegiełka

unread,
Nov 6, 2012, 2:40:51 PM11/6/12
to bareme...@googlegroups.com
Hi,
Regarding hardware, do you plan support for PCIe?

Daniel


2012/11/6 Ian Seyler <ise...@gmail.com>

Ian Seyler

unread,
Dec 17, 2012, 7:25:25 PM12/17/12
to bareme...@googlegroups.com
Yes, but no time has been spent on it yet. PCIe will be required to use newer network devices.

-Ian
Reply all
Reply to author
Forward
0 new messages