> Would he need to do a boot -r or a makedev to create the device files?
> Something like the tapes command.
drvconfig and ports should do the trick.
If the devices isn't present in /dev/cua after ports something is
1. Check what the serial driver is called:
If you have a working Netra T1 do a ls -l in /dev/cua.
On a E3000 it looks like:
Compare the path names to the faulty machine. If this looks OK and it
still won't work you are either using the wrong serial comm parameters
or the port is broken.
2. Check to see if the package is installed and the driver is where
it's supposed to be:
grep for the driver name and kernel in /var/sadm/install/contents to
find out which package the driver belongs to and the pathname it has
(probably in /kernel/drv or /platform/sun4u/kernel/drv). Compare this to
the faulty machine and install that package if necessary, check point 1
If the package is installed but it won't work anyway check /etc/name_to_major
to see that the driver is listed, if not add it with a uniq number and
redo drvconfig and ports.
3. Check for reported errors:
If this looks OK check /var/adm/messages and dmesg if it has reported
any errors for the device.
If the port is broken it's time to call Sun, you do have a support
contract don't you?
4. Get real:
Ditch Admintool, it will only try to hide the real truth from you.
If you can handle the truth that is... ;)
Life - the ultimate practical joke