From owner-freebsd-mobile Tue Jan 15 4:33: 6 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from eng05.embratel.net.br (eng05.embratel.net.br [200.255.125.133]) by hub.freebsd.org (Postfix) with ESMTP id 85DB537B41A for ; Tue, 15 Jan 2002 04:32:57 -0800 (PST) Received: from embratel.net.br (uni-eng.embratel.net.br [200.255.125.98]) by eng05.embratel.net.br (Postfix) with ESMTP id 0D01024D69; Tue, 15 Jan 2002 10:32:56 -0200 (BRST) Message-ID: <3C442161.EC6989AD@embratel.net.br> Date: Tue, 15 Jan 2002 10:32:33 -0200 From: Joao Carlos Mendes Luis Organization: Internet via Embratel X-Mailer: Mozilla 4.76 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Scott Mitchell Cc: Kevin Oberman , freebsd-mobile@FreeBSD.ORG, John Gordon Subject: Re: xe driver broken? (Solution) References: <20020111230700.815875D17@ptavv.es.net> <3C431F29.E29A38AF@embratel.net.br> <20020114213258.A516@localhost> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Scott Mitchell wrote: > On Mon, Jan 14, 2002 at 04:10:49PM -0200, Joao Carlos Mendes Luis wrote: > > Kevin Oberman wrote: > > > OK. The issue is to figure out why the driver is having a problem > > > loading. A common cause of this is iomem address conflict, so lets try > > > adjusting that. > > > > > > Try this: > > > sysctl -w machdep.pccard.mem_start=0xd00000 > > > > Something changed, but still did not work. The CIS mapping could read > > something, but still, nonsense. Went to the sources, and suspected you meant > > 0xd0000, one zero less. It worked! > > > > Looking in Windows resources, pcmcia devices start using from 0xcc000. > > Tried this, and it is working. > > > > Setting sysctl from rc.local is not useful, since I need to remove and > > reinsert the card before using it. I tried to fix it by setting the default > > at /boot/loader.conf, but it did not work. Setting it at /etc/sysctl.conf > > seems to work, but there is a race condition. Maybe the memory range > > detection should be fixed, and/or loader should be taught how to set it. > > You can set pccard_mem in /etc/rc.conf, or tweak the resource pool settings > in /etc/pccard.conf -- these should both be read before pccardc attempts to > configure the card. If these should work, then there is another bug. The default for rc.conf is 0xd0000 and the default for pccard.conf is 0xd4000. These values would probably work, if they were indeed used. BTW: Is there a userland utility to map all resources used and/or bus tree? Something like Windows 9x device manager. This is something I'd like to see, and would surely help people with hardware conflicts. Jonny -- João Carlos Mendes Luís jonny@embratel.net.br Networking Engineer jonny@jonny.eng.br Internet via Embratel jcml@ieee.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message