Messages

106

GPU Compute / Accelerators / Re: AMD rendering issues with Debian Bullseye

« on: July 18, 2021, 04:32:59 pm »

Tried lxde + lightdm

The greeter runs okay and can actually log into an LXDE session. However, the background is black and window opened are not rendered properly. Moving them around produces this effect reminiscent of Windows XP:

(The black is erased revealing the actual Debian background and unrendered parts of open windows)

Tried lightdm + gnome
Can at least select Xorg or standard wayland gnome, same issue with failing to open the gnome session.

Debian 10 Buster
Lastly, I tried installing Buster again using the exact same ISO used when I originally set things up back in 2019.

Superblock last mount time is in the future
by less than a day, probably due to the hardware clock being incorrectly set.
Loads first part of gdm (black screen + cursor) and then exits to systemd(?) output:
([ OK ] ...
stops at [ OK ] Started GNOME Dsiplay Manager.

Interestingly, while first trying to boot the Debian 10 installer, and once in petitboot shell, I discovered "^[[25~" constantly being inputted as though a key is being held down. I tried different keyboards and it seems to occur regardless. Interesting since X11 logs had been complaining about keyboard input issues on the previous above ebian 11 installs.

Noticed in IPL startup output
Failed loading ucode lid 0x203d1

Failed BOOTKERNEL verification

I don't actually remember if this used to appear before I reflashed the PNOR, as I'd always disabled VGA for a discrete GPU.

tl;dr
I suspect that this issue derives from having flashed the PNOR earlier to correct a failed petitboot password change. None of these things were occurring until after I did that. I don't know nearly as much as some other Talos and Blackbird users, but I wonder if this could be from mismatched BMC and PNOR firmware versioning.
I recall my board arriving with an insert about how this is from a batch with "1.01" but am uncertain if that meant a hardware revision or the installed firmware revision. The only available pre-built PNOR image is 1.00. I know that Raptor advise against flashing BMC firmware during these supply shortages but I'm kind of backed into a corner here, and the system really isn't usable as it currently stands.

107

Applications and Porting / Re: OpenVPN Client for ppc64el

« on: July 13, 2021, 05:46:42 pm »

They should be right here, assuming you are on Fedora.

"Fedora:

    Building with OpenSSL (recommended):

    # yum install openssl-devel

    Building with mbed TLS (alternative):

    # yum install mbedtls-devel

    Generic build requirements:

    # yum install gcc-c++ git autoconf autoconf-archive automake make pkgconfig glib2-devel jsoncpp-devel libuuid-devel libcap-ng-devel selinux-policy-devel lz4-devel zlib-devel libxml2 tinyxml2-devel python3-dbus python3-gobject python3-pyOpenSSL python3-jinja2 python3-docutils python3-dbus bzip2 polkit

    Clone this git repository: git clone git://github.com/OpenVPN/openvpn3-linux
    Enter the openvpn3-linux directory: cd openvpn3-linux
    Run: ./bootstrap.sh
Completing these steps will provide you with a ./configure script."

108

GPU Compute / Accelerators / Re: AMD rendering issues with Debian Bullseye

« on: July 13, 2021, 05:37:42 pm »

Have not yet tried non-Debian, but I did just try a clean install with Debian Sid instead. I made no changes other than the following:

• Install Debian, add non-free repos and installed firmware-amd-graphics.
  
• Appended amdgpu to /etc/initramfs-tools/modules

Code: [Select]

sudo update-initramfs -u

• Added modprobe.blacklist=ast video=offb:off console=tty0 to GRUB_CMDLINE_LINUX

Code: [Select]

sudo update-grub

• Rebooted

Code: [Select]

sudo apt install gnome-session
After restarting, the same issue occurrs, arriving at the login screen:

Login fails and seems to restart gdm3. Same with gnome desktop from Tasksel, or gnome-core meta package. So I highly suspect this is a Gnome issue rather than a AMD GPU or Raptor Blackbird issue.

109

GPU Compute / Accelerators / Re: AMD rendering issues with Debian Bullseye

« on: July 11, 2021, 05:17:31 pm »

I have reverted all my changes on /usr/share/X11/xorg.conf.d/00-noglamoregl.conf and /etc/X11/xorg.conf.d/21-gpu-driver.conf, and found that the system still boots to gdm3 with no text rendering.
I may have misattributed the cause.

syslog shows errors for gnome-session and gdm:

gnome-session-binary[]: WARNING: Failed to upload environment to systemd: GDBus.Error: org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
gnome-session-binary[]: WARNING: Falling back to non-systemd startup procedure due to error: org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist

I have made sure that systemd-logind is running

110

GPU Compute / Accelerators / AMD rendering issues with Debian Bullseye

« on: July 10, 2021, 06:38:14 pm »

I have been struggling with getting a graphical session (Gnome, or Sway) running under Debian Bullseye. The system is a Blackbird with RX560. After installing firmware-amd-graphics, disabling the AST and setting amdgpu in initramfs modules, the system gets display but crashes out of Gnome GUI.

I have tried setting a default GPU per select desired GPU at runtime. And disabled GLAMOR with the relevant portion of this since it was also erroring about GL_OUT_OF_MEMORY for glamor.

This allowed GDM to now start, however text fails to render and login fails, always returning to the GDM login prompt. Aside from the text, everything looks okay in the GUI so I am confident that the GPU is working at least. It looks like the screen needs to be selected, according to xorg logs:

[     3.162] (==) No Layout section.  Using the first Screen section.
[     3.162] (**) |-->Screen "Screen0" (0)
[     3.162] (**) |   |-->Monitor "<default monitor>"
[     3.163] (**) |   |-->Device "GPU1"
[     3.163] (**) |   |-->GPUDevice "GPU1"
[     3.163] (==) No monitor specified for screen "Screen0".
        All GPUs supported by the amdgpu kernel driver
[     3.175] (EE) No devices detected.
[     3.176] (EE)
Fatal server error:
[     3.176] (EE) no screens found(EE)
[     3.176] (EE)

Has anybody gotten Bullseye up and running with an AMD card? And how do you determine the correct screen to select?

111

General OpenPOWER Discussion / Re: risks associated with Xorg / Wayland

« on: July 01, 2021, 10:12:56 pm »

I shelved the device, temporarily, while I examine resolutions. I had been using Debian 10 under Gnome's Wayland implementation without issue previously.

With the new installation (Debian 11) I recall seeing "Potential missing firmware" relating to AMDGPU in apt actions, despite having firmware-amd-graphics installed and amdgpu added to initramfs (as I had done on Debian 10), so there may be something I am missing or some regression. I'll start poking around at it soon, I just had to scramble to get a fallback computer up and running.

112

General OpenPOWER Discussion / Re: risks associated with Xorg / Wayland

« on: July 01, 2021, 06:02:48 pm »

Addendum to my last post:

I have found Debian 11 so far to be unusable on RCS Blackbird with graphical environments. When loading up Sway WM, the screen renders but transparent objects were showing as opaque and the lines in my terminal emulator where displaying incorrectly.

'Alright, no skin off my back, I'll just use Gnome' I thought. After installing and starting gdm, the session immediately crashes out with a very generic error.

I next removed the GPU to see if I could tolerate using the ASPEED. It is stuck at a maximum of 1024x768 

I am currently weighing my options.

113

General OpenPOWER Discussion / Re: News?

« on: July 01, 2021, 05:53:22 pm »

The integrated audio on the Blackbird is weak on lows and bass, and the mic input needs to be turned all the way up seemingly. So you're not missing much in that regard. Like you, I am patiently awaiting more Blackbird stock. It would be neat if RCS could share which parts are holding up the process, so at least we could monitor component stock through customs channels. Its a shame that these made-in-USA boards all use parts from overseas anyway.

114

General CPU Discussion / Re: max memory speeds

« on: July 01, 2021, 05:40:12 pm »

A recent personal catastrophe has had me scouring the wiki, and I've discovered that the firmware version may be a limiting factor. I cannot confirm this at the moment, as my system is currently in the dry dock.

EDIT: Found the same to be true for the Talos firmware.

Enable 2666MHz DDR4 memory DIMMs

115

User Zone / Re: Forgotten Petiteboot menu password

« on: July 01, 2021, 05:15:42 pm »

A brief follow up to this: I have flashed the PNOR/Openpower firmware chip and found it to clear the passphrase. I now have access to the device boot settings again. In case this happens for some other unfortunate individuals, I will detail the process below.

Unofficial guide: Forgotten petitboot menu credentials, but still have BMC access.

Requires:

• A helper computer (of reasonable trustworthiness, your BMC creds will be traversing through here!)
• Ethernet and possibly a router which will never touch the public internet afterward
• The OpenPOWER firmware for your PNOR flash chip, verified with GPG.

Establish that you can first log into the BMC. If you were foolish, like me, and forgot which static IP it was set to, run nmap from your helper computer. Assuming you know the range was set within 10.0.10.* for example:

Code: [Select]

nmap -v 10.0.10.1/24The helper computer (or router between the two computers) should be set to this same address space.

Acquire the Openpower firmware, verify and decompress it, then copy the .pnor (or .bin if 1.00 series) to the helper system.

Following the steps outlined in the wiki, transfer the firmware image:

Code: [Select]

my_helper_pc$ scp NAME_OF_DECOMPRESSED_FILE.pnor root@$10.0.10.99:/tmp/
Log into the BMC and apply the new firmware, following the wiki steps:

Code: [Select]

root@blackbird:~# pflash -E -p /tmp/NAME_OF_DECOMPRESSED_FILE.pnor

Code: [Select]

root@blackbird:~# pflash -P CVPD -c
The process will take a couple minutes to complete. Let the system restart, you will find that you can now set new petitboot menu credentials.

Some take away from this:
The prompt for setting/resetting petitboot menu credentials does not ask for multiple inputs to check against typos. And it also does not show the characters (*) as you type. This is essentially flying blind and you need to be absolutely careful what is entered in this form.

116

Blackbird / Re: [SELL] 2 x 8GB DDR4 ECC stock RAM

« on: June 20, 2021, 10:36:20 pm »

Do Raptor systems even support memory at 2666 speeds yet? The PNOR limits to 2400 according to the wiki.

117

User Zone / Forgotten Petiteboot menu password

« on: June 20, 2021, 08:26:09 pm »

I have idiotically reset the passphrase on my Blackbird (1.01 firmware) and can no longer make changes since I don't really know what I've set it to. Will resetting this require a serial cable? I see some resources saying it might be possible through ipmitool.

Update: I have found that I can still log in on BMC over ethernet. Just looking to figure out how to reset the petiteboot passphrase from here.

118

Applications and Porting / Re: How to build Barony Game

« on: June 14, 2021, 11:20:58 pm »

Very much. I only go out of my way to build from source is a game is particularly interesting.

119

Applications and Porting / How to build Barony Game

« on: June 13, 2021, 03:05:15 pm »

I have finally gotten around to building Barony from source. No changes need to be made as it builds and runs just fine on Power. However, the instructions are a little incomplete, so I thought I would share here for the other 3 people on Earth who play this and also use PowerPC.

Adapted from their resources:

Code: [Select]

apt install libsdl2-dev libsdl2-image-dev libsdl2-net-dev libsdl2-ttf-dev libpng-dev libz-dev libphysfs-dev rapidjson-dev

git clone https://github.com/TurningWheel/Barony.git

mkdir build && cd build
The OpenAL bit is important, otherwise it will have no sound.

Code: [Select]

cmake .. -DOPENAL_ENABLED=ON

cd ../

make -j 4
Should create barony: ELF 64-bit LSB pie executable, 64-bit PowerPC or cisco 7500, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld64.so.2, for GNU/Linux 3.10.0, BuildID[sha1]=3923290b782f5cac6359a315534a6b79471522ee, not stripped

Next, pull in the game resources:

Code: [Select]

wget https://github.com/TurningWheel/Barony/releases/download/V3.3.7-dev/tmp-master-assets.zip

unzip tmp-master-assets.zip
From your copy of Barony, the following asset directories will need to be copied into the same directory as the barony executable; books, images, items, maps, models, music, sound.

Code: [Select]

./barony to play

120

Operating Systems and Porting / Re: Ubuntu anomalies on Power

« on: April 28, 2021, 09:40:21 pm »

Just taking an uneducated guess but try disabling the Firefox apparmor profile.