Raptor Computing Systems Community Forums (BETA)
Software => User Zone => Topic started by: MPC7500 on December 09, 2019, 06:39:13 am
-
Hello,
in Fedora is there a GNOME shell extension for IPMItool? At the moment I'm using Sensors GNOME shell extensions, but as you know without fan RPMs.
-
I'm running Fedora 31. Try sudo ipmitool sdr . Works here.
-
IPMITool works, but what about a GUI, like this (https://extensions.gnome.org/extension/1145/sensory-perception/) one?
-
I use https://extensions.gnome.org/extension/120/system-monitor/ personally. It's not perfect but it does give me temperature and fan rpm.
-
This I have tried. How did you lm_sensors working? lm_sensors doesn't detect any sensor.
-
I don't recall doing anything special, tbh. This is on a Talos II; I don't know if it's different for a Blackbird but IIRC it "just worked."
-
here I get the ibmpowernv kernel module automatically loaded to get sensors, on both Talos and Blackbird (but I don't use Fedora). Interestingly, on a POWER8, the same module also provided sensors, but did not get automatically loaded
-
Is there a bug in GNOME? If I select GNOME on the installer, I don't get a login screen after installation. I even can't switch to the console, mouse doesn't react.
-
Yes I confirm this your feedback. I could see that there is a big bug in GNOME version 3.34 for PPC64el. The problem lies precisely in GNOME as the problem also occurs on Ubuntu as well as on Fedora and is the same problem. Me if I noticed by chance, when I installed the first time Ubuntu 19.10, after downloading the GNOME 3.34, rebooting the system, just loaded it all, it irreversibly stopped everything. I had to reboot and realized that there was a big problem and since it worked in server mode, I immediately realized that it could be the GNOME 3.34. Then I installed Fedora 31 as soon as it came out and did the same procedure as the 30 or after installing the server version, I installed the XFCE package. I started Fedora 31 and everything was ok. At that point I decided to install the GNOME 3.34 and after the start there were no problems whatsoever. I realized that my suspicions were well founded when, due to a mistake, I had to reinstall Fedora. Yes, because this time I put the GNOME first as a desktop environment and as soon as I restarted Fedora froze exactly the same way as Ubuntu. At that point I had confirmation of the GNOME problem. At the same time, however, I realized that if you install the XFCE first and then from inside that, put GNOME then the problem doesn't exist and it works. If instead you want to put GNOME from the beginning, then everything stops irreversibly. At that point I also understood that Ubuntu could work in the same way and in fact after the server installation ranking, I put XFCE, then GNOME and so I also made Ubuntu 19.10 work ...
-
Is there a bug in GNOME? If I select GNOME on the installer, I don't get a login screen after installation. I even can't switch to the console, mouse doesn't react.
Wayland or X? If it's Wayland, that might be your problem. See https://www.talospace.com/2019/11/fedora-31-mini-review-on-blackbird-and.html
-
Classic excuses a question, or rather 2, in the article dedicated to Firefox 70 advised to tell Firefox that we are using Power 9, can you write the precise syntax of the command to give to get this? Second question, I'm looking for an application to be able to read Blu-Ray discs correctly, VLC isn't currently on Power, do you know what you can use as an alternative? Thanks
-
Wayland or X? If it's Wayland, that might be your problem. See https://www.talospace.com/2019/11/fedora-31-mini-review-on-blackbird-and.html
Thanks. I will look into it. On the installer, I select "Fedora Workstation". After reboot, I got a blank screen without login window. So I can't choose X or Wayland. Even Ctrl + Alt + F2 doesn't work.
Surprisingly, a few weeks ago the update from 30 to 31 worked without any problems. Now neither a Clean Install nor the update from 30 to 31 works. The same error.
I remember using the GNOME Tweak tool under 30.
-
Replying to two posts:
Wayland or X? If it's Wayland, that might be your problem. See https://www.talospace.com/2019/11/fedora-31-mini-review-on-blackbird-and.html
Thanks. I will look into it. On the installer, I select "Fedora Workstation". After reboot, I got a blank screen without login window. So I can't choose X or Wayland. Even Ctrl + Alt + F2 doesn't work.
Have you tried installing Server, and then converting to Workstation? This comes up with a text boot, but then you can "startx" to go to GNOME. That's how this T2 is configured.
Still, I agree this sounds like a bug.
Classic excuses a question, or rather 2, in the article dedicated to Firefox 70 advised to tell Firefox that we are using Power 9, can you write the precise syntax of the command to give to get this? Second question, I'm looking for an application to be able to read Blu-Ray discs correctly, VLC isn't currently on Power, do you know what you can use as an alternative? Thanks
I mean to tell the compiler you're using POWER9. If you're just running a pre-built version, then it's however it was configured and assuming the autodetect works properly. (It should on the Fedora builds.)
However, VLC is definitely in the repositories. Make sure you have RPM Fusion connected up. https://rpmfusion.org/Configuration
BD playback may require some bits that Raptor may be nervous about us posting, so just read the Arch Linux documentation about that. https://wiki.archlinux.org/index.php/Blu-ray
-
yes I just installed it and it works, I also asked in the discussion dedicated to the software and MPC published the procedure thanks to which I installed VLC. The only problem is that I can't see Bluray, I was trying to make AACS work, the library for this task, but I still couldn't do it. I need to figure out how to enable it. Thanks for the link I'm going to take a look
-
We would ask that you please refrain from any discussion on decrypting commercial DRM-protected media on these forums. While we are aware that legality varies worldwide, we are US based and this is not something we can tolerate on these boards as a result.
Our official stance is to obtain the media in non-DRM protected form -- for instance, record it from an OTA TV showing (most ATSC/DVB tuners work great wirh unencrypted broadcasts on POWER including software like MythTV), or to simply play the media on an authorized device (i.e. a standalone Bluray player).
It also wouldn't hurt overall to let the studios know you're wanting to purchase a DRM-free version of the movie since you won't be giving them access to your personal data on your PC just to watch a movie. Having a higher priced DRM-free variant of a movie (compare CD audio to Sirius, for example) has been something we've wanted the studios to consider for a long time.
-
Have you tried installing Server, and then converting to Workstation? This comes up with a text boot, but then you can "startx" to go to GNOME. That's how this T2 is configured.
Still, I agree this sounds like a bug.
Yes, this I have tried, too. On the installer I selected network installation, then selected the Fedora minimal installation. Reboot is successfully. Then I enter:
sudo yum groupinstall "Fedora Workstation", got the following messages:
No match for group package "xorg-x11-drv-intel"
No match for group package "xorg-x11-drv-omap"
No match for group package "virtualbox-guest-additions"
No match for group package "mcelog"
No match for group package "xorg-x11-drv-vesa"
No match for group package "totem-nautilus"
No match for group package "xorg-x11-drv-armsoc"
No match for group package "xorg-x11-drv-openchrome"
No match for group package "open-vm-tools-desktop"
No match for group package "hyperv-daemons"
No match for group package "microcode_ctl"
No match for group package "xorg-x11-drv-vmware"
Error:
Problem: problem with installed package fedora-release-31-2.noarch
- package fedora-release-31-2.noarch conflicts with system-release provided by fedora-release-workstation-31-1.noarch
- package fedora-release-workstation-31-1.noarch conflicts with system-release provided by fedora-release-31-2.noarch
- package fedora-release-31-1.noarch conflicts with system-release provided by fedora-release-workstation-31-1.noarch
- package fedora-release-workstation-31-1.noarch conflicts with system-release provided by fedora-release-31-1.noarch
- conflicting requests
- package fedora-release-31-2.noarch conflicts with system-release provided by fedora-release-workstation-31-2.noarch
- package fedora-release-workstation-31-2.noarch conflicts with system-release provided by fedora-release-31-2.noarch
- package fedora-release-workstation-31-2.noarch conflicts with system-release provided by fedora-release-31-1.noarch
- package fedora-release-31-1.noarch conflicts with system-release provided by fedora-release-workstation-31-2.noarch
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)
Then I tried: yum groupinstall gnome-desktop and got this message:
No match for group package "totem-nautilus"
But I'm able to proceed with the installation.
After reboot, I enter startx and got the following message:
xauth: file /root/.serverauth.2074 does not exist
xauth: file /root/.Xauthority does not exist
xauth: file /root/.Xauthority does not exist
X.Org X Server 1.20.6
X Protocol Version 11, Revision 0
Build Operating System: 5.2.7-100.fc29.ppc64le
Current Operating System: Linux power9.fritz.box 5.3.15-300.fc31.ppc64le #1 SMP Thu Dec 5 14:47:38 UTC 2019 ppc64le
Kernel command line: root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet
Build Date: 25 November 2019 12:00:00AM
Build ID: xorg-x11-server 1.20.6-1.fc31
Current version of pixman: 0.38.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 16 01:50:54 2019
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
pci id for fd 12: 1a03:2000, driver (null)
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
Edit:
I tried: yum groupinstall base-x and got this messages:
No match for group package "xorg-x11-drv-vmware"
No match for group package "xorg-x11-drv-intel"
No match for group package "xorg-x11-drv-omap"
No match for group package "xorg-x11-drv-armsoc"
No match for group package "xorg-x11-drv-vesa"
No match for group package "xorg-x11-drv-openchrome"
But could proceed. At the end, same error message.
cat /var/log/Xorg.0.log:
https://pastebin.com/uxzHx1RV
Edit2: From my pastebin:
[ 175.383] (WW) Warning, couldn't open module ast
[ 175.383] (EE) Failed to load module "ast" (module does not exist, 0)
[ 175.398] (WW) Falling back to old probe method for fbdev
[ 175.744] (EE) modeset(0): glamor initialization failed
-
I after installing Fedora server, both with 30 before and after 31, I have always performed this procedure.
1 dnf group install xfce
2 dnf install xorg-x11-drv-evdev lightdm
3 systemctl set-default graphical.target
4 system enable lightdm.
With these 4 commands you install XFCE, then from inside the XFCE simply install the GNOME and run the GNOME bug itself.
-
This I know, thanks.
-
We would ask that you please refrain from any discussion on decrypting commercial DRM-protected media on these forums. While we are aware that legality varies worldwide, we are US based and this is not something we can tolerate on these boards as a result.
Our official stance is to obtain the media in non-DRM protected form -- for instance, record it from an OTA TV showing (most ATSC/DVB tuners work great wirh unencrypted broadcasts on POWER including software like MythTV), or to simply play the media on an authorized device (i.e. a standalone Bluray player).
It also wouldn't hurt overall to let the studios know you're wanting to purchase a DRM-free version of the movie since you won't be giving them access to your personal data on your PC just to watch a movie. Having a higher priced DRM-free variant of a movie (compare CD audio to Sirius, for example) has been something we've wanted the studios to consider for a long time.
Excuseme but I don't understand what you're referring to specifically! I have only said and asked to have information on how to install VLC as I was not able to find it and then I wrote that I wanted to understand how to make everything work better with Bluray, I do not think I have altered anything, I only use ORIGINAL software for DVDs and Bluray so if you think I'm asking for information for non-original material to play you're wrong and very pure! Reproducing original material can be done in any place, both home reader and computer reader, so I repeat I don't understand what your problem is sincerely ... If there is something that has translated badly then it is another matter, using the translator of Google doesn't always come out exactly as you write it, but I don't see it myself ...
-
Excuetce but I don't understand what you're referring to specifically! I have only said and asked to have information on how to install VLC as I was not able to find it and then I wrote that I wanted to understand how to make everything work better with Bluray, I do not think I have altered anything, I only use ORIGINAL software for DVDs and Bluray so if you think I'm asking for information for non-original material to play you're wrong and very pure! Reproducing original material can be done in any place, both home reader and computer reader, so I repeat I don't understand what your problem is sincerely ... If there is something that has translated badly then it is another matter, using the translator of Google doesn't always come out exactly as you write it, but I don't see it myself ...
Most likely this got lost in translation.
In the US there is conflicting law, one law states that you are not even allowed to decrypt original media for playback if it was encrypted (e.g. commercial BluRay). Due to that law (the DMCA), we cannot allow discussion of how to break encryption (even for interoperability / playback of original media) on these forums.
If you are playing unencrypted BluRay data disks (e.g. mkv data from a camera, etc.) of course that discussion is not a problem here.
-
This I know, thanks.
I'll bug Dan Horak about this, it might be known.
Actually, one last thought: any difference with
dnf install @workstation-product-environment
? Or any of the suggestions on https://docs.fedoraproject.org/en-US/quick-docs/switching-desktop-environments/ ?
-
Best way to install a desktop for a Power machine is to start from the Everything netinstall ISO, it will offer you all desktops in the installer GUI.
Regarding the "release" conflict, does it go away when you pass "--allowerasing" option to dnf (as suggested)? Also as this is nothing specific to Power I suppose it has been discussed on regular user focused Fedora forums already.
-
Hi Dan,
thanks for register.
I'll start at the beginning. I had Fedora 30 "Workstation" installed. After Fedora 31 came out, I did the update through the GNOME Store, all without any problems.
A few days ago I wanted to try something different and I deleted Fedora. Then I reinstalled Fedora 30 and did the update via the GNOME Store again.
Then I had the problem that after the update to 31 no login window appears, only a blank screen.
If I now install a minimal Fedora and then Fedora Workstation (--allowerasing or --skip-broken does the job) on top, then after running startx I get the message that an error occurred and I have to log out again.
As MauryG5 wrote before, another DE can be installed without problems. In my opinion it must have something to do with GNOME and or in combination with ASpeed.
I used the "netinstall.iso" and then the "Install-over-network" option. But I can also try Everything.
What surprises me is that the first time the update worked through the GNOME Store. Not the second time. The only difference was IIRC, that the first time I used the two snippets and the GNOME Tweak Tool. The snippets were "Xorg crashes or is laggy with the AST VGA GPU" and "Low Resolution".
The previous error messages can be found above.
I can use the workaround with the other DE, but that's not really a solution for the problem.
Actually, one last thought: any difference with
dnf install @workstation-product-environment
? Or any of the suggestions on https://docs.fedoraproject.org/en-US/quick-docs/switching-desktop-environments/ ?
Sadly no difference. Same error messages/ problem.
-
In my opinion if you install xfce first and then from inside xfce give the commands to install gnome, the problem no longer exists. I didn't have any problems doing this and I'm still using Fedora 31 with GNOME. Same for Ubuntu, if you install gnome directly from the server version, just reload with gnome nothing works and crashes irreversibly if instead you install it from xfce then restarting it works great and gives you no more problems.
-
As I said above, to install two DEs to get GNOME working isn't a solution for me.
@sharkcz: Everything (source: media -> Fedora Workstation) doesn't work either. After reboot I got a blank screen with a frozen mouse. I even can't login via ssh (connection refused). On installation I selected ssh root login with password allowed. Alt + Ctrl + F2 doesn't work also.
-
only at the moment I think there is no other solution because as I said in the previous posts there is a big bug in GNOME 3.34 and I don't even know if they know that there is this problem. Can you wait and solve the problem? How much time will pass? I think you should do as I did, xfce doesn't weigh and it's a good alternative in my opinion ... then you do ...
-
Now I'm back on Fedora Workstation 30 again, without any problems. Tomorrow I'll try to set it up the way I did. And then updated to 31. Let's see if it works then.
-
be very careful because the first time it happened to me to update Ubuntu from 19.04 to 19.10. Having installed the Gnome by default, when the system updates, automatically downloads and installs the Gnome 3.34 and if they have not yet corrected the problem, as soon as you restart with the updated system, once you get to the login screen you will be irreversibly blocked and you will not be able to do anything else that re-install everything ... The problem as I said earlier is with Gnome, not Fedora or Ubuntu. He does it in all the distros that have the possibility to install the Gnome 3.34 ... Siteadmin, excuse me then, I was not aware of this thing from you in America. With us if you reproduce original material then there are no problems and you can talk about it freely ... I didn't know
-
Wayland or X? If it's Wayland, that might be your problem. See https://www.talospace.com/2019/11/fedora-31-mini-review-on-blackbird-and.html
Thanks for the link, BTW. At the end this was the only solution.
-
Is there a bug in GNOME? If I select GNOME on the installer, I don't get a login screen after installation. I even can't switch to the console, mouse doesn't react.
I have managed to install Gnome with Ubuntu Server 19.10 directly without installing Xfce first:
* Boot recovery from petitboot and open the root shell
* Install lightdm (replacing gdm3 which seems to have problems): sudo apt-get install lightdm* Reboot
For a detailed description of Ubuntu Server 19.10 installation, findings and solutions see my raptor wiki page (work in progress) at https://wiki.raptorcs.com/wiki/User:FlyingBlackbird (https://wiki.raptorcs.com/wiki/User:FlyingBlackbird).
-
Is there any way to enable a suspend-mode in Fedora? Because, when I press the suspend button I get a black screen. Power consumption drops from 54W to 51W. My guess, only the AST is suspended? Then I couldn't wake up the computer again.
I have also read: Unlike the previous architecture of the POWER8 processor, POWER9 processor only supports one instruction to enter idle state. POWER ISA (Instruction Set Architecture) has been revised to remove legacy idle state instructions (nap, sleep, winkle). A new instruction, 'stop', has been added for this purpose to the ISA.
An Overview of Idle States in the POWER9 Processor (https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Power%20Systems/page/An%20Overview%20of%20Idle%20States%20in%20the%20POWER9%20Processor)
-
Not that I'm aware of, or at least it doesn't seem to make any difference.
-
Is there any way to enable a suspend-mode in Fedora? Because, when I press the suspend button I get a black screen. Power consumption drops from 54W to 51W. My guess, only the AST is suspended? Then I couldn't wake up the computer again.
I have exactly the same problem on Ubuntu 19.10 (and Fedora 31 as well) - also with almost no reduction of power consumption and a dead black screen - and seen no solution so far...
-
Is it possible that the kernel module ibmpowernv is not available under Fedora?
I wonder how then ClassicHasClass gets the fan sensors displayed on it?
-
% sudo dnf install lm_sensors
Last metadata expiration check: 0:00:12 ago on Thu 06 Feb 2020 08:23:56 PM PST.
Package lm_sensors-3.5.0-6.fc31.ppc64le is already installed.
Dependencies resolved.
Nothing to do.
Complete!
% sensors
ibmpowernv-isa-0000
Adapter: ISA adapter
Chip 0 Vdd Remote Sense: +1.00 V (lowest = +0.67 V, highest = +1.01 V)
Chip 0 Vdn Remote Sense: +0.72 V (lowest = +0.72 V, highest = +0.72 V)
Chip 8 Vdd Remote Sense: +0.93 V (lowest = +0.63 V, highest = +0.94 V)
Chip 8 Vdn Remote Sense: +0.69 V (lowest = +0.69 V, highest = +0.69 V)
Chip 0 Vdd: +1.01 V (lowest = +0.68 V, highest = +1.01 V)
Chip 0 Vdn: +0.72 V (lowest = +0.72 V, highest = +0.72 V)
Chip 8 Vdd: +0.94 V (lowest = +0.64 V, highest = +0.94 V)
Chip 8 Vdn: +0.69 V (lowest = +0.69 V, highest = +0.69 V)
Chip 0 Core 0: +56.0°C (lowest = +7.0°C, highest = +80.0°C)
Chip 0 Core 4: +65.0°C (lowest = +6.0°C, highest = +80.0°C)
Chip 0 Core 8: +55.0°C (lowest = +8.0°C, highest = +82.0°C)
Chip 0 Core 12: +55.0°C (lowest = +8.0°C, highest = +80.0°C)
Chip 8 Core 16: +50.0°C (lowest = +21.0°C, highest = +65.0°C)
Chip 8 Core 20: +43.0°C (lowest = +22.0°C, highest = +65.0°C)
Chip 8 Core 24: +43.0°C (lowest = +22.0°C, highest = +67.0°C)
Chip 8 Core 28: +43.0°C (lowest = +5.0°C, highest = +81.0°C)
Chip 0 DIMM 0 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 1 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 2 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 3 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 4 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 5 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 6 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 7 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 8 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 9 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 10 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 11 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 12 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 13 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 14 : +47.0°C (lowest = +32.0°C, highest = +56.0°C)
Chip 0 DIMM 15 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 0 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 1 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 2 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 3 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 4 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 5 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 6 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 7 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 8 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 9 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 10 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 11 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 12 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 13 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 14 : +33.0°C (lowest = +25.0°C, highest = +42.0°C)
Chip 8 DIMM 15 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 Nest: +55.0°C (lowest = +24.0°C, highest = +61.0°C)
Chip 8 Nest: +43.0°C (lowest = +22.0°C, highest = +59.0°C)
Chip 0 VRM VDD: +50.0°C (lowest = +33.0°C, highest = +57.0°C)
Chip 8 VRM VDD: +36.0°C (lowest = +27.0°C, highest = +47.0°C)
Chip 0 : 38.00 W (lowest = 26.00 W, highest = 75.00 W)
Chip 0 Vdd: 11.00 W (lowest = 0.00 W, highest = 47.00 W)
Chip 0 Vdn: 8.00 W (lowest = 7.00 W, highest = 9.00 W)
Chip 8 : 41.00 W (lowest = 27.00 W, highest = 75.00 W)
Chip 8 Vdd: 14.00 W (lowest = 0.00 W, highest = 47.00 W)
Chip 8 Vdn: 8.00 W (lowest = 7.00 W, highest = 10.00 W)
Chip 0 : 49.47 MJ
Chip 0 Vdd: 7.41 MJ
Chip 0 Vdn: 15.00 MJ
Chip 8 : 65.08 MJ
Chip 8 Vdd: 13.89 MJ
Chip 8 Vdn: 15.18 MJ
Chip 0 Vdd: +11.13 A (lowest = +0.13 A, highest = +48.13 A)
Chip 0 Vdn: +12.13 A (lowest = +10.38 A, highest = +13.75 A)
Chip 8 Vdd: +16.13 A (lowest = +0.63 A, highest = +50.88 A)
Chip 8 Vdn: +12.75 A (lowest = +11.25 A, highest = +15.50 A)
amdgpu-pci-0100
Adapter: PCI adapter
vddgfx: +0.95 V
fan1: 1215 RPM (min = 700 RPM, max = 4500 RPM)
edge: +57.0°C (crit = +99.0°C, hyst = -273.1°C)
power1: 20.17 W (cap = 95.00 W)
-
Your mainboard fans also not shown. Got it. Thanks!
-
Yeah, it's just the video card. Same for the Blackbird (that was done on this T2).
-
Your mainboard fans also not shown. Got it. Thanks!
ipmitool sensor will show you the fan speeds etc. alongside CPU / DIMM / planar temps and power usage.
-
Hi guys, I don't know if you have noticed but I think so now, after the latest Fedora updates, a nice bug has come out in the application that manages the software, the Fedora software market. It no longer displays the images of the applications and what is worse no longer lets you manage them, by selecting updates or installed, the wait turns endlessly ... Has someone managed to report this anomaly by chance already?
-
Terminal command
pkcon refresh force should fix the problem, I think.
code]ipmitool sensor[/code] will show you the fan speeds etc. alongside CPU / DIMM / planar temps and power usage.
I'm aware of IPMItool. Would be nice to have a GNOME shell that uses IPMItool.
-
tried a little while ago but unfortunately nothing, the problem persists, I think we should report it to the Fedora team as there is a bug in the last update ... I don't know how to do it if someone can report it to him it would be a very good thing ... Thanks always for the help, thanks MPC always great and always very active in the Power community!
-
I'm aware of IPMItool. Would be nice to have a GNOME shell that uses IPMItool.
Sounds like I have a project for the weekend ...
-
Well, that didn't take too long, even though I've been on duty all weekend.
https://www.talospace.com/2020/02/diy-ipmi-fans.html
-
Cool. Thank you very much. I will try it later.
-
Sorry, I have to ask you one thing. I have done adduser and addgroup. The files looks as folows:
vigr:
ipmi:x:1001:username
vigr -s:
ipmi:!::username
vipw:
username:x:1000:1001:ipmi:/home/username:/bin/bash
groups:
ipmi wheel
I guess, the vipw entry are wrong? What have I got to enter in this file?
Because, when I type: ipmitool sdr type fan, I got:
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
I still have to sudo.
-
What does ls -l /dev/ipmi0 look like? On this system,
% ls -l /dev/ipmi0
crw-rw----. 1 root ipmi 239, 0 Feb 5 09:05 /dev/ipmi0
I think you have the groups right, but either your udev rule is wrong or it hasn't taken effect yet.
-
$ ls -l /dev/ipmi0
crw-r-----. 1 root ipmi 241, 0 5. Feb 18:05 /dev/ipmi0
$ cat /etc/udev/rules.d/99_my.rules
# allow ipmi to be seen by ipmi group
KERNEL=="ipmi*", GROUP="ipmi", MODE="0640"
chgrp ipmi /dev/ipmi0
chmod 0640 /dev/ipmi0
What have I done wrong and how do I correct the permissions?
-
Oh, my bad. Yes, it does need to be writeable to send the commands to the BMC. Try 0660 instead of 0640. I wasn't thinking there.
-
Thanks, that's it :-)
For future revisions:
Link between IPMI fan 0/1/2 and mainboard fan connectors (https://www.flamingspork.com/blog/2019/12/15/are-you-fans-of-the-blackbird-speak-up-i-cant-hear-you-over-the-fan/)
-
Yes, but I don't know if that mapping applies for the T2. IPMI reports six fans on this machine. I haven't sat down to figure out which are which.
Incidentally, what is the CPU monitor tool you're using there? I like the clockspeed display.
-
Yes, the mapping is for the Blackbird only.
I'm using cpufreq (https://extensions.gnome.org/extension/1082/cpufreq/).
-
It is a pity that cpufreq does not distinguish between physical cores and threads. Then it would be possible to switch off single cores and you could also switch between SMT1, 2 and 4.
-
Guys finally fixed the Fedora Software application problem. In recent updates have sent the fix to the problem.
-
Which repository have I to enable to get Kernel 5.6?
I currently have a problem with the 8x PCIe slot. There is a NVMe adopter (with Corsair MP600) in this slot and I get the error:
nvme nvme0: frozen state error detected, reset.
Removing after probe failure status: -19.
can't change power state from D3hot to D0 (config space inaccessible)
I guess this could be a kernel problem?
This error only occurs if the 16x slot is used (RX5500XT).
Has anyone an idea how to locate the error?
Edit: Here I found someone with a similar issue (https://bugzilla.kernel.org/show_bug.cgi?id=195039).
His conclusion in the last post: Mainboard change to a different model.
-
One further quwestion, I'm following this guide: Installing Kernel (https://wiki.raptorcs.com/wiki/Enabling_Navi_10_On_Fedora_31#Compiling_The_Kernel)
When I perform: sudo make INSTALL_MOD_STRIP=1 -j`nproc` install, I get this:
LDS arch/powerpc/boot/zImage.lds
WRAP arch/powerpc/boot/zImage.pseries
WRAP arch/powerpc/boot/zImage.epapr
sh -x ./arch/powerpc/boot/install.sh "5.6.0-rc3+" vmlinux System.map "/boot"
+ set -e
+ '[' -x /root/bin/installkernel ']'
+ '[' -x /sbin/installkernel ']'
++ basename vmlinux
+ image_name=vmlinux
+ '[' -f /boot/vmlinux ']'
+ mv /boot/vmlinux /boot/vmlinux.old
+ '[' -f /boot/System.map ']'
+ mv /boot/System.map /boot/System.old
+ cat vmlinux
+ cp System.map /boot/System.map
+ path=/boot
+ shift 4
+ '[' 0 -ne 0 ']'
Instead of this:
LDS arch/powerpc/boot/zImage.lds
WRAP arch/powerpc/boot/zImage.pseries
WRAP arch/powerpc/boot/zImage.epapr
sh -x ./arch/powerpc/boot/install.sh "5.6.0-rc3+" vmlinux System.map "/boot"
+ set -e
+ '[' -x /root/bin/installkernel ']'
+ '[' -x /sbin/installkernel ']'
+ exec /sbin/installkernel 5.6.0-rc3+ vmlinux System.map /boot
What's my error?
-
but sorry, this 5500 XT graphics card, can you make it work with the same patch as the 5.5.0.rc1 kernel that we installed some time ago? I know that is for ships 10 and this is ships 14 ... How do you make it work let me understand ...
-
It's the same patch. Because Navi 14 and Navi 10 are almost the same GPUs.
-
Got it all clear. And why did you decide to install Kernel 5.6? The patch is then provided by default in these new Kernels or should we always install it ourselves?
-
Yes, I thought the patch is applied to Kernel 5.6. But with Kernel 5.6 it doesn't work.
-
So I think you should wait now. In fact, I have not yet understood what will happen with the new Kernels regarding the operation of Navi10 / 14 because obviously we must always be able to use the graphics cards otherwise it doesn't make sense ... I am currently doing very well and I hold on to 5.5.0.rc1 with patches, then when they give me guarantees of being able to use new Kernels that support Navi10 / 14 then I will be happy to install the new Kernels.
-
Kernel 5.6 I have to try again.
-
Now you are using Kernel 5.4.0.2 and not 5.5.0.rc1 + ... I see that you also have the gnome in version 3.35, they said shortly that they will release version 3.36 of the Gnome, it should happen on the 11th of this month. ..