Re: Wireless Card Trouble ipw220

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I get the output as follows when i run iwpriv eth1
eth1      Available private ioctls :
         monitor          (8BE0) : set   2 int   & get   0
         reset            (8BE1) : set   0 int   & get   0
         set_power        (8BE2) : set   1 int   & get   0
         get_power        (8BE3) : set   0       & get  80 char
         set_preamble     (8BE4) : set   1 int   & get   0
         get_preamble     (8BE5) : set   0       & get  16 char
         set_crc_check    (8BE6) : set   1 int   & get   0
         get_crc_check    (8BE7) : set   0       & get  16 char
This would indicate the driver is correct?
But I am stuck in bringing up the interface.

Any help further help would be good.

On 26/06/06, Charles Curley <charlescurley@xxxxxxxxxxxxxxxxx> wrote:
First, please turn off HTML in your email. It looks like hell and
makes things hard to read. Thank you.

I take it this is a new installation.

I have a Lenovo, but the installations should be
similar. http://www.charlescurley.com/Lenovo.R51.html

On Mon, Jun 26, 2006 at 10:48:34PM +0100, Paul Ward wrote:
>
>    Hi,
>    I am currently using a compaq nx7010 laptop with FC5. I seem to be having
>    trouble with the wirless configuration.
>    I have a ipw2200 card built in, I have used livna to install the latest
>    drivers but can not get fedora to use it can someone please help.
>    ipw2200-firmware-3.0-1.lvn5

This is a firmware package, not a driver. You need both.

>    kernel2.6.17-1.2139_FC5
>    ifcfg-eth1
>    # Intel Corp.|PRO/Wireless LAN 2200 3B Mini PCI Adapter
>    DEVICE=eth1
>    ONBOOT=yes
>    BOOTPROTO=dhcp
>    MODE=Managed
>    ESSID=HOME-NET
>    #lspci |grep ipw
>    I get nothing back

Normal. Try instead:

        [root@dragon rpms]# lspci | grep 2200
        02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG (rev 05)


>    #rmmod ipw2100
>    again nothing back

Reasonable, as it shouldn't be installed to start with.

>    #modprobe ipw2200
>    nothing

Normal. Unix tools are normally silent on success so that only error
messages get displayed.

>    #cat /var/log/dmesg |grep ipw
>     ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
>     ipw2100: Copyright(c) 2003-2006 Intel Corporation
>     ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
>     ipw2100: eth0: Firmware 'ipw2100-1.3.fw' not available or load failed.
>     ipw2100: eth0: ipw2100_get_firmware failed: -2
>     ipw2100: eth0: Failed to power on the adapter.
>     ipw2100: eth0: Failed to start the firmware.
>     ipw2100Error calling register_netdev.
>     ipw2100: probe of 0000:02:02.0 failed with error -5

If you have an ipw2200 and are installing the ipw2100 driver, something
is wrong with your setup. I'd check /etc/modprobe.conf. You should
have, inter alia:

        options ipw2200 hwcrypto=0
        alias eth0 ipw2200

Also, this looks like the kernel is trying to attach the driver to
eth0, when ifcfg-eth1 has it at eth1. Check ifcfg-eth0 just in case,
but I suspect you're a victim of the demented driver dance others have
seen, whereby the kernel swaps eth0 and eth1 around from time to time.

This is what you want to see:

        [root@dragon ~]# dmesg | grep ipw2
        ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.0.8
        ipw2200: Copyright(c) 2003-2005 Intel Corporation
        ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection

It will complain if it does not find the correct firmware, 2.4.

>    #ifup eth1
>    ipw2100 device eth1 does not seem to be present, delaying initialization.
>    I have tried to rpm -qa | grep ipw
>    but only the ipw2200 driver shows up

??? The driver is part of the kernel, and should not have its own
package. At least my driver does not. Or do you mean that you have the
firmware package from livna?

Have you checked to make sure the firmware version matches the one
required by the driver? I'm lazy; I put all of the firmware files into
the directory, and let the driver get the one it wants.

Also, I see you are running kernel2.6.17-1.2139_FC5. Can you fall back
to 2.6.16-1.2133_FC5 (the most recent from updates) and see if you
still have this problem. If not, I would suspect a kernel problem.

--

Charles Curley                  /"\    ASCII Ribbon Campaign
Looking for fine software       \ /    Respect for open standards
and/or writing?                  X     No HTML/RTF in email
http://www.charlescurley.com    / \    No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB


--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list





[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux