William D Waddington wrote: > Michael Li wrote: > >> Michael Bynum ??: >> >>> I deleted the contents of /var/adm/messages and then issued the command >>> >>> mbynum at opensolaris:~# update_drv -a -i 'pci14E4,4328' bcmndis >>> devfsadm: driver failed to attach: bcmndis >>> Warning: Driver (bcmndis) successfully added to system but failed to attach >>> >>> Contents of /var/adm/messages: >>> Jan 9 19:51:43 opensolaris pcplusmp: [ID 444295 kern.info] pcplusmp: ide >>> (ata) instance #1 vector 0xf ioapic 0x2 intin 0xf is bound to cpu 0 >>> >>> >> From the log, bcmndis driver attach entry was not invoked. It seems to >> be device ID match issue, please post whole output of >> #prtconf -pv, so that we can find out the actual device ID in your system. >> > > Sorry, I'm just sticking my beak into the middle of this. > > Back in the day, it required nested quotes to get this to work. Like: > > # update_drv -a -i '"pci14E4,4328"' bcmndis > > Has that changed? Or was it just add_drv that required this? > > Bill > I think the use of double quotes to specify an alias is optional when used by add_drv(1M) from the command line. the double quotes are required by package postinstall script.
Please try below steps to install bcmndis driver to system: #rem_drv bcmndis #modinfo|grep ndisapi #modunload -i <ndisapi module's id> #add_drv -i '"pciex14e4,4328.3"' bcmndis It should work, otherwise, please check /var/adm/messages and the output of #prtconf -D. An similar issue has ever been reported by users that command:add_drv -i '"pci14e4,4324"' bcmndis fail to install driver for bcm4324, because "pci1028,3" is detected in bcm4324 compatible device table, but Solaris matchs it to aac(7D) driver. The workaround is #rem_drv aac and reinstall bcmndis driver with add_drv command. Thanks, Michael
