Solaris 10, Intel PRO/Wireless 3945ABG - Solaris

This is a discussion on Solaris 10, Intel PRO/Wireless 3945ABG - Solaris ; Hi, I've successfully installed Solaris 10 x86 6/06 on my IBM ThinkPad Z61m. The laptop has an Intel PRO/Wireless 3945ABG WLAN Network Card. Before installation i run the Solaris installation check tool. It recognized the card correctly and it told ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Solaris 10, Intel PRO/Wireless 3945ABG

  1. Solaris 10, Intel PRO/Wireless 3945ABG

    Hi,

    I've successfully installed Solaris 10 x86 6/06 on my IBM ThinkPad
    Z61m.
    The laptop has an Intel PRO/Wireless 3945ABG WLAN Network Card.

    Before installation i run the Solaris installation check tool. It
    recognized the card correctly and it told me that Solaris drivers were
    found.

    After installation i don't have an /dev/e1000g and ifconfig can't
    "plumb" the interface.
    In /var/adm/messages appears the follwing line:
    [...] e1000g: [ID 801593 kern.warning] WARNING: pci8086,1011 -
    e1000g[0] : Could not identify hardware

    In /etc/driver_aliases are these lines (and many others beginning with
    e1000g):

    e1000g "pci8086,1008"
    e1000g "pci8086,1009"
    e1000g "pci8086,100d"
    e1000g "pci8086,100e"
    e1000g "pci8086,100f"
    e1000g "pci8086,1010"
    e1000g "pci8086,1011"


    The prtdev.ksh script from bolthole.com prints:

    VendorID=0x8086, DeviceID=0x4227
    Sub VendorID=0x8086, Sub DeviceID=0x1011
    model: 'PCIe-PCI bridge'
    name: 'pci8086,1011'


    prtconf -pv give me:

    Node 0x000019
    assigned-addresses:
    82030010.00000000.edf00000.00000000.00001000
    reg:
    00030000.00000000.00000000.00000000.00000000.02030 010.00000000.00000000.00000000.00001000
    compatible: 'pciex8086,4227.8086.1011.2' +
    'pciex8086,4227.8086.1011' + 'pciex8086,4227.2' + 'pciex8086,4227' +
    'pciexclass,028000' + 'pciexclass,0280' + 'pci8086,4227.8086.1011.2' +
    'pci8086,4227.8086.1011' + 'pci8086,1011' + 'pci8086,4227.2'
    + 'pci8086,4227' + 'pciclass,028000' + 'pciclass,0280'
    model: 'PCIe-PCI bridge'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    interrupts: 00000001
    subsystem-vendor-id: 00008086
    subsystem-id: 00001011
    unit-address: '0'
    class-code: 00028000
    revision-id: 00000002
    vendor-id: 00008086
    device-id: 00004227
    pci-msi-capid-pointer: 000000d0
    name: 'pci8086,1011'


    Any ideas what i can do?

    Thanks

    Julian


  2. Re: Solaris 10, Intel PRO/Wireless 3945ABG

    Julian Thomas wrote:
    > Hi,
    >
    > I've successfully installed Solaris 10 x86 6/06 on my IBM ThinkPad
    > Z61m.
    > The laptop has an Intel PRO/Wireless 3945ABG WLAN Network Card.
    >
    > Before installation i run the Solaris installation check tool. It
    > recognized the card correctly and it told me that Solaris drivers were
    > found.
    >
    > After installation i don't have an /dev/e1000g and ifconfig can't
    > "plumb" the interface.
    > In /var/adm/messages appears the follwing line:
    > [...] e1000g: [ID 801593 kern.warning] WARNING: pci8086,1011 -
    > e1000g[0] : Could not identify hardware
    >
    > In /etc/driver_aliases are these lines (and many others beginning with
    > e1000g):
    >
    > e1000g "pci8086,1008"
    > e1000g "pci8086,1009"
    > e1000g "pci8086,100d"
    > e1000g "pci8086,100e"
    > e1000g "pci8086,100f"
    > e1000g "pci8086,1010"
    > e1000g "pci8086,1011"
    >
    >
    > The prtdev.ksh script from bolthole.com prints:
    >
    > VendorID=0x8086, DeviceID=0x4227
    > Sub VendorID=0x8086, Sub DeviceID=0x1011
    > model: 'PCIe-PCI bridge'
    > name: 'pci8086,1011'
    >
    >
    > prtconf -pv give me:
    >
    > Node 0x000019
    > assigned-addresses:
    > 82030010.00000000.edf00000.00000000.00001000
    > reg:
    > 00030000.00000000.00000000.00000000.00000000.02030 010.00000000.00000000.00000000.00001000
    > compatible: 'pciex8086,4227.8086.1011.2' +
    > 'pciex8086,4227.8086.1011' + 'pciex8086,4227.2' + 'pciex8086,4227' +
    > 'pciexclass,028000' + 'pciexclass,0280' + 'pci8086,4227.8086.1011.2' +
    > 'pci8086,4227.8086.1011' + 'pci8086,1011' + 'pci8086,4227.2'
    > + 'pci8086,4227' + 'pciclass,028000' + 'pciclass,0280'
    > model: 'PCIe-PCI bridge'
    > power-consumption: 00000001.00000001
    > devsel-speed: 00000000
    > interrupts: 00000001
    > subsystem-vendor-id: 00008086
    > subsystem-id: 00001011
    > unit-address: '0'
    > class-code: 00028000
    > revision-id: 00000002
    > vendor-id: 00008086
    > device-id: 00004227
    > pci-msi-capid-pointer: 000000d0
    > name: 'pci8086,1011'
    >
    >
    > Any ideas what i can do?
    >
    > Thanks
    >
    > Julian
    >


    Julian,

    It looks to me that you are not finding the wifi chip
    unless it is hiding behind the pci-pci bridge. You
    probably don't have a e1000g (wired gigabit ethernet
    from intel) but some other gigabit wired chipset. My
    T43p has a broadcom using the bge driver.

    You may be having a similar problem to what I had with a T43p.
    The 2915abg wifi chip was identified as a e1000g and that
    prevented the iwi driver (for the 2915 but NOT the 3945) from
    attaching. However, that isn't the real problem at this point.

    I don't think there is a Solaris driver for the 3945 yet - you
    should check the Open Solaris laptop discussion - see:

    http://www.opensolaris.org/jive/thre...14684&tstart=0

    It appears that Sun is testing a version internally for the 3945
    but nothing has been released.

    What I did was to delete the e1000g line from /etc/driver_aliases
    for the particular entry that loaded against the wifi chip (1010
    for the T43p). Then I did a reconfiguration reboot. Then later
    versions of the iwi driver put the appropriate lines in the file.

    Later, when an appropriate driver for the 3945 is released, the
    driver for the 3945 should provide appropriate entries for the
    /etc/driver_aliases file and then the wifi driver should attach
    to the hardware.

    Stuart


  3. Re: Solaris 10, Intel PRO/Wireless 3945ABG

    Thank you for your reply.

    > It looks to me that you are not finding the wifi chip
    > unless it is hiding behind the pci-pci bridge. You
    > probably don't have a e1000g (wired gigabit ethernet
    > from intel) but some other gigabit wired chipset. My
    > T43p has a broadcom using the bge driver.


    I've got a broadcom nic for the cabled LAN, but definitively an Intel
    PRO/Wireless
    3945 chipset for the WLAN.

    So, I have to wait until Sun provides the right driver?

    Julian


  4. Re: Solaris 10, Intel PRO/Wireless 3945ABG

    Julian Thomas wrote:
    > Thank you for your reply.
    >
    >
    >>It looks to me that you are not finding the wifi chip
    >>unless it is hiding behind the pci-pci bridge. You
    >>probably don't have a e1000g (wired gigabit ethernet
    >>from intel) but some other gigabit wired chipset. My
    >>T43p has a broadcom using the bge driver.

    >
    >
    > I've got a broadcom nic for the cabled LAN, but definitively an Intel
    > PRO/Wireless
    > 3945 chipset for the WLAN.
    >
    > So, I have to wait until Sun provides the right driver?
    >
    > Julian
    >


    I expect that you will have to wait until a driver is released,
    probably first for Open Solaris through the laptop community
    at www.opensolaris.org. If you have experience writing Solaris
    device drivers you might assist or port a madwifi driver ...

    There are some possible interim solutions:

    1) If the Z61m has a Cardbus slot and the OpenSolaris v0.3
    cardbus driver works with A61m cardbus chipset, you might purchase
    one of the supported atheros chipset cardbus wifi cards and use the
    ath driver. There is a first hack at WPA support for the ath
    driver. As far as I know, only the ath driver has the WPA support
    so far. You would probably need to turn off the 3945 so the
    two wifi radios would not interfere with each other.

    2) As long as the Z61m doesn't have bios issues and the
    3945 is a miniPCI card, get a supported miniPCI card (ath or
    iwi driver for example) and replace the 3945 with the supported
    card and driver.

    Stuart

+ Reply to Thread