6.0-release beta1 breaks ndis for dell truemobile 1400

From: Ben Kaduk (minimarmot_at_gmail.com)
Date: 07/21/05

  • Next message: Kris Kennaway: "Re: linuxthreads compile error in latest 6.0-BETA1" 
    Date: Wed, 20 Jul 2005 23:28:05 -0500
To: freebsd-current@freebsd.org

    Hi All,
    I have not extensively used the ndis driver since I am not often
    around wireless networks, but
    after installing 5.4-release I compiled the driver using
    cd /usr/src/sys/modules/ndis
    make install
    cd /usr/src/sys/modules/if_ndis
    ndiscvt -i bcmwl5a.inf -s bcmwl5.sys -o ndis_driver_data.h
    make && make install

    as recommended, with the bcmwl* files being the ones here:
    http://netfiles.uiuc.edu/kaduk/www/*

    The self-extracting driver (for windows) also generated a bcmwl5.inf
    (not 'a'), but ndiscvt
    produced an error whilst trying to read this file, so I used the 'a'
    version, and ndiscvt finished
    successfully; if_ndis was produced with no errors, and I was able to
    kldload if_ndis.ko and ndis.ko. Upon doing this, console messages
    were produced recognizing my Dell TrueMobile 1400 (broadcom bcm4324
    chipset), but i didn't have a wireless network to use then.
    Since then, I have performed a source upgrade to 6.0-release beta1
    (cvsup last saturday; can't be more precise since I must boot windows
    to use wireless :( ).
    I just today had occasion to use the wireless card, and kldload()-ing
    if_ndis resulted in a panic(). I didn't save the message for two
    reasons: (1), I thought it was just that if_ndis.ko had not been
    rebuild with world, and (2) I'm using my laptop at a friend's
    appartment with no serial console. After performing several
    iterations of cleaning for ndis, if_ndis, and wlan, and
    rebuilding/installing, I produced if_ndis.ko, ndis.ko, and wlan.ko
    that I could successfully kldload() with no panic. However, there
    were no console messages that appeared indicating that the system had
    found my hardward, leading to the statement in the subject that the
    beta breaks ndis for this card. I have already posted a pciconf -lv
    to the list in this thread:
    http://docs.freebsd.org/cgi/getmsg.cgi?fetch=116619+0+current/freebsd-current

    What steps can I take to help debug this regression?

    Thanks,

    Ben Kaduk
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Kris Kennaway: "Re: linuxthreads compile error in latest 6.0-BETA1"

    Relevant Pages

    • Re: problem code 31 when I install NDIS 6
      ... I bet he forgot to put the new required keys in the inf's install section. ... problem when I install NDIS driver in Vista. ... I dump the message in WinDbg and found NDIS didn't call Driver ...
      (microsoft.public.development.device.drivers)
    • Re: Install NDIS Driver
      ... Installing a NDIS IM filter driver requires two INF files: one for the lower-edge "service" or protocol section and one for the upper-edge miniport section. ... The DDK Passthru driver sample includes two INF files needed to install that driver. ...
      (microsoft.public.development.device.drivers)
    • Re: Driver Install failure
      ... After you install the HW driver, should the "new hardware found" dialog for the NDIS device pop up automatically? ... is acting as if it doesn't see the .INF file OR there is something askew in ...
      (microsoft.public.development.device.drivers)
    • ndis 6.0 miniport bluescreen after miniportinitializeex
      ... I am writing a ndis 6.0 miniport driver. ... I install the driver from ... Miniportinitializeex is called. ...
      (microsoft.public.development.device.drivers)
    • Re: XPSP2 Near Miss!!!
      ... SP 2 has updated software for wireless networks. ... the install, it is possible that the new updates for wireless networks ... XPSP2 Windows does not like my wireless connection ...
      (microsoft.public.windowsxp.security_admin)