RTL8139 Carbus Card fails to activate

Jorn Argelo jorn at wcborstel.nl
Thu Dec 9 12:50:53 PST 2004


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 
> > > in solving it.  Now that I have some more information about it and a 
> > > better understanding I hope this problem can be fixed.  I have a 
> > > 10/100 fast ethernet carbus card that uses the realtek 8139 chipset 
> > > that I'd like to use with FreeBSD.  I have 5.3-RELEASE installed on 
> > > a PIII Celeron in a Compaq Presario Laptop.  The card is reconized 
> > > and the rl driver seems to load, but fails to map the card's memory 
> > > or i/o ports.  Here is the appropriate kernel messages:
> > > 
> > > 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
> > 
> > Well, if you ask me, your card is simply not supported by the rl or the 
re 
> > driver (Correct me if I'm wrong). Or your card is broken. Can you confirm 
that 
> > the card is still 100% functional?
> 
> 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.

I don't think that the Linux and FreeBSD drivers for the realtek cards are 
quite the same :) After all, they have to talk to different kernels. So I 
still think that your card is simply not supported by the drivers FreeBSD 
provides.

> 
> > 
> > Cheers,
> > 
> > Jorn
> > 
> > > 
> > > Intrestingly, it looks like two different realtek drivers are trying 
> > > to access it, re and rl.  Can this cause a problem and is there a 
> > > way to determine the correct driver for it?  I think rl is the one I 
> > > need. Here's pciconf -vl for the card:
> > > 
> > > none3 at pci2:0:0: class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10
> > > hdr=0x00
> > >     vendor   = 'Realtek Semiconductor'
> > >     device   = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter'
> > >     class    = network
> > >     subclass = ethernet
> > > 
> > > 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?
> > > 
> > > 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.
> > > 
> > > -- 
> > > 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
> > > 
> > > _______________________________________________
> > > freebsd-questions at freebsd.org mailing list
> > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > > To unsubscribe, send any mail to "freebsd-questions-
unsubscribe at freebsd.org"
> 
> -- 
> 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
> 
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"



More information about the freebsd-questions mailing list