Invoking Sun Device Detection Tool
To start Sun Device Detection Tool 2.3, ensure that you have met the System Prerequisites listed above. Click the link below to invoke Sun Device Detection Tool 2.3:
-
- Start Sun Device Detection Tool 2.3
The Sun Device Detection Tool 2.3 download window is displayed. Click Accept to agree with the license agreement.
Note: Sun Device Detection Tool is a Java Web Start application that runs automatically as soon as you click Accept. You do not need to install the Sun Device Detection Tool on your system.
After the tool is invoked, the main window is displayed.
The main window of Sun Device Detection Tool displays the driver information for the latest releases of the Solaris 10 OS and the OpenSolaris OS. Select the OS for which you want to know whether the Solaris device drivers exist from the Target Operating System drop-down list of the main window.
The example below shows the Sun Device Detection Tool 2.3 main window.
Detecting Native System
To proceed with detecting your native system, click the Start button. Sun Device Detection Tool searches for the devices on your system and compares the detected devices with a database of devices that are supported in the target Solaris OS. Sun Device Detection Tool detects the PCI controllers automatically on all the systems. The Solaris OS driver availability report for your native system is generated.
Note: The root log in is necessary for detecting the PCI controllers automatically on FreeBSD and SPARC Solaris systems.
Importing Device Data Files
Apart from testing the current system on which Sun Device Detection Tool is invoked, you can also test the device data files that are generated from the external systems. To test the external device data files, print the PCI configuration of the external systems to a text file by using the following commands:
- prtconf -pv on Solaris OS.
- lspci -vv -n on Linux OS.
- reg query hklm\system\currentcontrolset\enum\pci /s on Windows OS.
To import external device data file, perform the following steps:
- Gather the system information using one of the commands listed in the above section, to create a text file. For example:
c: \ > reg query hklm\system\currentcontrolset\enum\pci /s > register-1.txt
The PCI controller information is stored in a plain text file.
-
- Select Import from the File menu of the main window. A file chooser dialog box is displayed.
- Select one or more device data files for which you want to check whether the Solaris device driver exists from the file chooser and click open.
-
- Click Start. If you select multiple files, you are prompted to type the directory path where the generated HTML files are be stored.
-
The tool scans the imported device data files.
After the reports are generated for the imported device data files, select either one of the following options:
- Select the Check compatibility with previously-imported files radio button to re-scan the imported device data files either for the specified Solaris OS release or for another target OS. Click Run Again or Start.
- Select the Check compatibility with the system radio button to scan your native system for the specified Solaris OS release or for another target OS. Click Start.
Overview of the Report
Sun Device Detection Tool generates a tabular report of the existing Solaris device drivers for your system. The table contains a row for each device that is detected. If you have selected multiple device data files, the reports are generated for each device data file individually one after the other.
Results are displayed for both 32-bit and 64-bit versions of the Solaris OS. If you are working on the SPARC Solaris platform, the device driver table displays the driver status information only for the 64-bit versions since the SPARC platform exists only as the 64-bit versions.
The report window has colored indicators for which the explanation is as given below:
(Solaris Bundled Driver) PH*PH*PH\u2014PH*PH*PH The target version of Solaris OS has the driver bundled.-
(Third Party Driver) PH*PH*PH\u2014PH*PH*PH The target version of Solaris OS does not have a bundled driver but a third party driver is available. Visit the link provided on the page to get more information on the third party drivers.
-
(OpenSolaris Community Driver) PH*PH*PH\u2014PH*PH*PH OpenSolaris community drivers are provided by OpenSolaris community web site. Visit the link provided on the page to get more information on the OpenSolaris community drivers.
-
(No Solaris Driver) PH*PH*PH\u2014PH*PH*PH The target version of Solaris OS does not have a bundled driver and there is not a known third party driver or OpenSolaris community driver.
-
(No Dedicated Xorg Driver supporting Graphic Interface) PH*PH*PH\u2014PH*PH*PH Only kernel video driver is available for the video device and there is no Xorg video driver available to support Solaris graphic interface.
A tool tip appears when you roll over the mouse on each PCI device that is displayed in the report table. This tool tip provides device data information such as vendor ID, device ID, class code, subsystem vendor ID, subsystem ID, and the revision ID of the respective PCI device.
Sun Device Detection Tool detects both the kernel video driver and the Xorg video driver for each video device. Not all video devices have both of the two types of video drivers. Some video devices have only the kernel driver. For example, the ATI RV280[Radeon 9200 PRO] video device has only a kernel video driver named vgatext.
In the table, if the first two fields of a video device displays two names, then Sun Device Detection Tool has found a dedicated kernel and Xorg video driver for the device. For example, the S3 Unichrome Pro VGA Adapter has a kernel video driver named vgatext and an Xorg video driver named via.
For a video device that does not have a dedicated Xorg driver, you can try to attach the vesa driver on the device. The vesa driver is a generic Xorg video driver. For more information, see the vesa(7D) man page.
Note - also means that a driver can be associated with the corresponding device, but can not be guaranteed for the device to work properly. In such a scenario, the message displayed after the yellow indicator will be 'Driver support for indicated device not guaranteed'.
Saving the Report
You can also save the report in an HTML format by performing the following steps:
- Select Save from the File menu of the main window. A dialogue box appears that prompts you for the path where you want to save the HTML report.
- Type the path to the report directory to save the HTML report.
- Click Save.
Note - If a single device data file is imported, the report will be shown in a tabular format. Only when multiple device data files are imported, the reports are saved as HTML files in the specified directory.
Analyzing the Logs
Sun Device Detection Tool generates log files for troubleshooting purpose. Whenever the tool fails to function normally, the error details are included in the log files. You need to enable logs to create the log files. By default, logging is disabled.
You can enable Logging by performing the following steps:
- Select Log Settings from the File menu. The Log Settings pop-up window is displayed.
- Enable Save log files in specified directory check box.
- Type the directory name in the Log Directory text box.
- Click Save.
- Click the Start button to scan the native system or imported device data files. The logs are generated.
In the log directory, Sun Device Detection Tool creates a file with name of the format: running-MMDDhhmmXX.log.
If you need help analyzing the log files, send email to device-detect-feedback@sun.com.
Submitting System Configuration
You can submit your system information from the Solaris OS and the OpenSolaris OS to the HCL for auditing purposes. After auditing, if the system information meets HCL specifications, the audited report is published in the HCL.
If you are using Linux, Windows, Mac, and FreeBSD OS, you can submit your system configuration to Sun. However, this information is not considered for HCL auditing. This information is used for data mining purposes.
You can submit your system configuration by clicking the Submit button in the main window of the tool.
Note: The Submit button is enabled on the FreeBSD OS versions 6.0 and 6.1 only with the Diablo JRE version 1.5 software. On the FreeBSD OS versions with at least version 6.2, the Submit button is enabled with the Diablo JRE version 1.5 and 1.6 software.
You can also submit the system information manually at http://www.sun.com/bigadmin/hcl/submittal/submit.jsp.
Perform the following steps to submit the system information to Sun.
- Click Submit button in the main window of the tool. The Contact information window is displayed.
-
Enter contact information. Click Next. The System Information window is displayed.
-
Select the system type.
Sun Device Detection Tool automatically detects the Manufacturer, Model, CPU type, CPU number, architecture, BIOS/Firmware maker, and add-in patches information for the selected system type for Solaris, OpenSolaris, Windows, and Linux OS on x86 or x64 platforms. For Mac, FreeBSD, and SPARC Solaris systems, type the system information manually.
-
Type the remaining system information in the corresponding fields.
Use the General Notes field to provide additional information for the selected system type apart from the automatically detected values.
Note - The prtdiag command is available only with Solaris 10 6/06 (Update 2) and later.
-
Click Next.
The Summary window is displayed. Review the summary of the report. You can save this report by clicking the Save Report button on the bottom-left hand side of the window. Click Next to continue.
-
Provide Proxy Server Information. If you do not have a direct connection to Internet, you can select Use proxy server option. After selecting this option enter the proxy server address and the port in the fields provided.
Note - If you start Sun Device Detection Tool through Java Web Start using Java Runtime Environment (JRE) 1.6 on either the Solaris 10 OS or the OpenSolaris OS, the report submission might fail. In this scenario, you need to remove the Socks proxy settings from the web browser or set the proxy information in the Java Control Panel. For more information about this bug, see CR 6515296.
- Click Next to submit the report. To exit HCL Submission, simply close the window, click the Cancel button, or click Finish button after submission.
Other Information Collected
Apart from the system information you have provided, other system information is automatically collected and sent.
This additional system information includes:
- BIOS information
- Manufacturer information
- Motherboard information
- Processor information
- Memory information
- PCI device data information
- Attached driver name for each detected PCI device
The following example provides a summary of information detected and sent along with the report:
Configuration Summary:
System Type: Desktop System
Manufacturer Name: Dell Inc.
Model: Dell DXC061
OS Bit 64: false
OS Version: Solaris 10 8/07
CPU Type: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
CPU Number: 1
Patches Tested: No add-in patches
BIOS Maker and Version: Dell Inc.; Version: 2.2.1; Release Date: 03/23/2007; BIOS Revision: 2.2
Non-Standard BIOS Settings:
Board Revision Level:
General Notes:
System Information
Manufacturer: Dell Inc.
Product: Dell DXC061
BIOS Information
Vendor: Dell Inc.
Version: 2.2.1
Release Date: 03/23/2007
BIOS Revision: 2.2
Firmware Revision:
MotherBoard Information
Product: 0WG860
Manufacturer: Dell Inc.
Version:
On-board Device: [Video,Disabled]Intel Graphics Media Accelerator 950
CPU Information
Number of physical processors: 1
Number of virtual processors configured: 2
Number of virtual processors online: 2
Processor Name: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
Processor Identifiers(Family, Model, Stepping): 0x6,0xf,0x2
Virtual Machine Extensions Support: Yes
Number of cores: 2
Number of threads: 2
Processor Socket Information
Processor Socket 0
Processor Socket Type: Microprocessor
Processor Type: Central Processor
Processor Manufacturer: Intel
Current Voltage: 1.8V
External Clock: 1066MHZ
Max Speed: 5200MHZ
Current Speed: 1866MHZ
Memory Information
Memory Subsystem 0
Array Used Function: System memory
Memory Error Correction Supported: Single-bit ECC
Maximum Array Capacity: 4096M
Number of Memory Devices: 4
Memory Device 0
Memory Device Locator: DIMM_1
Total Width: 64
Data Width: 64
Installed Size: 1024M
Memory Device Type: DDR
Speed: 667MHZ
Memory Device 1
Memory Device Locator: DIMM_2
Total Width: 64
Data Width: 64
Installed Size: 1024M
Memory Device Type: DDR
Speed: 667MHZ
Memory Device 2
[Not Installed]
Memory Device 3
[Not Installed]
PCI Controllers Information:
PCI Controller 0:
Vendor ID: 1002
Device ID: 7187
Class Code: 00030000
Sub VID: 1028
Sub DID: 0402
Revision ID: 00
Attached Driver Name: vgatext
PCI Controller 1:
Vendor ID: 8086
Device ID: 104c
Class Code: 00020000
Sub VID: 1028
Sub DID: 01dc
Revision ID: 02
Attached Driver Name: e1000g
PCI Controller 2:
Vendor ID: 8086
Device ID: 2834
Class Code: 000c0300
Sub VID: 1028
Sub DID: 01dc
Revision ID: 02
Attached Driver Name: uhci
PCI Controller 3:
Vendor ID: 8086
Device ID: 2835
Class Code: 000c0300
Sub VID: 1028
Sub DID: 01dc
Revision ID: 02
Attached Driver Name: uhci
PCI Controller 4:
Vendor ID: 8086
Device ID: 283a
Class Code: 000c0320
Sub VID: 1028
Sub DID: 01dc
Revision ID: 02
Attached Driver Name: ehci
PCI Controller 5:
Vendor ID: 8086
Device ID: 284b
Class Code: 00040300
Sub VID: 1028
Sub DID: 01dc
Revision ID: 02
Attached Driver Name: audiohd
PCI Controller 6:
Vendor ID: 8086
Device ID: 2830
Class Code: 000c0300
Sub VID: 1028
Sub DID: 01dc
Revision ID: 02
Attached Driver Name: uhci
PCI Controller 7:
Vendor ID: 8086
Device ID: 2831
Class Code: 000c0300
Sub VID: 1028
Sub DID: 01dc
Revision ID: 02
Attached Driver Name: uhci
PCI Controller 8:
Vendor ID: 8086
Device ID: 2832
Class Code: 000c0300
Sub VID: 1028
Sub DID: 01dc
Revision ID: 02
Attached Driver Name: uhci
PCI Controller 9:
Vendor ID: 8086
Device ID: 2836
Class Code: 000c0320
Sub VID: 1028
Sub DID: 01dc
Revision ID: 02
Attached Driver Name: ehci
PCI Controller 10:
Vendor ID: 104c
Device ID: 8023
Class Code: 000c0010
Sub VID: 1028
Sub DID: 01dc
Revision ID: 00
Attached Driver Name: hci1394
PCI Controller 11:
Vendor ID: 8086
Device ID: 2820
Class Code: 0001018f
Sub VID: 1028
Sub DID: 01dc
Revision ID: 02
Attached Driver Name: pci-ide
PCI Controller 12:
Vendor ID: 8086
Device ID: 2825
Class Code: 00010185
Sub VID: 1028
Sub DID: 01dc
Revision ID: 02
Attached Driver Name: pci-ide
As you can infer, some sections are repeated signifying the number of hardware resources in the system. For instance, there can be more than one processor in the system.
Note - While Sun Device Detection Tool tries to collect the above mentioned information, it may not be possible to collect complete information about the system on all platforms.
Printer View