Five Step Hardware Device Troubleshoot
----------------------------------------------

The purpose of this document is to walk the user through
5 steps to ensure that a device is attached, identified by
the Boot Prom and also by the kernel.

This process assumes that a device is attached to the system already.
Devices include: ide disks, SCSI disks, SCSI tapes, inet interfaces.

Step #1

From the OS:

	# init 0

	ok setenv auto-boot? false
	ok probe-ide
	ok probe-scsi-all (if SCSI BUS or external SCSI controller)

#!! This will ensure that the device can be seen at the prom level.
#!! If you can't see the device from the probe command, the prom can't see it.
#!! If the prom can't see it, the kernel won't be able to see it.
#!! Check
#!!	- Device is turned on
#!!	- Device is terminating properly
#!!	- Cables are not damaged

Step #2

	ok boot -r

#!! Forces a reconfiguration reboot. The kernel will probe hardware
#!! and build device drivers for all hardware it sees.

	# dmesg | grep "sd@"

#!! The dmesg command ouputs all the hardware controllers identified by the 
#!! kernel during a (reconfiguration) boot. You are looking for the instance
#!! of where your device should exist.
#!!
#!! Jul 25 09:38:14 cannon genunix: [ID 936769 kern.info] sd3 is /pci@1f,0/pci@1/pci
#!! @1/SUNW,isptwo@4/sd@3,0
#!!
#!! The ouput says that an instance of a SCSI disk (sd@3,0) exists at target 3
#!! This entry states that the kernel has identified the device at the appropriate
#!! target.

Step 3

	# grep "sd@" /etc/path_to_inst

#!! The /etc/path_to_inst builds all the possible targets of where a device can exist.
#!! It will also tell the kernel what device driver to load should a device exist at 
#!! that target.
#!! 
#!! An entry in this file tells the kernel that the specific device can exist
#!! at the specific target and the appropriate driver will be loaded.

Step 4

	# prtconf | grep -v not

#!! The prtconf command will print the hardware target configuration
#!! of the system. It will show all possible instances of where a driver
#!! can be attached. A grep -v not will show you only the devices that have
#!! a driver attached. An entry in this output says that the kernel has
#!! loaded the appropriate driver into memory.

Step 5

	# modinfo | grep sd@

#!! The modinfo command will show all the modules in memory. An entry in this
#!! output will show that the physical driver exists in RAM.


#!! At this point you have checked to see if the PROM and the kernel can see the device.
#!! You have checked to see that the kernel knows where the device exists and to load the
#!! appropriate driver. You have then checked to see that the driver is attached
#!! and in memory.
#!! 
#!! If the device still does not function. it is safe to say that the device is BUSTED!

____________________________________________________________________________________________