Re: [osol-discuss] [basic] cmds to discover/report hardware
On 04/01/10 14:17, Harry Putnam wrote: Marion Hakansonhakan...@ohsu.edu writes: shawn.wal...@oracle.com said: Have you checked the output of prtdiag and prtconf -v ? Also smbios, and scanpci (in /usr/bin/X11/ on Solaris-10). Nice... I think most or maybe all that same info is available buy running the program `Device Driver Utility'. However see below for what happens here. Does anyone know the keyboard command to run the: Device Driver Utility Either in the Application/System menu or in some install media there is an icon left for `Device Driver Utility' left on the desktop. When I try to run it from Applications/System menu I get an icon in the taskbar saying `Device Driver Utility' is starting, but then it never appears, and after 30 seconds or so the icon in taskbar disappears but still never see the interface. So how can I start it from the cmdline? ddu as root... - Bart -- Bart Smaalders Solaris Kernel Performance bart.smaald...@oracle.com http://blogs.sun.com/barts You will contribute more with mercurial than with thunderbird. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [basic] cmds to discover/report hardware
Bart Smaalders bart.smaald...@sun.com writes: [...] shawn.wal...@oracle.com said: Have you checked the output of prtdiag and prtconf -v ? Also smbios, and scanpci (in /usr/bin/X11/ on Solaris-10). Nice... I think most or maybe all that same info is available buy running the program `Device Driver Utility'. However see below for what happens here. Does anyone know the keyboard command to run the: Device Driver Utility [...] So how can I start it from the cmdline? ddu as root... Well since the X session is not owned by root I get an error about not being able to open the display but its followed by what looks like a python error: # ddu Xlib: connection to :0.0 refused by server Xlib: No protocol specified /usr/lib/python2.6/vendor-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) Traceback (most recent call last): File /usr/bin/ddu, line 53, in module import pynotify ImportError: No module named pynotify And trying with pfex from the user whos X session it is: pfexec ddu Traceback (most recent call last): File /usr/bin/ddu, line 53, in module import pynotify ImportError: No module named pynotify This is with build 133 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [basic] cmds to discover/report hardware
I may have asked this question here before, but I'm finding no evidence of it. If I wanted to find as much info as I can about a machines hardware what commands would I use? Things like hdd and there specs. Video card, sound etc etc. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [basic] cmds to discover/report hardware
On 04/ 1/10 04:38 PM, Harry Putnam wrote: I may have asked this question here before, but I'm finding no evidence of it. If I wanted to find as much info as I can about a machines hardware what commands would I use? Have you tried the command, ddu? -Ghee Things like hdd and there specs. Video card, sound etc etc. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [basic] cmds to discover/report hardware
Ghee Teo ghee@sun.com writes: On 04/ 1/10 04:38 PM, Harry Putnam wrote: I may have asked this question here before, but I'm finding no evidence of it. If I wanted to find as much info as I can about a machines hardware what commands would I use? Have you tried the command, ddu? No, thanks... I didn't now about that. /usr/ddu/bin/i386/all_devices Shows quite a bit of info but still can't determine the motherboard. Not sure what else to try with it, there is apparently no man page for ddu. I noticed too that it might be listing the wrong sata adapter. I can't really tell if this line is referring to a pci adapter or the one built into the mobo. It does make reference to pci so I'm assuming this is the pci adapter I added. If so then the report has it wrong, because what I installed is an adaptec 1205a. Can you tell by looking if this might refer to a sata controller built into mobo (wrapped for mail): (Controller)Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] \ Serial ATA Controller:DEVID=0x3112:CLASS=00018085:[0,8,0]:\ pci-ide:1:Attached:VENDOR=0x1095 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [basic] cmds to discover/report hardware
On 04/ 1/10 05:39 PM, Harry Putnam wrote: Ghee Teoghee@sun.com writes: On 04/ 1/10 04:38 PM, Harry Putnam wrote: I may have asked this question here before, but I'm finding no evidence of it. If I wanted to find as much info as I can about a machines hardware what commands would I use? Have you tried the command, ddu? No, thanks... I didn't now about that. /usr/ddu/bin/i386/all_devices Shows quite a bit of info but still can't determine the motherboard. Have you checked the output of prtdiag and prtconf -v ? -Shawn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [basic] cmds to discover/report hardware
shawn.wal...@oracle.com said: Have you checked the output of prtdiag and prtconf -v ? Also smbios, and scanpci (in /usr/bin/X11/ on Solaris-10). Marion ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [basic] cmds to discover/report hardware
try smbios alan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [basic] cmds to discover/report hardware
Marion Hakanson hakan...@ohsu.edu writes: shawn.wal...@oracle.com said: Have you checked the output of prtdiag and prtconf -v ? Also smbios, and scanpci (in /usr/bin/X11/ on Solaris-10). smbios has gobs of satanic looking output but apparently still doesn't know which mobo is installed. (scanpci) That shows the same adapter: pci bus 0x cardnum 0x08 function 0x00: vendor 0x1095 device 0x3112 Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA Controller All good info posters I'm liking the tools mentioned sofar. I'm also wondering now if I've gotten things scrambled in my feeble memory. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [basic] cmds to discover/report hardware
Shawn Walker shawn.wal...@oracle.com writes: On 04/ 1/10 05:39 PM, Harry Putnam wrote: Ghee Teoghee@sun.com writes: On 04/ 1/10 04:38 PM, Harry Putnam wrote: I may have asked this question here before, but I'm finding no evidence of it. If I wanted to find as much info as I can about a machines hardware what commands would I use? Have you tried the command, ddu? No, thanks... I didn't now about that. /usr/ddu/bin/i386/all_devices Shows quite a bit of info but still can't determine the motherboard. Have you checked the output of prtdiag and prtconf -v ? No I hadn't. Wasn't even aware of the tools. Nice concise output except hard to make head or tails of `prtconf' output. [...] pci1106,3104, instance #0 isa, instance #1 motherboard (driver not attached) fdc, instance #1 fd, instance #1 [...] Good info and tools... thanks. (prtconf) Still doesn't appear to know which motherboard is installed. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [basic] cmds to discover/report hardware
Marion Hakanson hakan...@ohsu.edu writes: shawn.wal...@oracle.com said: Have you checked the output of prtdiag and prtconf -v ? Also smbios, and scanpci (in /usr/bin/X11/ on Solaris-10). Nice... I think most or maybe all that same info is available buy running the program `Device Driver Utility'. However see below for what happens here. Does anyone know the keyboard command to run the: Device Driver Utility Either in the Application/System menu or in some install media there is an icon left for `Device Driver Utility' left on the desktop. When I try to run it from Applications/System menu I get an icon in the taskbar saying `Device Driver Utility' is starting, but then it never appears, and after 30 seconds or so the icon in taskbar disappears but still never see the interface. So how can I start it from the cmdline? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [basic] cmds to discover/report hardware
On Thu, Apr 1, 2010 at 10:04 PM, Harry Putnam rea...@newsguy.com wrote: Marion Hakanson hakan...@ohsu.edu writes: Also smbios, and scanpci (in /usr/bin/X11/ on Solaris-10). smbios has gobs of satanic looking output but apparently still doesn't know which mobo is installed. Interesting. On one of my random boxes running 2009.06, smbios says: IDSIZE TYPE 2 57 SMB_TYPE_BASEBOARD (base board) Manufacturer: Gigabyte Technology Co., Ltd. Product: 8I865GVMK Version: x.x Serial Number: Chassis: 0 Flags: 0x0 Board Type: 0x0 Of course, these utilities are reliant on the hardware and bios actually reporting data back, which is somewhat variable in both quantity and quality. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [basic] cmds to discover/report hardware
On 04/ 1/10 04:26 PM, Peter Tribble wrote: On Thu, Apr 1, 2010 at 10:04 PM, Harry Putnamrea...@newsguy.com wrote: Marion Hakansonhakan...@ohsu.edu writes: Also smbios, and scanpci (in /usr/bin/X11/ on Solaris-10). smbios has gobs of satanic looking output but apparently still doesn't know which mobo is installed. Interesting. On one of my random boxes running 2009.06, smbios says: IDSIZE TYPE 2 57 SMB_TYPE_BASEBOARD (base board) Manufacturer: Gigabyte Technology Co., Ltd. Product: 8I865GVMK Version: x.x Serial Number: Chassis: 0 Flags: 0x0 Board Type: 0x0 Of course, these utilities are reliant on the hardware and bios actually reporting data back, which is somewhat variable in both quantity and quality. Likewise, mine supplies the motherboard model and name, but it's also a Gigabyte one, and I suspect these tools are BIOS-dependent for getting this information. -Shawn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [basic] cmds to discover/report hardware
Shawn Walker shawn.wal...@oracle.com writes: On 04/ 1/10 04:26 PM, Peter Tribble wrote: On Thu, Apr 1, 2010 at 10:04 PM, Harry Putnamrea...@newsguy.com wrote: Marion Hakansonhakan...@ohsu.edu writes: Also smbios, and scanpci (in /usr/bin/X11/ on Solaris-10). smbios has gobs of satanic looking output but apparently still doesn't know which mobo is installed. Interesting. On one of my random boxes running 2009.06, smbios says: IDSIZE TYPE 2 57 SMB_TYPE_BASEBOARD (base board) Manufacturer: Gigabyte Technology Co., Ltd. Product: 8I865GVMK Version: x.x Serial Number: Chassis: 0 Flags: 0x0 Board Type: 0x0 Of course, these utilities are reliant on the hardware and bios actually reporting data back, which is somewhat variable in both quantity and quality. Likewise, mine supplies the motherboard model and name, but it's also a Gigabyte one, and I suspect these tools are BIOS-dependent for getting this information. I notice they call it a `base board' not mother board so I grepped for that: smbios |grep 'base board' nothing smbios |grep Manufacturer Manufacturer: Manufacturer: Manufacturer: AMD Manufacturer: None Manufacturer: None Manufacturer: None Must be secretive hardware eh? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
