public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Warren Togami <wtogami@redhat.com>
To: Fabrice Bellet <fabrice@bellet.info>
Cc: fedora-devel-list@redhat.com, linux-kernel@vger.kernel.org,
	Bill Nottingham <notting@redhat.com>,
	csmith@redhat.com
Subject: Re: Trouble with Cisco Airo MPI350 and kernel-2.6.1+
Date: Sun, 01 Feb 2004 11:30:00 -1000	[thread overview]
Message-ID: <401D6FD8.2040406@redhat.com> (raw)
In-Reply-To: <401CCF8A.2010406@redhat.com>

Warren Togami wrote:
> Fabrice Bellet wrote:
> 
>> Hi Warren,
>>
>> On Sun, Jan 25, 2004 at 07:48:57PM -1000, Warren Togami wrote:
>>
>>> IBM Thinkpad T41
>>> Cisco Airo MPI350 802.11b Wireless
>>> PCIID: 0x14b9  0xa504
>>> Kernel: Fedora rawhide 2.6.1-1.57 (Based on 2.6.2-rc1)
>>>
>>> http://bellet.info/~bellet/laptop/t40.html#wireless
>>> http://bellet.info/~bellet/laptop/airo.c-2.6.1-mm2.diff
>>> airo.ko does not support this Airo device, but with the addition of 
>>> this patch it recognizes the device.
>>
>>
>>
> [SNIP]
> Used the ACU tool under Windows XP for flashing the firmware.  The 
> newest firmware version that operates with your driver is:
> 5.00.03
> 
> Perhaps mention within a comment and/or config Help of your patch that 
> the newest supported firmware is 5.00.03?  That would save people like 
> me a lot of time in the future...
> 

Are these many errors normal?

[root@ibmlaptop etc]# iwconfig eth1
Warning: Driver for device eth1 has been compiled with version 16
of Wireless Extension, while this program is using version 15.
Some things may be broken...

eth1      IEEE 802.11-DS  ESSID:"apophis"  Nickname:"ibmlaptop"
           Mode:Managed  Frequency:2.412GHz  Access Point: 00:0C:41:75:D4:02
           Bit Rate:11Mb/s   Tx-Power=20 dBm   Sensitivity=0/0
           Retry limit:16   RTS thr:off   Fragment thr:off
           Encryption key:****-****-**   Security mode:open
           Power Management:off
           Link Quality:30/0  Signal level:-70 dBm  Noise level:-98 dBm
           Rx invalid nwid:59  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:1  Invalid misc:4900   Missed beacon:3

[root@ibmlaptop etc]# ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:02:8A:DF:50:FC
           inet addr:192.168.1.103  Bcast:192.168.1.255  Mask:255.255.255.0
           inet6 addr: fe80::202:8aff:fedf:50fc/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:905 errors:655 dropped:0 overruns:0 frame:655
           TX packets:699 errors:33 dropped:0 overruns:0 carrier:0
           collisions:30 txqueuelen:1000
           RX bytes:439321 (429.0 Kb)  TX bytes:118979 (116.1 Kb)
           Interrupt:11 Base address:0x8000

  reply	other threads:[~2004-02-01 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26  5:48 Trouble with Cisco Airo MPI350 and kernel-2.6.1+ Warren Togami
     [not found] ` <20040127164031.GA13174@bellet.info>
2004-02-01 10:06   ` Warren Togami
2004-02-01 21:30     ` Warren Togami [this message]
2004-02-02  3:14       ` Lai Zit Seng
2004-02-02  3:14         ` Warren Togami
2004-02-02 15:22       ` Fabrice Bellet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=401D6FD8.2040406@redhat.com \
    --to=wtogami@redhat.com \
    --cc=csmith@redhat.com \
    --cc=fabrice@bellet.info \
    --cc=fedora-devel-list@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=notting@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox