iwi driver: Probes but no association (FreeBSD5.4).

From: Josef Karthauser (joe_at_FreeBSD.org)
Date: 05/23/05

  • Next message: Jeremie Le Hen: "Re: iwi driver: Probes but no association (FreeBSD5.4)."
    Date: Mon, 23 May 2005 09:52:39 +0100
    To: net@freebsd.org
    
    
    

    I'm trying to get the iwi driver working on my sony A290 laptop. It's
    got a BG2200 chipset in it and the driver probes and finds the adapter,
    but it doesn't appear to work.

    This is the probe message:

        iwi0: <Intel(R) PRO/Wireless 2200BG MiniPCI> mem 0xff6fd000-0xff6fdfff
        irq 7 at device 2.0 on pci2
        iwi0: Ethernet address: 00:0e:35:38:1e:14
        iwi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
        iwi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps
        24Mbps 36Mbps 48Mbps 54Mbps

    This is the output of ifconfig:

    iwi0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
            inet6 fe80::20e:35ff:fe38:1e14%iwi0 prefixlen 64 scopeid 0x2
            ether 00:0e:35:38:1e:14
            media: IEEE 802.11 Wireless Ethernet autoselect
            status: no carrier
            ssid tao 1:tao
            channel -1 authmode OPEN powersavemode OFF powersavesleep 100
            rtsthreshold 2312 protmode CTS txpower 100
            wepmode OFF weptxkey 1

    The device says in 'no carrier' mode even though my wireless network is
    seen by the same device (booting into windows native).

    The other end is provided by an athalon chipset device in my server:

        ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
                inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
                ether 00:09:5b:e5:1f:a4
                media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
                status: associated
                ssid tao 1:tao
                channel 1 authmode OPEN powersavemode OFF powersavesleep 100
                rtsthreshold 2312 protmode CTS
                wepmode OFF weptxkey 1
                wepkey 1:104-bit

    Have you any ideas as to what to try next? I really fancy me a bit of
    wireless.

    Joe.

    ps I'm running a driver compiled from iwi-freebsd-1.3.4.tgz on
    Damien Bergamini's website. The machine in question is: FreeBSD
    XXX 5.4-STABLE FreeBSD 5.4-STABLE #10: Fri Apr 29 10:39:24

    -- 
    Josef Karthauser (joe@tao.org.uk)	       http://www.josef-k.net/
    FreeBSD (cvs meister, admin and hacker)     http://www.uk.FreeBSD.org/
    Physics Particle Theory (student)   http://www.pact.cpes.sussex.ac.uk/
    ================ An eclectic mix of fact and theory. =================
    
    



  • Next message: Jeremie Le Hen: "Re: iwi driver: Probes but no association (FreeBSD5.4)."

    Relevant Pages

    • Re: Problems with sr driver and Wanic 400
      ... FreeBSD 6.1 doesen't work at any speed in this combo, ... I've got a driver for this card that I was sent by Imagestream, ... Supposedly the programming docs for the chipset used on the WanIC 500 are ... The best bet for current support for these cards is to use Linux, ...
      (freebsd-questions)
    • Re: nutball video question
      ... I am not aware of any MPEG2 hardware capture cards supported under FreeBSD ... MPEG2 encoder chipset]. ... register information that they said should be enough to write the driver. ...
      (freebsd-questions)
    • NIC Card Troubles
      ... I recently purchased a USRobotics 7902A Gigabit Ethernet NIC ... USRobotics never mentions what the chipset is but on the driver CD they ... I recently installed FreeBSD 6.1 on a new computer. ...
      (comp.unix.bsd.freebsd.misc)
    • Re: NIC Card Troubles
      ... I recently purchased a USRobotics 7902A Gigabit Ethernet NIC ... USRobotics never mentions what the chipset is but on the driver CD they ... detected by FreeBSD. ...
      (comp.unix.bsd.freebsd.misc)
    • Re: Asus K8S-MX / SiS 965L workarounds
      ... And you'll get the normal MAC address. ... >SiS 965L chipset). ... >To help all those who have a board with this same chipset, ... Driver for onboard LAN adapter completely missing. ...
      (comp.os.linux.hardware)