Rick Hedin wrote:
> Good evening.  
>
> I have been trying to configure my Intel PRO/Wireless 3945 ABG card on
> Solaris Express 10/06, using the ndis wrapper.  
>
> Earlier, Casper got me over hurdle of trying to put a 32-bit device driver
> into a 64-bit kernel.  I booted a 32-bit Solaris kernel.  
>
> Everything appears to build, and the modload step appeared to work, but when
> I tried to:  
>
>       add_drv -i '"8086,4222"' pcindis
>   

Hmm.... try maybe add_dv -i '"pci8086,4222"' pcindis

(note the "pci" prefix in the driver alias).

More below...
> the system hesitated for a while, and then rebooted itself.  This normally
> is where you quit, and work on something else.  
>
> I wonder two things:  
>
> 1)  There are two DLL's that go along with the .SYS file.  Could the problem
> be that the DLL's are not picked up by ndis wrapper?  
>   

Not being a windows guru, it seems possible.  Certainly if these DLLs
represent part of the kernel architecture, it would be a problem.  But
if they are only used by configuration tools, then it shouldn't be an issue.
> 2)  Now, when I try to add_drv again, I get the message:  
>
>       (ipwndis) already in use as a driver or alias.
>   

What you really want is not add_drv, but update_drv.  See the man page.

    -- Garrett
> Can you tell me how to wipe out ipwndis wherever it is lurking around the
> system?  I don't see a remove_drv command.  
>
> ------
>
> For those who like to chew on data, here is some output from prtconf -pv.
> The vendor,device -- 8086,4222 -- appears as a "compatible" device, but not
> as the "name" of the device.  
>
>             Node 0x00001c
>                 assigned-addresses:
> 82100010.00000000.f4000000.00000000.00001000
>                 reg:
> 00100000.00000000.00000000.00000000.00000000.02100010.00000000.00000000.0000
> 0000.00001000
>                 compatible: 'pciex8086,4222.103c.135b.2' +
> 'pciex8086,4222.103c.135b' + 'pciex8086,4222.2' + 'pciex8086,4222' +
> 'pciexclass,028000' + 'pciexclass,0280' + 'pci8086,4222.103c.135b.2' +
> 'pci8086,4222.103c.135b' + 'pci103c,135b' + 'pci8086,4222.2' +
> 'pci8086,4222' + 'pciclass,028000' + 'pciclass,0280'
>                 model:  'Network controller'
>                 power-consumption:  00000001.00000001
>                 devsel-speed:  00000000
>                 interrupts:  00000001
>                 subsystem-vendor-id:  0000103c
>                 subsystem-id:  0000135b
>                 unit-address:  '0'
>                 class-code:  00028000
>                 revision-id:  00000002
>                 vendor-id:  00008086
>                 device-id:  00004222
>                 pcie-capid-pointer:  000000e0
>                 pcie-capid-reg:  00000011
>                 pci-msi-capid-pointer:  000000d0
>                 name:  'pci103c,135b'
>
>
> Thanks for your ideas and insights.  
>
>
>               Regards, 
>
>               Rick
> _______________________________________________
> laptop-discuss mailing list
> laptop-discuss at opensolaris.org
>   


-- 
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134  Fax: 951 325-2191


Reply via email to