ipw3945 vs. Slackware 12.0: anyone have that working? - Slackware

This is a discussion on ipw3945 vs. Slackware 12.0: anyone have that working? - Slackware ; Hi, I recently installed 12.0 on a laptop (Dell D620) which has an Intel ipw3945ABG wireless card. This card worked fine (more or less) under 10.2 and 11.0, but under 12.0 the system hangs very abruptly as soon as you ...

+ Reply to Thread
Results 1 to 9 of 9

Thread: ipw3945 vs. Slackware 12.0: anyone have that working?

  1. ipw3945 vs. Slackware 12.0: anyone have that working?

    Hi,

    I recently installed 12.0 on a laptop (Dell D620) which has an Intel
    ipw3945ABG wireless card. This card worked fine (more or less) under
    10.2 and 11.0, but under 12.0 the system hangs very abruptly as soon
    as you try to send data (it will associate to the access point
    happily).

    I've tried various combinations of the driver (1.1.0, 1.2.0, 1.2.1,
    1.2.0 + some patches from bugzilla), firmware (1.13, 1.14.2 and
    something older), regulatory daemon (1.7.22 and something older) and
    kernels (2.6.21.6 and 2.6.19.7), with no luck so far.

    Anyone have this working under Slackware 12.0? If so, care to share
    the details?

    Thanks.

    Jim

  2. Re: ipw3945 vs. Slackware 12.0: anyone have that working?

    Jim Diamond a écrit :
    >
    > Anyone have this working under Slackware 12.0? If so, care to share
    > the details?


    You might give this a try:

    ftp://ftp.slackware.at/slackware-12....l-wlan-ipw3945

    "Wozu in die Ferne schweifen,
    Wenn das Gute liegt so nah?" (Goethe)

    )

    Niki

  3. Re: ipw3945 vs. Slackware 12.0: anyone have that working?

    On 2007-07-20, Niki Kovacs wrote:
    > Jim Diamond a écrit :
    >>
    >> Anyone have this working under Slackware 12.0? If so, care to share
    >> the details?

    >
    > You might give this a try:
    >
    > ftp://ftp.slackware.at/slackware-12....l-wlan-ipw3945


    Thanks for pointing that out, but, regrettably, it contains a
    combination of ipw stuff that I already tried out (unsuccessfully).

    Jim

  4. Re: ipw3945 vs. Slackware 12.0: anyone have that working?

    On Jul 20, 5:40 pm, Jim Diamond wrote:
    > On 2007-07-20, Niki Kovacs wrote:
    >
    > > Jim Diamond a écrit :

    >
    > >> Anyone have this working under Slackware 12.0? If so, care to share
    > >> the details?

    >
    > > You might give this a try:

    >
    > >ftp://ftp.slackware.at/slackware-12....l-wlan-ipw3945

    >
    > Thanks for pointing that out, but, regrettably, it contains a
    > combination of ipw stuff that I already tried out (unsuccessfully).
    >
    > Jim




    I've installed ipw3495 successfully on my wife's ASUS A8Js.
    I've also tried several versions of the driver/firmware but ended
    up using the ones in the slack12 DVD.

    I have not access to the laptop right now, but as far as I remember,
    removing the ieee80211 subsystem from the kernel was mandatory!
    This means building a custom kernel.

    >From there on, just follow the instructions in the READMEs...


    a) Install the ieee80211 subsystem
    #tar zxf ieee and the -1.2.17.tar.gz
    #cd ieee80211-1.2.17
    #make
    #make install

    b) Install kernel modules
    #tar zxf ipw3945-1.2.1.tar.gz
    #cd ipw3945-1.2.1
    #make
    #make install
    #depmod

    c) Copy the firmware to the right place
    #tar ipw3945-ucode-1.14.2.tgz
    #cd ipw3945-ucode-1.14.2
    #cp ipw3945.ucode /lib/firmware

    d) Compile the daemon
    #tar zxf ipw3945d-1.7.22.tgz
    #cd ipw3945d-1.7.22
    #make
    #make install

    Now make sure the ieee80211 the ipw3945 modules are
    loaded by the kernel. I suppose there is an utility in the
    ipw3945-1.2.1 directory called 'load' that will do just that, but
    it also can be accomplished by

    #modprobe ieee80211
    #modprobe ipw3945

    or, simply

    #modprobe ipw3945 (this will load the ieee80211).

    and start the daemon

    #/sbin/ipw3945d &

    You should know how to set up your box to do this automatically!

    Finally, I've used wpa_supplicant to set up the connection after
    updating values in its configuration file (I cannot remember, but
    it was somewhere in /etc..., probably /etc/wpa_supplicant.conf?).

    #wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf -B

    and then

    #dhcpcd eth1

    to get the IP... and that was it!

    Fortunately my wife doesn't mind typing all these commands
    (I mean the last three) She is also a slack user since late 1990s!

    Regards

    António


  5. Re: ipw3945 vs. Slackware 12.0: anyone have that working?

    On 2007-07-20, tomurias@gmail.com wrote:
    > On Jul 20, 5:40 pm, Jim Diamond wrote:
    >> On 2007-07-20, Niki Kovacs wrote:
    >>
    >> > Jim Diamond a écrit :

    >>
    >> >> Anyone have this working under Slackware 12.0? If so, care to share
    >> >> the details?

    >>
    >> > You might give this a try:

    >>
    >> >ftp://ftp.slackware.at/slackware-12....l-wlan-ipw3945

    >>
    >> Thanks for pointing that out, but, regrettably, it contains a
    >> combination of ipw stuff that I already tried out (unsuccessfully).
    >>


    > I've installed ipw3495 successfully on my wife's ASUS A8Js.
    > I've also tried several versions of the driver/firmware but ended
    > up using the ones in the slack12 DVD.

    Huh. Well, it's (sort of) good to see it works somewhere. I wonder
    if she has a different version of the card than I do. Hmmm...

    > I have not access to the laptop right now, but as far as I remember,
    > removing the ieee80211 subsystem from the kernel was mandatory!

    I read something while hunting today that suggested that was no longer
    necessary, but I did it anyway.
    > This means building a custom kernel.

    Yeah, I always do that anyway.

    >From there on, just follow the instructions in the READMEs...

    And that is what I did.



    > You should know how to set up your box to do this automatically!

    Yup, I've had it automated for the last year or so.

    Anyway, thanks for the reply.

    Jim

  6. Re: ipw3945 vs. Slackware 12.0: anyone have that working?

    tomurias@gmail.com wrote:
    > On Jul 20, 5:40 pm, Jim Diamond wrote:
    >> On 2007-07-20, Niki Kovacs wrote:
    >>
    >>> Jim Diamond a écrit :
    >>>> Anyone have this working under Slackware 12.0? If so, care to share
    >>>> the details?
    >>> You might give this a try:
    >>> ftp://ftp.slackware.at/slackware-12....l-wlan-ipw3945

    >> Thanks for pointing that out, but, regrettably, it contains a
    >> combination of ipw stuff that I already tried out (unsuccessfully).
    >>
    >> Jim

    >
    >
    >
    > I've installed ipw3495 successfully on my wife's ASUS A8Js.
    > I've also tried several versions of the driver/firmware but ended
    > up using the ones in the slack12 DVD.
    >
    > I have not access to the laptop right now, but as far as I remember,
    > removing the ieee80211 subsystem from the kernel was mandatory!
    > This means building a custom kernel.
    >
    >>From there on, just follow the instructions in the READMEs...

    >
    > a) Install the ieee80211 subsystem
    > #tar zxf ieee and the -1.2.17.tar.gz
    > #cd ieee80211-1.2.17
    > #make
    > #make install
    >
    > b) Install kernel modules
    > #tar zxf ipw3945-1.2.1.tar.gz
    > #cd ipw3945-1.2.1
    > #make
    > #make install
    > #depmod
    >
    > c) Copy the firmware to the right place
    > #tar ipw3945-ucode-1.14.2.tgz
    > #cd ipw3945-ucode-1.14.2
    > #cp ipw3945.ucode /lib/firmware
    >
    > d) Compile the daemon
    > #tar zxf ipw3945d-1.7.22.tgz
    > #cd ipw3945d-1.7.22
    > #make
    > #make install
    >
    > Now make sure the ieee80211 the ipw3945 modules are
    > loaded by the kernel. I suppose there is an utility in the
    > ipw3945-1.2.1 directory called 'load' that will do just that, but
    > it also can be accomplished by
    >
    > #modprobe ieee80211
    > #modprobe ipw3945
    >
    > or, simply
    >
    > #modprobe ipw3945 (this will load the ieee80211).
    >
    > and start the daemon
    >
    > #/sbin/ipw3945d &
    >
    > You should know how to set up your box to do this automatically!
    >
    > Finally, I've used wpa_supplicant to set up the connection after
    > updating values in its configuration file (I cannot remember, but
    > it was somewhere in /etc..., probably /etc/wpa_supplicant.conf?).
    >
    > #wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf -B
    >
    > and then
    >
    > #dhcpcd eth1
    >
    > to get the IP... and that was it!
    >
    > Fortunately my wife doesn't mind typing all these commands
    > (I mean the last three) She is also a slack user since late 1990s!
    >
    > Regards
    >
    > António
    >

    Have you tried ndiswrapper? I don't have your particular chipset but I
    just wanted to mention that there is another option available in case
    you can't get it to work. The driver is available on sourceforge.net
    I have been using it for about three years and it works flawlessly with
    most kernels including 2.6.21.5 and wpa_supplicant. I too disabled the
    ieee80211 subsystem.

    Good luck ...

    -- MG

  7. Re: ipw3945 vs. Slackware 12.0: anyone have that working?

    Jim Diamond wrote:
    > Hi,
    >
    > I recently installed 12.0 on a laptop (Dell D620) which has an Intel
    > ipw3945ABG wireless card. This card worked fine (more or less) under
    > 10.2 and 11.0, but under 12.0 the system hangs very abruptly as soon
    > as you try to send data (it will associate to the access point
    > happily).
    >
    > I've tried various combinations of the driver (1.1.0, 1.2.0, 1.2.1,
    > 1.2.0 + some patches from bugzilla), firmware (1.13, 1.14.2 and
    > something older), regulatory daemon (1.7.22 and something older) and
    > kernels (2.6.21.6 and 2.6.19.7), with no luck so far.
    >
    > Anyone have this working under Slackware 12.0? If so, care to share
    > the details?
    >
    > Thanks.
    >
    > Jim


    Hmmm, I haven't had any trouble with ipw3945 1.2.0. I'm using kernel
    2.6.21.6 and 2.6.22.1. I used the ieee80211 that came with the kernels.
    It works like a champ.

    Copy ipw3945.ucode to /lib/firmware.

    Copy ipw3945d to /sbin.

    Create /etc/modprobe.d/ipw3945 containing the following:

    install ipw3945 /sbin/modprobe -i ipw3945 && \
    { \
    while [ ! -d /var/run ]; do \
    sleep 1; \
    done; \
    until [ -e /var/run/ipw3945d.pid ]; do \
    /sbin/ipw3945d --quiet; \
    sleep 1; \
    done; \
    } &
    remove ipw3945 /sbin/ipw3945d --kill ; /sbin/modprobe -r -i ipw3945

  8. Re: ipw3945 vs. Slackware 12.0: anyone have that working?

    On Sat, 21 Jul 2007 06:31:34 -0600, cbxbiker61 scrawel pointlessly:

    > Hmmm, I haven't had any trouble with ipw3945 1.2.0. I'm using kernel
    > 2.6.21.6 and 2.6.22.1. I used the ieee80211 that came with the kernels.
    > It works like a champ.


    Same with me. I'm using 1.2.1d though.

    Custom kernel: 2.6.21.5-smp
    wpa_supplicant using wext driver
    ipw3945 source from /extra on slackware-12.0
    ** These are tarballs, not Slackware packages, despite ending in .tgz

    To the OP: Your post implied that you are getting the card up and
    running, but are having issues with data transmission. Is this the case,
    or have I misunderstood?

    If you have had this card up and running before on other installs, then I
    assume you probably got that far this time around as well. I'll post my
    output from some commands anyway just in case it helps point to something
    that may be missing on your setup.

    Is your output of the following commands similar to below:

    <---------------------------------------------------------

    $ lsmod | grep ipw3945
    ipw3945 198304 1
    ieee80211 34248 1 ipw3945

    <---------------------------------------------------------

    $ lsmod | grep ieee80211
    ieee80211_crypt_tkip 14336 2
    ieee80211 34248 1 ipw3945
    ieee80211_crypt 8576 2 ieee80211_crypt_tkip,ieee80211

    <---------------------------------------------------------

    # iwconfig
    lo no wireless extensions.

    dummy0 no wireless extensions.

    eth0 no wireless extensions.

    eth1 IEEE 802.11g ESSID:"IDONTTHINKSO" Nickname:"moon"
    Mode:Managed Frequency:2.447 GHz Access Point: AB:CD:EF:FA:GH:IJ
    Bit Rate:54 Mb/s Tx-Power:15 dBm
    Retry limit:15 RTS thrff Fragment thrff
    Encryption key:BB19-283C-8928-50B1-3329-63B5-628E-18FA
    Power Managementff
    Link Quality=96/100 Signal level=-32 dBm Noise level=-33 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:57 Missed beacon:0

    <----------------------------------------------------------

    # dmesg | grep ipw3945
    ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux,
    1.2.1d
    ipw3945: Copyright(c) 2003-2006 Intel Corporation
    ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
    ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a
    channels)

    <----------------------------------------------------------

    # ps aux | grep ipw3945d
    root 2026 0.0 0.0 1716 372 ? S 10:07 0:02 /sbin/
    ipw3945d --quiet --pid-file=/var/run/ipw3945d/ipw3945d.pid

    <-----------------------------------------------------------

    Any significant deviations/omissions from above may point you in the
    direction of your problem. If everything is loaded and running, then
    perhaps an authentication problem with wpa or wep?

    HTH

    --
    This isn't who it would be if it wasn't who it is.

  9. Re: ipw3945 vs. Slackware 12.0: anyone have that working?

    On 2007-07-21, cbxbiker61 wrote:
    > Jim Diamond wrote:
    >> Hi,
    >>
    >> I recently installed 12.0 on a laptop (Dell D620) which has an Intel
    >> ipw3945ABG wireless card. This card worked fine (more or less) under
    >> 10.2 and 11.0, but under 12.0 the system hangs very abruptly as soon
    >> as you try to send data (it will associate to the access point
    >> happily).
    >>
    >> I've tried various combinations of the driver (1.1.0, 1.2.0, 1.2.1,
    >> 1.2.0 + some patches from bugzilla), firmware (1.13, 1.14.2 and
    >> something older), regulatory daemon (1.7.22 and something older) and
    >> kernels (2.6.21.6 and 2.6.19.7), with no luck so far.
    >>
    >> Anyone have this working under Slackware 12.0? If so, care to share
    >> the details?


    >
    > Hmmm, I haven't had any trouble with ipw3945 1.2.0. I'm using kernel
    > 2.6.21.6 and 2.6.22.1. I used the ieee80211 that came with the kernels.
    > It works like a champ.




    Thanks for your report. I decided to give 2.6.22.1 a try and the
    wireless now works fine. (And, for those who may be interested, I
    used the 80211 code that came with 2.6.22.1, rather than installing
    the latest and greatest separately.)

    Sort of annoyingly, there are some updates to the networking code in
    2.6.22.1 that break the Cisco VPN client. However, a patch to fix the
    client can be found at
    http://tuxx-home.at/archives/2007/05/29/T16_34_26/

    Thanks to everyone else for their suggestions.

    Jim

+ Reply to Thread