Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 6 Feb 2001 16:23:28 +1030
From:      Greg Lehey <grog@lemis.com>
To:        Simon Epsteyn <seva@sevatech.com>
Cc:        freebsd-mobile@FreeBSD.ORG, Chris Yeoh <cyeoh@linuxcare.com.au>, Anton Blanchard <anton@linuxcare.com>
Subject:   Re: AiroNet 'No card in database for "(null)"("(null)")' problem (4.2-STABLE)
Message-ID:  <20010206162328.A682@wantadilla.lemis.com>
In-Reply-To: <Pine.LNX.4.10.10102051746360.7871-100000@null.cc.uic.edu>; from seva@sevatech.com on Mon, Feb 05, 2001 at 05:48:48PM -0600
References:  <200101060216.f062GBs58426@harmony.village.org> <Pine.LNX.4.10.10102051746360.7871-100000@null.cc.uic.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Monday,  5 February 2001 at 17:48:48 -0600, Simon Epsteyn wrote:
> On Fri, 5 Jan 2001, Warner Losh wrote:
>
>> In message <20010105131448.I48589@wantadilla.lemis.com> Greg Lehey writes:
>>>> The new bus kludge code does clip start and end to 0xd0000, but you
>>>> are right that is bogus.  On most machines, this is the only space
>>>> available.
>>>
>>> Right, but we shouldn't rely on that.  Anyway, it's not the only
>>> problem.
>>
>> Agreed, but at the moment it solves more problems than it causes.
>> Until we can bring the NEWCARD online, it is likely the least evil
>> thing we can do.
>
> BTW, this is what Linux thinks about the card:
>
> This is kind of odd: cs: memory probe 0xa0000000-0xa0ffffff: clean.
>
> Linux PCMCIA Card Services 3.1.19
>   kernel build: 2.2.16-22 #1 Tue Aug 22 16:49:06 EDT 2000
>   options:  [pci] [cardbus] [apm]
> PCI routing table version 1.0 at 0xfdf50
>   00:0a.0 -> irq 9
> Intel PCIC probe:
>   Ricoh RL5C475 rev 00 PCI-to-CardBus at slot 00:0a, mem 0x68000000
>     host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 32/34]
>     ISA irqs (default) = 3,4,5,7,10,11,12 PCI status changes
> cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
> cs: IO port probe 0x0800-0x08ff: clean.
> cs: IO port probe 0x0100-0x04ff: excluding 0x140-0x147 0x378-0x37f 0x4d0-0x4d7
> cs: IO port probe 0x0a00-0x0aff: clean.
> cs: memory probe 0xa0000000-0xa0ffffff: clean.
> airo:  Probing for PCI adapters
> airo:  Finished probing for PCI adapters
> airo: Doing fast bap_reads
> airo: MAC enabled  0:40:96:15:64:ab
> eth1: index 0x05: Vcc 5.0, Vpp 5.0, irq 3, io 0x0100-0x013f

Hmm.  It's a pity Linux doesn't give more information about the ID
strings.  About the only obvious thing identifying the card is the MAC
address, and it's nothing like the ones I have here:

ray0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.109.197.245 netmask 0xffffffc0 broadcast 192.109.197.255
        inet6 fe80::200:f1ff:fe10:f99f%ray0 prefixlen 64 scopeid 0xa 
        ether 00:00:f1:10:f9:9f 
        vlan: 0 parent interface: <none>
ray0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::200:f1ff:fe10:fcc2%ray0 prefixlen 64 scopeid 0xa 
        inet 192.109.197.243 netmask 0xffffffc0 broadcast 192.109.197.255
        ether 00:00:f1:10:fc:c2 
        vlan: 0 parent interface: <none>
ray0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::200:f1ff:fe10:fcc1%ray0 prefixlen 64 scopeid 0x9 
        inet 192.109.197.244 netmask 0xffffffc0 broadcast 192.109.197.255
        ether 00:00:f1:10:fc:c1 
        vlan: 0 parent interface: <none>

They could be lookalikes, of course.  Is there a way to display the
CIS strings?

Greg
--
Finger grog@lemis.com for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010206162328.A682>