> Brian Nitz wrote:
> > I haven't had any luck yet, but I really appreciate
> the suggestions. My comments are inline:
> >
> >
> >> Firstly, does it show up in the output of
> >>
> >>
> >> # cfgadm -lav
> >
> > No, not that I can distinguish. I only see a bunch
> of empty unavailable usb devices, such as:
> > When Type Busy Phys_Id
> > usb0/1 empty
> unconfigured ok
> ilable unknown n
> /devices/[EMAIL PROTECTED],0/pci1025,[EMAIL PROTECTED]:1
> usb2/8 empty
> unconfigured ok
> lable unknown n
> /devices/[EMAIL PROTECTED],0/pci1025,[EMAIL PROTECTED],2:8
> is kinda what I was expecting, unfortunately.
>
> ....
> >> modunload st and run "devfsadm -i st".
> >>
> >
> > devfsadm -i doesn't work it wants the numeric ID
> instead of the st symbolic. I used modinfo to find
> it:
> > Id Loadaddr Size Info Rev Module Name
> > 185 f9801000 12350 129 1 st (SCSI tape Driver
> 1.257)
>
> Now that is quite weird. I've never had devfsadm tell
> me that
> I can't give it a module name. Modunload, sure ...
> but not
> devfsadm. Perhaps you typed the wrong thing?
>
Ah yes, it was modunload which wanted the numeric module id. devfsadm -i st
reports:
# devfsadm -i st
devfsadm: driver failed to attach: st
and every time I do this, I get these in the kernel message buffer:
Apr 27 00:44:44 unknown genunix: [ID 773945 kern.info] UltraDMA mode 5 selected
Apr 27 00:44:44 unknown genunix: [ID 773945 kern.info] UltraDMA mode 2 selected
Apr 27 00:44:44 unknown last message repeated 3 times
Apr 27 00:46:44 unknown genunix: [ID 773945 kern.info] UltraDMA mode 5 selected
Apr 27 00:46:44 unknown genunix: [ID 773945 kern.info] UltraDMA mode 2 selected
> Brian, I should have asked you for prtconf -v output
> from
> this system - we haven't checked whether your scsi
> hba is
> actually supported. I reckon it probably isn't, but
> you'll
> have to send me that prtconf output to confirm.
I think this is the important part of the output of prtconf -v:
pcs, instance #0
Register Specifications:
Phys hi=0x0, Phys lo=0x0, Phys len=0
scsi (driver not attached)
Hardware properties:
name='device_type' type=string items=1
value='byte'
name='model' type=string items=1
value='KME,KXLC002,00,'
name='socket' type=int items=1
value=00000000
name='compatible' type=string items=4
value='pccard,KME,KXLC002,00,' + 'pccard32,304' + 'p
ccard,scsi' + 'scsi'
Register Specifications:
Phys hi=0x24000000, Phys lo=0x0, Phys len=0
Phys hi=0x22000000, Phys lo=0x0, Phys len=200
Phys hi=0x21000000, Phys lo=0x0, Phys len=f
Interrupt Specifications:
Interrupt Priority=0x0 (ipl 0)
pci1025,7e, instance #0
System software properties:
name='reserved-addresses' type=int items=9
value=0000ffff.f0000b00.00000200.0000ffff.f0000d00.00000
200.0000ffff.f0000234.00000004
name='ddi-forceattach' type=int items=1
value=00000001
name='active-dma-flush' type=int items=1
value=00000001
name='interrupt-priorities' type=int items=1
value=00000009
Hardware properties:
name='assigned-addresses' type=int items=10
value=82064a10.00000000.c0309000.00000000.00000800.82064
a14.00000000.c0300000.00000000.00004000
name='reg' type=int items=15
value=00064a00.00000000.00000000.00000000.00000000.02064
a10.00000000.00000000.00000000.00000800.02064a14.00000000.00000000.00000000.0000
4000
name='compatible' type=string items=7
value='pci104c,8032.1025.7e.0' + 'pci104c,8032.1025.7e'
+ 'pci1025,7e' + 'pci104c,8032.0' + 'pci104c,8032' + 'pciclass,0c0010' + 'pcicla
ss,0c00'
name='model' type=string items=1
value='FireWire (IEEE 1394) OpenHCI compliant'
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
