Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - SiteAdmin

Pages: 1 [2] 3
16
Firmware / Re: Compiling and Updating BMC
« on: February 09, 2022, 12:15:50 pm »
Thank you for your quick response.  Your assessment was spot on. After a quick "sudo mount --bind /dev ~/debian-chroot/dev" I was able to compile sort of-ish.  Now I get "Summary: There were 2 ERROR messages shown, returning a non-zero exit code."

Did the build process generate the ROM file?  If so, the errors can be ignored, if not, then you should delete the build directory and try again as the lack of SHM might have corrupted the build state enough to stop ROM generation.

17
Firmware / Re: Compiling and Updating BMC
« on: February 07, 2022, 02:03:20 pm »
Error 38 from Python means you don't have SHM (proc etc.) bind mounted in your chroot.

Correction: /dev is typically where the missing SHM node is located, so you need to bind mount /dev into your chroot.

18
Firmware / Re: Compiling and Updating BMC
« on: February 07, 2022, 01:06:44 pm »
Working on a Blackbird/Fedora via debian-chroot, I was able to self compile "blackbird.pnor". 

I am stuck with a
"OSError: [Errno 38] Function not implemented
)
ERROR: Unable to connect to bitbake server, or start one"
while Building the OpenBMC firmware.

I had decided to just download the pre-compiled version and became a little confused.  The instructions for self compiling say you should end up with 2 files,  "image-rofs" and "image-kernel" but when I open the pre-compiled version it contains only one file, "blackbird-v2.00-image-bmc".

EDIT: So, if updating via shell you use the web_ipmi_upgrade and if updating via the web you use the shell_upgrade?  I'm sure this makes sense to everybody else but I invert my x-y axis on FPS's. ;)

Error 38 from Python means you don't have SHM (proc etc.) bind mounted in your chroot.

19
I wouldn't spend much effort into Chromium development. First, Google sucks.

That was never in any doubt. ;)

Second, Chromium is just fine, it works. I'm on version 93 or 94. But if you're on 70, 80 or 90 doesn't play a role.

But I'm willing to donate for Firefox improvements. To make it on par or surpass Chromium.

That would be most welcome.  We'll kick this around a bit on our side and figure out if / how to make that happen, and whether it makes more sense to e.g. try to directly fund Cameron or if it might make more sense to add some of our resources to his efforts (i.e. determine if he's time or cash limited right now on the Firefox port).

And I assume Mozilla is accepting upstream POWER support?

Yes.  Firefox's issues stem purely from performance problems in regard to the lack of JIT etc., and they are willing to accept patches.

I'm pretty sure, in the long run it's better/ easier to support Firefox.

There is a bit of a marketshare (IE6-type) problem here, Chromium is all that many developers write for these days (right or wrong, this is just the way things are) and as a result it is still important to have Chromium support on POWER if it is to remain a viable desktop platform.  That said, if Firefox works better and we can really hammer home the privacy aspects (e.g. get Mozilla to start changing some stances on e.g. DRM in the browser) there might be a way back from the brink.

20
Raptor may be willing to pick this up but since Google has refused to upstream the POWER support, and Chromium is not exactly a "typical" free software product, in the current economy this would have to be under some type of bounty system.  Frankly, on our side if we're going to invest in a browser development project we'd probably pick Firefox over Chromium given Google's apparent public stance on owner control / individual data rights.

Our question is: is this something that would be palatable?  It's a lot of work, so it'd have to be probably in the several thousand USD range (or, worse, significantly more depending on just how Google managed to break the builds in the interim), but if there are (say) a hundred or more Chromium users here that would come down to $100 or less a person.  If it worked, we could even make it a subscription type development service; assuming the user numbers are even close to accurate, something like $50 annually and you all always have an up-to-date Chromium browser with builds for Debian / Fedora.

Thoughts welcome! 8)

21
Operating Systems and Porting / Re: kernel config: page size 4k vs 64k
« on: February 04, 2021, 10:56:44 pm »
Hi, I was not discussing privacy concerns. Actually I'm quite happy with my Blackbird and the community here, which is very supportive of new and less tech savvy users like myself. Also, it performs quite well for my needs from a desktop. I agree with MauryG5 and ClassicHasClass that it's pointless to compare performance.

I appreciate very much the work you guys do at Raptor developing open hardware and wish you continued sucess.

Sincerely

No problem.  We're glad to hear you're happy with your Blackbird, and of course are always interested in where we do fall a bit short in real-world performance (and how to improve said shortcomings with software optimizations)!

22
Operating Systems and Porting / Re: kernel config: page size 4k vs 64k
« on: February 04, 2021, 12:32:11 pm »
Maybe Power9 is a better fit for HPC or TB HANA in memory DBs but not as a Desktop alternative, not taking into account the difficulty to find software for the architecture.

That's a bit of a stretch, don't you think?  Those Intel cores (and similar AMD ones) come with a mandatory signed binary blob on a secondary CPU that has full access to all your data.  In the worst case, you could simply be computing faster for an adversary by selecting the Intel solution.

Given the lack of those blobs is one of POWER's main reasons to be used on desktop, a more appropriate comparison for the specific purpose of determining POWER's usability as a desktop computer would be against other silicon that is also blob-free -- older Intel parts (Core Duo timeframe), or blob-free ARM devices (e.g. Rockchip).

If you want the fastest possible desktop with no regard for security, owner control, or privacy, then the simple fact is the latest AMD devices running Windows are your best bet.  For many of us, and especially here at Raptor, that represents such a large risk that we'd rather go back to pen and paper...

...much like the Justice Department just did here in the US, actually, after the SolarWinds proprietary / signed malware problems. ;D

23
Talos II / Re: Advice for installing OS via BMC?
« on: February 03, 2021, 03:16:07 am »
I'm new to Raptor systems, and I have been granted remote access to a Talos II machine. I need to install the OS, but haven't been successful. So far, I tried the Ubuntu 20.10 PPC64LE and Debian PPC64LE full CD installer over the virtual media, and from the serial connection, I can see the kernel crashes.  I have been able to get to the menus in the serial connection for the Debian network installer, but I don't know the network settings. Is it ok to reuse the BMC IP? Is it a safe assumption that the BMC shares the first Ethernet connection port? Next I'm trying Void Linux to see if that's an improvement.

Can you copy / paste the crash messages here so we can take a look?  We should be able to resolve the problem rapidly once we know what you're seeing.

Thank you!

24
Firmware / Re: Error Cloning Firmware Git Repo
« on: December 12, 2020, 04:50:10 pm »
Looks like LetsEncrypt updated their intermediate certificates, and the server hosting our GIT repos needed that certificate updated.  The intermediate certificate expiry seems to have primarily impacted a handful of command-line tools that require a full certificate chain to be served from the host server.

25
Operating Systems and Porting / Re: [NEWS] Linux kernel 5.8 is out!
« on: August 03, 2020, 11:22:12 pm »
Can you elaborate on this? Has IBM introduced proprietary/vendor-signed components to POWER10 firmware?

Nothing is signed, but IBM has failed to release required firmware components as open source software.  We can't go much further into details other than to say we're working the problem, but until it is resolved we will not be able to manufacture a POWER10 system, nor would we recommend usage of the POWER10 processor.

There's another area where IBM made a very poor choice, but that will become more obvious once IBM releases more data on their own systems using the POWER10 device.  That issue is also being worked by Raptor.

26
Operating Systems and Porting / Re: [NEWS] Linux kernel 5.8 is out!
« on: August 03, 2020, 07:08:38 pm »
We just wanted to re-post this from a comment we added to Talospace:

Quote
There will probably be some exciting announcements for POWER hardware late this year / early next. Not POWER10 yet (IBM made some very poor choices regarding POWER10 that currently block our products and that we continue to work to resolve) but POWER overall is looking quite healthy for the future. For now, POWER9 is definitely the best way to go to get an open, owner-controlled, powerful system with long term support and tons of distro choices!

Basically, POWER10 is an academic curiosity at the moment due to some really bad management-level decisions at IBM.  It's not unrecoverable, but we do want to set expectations of POWER9 remaining the highest performing POWER product for the 2021 / early 2022 timeframe.  If, and this is a fairly large "if", anyone else besides IBM ships a POWER10 system in that timeframe, the reasoning behind our decision should become quite clear.

The best way to help owner controlled computing at the moment is to keep buying and using POWER9.  The other announcements we have (which are not IBM dependent) should be very exciting, but POWER9 will remain king in terms of raw performance for now.

TLDR: POWER10 is not off the table by any means; we have every intention of creating a POWER10 product line, but there are complex negotiations in play to reach the point where those POWER10 products will be up to our high open firmware / open systems standards.  Such negotiations always take time, hence the delays, though COVID19 has stretched them out several times longer than normal such that public product announcements are now being affected.  Buying from another vendor in the interim, even if one exists, will not help and you definitely won't like what you actually get in the end from another vendor in comparison to the normal Raptor standards.

27
General OpenPOWER Discussion / Re: News?
« on: July 31, 2020, 03:52:38 pm »
Indeed, our Twitter feed is the main place we tend to post minor updates or news articles.  That said with the COVID19 situation we've been a bit less active with the global community overall; our intent is that once things return to more normal we'll be able to ramp up our social media and marketing again.

We miss you all at the face to face conferences; those were excellent venues for more niche product lines like ours and we have yet to find a viable substitute.  Here's hoping 2021 will bring back the more decentralized physical events (i.e. supplant the Google/Amazon/Microsoft/Intel/AMD-dominated online events) and we'll get you see you in person with some of the technologies we're working on for 2021 / 2022!

Side note: Condor was in fact cancelled due to COVID19.  We didn't want to have to do that, but economic concerns regarding launching a brand new product into a soft market with limited IBM support won out in the end.  We're focusing our efforts on other open, owner controlled, ppc64le technologies, so stay tuned!  8)

28

Can anybody comment on ideas or case studies for hosting with the Talos II platform?

For example:

What type of workloads is it most suitable for, or how would you build a Talos II-based rack mount system for different types of workloads?

Many hosting companies sell space by full rack, half rack, quarter rack (approximately) - how would you fit out one of these spaces if you had a pure Talos II strategy, even using the platform for firewall and BGP perhaps?

The largest vendors can provide next day and sometimes same day replacement parts, worldwide.  How would you approximate this with RCS products?  One idea that comes to mind: keeping one or two "community" servers in each rack for developers to log in and run tests, running Jenkins (a.k.a. travis-ci for POWER9) on the understanding that these servers can be scavanged on short notice to resolve production outages.

Is there any interest in hosting here in Switzerland right now?

This is an interesting discussion, thank you for starting it!

A couple of points we'd like to make:

1.) Our sister companies have been running racks of POWER servers for many years now, including Raptor Engineering and Integricloud.  The latter is US based but offers VPS and bare metal options; the reliability data for those machines has come back as very, very good.

2.) We can do custom (paid) support contracts for things like overnight replacement parts.   We just don't get that many organizations that feel they require it, so it's normally negotiated on a one-off basis.  Our suspicion is that many organizations try to keep spare parts on hand so as to avoid ending up in an emergency call out / parts acquisition scenario, but we don't have hard data to validate that.

29
We're aware of the port 2200 regression.  It's not something we had officially supported before (thus was not tested prior to release), but since it seems to be popular we're fixing it up and making it an official feature.

The patch re-enabling it is here:
https://git.raptorcs.com/git/talos-openbmc/commit/?id=9f113646e96372f18dfa7853d0ba9ebc031cdf6b

At some point in the future we will likely post built 2.01 beta BMC images with a few tweaks including this patch.


30
Condor / Re: Technical features
« on: February 18, 2020, 06:31:56 pm »
We have a general policy not to announce final design specifications until we are ready to launch the product for ordering.  Like many other corporations, we were affected by the global impacts of COVID-19 on various supply chains, and this product is currently delayed.

Pages: 1 [2] 3