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 - pocock

Pages: [1] 2 3 ... 17
1

You could send it to me.  Some of the things I do with GPU testing are not possible on my primary workstation because I don't want to crash my desktop.

2
Talos II / Re: Indium pads required for 18-core CPU on Talos II Lite?
« on: July 29, 2022, 03:19:53 pm »

For a question like this, I would strongly recommend sending a formal support request to Raptor

If they supplied the CPU then they are responsible for any issues that arise if you fry your CPU during the warranty period

Please ask them to document stuff like this publicly, it will help the next person to avoid asking the same question

3
Applications and Porting / Re: FFMPEG
« on: July 23, 2022, 04:37:13 pm »

Maybe some of the other users can get together and crowdfund this bounty so the developer can feed his family.

We can impersonate IBM and pay $50 each in IBM's place

If we pay IBM's bills for them, will they accuse us of violating their trademark?

4

Thanks for this feedback

Looking at the IBM doc, the STOP4 and subsequent states (STOP5, STOP11) have some similarities to S3 sleep.  They are not related to full hibernation/suspend.

For those states:

- are they supported in the Talos II / Blackbird firmware?

- are they supported in the Linux (or *BSD) kernels?

- do they require any special utilities in the userspace or desktop?

For a full hibernate / suspend to disk: that particular IBM doc doesn't really indicate whether hibernate is supported.

In the S3 sleep mode from the x86 world, similar to the POWER modes where some cores remain active, RAM continues to have power.

In the full hibernate, you can completely unplug the power supply.  All state from the CPU, RAM, hardware and GPU has been persisted on disk and all of those devices can recover their state when power comes back.

5
Applications and Porting / Re: FFMPEG
« on: July 10, 2022, 04:45:47 pm »

I had some communication with one of the developers who contributed a patch for one of these bounties

He said he did not receive payment

I feel very uncomfortable using ffmpeg if people have not been paid for their work

Personally, I found the unit tests did not pass, this implies that some more work may be necessary before the patch is merged.

https://fftrac-bg.ffmpeg.org/ticket/5570

On the other hand, if nobody looks at the patch from the developer or the feedback from other users then it is very unfair to the person who did the work.

6
Operating Systems and Porting / suspend, sleep, hibernate and resume?
« on: July 08, 2022, 08:24:44 am »

I saw a couple of threads with comments that the Raptor systems can't suspend or hibernate, this comment and this comment

I searched the wiki and it didn't have any pages about suspend, sleep, hibernate

Does anybody have more details about this?

In the event that hibernate is really impossible, are there any workarounds that people recommend for restoring desktop to a previous state after a complete shutdown?  For example, I've seen some utilities that can reopen windows on the same workspaces and in the same places but this doesn't solve everything.


7
Talos II / Re: Installing the system on a Samsung 980 Pro SSD 1TB
« on: June 25, 2022, 04:01:11 am »

I have the following setup

2x PM9A1 (the OEM version of the 980 Pro)

2× IB-PCI208-HS - Icy Box PCIe 4.0

Linux with btrfs RAID1

I use the Debian stable kernel rebuilt for the 4k page size as described in other discussions in this forum
5.10.0-8-powerpc64le-4k


I purchased the SSDs in October 2021

The system has currently been running 177 days without reboot

8
General OpenPOWER Discussion / Re: News?
« on: June 12, 2022, 06:47:45 am »

Raptor has made the motherboards to a high standard and most people seem to agree they will last a long time, hopefully long enough for RISC V to appear on our desktops too.



If you look at that comment, there is nothing in it to suggest an open RISC V will arrive imminently.  In fact, given that nobody is holding their breath for open RISC V, the comment could be seen as deliberately optimistic about Talos II boards running for years to come due to their quality.


we would advise against switching to blob-filled, proprietary platforms just to "hit back" at IBM.

There was nothing in the post to suggest people "hit back" at IBM

It is just a reality check, that is all.  We can see the way people started building Alma Linux and other continuations of CentOS.  That is not to "hit back" at Red Hat or IBM, they are building that because they need it and it was the right thing to do.

Given the communities are not so big, these situations do lead to people duplicating effort (e.g. Rocky Linux) and other inefficiencies that may have been avoidable.  Rather than having 3 or 4 forks of CentOS, developers doing exactly the same thing in parallel, it would be interesting if some of that developer effort went to POWER9 porting.

Speaking as a developer, I fully respect the right of any developer, whether it is a lone volunteer or a giant company like IBM to change their direction.  It then raises the question about how other people work around that.

For example, do you see the IBM POWER9 chips continuing to be available in sufficient quantities for the Raptor ecosystem?

Do you see any other manufacturer coming along with a 100% open chip to continue from POWER9?

The best way to keep things open in the short term, when also looking at long-term effects, would be to simply standardize the open software ecosystem on the POWER9 ISA vs. the POWER10 ISA.

Could you define that?  For example, which key software products need to commit to that statement?  In practice, how many of the developers on that part of the open source ecosystem are employed by IBM / Red Hat and could that take them down a POWER10 path?

...typing this from a Talos II workstation with Debian and Ungoogled Chromium installed

Does this mean the Chromium libs are now available for building other things?  If so, I might have another look at some projects that were pending for me to port.

9
General OpenPOWER Discussion / Re: News?
« on: June 11, 2022, 04:49:41 pm »
I think some of this is out of Raptor's control

There is widespread discussion elsewhere about IBM wrecking things in Red Hat, CentOS and Fedora, POWER10 not being 100% open and Google has been wrecking things in Debian.  Coincidentally, IBM and Google are the two key players in OpenPOWER.  I don't want to gripe about it, only to express what it may mean for everybody who already bought in to this platform.

They had an OpenPOWER room at FOSDEM, they accepted my talk and then they canceled it, this is incredibly nasty stuff.  We go to FOSDEM every year as volunteers.  It was online this year, the Google people don't have to look the volunteers in the eye because it is all remote so they brought this dirty behavior into FOSDEM.

On a platform like POWER where there are not so many developers to begin with you can't do stuff like that.  If people see one volunteer being hurt then ten other volunteers will avoid the platform.  People don't care who is right or wrong, when they get the feeling of conflict, they decide to give it a pass or come back and look again in 12 months.  That makes it much harder for Raptor to sell to volunteer developers.

Debian has started spending a lot of money on a lawsuit recently.  I don't want to hijack this thread with details of the lawsuit, you can download the dossier if you really want to, the only thing I want to emphasize is that 17 developers resigned.  15 of those developers were removed from the keyring on 7 June.  Most of them will probably not make any statement about their resignation, most people don't like to take sides but there is a cause and effect: when conflict starts, some people quit.

This is all out of Raptor's control of course but it is a risk to the platform.

Personally, having contributed to patching packages for POWER9, I'm optimistic that lessons learnt from porting work on this platform will be easily transposed to ARM64 and RISC V.  Raptor has made the motherboards to a high standard and most people seem to agree they will last a long time, hopefully long enough for RISC V to appear on our desktops too.


10
There are some hints about multi-seat setups in other topics in the forum

Multi-seat can make the workstations more viable because the cost is shared between two or three users.

I had some discussions about this with a few people.  Most people are satisfied that POWER9 provides enough compute capacity but there were some practical concerns

The type of user who would benefit from this setup is typically a developer, system administrator or IT support worker who already works in Linux

By their nature, this type of user would like to tweak the system, for example, installing some kernel module, installing some non-standard version of some development header files or whatever.

What level of isolation can be achieved between users in such scenarios?

For example, using virtualization, people can have their own kernels and separate GPU ports.

Using LXC and cgroups, people can have their own root filesystem but they share a kernel

Has anybody tested these possibilities with POWER / Linux workstations or even on x86?

I found some links about the topic for some of the distributions that people are using

Hardware passthrough in LXC or running a desktop in a cgroup

two X servers one graphics card

Debian - Multi Seat

Fedora - Multi Seat

Arch - Multi Seat

FreeBSD - Multi Seat

11
The PCIe capabilities of these cards make them a very good match for Talos II at a hardware level so it is sad that nothing happened.

I suspect AMD would tell us that it is easier for us to buy their Ryzen processors and they might not make the effort on these drivers for non-x86 users

IBM, who make both the POWER9 and own Red Hat recently wasted a lot of money on an attempted reverse-domain-name-hijacking.  If they stopped giving the money to lawyers and gave it to real developers then some of us would probably spend the time to fix the GPU drivers.

12
There is one bug open against kernel 5.10.x, if anybody can try the card with a newer kernel like 5.15.x that would be helpful

13
Has anybody tried any of these cards with a recent kernel?

Does the kernel command line option mentioned on the wiki here make any difference?

Code: [Select]
amdgpu.aspm=0

14
I wouldn't care. Because the maintainers of Fedora (sharkcz is on this forum) are aware of the problem. If they don't feel the need to offer 4K kernels, so be it...

That's the blessing of open source, you can choose whatever you like.

Given the POWER eco-system is smaller compared to the overall eco-system, the choices are not so wide and the POWER development teams in each distribution are relatively limited in what they can do

The commit below doesn't credit people who spent time identifying the root cause of the problem, that is not a blessing at all.  It verges on plagiarism.

And it seems the problem is fixed?
Commit 5234de6c797565815ece9321b1dfe2e6732b5090
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.101

15

There is an update on the Fedora situation today

A legal panel has declared that rogue elements of Fedora committed harassment and abuse, this is what is effectively slowing down my work to help Fedora users on POWER

Here is my blog about it

Here is the verdict from the panel

It is interesting to note that when people immersed in the open source space make accusations of harassment, they are usually very biased and swayed by conflicts of interest and personal relationships.

The verdict on Fedora was made by an outside observer so it is more credible than a code of conduct.

Pages: [1] 2 3 ... 17