Re: problems with Xircom REM56G (non-Cardbus) on -CURRENT

Stijn Hoop <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
On Thu, Jun 27, 2002 at 12:00:11PM -0600, M. Warner Losh wrote:
> In message: <[email protected]>
>             M. Warner Losh <[email protected]> writes:
> : 
> : You might want to try to set machdep.pccard.mem_start and/or .mem_end
> : to see if you can get things working right.
> 
> Alternatively, the following patch might help:
> 
> Index: pccard_nbk.c
> ===================================================================
> RCS file: /home/imp/FreeBSD/CVS/src/sys/pccard/pccard_nbk.c,v
> retrieving revision 1.40
> diff -u -r1.40 pccard_nbk.c
> --- pccard_nbk.c	30 May 2002 18:48:44 -0000	1.40
> +++ pccard_nbk.c	27 Jun 2002 18:00:06 -0000
> @@ -86,8 +86,13 @@
>  
>  SYSCTL_NODE(_machdep, OID_AUTO, pccard, CTLFLAG_RW, 0, "pccard");
>  
> +#ifdef UNSAFE
>  static u_long mem_start = IOM_BEGIN;
>  static u_long mem_end = IOM_END;
> +#else
> +static u_long mem_start = 0xd0000;
> +static u_long mem_end = 0xeffff;
> +#endif
>  
>  SYSCTL_ULONG(_machdep_pccard, OID_AUTO, mem_start, CTLFLAG_RW,
>      &mem_start, 0, "");

Still no luck with both methods. Rebuilding & installing a GENERIC kernel
would make the patch work, right?

I tried setting machdep.pccard.mem_start to 0xd0000, 0xd1000,
0xd4000 & 0xd8000. I also set machdep.pccard.mem_end to 0xd1fff one time.

I would still get the message:

Jun 28 13:07:53 nbwin141 pccardd[146]: driver allocation failed for Xircom(Creditcard Ethernet 10/100 + Modem 56): Device not configured

Any other options left?

--Stijn

-- 
Tact, n.:
	The unsaid part of what you're thinking.
signature.asc (application/pgp-signature, 187 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE9HEQwY3r/tLQmfWcRAotmAJ9/Z/9wDMUCA4j32p+YLAL6a0o9UwCeMOgP
aUKFSu2KhafsNskqOa27c4E=
=TLxo
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.