Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Sep 2002 22:23:49 -1000 (HST)
From:      Vincent Poy <vince@oahu.WURLDLINK.NET>
To:        "M. Warner Losh" <imp@bsdimp.com>
Cc:        FreeBSD-mobile@FreeBSD.ORG
Subject:   Re: Intel Mobile fxp Cardbus cards supported?
Message-ID:  <20020926222224.T45901-100000@oahu.WURLDLINK.NET>
In-Reply-To: <20020926.212927.127177161.imp@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 26 Sep 2002, M. Warner Losh wrote:

> In message: <20020926000019.A45901-100000@oahu.WURLDLINK.NET>
>             Vincent Poy <vince@oahu.WURLDLINK.NET> writes:
> : On Fri, 20 Sep 2002, M. Warner Losh wrote:
> :
> : > In message: <20020920132717.O3782-100000@oahu.WURLDLINK.NET>
> : >             Vincent Poy <vince@oahu.WURLDLINK.NET> writes:
> : > : 	Which model of the cardbus card are you using?  I'm going to try
> : > : the MBLA3300C3 next which is the one without the modem.
> : >
> : > MBLA3300 is the one that I've used.
> : >
> : > fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0x1000-0x103f mem 0xf4020000-0xf403ffff,0xf4040000-0xf4040fff irq 10 at device 0.0 on cardbus0
> : > fxp0: Disabling dynamic standby mode in EEPROM
> : > fxp0: New EEPROM ID: 0x4880
> : > fxp0: EEPROM checksum @ 0xff: 0x7a17 -> 0x7a19
> : > fxp0: Ethernet address 00:d0:b7:02:0e:f6
> : > inphy0: <i82555 10/100 media interface> on miibus0
> : > inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> : >
> : > is what dmesg says when I insert the card.  I've not used it in a
> : > little while, but the new EEPROM ID is something I should look into.
>
> I only get that message once.
>
> : 	After trying the MBLA3300, MBLA3300C3, MBLA3356C3 on both the IBM
> : ThinkPad 770Z and the Dell Inspiron 8200, all three cards had the
> : following results:
>
> Then there's something wrong with these machines.  The MBLA3300 works
> pefectly on my inspiron 8000.  Something else must be keeping you from
> using these cards on the machines that you are trying it on.  It is
> clear from the behavior that these machines can't memory map to
> 0xf4020000 because all reads from the card appear to return
> 0xffffffff.

	Hmmm, is there a way to fix this or a way to find what's actually
causing it?  With the dc0 cards, it does memory map to something else
other than 0xffffffff.

dc0: <Accton EN2242 MiniPCI 10/100BaseTX> port 0x1000-0x10ff mem
0x88000000-0x880003ff irq 11 at device 0.0 on cardbus0


Cheers,
Vince - vince@WURLDLINK.NET - Vice President             ________   __ ____
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
WurldLink Corporation                                  / / / /  | /  | __] ]
San Francisco - Honolulu - Hong Kong                  / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____]
Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin


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?20020926222224.T45901-100000>