Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 9 Oct 1999 16:59:26 +0100
From:      Scott Mitchell <s.mitchell@computer.org>
To:        Richard Puga <puga@mauibuilt.com>
Cc:        freebsd-mobile@freebsd.org, freebsd-xircom@lovett.com
Subject:   Re: Real Port Combo cardbus or legacy?
Message-ID:  <19991009165926.B654@lungfish.freeserve.co.uk>
In-Reply-To: <37FB413C.FBF8A0A5@mauibuilt.com>; from Richard Puga on Wed, Oct 06, 1999 at 02:31:56AM -1000
References:  <37FB413C.FBF8A0A5@mauibuilt.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 06, 1999 at 02:31:56AM -1000, Richard Puga wrote:
> 
> 
> Do any of the RealPort 10/100+ 56kModem cards work with FreeBSD
> 3.3-RELEASE using
> PAO3-19991005.tar.gz?

The RealPort is probably the best supported of any of the Xircom cards --
it certainly runs under 3.2-RELEASE and relatively recent incarnations of
-STABLE.  Not sure about 3.3 specifically though as I haven't upgraded
yet.  I expect someone on the freebsd-xircom list has tried it
though.. guys?

Using PAO is a bit of an unknown factor as well.  Have you tried it with a
non-PAO kernel?

> I tried a frends card with no luck..
> 
> I tried using
> ftp://dogma.freebsd-uk.eu.org/pub/scott/xe_drv/xe_drv-1.20.tar.gz but
> the files in
> /usr/src/sys/dev/pccard seemed to be newer and referance a
> differant location.
> 
> I tried configurations 0x27 0xf 0x1f 0x17 and 0x3f.
> 
> 0x3f and 0x1f brought up the xe0 device with errors. I dont have the
> card any more so i cant post more robust errors other than what I have
> left over in
> /var/log/messages..
> 
> Oct  5 15:16:03 ricoh /kernel: card1: assign xe0 iobase 0x2e8 irq 9
> Oct  5 15:16:04 ricoh /kernel: xe: Probing for unit 0
> Oct  5 15:16:04 ricoh /kernel: xe0: attach
> Oct  5 15:16:04 ricoh /kernel:
> Oct  5 15:16:04 ricoh /kernel: xe0: Xircom CEM56, bonding version 0x55,
> 100Mbps capable, with modem
> Oct  5 15:16:04 ricoh /kernel: xe0: DingoID = 0x444b, RevisionID = 0x1,
> VendorID = 0
> Oct  5 15:16:04 ricoh /kernel: xe0: Ethernet address 00:10:a4:fb:0d:0f
> Oct  5 15:16:04 ricoh /kernel: xe0: hard_reset
> Oct  5 15:16:04 ricoh /kernel: xe0: setmedia
> Oct  5 15:16:04 ricoh /kernel: xe0: disable_intr
> Oct  5 15:16:04 ricoh /kernel: xe0: init
> Oct  5 15:16:06 ricoh /kernel: xe0: setmedia
> Oct  5 15:16:06 ricoh /kernel: xe0: disable_intr
> Oct  5 15:16:06 ricoh /kernel: xe0: soft_reset
> Oct  5 15:16:06 ricoh /kernel: xe0: silicon revision = 5
> Oct  5 15:16:06 ricoh /kernel: xe0: disable_intr
> Oct  5 15:16:06 ricoh /kernel: xe0: MII registers:  0:3400 1:7809 4:01e1
> 5:0000 6:0000

Those look like the normal output you'd get for a working card.  What
symptoms did you have when it didn't work? ie., did any of the dongle LEDs
come on, could you send or receive at all, did you get timeouts?

There may well be some changes needed for the driver to work with 3.3, so
any info you can provide is useful.

Cheers,

	Scott
-- 
===========================================================================
Scott Mitchell          | PGP Key ID |"If I can't have my coffee, I'm just
Cambridge, England      | 0x54B171B9 | like a dried up piece of roast goat"
s.mitchell@computer.org | 0xAA775B8B |     -- J. S. Bach.


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?19991009165926.B654>