Caua Siqueira Carulli - Sun Microsystems writes:
> ## Executing postinstall script.
> devfsadm: driver failed to attach: ath
> Warning: Driver (ath) successfully added to system but failed to attach
This is the same error you've had all along. It might be a good idea
to try to get more details on what's going wrong with the driver
attach. Setting moddebug to 0x60000000 (using mdb or /etc/system) and
examining the system log messages would probably be a start.
To get more information, add this to /etc/system:
set ath:ath_dbg_flags = 0xffff
then reboot and try to load the driver again. It should write details
about the problem that causes attach to fail.
For what it's worth, "failed to attach" generally means that either
this driver isn't the right one for this system (e.g., attempting to
load an opensolaris driver on Solaris 10) or that the hardware itself
is of a kind that's just not supported by the driver.
(I don't think the prior advice you received to set ath_dbg_flags via
mdb is going to work here, as the problem is during the initial driver
load, and not when open(9E) is called by plumbing. Using mdb to set
that flag is just way too late.)
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
[email protected]
