Date: Mon, 14 Jan 2002 16:10:49 -0200 From: Joao Carlos Mendes Luis <jonny@embratel.net.br> To: Kevin Oberman <oberman@ptavv.es.net> Cc: freebsd-mobile@freebsd.org, John Gordon <john.gordon@windriver.com> Subject: Re: xe driver broken? (Solution) Message-ID: <3C431F29.E29A38AF@embratel.net.br> References: <20020111230700.815875D17@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
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.
Thanks everybody,
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C431F29.E29A38AF>