Date: Wed, 01 Aug 2001 21:02:24 +0100 From: Ian Dowse <iedowse@maths.tcd.ie> To: Marc Fonvieille <fonvi@easynet.fr> Cc: freebsd-mobile@freebsd.org Subject: Re: Better patches [long] Message-ID: <200108012102.aa07501@salmon.maths.tcd.ie> In-Reply-To: Your message of "Wed, 01 Aug 2001 21:30:54 %2B0200." <20010801213054.A24151@gothic.blackend.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20010801213054.A24151@gothic.blackend.org>, Marc Fonvieille writes: >However nothing about miibus appears in logs. > >Aug 1 20:58:07 marduk pccardd[102]: ed1: NETGEAR (FA410TX) inserted. >Aug 1 20:58:07 marduk /kernel: ed1 at port 0x300-0x31f irq 3 slot 0 on pccard0 >Aug 1 20:58:07 marduk /kernel: ed1: address 00:e0:98:7a:f5:61, type Linksys (16 bit) >device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 > >device miibus >device ed0 at isa? This is certainly odd; all FA410 cards that I have seen do have an miibus interface, even the old ones that didn't require fa_select. The only thing I can think of is that there might be an unknown device at IO address 0x31c (the miibus port is the base + 0x1c) that is conflicting with the miibus part of the card's IO space, but not the main interface. Maybe try changing the range of free IO addresses in pccard.conf to see if the miibus stuff is detected when the card gets a different IO address. At what IO address was the card working previously with fa_select? If the ed driver does not detect an miibus, it will not attempt to talk to the miibus port again, so it should be safe to try running fa_select. If you can't get fa_select to work, then it really suggests that something has changed hardware-wise since it last worked for you. A dmesg from when the card was working would be very helpful for comparison. Ian 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? <200108012102.aa07501>