Date: Thu, 9 Dec 2004 23:52:31 -0800 From: "Loren M. Lang" <lorenl@alzatex.com> To: Jorn Argelo <jorn@wcborstel.nl> Cc: questions@freebsd.org Subject: Re: RTL8139 Carbus Card fails to activate Message-ID: <20041210075231.GD32126@alzatex.com> In-Reply-To: <20041209204912.M55795@wcborstel.nl> References: <20041209074943.GA32126@alzatex.com> <20041209090252.M75753@wcborstel.nl> <20041209145821.GC32126@alzatex.com> <20041209204912.M55795@wcborstel.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 09, 2004 at 09:51:09PM +0100, Jorn Argelo wrote: > On Thu, 9 Dec 2004 06:58:21 -0800, Loren M. Lang wrote > > On Thu, Dec 09, 2004 at 10:05:30AM +0100, Jorn Argelo wrote: > > > On Wed, 8 Dec 2004 23:49:43 -0800, Loren M. Lang wrote > > > > I sent a request for help on this problem earlier, but with no luck= =20 > > > > in solving it. Now that I have some more information about it and = a=20 > > > > better understanding I hope this problem can be fixed. I have a=20 > > > > 10/100 fast ethernet carbus card that uses the realtek 8139 chipset= =20 > > > > that I'd like to use with FreeBSD. I have 5.3-RELEASE installed on= =20 > > > > a PIII Celeron in a Compaq Presario Laptop. The card is reconized= =20 > > > > and the rl driver seems to load, but fails to map the card's memory= =20 > > > > or i/o ports. Here is the appropriate kernel messages: > > > >=20 > > > > cbb alloc res fail > > > > cardbus0: Can't get memory for IO ports > > > > cbb alloc res fail > > > > re0: couldn't map ports/memory > > > > cbb alloc res fail > > > > rl0: couldn't map ports/memory > > > > cardbus0: <network, ethernet> at device 0.0 (no driver attached) > > > > cbb0: CardBus card activation failed > > >=20 > > > Well, if you ask me, your card is simply not supported by the rl or t= he=20 > re=20 > > > driver (Correct me if I'm wrong). Or your card is broken. Can you con= firm=20 > that=20 > > > the card is still 100% functional? > >=20 > > A few months ago I tried getting this card working and couldn't, before > > then and after then it's been used in a linux laptop just fine with the > > rtl8139 and 8130too drivers. Now I just traded it with the linux laptop > > again and it still doesn't work with freebsd. >=20 > I don't think that the Linux and FreeBSD drivers for the realtek cards ar= e=20 > quite the same :) After all, they have to talk to different kernels. So I= =20 > still think that your card is simply not supported by the drivers FreeBSD= =20 > provides. >=20 I wasn't saying that since Linux supports it, FreeBSD should too, but I was just confirming that the card is 100% functional. The annoying part is that they're both open source oses, but I can't just copy code or model it after the other without violating a license or two. If I didn't have that to worry about, I could probably get the card to work pretty easily. > >=20 > > >=20 > > > Cheers, > > >=20 > > > Jorn > > >=20 > > > >=20 > > > > Intrestingly, it looks like two different realtek drivers are tryin= g=20 > > > > to access it, re and rl. Can this cause a problem and is there a= =20 > > > > way to determine the correct driver for it? I think rl is the one = I=20 > > > > need. Here's pciconf -vl for the card: > > > >=20 > > > > none3@pci2:0:0: class=3D0x020000 card=3D0x813910ec chip=3D0x813910e= c rev=3D0x10 > > > > hdr=3D0x00 > > > > vendor =3D 'Realtek Semiconductor' > > > > device =3D 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter' > > > > class =3D network > > > > subclass =3D ethernet > > > >=20 > > > > Also, /dev/card0 does not exist, is this a legacy item from 4.x and > > > > earlier. If so, then pccardd and pccardc are also no longer needed? > > > >=20 > > > > It seems like somewhere I saw a similar problem with another cardbus > > > > card and the solution was to set some sysctl like allow_unsupported > > > > something or another in the loader at boot. > > > >=20 > > > > --=20 > > > > I sense much NT in you. > > > > NT leads to Bluescreen. > > > > Bluescreen leads to downtime. > > > > Downtime leads to suffering. > > > > NT is the path to the darkside. > > > > Powerful Unix is. > > > >=20 > > > > Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc > > > > Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C > > > >=20 > > > > _______________________________________________ > > > > freebsd-questions@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" > >=20 > > --=20 > > I sense much NT in you. > > NT leads to Bluescreen. > > Bluescreen leads to downtime. > > Downtime leads to suffering. > > NT is the path to the darkside. > > Powerful Unix is. > >=20 > > Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc > > Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C > >=20 > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd= .org" --=20 I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C =20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041210075231.GD32126>