comment all lines in sgen.conf with the exception of device-type-config-list="changer"; name="sgen" class="scsi" target=0 lun=0;
then unload the module and run devsfadm again. if devfsadm didn't error with "failed to attach" then is should create the device files. i'm guessing it's not there due to the other lines not being commented in sgen.conf. Jerry wrote: > ok. My sgen.conf has this basically: > > device-type-config-list= > "changer" (type 0x08) > > name="sgen" class="scsi" target=0 lun=0; > name="sgen" class="scsi" target=1 lun=0; > name="sgen" class="scsi" target=2 lun=0; > name="sgen" class="scsi" target=3 lun=0; > name="sgen" class="scsi" target=4 lun=0; > name="sgen" class="scsi" target=5 lun=0; > name="sgen" class="scsi" target=6 lun=0; > name="sgen" class="scsi" target=7 lun=0; > name="sgen" class="scsi" target=8 lun=0; > name="sgen" class="scsi" target=9 lun=0; > name="sgen" class="scsi" target=10 lun=0; > name="sgen" class="scsi" target=11 lun=0; > name="sgen" class="scsi" target=12 lun=0; > name="sgen" class="scsi" target=13 lun=0; > name="sgen" class="scsi" target=14 lun=0; > name="sgen" class="scsi" target=15 lun=0; > > Also, if i do a probe-scsi-all I see the changer as > EXB-210 on scsi@1,1 target 0, unit 0 > and I see the M2 Drive inside it as target 1, unit 0 > > I modunload and modload sgen, then I devfsadm -i sgen > and get no errors, but I don't see the changer dev > file. > > The output of prtconf |grep -v "not attached" is: > > System Configuration: Sun Microsystems sun4u > Memory size: 256 Megabytes > System Peripherals (Software Nodes): > > SUNW,UltraSPARC-IIi-Engine > options, instance #0 > pci, instance #0 > pci, instance #0 > ebus, instance #0 > se, instance #0 > su_pnp, instance #0 > su_pnp, instance #1 > ecpp, instance #0 > fdthree, instance #0 > SUNW,rasctrl, instance #0 > network, instance #0 > pci, instance #1 > scsi, instance #0 > sd, instance #0 > sd, instance #6 > scsi, instance #1 > st, instance #8 > TSI,gfxp, instance #0 > pseudo, instance #0 > > Thanks for the help so far. FYI, I also have mtx > compiled from sourceforge, I just need the device file > to appear. > > Jerry > > --- Darin Perusich <[EMAIL PROTECTED]> wrote: > >>hi jerry, >> >>i've been using an ex17 autoloader under various >>version of solaris (2.6 >>and 8) for the past 3 years. you WILL need to modify >> >>/kernel/drv/sgen.conf so that the device will be >>recognized, you >>basically need to add the following lines: >> >>device-type-config-list="changer"; >>name="sgen" class="scsi" target=1 lun=0; # which >>target is the scsi id. >> >>comment out all other lines. you can then run >>devfsadm -i sgen to load >>up the driver. you should then have a >>/dev/sgen@1,0:changer device, >>which is a softlink to >> > > /devices/pci@1f,0/pci@1/pci@3/SUNW,isptwo@4/sgen@1,0:changer, > >>or >>something similare. >> >>you will need to compile and install mtx, >>http://mtx.sourceforge.net. >>i've been using version 1.2.10 with great success. >>you also need to use >>the chg-zd-mtx scripts for amanda to control the >>device. i've made >>segnifagent modifications to the script for it to >>handle the device, if >>you want my hacked version email me and i'll mail it >>to you. >> >>the cfgadm(1M) command is used on sun enterprise >>server to dynamically >>reconfigure hardware on the system. you use it to >>take system boards, >>processors, memory in/out of service. you don't need >>to use to for >>amanda, unless you're adding an I/O tray and scsi >>controller to a >>machine on-the-fly. >> >>Jerry wrote: >> >>>I'm an amanda newbie was evaluating it for use in >> >>a >> >>>lab I maintain. I was wondering if anyone has an >>>Exabyte EZ17 Autoloader working with it on >> >>Solaris. >> >>>I am able to amdump and amrestore from it, but I >>>haven't delved into the changer stuff yet. I had >> >>2 >> >>>veritas guys in trying to configure their very >>>expensive software and they never called me back >> >>after >> >>>they ran into some tape errors. (oh well for >> >>them). >> >>>Anyway, I am confused on st.conf sgen.conf or if I >>>even need to touch those to make the changer >> >>appear. >> >>>At one time, I noticed when I had veritas >> >>installed >> >>>cfgadm -al showed quite a few devices (I assume >> >>for >> >>>changer) but after un-installing it appears back >> >>to >> >>>normal (just showing rmt). >>> >>>Any ideas on whether the autoloader works, or even >> >>if >> >>>it can be put into sequential mode, maybe amanda >> >>can >> >>>cycle through the tapes until it finds the right >> >>one? >> >>>At one time I started on the mtx avenue to try to >> >>get >> >>>the changer to work (since I assumed at that point >> >>I >> >>>would be better off the get amanda working with >> >>it) >> >>>but I am stumped on not having an sg0 device or >>>whatever solaris calls it. >>> >>>Ap_Id Type >> >>Receptacle >> >>> Occupant Condition >>>c0 scsi-bus >> >>connected >> >>> configured unknown >>>c0::dsk/c0t0d0 disk >> >>connected >> >>> configured unknown >>>c0::dsk/c0t6d0 CD-ROM >> >>connected >> >>> configured unknown >>>c1 scsi-bus >> >>connected >> >>> configured unknown >>>c1::rmt/0 tape >> >>connected >> >>> configured unknown >>> >>> >>> >>> >>>__________________________________________________ >>>Do you Yahoo!? >>>Faith Hill - Exclusive Performances, Videos & More >>>http://faith.yahoo.com >>> >>> >> >> >>-- >>Darin Perusich >>Unix Systems Administrator >>Cognigen Corp. >>[EMAIL PROTECTED] >> >> > > > > __________________________________________________ > Do you Yahoo!? > Faith Hill - Exclusive Performances, Videos & More > http://faith.yahoo.com > > -- Darin Perusich Unix Systems Administrator Cognigen Corp. [EMAIL PROTECTED]
