Page 1 of 2
lshw
Posted: Mon 28 Mar 2011, 00:50
by DPUP5520
provide detailed information on the hardware configuration of the machine. It can report exact memory configuration, firmware version, mainboard configuration, CPU version and speed, cache configuration, bus speed, etc. on DMI-capable x86 or EFI (IA-64) systems and on some PowerPC machines.
Edit: added Fix for GLIBCXX issues for Wary and Quirky hopefully, let me know if it works or not.
Posted: Mon 28 Mar 2011, 03:53
by GustavoYz
Thanks!
I was looking something like this.
Posted: Mon 28 Mar 2011, 15:47
by DPUP5520
Always happy to help
Posted: Tue 29 Mar 2011, 17:35
by abushcrafter
You beat me to it!
Does the GUI work fully? I couldn't get it working completely.
Posted: Tue 29 Mar 2011, 18:29
by DPUP5520
neither could I however I will try to get it working properly today or tomorrow.
Posted: Tue 29 Mar 2011, 20:16
by DPUP5520
Added lshw gui above
Posted: Tue 29 Mar 2011, 20:21
by abushcrafter
So does it display all the info like it should? I was able to compile and run it but most of the info did not show in the GUI but the command line program can get it and export it info HTML.
Posted: Tue 29 Mar 2011, 20:26
by DPUP5520
Seems to display everything fine on my system and I was able to export reports into html and xml
Posted: Tue 29 Mar 2011, 20:36
by abushcrafter
What were your compile parameters then? I am using Wary. I tried your PET but it wanted a different glib.
Posted: Wed 30 Mar 2011, 02:33
by DPUP5520
What error was it giving you about glib, I don't use Wary so I don't think i'd be able to reproduce your error.
Posted: Wed 30 Mar 2011, 10:11
by abushcrafter
Code: Select all
1>>> lshw-gtk
lshw-gtk: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by lshw-gtk)
<Wed Mar 30><09:50:01>~
Custom console setup. Hence the "1>>> " & the "<Wed Mar 30><09:50:01>~".
Posted: Wed 30 Mar 2011, 12:30
by DPUP5520
It looks like lshw is looking in the wrong place for the lib, it may have installed in a non-standard location for you for some reason, use pfind and figure out where it was installed and point lshw to that location.
Posted: Wed 30 Mar 2011, 13:34
by abushcrafter
No, I don't have GLIBCXX.
Posted: Wed 30 Mar 2011, 13:42
by rcrsn51
I have the same problem with lshw in Quirky - it only works for me in Lupu. Did you compile this from source or get it from a repo?
Posted: Wed 30 Mar 2011, 17:18
by DPUP5520
I compiled from source, I was trying to find it in a repo cause I was having trouble compiling it at first. Someone found a solution on a different forum for a similar problem and I will post a proposed solution when I get to a computer that I'm able to boot into puppy and compile on.
Posted: Thu 31 Mar 2011, 04:28
by GustavoYz
Doesn't seems to work on Quirky 1.2 (same error message posted above).
It works on Lupu 520.
Posted: Thu 31 Mar 2011, 23:47
by DPUP5520
Added a fix up top, please let me know if it works for you or not, if it doesn't then i'm out of options for Wary and Quirky.
Posted: Fri 01 Apr 2011, 00:04
by rcrsn51
It worked for me in Quirky 1.3
Posted: Fri 01 Apr 2011, 00:06
by DPUP5520
Glad to hear it , thanks for the feedback
Posted: Fri 01 Apr 2011, 03:16
by Bernie_by_the_Sea
Keep in mind I've only used Puppy for a month or so and don't know what I'm doing, but...
in Wary 5.0.0 the gui displays only the motherboard info (Desktop Computer)...
but in a console (only after changing directories to /usr/bin/) the command ishw displays everything.