James C. McPherson wrote:
> Christian Kaiser wrote:
>> James C. McPherson wrote:
>>> Christian Kaiser wrote:
> ...
>>>> In general, how can I clean this up properly?
>>> Did you try either
>>>
>>> (a) devfsadm -C
>>>
>>> or
>>>
>>> (b) a reconfigure reboot, by add "-r" to the end of your kernel$
>>> line in grub
>> both tries did not change the bahavior... any other idea?
>
>
> Well, apart from trying a 'boot -a' (see the boot(1m)
> manpage for more details), you're either going to have
> to hand-edit your /etc/path_to_inst - which is Not Supported(tm).
> (Warning Warning Danger! Will Robinson etc etc).
I modified the /etc/path_to_inst already. See my post where I answered
to myself...
> Or, you could clue me/us in on why it's such a problem to
> have those two lines in your /etc/path_to_inst? Are they
> hurting you in some material fashion?
It does not hurt but the system seems to be in an undefined state and
the only question was how to bring it back to a defined state.
Just to clarify, I do:
# prtconf -D | grep 9902,101
pci9902,101, instance #0 (driver name: dis_dx)
# grep 9902,101 /etc/path_to_inst
"/[EMAIL PROTECTED],0/pci8086,[EMAIL PROTECTED]/pci9902,[EMAIL PROTECTED]" 0
"dis_dx"
# rem_drv dis_dx; add_drv -v -m '* 0666 root sys' -i \"pci9902,101\" dis_dx
exit status = 0
Driver (dis_dx) installed.
But in the syslog I see two calls to my attach function for the same
instance #0. What other place may store the information about the second
(although non-existent) instance #0 then?
Christian
--
Christian Kaiser, Software Engineer, Dolphin Interconnect Solutions
http//www.dolphinics.com
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
