Linux hardware info tool (GUI)
- Thread starter hacktheworld
- Start date
Have you checked out these?: https://www.techgainer.com/5-gui-tools-to-see-hardware-information-in-ubuntulinux/
Although you didn't ask for it, if you want more detailed hardware info, it is available via command line programs such as those in post #55 in this thread: https://linux.org/threads/getting-hardware-information-from-linux-to-help-forum-helpers.9676/page-3
Although you didn't ask for it, if you want more detailed hardware info, it is available via command line programs such as those in post #55 in this thread: https://linux.org/threads/getting-hardware-information-from-linux-to-help-forum-helpers.9676/page-3
tinfoil-hat
Active Member
you mean something like GPU-Viewer?
Condobloke
Well-Known Member
GPU-Viewer, can be found in the Linux Mint Software Manager....quite extensive info
On the matter of lshw-gtk not working properly, you would need all the dependencies installed for it which on this debian system are as follows:
Code:
[tom@min ~]$ apt-cache depends lshw-gtk
lshw-gtk
Depends: libc6
Depends: libgcc-s1
Depends: libgdk-pixbuf-2.0-0
Depends: libglib2.0-0
Depends: libgtk-3-0
Depends: libstdc++6
Recommends: menu
Recommends: pciutils
Recommends: usbutilsCondobloke
Well-Known Member
The OP has not told us which Linux os he is using....which is disappointing.
If he is using Linux Mint, he will find Lshw-gtk in the Software Manager
If he is using Linux Mint, he will find Lshw-gtk in the Software Manager
Brickwizard
Well-Known Member
I usually stick with inxi, it is pre-installed in some distros, or available in the repositories [software manager] of most others
it is down to personal preference which you use example, I dont use a gui display
it is down to personal preference which you use example, I dont use a gui display
rian@the-answer-42:~$ inxi -Fnxxz
System:
Kernel: 6.1.0-17-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
Desktop: Cinnamon v: 6.0.4 tk: GTK v: 3.24.38 wm: muffin dm: LightDM
Distro: LMDE 6 Faye base: Debian 12.1 bookworm
Machine:
Type: Desktop System: HP product: HP ProDesk 400 G2.5 SFF v: N/A
serial: <superuser required> Chassis: type: 3 serial: <superuser required>
Mobo: HP model: 8105 serial: <superuser required> UEFI: AMI v: 02.19
date: 02/16/2017
CPU:
Info: quad core model: Intel Core i5-4590S bits: 64 type: MCP arch: Haswell
rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 798 high: 800 min/max: 800/3700 cores: 1: 798 2: 798
3: 800 4: 798 bogomips: 23945
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-7.5 ports:
active: VGA-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0412
Device-2: Aveo USB2.0 Camera type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 2-8:4 chip-ID: 1871:0142
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: VGA-1 model: AOC 2270W res: 1920x1080 dpi: 102
diag: 547mm (21.5")
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 4600 (HSW
GT2) direct-render: Yes
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 2-8:4
bus-ID: 00:03.0 chip-ID: 1871:0142 chip-ID: 8086:0c0c
Device-2: Intel 8 Series/C220 Series High Definition Audio
vendor: Hewlett-Packard 8 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:8c20
Device-3: Aveo USB2.0 Camera type: USB driver: snd-usb-audio,uvcvideo
API: ALSA v: k6.1.0-17-amd64 status: kernel-api
Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel pcie: speed: 2.5 GT/s
lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: lxcbr0 state: down mac: <filter>
Drives:
Local Storage: total: 704.24 GiB used: 99.89 GiB (14.2%)
ID-1: /dev/nvme0n1 vendor: Netac model: NVMe SSD 256GB size: 238.47 GiB
speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 39.9 C
ID-2: /dev/sda vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB
speed: 6.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 112.18 GiB used: 99.88 GiB (89.0%) fs: ext4
dev: /dev/nvme0n1p3
ID-2: /boot/efi size: 285.4 MiB used: 6.4 MiB (2.2%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: partition size: 8.1 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p2
Sensors:
System Temperatures: cpu: 33.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 214 Uptime: 10m Memory: 7.68 GiB used: 3.59 GiB (46.7%)
Init: systemd v: 252 target: graphical (5) default: graphical Compilers:
gcc: 12.2.0 alt: 12 Packages: 2731 pm: dpkg pkgs: 2712 pm: flatpak pkgs: 19
Shell: Bash v: 5.2.15 running-in: gnome-terminal inxi: 3.3.26
brian@the-answer-42:~$
System:
Kernel: 6.1.0-17-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
Desktop: Cinnamon v: 6.0.4 tk: GTK v: 3.24.38 wm: muffin dm: LightDM
Distro: LMDE 6 Faye base: Debian 12.1 bookworm
Machine:
Type: Desktop System: HP product: HP ProDesk 400 G2.5 SFF v: N/A
serial: <superuser required> Chassis: type: 3 serial: <superuser required>
Mobo: HP model: 8105 serial: <superuser required> UEFI: AMI v: 02.19
date: 02/16/2017
CPU:
Info: quad core model: Intel Core i5-4590S bits: 64 type: MCP arch: Haswell
rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 798 high: 800 min/max: 800/3700 cores: 1: 798 2: 798
3: 800 4: 798 bogomips: 23945
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-7.5 ports:
active: VGA-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0412
Device-2: Aveo USB2.0 Camera type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 2-8:4 chip-ID: 1871:0142
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: VGA-1 model: AOC 2270W res: 1920x1080 dpi: 102
diag: 547mm (21.5")
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 4600 (HSW
GT2) direct-render: Yes
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 2-8:4
bus-ID: 00:03.0 chip-ID: 1871:0142 chip-ID: 8086:0c0c
Device-2: Intel 8 Series/C220 Series High Definition Audio
vendor: Hewlett-Packard 8 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:8c20
Device-3: Aveo USB2.0 Camera type: USB driver: snd-usb-audio,uvcvideo
API: ALSA v: k6.1.0-17-amd64 status: kernel-api
Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel pcie: speed: 2.5 GT/s
lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: lxcbr0 state: down mac: <filter>
Drives:
Local Storage: total: 704.24 GiB used: 99.89 GiB (14.2%)
ID-1: /dev/nvme0n1 vendor: Netac model: NVMe SSD 256GB size: 238.47 GiB
speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 39.9 C
ID-2: /dev/sda vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB
speed: 6.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 112.18 GiB used: 99.88 GiB (89.0%) fs: ext4
dev: /dev/nvme0n1p3
ID-2: /boot/efi size: 285.4 MiB used: 6.4 MiB (2.2%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: partition size: 8.1 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p2
Sensors:
System Temperatures: cpu: 33.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 214 Uptime: 10m Memory: 7.68 GiB used: 3.59 GiB (46.7%)
Init: systemd v: 252 target: graphical (5) default: graphical Compilers:
gcc: 12.2.0 alt: 12 Packages: 2731 pm: dpkg pkgs: 2712 pm: flatpak pkgs: 19
Shell: Bash v: 5.2.15 running-in: gnome-terminal inxi: 3.3.26
brian@the-answer-42:~$
Graphically Examine Hardware Info With HardInfo • Linux Tips
Sometimes old tools are the best, or at least adequate. In this case, we're talking about HardInfo - a tool that hasn't been updated in about 7 years, but still does a great job.
linux-tips.us
I'm with @Brickwizard , I use inxi and it's always worked well even if it's not GUI.
OP
hacktheworld
Active Member
Thank you, I have checked the depends and recommends listed: I have all.
I have installed lshw-gtk and it work typing "sudo lshw-gtk" but when I close the terminal the program closes.
Last edited:
OP
hacktheworld
Active Member
Sorry, I use Pure OS 10 byzantium (I have not lshw-gtk in the Software Manager)
OP
hacktheworld
Active Member
Thank you, I have tried GPU-Viewer but don't start.
OP
hacktheworld
Active Member
I prefer lshw-gtk because it is more detailed.Graphically Examine Hardware Info With HardInfo • Linux Tips
Sometimes old tools are the best, or at least adequate. In this case, we're talking about HardInfo - a tool that hasn't been updated in about 7 years, but still does a great job.
On the issue of lshw-gtk not working properly on the system, this ought not to happen so far as I can see for a few reasons and may be a symptom of some other problem on the system.
Visiting the PureOS site FAQ, it is fairly clear that the program should run:
The package is available in the debian main repo, and it is also available in the PureOS main repo here:
but you would download it with the package manager that you choose rather than from this location.
The FAQ also advises that resources for problems pertaining specifically to PureOS are as follows:
Tagging the questions you have will likely engage with more users of PureOS who may have good up to date advice to provide.
My own advice in this case, if the program is not working properly, is in the first instance, to remove it, update the system, and then reinstall a new updated version of it. If the system is already updated to the latest version, then perhaps try removing the package, and then re-installing a new copy. No guarantees though.
I'll second @KGIII 's recommendation of HardInfo. This has been a default, OOTB component of every Puppy for years.......certainly, as far back as I can remember. It's more detailed than most people realize, and isn't far off Speccy in terms of output.
For those that want their information in this way, I also have a 'portable' build of Inxi I can quickly run. It runs from an icon in the notification area, and just needs the parameter entering into a wee YAD-powered 'input' box....outputting to a Urxvt terminal window.
I have lshw-gtk installed in a couple of Puppies, but personally I find it a tad confusing to use. Puppy has its own 'system' GUI, PupSysInfo, which will tell you everything you could possibly wish to know about your Puppy system; not only hardware, but software, installed items, background processes, diskspace, etc, etc. It basically pulls together & graphically presents info from dozens of existing Puppy scripts that have been in the OS since time out of mind. Works very well, too!
Mike.
For those that want their information in this way, I also have a 'portable' build of Inxi I can quickly run. It runs from an icon in the notification area, and just needs the parameter entering into a wee YAD-powered 'input' box....outputting to a Urxvt terminal window.
~~~~~~~~~~~~~~~~~~~~~
I have lshw-gtk installed in a couple of Puppies, but personally I find it a tad confusing to use. Puppy has its own 'system' GUI, PupSysInfo, which will tell you everything you could possibly wish to know about your Puppy system; not only hardware, but software, installed items, background processes, diskspace, etc, etc. It basically pulls together & graphically presents info from dozens of existing Puppy scripts that have been in the OS since time out of mind. Works very well, too!
Mike.
Condobloke
Well-Known Member
Is that exactly as you typed it into Terminal ??
I am quite certain there should be a space in there.....
Dont rely on your typing skills....copy and paste the command from wherever you found it, and add what needs to be added for the information you seek.
If you have trouble with that, read the following
No joy there?.....install inxi
inxi :: installation information
Inxi WILL work
You just have to put the time in
Or....click on menu and type in System Info...click on it and copy and paste the info you need or save the whole lot to a document etc
Sorry Brian, not so.
I ran a Live USB of Pure OS GNOME a few hours ago, and that is one way of launching it
You have to leave the underlying Terminal open while the GUI runs, and the Terminal will produce output messages as well.
Another way to open it is from the GNOME Activities
There, it shows as "Hardware Lister".
But it will still throw open a Terminal with that, and it asked me for a Root password.
If you need to set up a root password in order to use that, then simply
Code:
sudo passwd rootand enter your usual password, then enter one for Root and repeat it to make the change.
That window will remain open, also, but you can use another Terminal if you wish it.
Some details can be learned, but you have to click and double-click a bit to find what works.
Wizard
If the problem you have with lshw-gtk is: "when I close the terminal the program closes", it is easily avoided by running the lshw-gtk command with an & in a terminal, as below. That command will run the program and leave a terminal for use, which if closed, will not close the program, but only close the terminal, and the program itself can be closed from its own menu:
Code:
lshw-gtk &With a proviso (at least from the Live version)
You need to press Ctrl-c first to dispense with the stdout content on the terminal screen, and then from the prompt you can exit.
If you simply close the terminal down, it will also close the GUI window.
Wiz
You need to press Ctrl-c first to dispense with the stdout content on the terminal screen, and then from the prompt you can exit.
If you simply close the terminal down, it will also close the GUI window.
Wiz
Good to know. Tested here on a debian installed machine, not PureOS, and worked as described in post #18. That description is fairly standard in my experience with distros, but I didn't use PureOS so I was supposing it should behave the same as with other distros with the standard bash shell.
