Sun Device Detection Tool helps you to detect whether the Solaris Operating System (OS) can be installed on your x86 or x64 system. This tool indicates in a couple of minutes whether
the Solaris OS supports the devices that are detected in your x86 or x64
system.
If your devices are already shown on the Solaris OS Hardware Compatibility Lists
(HCL), then you do not need to use this tool.
This page provides the following information
about Sun Device Detection Tool 2.1:
When you invoke the Sun
Device Detection Tool, it generates a table that shows
whether a Solaris driver exists for each device that the tool
detects. The table also indicates whether the driver is built-in with
the
Solaris OS or available in OpenSolaris.org
or whether a third-party driver is available.
NOTE: Sun does
not warrant the behavior of any third-party driver or OpenSolaris
driver.
Sun
Device Detection Tool is updated periodically to include new drivers in
the driver database that the tool uses. The current version has a driver database that contains information about
the Solaris OS built-in drivers, Open Solaris drivers and the third-party drivers. If the tool detects that one of your devices does not have the supported drivers, re-run the Sun Device Detection Tool after the release of a new version of the Solaris OS to determine whether there exists any latest drivers that supports the device.
Sun Device Detection Tool 2.1 enables you to
submit the system information to HCL using the HCL
Submission function.
Only the following operating systems are
supported by Sun Device Detection Tool:
Solaris OS
Solaris 10 release x86 or x64 updates
Solaris Express Developer
Edition release x86 or x64 updates
Microsoft
Windows
Windows Vista
Windows XP
Windows Server 2003
Windows 2000
Linux version 2.6 kernel x86 or x86_64 distributions
Mac OS X x86 or x86_64
Note: Sun Device Detection Tool supports both 32-bit and 64-bit systems for Solaris, Linux, Windows and Mac OS
To run Sun Device Detection Tool, your system must have Java 2 Platform, Standard Edition (J2SE), Java Runtime Environment (JRE) version 1.4 or later installed. The JRE enables you to run the Java applications.
To start Sun Device Detection Tool 2.1, make
sure you have met the System Prerequisites
listed above. Click the link below to invoke the Sun Device Detection Tool 2.1:
The Sun Device Detection Tool 2.1 download
window is displayed. Click Accept to agree with the license agreement.
Note:
The Sun Device Detection Tool runs automatically as soon as you click Accept. You do not need to install Sun Device Detection Tool.
After the tool is invoked, the main window containing the Start button is displayed.
The main window of Sun Device Detection Tool provides the driver information for the latest releases of Solaris 10 and Solaris Express Developer Edition. Select the target operating system for which you want to know whether the Solaris drivers exist from the drop-down list of the main window.
The example below shows the Sun Device
Detection Tool 2.1 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. The Solaris OS driver availability report for your native system is generated.
Importing
Device Data Files
Apart from testing the current system on
which the
tool is invoked, you can also provide a plain text file that contains
the output of the following system commands:
prtconf
-pv (on Solaris OS).
lspci
-vv -n (on Linux OS).
reg
query hklm\system\currentcontrolset\enum\pci /s
(on Windows based OS).
To import external device data file, perform the following steps:
Gather the system information using one
of the commands listed in
the above. For instance:
Select Import... from the File menu of the main window. A file chooser dialog is displayed.
Select one or more device data files for which you want to check whether the Solaris 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, a check box appears at the top-right corner of the main window. By default, the check box is kept selected. In this case, you can change the target operating system from the main window and start checking the Solaris availability for the imported files for another Solaris release.
If you unselect the check box and click Start, the tool returns to scan your native system again. In this case, the tool does not display the check box after generating the native system report.
Overview
of the Report
Sun Device Detection Tool displays a table of
results. The table contains a row for each device that was detected.
Results are displayed for both 32-bit and 64-bit versions
of the Solaris OS.
The report window has some colored
indicators for which the explanation is as given below:
(Solaris
Bundled Driver) — The
target version of Solaris OS has the driver bundled.
(Third
Party Driver) — The target
version of Solaris OS does not have a bundled driver but a third party
driver is available. You can visit the link provided on the page to get
more information on the third party drivers.
(Open
Solaris Driver) — Open
Solaris drivers are provided by
OpenSolaris.org.
You can visit the link provided on the page to get
more
information on the OpenSolaris drivers.
(No
Solaris Driver) — The target
version of Solaris OS does not have a bundled driver and there is not a
known third party driver or OpenSolaris driver.
(No
Dedicated Xorg Driver
supporting Graphic Interface) — Only kernel video driver is available
for the video device and there is no Xorg video driver available to
support Solaris graphic interface.
A tooltip appears when you roll over the mouse on each PCI device that is displayed in the report table. This tooltip provides device data information such as vendor id, device id, class code, sub-system vendor id, sub-system 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.
You can submit your system information
to the HCL
for
auditing purposes. After auditing, if the system information meets
HCL specifications, the audited report is published in the HCL. You can
invoke the HCL Submission option by clicking File > Submit menu
item.
This function can be used only with the
following
operating systems on x86/x64 platforms:
NOTE:
The HCL Submission functionality is not available with Windows, Linux and Mac OS. For
this reason, the Submit menu will not be visible on Windows,
Linux, and Mac OS. If you are using Sun Device Detection Tool on a Solaris
release other than the above listed Solaris releases, then the Submit
menu will be in a disabled state. In this case, you can
manually submit the system information at the http://www.sun.com/bigadmin/hcl/submittal/submit.jsp
web page.
To submit the system information to
the HCL, follow these
steps:
Click Submit... from the File menu of the main window. 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, and BIOS/Firmware maker information for
the selected system type. If this function is unable to detect
information for the specified system type, then you need to manually
type the system information. Provide System Information.
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 Solaris 10 OS or Solaris
Express Developer Edition, 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,
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.
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 5/08
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.; 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
MotherBoard Information:
Product: 0WG860
Manufacturer: Dell Inc.
Version:
Onboard Device: [Video,Disabled]Intel Graphics Media Accelerator 950
CPU Information:
Processor 0:
Processor Socket Type: Microprocessor
Processor Name: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
Processor Manufacturer: Intel
Processor Identifiers: 0x6,0xf,0x2
Current Voltage: 1.8V
External Clock: 1066MHZ
Max Speed: 5200MHZ
Current Speed: 1866MHZ
Virtual Machine Extensions Support: Yes
Number of cores per processor: 2
Number of threads per processor: 2
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
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.
Sun Device Detection Tool - Stand-alone Version
Sun Device Detection Tool is also available as a stand-alone version on DVD.
The features of the stand-alone version is same as that of the version available on
the website. The stand-alone version does not require an internet access to run
as it includes the built-in driver data. You can check for the most current updates by
downloading the version that is available on the website.
The stand-alone version of Sun Device Detection Tool is integrated with the
Solaris Express Developer Edition 1/08 release, also called as SXDE. It
provides driver information about SXDE.
If these commands do not work, check your system documentation for
commands to
use to collect device data. For each device on your system, send the
device ID, vendor ID, class code, subsystem vendor ID, and subsystem ID
to device-detect-feedback@sun.com.
Does
this tool have a minimum resolution requirement?
A
resolution higher than 800x600 is recommended to run Sun Device
Detection Tool. However, this tool can run under any resolution.
When
I clicked the link to run this tool, a jnlp file
was downloaded. What should I do with this jnlp
file?
If you do have JRE 1.4 or later
installed, then on a Windows system do the following steps:
Open the Start menu.
Click Run.
In the Run text box, enter the
command cmd. A terminal window opens.
In the terminal window, use the cd
command to go to the directory where the jnlp
file is located.
In the same terminal window, enter
the following command:
javaws name_of_jnlp_file
Note: Your Internet
connection must be maintained during this entire procedure.
On a Solaris or Linux system, do the
following:
In a terminal window, use the cd
command to go to the directory where the jnlp
file is located.
In the same terminal window, enter
the following command:
javaws name_of_jnlp_file
Note: Your Internet
connection must be maintained during this entire procedure.
What
can I do if Sun Device Detection Tool does not launch on my system?
Make sure your firewall is not
blocking this tool.
Make sure you are using JRE 1.5 or later. (This solution is
not applicable for JRE 1.4.)
Open the Java Application Control
Panel Reviewer window.
For Solaris OS or a Linux OS, open a terminal window and enter the
following command:
ControlPanel
For Windows XP OS, click the Java icon in the Windows Control Panel.
Select
the first page (titled "General") on the control panel. Click the
Network Settings button in the middle of the page. You should see the
Network Settings window.
Select the Use proxy server item,
and input corresponding address and port information below this item.
If you do not need proxy, then select the Direct Connection item.
Click the OK button on this General
window.
Click the OK button on the Java
Control Panel.
Close the Java Application Control
Panel Reviewer window.
Enter the following command:
javaws name_of_jnlp_file
Sun Device Detection Tool should run.
What
can I do if the Sun Device Detection Tool launches on my Solaris
Express Developer Edition system, but the GUI does not display?
Open a terminal window and enter the
following command:
unset GNOME_DESKTOP_SESSION_ID
In the same terminal window, run the
Sun Device Detection Tool again.
What
can I do if the Start button is disabled?
If the Start button is disabled, you
probably are not running on a supported system. See the System Prerequisites
section. If your system does not meet the system prerequisites, you can
collect your device information yourself and send it as described above.
How
should I run the registry query command on the Windows XP OS? Where is
the register.txt file after I run this command?
Follow these steps to run the registry
query command on a Windows XP system:
Open the Start menu.
Click Run.
In the Run text box, enter the cmd
command. A terminal window opens.
In the terminal window, enter the
following command exactly as shown:
The register.txt file is saved in the current
directory. To confirm the name of the current directory, enter the cd
command.
What
does "Note-1" mean in the driver report?
"Note-1"
means this device has a third-party driver, and the download address of
this third-party driver is below the report table and labeled "Note-1".
If more than one device on your system has a third-party driver, the
first such device is labeled "Note-1", the second is labeled "Note-2",
and so forth.
I
installed a third-party driver for my device, and it works well. Why is
this device labeled "No Solaris Driver" in the driver report?
This
device has a driver for other operating systems, but not for the
Solaris Express Developer Edition 1/08 release or Solaris 10 5/08 OS. Sun
Device Detection Tool 2.1 reports whether Solaris Express Developer
Edition 1/08 release or Solaris 10 5/08 OS drivers exist for your detected
devices, either as part of the Solaris Express Developer Edition 1/08
release or Solaris 10 5/08 OS or available from third parties.
If
you have a driver for this device that works with the Solaris Express
Developer Edition 1/08 release or Solaris 10 5/08 OS, please tell us.
If you want to suggest particular drivers that should be integrated
into the Solaris OS, send email to driver-request@sun.com.
If
a device is marked "No Solaris Driver" in the driver report, can this
device still work with the Solaris Express Developer Edition release or
Solaris 10 OS?
A device that is marked "No Solaris
Driver" in the driver report might work with the Solaris Express
Developer Edition OS or Solaris 10 OS if one of the following
conditions is true:
A third-party driver exists for this
device, but
that third-party driver is not yet included in the Sun Device Detection
Tool database. Check this web page periodically to make sure you are
using the most current release of Sun Device Detection Tool.
The device is supported unofficially
by a driver that is included in the Sun Device Detection Tool database.
For example, the iprb
driver is known to work on most Intel 100M network controllers, but
only a few of these network controllers are officially supported.
The device is supported unofficially
by a driver that is published on the OpenSolaris
web site, but the driver is not included in the Sun Device Detection
Tool database. Check the OpenSolaris web site periodically to search
for drivers you need.
Where
can I get more information about third-party drivers?
If you have general questions or suggestions about Sun
Device Detection Tool, send email to device-detect-feedback@sun.com.
If you want to suggest particular drivers that should be
integrated into the Solaris OS, send email to driver-request@sun.com.
See Solaris
for
x86 Device Support for the latest list of devices that are
supported by the Solaris OS on x86 platforms.