Date: Thu, 24 Jan 2002 15:22:13 -0800 From: "Kevin Oberman" <oberman@es.net> To: "Tom Skoglund" <tomsk@chello.no> Cc: freebsd-mobile@FreeBSD.org Subject: Re: REM56G-100 and 4.5-RC2 Message-ID: <20020124232213.202F65D13@ptavv.es.net> In-Reply-To: Your message of "Thu, 24 Jan 2002 22:02:44 %2B0100." <005201c1a51a$783422e0$0605800a@chello.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: "Tom Skoglund" <tomsk@chello.no>
> Date: Thu, 24 Jan 2002 22:02:44 +0100
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_004F_01C1A522.D99CFD60
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> "Kevin Oberman" <oberman@es.net> wrote:
> > > From: "Tom Skoglund" <tomsk@chello.no>
> > > Date: Thu, 24 Jan 2002 19:17:38 +0100
> > > Sender: owner-freebsd-mobile@FreeBSD.ORG
> > >
> > > Hi again,
> > >
> > > I have sort of postponed my attempt to get the Xircom Cardbus
> > > (RBEM56G-100) working on current. I started debugging the code, but I
> > > don't have enough time to do it properly these days.
> > >
> > > I then got hold of a 16-bit Xircom (REM56G-100) and gave 4.5-RC2 a
> shot.
> > > Here I try to use the XE driver, but it keeps locking the machine each
> > > time I start pccardd. It reads:
> > > Card "Xircom"("CreditCard Ethernet 10/100 +Modem56") [CEM56] [1.00]
> > > matched "Xircom" ("CreditCard Ethernet 10/100 + Modem 56") [(null)]
> > > [(null)]
> > > xe0 at port 0x2e8-0x2ef iomem 0xd0000-0xd0fff irq 11 slot 0 on pccard0
> > >
> > > and then locks up. I have tried all sorts of other irq's, and also
> using
> > > "-z -I" (also -i with supplied irq), but it always locks up...:(
> > >
> > > I have also tried the "old" irq routing (hw.pcic.intr_path="1",
> > > hw.pcic.irq="0"), but still no cigar.
> > > I tested some other cards, Etherlink III and one other. They both
> works
> > > fine but are only 10Mb, and the HUB I use at home is pure 100Mb.
> > >
> > > Anyone else had some luck with this card?
> >
> > I use the RE-100, the Ethernet only version of the card, with no
> > problem. Can you send a dmesg of the boot. Specifically the pcic
> > and pccard information is of some interest. There are a few bridge
> > devices that are known to have problems.
> >
> > Best guess: try setting the following sysctl:
> > sysctl -w machdep.pccard.mem_start=0xd0000
> >
> > If it works, put it into /etc/sysctl.conf.
> >
> > If not, try 0xd4000 and 0xd8000.
>
>
> Nothing spectacular in the dmesg. I have tried setting ...mem_start=0xd000
> (it wass a bit lower in the kernel I saw) but not real change still. It's
> kind of boring trying to set a new parameter somewhere, and then have to
> reboot with a fsck each time it locks up. The settings does not always
> seem to take effect either regardless of using -I or not.
Was this a typo? You want 0xd0000, 0xd4000, or 0xd8000. 0xd000 has a
near zero probability of success.
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net Phone: +1 510 486-8634
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?20020124232213.202F65D13>