Hello
It doesn’t work properly.
It continues with errors already mentioned and previously reported.
Hello
It doesn’t work properly.
It continues with errors already mentioned and previously reported.
@Serial.com did you install gcc?
Can you post the output from dmidecode -t processor | grep Upgrade:
.
I don’t have gcc installed! Shouldn’t this have been installed by default or is it a requirement for the full cpu-x install?
Complete the installation?
edson@localhost:~> sudo zypper in gcc
[sudo] password for root:
Sorry, please try again.
[sudo] password for root:
Loading data from repository…
Reading installed packages…
Resolving package dependencies…The following 13 NEW packages will be installed:
binutils gcc gcc12 gcc12-locale glibc-devel libasan8 libctf0 libctf-nobfd0
libitm1 liblsan0 libtsan2 libxcrypt-devel linux-glibc-devel13 new packages to be installed.
Total download size: 45.7 MiB. Already cached: 0 B. After the operation, 179.4
Additional MiB will be used.
Continue? y/n/v/…? displays all options:
Can you put this command separately? I couldn’t apply it correctly and the output doesn’t appear for me, thanks!
dmidecode -t processor | grep Upgrade:
Would it be this?
edson@localhost:~> sudo dmidecode -t processor | grep Upgrade
[sudo] password for root:
Upgrade: Other
edson@localhost:~> dmidecode -t processor | grep Upgrade:
dmidecode: command not found
edson@localhost:~>
@Serial.com so can you install dmidecode then
zypper in dmidecode
You need to be root user to run this program as well.
It’s already installed
edson@localhost:~> sudo zypper in dmidecode
[sudo] password for root:
Loading data from repository…
Reading installed packages…
‘dmidecode’ is already installed.
No update candidates for ‘dmidecode-3.4-2.1.x86_64’. The highest available version is already installed.
Resolving package dependencies…
Nothing to do.
edson@localhost:~>
program run in root:
same output:
edson@localhost:~> sudo su
localhost:/home/edson # dmidecode -t processor | grep Upgrade:
Upgrade: Other
localhost:/home/edson #
@Serial.com then just the full output from;
dmidecode -t processor
Now it worked
edson@localhost:~> sudo su
[sudo] password for root:
I’m sorry, please try again.
[sudo] password for root:
localhost:/home/edson # dmidecode -t processordmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 2.6 present.Handle 0x0004, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU 1
Type: Central Processor
Family: Other
Manufacturer: Intel
ID: 52 06 02 00 FF FB EB BF
Version: Intel(R) Core™ i3 CPU 540 @ 3.07GHz
Voltage: Unknown
External Clock: 133 MHz
MaxSpeed: 3066 MHz
Current Speed: 3066 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0005
L2 Cache Handle: 0x0006
L3 Cache Handle: 0x0007
Serial Number:
Asset Tag:
Part Number:
Core Count: 2
CoreEnabled: 2
Thread Count: 4
Characteristics:
64-bit capablelocalhost:/home/edson #
@Serial.com did the cc warning go away?
The other warning about the socket is because you system doesn’t identify as it show, that is related to your system BIOS, report to the manufacturer…
I’ll look at a desktop file at some point, else create your own…
Thank you for your effort to find a solution.
Interesting that using the same machine, only that, in another hd, I have installed Fedora 37, where cpu-x works normally in X11 and wayland, where the cpu-x icon appears in the menu: (show applications) in the search tab do (show apps) and the icon can be added to the dock taskbar.
If you want, I can print the screens and show them later.
@Serial.com the openSUSE Maintainers opted to remove the desktop file (I suspect to show errors like your seeing), because it runs a bundled dmidecode you would need to talk to upstream about your cpu, but because you system doesn’t show the socket, you will always see the error…
On Fedora, if you start from the command line, what output is observed.
Olá @malcolmlewis
The output is almost the same, see:
[edson@fedora ~]$ cpu-x
Failed to build Vulkan for device 0 (VK_ERROR_EXTENSION_NOT_PRESENT)
VK_EXT_pci_bus_info is not compatible with device 0, just use the deviceID for matching
No OpenCL supported platform (CL_PLATFORM_NOT_FOUND_KHR)
Your CPU socket is not in the database ==> Intel(R) Core™ i3 CPU 540 @ 3.07GHz, codename: Clarkdale (Core i3)
CPU-X:core.c:2272: There was a failure during CPU voltage recovery (fallback mode)
CPU-X:core.c:1786: Failed to get GPU frequency
However, with one detail! Application icons appear on all desktops, and can even be added to the dock’s task bar. Thing that cannot be done in Tumbleweed. This is the “problem” in question.
See the images below:
The application can be opened from the available icons and from the terminal normally.
The application is previewed in the Gnome Store and can be opened normally.
The application is found and viewed normally in the search field of the menu: ( Show Applications)
After the app is searched, the icon appears normally in the show apps menu.
The application Icon can be fixed normally on the taskbar, see image below:
I hope it helped, because I believe that in openSuse Tumbleweed and other distros, applications should by default work this way in versions with gnome
@Serial.com it’s not a problem from the maintainers perspective, you can fix locally, just copy the desktop file from fedora to ~/.local/share/applications, or create your own launcher.
I suspect they want to identify issues, so want it started from the command line, plus the developer doesn’t have time AFAIK to fix issues…
vi ~/.local/share/applications/cpu-x.desktop
[Desktop Entry]
Name=CPU-X
Comment=Gathers information on CPU, motherboard and more
Exec=cpu-x
Icon=cpu-x
Type=Application
Categories=GTK;System;Monitor;
Terminal=false
Keywords=CPU;system;core;speed;clock;rate;Intel;AMD;motherboard;
Hello friend
Many thanks for the help and guidance.
I used nano and it worked.
nano ~/.local/share/applications/cpu-x.desktop
It worked at least in appearing the icon in the menu (show applications) and fixing it in the taskbar.
Now it still doesn’t show up in the gnome store search menu and the (show apps) search menu
I hope that the application’s information when opening it via the terminal can help with a solution.
Life goes on!