Sun Device Detection Tool helps you to detect whether the Solaris 10 Operating System (OS) or the OpenSolaris OS can be installed on your x86, x64, or SPARC systems. This tool indicates whether
the Solaris 10 OS or the OpenSolaris OS supports the devices that are detected in your x86, x64, or SPARC
system.
If your devices are already shown on the Solaris OS Hardware Compatibility List
(HCL), then you do not need to use this tool.
This page provides the following information
about Sun Device Detection Tool 2.3:
When you invoke Sun
Device Detection Tool, it generates a report that shows
whether a Solaris device driver exists for each device that the tool
detects. This report also indicates whether the driver is built-in with
the
Solaris OS, a driver exists at OpenSolaris community web site
or whether a corresponding third-party driver exists. You can save the report in the HTML format.
Note: Sun does
not warrant the behavior of any third-party driver or OpenSolaris community
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, OpenSolaris community drivers, and the third-party drivers. If the tool detects that one of your devices does not have the supported drivers, rerun Sun Device Detection Tool after the release of a newer version of the Solaris OS to determine whether there exist any latest drivers that support the device.
The current version of Sun Device Detection Tool is designed to detect and run in the default language on your system. The GUI of the tool and the reports are generated in the corresponding language. The supported languages are English, Simplified Chinese, German, French, Japanese, Korean, Italian, Traditional Chinese, Russian, Portuguese, and Spanish.
Sun Device Detection Tool 2.3 enables you to
submit system information to Sun Microsystems Inc. The submissions from Solaris 10 OS and OpenSolaris OS are sent to HCL. The submissions from other OS are sent to Sun for data mining. See Submitting System Configuration for more information about the submitting options.
Click the following links if you want to install the Solaris OS and OpenSolaris OS.
Sun Device Detection Tool supports the following operating systems:
Solaris 10 release on x86, x64, or SPARC systems
OpenSolaris release on x86 or x64 systems
Microsoft
Windows on x86 or x64 systems
Windows Vista
Windows XP
Windows Server 2003
Windows 2000
Windows Server 2008
Windows 7
Linux version 2.6 kernel on x86 or x86_64 systems
Mac OS X on x86 or x86_64 systems
FreeBSD 6 and 7 on x86 or x86_64 systems
Note: Sun Device Detection Tool supports both 32-bit and 64-bit systems for Solaris, Linux, Windows, Mac, and FreeBSD OS on x86 or x64 platforms.
To run Sun Device Detection Tool, your system must have installed Java 2 Platform Standard Edition (J2SE) software and at least Java Runtime Environment (JRE) version 1.5. The JRE enables you to run Java applications.
Note: Sun does not warrant the behavior of any third-party JVM.
Using
Sun Device Detection Tool
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:
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:
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) — 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. Visit the link provided on the page to get
more information on the third party drivers.
(OpenSolaris Community Driver) — 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) — 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) — 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.
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.
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.
Does Sun
Device Detection Tool modify any configuration or data on the system?
Sun Device Detection Tool does not
modify any configuration or data on your system.
How
do I identify the JRE version installed?
To verify that at least JRE version 1.5 installed on your system, use the -version option with the java
command, as shown in the following example:
% java -version java version "1.5.2_13" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.2_13-b06) Java HotSpot(TM) Client VM (build 1.5.2_13-b06, mixed mode)
What should
I do if the system does not meet system prerequisites?
If your system does not meet system prerequisites for Sun Device
Detection Tool 2.3, use Installation Check Tool to determine whether your
system can install and run the Solaris OS.
Type the following commands in the command prompt of your respective OS, to collect the device data of your system.
For Solaris systems, prtconf -pv
For Linux systems, lspci -vv -n
For Windows systems,
reg query hklm\system\currentcontrolset\enum\pci /s
If these commands do not work, check the OS documentation to know the
commands for
collecting 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
Sun Device Detection Tool have a minimum resolution requirement?
A
resolution higher than 800x600 is ideal to run Sun Device
Detection Tool. However, this tool can run under any resolution.
When
I click Start Sun Device Detection Tool 2.3 link on the web page, a jnlp file
is downloaded, instead of the tool getting invoked. Can I still invoke the tool by using this jnlp
file?
Ensure that you have at least JRE version
1.5 installed on your system. See system prerequisites.
If you have at least JRE version 1.5 installed, you can manually invoke Sun Device Detection Tool with the jnlp file that is downloaded in your system.
If you are working on the Windows OS, perform the following steps to invoke Sun Device Detection Tool manually:
Open the Start menu on the desktop and click Run. The Run window is displayed.
Type the cmd command in the text field. A terminal window is displayed.
In the terminal window, type the cd
command and navigate to the directory where the jnlp
file is located.
Type javaws jnlp_filename in the same terminal under the respective directory.
Perform the following steps if you are on the Solaris OS or Linux OS to invoke Sun Device Detection Tool manually:
In a terminal window, type the cd
command to navigate to the directory where the jnlp
file is located.
Type javaws jnlp_filename in the same terminal under the respective directory.
Note: Ensure that the Internet connectivity is functioning during this period.
Sun Device Detection Tool does not invoke on my system.
If Sun Device Detection Tool does not invoke, check the following in your system.
Ensure that Firewall is not
blocking Sun Device Detection Tool.
Ensure that you are using at least JRE version 1.5 on your system.
If the above described conditions are proper, you need to make some manual changes to the settings in your system's Java Control Panel. Perform the following steps for setting the Java Control Panel.
Open the Java Application Control
Panel Reviewer window. The method of invoking this window is different for various OS as explained in the following section:
For Solaris OS or Linux OS, open a terminal window and type ControlPanel.
For Windows OS, click the Java icon in Control Panel.
On the General tab of Java Control Panel, click the
Network Settings button. The
Network Settings window is displayed.
Select the Use proxy server radio button.
Type the address and the port information in the given fields.
If you do not need the proxy server, select the Direct Connection radio button.
Click OK.
Close the Java Application Control
Panel Reviewer window.
Type javaws jnlp_filename in the terminal after navigating into the directory where the jnlp file is downloaded.
Sun Device Detection Tool invokes.
Sun Device Detection Tool invokes in the OpenSolaris OS, but the GUI does not display.
Perform the following steps to run Sun Device Detection Tool in the GUI mode.
Open a terminal window and type the
following command:
unset GNOME_DESKTOP_SESSION_ID
In the same terminal window, rerun the
Sun Device Detection Tool.
Why is
the Start button being disabled in the Sun Device Detection Tool window when invoked in my system?
If the Start button is disabled, you
might be running Sun Device Detection Tool on a system that does not meet System Prerequisites. If your system does not meet system prerequisites,
collect the device information yourself and send it to Sun as described in FAQ 3.
How
should I run the registry query command on the Windows OS? Where is
the register.txt file saved?
To run the registry
query command on a Windows system, perform the following steps:
Open the Start menu in the desktop and click Run.
In the Run window, type the cmd
command in the field provided. A terminal window is displayed.
In the terminal window, type the
following command:
The register.txt file is saved in the current
directory in which you are working.
What
does Note-1 indicate in the driver report?
Note-1
indicates that the device has a third-party driver and the respective download link of
the third-party driver is mentioned below the report table and is labeled Note-1.
For example, if more than one device on your system has a third-party driver, the
first device is labeled Note-1, the second is labeled Note-2.
I
installed a third-party driver for my device and it is functioning properly. Why is the status of
this device No Solaris Driver in the driver report?
This
device might have drivers for the other operating systems, but not for
the latest releases of the Solaris 10 OS and the OpenSolaris OS. Sun
Device Detection Tool 2.3 reports whether the latest Solaris drivers or the OpenSolaris drivers exist for your detected
devices. The detected drivers for your devices can exist either as a part of the latest releases of Solaris 10 OS or the OpenSolaris OS. The drivers might also exist in the third-party web sites.
If
you have a driver for a device that works with the latest releases of Solaris 10 OS or the OpenSolaris OS, send an email to device-detect-feedback@sun.com.
To add particular drivers that should be integrated
with the Solaris OS, send an email to driver-request@sun.com.
The status of the device in the driver report
is No Solaris Driver. Can this
device still work on the Solaris 10 OS or the OpenSolaris OS?
A device with the status No Solaris
Driver in the driver report might work with the Solaris 10 OS or the OpenSolaris 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 that you are
using the most current release of Sun Device Detection Tool.
The device is not supported but might work with the
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 listed as supported.
The device is not supported and might work with the
driver that is published on the OpenSolaris
community web site. However, the driver is not included in the Sun Device Detection
Tool database. Check the OpenSolaris community web site periodically to search
for drivers that you need.
Where
can I get more information about third-party drivers?
The following sources provide more information about third-party drivers.
Why am I not able to invoke Sun Device Detection Tool on the OpenSolaris 2008.05 system by using the default Firefox web browser?
On the OpenSolaris 2008.05 system, the jnlp file of Sun Device Detection Tool is configured to open with the Firefox web browser by default. However, a jnlp file is not invoked with the Firefox web browser.
To run Sun Device Detection Tool on OpenSolaris 2008.05, perform the following steps:
Click the jnlp file link of Sun Device Detection Tool. The Opening window is displayed.
Select Other from the drop-down list that is shown when the Open radio button is clicked.
Select javaws application under /usr/java/bin directory.
Click the Open button in the window and then click Ok.
Sun Device Detection Tool starts automatically.
Unable to find the Submit button while running Sun Device Detection Tool 2.3 on a system that has FreeBSD OS versions 6.0 and 6.1 with the Diablo JRE 1.6 software installed.
The submission function is disabled when the tool is run with the Diablo JRE 1.6 software. To submit your system configuration to Sun from a FreeBSD OS versions 6.0 or 6.1, you need to run Sun Device Detection Tool with the Diablo JRE 1.5 software.
Why do characters displayed in the Sun Device Detection Tool 2.3 GUI appear garbled whenever Sun Device Detection Tool is started by selecting Simplified Chinese as the default language?
Ensure that your system has installed the Simplified Chinese package successfully. If not, install the language package before invoking Sun Device Detection Tool.
If you are on Solaris OS, ensure that your language code is GB18030. Otherwise, log out of your system and log in again by selecting the Simplified Chinese GB18030 language, and rerun Sun Device Detection Tool 2.3.
If you are on Linux OS, perform the following steps:
If there is fonts directory under /lib, make directory fallback under /lib/fonts/. Otherwise, make two level directory fonts/fallback under /lib
Copy the simsun.ttf file to the fonts and the fallback directories.
Reboot the system to rerun Sun Device Detection Tool 2.3.
Unable to switch focus among the GUI components such as buttons and
check boxes by using hot keys or the Tab key.
Ensure that the window on which you want to switch focus among the
components is focused. Click the window with your mouse or press
Alt + Tab to focus on it.
If the report table on the main window is focused, use Ctrl + Tab to
defocus it.
Why is system information such as Manufacturer, Model, CPU type, CPU number, architecture, and BIOS/Firmware maker not detected automatically on the Windows OS?
If you start Sun Device Detection Tool on the Windows OS, Manufacturer, Model, CPU type, CPU number, architecture, and BIOS/Firmware maker might not be detected automatically. In such cases, type the Manufacturer, Model, CPU type, and BIOS/Firmware maker information manually. Type the information of CPU number and architecture in the General Notes field.
The system configuration submission fails on FreeBSD OS versions 6 and 7.
Type the following command in the terminal to confirm whether the FreeBSD OS versions 6 or 7 on your system can ping outside the LAN.
ping www.sun.com
If the following message is displayed, you need to manually add a name server to the /etc/resolv.conf file.
ping: cannot resolve www.sun.com: Host name lookup failure
Perform the following steps to add a name server:
Edit the /etc/resolv.conf file. Create the file if it does not exist.
Type the following in the file. Substitute the IP address of your name server as needed:
nameserver nameserver_IP_address
Reboot your system.
Rerun Sun Device Detection Tool to submit the system configuration report.
The submission will succeed.
Help
If you have general questions or suggestions about Sun
Device Detection Tool, send email to device-detect-feedback@sun.com.
To suggest particular drivers that should be
integrated with 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.
(Solaris
Bundled Driver) — The
target version of Solaris OS has the driver bundled.
