Use this page to discuss issues with Xircom ethernet cards. This includes the 16-bit cards (xirc2ps_cs driver) as well as the newer CardBus adapters (tulip_cb driver). Before posting, be sure you've checked any relevant sections of the PCMCIA-HOWTO, such as: Particularly useful bits of information to post include your laptop's make and model; the type(s) of card(s) you are using; and, of course, any relevant system log messages.

Messages Inline: 0 1

Question CE3 and 100mbs only (the old story...)

Date: 1999, Oct 29
From: Peter Schäfer peter

Hi (not very much traffic here...)!

I've got the old problem with a CE3: it works only at 100mbs. The patch from the old message board (seems to write the same thing as a "two liner") doesn't work for me.

So, i think i know what a compiler is and have a non-working card at hand - perhaps i can try something out as the packages seems to be unmaintained at the moment.

Does anybody have some documentation about the tranceiver of this card? Patches?

Thanks for your help!

CU

Peter

Sad CE3 / RealPort 10/100 - Me too.

Re: Question CE3 and 100mbs only (the old story...) (Peter Schäfer)
Date: 1999, Nov 05
From: Mark Harvey <mark.harvey@enstor.com.au>

I've been waiting on a reply to the 10/100 problem because I have the same problem.

On the Xircom RealPort 10/100 it will only work at 100Mbit. Using a Xircom CE3-10/100 will only work at 10Mbit.

The same driver is used in both cases.

Caldera 2.3, pcmcia 3.0.14 (complied from source), Kernel 2.2.13.

Any ideas on a solution (or sugestion).

Best regards Mark Harvey

Ok SUCCESS (finally!)

Re: Question CE3 and 100mbs only (the old story...) (Peter Schäfer)
Date: 1999, Nov 05
From: Peter Schäfer peter

Hi!

I've downloaded the newest package from the NEWS directory at ftp.sourceforge.org (pcmcia-cs.02-Nov-99). That works for me with a Toshiba Tecra8000, Xircom Creditcard CE3B and Kernel 2.2.13.

Try it!

Ok Success

Re: Question CE3 and 100mbs only (the old story...) (Peter Schäfer)
Date: 1999, Nov 10
From: Mark Harvey <mark.harvey@enstor.com.au>

Many thanks to David Hinds...

Downloaded the latest 04-Nov-99 pcmcia package. Works a treat.

I did come across a problem with it crashing the system if I added the PnP BIOS resource checking however.

Best regards Mark Harvey

Note CBEM56G

Date: 1999, Oct 29
From: Chris Kees kees

I just upgraded my pcmcia from 3.1.0 to 3.1.3 (kernel = 2.2.5-22, Inspiron 7000) because I was having trouble starting and stopping pcmcia repeatedly. Under 3.1.0 and 3.1.1 there was a problem with the interrupt allocation that looked like the available interrupts were disappearing. When I had the CardBus controller try a PCI interrupt it worked through one restart and then gave the same problem.

The new version 3.1.3 seems to have fixed that problem, but I ran into some minor problems with my network configuration. Basically, something was wrong with the network configuration when configured by the pcmcia network script. If I bypass the pcmcia network configuration by commenting out the network parameters and putting ifup eth0 in the start_fn (similarly ifdown in stop_fn) then the network gets configured correctly, and I can start and stop card services repeatedly.

To get pcmcia to cooperate with apm I had to put sleep 10 before and after the calls to /etc/rc.d/init.d/pcmcia stop(and start) in the apmd_proxy script. I could not get cardctl eject and insert to work with apm--eject worked, but I had to manually remove the card and reinsert it after I did a resume. I tried it with some pauses around cardctl eject/insert, but that didn't work.

These fixes allow me to move around without rebooting my machine but they're not optimal. I'll be glad to provide log messages to anybody who's working on this more seriously.

None Re: Note: CBEM56G

Re: Note CBEM56G (Chris Kees)
Date: 1999, Oct 29
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Fri, Oct 29, 1999 at 02:05:53PM -0700, Chris Kees wrote:
> 
> If I bypass the pcmcia network configuration by
> commenting out the network parameters and putting ifup eth0 in the
> start_fn (similarly ifdown in stop_fn) then the network gets configured
> correctly, and I can start and stop card services repeatedly.

This is as expected for a Red Hat installation; it is mentioned in the
PCMCIA-HOWTO, also.

> To get pcmcia to cooperate with apm I had to put sleep 10 before and
> after the calls to /etc/rc.d/init.d/pcmcia stop(and start) in the
> apmd_proxy script. I could not get cardctl eject and insert to work with
> apm--eject worked, but I had to manually remove the card and reinsert it
> after I did a resume.

The tulip_cb driver currently doesn't handle suspend and resume
events.  I did try to fix this once, but there was something tricky
about the power-up sequence that I couldn't get to work right.  The
driver startup code is somewhat convoluted, because it is written to
handle a lot of different card variants.

-- Dave

None Re: Note: CBEM56G

Re: None Re: Note: CBEM56G (David Hinds)
Date: 1999, Oct 29
From: Chris Kees kees

David Hinds wrote:
> 
> This is as expected for a Red Hat installation; it is mentioned in the
> PCMCIA-HOWTO, also.
> 

The reason I put those calls in start_fn was because I had seen it
suggested in the HOWTO, but everything was working fine with 3.1.0 and
3.1.1 just using the scripts that came with the pcmcia package. I
thought the notes in the HOWTO meant that you could use Redhat with the
workaround if you wanted to. I was keeping all my network configuration
information in network.opts instead of fooling with the Redhat stuff
because I've got some AFS client software that I liked to start and stop
in start(stop)_fn. I pulled that out for now because I didn't want to
complicate things.

> > after I did a resume.
> 

I meant to say insert here. I don't appear to be having any problems
using cardctl insert and eject with the the current package which is why
I thought I could just use them with apm instead of shutting down the
whole pcmcia package with pcmcia stop. Should I avoid using eject and
insert as well as suspend/resume? Are eject and insert actually doing
suspend and resume?

-Chris

None Re: Note: CBEM56G

Re: None Re: Note: CBEM56G (Chris Kees)
Date: 1999, Oct 29
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Fri, Oct 29, 1999 at 03:01:23PM -0700, Chris Kees wrote:
> 
> The reason I put those calls in start_fn was because I had seen it
> suggested in the HOWTO, but everything was working fine with 3.1.0 and
> 3.1.1 just using the scripts that came with the pcmcia package.

Then in that case I'm not sure what's going on.  I don't see any
relevant changes in the 3.1.2-3.1.3 network scripts.  To diagnose, you
should verify that the network script isn't putting any errors in the
system log.  You can also run the script by hand ("/etc/pcmcia/network
start eth0", or "sh -x /etc/pcmcia/network start eth0") to see exactly
what it is doing.

> I meant to say insert here. I don't appear to be having any problems
> using cardctl insert and eject with the the current package which is why
> I thought I could just use them with apm instead of shutting down the
> whole pcmcia package with pcmcia stop.

You should be able to use insert and eject, and no, they don't do the
same thing as suspend and resume.  It might be that there are some
weird timing issues at resume time; most of my cards work correctly
across suspend/resume so I haven't experimented with setups like this.

-- Dave

More IBM CardBus EtherJet saga continues..

Date: 1999, Nov 03
From: Paul Kronenwetter kronenpj

Background: IBM ThinkPad 600 with IBM CardBus EtherJet + 56K modem in 10BT mode. Redhat Linux 6.0 with Kernel rev 2.2.12 (see below). Pcmcia-cs-3.1.[123] (again see below). /var/log/message data is uninteresting (or at least unchanged from the posts on hyper.stanford.

Under Linux kernel rev 2.2.12 and pcmcia-cs-3.1.3 things went downhill. I couldn't ping anything, all I saw were destination unreachable messages from ping.

Figuring things were generally better but tulip_cb.c was a little worse, I took my modified source from 3.1.2 (tulip_cb.c v0.91g, patch at http://n2kiq.fdns.net/tulip_cb.c_91-91g.patch UNOFFICIAL combination of tulip_cb.c v0.91 and Donald Becker's tulip.c v0.91g experimental version.)

After re-compiling things got better, actually a fair bit better as I can ifconfig the interface down and back up and things work again. While searching for another update to the 0.91 series, I found that Mr. Becker created a tulip debugging program that dumped information about the card's state.

Running that at various times gives interesting information. When things are ok it gives the following status:

  • RX Process - Waiting for packets
  • TX Process - Idle
  • TX Timeout - 128

When things are bad (i.e. getting no response at all from ping) it gives this:

  • RX Process - Suspended -- No RX buffers
  • TX Process - Idle
  • TX Timeout - (varies from 128 to 512)

Doing the ifconfig down/up resets the RX process and things continue, for a while. It also says that the EEPROM is #6 and in an old style EEPROM layout, which may cause some features to be unavailable.

I've captured packets on another machine and the stuff the driver sends appears to be correct, it didn't say anything about corrupted packets. The stuff it did see was sometimes out of sequence, which I thought was strange.

-Paul

Warning I'm determined to get this thing working...

Re: More IBM CardBus EtherJet saga continues.. (Paul Kronenwetter)
Date: 1999, Dec 18
From: Paul Kronenwetter kronenpj

David,

  I'm feeling more determined to make this EtherJet Cardbus thingy work.  I'm getting tired of being trapped in Gates' World (tm).

  Unfortunately since the later 3.1.x versions have progressed, the card's performance went down hill.  I believe it can be made to work, I just don't have the background to do much with it. So...

  What can I do, where can I look, (etc) to help debug this thing? Should I be E-mailing Mr. Becker or is the tulip_cb source too out-of-sync?  Should I try anyway?

Please help! Windows is really bad! Help!

-Paul

None Not much I can do

Re: Warning I'm determined to get this thing working... (Paul Kronenwetter)
Date: 1999, Dec 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The unfortunate problem with the Xircom tulip stuff is that Donald
doesn't want to support these cards at all (which is not that
unreasonable a position; given the number of problems reported with
these cards, I'm not too happy about them either).  And there really
is no maintainer for these patches: a few people have contributed
patches, but there seem to be several card variants floating around
and no one has tried to characterize the differences between these
revisions.

There is not much I can do to help for problems that are in the tulip
driver.  I am not really familiar with the tulip chipsets... and do
not have any of these Xircom cards... and before anyone offers to send
me one, I probably wouldn't be too excited about getting more involved
in this anyway.

-- Dave

Feedback Actually, you can help - Provide gems of wisdom and guideance

Re: None Not much I can do (David Hinds)
Date: 1999, Dec 21
From: Paul Kronenwetter kronenpj

Ok, it may seem like I'm trying to butter you up or something, but I'd like to work on this. I just need to get your feeling as to where the problem might be starting. I don't know if it's the interface to the kernel, the card or something else.

It appears as though there are two problems: 1) The card/driver/kernel doesn't empty the receive buffer completely or fast enough. I don't know which. 2) The card/driver/kernel isn't actually sending packets out on time. It's tough for me to test this one, although I think I can pull it off.

I'm tempted to think it's not a kernel problem, unless the driver is neglecting to notify the kernel that there's information or buffers are empty enough to fill again.

Can that sort of help be provided, by anyone?

-Paul

More It appears to be the receive code...

Re: Feedback Actually, you can help - Provide gems of wisdom and guideance (Paul Kronenwetter)
Date: 1999, Dec 21
From: Paul Kronenwetter kronenpj

I ran a little test, the transmitted packets go out pronto. The reply comes back just as quick, but the card/driver/kernel doesn't see it for a while.

I'm instrumenting the tulip_rx routine in an attempt to localize, but it doesn't make much sense to me so far.

-Paul

Dec 20 21:29:43 pc kernel: klogd 1.3-3, log source = /proc/kmsg started.
Dec 20 21:29:43 pc kernel: Inspecting /boot/System.map-2.2.13
Dec 20 21:29:43 pc kernel: Loaded 6301 symbols from /boot/System.map-2.2.13.
Dec 20 21:29:43 pc kernel: Symbols match kernel version 2.2.13.
Dec 20 21:29:43 pc kernel: Loaded 140 symbols from 12 modules.
Dec 20 21:29:49 pc kernel: eth0: interrupt  csr5=0x60690004 new csr5=0x60680000. 
Dec 20 21:29:49 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:29:49 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:29:49 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:29:49 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:29:49 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:29:49 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:04 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:30:04 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:04 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:04 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:30:04 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:30:04 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:04 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:17 pc kernel: eth0: 21143 negotiation status 000000c2, 10baseT. 
Dec 20 21:30:19 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:30:19 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:19 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:19 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:30:19 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:30:19 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:19 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:22 pc kernel: eth0: interrupt  csr5=0x60670005 new csr5=0x60660000. 
Dec 20 21:30:22 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:22 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:22 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:30:22 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:30:22 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:22 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:25 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:30:25 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:25 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:25 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:30:25 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:30:25 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:25 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:26 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:30:26 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:26 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:26 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:30:26 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:30:26 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:26 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:27 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:30:27 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:27 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:27 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:30:27 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:30:27 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:27 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:29 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:30:29 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:29 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:29 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:30:29 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:30:29 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:29 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:30 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:30:30 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:30 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:30 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:30:30 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:30:30 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:30 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:37 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:30:37 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:37 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:37 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:30:37 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:30:37 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:37 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:42 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:30:42 pc kernel:  In tulip_rx(), entry 0 005e0300. 
Dec 20 21:30:42 pc kernel:  In tulip_rx(), entry 0 005e0300. 
Dec 20 21:30:42 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:42 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:30:57 pc kernel:  In tulip_rx(), entry 1 00eb0300. 
Dec 20 21:30:57 pc kernel:  In tulip_rx(), entry 1 00eb0300. 
Dec 20 21:30:57 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:30:57 pc kernel:  In tulip_rx(), entry 2 004e0300. 
Dec 20 21:30:57 pc kernel:  In tulip_rx(), entry 2 004e0300. 
Dec 20 21:30:57 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:30:57 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:00 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:00 pc kernel:  In tulip_rx(), entry 3 00790300. 
Dec 20 21:31:00 pc kernel:  In tulip_rx(), entry 3 00790300. 
Dec 20 21:31:00 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:00 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:00 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:00 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:00 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:00 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:00 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:00 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:00 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:00 pc kernel:  In tulip_rx(), entry 4 00460300. 
Dec 20 21:31:00 pc kernel:  In tulip_rx(), entry 4 00460300. 
Dec 20 21:31:00 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:00 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x606980c0 new csr5=0x60680000. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 5 005a0300. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 5 005a0300. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 6 00660300. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 7 00660300. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 8 00660300. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 9 00eb0300. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 10 005e0300. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 11 005e0300. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 12 00eb0300. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 13 005e0300. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 14 005e0300. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 15 00eb0300. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:31:01 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60690004 new csr5=0x60680000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:31:01 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60690004 new csr5=0x60680000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:31:01 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60670005 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:01 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:01 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:02 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:02 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:02 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:02 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:02 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:02 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:02 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:02 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:02 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:02 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:02 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:04 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:04 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:04 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:04 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:04 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:04 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:04 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:04 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:04 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:04 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:04 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:07 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:07 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:07 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:07 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:07 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:07 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:07 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:07 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:07 pc kernel:  In tulip_rx(), entry 0 00560300. 
Dec 20 21:31:07 pc kernel:  In tulip_rx(), entry 0 00560300. 
Dec 20 21:31:07 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:07 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:07 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:07 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:07 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:07 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:07 pc kernel:  In tulip_rx(), entry 1 00460300. 
Dec 20 21:31:07 pc kernel:  In tulip_rx(), entry 1 00460300. 
Dec 20 21:31:07 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:07 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 2 00650300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 2 00650300. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 3 00460300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 3 00460300. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 4 00540300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 4 00540300. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x606980c0 new csr5=0x60680000. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 5 00f40300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 5 00f40300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 6 00560300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 7 00460300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 8 00560300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 9 00460300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 10 00560300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 11 00460300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 12 00560300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 13 00460300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 14 00560300. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 15 00460300. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:31:11 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60290001 new csr5=0x60280000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60280000 new csr5=0x60280000. 
Dec 20 21:31:11 pc kernel: eth0: exiting interrupt, csr5=0x60280000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60690004 new csr5=0x60680000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:31:11 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60690004 new csr5=0x60680000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:31:11 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x606f0040 new csr5=0x606e0000. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x606e0000 new csr5=0x606e0000. 
Dec 20 21:31:11 pc kernel: eth0: exiting interrupt, csr5=0x606e0000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:11 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:11 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:11 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:12 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:12 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:12 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:12 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:12 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:12 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:12 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:12 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:12 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:13 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:13 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:13 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:13 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:13 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:13 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:13 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:13 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:13 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:13 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:13 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:14 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:14 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:14 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:14 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:14 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:14 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:14 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:14 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:14 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:14 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:14 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:17 pc kernel: eth0: 21143 negotiation status 000000c2, 10baseT. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 0 00460300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 0 00460300. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 1 01af0300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 1 01af0300. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 2 00460300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 2 00460300. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 3 00540300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 3 00540300. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 4 00460300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 4 00460300. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x606980c0 new csr5=0x60680000. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 5 00460300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 5 00460300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 6 00460300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 7 01af0300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 8 00460300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 9 01af0300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 10 00460300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 11 01af0300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 12 00460300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 13 01af0300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 14 00460300. 
Dec 20 21:31:18 pc kernel:  In tulip_rx(), entry 15 01af0300. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:31:18 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60690004 new csr5=0x60680000. 
Dec 20 21:31:18 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:31:18 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:31:28 pc kernel: eth0: interrupt  csr5=0x60690004 new csr5=0x60680000. 
Dec 20 21:31:28 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:31:28 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:31:28 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:28 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:28 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:28 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:30 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:30 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:30 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:30 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:30 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:30 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:30 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:35 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:35 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:35 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:35 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:35 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:35 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:35 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:46 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:46 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:46 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:46 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:48 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:48 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:48 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:48 pc kernel: eth0: interrupt  csr5=0x60670005 new csr5=0x60660000. 
Dec 20 21:31:48 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:48 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:48 pc kernel: eth0: interrupt  csr5=0x606f0040 new csr5=0x606e0000. 
Dec 20 21:31:48 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:48 pc kernel: eth0: interrupt  csr5=0x606e0000 new csr5=0x606e0000. 
Dec 20 21:31:48 pc kernel: eth0: exiting interrupt, csr5=0x606e0000. 
Dec 20 21:31:48 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:48 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:48 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:48 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:48 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:48 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:48 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:48 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:51 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:51 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:51 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:51 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:51 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:51 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:51 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:51 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:51 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:51 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:51 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:57 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:57 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:57 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:57 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:57 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:57 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:57 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel:  In tulip_rx(), entry 0 004e0300. 
Dec 20 21:31:58 pc kernel:  In tulip_rx(), entry 0 004e0300. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel:  In tulip_rx(), entry 1 00460300. 
Dec 20 21:31:58 pc kernel:  In tulip_rx(), entry 1 00460300. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel:  In tulip_rx(), entry 2 02b30300. 
Dec 20 21:31:58 pc kernel:  In tulip_rx(), entry 2 02b30300. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel:  In tulip_rx(), entry 3 00460300. 
Dec 20 21:31:58 pc kernel:  In tulip_rx(), entry 3 00460300. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel:  In tulip_rx(), entry 4 004e0300. 
Dec 20 21:31:58 pc kernel:  In tulip_rx(), entry 4 004e0300. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:59 pc kernel: eth0: interrupt  csr5=0x606980c0 new csr5=0x60680000. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 5 00460300. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 5 00460300. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 6 005e0300. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 7 005e0300. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 8 005e0300. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 9 005e0300. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 10 00400300. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 11 00400300. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 12 004e0300. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 13 004e0300. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 14 004e0300. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 15 004e0300. 
Dec 20 21:31:59 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:31:59 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:31:59 pc kernel: eth0: interrupt  csr5=0x60690005 new csr5=0x60680000. 
Dec 20 21:31:59 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:31:59 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:31:59 pc kernel: eth0: interrupt  csr5=0x606f0040 new csr5=0x606e0000. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:59 pc kernel: eth0: interrupt  csr5=0x606e0000 new csr5=0x606e0000. 
Dec 20 21:31:59 pc kernel: eth0: exiting interrupt, csr5=0x606e0000. 
Dec 20 21:31:59 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:59 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:59 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:31:59 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:31:59 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:31:59 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:31:59 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:00 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:32:00 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:00 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:00 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:00 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:32:00 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:00 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:02 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:32:02 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:02 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:02 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:02 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:32:02 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:02 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:02 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:02 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:32:02 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:02 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:06 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:32:06 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:06 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:07 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:07 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:32:07 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:07 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:08 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:08 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:32:08 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:08 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:15 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:32:15 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:15 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:15 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:15 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:32:15 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:15 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:17 pc kernel: eth0: 21143 negotiation status 000000c2, 10baseT. 
Dec 20 21:32:20 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:20 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:32:20 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:20 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:31 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:32:31 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:31 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:31 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:31 pc kernel:  In tulip_rx(), entry 0 005e0300. 
Dec 20 21:32:31 pc kernel:  In tulip_rx(), entry 0 005e0300. 
Dec 20 21:32:31 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:31 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:33 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:32:33 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:33 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:33 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:33 pc kernel:  In tulip_rx(), entry 1 00460300. 
Dec 20 21:32:33 pc kernel:  In tulip_rx(), entry 1 00460300. 
Dec 20 21:32:33 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:33 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:36 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:32:36 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:36 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:36 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:36 pc kernel:  In tulip_rx(), entry 2 005e0300. 
Dec 20 21:32:36 pc kernel:  In tulip_rx(), entry 2 005e0300. 
Dec 20 21:32:36 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:36 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:40 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:32:40 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:40 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:40 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:40 pc kernel:  In tulip_rx(), entry 3 005e0300. 
Dec 20 21:32:40 pc kernel:  In tulip_rx(), entry 3 005e0300. 
Dec 20 21:32:40 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:40 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:40 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:40 pc kernel:  In tulip_rx(), entry 4 005e0300. 
Dec 20 21:32:40 pc kernel:  In tulip_rx(), entry 4 005e0300. 
Dec 20 21:32:40 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:40 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:44 pc kernel: eth0: interrupt  csr5=0x606980c0 new csr5=0x60680000. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 5 00f20300. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 5 00f20300. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 6 00460300. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 7 00f20300. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 8 05ee0300. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 9 00460300. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 10 00460300. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 11 00f20300. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 12 00460300. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 13 00f20300. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 14 00460300. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 15 00f20300. 
Dec 20 21:32:44 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:32:44 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:32:44 pc kernel: eth0: interrupt  csr5=0x60690005 new csr5=0x60680000. 
Dec 20 21:32:44 pc kernel: eth0: interrupt  csr5=0x60680000 new csr5=0x60680000. 
Dec 20 21:32:44 pc kernel: eth0: exiting interrupt, csr5=0x60680000. 
Dec 20 21:32:44 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:44 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:32:44 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:44 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:50 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:50 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:32:50 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:50 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:55 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:32:55 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:55 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:55 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:32:55 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:32:55 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:55 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:56 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:32:56 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:56 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:32:58 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:32:58 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:32:58 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:33:02 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:33:02 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:33:02 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:33:11 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:33:11 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:33:11 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:33:11 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:33:11 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:33:11 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:33:11 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:33:17 pc kernel: eth0: 21143 negotiation status 000000c2, 10baseT. 
Dec 20 21:33:28 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:33:28 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:33:28 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:33:34 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:33:34 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:33:34 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:33:34 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:33:34 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:33:34 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:33:34 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:33:41 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:33:41 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:33:41 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:33:43 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:33:43 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:33:43 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:33:43 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:33:43 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:33:43 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:33:43 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:33:43 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:33:43 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:33:43 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:33:43 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:33:54 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:33:54 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:33:54 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:33:54 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:34:02 pc kernel: eth0: interrupt  csr5=0x60670004 new csr5=0x60660000. 
Dec 20 21:34:02 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:34:02 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:34:04 pc kernel: eth0: interrupt  csr5=0x60670040 new csr5=0x60660000. 
Dec 20 21:34:04 pc kernel:  In tulip_rx(), entry 0 80000000. 
Dec 20 21:34:04 pc kernel: eth0: interrupt  csr5=0x60660000 new csr5=0x60660000. 
Dec 20 21:34:04 pc kernel: eth0: exiting interrupt, csr5=0x60660000. 
Dec 20 21:34:17 pc kernel: eth0: 21143 negotiation status 000000c2, 10baseT. 

More Just spoke to IBM tech support...

Re: More It appears to be the receive code... (Paul Kronenwetter)
Date: 2000, Mar 28
From: Paul Kronenwetter kronenpj

The identity of the chipset is "CONFIDENTIAL"... But they did say that it's compatible with a Xircom of the same configuration. Yea.

They did seem willing to supply information sufficient to writing the driver. If I could ask the right questions, I think they'd send me information. I just don't know what to ask.

Pointers? -Paul

More Detailed information from 3.0.14 (hey, it works, sort of)

Re: More IBM CardBus EtherJet saga continues.. (Paul Kronenwetter)
Date: 1999, Dec 18
From: Paul Kronenwetter kronenpj

Here's the information that should have appeared in the previous post, but I couldn't supply because I didn't have it.  I've gone back to 3.0.14 'cause it at least works some of the time.  

[root@pc diag]# cat /etc/pcmcia/config.opts |more
#
# Local PCMCIA Configuration File
#
# System resources available for PCMCIA devices
#
include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff
include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff
#
# Extra port range for IBM Token Ring
#
#include port 0xa00-0xaff
#
# Resources we should not use, even if they appear to be available
#
# First built-in serial port
exclude irq 4
# Second built-in serial port
#exclude irq 3
# First built-in parallel port
exclude irq 7
#
# Examples of options for loadable modules
#
# To fix sluggish network with IBM ethernet adapter...
#module "pcnet_cs" opts "mem_speed=600"
#
# Options for Xircom Netwave driver...
#module "netwave_cs" opts "domain=0x100 scramble_key=0x0"
#
# Options for IBM Token Ring adapters
#module "ibmtr_cs" opts "mmiobase=0xd0000 srambase=0xd4000"

# ThinkPad 600 stuff
include port 0x100-0x7ff, port 0x1000-0x17ff
include memory 0xd0000-0xdffff, memory 0xa0000000-0xa0ffffff
# First built-in serial port
exclude irq 4
# Second built-in serial port
exclude irq 3
# First built-in parallel port
exclude irq 7
exclude port 0x2f8-0x2ff
exclude port 0x230-0x233
exclude irq 5
module "tulip_cb" opts "debug=255"

[root@pc diag]# cat /etc/conf.modules
alias parport_lowlevel parport_pc
pre-install pcmcia_core /etc/rc.d/init.d/pcmcia start
keep
path[pcmcia]=/lib/modules/default
path[pcmcia]=/lib/modules/preferred

alias sound-slot-0 cs4232
alias sound-service-0-0 cs4232
alias sound cs4232
alias midi opl3
options opl3 io=0x388
options cs4232 io=0x530 irq=5 dma=1 dma2=0 mpuio=0x330 mpuirq=5 synthirq=-1 synt
hio=-1

[root@pc diag]# ./tulip-diag  -p 0x1000     
tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Assuming a Digital Tulip, unknown type adapter at 0x1000.
 Port selection is MII, half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Suspended -- no Rx buffers'.
  The Tx process state is 'Idle'.
  The transmit threshold is 256.
 MII PHY found at address 0, status 0x782d.
 MII PHY #0 transceiver registers:
   3100 782d 0300 e54a 01e1 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0140 0005 0000 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 Basic mode status register 0x782d ... 782d.
   Link status: established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Vendor ID is 00:c0:39:--:--:--, model 20 rev. 10.
   Vendor/Part: TDK transceiver (unknown type).
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 0000:.
   Negotiation did not complete.
  TDK 78q2120 extra registers:
    Vendor specific register 16 is 0x0140.
      Link polarity is detected as normal.
    Vendor specific register 18 is 0x0100.
      Auto-negotiation complete, 10Mbps half duplex.
      Rx link in fail state, PLL locked.
    Vendor specific register 17 is 0x0000.
      Events since last read:

[root@pc diag]# ./tulip-diag  -p 0x1000 -e
tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Assuming a Digital Tulip, unknown type adapter at 0x1000.
 Port selection is MII, half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Suspended -- no Rx buffers'.
  The Tx process state is 'Idle'.
  The transmit threshold is 256.
EEPROM size is 6.
  * An old-style EEPROM layout was found.
  * The old-style layout does not contain transceiver control information.
  * This board may not work, or may work only with a subset of transceiver
  * options or data rates.

/etc/pcmcia/config entry

card "IBM 10/100 EtherJet CardBus Adapter with 56K Modem"
  manfid 0x00a4, 0x0103
  bind "tulip_cb" to 0, "serial_cb" to 1

Unusual ping behavior:
[pc](8:33pm) {~} % ping -i 30 gw
PING gw (192.168.0.1) from 192.168.0.11 : 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=5.1 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=1.4 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=255 time=2.8 ms
64 bytes from 192.168.0.1: icmp_seq=0 ttl=255 time=89993.6 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=255 time=6.4 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=255 time=2.9 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=255 time=0.5 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=255 time=11.6 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=255 time=11.5 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=255 time=0.5 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=255 time=9.9 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=255 time=216543.8 ms
From pc (192.168.0.11): Destination Host Unreachable
From pc (192.168.0.11): Destination Host Unreachable
From pc (192.168.0.11): Destination Host Unreachable
From pc (192.168.0.11): Destination Host Unreachable

--- gw ping statistics ---
23 packets transmitted, 12 packets received, +8 errors, 47% packet loss
round-trip min/avg/max = 0.5/25549.1/216543.8 ms
(Restarted pcmcia services)
[pc](8:44pm) {~} % ping -i 30 gw
PING gw (192.168.0.1) from 192.168.0.11 : 56(84) bytes of data.
From pc (192.168.0.11): Destination Host Unreachable
From pc (192.168.0.11): Destination Host Unreachable
64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=7.4 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=255 time=2.6 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=255 time=9.9 ms
From pc (192.168.0.11): Destination Host Unreachable
64 bytes from 192.168.0.1: icmp_seq=7 ttl=255 time=0.5 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=255 time=10.0 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=255 time=102994.2 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=255 time=14.0 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=255 time=1.1 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=255 time=0.5 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=255 time=0.5 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=255 time=9.9 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=255 time=2.9 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=255 time=0.5 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=255 time=0.5 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=255 time=2.9 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=255 time=0.5 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=255 time=4.6 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=255 time=11.6 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=255 time=0.5 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=255 time=11.6 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=255 time=4.6 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=255 time=2.9 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=255 time=181302.8 ms

Stuff from /var/log/messages
Dec 17 20:31:24 pc pcmcia: Starting PCMCIA services:
Dec 17 20:31:24 pc pcmcia:  modules
Dec 17 20:31:24 pc kernel: Linux PCMCIA Card Services 3.0.14
Dec 17 20:31:24 pc kernel:   kernel build: 2.2.13 #3 Sun Oct 31 23:18:16 EST 199
9
Dec 17 20:31:24 pc kernel:   options:  [pci] [cardbus] [apm]
Dec 17 20:31:24 pc kernel: Intel PCIC probe:
Dec 17 20:31:24 pc kernel:   TI 1250A PCI-to-CardBus at bus 0 slot 2, mem 0x2030
1000, 2 sockets
Dec 17 20:31:24 pc kernel:     host opts [0]: [ring] [pwr save] [isa irq] [no pc
i irq] [lat 168/176] [bus 1/3]
Dec 17 20:31:24 pc kernel:     host opts [1]: [ring] [pwr save] [isa irq] [no pc
i irq] [lat 168/176] [bus 4/6]
Dec 17 20:31:24 pc kernel:     ISA irqs (scanned) = 3,4,7,9,10 status change on 
irq 10
Dec 17 20:31:25 pc pcmcia:  cardmgr.
Dec 17 20:31:25 pc cardmgr[352]: starting, version is 3.0.14
Dec 17 20:31:25 pc cardmgr[352]: watching 2 sockets
Dec 17 20:31:25 pc kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x15e8-0x1
5ef
Dec 17 20:31:25 pc kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22
f 0x388-0x38f 0x4d0-0x4d7
Dec 17 20:31:25 pc cardmgr[352]: could not adjust resource: IO ports 0x1000-0x17
ff: Device or resource busy
Dec 17 20:31:25 pc cardmgr[352]: could not adjust resource: IO ports 0x100-0x7ff
: Device or resource busy
Dec 17 20:31:25 pc cardmgr[352]: could not adjust resource: memory 0xa0000000-0x
a0ffffff: Device or resource busy
Dec 17 20:31:25 pc cardmgr[352]: could not adjust resource: memory 0xd0000-0xdff
ff: Device or resource busy
Dec 17 20:31:25 pc rc: Starting pcmcia succeeded
Dec 17 20:32:11 pc cardmgr[352]: initializing socket 1
Dec 17 20:32:11 pc cardmgr[352]: socket 1: IBM 10/100 EtherJet CardBus Adapter w
ith 56K Modem
Dec 17 20:32:11 pc cardmgr[352]: executing: 'insmod /lib/modules/2.2.13/pcmcia/c
b_enabler.o'
Dec 17 20:32:11 pc cardmgr[352]: executing: 'insmod /lib/modules/2.2.13/pcmcia/t
ulip_cb.o debug=255'
Dec 17 20:32:11 pc cardmgr[352]: executing: 'insmod /lib/modules/2.2.13/pcmcia/serial_cb.o'
Dec 17 20:32:11 pc kernel: cs: cb_config(bus 4): vendor 0x115d, device 0x0003
Dec 17 20:32:11 pc kernel:   fn 0 bar 2: mem 0x60017000-0x600177ff
Dec 17 20:32:11 pc kernel:   fn 0 bar 3: mem 0x60016000-0x600167ff
Dec 17 20:32:11 pc kernel:   fn 1 bar 1: io 0x1080-0x1087
Dec 17 20:32:11 pc kernel:   fn 1 bar 2: mem 0x60015000-0x600157ff
Dec 17 20:32:11 pc kernel:   fn 1 bar 3: mem 0x60014000-0x600147ff
Dec 17 20:32:11 pc kernel:   fn 0 bar 1: io 0x1000-0x107f
Dec 17 20:32:11 pc kernel:   fn 0 rom: mem 0x60010000-0x60013fff
Dec 17 20:32:11 pc kernel:   fn 1 rom: mem 0x6000c000-0x6000ffff
Dec 17 20:32:11 pc kernel: tulip_attach(bus 4, function 0)
Dec 17 20:32:11 pc kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (mo
dified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Dec 17 20:32:11 pc kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mo
de) rev 3 at 0x1000, 00:04:AC:64:7E:65, IRQ 9.
Dec 17 20:32:11 pc kernel: eth0:  MII transceiver #0 config 3100 status 7809 adv
ertising 01e1.
Dec 17 20:32:11 pc kernel: XIRCOM init
Dec 17 20:32:11 pc kernel: serial_attach(bus 4, fn 1)
Dec 17 20:32:11 pc kernel: tty02 at 0x1080 (irq = 9) is a 16550A
Dec 17 20:32:11 pc kernel: eth0: The transmitter stopped.  CSR5 is 60678006, CSR
6 320c2002, new CSR6 b2020000.
Dec 17 20:32:11 pc kernel: eth0: The transmitter stopped.  CSR5 is 60678106, CSR
6 320c2002, new CSR6 b2020000.
Dec 17 20:32:11 pc last message repeated 4 times
Dec 17 20:32:11 pc cardmgr[352]: executing: './serial start ttyS2'
Dec 17 20:32:16 pc kernel: eth0: 21143 negotiation status 000000c2, 10baseT.
Dec 17 20:33:16 pc kernel: eth0: 21143 negotiation status 000000c2, 10baseT. 
Dec 17 20:34:16 pc kernel: eth0: 21143 negotiation status 000000c2, 10baseT. 
Dec 17 20:36:16 pc last message repeated 2 times
Dec 17 20:38:16 pc last message repeated 2 times
Dec 17 20:40:16 pc last message repeated 2 times
Dec 17 20:42:16 pc last message repeated 2 times
Dec 17 20:44:16 pc last message repeated 2 times
Dec 17 20:45:00 pc kernel: eth0: The transmitter stopped.  CSR5 is 60698186, CSR
6 320c6002, new CSR6 b2024000.
Dec 17 20:45:08 pc cardmgr[352]: executing: './network check eth0'
Dec 17 20:45:08 pc cardmgr[352]: executing: './serial check ttyS2'
Dec 17 20:45:09 pc cardmgr[352]: shutting down socket 1
Dec 17 20:45:09 pc cardmgr[352]: executing: './network stop eth0'
Dec 17 20:45:09 pc cardmgr[352]: executing: './serial stop ttyS2'
Dec 17 20:45:09 pc kernel: tulip_detach(eth0)
Dec 17 20:45:09 pc kernel: tty02 unloaded
Dec 17 20:45:09 pc cardmgr[352]: executing: 'rmmod tulip_cb'
Dec 17 20:45:09 pc cardmgr[352]: executing: 'rmmod serial_cb'
Dec 17 20:45:09 pc cardmgr[352]: executing: 'rmmod cb_enabler'
Dec 17 20:45:13 pc cardmgr[352]: exiting
Dec 17 20:45:15 pc kernel: unloading PCMCIA Card Services
Dec 17 20:45:31 pc kernel: Linux PCMCIA Card Services 3.0.14
Dec 17 20:45:31 pc kernel:   kernel build: 2.2.13 #3 Sun Oct 31 23:18:16 EST 199
9
Dec 17 20:45:31 pc kernel:   options:  [pci] [cardbus] [apm]
Dec 17 20:45:31 pc kernel: Intel PCIC probe:
Dec 17 20:45:31 pc kernel:   TI 1250A PCI-to-CardBus at bus 0 slot 2, mem 0x2030
1000, 2 sockets
Dec 17 20:45:31 pc kernel:     host opts [0]: [ring] [pwr save] [isa irq] [no pc
i irq] [lat 168/176] [bus 1/3]
Dec 17 20:45:31 pc kernel:     host opts [1]: [ring] [pwr save] [isa irq] [no pc
i irq] [lat 168/176] [bus 4/6]
Dec 17 20:45:31 pc kernel:     ISA irqs (scanned) = 3,4,7,9,10 status change on 
irq 10
Dec 17 20:45:31 pc cardmgr[1015]: starting, version is 3.0.14
Dec 17 20:45:31 pc cardmgr[1015]: watching 2 sockets
Dec 17 20:45:31 pc kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x15e8-0x1
5ef
Dec 17 20:45:31 pc kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x388-0x38f 0x4d0-0x4d7
Dec 17 20:45:31 pc cardmgr[1015]: could not adjust resource: IO ports 0x1000-0x1
7ff: Device or resource busy
Dec 17 20:45:31 pc cardmgr[1015]: could not adjust resource: IO ports 0x100-0x7f
f: Device or resource busy
Dec 17 20:45:31 pc cardmgr[1015]: could not adjust resource: memory 0xa0000000-0
xa0ffffff: Device or resource busy
Dec 17 20:45:31 pc cardmgr[1015]: could not adjust resource: memory 0xd0000-0xdf
fff: Device or resource busy
Dec 17 20:45:31 pc cardmgr[1015]: initializing socket 1
Dec 17 20:45:31 pc cardmgr[1015]: socket 1: IBM 10/100 EtherJet CardBus Adapter 
with 56K Modem
Dec 17 20:45:31 pc cardmgr[1015]: executing: 'insmod /lib/modules/2.2.13/pcmcia/
cb_enabler.o'
Dec 17 20:45:31 pc cardmgr[1015]: executing: 'insmod /lib/modules/2.2.13/pcmcia/
tulip_cb.o debug=255'
Dec 17 20:45:32 pc kernel: cs: cb_config(bus 4): vendor 0x115d, device 0x0003
Dec 17 20:45:32 pc kernel:   fn 0 bar 2: mem 0x60017000-0x600177ff
Dec 17 20:45:32 pc kernel:   fn 0 bar 3: mem 0x60016000-0x600167ff
Dec 17 20:45:32 pc kernel:   fn 1 bar 1: io 0x1080-0x1087
Dec 17 20:45:32 pc kernel:   fn 1 bar 2: mem 0x60015000-0x600157ff
Dec 17 20:45:32 pc kernel:   fn 1 bar 3: mem 0x60014000-0x600147ff
Dec 17 20:45:32 pc kernel:   fn 0 bar 1: io 0x1000-0x107f
Dec 17 20:45:32 pc kernel:   fn 0 rom: mem 0x60010000-0x60013fff
Dec 17 20:45:32 pc kernel:   fn 1 rom: mem 0x6000c000-0x6000ffff
Dec 17 20:45:32 pc kernel: tulip_attach(bus 4, function 0)
Dec 17 20:45:32 pc kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (mo
dified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Dec 17 20:45:32 pc kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mo
de) rev 3 at 0x1000, 00:04:AC:64:7E:65, IRQ 9.
Dec 17 20:45:32 pc kernel: eth0:  MII transceiver #0 config 3100 status 7809 adv
ertising 01e1.
Dec 17 20:45:32 pc kernel: XIRCOM init
Dec 17 20:45:32 pc cardmgr[1015]: executing: './network start eth0'
Dec 17 20:45:32 pc kernel: eth0: The transmitter stopped.  CSR5 is 60678006, CSR
6 320c2002, new CSR6 b2020000.
Dec 17 20:45:32 pc kernel: eth0: The transmitter stopped.  CSR5 is 60678106, CSR
6 320c2002, new CSR6 b2020000.
Dec 17 20:45:32 pc last message repeated 4 times
Dec 17 20:45:37 pc kernel: eth0: 21143 negotiation status 000000c2, 10baseT.
Dec 17 20:46:37 pc kernel: eth0: 21143 negotiation status 000000c2, 10baseT.
Dec 17 20:48:37 pc last message repeated 2 times
Dec 17 20:50:37 pc last message repeated 2 times
Dec 17 20:52:37 pc last message repeated 2 times
Dec 17 20:54:37 pc last message repeated 2 times

Question Experiences with the CEM56-100MD card?

Date: 1999, Nov 04
From: Jason Arnold jarnold

Hey all,

Running both Slackware and RedHat w/3.0.14 on a Micron TransPort NX which uses an O2Micro Cardbus PC Card controller.

I'm thinking about buying the Xircom CEM56-100MD card. Any experiences (good or bad) before I plunk down the $200+ on this card?

I read the Supported Cards list and it lists "CEM56", but no further specifics. As their are multiple Xircom cards with model numbers which start with CEM56, I want to be sure that this one is inclusive in that list.

Thanks in advance for the thoughts/opinions.

Regards,

Jason

Ok Untitled

Re: Question Experiences with the CEM56-100MD card? (Jason Arnold)
Date: 1999, Dec 17
From: David Levin atlas

The CEM56 model covers all adapters that support 10/100 Ethernet and 56K modem. The specific model you mentioned is covered.

Be aware that the CEM5610 is a different model adapter that only supports 10mb ethernet.

Xircom Unix Support David Levin

Question Problems with Kernel 2.2.13 and pcmcia 3.1.3

Date: 1999, Nov 04
From: Stefan Kapfhammer StefanKapfhammer

Whilst Kernel 2.2.10 and pcmcia 3.1.3 worked fine, I upgraded to Kernel 2.2.13 (still recompiled pcmcia 3.1.3 after upgrade) and now it says I have the serial at ttyS1 instead of ttyS0 as it was before.

On ttyS1 I get an I/O Error when trying to access the port and ttyS0 is not available for modem.

I have a Toshiba Tecra 8000 with a RBEM56-100BTX, in the Tosh-BIOS I set the PCMCIA to Cardbus 16-Bit so the 3.1.3 sees a ToPIC95B Chipset instead of the troublemaking ToPIC97 (that worked already until the Kernel-upgrade.

The new Kernel has the serial and shared serial compiled in.

What did I wrong?

Question Problems with Kernel 2.2.12/RH 6.1/Xircom RBEM56G

Re: Question Problems with Kernel 2.2.13 and pcmcia 3.1.3 (Stefan Kapfhammer)
Date: 1999, Nov 06
From: Rick Knight rknight

I have a similar problem with my Xircom RBEM56G-100 on RedHat 6.1 with kernel 2.2.12 and a Dell Latitude CPt400G. Card Services start ok and the network half ot the card is fine. The modem side is assigned to tty00 according to dmesg. When I look at the system log it shows the card started on ttyS0 at irq3. These settings should work but when I try to access the modem I get a modem busy message. I've looked for some sort of lock but can't find one. This same hardware worked very well with RedHat 5.2/Kernel 2.2.7/pcmcia-cs-3.0.14. Have I missed something in the configuration?

Thanks, Rick Knight (rknight@jps.net)

Sad Problems with Kernel 2.2.13/RH 6.1/Xircom RBEM56G also

Re: Question Problems with Kernel 2.2.12/RH 6.1/Xircom RBEM56G (Rick Knight)
Date: 1999, Nov 08
From: Ron Golan rgolan

I had the same problem with my DEC HiNote VP765 and Xircom RBEM56G. I was using Red Hat 6.1 and kernel 2.2.13 and pcmcia 3.1.1. The network side of the card worked fine but trying to use minicom to even get an OK from the modem was impossible. Minicom claimed the modem on online even after a forced hang up.

I'm suspecting something in the 6.1 release is the problem because I'm using the same kernel now with Red Hat 6.0 and it works fine. I also tried an external modem on the rear serial port and it showed the same behavior. So I guess it can't be blamed on the pcmcia stuff.

Ok Modems and ttyS*

Re: Sad Problems with Kernel 2.2.13/RH 6.1/Xircom RBEM56G also (Ron Golan)
Date: 1999, Nov 08
From: Philippe Henry henry

I use SuSE 6.2 kernel 2.2.10. I have the same problem, and the results are good or bad, depending on the setup of a parameter called char-major-4 and char-major-5 in the files /etc/conf.modules. If these parameters are set to "serial" modem is detected on port /dev/ttyS0 and it works fine. If these parameters are set to "off" modem is detected on port /dev/ttyS2 but it doesn' t work at all. These results are the same with pcmcia-cs-3.1.0 and 3.1.1. With kernel 2.2.13 the results are always bad.

Ok Irq init and ttyS* ports at boot time.

Re: Question Problems with Kernel 2.2.13 and pcmcia 3.1.3 (Stefan Kapfhammer)
Date: 1999, Nov 10
From: Philippe Henry henry

I read something about this on the old forums at Stanford for debian users. For SuSE 6.2 the command to type is "chmod a-x /sbin/setserial" which avoid automatic setting of irq at boot time for ttyS* ports. With this command the xircom pcmcia modem is on ttyS2 port and works fine. I still don't know if I can access my DOS COM1 and COM2 ports...

Question CEM-28 combo card stopped working....

Date: 1999, Nov 04
From: bboett

Hello,

suddenly last wek my xircom combo card stopped working, after some manipulations of my system (among others the latest update to the latest debian potato...) the next reboot resulted in the loss of the ethernet ability of my laptop...

I tryed to recompile the pcmcia package, i installed the package 3.1.3, recompiled the kernel, tryed with the kernel 2.2.9 and 2.2.12, ntohing helps...

the exerpt of the /var/log/messages:
Nov  4 01:07:53 localhost kernel: Linux PCMCIA Card Services 3.1.3
Nov  4 01:07:53 localhost kernel:   kernel build: 2.2.12 #1 Fri Sep 3 07:39:42 C
EST 1999
Nov  4 01:07:53 localhost kernel:   options:  [pci] [cardbus] [apm] [pnp]
Nov  4 01:07:53 localhost kernel: PnP: PNP BIOS installation structure at 0xc00f
66d0
Nov  4 01:07:53 localhost kernel: PnP: PNP BIOS version 1.0, entry at f0000:a62f
, dseg at 400
Nov  4 01:07:53 localhost kernel: PCI routing table version 1.0 at 0xfdf90
Nov  4 01:07:53 localhost kernel: Intel PCIC probe: 
Nov  4 01:07:53 localhost kernel:   TI 1131 PCI-to-CardBus at bus 0 slot 10, mem
 0x68000000, 2 sockets
Nov  4 01:07:53 localhost kernel:     host opts [0]: [ring] [clkrun irq 12] [pci
 + serial irq] [no pci irq] [lat 168/176] [bus 32/34]
Nov  4 01:07:53 localhost kernel:     host opts [1]: [ring] [clkrun irq 12] [pci
 + serial irq] [no pci irq] [lat 168/176] [bus 35/37]
Nov  4 01:07:53 localhost kernel:     ISA irqs (scanned) = 3,4,7,10,11,15 status
 change on irq 15
Nov  4 01:07:54 localhost kernel: cs: IO port probe 0x1000-0x17ff: clean.
Nov  4 01:07:54 localhost kernel: cs: IO port probe 0x0100-0x04ff: clean.
Nov  4 01:07:54 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Nov  4 01:07:54 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Nov  4 01:07:54 localhost kernel: xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+k
vh)
Nov  4 01:07:54 localhost kernel: xirc2ps_cs: no ports available
Nov  4 01:09:55 localhost kernel: xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+k
vh)
Nov  4 01:09:55 localhost kernel: xirc2ps_cs: no ports available

while the daemon.log reports:

Nov  4 01:09:55 localhost cardmgr[389]: initializing socket 0
Nov  4 01:09:55 localhost cardmgr[389]: socket 0: Xircom CEM28 Ethernet/Modem
Nov  4 01:09:55 localhost cardmgr[389]: executing: 'insmod /lib/modules/2.2.12/p
cmcia/xirc2ps_cs.o'
Nov  4 01:09:55 localhost cardmgr[389]: module /lib/modules/2.2.12/pcmcia/p<80>^
N@p<80>^N@x.o not available
Nov  4 01:09:55 localhost cardmgr[389]: get dev info on socket 0 failed: No such
 device

especially the line Nov 4 01:09:55 localhost cardmgr[389]: module /lib/modules/2.2.12/pcmcia/p<80>^ N@p<80>^N@x.o not available seems really strange....

BTW, here'S the shortened output of lsmod and 2x carctl:

Module Size Used by xirc2ps_cs 13564 0 (unused) ds 6408 4 [xirc2ps_cs] i82365 28440 2 pcmcia_core 50944 0 [xirc2ps_cs ds i82365]

erm7:/etc/pcmcia# cardctl status
Socket 0:
  5V 16-bit PC Card
  function 0: [ready]
Socket 1:
  no card
erm7:/etc/pcmcia# cardctl ident 
Socket 0:
  product info: "Xircom", "CreditCard Ethernet+Modem 28.8", "CEM28", "2.00"
  manfid: 0x0105, 0x110b
  function: 2 (serial)
Socket 1:
  no product info available

I find it strange that cardctl ident recognizes the card, but that cardctl status shows off nothing...

so what's going wrong? Do i have to assume that my card is fryed? But in that case i wonder why the system is able to recognize it correctly as a xircom card...

So i suppose there is something else....

Sad also get "no port available" msg for REM56

Re: Question CEM-28 combo card stopped working....
Date: 1999, Nov 10
From: Adam Di Carlo aph

I also rather suddenly get the exact same "no ports available" message. I have checked the available IO addresses between the time it was working and the time it stopped working -- no change.

This is very vexing!

Ok RETRACTION -- pcmcia not to blame for "no port available"

Re: Sad also get "no port available" msg for REM56 (Adam Di Carlo)
Date: 1999, Nov 10
From: Adam Di Carlo aph

I was suffering from "xirc2ps_cs: no ports available" but it turns out it was setserial's fault, not PCMCIA. You can disable setserial (chmod a-x /etc/init.d/setserial) to fix the problem, at least on a Debian system. See Bug#39635, at http://www.chiark.greenend.org.uk/debian/Bugs/db/39/39635.html

None Re: Ok: RETRACTION -- pcmcia not to blame for "no port available"

Re: Ok RETRACTION -- pcmcia not to blame for "no port available" (Adam Di Carlo)
Date: 1999, Nov 10
From: Bruno Boettcher bboett

On Tue, Nov 09, 1999 at 08:25:00PM -0800, Adam Di Carlo wrote:
> I was suffering from "xirc2ps_cs: no ports available" but it turns out
> it was setserial's fault, not PCMCIA. You can disable setserial (chmod
> a-x /etc/init.d/setserial) to fix the problem, at least on a Debian
> system. See Bug#39635, at
> http://www.chiark.greenend.org.uk/debian/Bugs/db/39/39635.html
THANKS a lot, this did it for me too!
aaaaaaaahhhhhh ethernets back! i may work again! ;)


-- 
ciao bboett
==============================================================
bboett@earthling.net
http://inforezo.u-strasbg.fr/~bboett http://erm1.u-strasbg.fr/~bboett
===============================================================
the total amount of intelligence on earth is constant.
human population is growing....

Feedback Re: Ok: RETRACTION -- pcmcia not to blame for "no port available"

Re: None Re: Ok: RETRACTION -- pcmcia not to blame for "no port available" (Bruno Boettcher)
Date: 1999, Nov 13
From: Adam Di Carlo aph

If you are having errors in PCMCIA with setserial and you are running Debian, could you please try updating to the newest setserial in potato (if you're running potato) and work with the Debian setserial maintainer to fix this? I.e., file a bug....

Thanks -- that will ensure that when potato releases, we will have a nice system for laptop users without fuss or muss.

Question How to turn off PM of PCMCIA?

Date: 1999, Nov 04
From: Balu Nadiga balu

I use Xircom REM56 with IBM Thinkpad 570. I run RH6.0 kernel 2.2.12. Suspend-resume leaves PCMCIA card unusable. Have to reboot!

So, is there a way to turn off power management of the PCMCIA card alone?

Thanks, Balu

None Re: Question: How to turn off PM of PCMCIA?

Re: Question How to turn off PM of PCMCIA? (Balu Nadiga)
Date: 1999, Nov 04
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Can you turn off power management of just the PCMCIA card?  No.  That
is a function of your laptop BIOS, and there is nothing Linux can do
about it.

Do you have to reboot to deal with this?  No.  Obvious workarounds
include... ejecting the card before you suspend, or doing a "cardctl
eject", then inserting or doing "cardctl insert" after you resume.
It is also possible to tell apmd to handle the eject and insert
commands.

Ideally, this driver would be fixed so that it could recover from a
suspend/resume cycle.  But it is not the best written driver.

-- Dave

Warning Machine freezes for 2-3 seconds on insertion of Xircom REM56G-100BTX

Date: 1999, Nov 05
From: Bryce Nesbitt brycen

The card works fine, but each time the REM56G-100BTX Ethernet/Modem card is inserted, the entire machine freezes totally -- no mouse, no graphic updates, no process, nothing -- for 2-3 seconds. Normal? Bug?

NEC Versa 6200MX, TI PCI1130 controller http://sunflower.singnet.com.sg/~anupmc/Linux_on_6200MMX.html

More More info on freeze

Re: Warning Machine freezes for 2-3 seconds on insertion of Xircom REM56G-100BTX (Bryce Nesbitt)
Date: 1999, Nov 05
From: Bryce Nesbitt brycen

stetson:/etc/X11> uname -rv
2.0.36 #1 Tue Oct 13 22:17:11 EDT 1998
stetson:/etc/X11> cardctl -V
cardctl version 3.0.14



Nov  4 19:41:46 stetson cardmgr[337]: initializing socket 0
Nov  4 19:41:46 stetson cardmgr[337]: unsupported card in socket 0
Nov  4 19:41:46 stetson cardmgr[337]:   no product info available
Nov  4 19:41:46 stetson cardmgr[337]: initializing socket 0
Nov  4 19:41:46 stetson cardmgr[337]: socket 0: Xircom CEM56 Ethernet/Modem
Nov  4 19:41:47 stetson cardmgr[337]: executing: '/sbin/insmod /lib/modules/preferred/pcmcia/xirc2ps_cs.o'
Nov  4 19:41:47 stetson cardmgr[337]: + /lib/modules/preferred/pcmcia/xirc2ps_cs.o: a module named xirc2ps_cs already exists
Nov  4 19:41:47 stetson cardmgr[337]: /sbin/insmod exited with status 1
Nov  4 19:41:47 stetson cardmgr[337]: executing: '/sbin/modprobe xirc2ps_cs'
Nov  4 19:41:47 stetson cardmgr[337]: + can't locate module xirc2ps_cs
Nov  4 19:41:47 stetson cardmgr[337]: /sbin/modprobe exited with status 1


Then it all works.

Nov  4 19:41:47 stetson cardmgr[337]: executing: '/sbin/insmod /lib/modules/preferred/pcmcia/serial_cs.o'
Nov  4 19:41:47 stetson cardmgr[337]: + /lib/modules/preferred/pcmcia/serial_cs.o: a module named serial_cs already exists
Nov  4 19:41:47 stetson cardmgr[337]: /sbin/insmod exited with status 1
Nov  4 19:41:47 stetson cardmgr[337]: executing: '/sbin/modprobe serial_cs'
Nov  4 19:41:47 stetson cardmgr[337]: + can't locate module serial_cs
Nov  4 19:41:52 stetson kernel: eth0: auto negotation failed; using 10mbs
Nov  4 19:41:52 stetson kernel: eth0: media 10BaseT, silicon revision 5
Nov  4 19:41:52 stetson kernel: eth0: Xircom: port 0x300, irq 3, hwaddr 00:10:A4:E2:60:3C
Nov  4 19:41:47 stetson cardmgr[337]: /sbin/modprobe exited with status 1
Nov  4 19:41:52 stetson cardmgr[337]: executing: './network start eth0'
Nov  4 19:41:52 stetson kernel: tty03 at 0x02e8 (irq = 3) is a 16550A
Nov  4 19:41:53 stetson cardmgr[337]: executing: './serial start ttyS3'

None Not connected

Re: More More info on freeze (Bryce Nesbitt)
Date: 1999, Nov 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'm not sure what's going on here.  It looks like the xirc2ps_cs and
serial_cs modules somehow got loaded before cardmgr identified the
card.  Maybe you've got something bogus in /etc/modules.conf or in
your init scripts that is trying to help out by loading these modules.
It isn't related to the freezes.

-- Dave

None Alas, it is normal

Re: Warning Machine freezes for 2-3 seconds on insertion of Xircom REM56G-100BTX (Bryce Nesbitt)
Date: 1999, Nov 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Sadly, this is normal for this lame driver.  It does a busy loop
waiting for the transceiver to autonegotiate the connection speed.

The driver should really be fixed to do this in the background, but
I'm not going to be the one to do it.

-- Dave

Question ISDN Xircom 10/100 mb ?

Date: 1999, Nov 05
From: J.P jeepee

Are there any people out there that already tried something with the ISDN option of the Xircom card. It runs oke under Win98/NT but I rather have it running under Linux. I an running a Versa LX laptop with Win98 / NT / Linux (which is slackware 4.0 with 2.2.13 and pcmcia 3.1.3)

If someone has a good result please email me on jeepee@gids.nl

Ciao...

Ok ISDN works but...

Re: Question ISDN Xircom 10/100 mb ? (J.P)
Date: 1999, Nov 05
From: Philippe Henry henry

You can use ISDN speed but not all ISDN features. See messages n° 215 on the old forums at Stanford. As modem emulation you have a 64K speed, but no possibility for channel bundling... We are all waiting for the drivers to use isdn4linux packages. I use SuSE 6.2, kernel-2.2.10 and pcmcia-cs-3.1.0, and it works fine. Just remember to setup the correct parameters as said in message n° 215. "Bonne chance".

More Sorry wrong answer to question

Re: Ok ISDN works but... (Philippe Henry)
Date: 1999, Nov 15
From: Stefan Kapfhammer StefanKapfhammer

See subject

Question Xircom and ISDN

Re: Ok ISDN works but... (Philippe Henry)
Date: 2000, Mar 20
From: Pascal CHambre pchambre

The message 215 from old Stanford forums is no more available.

I can't install ISDN features on my laptop(DELL INSPIRON 7500) with the Xircom RealPort ISDN Connection Kit

I'm running Redhat 6.1

My Xircom RealPort works fine with ethernet and standard modem.

Please help.

Thanks

Idea Kernel 2.2.10 (orig) and cs-3.1.4 works with ISDN

Re: Question ISDN Xircom 10/100 mb ? (J.P)
Date: 1999, Nov 15
From: Stefan Kapfhammer StefanKapfhammer

ISDN works, just send only ATZ (I use wvdial). It does not respond to a AT&F

Question RBEM56G asymmetrical transfer speeds

Date: 1999, Nov 08
From: Ron Golan rgolan

In doing some testing I found that the Xircom RBEM56G is much slower in receiving than in sending.

RX (ftp get) 3610159 bytes received in 13.8 secs (2.6e+02 Kbytes/sec)

TX (ftp put) 3610159 bytes received in 0.57 secs (6.2e+03 Kbytes/sec)

The test is done with command line ftp between a DEC HiNote VP765 and a fast desktop machine connected by a 10/100 switch. The connections are 100baseTX and full duplex. I'm using Red Hat 6.0 with 2.2.13 kernels at both ends. The difference in speed is about 24 times! I am going to repeat the test with a cross-over cable to eliminate problems with the switch.

Is anyone else with this Xircom card getting good receive performance?

More Further testing on RBEM56G

Re: Question RBEM56G asymmetrical transfer speeds (Ron Golan)
Date: 1999, Nov 15
From: Ron Golan rgolan

I just updated to pcmcia-cs-3.1.14 and this is what I found.

The tulip_cb driver is still broken. Can't ping anything. I copied in the one from 3.1.11 which is the last one that worked for me.

The transfer speeds are still asymmetrical. TX is much faster than RX. TX is about 30 times faster if my crude testing methods can be trusted. Below is some ifconfig output:

eth0      Link encap:Ethernet  HWaddr 00:10:A4:F3:64:17  
          inet addr:192.168.10.8  Bcast:192.168.10.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20730 errors:5 dropped:0 overruns:0 frame:0
          TX packets:7937 errors:17801 dropped:0 overruns:0 carrier:17801
          collisions:0 txqueuelen:100 
          Interrupt:3 Base address:0x1000 

There seem to be a lot of carrier errors. I am using the Xircom RBEM56G at 100baseT and full duplex. It doesn't seem to make any difference if I use a switch or a cross-over cable.

Note Sorry, that was 3.1.4, not 3.1.14

Re: More Further testing on RBEM56G (Ron Golan)
Date: 1999, Nov 15
From: Ron Golan rgolan

In the above message I was using 3.1.4, not 3.1.14.

Ok Tosh Tecra 8000 with RBEM56-10/100BTX works with ToPIC97 at 32-Bit

Date: 1999, Nov 15
From: Stefan Kapfhammer StefanKapfhammer

Hello everyone,

after hours and hours of nightly work I got it run!

My Toshiba Tecra 8000 with ToPIC97 and a RBEM56-10/100BTX Card. Currently with Kernel 2.2.10 (Original, not SuSE-modified) Analog, ISDN and Networking at 100MBit/s works fine.

Will try with 2.2.13 when again downloaded (I had a hard-crash, uuups ;-( )

Note T8K BIOS GOTCHA

Re: Ok Tosh Tecra 8000 with RBEM56-10/100BTX works with ToPIC97 at 32-Bit (Stefan Kapfhammer)
Date: 1999, Nov 23
From: Zaphod Beeblebrox Zaph0d

Remember also for Tecra 8k's to chance the PCMCIA mode to
CardBus/16 rather than auto.  Mine did not work properly
until I forced it into cardbus mode with tsetup.exe

Question Problems with cs-3.1.4 and Kernel 2.2.13

Date: 1999, Nov 17
From: Stefan Kapfhammer StefanKapfhammer

Hardware: Toshiba TECRA 8000 with RBEM56-10/100BTX

After a successful run with Kernel 2.2.10 and cs-3.1.4, I upgraded to Kernel-release 2.2.13.

Have error-msg with dmesg:

cs: socket 0 timed out during reset

This happens with BIOS-Setting ToPIC95B and ToPIC97. I used irq_list=10 in /sbin/init.d/pcmcia under PCIC_OPTS. That has worked fine in 2.2.10 Kernel.

After suspending and resuming socket 0 the cs recognised the right card, but cannot access the ttyS* with wvdial nor minicom.

Are there any workarounds available or a specific Kernel parameters to set (build-in/modules)

Regards,

Stefan

Ok ttys* init

Re: Question Problems with cs-3.1.4 and Kernel 2.2.13 (Stefan Kapfhammer)
Date: 1999, Nov 18
From: Philippe Henry henry

I use SuSE 6.2 with kernel-2.2.13 and pcmcia-3.1.4. I had to disable automatic setting of irq at boot time for ttyS* ports, typing the command "chmod a-x /sbin/setserial", then reboot.

Question RBEM56G eth0 timed out when used with ISDN modem (ipmasq)

Re: Ok ttys* init (Philippe Henry)
Date: 1999, Nov 18
From: Jean-Pierre Hermand jph

Tecra8000/kernel 2.2.13/pcmcia 3.1.2

Any idea why eth0 timed out (TX hung) when using SIMULTANEOUSLY 10 Mbit ethernet and modem-emulated ISDN with a ipmasq (ipchains) setup?

Problems also occur with extensive pinging home lan meanwhile connected to ISP via PPP.

the Xircom RBEM56G is assigned irq 10.

I saw a few messages in the old forums about eth0 timed out but nobody ever replied to these messages.

None The card is dropping interrupts

Re: Question RBEM56G eth0 timed out when used with ISDN modem (ipmasq) (Jean-Pierre Hermand)
Date: 1999, Nov 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It sounds like an interrupt sharing problem; ensuring that interrupts
are not lost when both card functions are in simultaneous use can be
tricky.  This driver doesn't do anything special in this situation.
I'm not sure if/when it can be fixed.

-- Dave

Question Checking dropped interrupts

Re: None The card is dropping interrupts (David Hinds)
Date: 1999, Nov 20
From: Stefan Kapfhammer StefanKapfhammer

Hi Dave,

I can work with ISDN and Networking at 100-MBit/s simultanous. Are there any tools under Linux where I can check interrupt-problems in realtime while doing both ISDN and Networking? I am not familiar in the C programming language, so I cannot help developing but I can help in testing new releases of pcmcia-cs and kernels in cooperation with the RBEM56-10/100BTX card.

B.T.W. Have you descriptions for the AT command-set with the RICK ISDN Kit, I could not find them in the bypacked book or do you know where to get them?

Thanks in advance

Regards,

Stefan

Feedback Partial success

Re: Ok ttys* init (Philippe Henry)
Date: 1999, Nov 19
From: Stefan Kapfhammer StefanKapfhammer

I executed the command as of Message 12/1 and had a partial success. While the card is inserted during boot it is not properly set up. After a short removal and insertion of the card it works fine.

Question Problem getting 100BaseT FDX on a REM56G-100

Date: 1999, Nov 23
From: Zaphod Beeblebrox Zaph0d

I am having problems getting a Xircom REM56G-100 RealPort card going at full duplex, anyone else had this kind of preoblem ?? It only autonegotiates aat half duplex according to the lights on my switch.

Idea Possible solution

Re: Question Problem getting 100BaseT FDX on a REM56G-100 (Zaphod Beeblebrox)
Date: 1999, Dec 17
From: David Levin atlas

This may be part of a known issue with NWay. The auto detect feature tends to fail on some hubs and switches if Duplex (half/full) and speed (10/100) are both forced. One of the setting must be left to auto for the Nway negoiation to occur. If both are forced some devices just fall back to a default and you do not get the speed you wanted, or possible a failed network connection all together.

Sad Still Having Problems

Re: Idea Possible solution (David Levin)
Date: 1999, Dec 17
From: Zaphod Beeblebrox Zaph0d

I am not sure what NWay is...

I am not forcing any of the modes, It appears to get 100FDX when the interface comes up then somehow the link lights go down again and when they come back up it is only at HDX. I am wondering if it is something to do with pump or if it is the driver. I have however tried it without using pump and the noted the following, as soon as I plug in the RealPort card into the pcmcia socket I get all three lights on the switch (link,100,FDX). The first beep is heard and all seems ok, then all three lights go out and the second beep is heard.

Hope this helps, I am running STD RH6.2 I did try the latest pcmcia modules but it didn't make a difference.

Angry is that really possible?

Re: Question Problem getting 100BaseT FDX on a REM56G-100 (Zaphod Beeblebrox)
Date: 2000, Feb 08
From: Magnus Damm damm

according to the datasheet for the controller

http://www.xircom.com/sdk/x1601-3.zip

the controller does not support full duplex at 100Mbit
even if the PHY supports it.

full duplex is only available for 10Mbit.

you can find more information at 

http://www.xircom.com/cda/page/0,1298,1_20-475,00.html

Cheers /

Magnus

None I guess so...

Re: Angry is that really possible? (Magnus Damm)
Date: 2000, Feb 08
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Hmmm, well, the datasheet does not seem to be ambiguous.

I guess it is not a particularly unreasonable limitation.  As a 16 bit
card is already limited to a maximum throughput of maybe 1.5 MB/sec,
full duplex 100baseT is not going to give you any non-psychological
improvement over half duplex.

-- Dave Hinds

Question RealPort Ethernet 10/100 + Modem 56 REM 56G - 100

Re: Question Problem getting 100BaseT FDX on a REM56G-100 (Zaphod Beeblebrox)
Date: 2000, May 28
From: Paul A Norman Paulanor

Is this the right place to find any help information for using the RealPort Ethernet 10/100 + Modem 56 REM 56G - 100 under Linux Redhat 6.0/ Mandrake 6.0? (On a Toshiba Satellite 2520CDS )

It seems I have been having similar problems to this thread.

However I can not get the computer to recognise the Modem/Ethernet at all.

TIA

Paul

None Not a good combination

Re: Question RealPort Ethernet 10/100 + Modem 56 REM 56G - 100 (Paul A Norman)
Date: 2000, May 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Red Hat 6.0 is too old to expect this card to possibly work.

You should probably try a PCMCIA driver upgrade.  The odds are not in
your favor: this card is still "not recommended", and I also don't
recommend Toshiba laptops, because they are both so troublesome under
Linux.

-- Dave

Question eth0: RX drop,too much done

Date: 1999, Nov 25
From: Mark Harvey <mark.harvey@enstor.com.au>

I'm running Linux 2.2.13 kernel and pcmcia-cs-3.1.4 (04-Nov-99 This is to fix the 10/100 problem with Xircom).

<background information> I have just installed Legato client backup software on my laptop to do a network backup to the backup server. My co-worker was having all sorts of problems with his laptop (same configuration as mine but no backup running). ie very slow. </bacground information>

His log files were full of the following:

Nov 26 10:20:23 xsara kernel: xirc2ps_cs: eth0: RX drop, too much done
Nov 26 10:20:54 xsara last message repeated 2352 times
Nov 26 10:21:55 xsara last message repeated 4221 times
Nov 26 10:22:56 xsara last message repeated 3908 times
Nov 26 10:24:00 xsara last message repeated 2602 times
Nov 26 10:25:00 xsara last message repeated 1472 times
Nov 26 10:25:00 xsara CRON[1123]: (root) CMD (/sbin/rmmod -a)
Nov 26 10:25:00 xsara kernel: xirc2ps_cs: eth0: RX drop, too much done
etc....

All machines are connected to a 100Mbit hub.

Is this a fact of life where the amount of data on the 100BaseT is just too fast for the pcmcia interface or is it a problem in the xircom driver ?

Best regards Mark Harvey

None Unfortunately, that's probably just the way it is

Re: Question eth0: RX drop,too much done (Mark Harvey)
Date: 1999, Nov 29
From: David Hinds <dhinds@pcmcia.sourceforge.org>

A 16-bit PCMCIA card can only transfer about 2 MB/sec over the PCMCIA
bus.  So yes, it is a fact of life that you'll drop packets on a
100baseT (10 MB/sec) network connection.

We may want to make this problem silent, since there isn't anything to
be done about it, and generating thousands of kernel messages isn't
very productive.

-- Dave

More Same message, but with 10baseT ... also "auto negotiation failed"

Re: Question eth0: RX drop,too much done (Mark Harvey)
Date: 1999, Dec 07
From: Serge Winitzki winitzki

Hi,

I'm using Xircom creditcard ethernet 10/100 on a 10baseT network. It works fine except for two messages:

xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh)
eth0: Xircom: port 0x300, irq 3, hwaddr 00:80:C7:4B:4A:BF
eth0: auto negotation failed; using 10mbs
eth0: media 10BaseT, silicon revision 4
---

and

kernel: xirc2ps_cs: eth0: RX drop, too much done
last message repeated 75 times

---
I have put 'IF_PORT="10baseT"' into "/etc/pcmcia/network.opts" to help it recognize our 10mbs network but it doesn't seem to change anything.

Regards,
Serge

None Just look the other way

Re: More Same message, but with 10baseT ... also "auto negotiation failed" (Serge Winitzki)
Date: 1999, Dec 07
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If the card works fine except for the messages, try to just ignore
them.  The messages are harmless.

-- Dave

Ok PCMCIA Modems (Xircom) and RedHat Linux 6.1 -- fixed

Date: 1999, Nov 28
From: Atul Chitnis achitnis

Some (me included) will find that their PCMCIA modems mysteriously stop functioning under RHL 6.1, while the Ethernet part on the same card may work fine.

The problem is not with PCMCIA, but with the hardware detection utility (kudzu) that RHL 6.1 introduced.

The fix is simple - edit /etc/rc.d/init.d/kudzu and change

        /usr/sbin/kudzu -t 30
to
        /usr/sbin/kudzu -t 30 -s

This stops kudzu from initializing and "freezing" the serial port configs.

The same fix also takes care of some machines that keep\ finding/losing their serial port mouse (usually on /dev/ttyS1 - COM2 for DOSsies).

This information was found at the *old* PCMCIA forums, so I thought it may be useful to people who only come to the new forums here.

Atul

Note Thanks :-)

Re: Ok PCMCIA Modems (Xircom) and RedHat Linux 6.1 -- fixed (Atul Chitnis)
Date: 2000, Apr 22
From: Erik Schall ErikS

Ok, thanks a lot for the kudzu trick !

For info, i've been trying for a few minutes now a Xircom Realport Cardus RBEM56G-100BTX on my compaq 1598DT Armada with a stock Mandrake 7.02 (air), with default pcmcia package 3.1.9 and both function of the card seems to be working ok !

Writing this message on the net by modem while copying some stuff on the LAN :-))

Anyway, at the beginning, the ethernet part seemed OK, but the modem didn't ! I then remembered the kudzu trick which solved the problem and now everything works together.

Well, i will go through a bit more testing but up to now, i am happy. I don't know much by now about how the RBEM56-100 will act with suspend etc...

Thanks to everyone on this forum and specially to David for his fantastic work !

Erik.

None Machine Lockup with high network traffic

Date: 1999, Nov 29
From: Mark Harvey <mark.harvey@enstor.com.au>

I am having problems with my laptop locking up with very high network traffic.

The version of pcmcia drivers seems to make quite a difference to the timing of the problem.

ie: the latest (NEW) pcmcia 3.1.5 drivers lock the machine solid very quickly however 3.1.4 seems to hold out for about 10 minutes.

The laptop ONLY locks up when tring to run a vmware session and there is very high network traffic. Without vmware running the laptop is stable with only the syslog recording lots of dropped packets.

I feel it is a race condition within vmware/kernel/pcmcia however I get no oops, there is nothing in the log files, just a total lockup. - caps-lock doesn't work, can not ping the machine etc. The power button (the "Oh shit" button) is the only solution.

Any sugestions on how to track this one down ?

ps: I am now going to log this with vmware as a problem.

Best regards Mark Harvey

None More information would be helpful

Re: None Machine Lockup with high network traffic (Mark Harvey)
Date: 1999, Nov 29
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It might help to mention what kind of laptop this is, what kind of
network card you're using, exactly what messages you get in your
system log, etc.

-- Dave

Feedback Extra Information...

Re: None More information would be helpful (David Hinds)
Date: 1999, Nov 29
From: Mark Harvey <mark.harvey@enstor.com.au>

Hi David,

The both laptops in the office are Armada 1750's with the xircom 10/100 pcmcia drivers. The hardware is as identical as possible when purchased a couple of weeks apart.

They have 333MHz Mobile Pent II, 128M RAM and 6G HDD.

One of the laptops is running 2.2.13 and I'm running 2.2.14pre9. Both are on top of Opencaldera 2.3. PCMCIA I've tried is 3.1.4 & 3.1.5 (to get 10Mbit working on the xircom). Using 3.1.5 will cause the machine to lock up within 2 minutes. Using 3.1.4 will allow the machine hang around for up to an hour or so but will finally lock solid as well.

The network in the office is a 100Mbit hub with a Solaris server along with 3 NT boxes.

There is nothing in the logs around the time of the lockup (except the dropped packets I reported in an earler message)

To get the machine to lock up is a matter of generating lots of 100Mbit traffic (in our case using Legato backup software to backup a machine across the network). The laptop sitting idle (or busy) but not involved with the backup will just lock solid. vmware has to be running. The machine without vmware will function as normal.

Any other information can be produced upon request.

Best regards Mark Harvey

None VMware is going to make this very hard to debug

Re: Feedback Extra Information... (Mark Harvey)
Date: 1999, Nov 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The fact that the lockup only happens when running VMware troubles me,
and I'm somewhat afraid to even try to debug the problem if it only
happens in such a specific setup.  I don't know much about how VMware
works.  I don't see an obvious reason why 3.1.5 would be worse than
3.1.4; you could compare the startup messages from each, to see if
something is being configured differently.  You could also follow the
suggestions in the PCMCIA-HOWTO for debugging system lock-ups, though
I don't know if they'll be effective under VMware.

-- Dave

Sad Total lockup with xircom in promiscuous mode

Re: None Machine Lockup with high network traffic (Mark Harvey)
Date: 1999, Dec 08
From: Mark Harvey <mark.harvey@enstor.com.au>

The on-going saga... With the help of vmware I found they put the driver in promiscuous mode when vmware is configured as 'bridged' mode. As an experiment I did not run vmware and did run 'tcpdump -n -i eth0' instead. Result: Total lockup after 10 minutes...

ie can not ping, keyboard dead, only power button works.

A network backup started just after 20:30. This machine is NOT involved with the backup, it just happens to be connected to the same collision domain on the 100Mbit ethernet.

----- /var/log/messages -----

Dec  8 20:30:00 xsara CRON[1116]: (root) CMD (/sbin/rmmod -a)
Dec  8 20:34:00 xsara kernel: xirc2ps_cs: eth0: RX drop, too much done
Dec  8 20:34:30 xsara last message repeated 1098 times
Dec  8 20:35:00 xsara CRON[1130]: (root) CMD (/sbin/rmmod -a)
Dec  8 20:37:06 xsara kernel: xirc2ps_cs: eth0: RX drop, too much done
Dec  8 20:37:37 xsara last message repeated 2919 times
Dec  8 20:38:37 xsara last message repeated 4872 times
Dec  8 20:39:39 xsara last message repeated 7735 times                          Dec  8 20:40:00 xsara last message repeated 7318 times
Dec  8 20:40:00 xsara CRON[1133]: (root) CMD (/sbin/rmmod -a)
Dec  8 20:40:00 xsara kernel: xirc2ps_cs: eth0: RX drop, too much done
Dec  8 20:40:30 xsara last message repeated 12388 times                         Dec  8 20:40:58 xsara last message repeated 1201 times
Dec  8 20:42:00 xsara CRON[1146]: (root) CMD ([ -x /usr/sbin/cronloop ] && /usr/
sbin/cronloop Hourly)
Dec  8 20:42:08 xsara kernel: xirc2ps_cs: eth0: RX drop, too much done
Dec  8 20:42:44 xsara last message repeated 3089 times
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Dec 9 09:05:09 xsara syslogd 1.3-3: restart. Dec 9 09:05:11 xsara kernel: klogd 1.3-3, log source = /proc/kmsg started. Dec 9 09:05:11 xsara kernel: Inspecting /System.map D

----------- End of /var/log/message ------

Unfortunally nothing of interest in the log file.

Hardware/software config : Compaq Armada 1750, Xircom RealPort 10/100, xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh), Kernal 2.2.13, pcmcia 3.1.5

The laptop is plugged into a 100Mbit shared hub. The problem occurs when a lot of traffic is generated on the network. In our case a backup between a server and a client machine.

Regards Mark Harvey

None Well, I guess that's progress

Re: Sad Total lockup with xircom in promiscuous mode (Mark Harvey)
Date: 1999, Dec 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The "RX drop" messages will be turned off in 3.1.6, since they are
"normal": this card cannot possibly keep up with a 100baseT traffic
stream, because the data path between the card and the CPU is only
about 2MB/sec.  It works ok in non-promiscuous mode because a sender
will automatically throttle down its data rate when packets are
dropped.  In promiscuous mode, if the segment is loaded, you'll
just soak up 100% of your CPU time servicing receive interrupts. 

The system still shouldn't totally freeze.  Since you can recreate the
problem outside of VMWare, you should be able to use the instructions
in the PCMCIA-HOWTO for tracking down a kernel lock-up (i.e., direct
kernel messages to the console, cause the problem, see if you get a
kernel trap or can get a location for the freeze using alt-sysrq-P).

-- Dave

Question CBEM56G sleeps 'til a little nudge thru tcpdump(?!)

Date: 1999, Nov 30
From: Kai Krebber bacardi

Hi!

A couple of weeks ago, I installed V 3.0.14 on a Compaq Armada 1700 with SUSE Linux 6.0 and a CBEM56G. Worked fine from the start.

Yesterday I installed V 3.1.4 on a different Armada 1700 with SUSE Linux 6.2 and a CBEM56G on it.

During bootup, the Card starts and ifconfig shows my eth0 - interface. Only I can't ping anything from this machine and the machine doesn't reply to pings from other machines in the net - until I start tcpdump on my Compaq. Then suddenly everything works fine until the next reboot.

Sure it looks a bit funny to first start tcpdump before I can use my card. Is there a more clean way / configuration hint?

TIA,
       Kai Krebber

None Maybe just set promiscuous mode?

Re: Question CBEM56G sleeps 'til a little nudge thru tcpdump(?!) (Kai Krebber)
Date: 1999, Nov 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Try doing "ifconfig eth0 promisc".

I think there's still something broken in how the driver sets up the
chip's address filtering.

-- Dave

Agree This works on RBEM100-56G

Re: None Maybe just set promiscuous mode? (David Hinds)
Date: 1999, Dec 10
From: Chris Hanson <cph@zurich.ai.mit.edu>

I had the same problem with an RBEM100-56G, which appears to be fixed by the "ifconfig eth0 promisc" workaround. So I think Dave's supposition is right.

Feedback try ifconfig too

Re: None Maybe just set promiscuous mode? (David Hinds)
Date: 1999, Dec 11
From: Richard rlotz

I had similar problems with the later tulip_cs driver. Yes, I do believe it is the driver, not the init scripts because I have used the older driver in with newer packages (just copy over new tulip_cs.c with old tulip_cs.c)

I "remedied" the situation by performing an `ifconfig eth0 down` then and `ifconfig eth0 up`

Solves it for me.

Question RBEM56G-100: eth0: Transmit timed out

Date: 1999, Nov 30
From: Bjoern Bayard bb

Hi everybody!

I try to get a Kernel 2.2.13, pcmcia 3.1.4 and a Xircom CARDBUS Ethernet 10/100+Modem 56 running.

Meanwhile all starts fine but when I try to use the eth0 interface (e.g. with a ping) I get the following error-message:

eth0: Transmit timed out, status 60660000, CSR12 000000c4, resetting ...

If I use a REM56G-100 all (eth and modem) works fine in the same machine.

Any ideas?

Best regards Björn Bayard

Note Here are the log-messages

Re: Question RBEM56G-100: eth0: Transmit timed out (Bjoern Bayard)
Date: 1999, Dec 02
From: Bjoern Bayard bb

Hi!

I have tested it with to different systems:

1) Dell CPt C400GT Celeron 400 128MB SuSE 6.2 Kernel 2.2.13, pcmcia
3.1.4

Bootup-Messages from /var/log/messages:

Dec 1 11:21:45 dell syslogd 1.3-3: restart.
Dec 1 11:21:46 dell kernel: klogd 1.3-3, log source = /proc/kmsg
started.
Dec 1 11:21:46 dell kernel: Inspecting /boot/System.map
Dec 1 11:21:46 dell kernel: Loaded 7748 symbols from
/boot/System.map.
Dec 1 11:21:46 dell kernel: Symbols match kernel version 2.2.13.
Dec 1 11:21:46 dell kernel: Loaded 15 symbols from 7 modules.
Dec 1 11:21:46 dell kernel: Linux PCMCIA Card Services 3.1.4
Dec 1 11:21:46 dell kernel: kernel build: 2.2.13 #4 Wed Dec 1
12:08:02 CET
1999
Dec 1 11:21:46 dell kernel: options: [pci] [cardbus] [apm] [pnp]
Dec 1 11:21:46 dell kernel: PnP: PNP BIOS installation structure at 0xc00fe2d0
Dec 1 11:21:46 dell kernel: PnP: PNP BIOS version 1.0, entry at f0000:e2f4, dseg at 40
Dec 1 11:21:46 dell kernel: PCI routing table version 1.0 at 0xfbd90
Dec 1 11:21:46 dell kernel: 00:03.0 -> irq 11
Dec 1 11:21:46 dell kernel: 00:03.1 -> irq 11
Dec 1 11:21:46 dell kernel: Intel PCIC probe:
Dec 1 11:21:46 dell kernel: TI 1225 PCI-to-CardBus at bus 0 slot 3,
mem
0x68000000, 2 sockets
Dec 1 11:21:46 dell kernel: host opts [0]: [ring] [serial pci &
irq] [pci
irq 11] [lat 32/176] [bus 32/34]
Dec 1 11:21:46 dell kernel: host opts [1]: [ring] [serial pci &
irq] [pci
irq 11] [lat 32/176] [bus 35/37]
Dec 1 11:21:46 dell kernel: ISA irqs (scanned) = 3,4,7,9,10
polling
interval = 1000 ms
Dec 1 11:21:46 dell kernel: cs: cb_alloc(bus 32): vendor 0x115d,
device 0x0003
Dec 1 11:21:46 dell kernel: kmem_grow: Called nonatomically from int
- size-128
Dec 1 11:21:46 dell kernel: cs: IO port probe 0x1000-0x17ff: clean.
Dec 1 11:21:46 dell kernel: cs: IO port probe 0x0100-0x04ff: clean.
Dec 1 11:21:46 dell kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Dec 1 11:21:46 dell kernel: ROM image dump:
Dec 1 11:21:46 dell kernel: image 0: 0x000000-0x0001ff, signature
PCIR
Dec 1 11:21:46 dell kernel: Serial driver version 4.27 with no serial
options
enabled
Dec 1 11:21:46 dell kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
Dec 1 11:21:46 dell kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A
Dec 1 11:21:46 dell kernel: cs: cb_config(bus 32)
Dec 1 11:21:46 dell kernel: fn 0 bar 2: mem 0x60017000-0x600177ff
Dec 1 11:21:46 dell kernel: fn 0 bar 3: mem 0x60016000-0x600167ff
Dec 1 11:21:46 dell kernel: fn 1 bar 1: io 0x4b0-0x4b7
Dec 1 11:21:46 dell kernel: fn 1 bar 2: mem 0x60015000-0x600157ff
Dec 1 11:21:46 dell kernel: fn 1 bar 3: mem 0x60014000-0x600147ff
Dec 1 11:21:46 dell kernel: fn 0 bar 1: io 0x430-0x4af
Dec 1 11:21:46 dell kernel: fn 0 rom: mem 0x60010000-0x60013fff
Dec 1 11:21:46 dell kernel: fn 1 rom: mem 0x6000c000-0x6000ffff
Dec 1 11:21:46 dell kernel: cs: cb_enable(bus 32)
Dec 1 11:21:46 dell kernel: bridge io map 0 (flags 0x21):
0x430-0x4b7
Dec 1 11:21:46 dell kernel: bridge mem map 0 (flags 0x1):
0x6000c000-0x60017fff
Dec 1 11:21:46 dell kernel: tulip_attach(bus 32, function 0)
Dec 1 11:21:46 dell kernel: tulip.c:v0.91 4/14/99
becker@cesdis.gsfc.nasa.gov
(modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug
Ledford)
Dec 1 11:21:46 dell kernel: eth0: Xircom Cardbus Adapter (DEC 21143
compatible
mode) rev 3 at 0x400, 00:10:A4:E6:9B:70, IRQ 10.
Dec 1 11:21:46 dell kernel: eth0: MII transceiver #0 config 3100
status 7809
advertising 01e1.
Dec 1 11:21:46 dell kernel: serial_attach(bus 32, fn 1)
Dec 1 11:21:46 dell kernel: tty02 at 0x04b0 (irq = 10) is a 16550A
Dec 1 11:21:51 dell lpd[195]: restarted
Dec 1 11:21:54 dell /usr/sbin/cron[224]: (CRON) STARTUP (fork ok)
Dec 1 11:21:54 dell sshd[221]: log: Server listening on port 22.
Dec 1 11:21:54 dell sshd[221]: log: Generating 768 bit RSA key.
Dec 1 11:21:54 dell sshd[221]: log: RSA key generation complete.
Dec 1 11:22:01 dell login: pam_unix session started for user root,
service
login
Dec 1 11:31:03 dell kernel: eth0: Transmit timed out, status
ffffffff, CSR12
000000c4, resetting...
Dec 1 11:31:08 dell kernel: eth0: Transmit timed out, status
ffffffff, CSR12
000000c4, resetting...
Dec 1 11:31:13 dell kernel: eth0: Transmit timed out, status
ffffffff, CSR12
000000c6, resetting...
Dec 1 11:31:43 dell last message repeated 6 times



The second machine I tried is a Toshiba Satellite 4090 XCDT, SuSE 6.2
Kernel
2.2.10 pcmcia 3.1.4. Here is the log from the Toshiba:

Nov 29 17:59:52 satellite syslogd 1.3-3: restart.
Nov 29 17:59:53 satellite kernel: klogd 1.3-3, log source = /proc/kmsg
started.
Nov 29 17:59:53 satellite kernel: Inspecting /boot/System.map
Nov 29 17:59:53 satellite kernel: Loaded 8279 symbols from
/boot/System.map.
Nov 29 17:59:53 satellite kernel: Symbols match kernel version 2.2.10.
Nov 29 17:59:53 satellite kernel: Loaded 20 symbols from 8 modules.
Nov 29 17:59:53 satellite kernel: Serial driver version 4.27 with
HUB-6
MANY_PORTS MULTIPORT SHARE_IRQ enabled
Nov 29 17:59:53 satellite kernel: ttyS00 at 0x03f8 (irq = 4) is a
16550A
Nov 29 17:59:53 satellite kernel: ttyS01 at 0x02f8 (irq = 3) is a 8250
Nov 29 17:59:53 satellite kernel: Linux PCMCIA Card Services 3.1.4
Nov 29 17:59:53 satellite kernel: kernel build: 2.2.10 #4 Thu Nov 18
21:30:36
CET 1999
Nov 29 17:59:53 satellite kernel: options: [pci] [cardbus] [apm]
Nov 29 17:59:53 satellite kernel: Intel PCIC probe:
Nov 29 17:59:53 satellite kernel: Toshiba ToPIC97 PCI-to-CardBus at
bus 0 slot
2, mem 0x68000000, 2 sockets
Nov 29 17:59:53 satellite kernel: host opts [0]: [slot 0xf0] [ccr
0x10] [cdr
0x86] [rcr 0x02] [no pci irq] [lat 168/176] [bus 20/20]
Nov 29 17:59:53 satellite kernel: host opts [1]: [slot 0xf0] [ccr
0x20] [cdr
0x86] [rcr 0x02] [no pci irq] [lat 168/176] [bus 21/21]
Nov 29 17:59:53 satellite kernel: ISA irqs (default) =
4,5,7,9,10,12 polling
interval = 1000 ms
Nov 29 17:59:53 satellite kernel: cs: IO port probe 0x1000-0x17ff:
clean.
Nov 29 17:59:53 satellite kernel: cs: IO port probe 0x0100-0x04ff:
excluding
0x378-0x37f 0x4d0-0x4d7
Nov 29 17:59:53 satellite kernel: cs: IO port probe 0x0a00-0x0aff:
clean.
Nov 29 17:59:53 satellite kernel: cs: cb_alloc(bus 20): vendor 0x115d,
device
0x0003
Nov 29 17:59:53 satellite kernel: ROM image dump:
Nov 29 17:59:53 satellite kernel: image 0: 0x000000-0x0001ff,
signature PCIR
Nov 29 17:59:53 satellite kernel: cs: cb_config(bus 20)
Nov 29 17:59:53 satellite kernel: fn 0 bar 2: mem
0x60017000-0x600177ff
Nov 29 17:59:53 satellite kernel: fn 0 bar 3: mem
0x60016000-0x600167ff
Nov 29 17:59:53 satellite kernel: fn 1 bar 1: io 0x290-0x297
Nov 29 17:59:53 satellite kernel: fn 1 bar 2: mem
0x60015000-0x600157ff
Nov 29 17:59:53 satellite kernel: fn 1 bar 3: mem
0x60014000-0x600147ff
Nov 29 17:59:53 satellite kernel: fn 0 bar 1: io 0x210-0x28f
Nov 29 17:59:53 satellite kernel: fn 0 rom: mem
0x60010000-0x60013fff
Nov 29 17:59:53 satellite kernel: fn 1 rom: mem
0x6000c000-0x6000ffff
Nov 29 17:59:53 satellite kernel: cs: cb_enable(bus 20)
Nov 29 17:59:53 satellite kernel: bridge io map 0 (flags 0x21):
0x210-0x297
Nov 29 17:59:53 satellite kernel: bridge mem map 0 (flags 0x1):
0x6000c000-0x60017fff
Nov 29 17:59:53 satellite kernel: tulip_attach(bus 20, function 0)
Nov 29 17:59:53 satellite kernel: tulip.c:v0.91 4/14/99
becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de
for XIRCOM
CBE, fixed by Doug Ledford)
Nov 29 17:59:53 satellite kernel: eth0: Xircom Cardbus Adapter (DEC
21143
compatible mode) rev 3 at 0x200, 00:10:A4:E6:9B:70, IRQ 5.
Nov 29 17:59:53 satellite kernel: eth0: MII transceiver #0 config
3100 status
7809 advertising 01e1.
Nov 29 17:59:53 satellite kernel: serial_attach(bus 20, fn 1)
Nov 29 17:59:53 satellite kernel: tty02 at 0x0290 (irq = 5) is a
16550A
Nov 29 17:59:58 satellite lpd[195]: restarted
Nov 29 18:00:00 satellite sshd[218]: log: Server listening on port 22.
Nov 29 18:00:00 satellite sshd[218]: log: Generating 768 bit RSA key.
Nov 29 18:00:01 satellite /usr/sbin/cron[220]: (CRON) STARTUP (fork
ok)
Nov 29 18:00:02 satellite sshd[218]: log: RSA key generation complete.
Nov 29 18:00:07 satellite login: pam_unix session started for user
root, service
login
Nov 29 18:03:57 satellite kernel: eth0: Transmit timed out, status
60660000,
CSR12 000000c4, resetting...

Warning Xircom RealPort CardBuss Ethernet 10/100 + Modem 56 problem...

Date: 1999, Nov 30
From: Cahlen Humphreys Cahlen

I just downloaded the new pcmcia drivers from sourceforge..

pcmcia-cs-3.1.4.tar.gz it looks like. Well, it all compiles find and installs. When I try to start up Cardmanager it works fine still. Then it starts up the network. After that though, when I try to ping something it gives me a time out error. It says:

eth0: Transmit timed out, status ffffffff, CSR12000000c2, resetting...

Can anybody help? Thanx.

-Cahlen

Sad IBM 10/100 EtherJet Cardbus

Date: 1999, Dec 01
From: John Payne jpayne

IBM Thinkpad 600E, Redhat 6.1, downloaded kernel 2.2.12, 
tried cardservices 3.0.14 through 3.1.4 and the latest 
3.1.5 development available...

The card is ident'd correctly... I get some destination
host unreachables (the correct route has been added). Then
some random responses. There are 2 devices on this 10Mb hub...
the router and the thinkpad.

eth0      Link encap:Ethernet  HWaddr 00:04:AC:90:6A:09  
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:512 errors:0 dropped:0 overruns:0 frame:0
          TX packets:526 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:9 Base address:0x400 

Kernel Interface table
Iface   MTU Met    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0   1500   0      512      0      0      0      526      0      0      0 BRU
lo     3924   0       60      0      0      0       60      0      0      0 LRU
PING 192.168.1.1 (192.168.1.1) from 192.168.1.2 : 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=10 ttl=255 time=0.8 ms
64 bytes from 192.168.1.1: icmp_seq=0 ttl=255 time=10996.7 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=10000.7 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=9000.7 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=255 time=8000.7 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=255 time=7000.8 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=255 time=6000.8 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=255 time=5000.8 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=255 time=4000.9 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=255 time=3000.9 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=255 time=2000.9 ms
64 bytes from 192.168.1.1: icmp_seq=41 ttl=255 time=0.6 ms
64 bytes from 192.168.1.1: icmp_seq=42 ttl=255 time=0.8 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=255 time=31000.9 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=255 time=30000.9 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=255 time=29000.9 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=255 time=28001.0 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=255 time=27001.0 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=255 time=26001.0 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=255 time=25001.1 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=255 time=24001.1 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=255 time=23001.1 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=255 time=22001.1 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=255 time=21001.2 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=255 time=20001.2 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=255 time=19001.2 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=255 time=18001.2 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=255 time=17001.3 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=255 time=16001.3 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=255 time=15001.3 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=255 time=14001.4 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=255 time=13001.4 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=255 time=12001.4 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=255 time=11001.4 ms
64 bytes from 192.168.1.1: icmp_seq=32 ttl=255 time=10001.5 ms
64 bytes from 192.168.1.1: icmp_seq=33 ttl=255 time=9001.5 ms
64 bytes from 192.168.1.1: icmp_seq=34 ttl=255 time=8001.5 ms
64 bytes from 192.168.1.1: icmp_seq=35 ttl=255 time=7001.5 ms
64 bytes from 192.168.1.1: icmp_seq=36 ttl=255 time=6001.6 ms
64 bytes from 192.168.1.1: icmp_seq=37 ttl=255 time=5001.6 ms
64 bytes from 192.168.1.1: icmp_seq=38 ttl=255 time=4001.6 ms
64 bytes from 192.168.1.1: icmp_seq=39 ttl=255 time=3001.7 ms
64 bytes from 192.168.1.1: icmp_seq=40 ttl=255 time=2001.7 ms
From 192.168.1.2: Destination Host Unreachable
From 192.168.1.2: Destination Host Unreachable
From 192.168.1.2: Destination Host Unreachable
From 192.168.1.2: Destination Host Unreachable
From 192.168.1.2: Destination Host Unreachable
From 192.168.1.2: Destination Host Unreachable
64 bytes from 192.168.1.1: icmp_seq=67 ttl=255 time=1.1 ms
64 bytes from 192.168.1.1: icmp_seq=43 ttl=255 time=24001.2 ms
64 bytes from 192.168.1.1: icmp_seq=44 ttl=255 time=23001.3 ms
64 bytes from 192.168.1.1: icmp_seq=45 ttl=255 time=22001.3 ms
64 bytes from 192.168.1.1: icmp_seq=46 ttl=255 time=21001.3 ms
64 bytes from 192.168.1.1: icmp_seq=47 ttl=255 time=20001.4 ms
64 bytes from 192.168.1.1: icmp_seq=48 ttl=255 time=19001.4 ms
64 bytes from 192.168.1.1: icmp_seq=49 ttl=255 time=18073.7 ms
64 bytes from 192.168.1.1: icmp_seq=50 ttl=255 time=17073.7 ms
64 bytes from 192.168.1.1: icmp_seq=51 ttl=255 time=16073.7 ms
64 bytes from 192.168.1.1: icmp_seq=52 ttl=255 time=15073.8 ms
64 bytes from 192.168.1.1: icmp_seq=53 ttl=255 time=14073.8 ms
64 bytes from 192.168.1.1: icmp_seq=54 ttl=255 time=13073.8 ms
64 bytes from 192.168.1.1: icmp_seq=55 ttl=255 time=12073.8 ms
64 bytes from 192.168.1.1: icmp_seq=56 ttl=255 time=11073.9 ms
64 bytes from 192.168.1.1: icmp_seq=57 ttl=255 time=10073.9 ms
64 bytes from 192.168.1.1: icmp_seq=58 ttl=255 time=9073.9 ms
64 bytes from 192.168.1.1: icmp_seq=59 ttl=255 time=8074.0 ms
64 bytes from 192.168.1.1: icmp_seq=60 ttl=255 time=7074.0 ms
64 bytes from 192.168.1.1: icmp_seq=98 ttl=255 time=0.9 ms
64 bytes from 192.168.1.1: icmp_seq=99 ttl=255 time=1.1 ms
64 bytes from 192.168.1.1: icmp_seq=68 ttl=255 time=31001.2 ms
64 bytes from 192.168.1.1: icmp_seq=69 ttl=255 time=30001.2 ms
64 bytes from 192.168.1.1: icmp_seq=70 ttl=255 time=29001.2 ms
64 bytes from 192.168.1.1: icmp_seq=71 ttl=255 time=28001.3 ms
64 bytes from 192.168.1.1: icmp_seq=72 ttl=255 time=27001.3 ms
64 bytes from 192.168.1.1: icmp_seq=73 ttl=255 time=26001.3 ms
64 bytes from 192.168.1.1: icmp_seq=74 ttl=255 time=25001.3 ms
64 bytes from 192.168.1.1: icmp_seq=75 ttl=255 time=24001.4 ms
64 bytes from 192.168.1.1: icmp_seq=76 ttl=255 time=23001.4 ms
64 bytes from 192.168.1.1: icmp_seq=77 ttl=255 time=22001.4 ms
64 bytes from 192.168.1.1: icmp_seq=78 ttl=255 time=21001.5 ms
64 bytes from 192.168.1.1: icmp_seq=79 ttl=255 time=20001.5 ms
64 bytes from 192.168.1.1: icmp_seq=80 ttl=255 time=19001.5 ms
64 bytes from 192.168.1.1: icmp_seq=81 ttl=255 time=18001.5 ms
64 bytes from 192.168.1.1: icmp_seq=82 ttl=255 time=17001.6 ms
64 bytes from 192.168.1.1: icmp_seq=83 ttl=255 time=16001.6 ms
64 bytes from 192.168.1.1: icmp_seq=84 ttl=255 time=15001.6 ms
64 bytes from 192.168.1.1: icmp_seq=85 ttl=255 time=14001.7 ms
64 bytes from 192.168.1.1: icmp_seq=86 ttl=255 time=13001.7 ms
64 bytes from 192.168.1.1: icmp_seq=87 ttl=255 time=12001.7 ms
64 bytes from 192.168.1.1: icmp_seq=88 ttl=255 time=11001.7 ms
64 bytes from 192.168.1.1: icmp_seq=89 ttl=255 time=10001.8 ms
64 bytes from 192.168.1.1: icmp_seq=90 ttl=255 time=9001.8 ms
64 bytes from 192.168.1.1: icmp_seq=91 ttl=255 time=8001.8 ms
64 bytes from 192.168.1.1: icmp_seq=92 ttl=255 time=7001.9 ms
64 bytes from 192.168.1.1: icmp_seq=93 ttl=255 time=6001.9 ms
64 bytes from 192.168.1.1: icmp_seq=94 ttl=255 time=5001.9 ms
64 bytes from 192.168.1.1: icmp_seq=95 ttl=255 time=4001.9 ms
64 bytes from 192.168.1.1: icmp_seq=96 ttl=255 time=3002.0 ms
64 bytes from 192.168.1.1: icmp_seq=97 ttl=255 time=2002.0 ms
From 192.168.1.2: Destination Host Unreachable
From 192.168.1.2: Destination Host Unreachable
From 192.168.1.2: Destination Host Unreachable
From 192.168.1.2: Destination Host Unreachable
From 192.168.1.2: Destination Host Unreachable
From 192.168.1.2: Destination Host Unreachable
From 192.168.1.2: Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
107 packets transmitted, 94 packets received, +13 errors, 12% packet loss
round-trip min/avg/max = 0.6/14202.0/31001.2 ms
eth0      Link encap:Ethernet  HWaddr 00:04:AC:90:6A:09  
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:640 errors:0 dropped:0 overruns:0 frame:0
          TX packets:661 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:9 Base address:0x400 

Kernel Interface table
Iface   MTU Met    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0   1500   0      640      0      0      0      661      0      0      0 BRU
lo     3924   0       73      0      0      0       73      0      0      0 LRU

None Interrupt conflict?

Re: Sad IBM 10/100 EtherJet Cardbus (John Payne)
Date: 1999, Dec 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You should always look at your system log messages.

Looks to me like you've got an interrupt conflict on irq 9.

-- Dave

Disagree i don't think so

Re: None Interrupt conflict? (David Hinds)
Date: 1999, Dec 01
From: John Payne jpayne

Nothing in syslog... and nothing in dmesg that looks out of place (I stupidly forgot to copy the dmesg output I snarfed onto this partition... if you do need it, I'll post it later today after I've slept some).

I excluded IRQ 9, and lo, the card popped up on IRQ 10 with exactly the same symptoms, and /proc/interrupts didn't flag anything on 9.

Windows System Properties shows IRQ 9 as available, with the DSP on IRQ 10. Windows puts my EtherJet in on IRQ 11 along with a stack of other devices such as the PCI to USB Universal Host Controller, Video card, Cardbus controller and several IRQ holders for PCI Steering.

PCMCIA newbie Question - could I force cardservices to force IRQ 11?

None The system log messages are important

Re: Disagree i don't think so (John Payne)
Date: 1999, Dec 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You can't have nothing in your system log: if you think you do, then
you're looking in the wrong place.

And yes, the messages are important.

-- Dave

None here's the logs

Re: None The system log messages are important (David Hinds)
Date: 1999, Dec 01
From: John Payne jpayne

From the syslog... 
Dec  1 00:30:15 localhost pcmcia: Starting PCMCIA services:
Dec  1 00:30:15 localhost pcmcia:  modules
Dec  1 00:30:15 localhost kernel: Linux PCMCIA Card Services 3.1.5 
Dec  1 00:30:15 localhost kernel:   kernel build: 2.2.12 #1 Fri Nov 26 04:55:18 GMT 1999 
Dec  1 00:30:15 localhost kernel:   options:  [pci] [cardbus] [apm] 
Dec  1 00:30:15 localhost kernel: Intel PCIC probe:  
Dec  1 00:30:15 localhost kernel:   TI 1251A PCI-to-CardBus at bus 0 slot 2, mem 0x50102000, 2 sockets 
Dec  1 00:30:15 localhost kernel:     host opts [0]: [ring] [pwr save] [isa irq] [no pci irq] [lat 168/176] [bus 2/4] 
Dec  1 00:30:15 localhost kernel:     host opts [1]: [ring] [pwr save] [isa irq] [no pci irq] [lat 168/176] [bus 5/7] 
Dec  1 00:30:15 localhost kernel:     ISA irqs (scanned) = 3,4,7,9,10 polling interval = 1000 ms 
Dec  1 00:30:15 localhost pcmcia:  cardmgr.
Dec  1 00:30:16 localhost cardmgr[324]: starting, version is 3.1.5
Dec  1 00:30:16 localhost rc: Starting pcmcia succeeded
Dec  1 00:30:16 localhost cardmgr[324]: watching 2 sockets
Dec  1 00:30:16 localhost kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x15e8-0x15ef 
Dec  1 00:30:16 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x130-0x137 0x200-0x207 0x220-0x22f 0x388-0x38f 0x3b8-0x3df 0x4d0-0x4d7 
Dec  1 00:30:16 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Dec  1 00:30:16 localhost kernel: cs: cb_alloc(bus 5): vendor 0x115d, device 0x0003 
Dec  1 00:30:16 localhost cardmgr[324]: initializing socket 1
Dec  1 00:30:16 localhost cardmgr[324]: socket 1: IBM 10/100 EtherJet CardBus
Dec  1 00:30:16 localhost inet: inetd startup succeeded
Dec  1 00:30:16 localhost cardmgr[324]: executing: 'insmod /lib/modules/2.2.12/pcmcia/cb_enabler.o'
Dec  1 00:30:16 localhost cardmgr[324]: executing: 'insmod /lib/modules/2.2.12/pcmcia/tulip_cb.o'
Dec  1 00:30:16 localhost kernel: cs: cb_config(bus 5) 
Dec  1 00:30:16 localhost kernel:   fn 0 bar 1: io 0x400-0x47f 
Dec  1 00:30:16 localhost kernel:   fn 0 bar 2: mem 0x6000d000-0x6000d7ff 
Dec  1 00:30:16 localhost kernel:   fn 0 bar 3: mem 0x6000c000-0x6000c7ff 
Dec  1 00:30:16 localhost kernel:   fn 0 rom: mem 0x60008000-0x6000bfff 
Dec  1 00:30:16 localhost kernel: tulip_attach(bus 5, function 0) 
Dec  1 00:30:16 localhost kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford) 
Dec  1 00:30:16 localhost kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x400, 00:04:AC:90:6A:09, IRQ 9. 
Dec  1 00:30:16 localhost kernel: eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1. 
Dec  1 00:30:16 localhost cardmgr[324]: executing: './network start eth0'


And from dmesg:
Linux PCMCIA Card Services 3.1.5
  kernel build: 2.2.12 #1 Fri Nov 26 04:55:18 GMT 1999
  options:  [pci] [cardbus] [apm]
Intel PCIC probe: 
  TI 1251A PCI-to-CardBus at bus 0 slot 2, mem 0x50102000, 2 sockets
    host opts [0]: [ring] [pwr save] [isa irq] [no pci irq] [lat 168/176] [bus 2/4]
    host opts [1]: [ring] [pwr save] [isa irq] [no pci irq] [lat 168/176] [bus 5/7]
    ISA irqs (scanned) = 3,4,7,9,10 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: excluding 0x15e8-0x15ef
cs: IO port probe 0x0100-0x04ff: excluding 0x130-0x137 0x200-0x207 0x220-0x22f 0x388-0x38f 0x3b8-0x3df 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: cb_alloc(bus 5): vendor 0x115d, device 0x0003
ROM image dump:
  image 0: 0x000000-0xffffffff, signature PCIR
cs: cb_config(bus 5)
  fn 0 bar 1: io 0x400-0x47f
  fn 0 bar 2: mem 0x6000d000-0x6000d7ff
  fn 0 bar 3: mem 0x6000c000-0x6000c7ff
  fn 0 rom: mem 0x60008000-0x6000bfff
cs: cb_enable(bus 5)
  bridge io map 0 (flags 0x21): 0x400-0x47f
  bridge mem map 0 (flags 0x1): 0x60008000-0x6000dfff
tulip_attach(bus 5, function 0)
tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x400, 00:04:AC:90:6A:09, IRQ 9.
eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1.

Do you need anything else?

None A question and something to try

Re: None here's the logs (John Payne)
Date: 1999, Dec 02
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Do you have any other cards that work (or not)?

Try setting PCIC_OPTS="irq_mode=2" in /etc/sysconfig/pcmcia.

-- Dave

None still no luck

Re: None A question and something to try (David Hinds)
Date: 1999, Dec 03
From: John Payne jpayne

PCIC_OPTS didn't fix it...

I have a Turbo TokenRing card that works if I comment out the himem line and leave the tokenring line commented out in config.opts.

Note Hmm. I had that card working (I think)

Re: Sad IBM 10/100 EtherJet Cardbus (John Payne)
Date: 1999, Dec 05
From: Paul Kronenwetter kronenpj

John,

  It sounds like the same problem I'm having, except that my card is an IBM CB EtherJet + 56K modem.  I recognize that you don't have that card from the Manufacturer ID (unless they've changed it.)

I don't remember the specifics on what I did to make the card work (it's been about 6 months since I "upgraded"). Although I do remember having 0.91g from Donald Becker and using something in the 3.0.x series. (That's before clients/tulip_cb.c appeared and instead was named clients/tulip.c).

I'm interested in what you find out and/or helping if possible.

-Paul

Sad Problem with T8000 and CBE 10/100

Date: 1999, Dec 03
From: Frederic FENOGLIETTO Pegase

I write the 29 August 1999 in your last message forum

I've got some problems with my Xircom ethernet card and my Toshiba.

I use kernel 2.2.10 of Linux and Pcmcia package 3.0.14.

I make all the modifications I read before, as change the Pcmcia bios version to cardbus and force the Xircom to take the IRQ 10 with the irq_list parameter.

The Pcmcia package 3.0.14 have the right version of tulip_cb.o so I don't change it. The only modification I do for the package is in the config file, where I change the Xircom "CBEII-1O/100" value with the ""CBE-10/100", "*"".

My card is recognize by the cardmgr, but the tulip driver doesn't find it is a Xircom one. Look at this...

Aug 29 16:36:47 localhost kernel: Linux PCMCIA Card Services 3.0.14 
Aug 29 16:36:47 localhost kernel:   kernel build: 2.2.10 #1 jeu aoû 26 10:39:13 CEST 1999 
Aug 29 16:36:47 localhost kernel:   options:  [pci] [cardbus] [apm] 
Aug 29 16:36:47 localhost kernel: Intel PCIC probe:  
Aug 29 16:36:47 localhost kernel:   Toshiba ToPIC95-B PCI-to-CardBus at bus 0 slot 11, mem 0x68000000, 2 sockets 
Aug 29 16:36:47 localhost kernel:     host opts [0]: [slot 0xf0] [ccr 0x10] [cdr 0x86] [rcr 0x02] [no pci irq] [lat 168/176] [bus 20/20] 
Aug 29 16:36:47 localhost kernel:     host opts [1]: [slot 0xf0] [ccr 0x20] [cdr 0x86] [rcr 0x02] [no pci irq] [lat 168/176] [bus 21/21] 
Aug 29 16:36:47 localhost kernel:     ISA irqs (default) = 3,10 polling interval = 1000 ms 
Aug 29 16:36:47 localhost kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Aug 29 16:36:47 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x4d0-0x4d7 
Aug 29 16:36:47 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Aug 29 16:36:47 localhost cardmgr[622]: starting, version is 3.0.14
Aug 29 16:36:47 localhost cardmgr[622]: watching 2 sockets
Aug 29 16:36:47 localhost cardmgr[622]: initializing socket 0
Aug 29 16:36:47 localhost kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
Aug 29 16:36:47 localhost cardmgr[622]: socket 0: Serial or Modem
Aug 29 16:36:47 localhost cardmgr[622]: executing: 'insmod /lib/modules/2.2.10/pcmcia/serial_cs.o'
Aug 29 16:36:47 localhost kernel: tty01 at 0x02f8 (irq = 3) is a 16550A 
Aug 29 16:36:47 localhost cardmgr[622]: executing: './serial start ttyS1'
Aug 29 16:36:47 localhost cardmgr[622]: initializing socket 1
Aug 29 16:36:47 localhost cardmgr[622]: socket 1: Xircom CardBus 10/100 Ethernet
Aug 29 16:36:48 localhost cardmgr[622]: executing: 'insmod /lib/modules/2.2.10/pcmcia/cb_enabler.o'
Aug 29 16:36:48 localhost cardmgr[622]: executing: 'insmod /lib/modules/2.2.10/pcmcia/tulip_cb.o'
Aug 29 16:36:48 localhost kernel: cs: cb_config(bus 21): vendor 0x1011, device 0x0019 
Aug 29 16:36:48 localhost kernel:   fn 0 bar 1: io 0x400-0x47f 
Aug 29 16:36:48 localhost kernel:   fn 0 bar 2: mem 0x60081000-0x6008107f 
Aug 29 16:36:48 localhost kernel:   fn 0 rom: mem 0x60041000-0x60080fff 
Aug 29 16:36:48 localhost kernel: tulip_attach(bus 21, function 0) 
Aug 29 16:36:48 localhost kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford) 
Aug 29 16:36:48 localhost kernel: eth0: Digital DS21143 Tulip rev 48 at 0x400, EEPROM not present, 00:4C:69:6E:75:79, IRQ 10. 
Aug 29 16:36:48 localhost cardmgr[622]: executing: './network start eth0'

The kernel say it's a digital one. I saw in the mini how-to version 3 that the kernel must say it's a Xircom ethernet card. And, the MAC address is false...

Here a part of the mini how-to

Jul 15 14:23:39 ocs3 kernel: tulip_attach(bus 1, function 0) 
  Jul 15 14:23:39 ocs3 kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov 
  Jul 15 14:23:39 ocs3 kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0xa00, auto scanning for Xircom cis_hwaddr, found at 0x170. 00:10:A4:F3:A3:79, IRQ 3. 
  Jul 15 14:23:39 ocs3 kernel: tulip.c: Check ethernet address, might have wrong value! 
  Jul 15 14:23:39 ocs3 kernel: tulip.c: Should start with 00:10:A4 for RBEM56, use cis_hwaddr if necessary. 
  Jul 15 14:23:39 ocs3 kernel: eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1. 
  Jul 15 14:23:39 ocs3 kernel: XIRCOM init 

In consequencies, the card doesn't work in my network.

Here a part of my dump_cis

Socket 1:
  offset 0x82, tuple 0x13, link 0x03
    ff ff ff 
  link_target

  offset 0x87, tuple 0x15, link 0x32
    05 00 58 69 72 63 6f 6d 00 43 61 72 64 42 75 73 
    20 45 74 68 65 72 6e 65 74 20 31 30 2f 31 30 30 
    00 43 42 45 2d 31 30 2f 31 30 30 00 31 2e 30 31 
    00 ff 
  vers_1 5.0, "Xircom", "CardBus Ethernet 10/100", "CBE-10/100", "1.01"

  offset 0xbb, tuple 0x88, link 0x04
    ff ff ff ff 

  offset 0xc1, tuple 0x20, link 0x05
    05 01 02 01 81 
  manfid 0x0105, 0x0102

  offset 0xc8, tuple 0x44, link 0x04
    ff ff ff ff 

  offset 0xce, tuple 0x21, link 0x02
    06 00 
  funcid network_adapter

  offset 0xd2, tuple 0x22, link 0x08
    ff ff ff ff ff ff ff ff 

  offset 0xdc, tuple 0x22, link 0x02
    ff ff 

  offset 0xe0, tuple 0x22, link 0x05
    ff ff ff ff ff 

  offset 0xe7, tuple 0x22, link 0x05
    ff ff ff ff ff 

  offset 0xee, tuple 0x22, link 0x02
    ff ff 

  offset 0xf2, tuple 0x22, link 0x02
    ff ff 

  offset 0xf6, tuple 0x22, link 0x02
    ff ff 

  offset 0xfa, tuple 0x1c, link 0x04
    ff ff ff ff 

  offset 0x100, tuple 0x07, link 0x06
    ff ff ff ff ff ff 
  BAR 7 size 4095mb [io] [prefetch] [cacheable] [<1mb]

  offset 0x108, tuple 0x07, link 0x06
    ff ff ff ff ff ff 
  BAR 7 size 4095mb [io] [prefetch] [cacheable] [<1mb]

  offset 0x110, tuple 0x07, link 0x06
    ff ff ff ff ff ff 
  BAR 7 size 4095mb [io] [prefetch] [cacheable] [<1mb]

  offset 0x118, tuple 0x04, link 0x07
    ff ff ff ff ff ff ff 
  parse error: Paramètre invalide

  offset 0x121, tuple 0x05, link 0x08
    ff ff ff ff ff ff ff ff 
  parse error: Paramètre invalide

  offset 0x12b, tuple 0x05, link 0x08
    ff ff ff ff ff ff ff ff 
  parse error: Paramètre invalide

No lan_id parameter...

I try a lot of things like uses the old driver, pcmcia 3.0.13 and the patch for the Xircom etc... The result is the same...

If anyone could help me...

Now, I am T8000 bios version 8.2 (prior 8.00), linux kernel 2.2.13 pre 15 and PCMCIA Package 3.1.5.

Now, it's OK with dump_cis

Socket 1:
  vers_1 5.0, "Xircom", "CardBus Ethernet 10/100", "CBE-10/100", "1.01"
  manfid 0x0105, 0x0102
  funcid network_adapter
  lan_node_id 00 80 c7 64 83 a2
  lan_technology ethernet
  lan_speed 10 mb/sec
  lan_speed 100 mb/sec
  lan_media unshielded_twisted_pair
  lan_media thin_coax
  lan_connector Closed connector standard
  BAR 1 size 63kb [io]
  BAR 2 size 128b [mem] [prefetch]
  BAR 7 size 1kb [mem] [prefetch]
  config_cb base 0x0042 last_index 0x02
  cftable_entry_cb 0x01 [default]
    [master] [invalidate] [parity] [wait] [serr] [fast back]
    irq mask 0x8ebc [level] [shared]
    mem_base 2
  cftable_entry_cb 0x02
    [master] [invalidate] [parity] [wait] [serr] [fast back]
    io_base 1
    irq mask 0x8ebc [level] [shared]

Whaooo, i've hot a lan_id.

But, I always have problem with the tulip_cb driver...

Dec  3 22:40:27 localhost kernel: Linux PCMCIA Card Services 3.1.5 
Dec  3 22:40:27 localhost kernel:   kernel build: 2.2.13pre15 #2 sam nov 6 23:24:11 CET 1999 
Dec  3 22:40:27 localhost kernel:   options:  [pci] [cardbus] [apm] 
Dec  3 22:40:27 localhost kernel: Intel PCIC probe:  
Dec  3 22:40:27 localhost kernel:   Toshiba ToPIC97 PCI-to-CardBus at bus 0 slot 11, mem 0x68000000, 2 sockets 
Dec  3 22:40:27 localhost kernel:     host opts [0]: [slot 0xf0] [ccr 0x10] [cdr 0x86] [rcr 0x02] [no pci irq] [lat 168/176] [bus 20/20] 
Dec  3 22:40:27 localhost kernel:     host opts [1]: [slot 0xf0] [ccr 0x20] [cdr 0x86] [rcr 0x02] [no pci irq] [lat 168/176] [bus 21/21] 
Dec  3 22:40:27 localhost kernel:     ISA irqs (default) = 3,10 polling interval = 1000 ms 
Dec  3 22:40:27 localhost cardmgr[623]: starting, version is 3.1.5
Dec  3 22:40:27 localhost cardmgr[623]: watching 2 sockets
Dec  3 22:40:27 localhost kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Dec  3 22:40:27 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x378-0x37f 0x4d0-0x4d7 
Dec  3 22:40:27 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Dec  3 22:40:28 localhost kernel: cs: cb_alloc(bus 21): vendor 0x1011, device 0x0019 
Dec  3 22:40:28 localhost kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
Dec  3 22:40:28 localhost cardmgr[623]: initializing socket 0
Dec  3 22:40:28 localhost cardmgr[623]: socket 0: Serial or Modem
Dec  3 22:40:28 localhost cardmgr[623]: executing: 'insmod /lib/modules/2.2.13pre15/pcmcia/serial_cs.o'
Dec  3 22:40:28 localhost kernel: tty01 at 0x13f8 (irq = 3) is a 16550A 
Dec  3 22:40:28 localhost cardmgr[623]: executing: './serial start ttyS1'
Dec  3 22:40:28 localhost cardmgr[623]: initializing socket 1
Dec  3 22:40:28 localhost cardmgr[623]: socket 1: Xircom CardBus 10/100 Ethernet
Dec  3 22:40:28 localhost cardmgr[623]: executing: 'insmod /lib/modules/2.2.13pre15/pcmcia/cb_enabler.o'
Dec  3 22:40:28 localhost cardmgr[623]: executing: 'insmod /lib/modules/2.2.13pre15/pcmcia/tulip_cb.o'
Dec  3 22:40:29 localhost kernel: cs: cb_config(bus 21) 
Dec  3 22:40:29 localhost kernel:   fn 0 bar 1: io 0x280-0x2ff 
Dec  3 22:40:29 localhost kernel:   fn 0 bar 2: mem 0x600c0000-0x600c007f 
Dec  3 22:40:29 localhost kernel:   fn 0 rom: mem 0x60080000-0x600bffff 
Dec  3 22:40:29 localhost kernel: tulip_attach(bus 21, function 0) 
Dec  3 22:40:29 localhost kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford) 
Dec  3 22:40:29 localhost kernel: eth0: Digital DS21143 Tulip rev 48 at 0x280, EEPROM not present, 00:4C:69:6E:75:79, IRQ 10. 
Dec  3 22:40:29 localhost cardmgr[623]: executing: './network start eth0'

As we can see, it's not the good MAC adress !!!

I try the IRQ 9 and 10 with the same result. And, my Xircom card is not recognize as a Xircom one.

I'm not very good in C, but, in the tulip_cb driver, I read that the driver use the lan_id value for initialize the MAC Adress, but as my card is not see as a Xircom one.

None Try newer drivers

Re: Sad Problem with T8000 and CBE 10/100 (Frederic FENOGLIETTO)
Date: 1999, Dec 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> I use kernel 2.2.10 of Linux and Pcmcia package 3.0.14.

Upgrade to the current driver release, which is now 3.1.5.

-- Dave Hinds

More I've already do that

Re: Sad Problem with T8000 and CBE 10/100 (Frederic FENOGLIETTO)
Date: 1999, Dec 05
From: Frederic FENOGLIETTO Pegase

I say it at the end of my last message. In fact, in my last message, I explain the problem I have later (no good result with dump_cis) and the result I've got now with the new 3.1.5 pcmcia package (good result with dump_cis but the tulip_cb driver don't work with my card).

If someone have an idea !

Note Sorry, you are out of luck

Re: Sad Problem with T8000 and CBE 10/100 (Frederic FENOGLIETTO)
Date: 1999, Dec 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I misread your original message. The CBE 10/100 is just not supported. The fact that dump_cis works now is irrelevant and not helpful, because dump_cis should work for any random card. It doesn't change the fact that there's no driver for this card.

-- Dave

Question eth0 TIMED OUT with RBEM56G

Date: 1999, Dec 04
From: Jean-Pierre Hermand jph

Tecra8000/kernel 2.2.13/pcmcia 3.1.2

I am reposting this message because he was misplaced.

Any idea why eth0 timed out (TX hung) when using SIMULTANEOUSLY 10 Mbit ethernet and modem-emulated ISDN with a ipmasq (ipchains) setup?

Problems also occur with extensive pinging home lan meanwhile connected to ISP via PPP.

The Xircom RBEM56G is assigned irq 10.

I saw a few messages in the old forums about eth0 timed out but nobody ever replied to these messages.

Now in the new forum I can see that there are again questions on related problems.

Does anybody ever succeed to use both functions of this card simultaneously??? My experience is that both functions can work for a while but eventually the ethernet will fail. Then a ifconfig eth0 stop/start cycle will usually (but not always) restores operation.

Another question: How can we force a specific interrupt for CARDBUS drivers. Looking at the drivers code it does not seem to be an option.

Jp

None It's a limitation of the current driver

Re: Question eth0 TIMED OUT with RBEM56G (Jean-Pierre Hermand)
Date: 1999, Dec 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

At the driver level, it is hard to correctly handle simultaneous use
of both card functions, without occasionally dropping interrupts.  The
tulip driver will need to be modified to detect and recover from this;
but no one is maintaining the Xircom updates to this driver.

-- Dave

Sad RBEM56G-100 & Tosibha 2655XDVD machines... whacky stuff

Date: 1999, Dec 05
From: Eric Malkowski <malk@ultranet.com>

Hi all-

We just got 4 laptops and w/Xircom RBEM56G-100 cards for business use. I've been able to use the card perfectly under only one specific set of conditions--during a Slackware 7.0 install via NFS. Slack 7.0 comes with kernel 2.2.13 and PCMCIA 3.0.14. I used the bare.i bootdisk, color.gz rootdisk, and supplemental pcmcia.dsk (a new thing Pat Volkerding has been doing) to get things up and going.

The laptops are Toshiba 2655 XDVD models w/ the software configurable BIOS via "tsetup.exe" program. The pcmcia bios selection was set to "AUTO" for the above slack 7.0 case.

When starting pcmcia.dsk, the modules get loaded from floppy (introducing some "delay" due to slowness of a floppy). The ususal beeps would be heard (with some delay between them) and the card comes up fine. The slack 7.0 setup mounts NFS without a problem and installation is flawless.

However... after install and reboot, no beeps are heard from PCMCIA startup, and the keyboard doesn't work (typing anything at the login prompt reveals nothing!) 3 fingered salute (CTRL-ALT-DEL) doesn't work...

power off and boot to single user, disable PCMCIA, and the system comes up.

Starting PCMCIA after boot-up manually... Cardcage is detected (PCIC I think -- I'll verify), but cardmgr comes back after a few seconds with "Socket 0: timed out on reset". No keyboard hang luckily...

Ok ... So I changed to Redhat because that's what we want to use when we deliver these to our customer... Redhat 6.1 comes w/kernel 2.2.12(20) w/ same PCMCIA version. Same behavior.

So I started messing with CARDMGR_OPTS in /etc/sysconfig/pcmcia file... I kept doubling every delay parameter available (the reset-related ones etc). After a while of trial and error and pretty large numbers in there, the card was detected and drivers loaded... couldn't test w/ a network cuz it was late and I was at home...

So next day I booted (w/ params left untouched) and no card detection ... Tried tweaking params some more... no dice.

Noticed that PCMCIA 3.1.5 was put up on December 2nd... grabbed it, built it fine, no 32 bit cardbus support. Same socket 0 timeout stuff... bummer.

So I changed the BIOS to "Cardbus-16" forced, rebooted and everything detected nicely and drivers loaded -- (I'm in ToPIC mode now) Thought I was all set!

Went into the lab and tried it out on the network... seemingly "random" ping packets would be received... telnet wouldn't work... I think RX or TX errors were going up in ifconfig report -- didn't look at netstat -i or anything... frustrated.

Tried booting slack 7.0 bare.i, color.gz, and pcmcia.dsk as a control... no card detection. Changed BIOS to "PCIC forced", no card detection. Changed BIOS to "Auto"... card works like a dream again (just like NFS install above)!!! ...

So -- the question is why the heck does this only seem to work when booted from slackware floppies w/ BIOS in "auto" mode... It works aweseome... If I can reproduce those conditions under a boot from harddisk environment, I'm all set (I suppose I could stick with 3.0.14 and 2.1.13 kernel).

BTW -- the post-install kernel from the slack 7.0 install I did is exactly the same as bare.i disk... 2.1.13, pcmcia 3.0.14 ... only the timeouts occur in that case.

I guess I haven't tried kernel 2.1.13 w/ 3.1.5 pcmcia stuff.

I'm going to try to simulate (when booted from hard disk) exactly what Pat Volkerding's pcmcia.dsk does w/ kernel 2.1.13 and PCMCIA 3.0.14... I'll try to post findings ... I'm open for any suggestions... I'm gonna also try kernel 2.1.13 w/ 3.1.5 PCMCIA stuff. I'll try all combinations of BIOS setting with these too....

The wierd thing is--I know it will work (from slack 7.0 install experience), so I'm not going to give up.

Ok More tinkering with this... Some success!

Re: Sad RBEM56G-100 & Tosibha 2655XDVD machines... whacky stuff (Eric Malkowski)
Date: 1999, Dec 06
From: Eric Malkowski <malk@ultranet.com>

After reading some more of the messages posted here, I tried something I saw someone else was having success with...

PCMCIA 3.0.14 with 2.2.12(20) kernel. Bootup still reveals socket 0: timed out during reset.

If I do a "cardctl eject" followed by a "cardctl insert" it comes up and works great!

PCMCIA 3.1.5 with 2.2.12(20) kernel w/ cardctl eject/insert trick doesn't work.

Tried forced PCIC mode in bios and nothing works. It only works with BIOS set to "auto" mode.

I haven't tried anything further w/ bios set to Cardbus/16 mode (which makes it be recognized as "ToPIC" mode)

So what I'm doing now is sticking w/ PCMCIA 3.0.14 w/ 2.2.12(20) kernel and I modified pcmia startup script so at the end of the startup it does a "cardctl eject". Now I hear a single beep each time I boot w/ the card installed... When I want to use the ethernet card, I simply do a "cardctl insert" from the shell prompt...

That's a good enough solution for now... it'd be nice if this could eventually be cleaned up. It's too bad Toshiba doesn't seem to want to release the info required to make this stable...

I'm willing to help out in any way by testing new changes to the PCMCIA stuff with my hardware. I'd love to help fix stuff, but I'm not knowledgeable enough w/ device driver programming and PCMCIA in general...

-Eric

Question IRQ sharing and Xircom CardBus (RBEM56G-100BTX)

Date: 1999, Dec 10
From: Anek Vorapanya anekin

Hi,
I've an IBM ThinkPad i1480 and I installed a Red Hat 6.1 Linux.
I'm having trouble with my Xircom network/modem CardBus
I'm suspecting that it has to do with interrupts and then I 
checked the /proc/interrupts and /proc/pci. 
The /proc/interrupts looks fine to me but the /proc/pci doesn't.

From /proc/pci, it seems the interrupt IRQ 9 is being used by
three different devices: CardBus bridge, Lucent Win Modem,
and ATI Rage Mobility M.  As for IRQ 11, I guess that they
are intentionally shared because the two devices (Ethernet
controller and Modem) are on the same Xircom CardBus
card. But the IRQ 9 being shared by three devices that don't
seem to relate in anyway is really something that I can't
quite comprehend. I would really appreciate it if someone
would enlighten me on this one. I've been trying to make
the Xircom CardBus to work for a week without any success
and I begin to think that it has to do with this interrupt
sharing things. I attach some relavent information below.
Thanks,
-anek

-----

I'm using Linux 2.2.13-0.5 kernel (rawhide/Red Hat)

Here is the /proc/interrupts:

           CPU0
  0:      68578          XT-PIC  timer
  1:        909          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  5:          0          XT-PIC  ESS Solo1
  8:          1          XT-PIC  rtc
 12:        499          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:      85314          XT-PIC  ide0
 15:          3          XT-PIC  ide1
NMI:          0

Here is the /proc/pci:

PCI devices found:
  Bus 32, device   0, function  0:
    Ethernet controller: Unknown vendor Unknown device (rev 3).
      Vendor id=115d. Device id=3.
      Medium devsel.  IRQ 11.
      Non-prefetchable 32 bit memory at 0x210 [0x210].
      Non-prefetchable 32 bit memory at 0x60017000 [0x60017000].
      Non-prefetchable 32 bit memory at 0x60016000 [0x60016000].
  Bus 32, device   0, function  1:
    Serial controller: Unknown vendor Unknown device (rev 3).
      Vendor id=115d. Device id=103.
      Medium devsel.  IRQ 11.
      Non-prefetchable 32 bit memory at 0x290 [0x290].
      Non-prefetchable 32 bit memory at 0x60015000 [0x60015000].
      Non-prefetchable 32 bit memory at 0x60014000 [0x60014000].
  Bus  0, device   0, function  0:
    Host bridge: Acer Labs Unknown device (rev 5).
      Vendor id=10b9. Device id=1621.
      Slow devsel.  Master Capable.  No bursts.
      Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
  Bus  0, device   1, function  0:
    PCI bridge: Acer Labs Unknown device (rev 1).
      Vendor id=10b9. Device id=5247.
      Fast devsel.  Master Capable.  No bursts.  Min Gnt=8.
  Bus  0, device   6, function  0:
    Communication controller: Lucent (ex-AT&T) Microelectronics Unknown
device (rev 1).
      Vendor id=11c1. Device id=449.
      Medium devsel.  Fast back-to-back capable.  IRQ 9.  Master Capable.
No bursts.  Min Gnt=252.Max Lat=14.
      Non-prefetchable 32 bit memory at 0x82400000 [0x82400000].
      I/O at 0x90b8 [0x90b9].
      I/O at 0x9400 [0x9401].
  Bus  0, device   7, function  0:
    ISA bridge: Acer Labs M1533 Aladdin IV (rev 10).
      Medium devsel.  Master Capable.  No bursts.
  Bus  0, device   8, function  0:
    Multimedia audio controller: Unknown vendor Unknown device (rev 2).
      Vendor id=125d. Device id=1969.
      Medium devsel.  Fast back-to-back capable.  IRQ 5.  Master Capable.
Latency=32.  Min Gnt=2.Max Lat=24.
      I/O at 0x9000 [0x9001].
      I/O at 0x9050 [0x9051].
      I/O at 0x9070 [0x9071].
      I/O at 0x9090 [0x9091].
      I/O at 0x90a4 [0x90a5].
  Bus  0, device  15, function  0:
    IDE interface: Acer Labs M5229 TXpro (rev 32).
      Medium devsel.  Fast back-to-back capable.  IRQ 15.  Master Capable.
Latency=32.  Min Gnt=2.Max Lat=4.
      I/O at 0x78c0 [0x78c1].
  Bus  0, device  17, function  0:
    Bridge: Acer Labs Unknown device (rev 9).
      Vendor id=10b9. Device id=7101.
      Medium devsel.  Fast back-to-back capable.
  Bus  0, device  19, function  0:
    CardBus bridge: O2 Micro Unknown device (rev 5).
      Vendor id=1217. Device id=6872.
      Slow devsel.  IRQ 9.  Master Capable.  Latency=32.  Min Gnt=128.Max
Lat=4.
  Bus  0, device  20, function  0:
    USB Controller: Acer Labs M5237 USB (rev 3).
      Medium devsel.  Fast back-to-back capable.  IRQ 10.  Master Capable.
Latency=32.
      Non-prefetchable 32 bit memory at 0x82600000 [0x82600000].
  Bus  1, device   0, function  0:
    VGA compatible controller: ATI Unknown device (rev 100).
      Vendor id=1002. Device id=4c4d.
      Medium devsel.  Fast back-to-back capable.  IRQ 9.  Master Capable.
Latency=32.  Min Gnt=8.
      Non-prefetchable 32 bit memory at 0x81000000 [0x81000000].
      I/O at 0x8000 [0x8001].
      Non-prefetchable 32 bit memory at 0x80500000 [0x80500000].

None Interrupt sharing is normal for PCI

Re: Question IRQ sharing and Xircom CardBus (RBEM56G-100BTX) (Anek Vorapanya)
Date: 1999, Dec 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The PCI interrupt sharing is perfectly normal.

Try setting, in /etc/sysconfig/pcmcia,

   PCIC_OPTS="pci_csc=1 pci_int=1"

-- Dave

Feedback Ethernet seems to be working but with some problem

Re: None Interrupt sharing is normal for PCI (David Hinds)
Date: 1999, Dec 11
From: Anek Vorapanya anekin

Hi,

THanks for the tip. The Ethernet part of the Xircom card seems
to be working now. Haven't had any chance to try the modem part
yet. I can send/receive packets on Ethernet. However, there
is some problem with timeout (see the log message below).  Ping
output, attached at the end, is also strange.

Thanks again,
-anek

-----------------------------------------------------------------------
From /var/log/messages:


Dec 10 16:51:10 cose pcmcia: Starting PCMCIA services:
Dec 10 16:51:10 cose pcmcia:  modules
Dec 10 16:51:10 cose kernel: Linux PCMCIA Card Services 3.1.4
Dec 10 16:51:10 cose kernel:   kernel build: 2.2.13-0.5 #1 Tue Nov 30 17:51:15 EST 1999
Dec 10 16:51:10 cose kernel:   options:  [pci] [cardbus] [apm] [pnp]
Dec 10 16:51:10 cose kernel: PnP: PNP BIOS installation structure at 0x800f6570
Dec 10 16:51:10 cose kernel: PnP: PNP BIOS version 1.0, entry at fa000:0, dseg at f0000
Dec 10 16:51:10 cose kernel: PCI routing table version 1.0 at 0xfbad0
Dec 10 16:51:10 cose kernel:   00:13.0 -> irq 9
Dec 10 16:51:10 cose kernel: Intel PCIC probe:
Dec 10 16:51:10 cose kernel:   O2Micro OZ6812 PCI-to-CardBus at bus 0 slot 19, mem 0x68000000, 1 socket
Dec 10 16:51:10 cose kernel:     host opts [0]: [a 24] [b 8d] [c 00] [d 83] [mhpg 18] [fifo 00] [e 2a] [pci irq 9] [lat 32/176] [bus 32/34]
Dec 10 16:51:11 cose kernel:     ISA irqs (default) = 3,4,7,11,12 PCI status changes
Dec 10 16:51:11 cose pcmcia:  cardmgr.
Dec 10 16:51:11 cose rc: Starting pcmcia succeeded
Dec 10 16:51:11 cose cardmgr[377]: starting, version is 3.1.4
Dec 10 16:51:11 cose cardmgr[377]: watching 1 sockets
Dec 10 16:51:11 cose kernel: cs: IO port probe 0x1000-0x17ff: clean.
Dec 10 16:51:11 cose kernel: cs: IO port probe 0x0100-0x04ff: clean.
Dec 10 16:51:11 cose kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Dec 10 16:51:11 cose kernel: cs: cb_alloc(bus 32): vendor 0x115d, device 0x0003
Dec 10 16:51:11 cose cardmgr[377]: initializing socket 0
Dec 10 16:51:11 cose cardmgr[377]: socket 0: Xircom CardBus 10/100 Ethernet + 56K Modem
Dec 10 16:51:11 cose inet: inetd startup succeeded
Dec 10 16:51:11 cose cardmgr[377]: executing: 'insmod /lib/modules/2.2.13-0.5/pcmcia/cb_enabler.o'
Dec 10 16:51:11 cose cardmgr[377]: executing: 'insmod /lib/modules/2.2.13-0.5/pcmcia/tulip_cb.o'
Dec 10 16:51:11 cose cardmgr[377]: executing: 'insmod /lib/modules/2.2.13-0.5/pcmcia/serial_cb.o'
Dec 10 16:51:11 cose kernel: cs: cb_config(bus 32)
Dec 10 16:51:11 cose kernel:   fn 0 bar 2: mem 0x60017000-0x600177ff
Dec 10 16:51:11 cose kernel:   fn 0 bar 3: mem 0x60016000-0x600167ff
Dec 10 16:51:11 cose kernel:   fn 1 bar 1: io 0x290-0x297
Dec 10 16:51:11 cose kernel:   fn 1 bar 2: mem 0x60015000-0x600157ff
Dec 10 16:51:11 cose kernel:   fn 1 bar 3: mem 0x60014000-0x600147ff
Dec 10 16:51:11 cose kernel:   fn 0 bar 1: io 0x210-0x28f
Dec 10 16:51:11 cose kernel:   fn 0 rom: mem 0x60010000-0x60013fff
Dec 10 16:51:11 cose kernel:   fn 1 rom: mem 0x6000c000-0x6000ffff
Dec 10 16:51:11 cose kernel: tulip_attach(bus 32, function 0)
Dec 10 16:51:11 cose kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Dec 10 16:51:11 cose kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x200, 00:10:A4:E5:A6:31, IRQ 9.
Dec 10 16:51:11 cose kernel: eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1.
Dec 10 16:51:11 cose kernel: serial_attach(bus 32, fn 1)
Dec 10 16:51:11 cose kernel: tty01 at 0x0290 (irq = 9) is a 16550A
Dec 10 16:51:11 cose cardmgr[377]: executing: './network start eth0'
Dec 10 16:51:12 cose lpd: lpd startup succeeded
Dec 10 16:51:12 cose autofs: Starting automounter:
Dec 10 16:51:12 cose cardmgr[377]: executing: './serial start ttyS1'
Dec 10 16:51:12 cose rc: Starting autofs succeeded
Dec 10 16:51:12 cose automount[512]: starting automounter version 3.1.3, path = /mnt, maptype = file, mapname = /etc/auto.mnt
Dec 10 16:51:13 cose keytable: Loading keymap:
Dec 10 16:51:13 cose automount[512]: using kernel protocol version 3
Dec 10 16:51:13 cose keytable: Loading /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
Dec 10 16:51:13 cose keytable: Loading system font:
Dec 10 16:51:13 cose rc: Starting keytable succeeded
Dec 10 16:51:15 cose sendmail: sendmail startup succeeded
Dec 10 16:51:16 cose gpm: gpm startup succeeded
Dec 10 16:51:16 cose xfs: xfs startup succeeded
Dec 10 16:51:17 cose xfs: Warning: The directory "/usr/X11R6/lib/X11/fonts/100dpi" does not exist.
Dec 10 16:51:17 cose xfs:          Entry deleted from font path.
Dec 10 16:51:17 cose linuxconf: Linuxconf final setup
Dec 10 16:51:19 cose rc: Starting linuxconf succeeded
Dec 10 16:51:37 cose PAM_pwdb[644]: (kde) session opened for user av0 by (uid=0)
Dec 10 16:51:53 cose automount[512]: attempting to mount entry /mnt/cdrom
Dec 10 16:51:53 cose automount[719]: lookup(file): lookup for cdrom failed
Dec 10 16:51:58 cose PAM_pwdb[727]: (su) session opened for user root by av0(uid=500)
Dec 10 16:52:17 cose PAM_pwdb[745]: (su) session opened for user root by av0(uid=500)
Dec 10 16:52:27 cose kernel: eth0: Transmit timed out, status 60660000, CSR12 000000c4, resetting...
Dec 10 16:52:49 cose PAM_pwdb[762]: (su) session opened for user root by av0(uid=500)
Dec 10 16:53:12 cose kernel: eth0: Transmit timed out, status 60660000, CSR12 000000c4, resetting...
Dec 10 16:53:47 cose last message repeated 3 times
Dec 10 16:54:52 cose last message repeated 5 times
Dec 10 16:56:02 cose last message repeated 5 times

---------------------------------------------------------------------------

Here is the result from ping:

** It should be less than a few milliseconds because the computer
** that I ping is connected to the same hub.

64 bytes from 128.227.176.71: icmp_seq=3526 ttl=255 time=3971.7 ms
64 bytes from 128.227.176.71: icmp_seq=3527 ttl=255 time=2971.7 ms
64 bytes from 128.227.176.71: icmp_seq=3528 ttl=255 time=1971.8 ms
64 bytes from 128.227.176.71: icmp_seq=3529 ttl=255 time=971.8 ms
From cose.dcs.cise.ufl.edu (128.227.176.90): Destination Host Unreachable
From cose.dcs.cise.ufl.edu (128.227.176.90): Destination Host Unreachable
From cose.dcs.cise.ufl.edu (128.227.176.90): Destination Host Unreachable
64 bytes from 128.227.176.71: icmp_seq=3530 ttl=255 time=49971.5 ms
64 bytes from 128.227.176.71: icmp_seq=3531 ttl=255 time=48971.5 ms
64 bytes from 128.227.176.71: icmp_seq=3532 ttl=255 time=47971.6 ms
64 bytes from 128.227.176.71: icmp_seq=3533 ttl=255 time=46971.6 ms

News Autopolarity feature confuses Xircom Cards

Re: Feedback Ethernet seems to be working but with some problem (Anek Vorapanya)
Date: 1999, Dec 17
From: Thomas Meckel tmeckel

Hi Guys,

i faced the same problems as Anek Vorapanya, lame performace
with my Xircom real port modem/lan card. I fixed the problem
by disabling the autopolarity feature in the csr14 register
for the 10baseT mode.
The following explanation is taken from the readme file out
of the recent windows driver release from Xircom:

--- snipp
Auto Polarity Correction
------------------------
Certain 10/100 switches (generally those using Broadcom
transceivers) implement automatic correction for polarity
reversed cables that is not completely compatible with the
same correction provided by the CBEM/RBEM.  If the network
speed is forced to 10Mbps, severe throughput problems may be
experienced.  To resolve this problem, a new Auto Polarity
keyword in the adapter's advanced properties has been added. 
If needed, the default setting of ON (meaning that the card
will compensate for reversed cables) can be set to OFF to
disable polarity correction.  This will restore normal
throughput. 
snapp ---

I plan to add a new option called "autopolarity" for the
tulip driver so that the user can specify if the card will
use this feature or not.

Cheers

Thomas

P.S.: Any comments welcome

Question Untitled

Re: News Autopolarity feature confuses Xircom Cards (Thomas Meckel)
Date: 1999, Dec 18
From: Anek Vorapanya anekin

Hi,

Is there any quick fix to this problem or should I wait for an updated tulip code?

-anek

Feedback Patch for tulip_cb.c

Re: Question Untitled (Anek Vorapanya)
Date: 1999, Dec 19
From: Thomas Meckel tmeckel

Replace the values in the static variable 't21142_csr14' 
(its an array) with the following

static u16 t21142_csr14[] = { 0xCFFF, 0x0705, 0x0705, 0x0000, 0x4F3D, };

and recompile the driver.

Send an reply if this fixes your problem. 
I must say that the fix only partly resolves my problem. 
The 'ping' to hosts on the same lan-segment now works ok, 
but the performance is still poor (32kb with a ftp-connection).
I dont have any clue whats still wrong. Maybe someone else
can help!

Cheers

Thomas

Question Ethernet with Xircom CEMII?

Date: 1999, Dec 10
From: Per von Zweigbergk cannon

Hello.

Anyone here using a Xircom CEM II for ethernet? The modem part works fine. I modified my /etc/pcmcia/config to use the xirc2ps_cs driver. It finds the card correctly, and the right hardware address and everything. Just one small problem: when transmission is attempted, a eth0: transmit timed out is recieved. Any ideas? I'm using the pcmcia support that came with Debian 2.1, and I'm using a 2.0.36 kernel (it's an old machine). Another network card for PCMCIA that I happen to posess, works fine in the same laptop.

Thanks on beforehand :)

Per von Zweigbergk

None I think you are out of luck

Re: Question Ethernet with Xircom CEMII? (Per von Zweigbergk)
Date: 1999, Dec 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I don't believe that the ethernet side of this card is compatible with
the xirc2ps_cs driver.  (which is why it isn't listed as supported)

-- Dave

More CEM II == CE II ?

Re: None I think you are out of luck (David Hinds)
Date: 1999, Dec 10
From: Per von Zweigbergk cannon

Actually, the CE II is listed as supported, and it's essentially the same, as far as I'm concerned, and it is actaully detected as a CE II.

Anyway, the hardware address is correctly detected, so I think that there is quite a good possibility that this card may work *I hope* :)

Any ideas on that?

None I don't think so

Re: More CEM II == CE II ? (Per von Zweigbergk)
Date: 1999, Dec 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Look again, the CE II is listed as *un*supported.  I'd guess that the
CEM II is the ethernet/modem version of the ethernet-only CE II card.

The Xircom cards store their hardware addresses in a generic format
that is part of the PCMCIA standard.  The xirc2ps_cs driver will be
able to pull the hardware address off any card that conforms to this
standard, whether or not the card is compatible with the driver.

-- Dave

Sad hm... ce2 != ce II? confused and angry.

Re: None I don't think so (David Hinds)
Date: 1999, Dec 10
From: Per von Zweigbergk cannon

Hmhm... there is a Xircom Creditcard CE2, which is marked as compatible, but alas, the Xircom CE II is also mentioned lower down, and is branded as unsupported. Didn't notice :(

Bad luck for me I guess :(

This thing with companies not realeasing info on how the cards work inside makes my blood boil. I guess I'll have to tell my friend who wanted to convert that laptop with the busted monitor to a linux consoleless server that he's out of luck unless he runs windows or gets some new cards.

:(

Any idea on any alternate UNIX-like operating system (open source), like, maybe FreeBSD supports this card or something? I'll have to research on that. The last, but most painful for me would be to make some kind of Windows "solution".

Anyways, thanks for some help, and just to be complete on this issue: any ideas on if [when?] there will be support for this card?

Thanks for the help.

None Prospects are dim indeed

Re: Sad hm... ce2 != ce II? confused and angry. (Per von Zweigbergk)
Date: 1999, Dec 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> 
> Any idea on any alternate UNIX-like operating system (open source),
> like, maybe FreeBSD supports this card or something? I'll have to
> research on that. The last, but most painful for me would be to make
> some kind of Windows "solution".

Forget it.  Linux PCMCIA support is much broader than any other UNIX
operating system, open source or otherwise.

> Anyways, thanks for some help, and just to be complete on this issue:
> any ideas on if [when?] there will be support for this card?

Most likely, never, since the card is long out of production, and
Xircom explicitly says on their web site that they will not release
specs for obsolete products.

-- Dave

None I asked for CEM2 specs anyway

Re: None Prospects are dim indeed (David Hinds)
Date: 2000, Feb 06
From: Chris Rasley ChrisRasley

They say on their web page that they can't release specs for some obsolete products because they hold patents on the technology. Well, it *is* obsolete technology. This type of posturing won't keep them ahead of the competition.

I sent in a request for CEM2 specs anyway. If they refuse, the second letter will be to let them know my next ethernet/modem card purchase will be from Anybody-But-Xircom.

Idea What is the position on rev-engineering of the communication?

Re: None Prospects are dim indeed (David Hinds)
Date: 2000, May 06
From: Stanislav Meduna numo

I have Xircom CE-10BC and have also asked Xircom for the specs - no response. I have analyzed some of the communication using dosemu port tracing facilities and some experimenting and now I have a working Linux driver (very basic, very unclean, not ready for publication, but it works for me).

I am however unsure about the possible legal problems with this approach (have asked Xircom too, no response). David, would you accept code created this way in the contrib section / is such code already there?

None Not so much a legal issue, I think

Re: Idea What is the position on rev-engineering of the communication? (Stanislav Meduna)
Date: 2000, May 08
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'd take it as a contrib driver but probably wouldn't want to include
it in the main PCMCIA distribution.  Not so much because of legal
issues, as that it will probably have a fairly limited audience, and
without real specs, maintenance might be a problem.

-- Dave

Feedback Model clarification

Re: Question Ethernet with Xircom CEMII? (Per von Zweigbergk)
Date: 1999, Dec 17
From: David Levin atlas

All the same models: CE2, CE II, CE IIPS, CreditCard Ethernet II Performance Series.

Not the same model as above: CEMII, CreditCard Ethernet + MOdem II

The driver for the CE2 should not work with the CEM2 product. It has a different (older) ethernet chip (Xircom proprietary).

Question OK, CEM2 uses a proprietary chipset, but are docs available?

Re: Feedback Model clarification (David Levin)
Date: 2000, Mar 28
From: Mike Bilow mbilow

Is there sufficient documentation available on the CEM2 and whatever proprietary chipset it contains to enable someone to write or modify a driver to work with its Ethernet half? I have a stack of them sitting here and it would be worth some effort to get them working, old as they are.

Question REM56G-100

Date: 1999, Dec 19
From: Allen Khodabash amk

Hi,

I'm running Caldera 2.3 on a Gateway 2500 Solo using ver 3.0.14-1. I get the "no pcmcia driver in /proc/devices" message from cardinfo. I've had this combo work with redhat, and am wondering if anyone knows any issues with Caldera.

Thanks, Allen

None Intel EtherExpress Pro/100 Mobile 16-bit | kernel 2.2.13 | cardctl 3.1.3

Date: 1999, Dec 22
From: Fuzz

Hi.  Newbie here.  I'm having a problem getting my Intel
EtherExpress 100/Pro 16-bit PCMCIA NIC to work under
SuSE 6.3.

System details:
kernel: 2.2.13
cardctl: 3.1.3
box: IBM ThinkPad 600 2645 41U

Relevant log messages:
kernel: eth0: auto negotiation failed, using 10mbs

Abstract:
Card is recognized and apparently set up properly (two
happy beeps).  In ifconfig I can see the card's correct
MAC address and IP address I've assigned.  However, I have
no link light on the dongle, though I do get one on the hub.  
I can use ifport to change back and forth from 10M to 100M
with apparent success.  Meaning when attached to my cheapie
10M Linksys hub I get a link light on the hub at 10M and when
I use ifport to change to 100M I get wild blinking and
collisions that stop when I switch back to 10M.  When plugged
into my Catalyst 3000, I get a link light on the Cat when
the card is set to 10M, no link light when I change the card
to 100M and the link light returns when I change the setting
on the card back to 10M.  The Catalyst 3000 is a 10M switch.
At no time does the link light (or any light) on the dongle
light up.  When I try to ping another box, no joy, not even
any activity on the wire.  I am able to ping my own IP
address, as well as the loopback address.

I do see that there's a known issue with some cards using
the xirc2ps_cs driver not auto-negotiating properly.  I also
realize I'm not using the most up-to-date cardctl.  I have
downloaded the latest version and I'm willing to take the rest
of the day to figure out how to compile and install, but if
I'm just going to be beating my head against the wall I have
other things more worthy of my time.

Any suggestions?

Thanks,
Fuzz

None A driver upgrade would be in order

Re: None Intel EtherExpress Pro/100 Mobile 16-bit | kernel 2.2.13 | cardctl 3.1.3
Date: 1999, Dec 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> cardctl: 3.1.3

There have been some fixes in the xirc2ps_cs autonegotiation code in
recent releases, specifically 3.1.4-3.1.6.  The latest driver release
is 3.1.8.

-- Dave

None That did the trick, thanks.

Re: None A driver upgrade would be in order (David Hinds)
Date: 1999, Dec 22
From: Fuzz

Now I shall banish the evil OS from this laptop forever.

Forever!

*mad laughter*

Question trouble unsuspending (RH 6.1, pcmcia 3.1.8, Xircom 10/100, IBM Thinkpad 770ED)

Date: 1999, Dec 23
From: Jamie Zawinski jwz

Hi,

When I suspend and then un-suspend my machine, I have to do this in order to get my Xircom ethernet card to come back online:

	usernetctl eth0 down
	/etc/rc.d/init.d/pcmcia restart
	usernetctl eth0 up

It's not enough to just restart pcmcia, nor is it enough to just take eth0 down and then up; I have to do it in that order.

I didn't need to do this with Red Hat 5.1: this started happening when I upgraded to 6.1. So I know that this card can tolerate my laptop suspending then unsuspending, hardware-wise. So something has gone wrong on the software side since I upgraded.

I don't remember what version of pcmcia-cs was on my system when it was still running 5.1.

Any suggestions on how to make my machine unsuspend properly without manual intervention?

Current system details:

    IBM Thinkpad 770ED
    Red Hat 6.1: kernel 2.2.12
    pcmcia-cs-3.1.8
    Xircom 10/100 ethernet/modem card

dmesg says:

    Linux PCMCIA Card Services 3.1.8
      kernel build: 2.2.12-20 #9 Wed Nov 3 03:36:32 PST 1999
      options:  [pci] [cardbus] [apm]
    Intel PCIC probe: 
      TI 1250A PCI-to-CardBus at bus 0 slot 2, mem 0x20822000, 2 sockets
        host opts [0]: [ring] [pwr save] [isa irq] [no pci irq] [lat 168/176] [bus 1/3]
        host opts [1]: [ring] [pwr save] [isa irq] [no pci irq] [lat 168/176] [bus 4/6]
        ISA irqs (scanned) = 3,4,7,10,11 polling interval = 1000 ms
    cs: IO port probe 0x0100-0x03ff: excluding 0x200-0x207 0x220-0x22f
    cs: IO port probe 0x0a00-0x0aff: clean.
    cs: warning: no high memory space available!
    cs: memory probe 0x0d0000-0x0dffff: clean.
    xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh)
    eth0: MII link partner: 0021
    eth0: MII selected
    eth0: media 10BaseT, silicon revision 5
    eth0: Xircom: port 0x300, irq 3, hwaddr 00:10:A4:FD:90:FD
    tty03 at 0x02e8 (irq = 3) is a 16550A
    eth0: MII link partner: 0021
    eth0: MII selected
    eth0: media 10BaseT, silicon revision 5

"grep 'pcmcia\|cardmgr' /var/log/messages" says:

    Dec 22 16:05:20 grendel pcmcia: Starting PCMCIA services:
    Dec 22 16:05:20 grendel pcmcia:  modules
    Dec 22 16:05:20 grendel kernel: Linux PCMCIA Card Services 3.1.8 
    Dec 22 16:05:20 grendel pcmcia:  cardmgr.
    Dec 22 16:05:20 grendel rc: Starting pcmcia succeeded
    Dec 22 16:05:20 grendel cardmgr[366]: starting, version is 3.1.8
    Dec 22 16:05:20 grendel cardmgr[366]: watching 2 sockets
    Dec 22 16:05:21 grendel cardmgr[366]: initializing socket 1
    Dec 22 16:05:21 grendel cardmgr[366]: socket 1: Xircom CEM56 Ethernet/Modem
    Dec 22 16:05:21 grendel cardmgr[366]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/xirc2ps_cs.o'
    Dec 22 16:05:21 grendel cardmgr[366]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/serial_cs.o'
    Dec 22 16:05:23 grendel cardmgr[366]: executing: './network start eth0'
    Dec 22 16:05:24 grendel cardmgr[366]: executing: './serial start ttyS3'
    Dec 22 08:08:38 grendel cardmgr[366]: executing: './network suspend eth0'
    Dec 22 08:08:38 grendel cardmgr[366]: executing: './serial suspend ttyS3'
    Dec 22 08:08:40 grendel cardmgr[366]: executing: './network resume eth0'
    Dec 22 08:08:40 grendel cardmgr[366]: executing: './serial resume ttyS3'
    Dec 22 08:09:08 grendel cardmgr[366]: executing: './network check eth0'
    Dec 22 08:09:08 grendel cardmgr[366]: executing: './serial check ttyS3'
    Dec 22 08:09:08 grendel cardmgr[366]: shutting down socket 1
    Dec 22 08:09:08 grendel cardmgr[366]: executing: './network stop eth0'
    Dec 22 08:09:08 grendel cardmgr[366]: executing: './serial stop ttyS3'
    Dec 22 08:09:08 grendel cardmgr[366]: executing: 'rmmod xirc2ps_cs'
    Dec 22 08:09:08 grendel cardmgr[366]: executing: 'rmmod serial_cs'
    Dec 22 08:09:09 grendel cardmgr[366]: exiting
    Dec 22 08:09:10 grendel kernel: unloading PCMCIA Card Services 
    Dec 22 08:09:10 grendel kernel: Linux PCMCIA Card Services 3.1.8 
    Dec 22 08:09:10 grendel cardmgr[1280]: starting, version is 3.1.8
    Dec 22 08:09:10 grendel cardmgr[1280]: watching 2 sockets
    Dec 22 08:09:11 grendel cardmgr[1280]: initializing socket 1
    Dec 22 08:09:11 grendel cardmgr[1280]: socket 1: Xircom CEM56 Ethernet/Modem
    Dec 22 08:09:11 grendel cardmgr[1280]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/xirc2ps_cs.o'
    Dec 22 08:09:11 grendel cardmgr[1280]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/serial_cs.o'
    Dec 22 08:09:14 grendel cardmgr[1280]: executing: './network start eth0'
    Dec 22 08:09:14 grendel cardmgr[1280]: executing: './serial start ttyS3'

More ditto except on Dell Latitude CS

Re: Question trouble unsuspending (RH 6.1, pcmcia 3.1.8, Xircom 10/100, IBM Thinkpad 770ED) (Jamie Zawinski)
Date: 2000, Jan 17
From: Stewart Allen mrallen

I find that I must kill dhcpcd and shut down card services if I want to suspend and use the card after wake-up (by restarting card services). I've experienced this ever since I got the Xircom (with RH6.0 and pcmcia 3.0x and now with RH6.1 and pcmcia 3.1.8).

The modem does not seem affected by the sleep/wake-up, but ethernet starts to generate errors and card services is then unable to unload/reload forcing a reboot.

results of `cat /proc/bus/pccard/*` (before sleep):

serial_cb                0 1
tulip_cb                 0 1
0000-001f : pnp 05
0020-003f : pnp 03
0040-005f : pnp 04
0060-0060 : pnp 06
0061-0061 : pnp 08
0064-0064 : pnp 06
0070-007f : pnp 09
0080-009f : pnp 05
00a0-00bf : pnp 03
00c0-00df : pnp 05
00e0-00e1 : pnp 01
00f0-00ff : pnp 0a
0378-037f : pnp 0e
03e0-03e1 : pnp 0b
03e8-03ef : pnp 0d
03f0-03f1 : pnp 01
03f2-03f5 : pnp 0f
03f7-03f7 : pnp 0f
03f8-03ff : pnp 0c
04d0-04d1 : pnp 03
0778-077b : pnp 0e
0800-083f : pnp 01
0840-084f : pnp 01
0860-086f : pci 00:07.1
0cf8-0cff : pnp 00
ece0-ecff : pci 00:07.2
f400-f4fe : pnp 02
  0:  pnp 04
  1:  pnp 06
  2:  pnp 03
  4:  pnp 0c, pnp 0d
  5:  pnp 0b
  6:  pnp 0f
  7:  pnp 0e
  8:  pnp 09
 11:  pci 00:07.2
 12:  pnp 07
 13:  pnp 0a
00000000-0009ffff : pnp 01
000f0000-000fffff : pnp 01
00100000-0fffffff : pnp 01
100a0000-100bffff : pnp 01
60008000-60013fff : cb_enabler
68000000-68000fff : i82365
68001000-68001fff : i82365
ed000000-edffffff : pnp 02
f0000000-f3ffffff : pci 00:00.0
fffe0000-ffffffff : pnp 01

Question Xircom 2CEps, tecra 8000, and RedHat 6.0

Date: 1999, Dec 30
From: Irene

I recently installed RedHat linux 6.0 on my Toshiba Tecra 8000 (dual booting with Windows 95). I have a Xircom 2CEps creditcard network adapter which I can't seem to get configured. I can ping the loopback address and myself, but I cannot ping anyone else on my subnet (messages are transmitted, but none received). I am a newbie to Linux but here is some information that I hope will help in diagnosing the problem:

During startup, I get the following messages:

Bringing up interface lo: OK Bringing up interface eth0: Delaying eth0 initialization: FAILED

In /var/log/boot.log, there is the following:

Poohbear network: Bringing up interface lo succeeded Poohbear ifup: Delaying eth0 initialization Poohbear network: Bringing up interface eth0 failed

Poohbear pcmcia:  Starting pcmcia services
Poohbear pcmcia:  modules
Poohbear pcmcia:  cardmgr
Poohbear rd: Starting pcmcia succeeded

Typing dmesg at /root gives me the following info: xirc2ps_cs.c 1.31 1998/12/09/19:32:55 (dd9jn+kvh)

eth0: Xircom: port 0x300, irq3, hwaddr 00:80:C7:D3:AD:95
eth0: media 10Base T, silicon revision 1

/etc/pcmcia/config has the following info: device "xirc2ps_cs" class "network" module "xirc2ps_cs"

card "xircom IIps Ethernet" version "Xircom", "*", "PS-CE2-10" bind "xirc2ps_cs"

Typing cardctl ident gives me Socket 0: product info: "Xircom", "CreditCard 10Base-T": "PS-CE2-10", "2.10" manfid: 0x0105, 0x10b function: 6 (network)

Typing cardctl status gives me: Socket 0: 5V 16-bit card present Function 0: ready

Can anyone help? I have no idea what to do . . .

Thanks!

None Some things to try

Re: Question Xircom 2CEps, tecra 8000, and RedHat 6.0
Date: 1999, Dec 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

First the easiest option.  I'll assume that you've configured your
network correctly, and "ifconfig eth0" looks fine (right IP address
and netmask, but shows no packets in or out).  You might just have an
interrupt conflict with some other built-in device.  Start by
excluding interrupts in /etc/pcmcia/config.opts (there are examples),
and see if that helps.  The card is using irq 3 now... exclude that
and reboot, and it will use the next seemingly-free interrupt.  Repeat
until either the card works or you run out of options.

If that doesn't help... then you might benefit from a PCMCIA driver
update.  There are instructions in the HOWTO for upgrading your PCMCIA
package.

-- Dave

None Problem using CEM 56 with new pcmcia-cs-3.1.8

Date: 2000, Jan 11
From: TeeJin TeeJin

I m using IBM 600 with Mandrake 6.1.

Was using CEM 56s working fine until I upgraded the pcmcia package to pcmcia-cs-3.1.8

Some stack error occured while doing a cardctl config.

Network seems fine , Red LEDS running at 100 BTX, I am able to get ifconfig up but modem fails to initialise.

Tried to exclude port 2f8-2ff but no avail. Tried excluding IRQ 3 as well.

THe other thing is previously prior to using the latest pcmcia pacakge I m trying to use 2 CEM 56s to setup an ethernet bridge. The first one eth0 runs at 10 BTX (green leds) while the 2nd eth1 runs at 100 btx (red led)

cardctl config and cat /var/run/stab shows up fine.

Network is fine with the exception of the difference in the line speed.

No such problem while running on a single card.

Any resources that I should exclude or include?

Read about a bug in multifunction cards but do not know if this applies.

Appreciate any help.

TeeJin

None Should be fixed now

Re: None Problem using CEM 56 with new pcmcia-cs-3.1.8 (TeeJin)
Date: 2000, Feb 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Both problems (the cardctl stack error, and the modem problem) should be fixed in the latest PCMCIA release.

-- Dave

Sad REM56G-10BT: problems with the modem half

Date: 2000, Jan 13
From: Jon Sundquist <jsundqui@buffnet.net>

I posted this in the serial message board, too. But since it is a Xircom multifunction, I thought I should put it here, too, since there may be more Xircom experience among readers here.

The ethernet part of my Xircom REM56G-10BT (it is the 16-bit realport card, combo 10BT ether and 56K modem) works great as an ethernet card. It also works in modem mode, but with troubles. I can reproducibly stall a file transfer.

 Setup:
 Dell Inspiron 3500
 Redhat 6.1, with pcmcia upgraded to 3.1.8 (upgrade didn't help)
 Card: Xircom REM56G-10BT

 inspiron:~$ uname -rv
 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999
 inspiron:~$ /sbin/cardctl -V
 cardctl version 3.1.8

More details of problem: I use kppp to initiate a modem ppp connection (a usenet post said that kppp may be a culprit, but that seems unlikely, and I have not yet crafted a straight pppd/chat script to confirm). Connection is made OK (sometimes not at too great a speed, but I chalk that up to poor lines). Things like web surfing are fine.

Now go to this page: http://www.vmware.com/download/downloadtools.html and try to download the vmware-tools package from any of the mirrors there. It always, reproducibly stalls at 5% (at about 77000 - 78000 bytes). It will stall from any of the mirrors, both from ftp and http. Interestingly, although it stalls the same place each time, some packets still come through. I.e., it transfers fine till about 5%, then maybe a packet or two every minute, but gradually getting even slower.

I mainly use the ethernet, so I havaen't done extensive testing for different sites/limitations. However, there were other downloads where I had similar problems (e.g. a TkDesk rpm from RedHat contrib IIRC). However, I have also had some downloads with no problems.

Again, loading web pages seems unaffected. I had some problems (long delays) loading/refreshing an IMAP mailbox, but that has not been quite so reproducible.

This is a dual boot machine. I had no problem downloading these files in windows via modem.

When swicthing between ethernet and modem, I first bring down the eth0 interface (ifconfig down) along with the associated routes.

Script changes: none serial-related. I added the network.opts as recommended for redhat. I also used redhats /etc/pcmcia/network. But then again, I am not having problems with the network, but with the modem/serial.

From the logs: This is from /var/log/messages from after I restarted cardmgr (via /etc/rc.d/init.d/pcmcia stop|start) following the installation of 3.1.8. Note, I first tested ethernet to see if it worked, then brought that down, and ran the ppp session.

Jan 12 18:16:36 inspiron cardmgr[6631]: starting, version is 3.1.8
Jan 12 18:16:36 inspiron cardmgr[6631]: watching 2 sockets
Jan 12 18:16:36 inspiron cardmgr[6631]: initializing socket 0
Jan 12 18:16:36 inspiron cardmgr[6631]: socket 0: Xircom RealPort REM10BT Ethernet/Modem
Jan 12 18:16:36 inspiron cardmgr[6631]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/xirc2ps_cs.o'
Jan 12 18:16:36 inspiron cardmgr[6631]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/serial_cs.o'
Jan 12 18:16:41 inspiron cardmgr[6631]: executing: './network start eth0'
Jan 12 18:16:45 inspiron cardmgr[6631]: executing: './serial start ttyS3'
Jan 12 18:21:50 inspiron modprobe: can't locate module char-major-108
Jan 12 18:21:50 inspiron pppd[6744]: pppd 2.3.10 started by root, uid 0
Jan 12 18:21:50 inspiron pppd[6744]: Using interface ppp0
Jan 12 18:21:50 inspiron pppd[6744]: Connect: ppp0 <--> /dev/ttyS3
Jan 12 18:21:56 inspiron pppd[6744]: Remote message: Login Succeeded
Jan 12 18:21:57 inspiron pppd[6744]: local  IP address 208.28.191.14
Jan 12 18:21:57 inspiron pppd[6744]: remote IP address 208.28.191.2
Jan 12 18:22:27 inspiron pppd[6744]: CCP: timeout sending Config-Requests 
Jan 12 18:28:51 inspiron pppd[6744]: Terminating on signal 15.
Jan 12 18:28:51 inspiron pppd[6744]: Connection terminated.
Jan 12 18:28:51 inspiron pppd[6744]: Connect time 7.1 minutes.
Jan 12 18:28:51 inspiron pppd[6744]: Sent 21300 bytes, received 480012 bytes.
Jan 12 18:28:51 inspiron pppd[6744]: Exit.

Question Problem with Intel EtherExpress 100 (16 bits)

Date: 2000, Jan 16
From: Jean-Francois Gadoury RedStorm

Hello,

I have been trying to get my Intel EtherExpress 100 16 bits card to work for while now without sucess. I would appreciate any ideas of what I could try to resolve my problem

I am Running Redhat v6.1 on a IBM ThinkPad 600e. The tests I have conducted were with version 2.2.12 and 2.2.14 of the linu Kernel. I am using pcmcia 3.0.14 package.

From what I see the pcmcia package is functionning correctly I hear the usual beeps for insertion and removal of cards from the pcmcia sockets. The scripts for initting the Ethernet card functions properly also I have tried the pcmcia default scripts as well as using the modification to conserve the Redhat init mechanism.

When I insert the card I the proper module is loaded xirc2ps_cs.o. I have specifying direct IP related information and have also tried DHCP. If I specify the IP and net info myself the interface eth0 is setup properly and if I ifconfig I get the proper output.

When using DHCP the interface is not mounted and an error is reported in /var/log/messages.

When setting the IP address and net information directly I tried to ping computers on the locl subnet without success I receive Network Unreachable messages. I also notice that the card does not show activity though the dongle leds.

Here is a terminal log of hopefully usefulll information:

#
# Local PCMCIA Configuration File
#
# System resources available for PCMCIA devices
#
# include port 0x100-0x4ff, port 0x1000-0x17ff
include port 0x1000-0x17ff include memory 0xc0000-0xfffff exclude memory 0xa0000000-0xa0ffffff include memory 0x60000000-0x60ffffff

exclude port 0x100-0x4ff

# First built-in serial port exclude irq 4 # Second built-in serial port exclude irq 3 # First built-in parallel port exclude irq 7 #exclude irq 9

[root@localhost /root]# cardctl ident
Socket 0:
  no product info available
Socket 1:
  product info: "Intel", "EtherExpress(TM) PRO/100 PC Card Mobile Adapter16", "PRO/100 M16A", "1.00"
  manfid: 0x0089, 0x010a
  function: 6 (network)
[root@localhost /root]# 

[root@localhost /root]# cardctl config
Socket 0:
  not configured
Socket 1:
  Vcc = 5.0, Vpp1 = 0.0, Vpp2 = 0.0
  Interface type is memory and I/O
  IRQ 9 is exclusive, level mode, enabled
  Function 0:
    Config register base = 0x0800
      Option = 0x41, status = 0000
    I/O window 1: 0x1000 to 0x100f, 16 bit
[root@localhost /root]# 

[root@localhost /root]# tail /var/log/messages

Jan 16 21:08:35 localhost cardmgr[2035]: socket 1: Intel EtherExpress PRO/100
Jan 16 21:08:35 localhost cardmgr[2035]: executing: 'insmod /lib/modules/2.2.14/pcmcia/xirc2ps_cs.o'
Jan 16 21:08:35 localhost kernel: xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh) 
Jan 16 21:08:35 localhost kernel: eth0: Intel: port 0x1000, irq 9, hwaddr 00:A0:C9:BA:20:9D 
Jan 16 21:08:35 localhost cardmgr[2035]: executing: './network start eth0'
Jan 16 21:08:40 localhost kernel: eth0: auto negotation failed; using 10mbs 
Jan 16 21:08:40 localhost kernel: eth0: media 10BaseT, silicon revision 4 
Jan 16 21:09:11 localhost kernel: eth0: media 10BaseT, silicon revision 4 
Jan 16 21:09:41 localhost cardmgr[2035]: + Determining IP information for eth0...Operation failed.
Jan 16 21:09:41 localhost cardmgr[2035]: +  failed.
[root@localhost /root]#

This card has already functioned under linux with Linux v6.0

thanks for any help :-)

alp!

Ok Nevermind 3.1.8 fixes my problems!

Re: Question Problem with Intel EtherExpress 100 (16 bits) (Jean-Francois Gadoury)
Date: 2000, Jan 17
From: Jean-Francois Gadoury RedStorm

v3.1.8 works great!

Question Is RBEM56G 10/100 Ethernet + Modem 56 supported?

Date: 2000, Jan 26
From: Stefan Kluth Stefan

I have:

Laptop Dell Inspiron 3700 450 GT

Xircom RealPort CardBus Ethernet 10/100 * Modem 56, which
identifies itself as  
vers_1 5.0, "Xircom", "CardBus Ethernet 10/100 + Modem 56",
"CBEM56G",  "1.03"
with dump_cis

Debian frozen potato, stock kernel 2.2.13, pcmcia-cs 3.1.8-4

In short, I did not get the ethernet part of the Xircom card
to work, even though the module "tulip_cb" got loaded ok and
no other obvious messages appeared. If this card is supposed
to work with the software I have I can of course provide more
info.

I succeeded by getting "tulip.c" from 
http://ivs.cs.uni-magdeburg.de/~danilo/linux.shtml (follow the
link "driver" in section IBM EtherJet PC Card Driver),
replacing clients/tulip_cb.c by the new code and
compiling/installing pcmcia-cs. I also pass the two options
"cis_hwaddr=0x170 strict_csr6=1" via /etc/pcmcia/config.ops to
the tulip_cb module. Note that these options are not available
in the standard tulip_cb.c

After reading the relevant postings here I fear that I am
doing something silly and that the card should work. 

I will be grateful for any hints/help. Stefan

None Depends on what you mean by "supported"

Re: Question Is RBEM56G 10/100 Ethernet + Modem 56 supported? (Stefan Kluth)
Date: 2000, Jan 26
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The card is listed in the SUPPORTED.CARDS file as "not recommended:
support is experimental and unreliable".  It seems to work for some
people but not others.

Does the modem part work?

> I succeeded by getting "tulip.c" from 
> http://ivs.cs.uni-magdeburg.de/~danilo/linux.shtml

This tulip driver is OLDER than the code in the 3.1.8 PCMCIA driver
package.  The options that are missing in the standard tulip_cb.c file
are missing because they are no longer needed.

Reinstall the 3.1.8 tulip driver, then post more details (type of
laptop, system log messages) if the problem persists.

-- Dave

Ok ethernet works with workaround

Re: None Depends on what you mean by "supported" (David Hinds)
Date: 2000, Jan 27
From: Stefan Kluth Stefan

After posting the message I realised that a workaround
was already posted in this newsgroup. I reinstalled pcmcia
3.1.8 and then I first tried

ifconfig eth0 promisc

which succeeded in getting the network working. Of course,
I didn't understand at all why "promisc" should be important.
Following another posting I tried

ifconfig eth0 down up

and this also does the trick. I added this line in
/etc/pcmcia/network right after 

/sbin/ifconfig $DEVICE up $IPADDR netmask $NETMASK $BC

Somehow a simple restart is enough to get the card working. 

I havn't tried the modem yet. If somebody tells me how to
collect statistics on network connections I could try to find
out how well the driver works. 

More I tried this on my Inspiron 7500 running RH 6.1 and CBEM56G

Re: Ok ethernet works with workaround (Stefan Kluth)
Date: 2000, Jan 31
From: Charlie Zender zender

I am having the problem where the CBEM56G and PCMCIA 3.1.19
are almost, but not quite, working.
The modem appears to work fine without any tweaks needed.
The ethernet card works but only after restarting some 
daemons.
When linuxconf issues the commands

/etc/rc.d/rc3.d/S10network reload and
/etc/rc.d/rc3.d/S50inet restart

then the ethernet card works, so also it appears to me
that the CBEM56G simply needs some daemon to be restarted
and it will work with RH6.1 on the inspiron 7500.
So I tried Stefan's suggestion, adding

/sbin/ifconfig eth0 down up 

right after the specified location but it did not get 
the card working. I still have to go into linuxconf
to get the system to issue the above commands to get
it working. 

There are no error messages in /var/log/messages, tulip_cb
seems to be setting up fine. But I am way out of my league
here, is there an easier way to trigger the restart of
the network and inet daemons than using linuxconf?
Something I could just add to the rc* script?
Is there something else I should try in /etc/pcmcia/network?

Thanks,
Charlie

None See the HOWTO...

Re: More I tried this on my Inspiron 7500 running RH 6.1 and CBEM56G (Charlie Zender)
Date: 2000, Jan 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The PCMCIA-HOWTO has a section that discusses different Linux
distributions.  See the section about Red Hat, and the comments about
the Red Hat network configuration scripts.

-- Dave

More OK, it works now

Re: None See the HOWTO... (David Hinds)
Date: 2000, Jan 31
From: Charlie Zender zender

Thanks David, for all your work and your quick response.

p. 12 of the PCMCIA HOWTO does show how to get the CBEM56G 
to work on system startup. I replaced the pcmcia-3.1.19 default /etc/pcmcia/network.opts with the Redhat-specific
version on this page, and now the card works
on powerup without requiring any additional tweaks.

The suspend/resume behavior is still not optimal.
I must eject the card before resuming in for it to 
resume properly. If I do not physically eject the
card before resuming, then I get the error:

cs: socket 0 timed out during reset

Trying to do a software resume at this point with 
'cardctl resume' yields the error 

ioctl(): Device or resource busy

I get the same error when I use 'cardctl eject' before
physically ejecting the card. Fortunately,
I have found that physically ejecting then reinserting
the card in such situations does work without first issuing
the command 'cardctl eject'. However, I am not sure this
is safe!

Any ideas on fixes to this suspend/resume behavior?

None Both issues are tricky

Re: More OK, it works now (Charlie Zender)
Date: 2000, Jan 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I've tried to make the tulip driver hot-eject-safe, however it is hard
to anticipate all possible failure modes.  In general it is more wise
to do "cardctl eject" or at least "ifconfig down" the interface first.

There is no fix for the suspend/resume problem at this time.  The
issue is that the resume code in the tulip driver needs to do a full
reset of the card, and the tulip initialization code is sufficiently
baroque that I've had a tough time rearranging the driver to make this
work.

-- Dave

Question Xircom CEM-56-100, Linux 2.3.42, pcmcia-cs 3.1.10

Date: 2000, Feb 08
From: Ian G Batten igb

I've just tried moving from 2.2.11-ac3 + pcmcia-cs-3.0.14
to 2.3.42 + pcmcia-cs-3.1.10.  My hardware is a Fujitsu
B110 laptop, plus a Xircom CEM-56-100 combo card.  After the
upgrade, the pcmcia initialisation reports

xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh)
xirc2ps_cs: MapMemPage: Bad handle

and the ethernet is inoperative.  I have answered `m'
to PCMCIA support in the kernel, and likewise for the cards
I need.  I am now trying it without the modules from the
kernel distribvution.

ian

Question Kernel oops when ejecting CBEM56G

Date: 2000, Feb 09
From: Eyvind Bernhardsen eyvind

I just upgraded to pcmcia-cs 3.1.9 (precompiled Debian "woody" version), which has fixed earlier problems I had with pcmcia, but which Oopses whenever the card is ejected, cardctl eject is called, or the system shuts down/reboots.

I'm not sure if I had this problem before, since I was pretty much happy to have the card _not_ lock the system solid (which it frequently did with pcmcia-cs 3.1.8), and didn't bother to check the kernel logs much once things were up and running :)

The system is a Dell Latitude CPtV466GT running Debian "potato" (aka "frozen") with kernel 2.2.14 plus the ext3 patch, the international kernel patch, and the 2.3.39 USB backport.

The output of ksymoops is as follows:

ksymoops 2.3.3 on i686 2.2.14ext3.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.2.14ext3/ (default)
     -m /boot/System.map-2.2.14ext3 (specified)

Unable to handle kernel paging request at virtual address 5a5a5ab6
current->tss.cr3 = 06f90000, %cr3 = 06f90000
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c80575f2>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010206
eax: 5a5a5a5a   ebx: c0233800   ecx: 5a5a5a5a   edx: c80599fc
esi: c80599fc   edi: c8052000   ebp: c6f8ff3c   esp: c6f8ff2c
ds: 0018   es: 0018   ss: 0018
Process rmmod (pid: 584, process nr: 36, stackpage=c6f8f000)
Stack: 00004000 c7e11ee0 0000000c c011ba98 c6f8ff6c c805790e c8059be8 00000000
       c6fbb150 c0116d73 c8052000 fffffff0 c7144180 08054006 00000000 c6f8e000
       bfffecac c0117130 c8052000 fffffff0 c6f8ffb0 bfffecac c4b77000 fffffffe
Call Trace: [<c011ba98>] [<c805790e>] [<c8059be8>] [<c0116d73>] [<c8052000>] [<c0117130>] [<c8052000>]
       [<c0116775>] [<c8052000>] [<c0116737>] [<c010a041>] [<c0109f3c>]
Code: 8b 59 5c 8d 53 0c 8a 83 72 05 00 00 24 03 3c 02 75 29 83 c4

>>EIP; c80575f2 <[tulip_cb]tulip_reap+2e/78>   <=====
Trace; c011ba98 <handle_mm_fault+c8/13c>
Trace; c805790e <[tulip_cb]cleanup_module+1a/84>
Trace; c8059be8 <[tulip_cb]tulip_ops+0/13>
Trace; c0116d73 <qm_info+9f/b8>
Trace; c8052000 <[tulip_cb]__module_kernel_version+0/1a>
Trace; c0117130 <free_module+20/a8>
Trace; c8052000 <[tulip_cb]__module_kernel_version+0/1a>
Trace; c0116775 <sys_delete_module+13d/1ec>
Trace; c8052000 <[tulip_cb]__module_kernel_version+0/1a>
Trace; c0116737 <sys_delete_module+ff/1ec>
Trace; c010a041 <error_code+2d/34>
Trace; c0109f3c <system_call+34/38>
Code;  c80575f2 <[tulip_cb]tulip_reap+2e/78>
00000000 <_EIP>:
Code;  c80575f2 <[tulip_cb]tulip_reap+2e/78>   <=====
   0:   8b 59 5c                  mov    0x5c(%ecx),%ebx   <=====
Code;  c80575f5 <[tulip_cb]tulip_reap+31/78>
   3:   8d 53 0c                  lea    0xc(%ebx),%edx
Code;  c80575f8 <[tulip_cb]tulip_reap+34/78>
   6:   8a 83 72 05 00 00         mov    0x572(%ebx),%al
Code;  c80575fe <[tulip_cb]tulip_reap+3a/78>
   c:   24 03                     and    $0x3,%al
Code;  c8057600 <[tulip_cb]tulip_reap+3c/78>
   e:   3c 02                     cmp    $0x2,%al
Code;  c8057602 <[tulip_cb]tulip_reap+3e/78>
  10:   75 29                     jne    3b <_EIP+0x3b> c805762d <[tulip_cb]tulip_reap+69/78>
Code;  c8057604 <[tulip_cb]tulip_reap+40/78>
  12:   83 c4 00                  add    $0x0,%esp

I've managed to parse the disassembled output enough to figure out that the kernel oopses in tulip_reap() while trying to dereference (*devp)->priv on line 3459 of tulip_cb.c, which might mean that root_tulip_dev is invalid, but I don't know how to debug the kernel so I can't find out :) What I _do_ know is that tulip_reap is called twice; once while loading the module, and once while cleaning up after it (I get the "tulip_reap()" message twice in my kernel log). The first invocation works fine, obviously.

Since I don't usually eject the network card once I've inserted it this isn't really a big deal for me, but I'd be happy to provide my configuration, log messages etc. if anyone wants to take a harder look at it.

None Ok, I think I found the problem

Re: Question Kernel oops when ejecting CBEM56G (Eyvind Bernhardsen)
Date: 2000, Feb 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Try today's beta (09-Feb-00) on sourceforge.org in /pub/pcmcia/NEW.

I think the problem only shows up on 2.2.14 kernels, thanks to a
kernel change meant to catch memory allocation errors.

-- Dave

Sad Possibly, but...

Re: None Ok, I think I found the problem (David Hinds)
Date: 2000, Feb 10
From: Eyvind Bernhardsen eyvind

Thanks for the quick response, but the new version doesn't even appear to recognize my card. I got the beta release, configured it with

 ./Configure -n --kernel=/usr/src/linux --srctree --cardbus

(stolen from the Debian source package's build target to try to get the same configuration), ran "make all", and installed all the files and modules. This is the kernel boot log with the card inserted:

Feb 10 09:15:47 helt kernel: Linux PCMCIA Card Services 3.1.11
Feb 10 09:15:47 helt kernel:   kernel build: 2.2.14ext3+supermount unknown
Feb 10 09:15:47 helt kernel:   options:  [pci] [cardbus] [apm]
Feb 10 09:15:47 helt kernel: PCI routing table version 1.0 at 0xfbd70
Feb 10 09:15:47 helt kernel:   00:03.0 -> irq 11
Feb 10 09:15:47 helt kernel:   00:03.1 -> irq 11
Feb 10 09:15:47 helt kernel: Intel PCIC probe:
Feb 10 09:15:47 helt kernel:   TI 1225 PCI-to-CardBus at slot 00:03, mem 0x68000000
Feb 10 09:15:47 helt kernel:     host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 32/32] [bus 0/2]
Feb 10 09:15:47 helt kernel:     host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat 32/32] [bus 3/5]
Feb 10 09:15:47 helt kernel:     ISA irqs (scanned) = 3,4,7,9,10 PCI status changes
Feb 10 09:15:47 helt kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
Feb 10 09:15:47 helt kernel: cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x84f
Feb 10 09:15:47 helt kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x4d0-0x4d7
Feb 10 09:15:47 helt kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Feb 10 09:15:48 helt kernel: cs: cb_alloc(bus 0): vendor 0x8086, device 0x7190

When the card is ejected I get a cb_free(bus 0) in the log, and when it is reinserted I get another cb_alloc(bus 0).

For comparison, this is the kernel log when the card is recognized (with the 3.1.9 pcmcia-cs and modules):

Feb 10 07:42:10 helt kernel: Linux PCMCIA Card Services 3.1.9
Feb 10 07:42:10 helt kernel:   kernel build: 2.2.14ext3+supermount unknown
Feb 10 07:42:10 helt kernel:   options:  [pci] [cardbus] [apm]
Feb 10 07:42:10 helt kernel: PCI routing table version 1.0 at 0xfbd70
Feb 10 07:42:10 helt kernel:   00:03.0 -> irq 11
Feb 10 07:42:10 helt kernel:   00:03.1 -> irq 11
Feb 10 07:42:10 helt kernel: Intel PCIC probe:
Feb 10 07:42:10 helt kernel:   TI 1225 PCI-to-CardBus at slot 00:03, mem 0x68000000
Feb 10 07:42:10 helt kernel:     host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 32/32] [bus 32/34]
Feb 10 07:42:10 helt kernel:     host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat 32/32] [bus 35/37]
Feb 10 07:42:10 helt kernel:     ISA irqs (scanned) = 3,4,7,9,10 PCI status changes
Feb 10 07:42:10 helt kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
Feb 10 07:42:10 helt kernel: cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x84f
Feb 10 07:42:10 helt kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x4d0-0x4d7
Feb 10 07:42:10 helt kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Feb 10 07:42:10 helt kernel: cs: cb_alloc(bus 32): vendor 0x115d, device 0x0003
Feb 10 07:42:10 helt kernel: ROM image dump:
Feb 10 07:42:10 helt kernel:   image 0: 0x000000-0x0001ff, signature PCIR
Feb 10 07:42:11 helt kernel: cs: cb_config(bus 32)
Feb 10 07:42:11 helt kernel:   fn 0 bar 2: mem 0x60013000-0x600137ff
Feb 10 07:42:11 helt kernel:   fn 0 bar 3: mem 0x60012000-0x600127ff
Feb 10 07:42:11 helt kernel:   fn 1 bar 1: io 0x480-0x487
Feb 10 07:42:11 helt kernel:   fn 1 bar 2: mem 0x60011000-0x600117ff
Feb 10 07:42:11 helt kernel:   fn 1 bar 3: mem 0x60010000-0x600107ff
Feb 10 07:42:11 helt kernel:   fn 0 bar 1: io 0x400-0x47f
Feb 10 07:42:11 helt kernel:   fn 0 rom: mem 0x6000c000-0x6000ffff
Feb 10 07:42:11 helt kernel:   fn 1 rom: mem 0x60008000-0x6000bfff
Feb 10 07:42:11 helt kernel: cs: cb_enable(bus 32)
Feb 10 07:42:11 helt kernel:   bridge io map 0 (flags 0x21): 0x400-0x487
Feb 10 07:42:11 helt kernel:   bridge mem map 0 (flags 0x1): 0x60008000-0x60013fff
Feb 10 07:42:11 helt kernel: tulip_reap()
Feb 10 07:42:11 helt kernel: tulip_attach(bus 32, function 0)
Feb 10 07:42:11 helt kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Feb 10 07:42:11 helt kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x400, 00:10:A4:E9:3C:E5, IRQ 11.
Feb 10 07:42:11 helt kernel: eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1.
Feb 10 07:42:11 helt kernel: serial_attach(bus 32, fn 1)
Feb 10 07:42:11 helt kernel: tty02 at 0x0480 (irq = 11) is a 16550A

Note the host opts "bus" parameter, and of course the cb_alloc. (Isn't 0x8086 Intel's vendor code?).

Additionally, the new modules really disliked being unloaded; I got something like two kernel aiees (no scrollback, so I could only see the last one) and a solid lock when I tried to stop cardmgr to downgrade to the old version.

Once I had restored the old userland utilities, I tried starting pcmcia with the new modules. The card still wasn't recognized, but I couldn't reproduce the crash.

Ok Yes!

Re: Sad Possibly, but... (Eyvind Bernhardsen)
Date: 2000, Feb 11
From: Eyvind Bernhardsen eyvind

The 09-Feb-00 beta was a non-starter, but the 10-Feb-00 beta works! cardctl eject beeps twice (not sure if this is normal, but it turned off the ethernet :), and reinserting the card brings everything back again. Multitudinous thanks to Dave, both for maintaining pcmcia-cs and (of course) for fixing the bug.

Question CBEM56M at irq10/port1480 "modem is busy"... HELP!

Date: 2000, Feb 09
From: Albert S. Johnston sofeise

I hava a Micron Transport Trek running R.H. 6.1; It has a xircom CBEM56G pcmcia card. Under win97 the modem part is at irq10/port1480-1487 and e/net part is at irq10/port1400-147F.

I have added the suguested PCIC_OPTS line to my /etc/sysconfig/pcmcia file (PCIC_OPTS="do_scan=0 irq_list=10) and modified the /etc/pcmcia/config.opts file so that only ports 0x1400-0x1500 are "included". The stuff in the boot log looks fine... stab file says there is a network/tulip_cb at eth0 and a serial/serial_cb at ttyS2

cardctl config says socket 1/fun 1 is 0x1400-0x1487 and socket 1/fun 2 is 0x1400-0x1487

So every thing is ok, right? well neither kppp or minicom are able to access the card. In them ttyS1 is okay (i think) but all the other ttyS's say things like "sorry, the modem is busy"...

I know a bunch of you have this working.... what am is doing wrong?

tnx

None Try a PCMCIA upgrade

Re: Question CBEM56M at irq10/port1480 "modem is busy"... HELP! (Albert S. Johnston)
Date: 2000, Feb 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'd suggest upgrading to the 3.1.10 PCMCIA drivers.  I think the modem
problem is a symptom of a bug in the kernel serial driver; there is a
workaround in the current PCMCIA package.

-- Dave

Ok SUCCESS!!!

Re: None Try a PCMCIA upgrade (David Hinds)
Date: 2000, Feb 10
From: Albert S. Johnston sofeise

David H's suggestion did the trick. Thanks!

Question RBEM56G-100BTX Ethernet working; modem not recognized

Date: 2000, Feb 10
From: RJ Johnston rjohnston

All, running pcmcia 3.1.9 and 2.2.12 with RedHat6.1 and the
 RBEM56G-100BTX, and after installing 3.1.9 the ethernet 
worked perfectly. Unfortunately, the modem doesn't work at 
all. Not only doesn't it work, but Kudzu comes up and says 
that the "Generic Serial Modem," and Ethernet Adapter have 
been removed from the system when I don't have the card 
connected to the LAN. Any ideas for what I might be doing 
wrong? Anyone got a lead but I haven't supplied the right 
information, by all means let me know!

None Its RBEM56G-100, sorry... also more details

Re: Question RBEM56G-100BTX Ethernet working; modem not recognized (RJ Johnston)
Date: 2000, Feb 10
From: RJ Johnston rjohnston

I incorrectly identified my Xircom card. It is, in fact, an
 RBEM56-100. Also, when I start my machine, it beeps twice at
 the same pitch in an indication that everything has started
 correctly. The modem settings (by doing a setserial -a)
 appear to be correct. It just isn't working properly. I have
 tried to set it to polling mode and then back to its assigned
 interrupt, then I have tried changing the port to match the
 one shown by cardctl config. Neither seems to do anything.
 Any suggestions are appreciated!

None Added Log Messages

Re: Question RBEM56G-100BTX Ethernet working; modem not recognized (RJ Johnston)
Date: 2000, Feb 10
From: RJ Johnston rjohnston

Below is the stab file located in var/state/pcmcia:

Socket 0: empty
Socket 1: Xircom CardBus 10/100 Ethernet + 56K Modem
1 network tulip_cb 0 eth0
1 serial serial_cb 0 ttyS1 4 65

Below is the system log:

Feb 10 09:53:11 localhost syslog: syslogd startup succeeded
Feb 10 09:53:11 localhost syslog: klogd startup succeeded
Feb 10 09:53:12 localhost atd: atd startup succeeded
Feb 10 09:53:12 localhost crond: crond startup succeeded
Feb 10 09:53:13 localhost pcmcia: Starting PCMCIA services:
Feb 10 09:53:13 localhost pcmcia: modules
Feb 10 09:53:13 localhost pcmcia: cardmgr.
Feb 10 09:53:13 localhost rc: Starting pcmcia succeeded
Feb 10 09:53:13 localhost inet: inetd startup succeeded
Feb 10 09:53:14 localhost lpd: lpd startup succeeded
Feb 10 09:53:14 localhost keytable: Loading keymap:
Feb 10 09:53:14 localhost keytable: Loading /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
Feb 10 09:53:15 localhost keytable: Loading system font:
Feb 10 09:53:15 localhost rc: Starting keytable succeeded
Feb 10 09:53:16 localhost sendmail: sendmail startup succeeded
Feb 10 09:53:17 localhost gpm: gpm startup succeeded
Feb 10 09:53:17 localhost xfs: xfs startup succeeded
Feb 10 09:53:18 localhost linuxconf: Linuxconf final setup
Feb 10 09:53:21 localhost rc: Starting linuxconf succeeded

Below is the output of cardctl config:

Socket 0:
  not configured
Socket 1:
  Vcc 3.3V Vpp1 3.3V Vpp2 3.3V
  interface type is "cardbus"
  irq 3 [exclusive] [level]
  function 0:
    io 0x0a00-0x0a87 [32bit]
  function 1:
    io 0x0a00-0x0a87 [32bit]

And finally, below is the output of setserial -a /dev/ttyS1:

/dev/ttyS1, Line 1, UART: 16550A, Port: 0x0a80, IRQ: 3
  Baud_base: 115200, close_delay: 50, divisor: 0
  closing_wait: 3000, closing_wait2: infinte
  Flags: spd_normal skip_testlink

David, Please let me know if there is anything else you need.
By the way, after reading Albert's post above, I am thinking
that my problem may be similar. I am in the process of
compiling 3.1.10 right now. Thanks again for any help you may
be able to provide.

Question CE IIps Problems, Can anybody help ??

Date: 2000, Feb 10
From: Anton Enright <enright@ebi.ac.uk>

I'm trying to get this bloody Xircom CEIIps card working, the only O/S that accepts it so far is Windows 2000 :)

When the pcmcia module cardmgr starts it reports:

xirc2ps_cs: unknown card (mediaid=01 prodid=ff)

Here's the versions I am running... pcmcia-cs => 3.1.10 kernel => 2.0.36-0.7

I've tried hacking the xirc2ps.c file to convince it that this is a CE2 card, but to no avail..

Anyone Help Me here ???

Thanks

Anton

Ok Problem Resolved...(I think ?)

Re: Question CE IIps Problems, Can anybody help ?? (Anton Enright)
Date: 2000, Feb 10
From: Anton Enright <enright@ebi.ac.uk>

Hmmm,

I've got it working now,

I've hardcode the Card Type in the set_card_type routine of xirc2ps_cs.c.

From: local->card_type = XIR_UNKNOWN;

To: local->card_type = XIR_CE2;

So that it defaults to CE2 when it can't workout the card-type...

Networking is fine, but weirdly, If I remove the card, and reinsert it, it is no-longer able to identify the card...

Anyway, I'm happy now, (I can go and FTP down RedHat 6.1)..

Anton

Question ISDN problems CEM

Date: 2000, Feb 12
From: J.P jeepee

Hello,

Today I updated from 3.1.8 to 3.1.10 after the upgrade all was oke except my ISDN speed there is no 64K anymore but just about 14.4 its realy slow even after updating the wvdial to 1.41 it still is the same. Only option I had was going back to 3.1.8 that works oke and gives me the full 64K.

Any ideas about this or how to fix it.

I am running a NEC Versa LX with a Xircom CEM-56 card (10/100 ISDN and 56K analog) Linux 2.2.13 Slackware

Regards J.P.....

None The usual questions

Re: Question ISDN problems CEM (J.P)
Date: 2000, Feb 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Can you compare PCMCIA system log messages from then and now?

-- Dave

Note Fixed now, apparently

Re: Question ISDN problems CEM (J.P)
Date: 2000, Feb 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'm not sure why, but the problem is fixed in 3.1.11.

-- Dave

Question Problem with Xircom RE-100 on RH6.1

Date: 2000, Feb 20
From: Aaron Parks aparks

Hi. I just got a new laptop (CTX 700G) and installed a clean copy of RH6.1 on it. I'm having trouble with my RE-100, which worked in my old laptop (a thinkpad running RH5.2).

First of all, I did have some problems probing interrupts, the probe would only find IRQ 4, which was in use anyway. I set PCIC_OPTS="irq_list=5,9 do_scan=0" and IRQ 5 was correctly allocated to the RE-100. IO address 0x300 was also allocated to it. The link light comes up green and autonegotiation is fine (10Mb). when i try to ping another host, the packets are lost. ifconfig shows that the TX and RX counters on the RE-100 (eth0) stay zeroed, but the TX and RX on lo increase.

kernel is 2.2.12-20 and pcmcia 3.0.14

anyone have a clue i could borrow?

thanks.

Aaron Parks

None Try a driver upgrade

Re: Question Problem with Xircom RE-100 on RH6.1 (Aaron Parks)
Date: 2000, Feb 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Are you sure that irq 5 is genuinely free?  (and not just happens to
be free at the moment: have you accounted for all your devices,
including your sound card?)

My first suggestion would be to try upgrading to the latest PCMCIA
package, which is currently 3.1.11, on the chance it is something that
has already been fixed.  Then if the problem persists, post the system
log messages you get.

-- Dave

Question network not starting automatically?

Date: 2000, Feb 24
From: Albert S. Johnston sofeise

I am running RH 6.1 using D.H's wonderful pcmcia driver. My laptop boots fine. the only "strange" msg's during boot are the "normal" FAILED for pcmcia and a "cant yp_bind/domain not bound" error when "listentin for NIS domain server". I understand that the first msg is as expected; the second one seems like a problem to me.

But when I log in I get "network unreachable"; if i then
run netconfig with args of
  137.244.203.219
  255.255.255.0
  137.244.203.3
  137.244.203.6
then the net is fine until I reboot.

I tried manually setting the above values in the /etc/pcmcia/network.opts file but the results were very simalar... including the "cant yp_bind" error during boot. Instead of a "network unreachible" msg from the ping, i get a "no route to host"... which makes it sound like I put the wrong value into the network.opts file... but I compaired it to the value i gave netconfig() and they were both the same (.3)...

Ideas? thanks

None The HOWTO has some comments about Red Hat

Re: Question network not starting automatically? (Albert S. Johnston)
Date: 2000, Feb 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If you are using a stock Red Hat setup, you should use netconf to
configure the interface.  As mentioned in the HOWTO, network.opts is
not recognized by Red Hat's version of the PCMCIA network script.
After booting, check your system log, and the output of ifconfig and
route, to see what was done.  Or see if "ifup eth0" works.

-- Dave

Sad Untitled

Re: None The HOWTO has some comments about Red Hat (David Hinds)
Date: 2000, Feb 24
From: Albert S. Johnston sofeise

I read the note on RH in the howto... "your driver" was installed "last" so the hook between linuxconfig and the normal linux stuff is broken... which is fine with me...

nothing abnormal in the boot log... just a couple of complaints about not being yp_bind'd... no surpize there since it cant find the nis server at this point.

ifconfig says

eth0 Link encap:Ethernet HWaddr 00:10:A4:E0:2B:87 inet addr:137.244.203.219 Bcast:137.244.203.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:27 errors:0 dropped:0 overruns:0 frame:0 TX packets:31 errors:2 dropped:0 overruns:0 carrier:2 collisions:0 txqueuelen:100 Interrupt:11 Base address:0x200

which seems fine to me.

ping says

[root@lysbd-laptop log]# ping 137.244.203.6 PING 137.244.203.6 (137.244.203.6) from 137.244.203.219 : 56(84) bytes of data. From lysbd-laptop.sofcsi.robins.af.mil (137.244.203.219): Destination Host Unreachable From lysbd-laptop.sofcsi.robins.af.mil (137.244.203.219):

I did a route but did not get its o/put captured (i am having to write this in win95)... but it listed 137.244.203.0 which I am not sure is correct. when I run netconfig() I give it 137.244.203.3 as a "gateway"... but since my ip 219 box is on the same side of the gateway as is the ip 6 box, this shouldnt matter... should it?

None What card is this, by the way?

Re: Sad Untitled (Albert S. Johnston)
Date: 2000, Feb 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

What happens if you do:

  ifdown eth0
  ifup eth0

Does the network start working then?  You also didn't actually say
what card you're using.  I've heard of some weird problems like this
with the Xircom CardBus cards but they are generally so troublesome
that it is hard to make any sense out of the bug reports.

-- Dave

None Untitled

Re: None What card is this, by the way? (David Hinds)
Date: 2000, Feb 24
From: Albert S. Johnston sofeise

re what card:

its a xircom rbgm56g... you helped me get this working a couple of weeks ago. I really expect this problem to be in the class of "dumb user doesnt now know what he's doing".

sorry, I forgot to run the ifdown/up the first time you ask.. first here is the result of a route()

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 137.244.203.0 * 255.255.255.0 U 0 0 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo

strangly enough when I did the ifdown eth0/ifup eth0 the route command showed a NEW entry: Destination Gateway Genmask Flags Metric Ref Use Iface 137.244.203.219 * 255.255.255.255 UH 0 0 0 eth0 137.244.203.0 * 255.255.255.0 U 0 0 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo YPBINDPROC_DOMAIN: Domain not bound

and now my pings resolve fine... the new line seems rather silly to me... as 137.244.203.219 is the ip of MY laptop...

Or is this just one of thoes things I am supposed to know about?

tnx

Sad Still need help!

Re: None The HOWTO has some comments about Red Hat (David Hinds)
Date: 2000, Feb 25
From: Albert S. Johnston sofeise

I am still looking for help on this one. I tried using "route add -host" to add the entry that was missing (my ip and 255.255.255.255 netmask) but route says this is not a legal netmask..

HELP!

tnx

Ok success!

Re: None The HOWTO has some comments about Red Hat (David Hinds)
Date: 2000, Feb 25
From: Albert S. Johnston sofeise

well, I got it working now. The pcmcia howto in sec 2.5.2 seems to say that "things" (the network) will work under redhat without doing creating the network.opts file. This section also seems to be indicating that the file will not exsists prior to this time. Since the file did exist, and had a @$#% of a lot of network related stuff in it already, i had no idea what would happen if I blew the RH6.1 version of the file away and tried using just the lines supplied in the pcmcia howto. I never could get this to work correctly.

Out of dispration I finally removed the old version of the file and created a new one with just the lines from the howto in it...

now everything works. I have no idea why...

Note to D. Hinds: You might want to add some wording to the howto... since it doesnt look like "i dont care about the redhat tools" method discribed in 2.5.2 will work.

-al

None HOWTO explanation

Re: Ok success! (Albert S. Johnston)
Date: 2000, Feb 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On a stock RH6.1 system, there is no network.opts file. That file was put there when you upgraded your PCMCIA drivers.

The standard PCMCIA network setup stuff does work, and it is fairly widely tested. I don't know specifically why it did not initialize your network correctly. If you want, send me the network.opts file you were using and I'll look for anything unusual.

I'll look at the wording in the HOWTO and make sure it is accurate.

-- Dave

Question Dell I7500 with Xircom CBEM56G-100 - odd problem

Date: 2000, Feb 25
From: Jakob Frandsen jakobf

I watched this forum before posting this because I don't know
what else to do.

I'm using pcmcia-cs 3.1.11 and kernel 2.2.12-20 (RH 6.1)

After inserting the card, it beeps twice, logs no bad things,
ifconfig shows eth0 just fine, route shows the route just
fine, the light on the adapter does not come on showing "link
integrity". As soon as I try to ping somebody on my net, it
goes "Destination host unreachable" which is a weird error
considering that I route to the net. Running ifconfig after
this attempt shows that some "error packets" has been sent.

It's on IRQ 11 eventhough I have excluded that
in /etc/pcmcia/config.opts

I have tried to do the "ifdown eth0 ; ifup eth0" trick, but
that does not work for me.

Here are the details:

% tail -n 23 /var/log/messages
Feb 25 10:00:00 localhost kernel: cs: cb_alloc(bus 35): vendor 0x115d, device 0x0003
Feb 25 10:00:00 localhost cardmgr[371]: initializing socket 1
Feb 25 10:00:00 localhost cardmgr[371]: socket 1: Xircom CardBus 10/100 Ethernet + 56K Modem
Feb 25 10:00:00 localhost cardmgr[371]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/cb_enabler.o'
Feb 25 10:00:00 localhost cardmgr[371]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/tulip_cb.o'
Feb 25 10:00:00 localhost cardmgr[371]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/serial_cb.o'
Feb 25 10:00:00 localhost kernel: cs: cb_config(bus 35) 
Feb 25 10:00:00 localhost kernel:   fn 0 bar 2: mem 0x60013000-0x600137ff 
Feb 25 10:00:00 localhost kernel:   fn 0 bar 3: mem 0x60012000-0x600127ff 
Feb 25 10:00:00 localhost kernel:   fn 1 bar 1: io 0x280-0x287 
Feb 25 10:00:00 localhost kernel:   fn 1 bar 2: mem 0x60011000-0x600117ff 
Feb 25 10:00:00 localhost kernel:   fn 1 bar 3: mem 0x60010000-0x600107ff 
Feb 25 10:00:00 localhost kernel:   fn 0 bar 1: io 0x200-0x27f 
Feb 25 10:00:00 localhost kernel:   fn 0 rom: mem 0x6000c000-0x6000ffff 
Feb 25 10:00:00 localhost kernel:   fn 1 rom: mem 0x60008000-0x6000bfff 
Feb 25 10:00:00 localhost kernel: tulip_attach(bus 35, function 0) 
Feb 25 10:00:00 localhost kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford) 
Feb 25 10:00:00 localhost kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x200, 00:10:A4:DF:E1:E4, IRQ 11. 
Feb 25 10:00:00 localhost kernel: eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1. 
Feb 25 10:00:00 localhost kernel: serial_attach(bus 35, fn 1) 
Feb 25 10:00:00 localhost kernel: tty01 at 0x0280 (irq = 11) is a 16550A 
Feb 25 10:00:00 localhost cardmgr[371]: executing: './network start eth0'
Feb 25 10:00:01 localhost cardmgr[371]: executing: './serial start ttyS1'

% ifconfig eth0

eth0      Link encap:Ethernet  HWaddr 00:10:A4:DF:E1:E4  
          inet addr:192.168.168.5  Bcast:192.168.168.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:11 Base address:0x200 

% route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.168.5   0.0.0.0         255.255.255.255 UH    0      0        0 eth0
192.168.168.0   0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo

% ping 192.168.168.10

PING 192.168.168.10 (192.168.168.10) from 192.168.168.5 : 56(84) bytes of data.
From 192.168.168.5: Destination Host Unreachable
From 192.168.168.5: Destination Host Unreachable
From 192.168.168.5: Destination Host Unreachable

--- 192.168.168.10 ping statistics ---
4 packets transmitted, 0 packets received, +3 errors, 100% packet loss

% ifconfig eth0

eth0      Link encap:Ethernet  HWaddr 00:10:A4:DF:E1:E4  
          inet addr:192.168.168.5  Bcast:192.168.168.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:6 dropped:0 overruns:0 carrier:6
          collisions:0 txqueuelen:100 
          Interrupt:11 Base address:0x200 


I can post more info if needed. Thank you is advance.

None Re: Question: Dell I7500 with Xircom CBEM56G-100 - odd problem

Re: Question Dell I7500 with Xircom CBEM56G-100 - odd problem (Jakob Frandsen)
Date: 2000, Feb 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If you look at /proc/interrupts, do you see the counter go up when you
try to send packets?

"Destination host unreachable" isn't a routing error; it means that
the packets couldn't be delivered for some reason.

The card is being assigned to a PCI interrupt, which is why you can't
override it by fiddling with config.opts.  You could put:

    PCIC_OPTS="pci_int=0"

in /etc/sysconfig/pcmcia, to force the driver to use an ISA interrupt
instead.

Just checking: you're using a real network cable, right?  Not a piece
of phone cord?  I'm asking because I've had maybe five bug reports in
the past two weeks, that turned out to be from people using old phone
cords or home-made cables.

-- Dave

Ok It works now - stupid faulty cable. :(

Re: None Re: Question: Dell I7500 with Xircom CBEM56G-100 - odd problem (David Hinds)
Date: 2000, Feb 28
From: Jakob Frandsen jakobf

I learned a lesson: never assume a new cable fresh from an unopened plasticbag actually works! :)

Anyway, it works now, with another cable. Thank you very much for your assistance though.

Question IBM PCMCIA Etherjet 10/100... lord help me.

Date: 2000, Feb 28
From: GarrettSerack gserack

Ok.

[gulp!]

I'm attempting to install linux (Mandrake 7.0 (2) ) on my laptop, a Sony Vaio PCG-F160, with an IBM Etherjet 10/100 ethernet card.

I managed to get Linux installed quickly enough, but My ethernet card is not working.

I've got a small firewall that handles DHCP for me, and my desktop machines in the house all get their IP addresses perfectly fine.

When the PCMCIA Etherjet card is inserted, the firewall is getting the request for the IP address, and is sending the response, but the laptop is not seeing the response.

Now, I started looking into this, it seems that the PCMCIA Etherjet card is trying to use the tulip_cb driver. It loads, and actually sends packets, but it does not seem to get the DHCP response.

I then gave the laptop a static IP address, and tried to ping the other systems in my house. The phone rang, and I was distracted for a few minutes, and then when I was finished, I noticed that the laptop _was_ getting the pings thru. at 25000 ms ping times. Wow, I didn't know that it would do that!

So I am fairly convinced that I have the right driver, and it would work, I'm just missing something...

I have a couple of questions about this :

1. are there any settings I should be putting into the /etc/pcmcia/config.opts file?

2. I noticed that Mandrake 7 uses pcmcia 3.1.9 and there is version 3.1.11 out. Would upgrading my pcmcia (and the modules therein) fix this?

3. My network is a 10mbit network, is there a way to force the PCMCIA Etherejet card to 10mb( if this is a problem)

4. Does anyone have a clue as to where I should go next?

Thanks, in advance, for any help anyone could offer me in my time of need... ;)

Garrett

PS. I had loaded linux on another laptop about a year ago, and I could have _sworn_ that I used this exact same ethernet card, and it worked really well. Am I on drugs, or what?

None System log messages?

Re: Question IBM PCMCIA Etherjet 10/100... lord help me. (GarrettSerack)
Date: 2000, Feb 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

System log messages might be useful.  My first suggestion would
probably be a PCMCIA driver upgrade.  With the caveat that support for
this card is officially "experimental" and may simply be broken.

-- Dave

Question Redhat 6.0 and Xircom Realport 10/100TX

Date: 2000, Feb 29
From: LaJchon McRight lajchon

I have a Xircom Realport 10/100TX + 56K Modem. I also have Redhat Linux 6.0 installed. I just read on Redhat's website that it does not support this network adapter. Is there something I can do to make it work with 6.0?

Thanks

LaJchon

None Maybe this is too obvious...

Re: Question Redhat 6.0 and Xircom Realport 10/100TX (LaJchon McRight)
Date: 2000, Feb 29
From: David Hinds <dhinds@pcmcia.sourceforge.org>

How about upgrading your PCMCIA drivers?

(actually, there are two completely different Xircom Realport 10/100TX
+ 56K cards: one is a 16-bit card, the other is a CardBus card.

-- Dave

Note I understand....

Re: None Maybe this is too obvious... (David Hinds)
Date: 2000, Feb 29
From: LaJchon McRight lajchon

I understand that I might have to upgrade my drivers.. My question was will my Xircom Realport 10/100TX Cardbus work with Redhat Linux 6.0 even though it says it is incompatible on Redhat's website.

And if so, what should I download?

Thanks,

None The incompatibility is just with what they ship

Re: Note I understand.... (LaJchon McRight)
Date: 2000, Feb 29
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The incompatibility just means that RH6.0 does not include an
appropriate driver, not that the right driver won't work.

There are more detailed instructions in the PCMCIA-HOWTO, for how to
compile and install the PCMCIA driver package.

-- Dave

Ok Thanks for the help

Re: None The incompatibility is just with what they ship (David Hinds)
Date: 2000, Feb 29
From: LaJchon McRight lajchon

I understand now.. Thanks so much for the help

LaJchon

None Module Support for Xircom RealPort 2

Date: 2000, Mar 08
From: TeeJin TeeJin

Just like to enquire if there is any support for Realport 2 Cardbus Ethernet 10/100 ?

Our Realport 2 Modem 56 works with the normal xircps module though.

Cheers TeeJin

None I don't know

Re: None Module Support for Xircom RealPort 2 (TeeJin)
Date: 2000, Mar 08
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> Just like to enquire if there is any support for Realport 2 Cardbus
> Ethernet 10/100 ?

Unknown.  I would just try the tulip_cb driver like the older Realport
Cardbus cards.

> Our Realport 2 Modem 56 works with the normal xircps module though.

?? the xirc2ps module is an ethernet driver.  It can't work with a
modem.

-- Dave

None I got it working with the tulip-cb .. but only sort of

Re: None I don't know (David Hinds)
Date: 2000, Jul 31
From: nyet

I have a Xircom CardBus RealPort 2. I got it working, but only after putting the card in promisc mode with tcpdump.

config entry:
card "Xircom RealPort2 CardBus Ethernet 10/100"
# manfid: 0x0105, 0x0103
  version "Xircom", "*", "R2BE-100BTX"
  bind "tulip_cb"

Feedback Xircom Cardbus issues

Date: 2000, Mar 11
From: James Morris <jmorris@intercode.com.au>

In the Known Problems document for 3.1.12 release, you mention an issue with the Xircom Cardbus card is shut down. I 'm not sure if this is exactly the same, but am able to reproduce an oops when removing the card while the tulip_cb module is loaded under kernel 2.3.51.

If rtnetlink messages are configured, the unregister_netdevice() call from the tulip_cb 'remove' operation kicks rtnetlink into issuing a routing message via the notifier block. This seems to be happening under interrupt (or at least, in_interrupt() returns true), which results in an oops as rtnetlink tries to allocate an skb non-atmomically.

There seem to be a number of other issues including tx timeouts. Unfortunately, I don't know enough about PC hardware to take this much further, but have noticed that tulip_cb registers itself as a pci driver. Is this correct?

Also, the non-pcmcia tulip driver in the current tree seems to be undergoing some significant changes. Is the pcmcia version being maintained in sync with this?

- James

None I think the 2.3.* issue is different

Re: Feedback Xircom Cardbus issues (James Morris)
Date: 2000, Mar 13
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I think the problem with tulip_cb in the 2.3.51 kernel tree is
different; the tulip_cb driver in the PCMCIA package does not have
this problem, because in my version of the driver, unregister_netdev
is not called in interrupt context.  Jeff Garzik, who is now
maintaining the tulip drivers in the 2.3 tree, plans to merge the
Cardbus-specific tulip stuff so that there will be just one tulip
driver.  Right now, the tulip_cb driver in the 2.3 tree is in a
temporarily funny state, because it has partially diverged from the
old tulip_cb driver, but the new merged tulip driver isn't ready yet.

The tulip_cb driver in the 2.3 tree uses the relatively new kernel
API's for hot swap PCI devices, which is really what cardbus cards
are.

-- Dave

Ok Ok, patch sent.

Re: None I think the 2.3.* issue is different (David Hinds)
Date: 2000, Mar 13
From: James Morris <jmorris@intercode.com.au>

Thanks for the info.

Just to let you know, I've just sent a patch to J. Garzik with the relevant xircom cardbus code from tulip_cb copied to the main tulip driver. Hopefully it will work ok (I can't test properly on this machine at the moment due to yenta/pci problems).

- James

None Problems with RBEM56G-100BTX Cardbus combo card

Date: 2000, Mar 16
From: Jeff Key jkey

I'm having trouble getting a RBEM56G-100BTX combo modem/ethernet card working on a Dell Inspiron 7500. I'm running Mandrake Linux 7.0 (kernel version 2.2.14) and installed the latest PCMCIA drivers (3.1.12). I did not do any special configuration or set any options.

Actually, I can get both the networking and modem functions working individually, but not without extra effort and not working at the same time. The first problem is that bringing up the eth0 interface at boot time fails. After I log on, however, restarting the network (/etc/rc.d/init.d/network restart) brings it up. Then network access seems fine.

The next problem is that I can only use the modem if I bring the eth0 interface down (ifconfig eth0 down). I don't think that this should be required, but maybe it's normal. If eth0 is up then either the pppd daemon dies or any attempt to use the network (e.g., ping) goes nowhere.

I read in the PCMCIA-HOWTO that the messages "Delaying eth0 initialization" and "[FAILED]", which I do get, don't really signify a failure. But eth0 doesn't come up during the boot process at all, so something really is wrong. I've included some log messages below.

I probably shouldn't have gotten this card and should have gone with the 16-bit version (non-Cardbus) instead. If I can't get it working properly, I might still be able to exchange it.

Any suggestions would be greatly appreciated.

Thanks,

Jeff

----------------From /var/log/messages:-------------------

Mar 15 15:26:26 droplet kernel: Linux PCMCIA Card Services 3.1.12 
Mar 15 15:26:26 droplet kernel:   kernel build: 2.2.14-15mdk #1 Tue Jan 4 22:24:20 CET 2000 
Mar 15 15:26:26 droplet kernel:   options:  [pci] [cardbus] [apm] 
Mar 15 15:26:26 droplet kernel: PCI routing table version 1.0 at 0xfdf50 
Mar 15 15:26:26 droplet kernel:   00:04.0 -> irq 11 
Mar 15 15:26:26 droplet kernel:   00:04.1 -> irq 11 
Mar 15 15:26:26 droplet kernel: Intel PCIC probe:  
Mar 15 15:26:26 droplet kernel:   TI 1225 PCI-to-CardBus at slot 00:04, mem 0x68000000 
Mar 15 15:26:26 droplet kernel:     host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 168/32] [bus 32/34] 
Mar 15 15:26:26 droplet kernel:     host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat 168/32] [bus 35/37] 
Mar 15 15:26:26 droplet kernel:     PCI irq 11 seems to be wedged! 
Mar 15 15:26:26 droplet kernel:     PCI irq 11 test failed 
Mar 15 15:26:26 droplet kernel:     ISA irqs (scanned) = 3,4,7,9,10 polling interval = 1000 ms 
Mar 15 15:26:26 droplet kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x107f 
Mar 15 15:26:26 droplet kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7 
Mar 15 15:26:26 droplet kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Mar 15 15:26:26 droplet kernel: cs: cb_alloc(bus 32): vendor 0x115d, device 0x0003 
Mar 15 15:26:26 droplet kernel: cs: cb_config(bus 32) 
Mar 15 15:26:26 droplet kernel:   fn 0 bar 2: mem 0x60013000-0x600137ff 
Mar 15 15:26:26 droplet kernel:   fn 0 bar 3: mem 0x60012000-0x600127ff 
Mar 15 15:26:26 droplet kernel:   fn 1 bar 1: io 0x280-0x287 
Mar 15 15:26:26 droplet kernel:   fn 1 bar 2: mem 0x60011000-0x600117ff 
Mar 15 15:26:26 droplet kernel:   fn 1 bar 3: mem 0x60010000-0x600107ff 
Mar 15 15:26:26 droplet kernel:   fn 0 bar 1: io 0x200-0x27f 
Mar 15 15:26:26 droplet kernel:   fn 0 rom: mem 0x6000c000-0x6000ffff 
Mar 15 15:26:26 droplet kernel:   fn 1 rom: mem 0x60008000-0x6000bfff 
Mar 15 15:26:26 droplet kernel: tulip_attach(bus 32, function 0) 
Mar 15 15:26:26 droplet kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford) 
Mar 15 15:26:26 droplet kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x200, 00:10:A4:C1:CF:39, IRQ 3. 
Mar 15 15:26:26 droplet kernel: eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1. 
Mar 15 15:26:26 droplet kernel: serial_attach(bus 32, fn 1) 
Mar 15 15:26:26 droplet kernel: tty01 at 0x0280 (irq = 3) is a 16550A 
Mar 15 15:26:26 droplet kernel: CSLIP: code copyright 1989 Regents of the University of California 
Mar 15 15:26:26 droplet kernel: ISDN subsystem Rev: 1.93/1.80/1.95/1.60/1.17/1.3 loaded 
Mar 15 15:26:26 droplet kernel: HiSax: Linux Driver for passive ISDN cards 
Mar 15 15:26:26 droplet kernel: HiSax: Version 3.3c (module) 
Mar 15 15:26:26 droplet kernel: HiSax: Layer1 Revision 2.36 
Mar 15 15:26:26 droplet kernel: HiSax: Layer2 Revision 2.20 
Mar 15 15:26:26 droplet kernel: HiSax: TeiMgr Revision 2.13 
Mar 15 15:26:26 droplet kernel: HiSax: Layer3 Revision 2.10 
Mar 15 15:26:26 droplet kernel: HiSax: LinkLayer Revision 2.40 
Mar 15 15:26:26 droplet kernel: HiSax: Approval certification valid 
Mar 15 15:26:26 droplet kernel: HiSax: Approved with ELSA Quickstep series cards 
Mar 15 15:26:26 droplet kernel: HiSax: Approval registration numbers: 
Mar 15 15:26:26 droplet kernel: HiSax: German D133361J CETECOM ICT Services GmbH 
Mar 15 15:26:26 droplet kernel: HiSax: EU (D133362J) CETECOM ICT Services GmbH 
Mar 15 15:26:26 droplet kernel: HiSax: Approved with Eicon Technology Diva 2.01 PCI cards 
Mar 15 15:26:26 droplet kernel: HiSax: Card 1 Protocol EDSS1 Id=Teles1 (0) 
Mar 15 15:26:26 droplet kernel: HiSax: Teles IO driver Rev. 2.14 
Mar 15 15:26:26 droplet kernel: Teles: 16.3 Byte at d80 is ff 
Mar 15 15:26:26 droplet kernel: HiSax: Card Teles 16.3 not installed ! 
Mar 15 15:26:26 droplet kernel: ISDN-subsystem unloaded 
Mar 15 15:26:26 droplet atd: atd startup succeeded
Mar 15 15:26:11 droplet rc.sysinit: Mounting proc filesystem succeeded 
Mar 15 15:26:11 droplet date: Wed Mar 15 15:26:10 CST 2000 

--------------- From /var/log/boot.log: -------------------

Mar 15 15:26:15 droplet rc.sysinit: Enabling swap space succeeded 
Mar 15 15:26:16 droplet mandrake_everytime: Building Window Manager Sessions succeeded 
Mar 15 15:26:22 droplet kudzu:  succeeded 
Mar 15 15:26:22 droplet network: Bringing up interface lo succeeded 
Mar 15 15:26:23 droplet ifup: Delaying eth0 initialization. 
Mar 15 15:26:23 droplet network: Bringing up interface eth0 failed 
Mar 15 15:26:23 droplet portmap: portmap startup succeeded 
Mar 15 15:26:24 droplet apmd: apmd startup succeeded 
Mar 15 15:26:24 droplet isdn4linux: Loading HiSax driver 
Mar 15 15:26:24 droplet isdn4linux: CardID: Teles1 
Mar 15 15:26:24 droplet isdn4linux: CardType: 3 
Mar 15 15:26:24 droplet isdn4linux: CardName: Teles 16.3 
Mar 15 15:26:24 droplet isdn4linux: Parameters: id=Teles1 type=3 protocol=2 irq=10 io=0xd80 
Mar 15 15:26:25 droplet isdn4linux: /lib/modules/2.2.14-15mdk/misc/hisax.o:  
Mar 15 15:26:25 droplet isdn4linux:  
Mar 15 15:26:25 droplet isdn4linux: Initialization of ISDN failed! 
Mar 15 15:26:25 droplet isdn4linux: Check the values in '/etc/sysconfig/isdn'! 
Mar 15 15:26:25 droplet isdn4linux:  
Mar 15 15:26:25 droplet isdn4linux: init_module: Device or resource busy 
Mar 15 15:26:25 droplet rc: Starting isdn4linux succeeded 
Mar 15 15:26:25 droplet random: Initializing random number generator succeeded 
Mar 15 15:26:25 droplet netfs: Mounting other filesystems succeeded 
Mar 15 15:26:27 droplet crond: crond startup succeeded
Mar 15 15:26:27 droplet inet: inetd startup succeeded
Mar 15 15:26:27 droplet lpd: lpd startup succeeded
Mar 15 15:26:28 droplet nfslock: rpc.lockd startup succeeded
Mar 15 15:26:28 droplet nfslock: rpc.statd startup succeeded
Mar 15 15:26:29 droplet amd: amd startup succeeded
Mar 15 15:26:29 droplet loadkeys: Loading /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
Mar 15 15:26:29 droplet keytable: Loading keymap: us succeeded
Mar 15 15:26:29 droplet loadkeys: Loading /usr/lib/kbd/keymaps/compose/compose.latin.gz
Mar 15 15:26:30 droplet keytable: Loading compose keys: compose.latin succeeded
Mar 15 15:26:30 droplet keytable:  succeeded
Mar 15 15:26:30 droplet keytable: Loading system font:  succeeded
Mar 15 15:26:30 droplet postfix: Starting postfix: 
Mar 15 15:26:30 droplet postfix: newaliases: fatal: My hostname droplet is not a fully qualified name - set myhostname or mydomain in /etc/postfix/main.cf
Mar 15 15:26:31 droplet postfix: postmap: fatal: My hostname droplet is not a fully qualified name - set myhostname or mydomain in /etc/postfix/main.cf
Mar 15 15:26:35 droplet last message repeated 4 times
Mar 15 15:26:37 droplet postfix: postfix
Mar 15 15:26:37 droplet rc: Starting postfix succeeded
Mar 15 15:26:38 droplet gpm: gpm startup succeeded
Mar 15 15:26:40 droplet xfs: xfs startup succeeded
Mar 15 15:26:41 droplet smb: smbd startup succeeded
Mar 15 15:26:41 droplet smb: nmbd startup succeeded
Mar 15 15:26:44 droplet linuxconf: Linuxconf final setup
Mar 15 15:26:46 droplet rc: Starting linuxconf succeeded

None Maybe a config file problem, and maybe a PPP specific problem

Re: None Problems with RBEM56G-100BTX Cardbus combo card (Jeff Key)
Date: 2000, Mar 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

For the first part of your problem, with the network card: check the
PCMCIA-HOWTO notes about Red Hat (and Mandrake).  There are some
config file issues when you upgrade the PCMCIA drivers, that may
prevent the drivers from automatically configuring a network card.

For the modem, this really sounds like a PPP configuration issue and
not a PCMCIA issue.  My guess is that the active network interface
(which probably includes a default route pointing to eth0) is not
cooperating with the new PPP device.  It is really hard to tell if
there is a driver problem using PPP: there are so many PPP specific
things that could be wrong.

If you want to diagnose whether the problem is with the modem or with
PPP, try to make a connection using a simple terminal program like
minicom.  If that works, then PPP is the problem, and the PPP-HOWTO
might be a good place to look.

-- Dave

None A partial answer to my own question

Re: None Problems with RBEM56G-100BTX Cardbus combo card (Jeff Key)
Date: 2000, Mar 19
From: Jeff Key jkey

I'll answer part of my own question based on a new discovery. Part of my problem was that eth0 wasn't being brought up on boot (at all). In /etc/rc.d/rc?.d (where ? is 2, 5, and a couple others) there were these links:

  S10network
  S45pcmcia

i.e., the network was starting before the pcmcia card manager. I changed 'S45pcmcia' to 'S07pcmcia' so that the card manager would start before the network. Viola! I'm not sure if this is the correct fix, but it does seem to work, at least so far.

The other problem, not being able to use ppp when eth0 is up, is a bit more complicated. What I did discover was that (a) it's not a modem problem and (b) this problem doesn't exist if I assign eth0 a "local" IP address (e.g., 10.0.0.1) and use DNS server addresses that correspond to my local ISP. I'm not sure which of these actually was the problem.

This setup is ok since I don't plan to be on a "connected" network (Internet) and use the phone at the same time. I do plan to use the phone when I'm connected to two other pcs that I have at home, but those are not actually connected to the outside world.

So, it appears that the Xircom Cardbus Ethernet 10/100 + 56 works just fine with the Dell Inspiron 7500 and Mandrake Linux 7.0.

Jeff

None The script order was actually correct

Re: None A partial answer to my own question (Jeff Key)
Date: 2000, Mar 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It is not a good idea to reverse the odrer of the startup scripts.
The original order was correct.  Believe it or not, it is not
necessary for the PCMCIA script to run before the network script.
If you think about it, hot insertion of a PCMCIA network card could
not possibly work, if the card needed to be initialized before the
network script runs.

-- Dave

None Hmm...it works!

Re: None The script order was actually correct (David Hinds)
Date: 2000, Mar 21
From: Jeff Key jkey

Dave,

I went back and reread that part of the HOWTO and it took on new meaning after your comments. The first time I read the Red Hat discussion it appeared to only relate to "breaking" the linuxconf connection to the network information. I see now that what actually broke was how the network came up.

I restored the original order of the pcmcia and network scripts and replaced network.opts with the code in the HOWTO. It seems to work fine.

Thanks for your help.

Jeff

David Hinds wrote:

> 
> If "ifup eth0" works after booting, but it didn't work with the
> original script order, then I bet you upgraded your PCMCIA package and
> didn't check the HOWTO section on RedHat/Mandrake.  You need to modify
> /etc/pcmcia/network.opts so that the Red Hat network startup program
> is executed when a network card is configured.  The HOWTO shows what
> to do.
> 
> -- Dave

Sad Xircom RE-100 and ThinkPad 600x

Date: 2000, Mar 18
From: Ron Ostiguy rostiguy

I'm having a problem with an IBM ThinkPad 600x and a Xircom RE-100.

I read the PCMCIA FAQ, but am still a bit unclear where to start troubleshooting. When I look at /var/log/messages, cardmgr give the following info:

cardmgr[10314]: starting, version is 3.0.14
cardmgr[10314]: watching 2 sockets
cardmgr[10314]: could not adjust resource: IO ports 0x1000-0x17ff: Device or resource busy
cardmgr[10314]: could not adjust resource: IO ports 0x100-0x4ff: Device or resource busy
cardmgr[10314]: could not adjust resource: memory 0xc0000-0xfffff: Device or resource busy
cardmgr[10314]: could not adjust resource: memory 0x60000000-0x60ffffff: Device or resource busy
cardmgr[10314]: could not adjust resource: IO ports 0xa00-0xaff: Device or resource busy
cardmgr[10314]: initializing socket 1
cardmgr[10314]: socket 1: Xircom CE3-10/100 Fast Ethernet
cardmgr[10314]: executing: 'insmod /lib/modules/2.2.10/pcmcia/xirc2ps_cs.o'
cardmgr[10314]: + /lib/modules/2.2.10/pcmcia/xirc2ps_cs.o: a module named xirc2ps_cs already exists
cardmgr[10314]: insmod exited with status 1
cardmgr[10314]: executing: 'modprobe xirc2ps_cs'
cardmgr[10314]: + can't locate module xirc2ps_cs
cardmgr[10314]: modprobe exited with status 1
cardmgr[10314]: 'xirc2ps_cs' already bound to socket 1
cardmgr[10314]: executing: './network start eth0'
cardmgr[10314]: exiting


I'm not sure where to begin! I saw a XIRCOM-HOWTO for the Thinkpad 600x, but when I went to download it that night, the site changed format and I can't find the archive!

Any pointing in the the right direction (I can RTFM if I know what I'm looking for) would be greatly appreciated!

Thanks in advance.
Ron Ostiguy

None I think a driver upgrade is your best bet

Re: Sad Xircom RE-100 and ThinkPad 600x (Ron Ostiguy)
Date: 2000, Mar 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

This is not a clean message log, so it is hard to interpret: it looks
like you restarted the PCMCIA stuff when it was already running.  So
the interesting messages are all earlier in your log, when PCMCIA was
started the first time.

However, my first suggestion would be to just upgrade to the current
PCMCIA driver release, which is now 3.1.13.  There have been fixes in
the Xircom driver between 3.0.14 and now.

-- Dave

Agree Working!

Re: None I think a driver upgrade is your best bet (David Hinds)
Date: 2000, Mar 29
From: Ron Ostiguy rostiguy

Just a quick note to let everyone know that I got my Xircom Realport Ethernet adapter working!

I would like to Thanks Dave Hinds for his suggestion. I downloaded a copy of 3.0.14 (the most recent version at the time) a couple of weeks ago hoping that it would allow my xircom card to work. It did not seem to fix my problems and I posted my questions to the newsgroup. Apparently version 3.1.13 came out while I was troubleshooting 3.0.14. I have since downloaded 3.1.13 and the card is working fine.

Thanks again for all your help!

Ron Ostiguy

Question CEM56 with 3.1.11: only fullduplex??

Date: 2000, Mar 20
From: Andreas Gräf Grumpftl

Hi,

I'm using the CEM56 here on a Suse 6.3, 2.2.14 and PCMCIA 3.1.11.
The card is used in a little network with 2 10MB-NE2000 (TP).

I discovered, that the Xircom-Card produces a lot of collisions on the network:
-Transfering data from/to the notebook: Collision
-transfer to any other pc: no Col.
-collision-counter on the NE2000 grows _very_ fast, but on the Xircom no collision is detected.

I think that thing is working full-duplex.

Any hints what to do?

	Thank you!

Question Xircom CE2 not identified on Toshiba 4030CDT

Date: 2000, Mar 21
From: Tony Kerr tkerr

Hi.

I'm having trouble getting cardmgr to identify my CE2 at boot time. Everything seems to come up OK, although I get a high/low beep and "cardctl ident" gives me "product info not available".

If I eject and then insert the card (using cardctl eject and cardctl insert) cardmgr has no trouble identifying it as a Xircom CE2, and it all seems to work normally. Suspend and resume also work, but reset does not.

I've tried putting calls to cardctl in etc/rc.d/rc.local to force the issue at boot time, but it doesn't work.

I have a Toshiba 4030CDT, kernel 2.2.14 and cs-3.1.13.

Any ideas?

Tony

More Additional info

Re: Question Xircom CE2 not identified on Toshiba 4030CDT (Tony Kerr)
Date: 2000, Mar 21
From: Tony Kerr tkerr

Oh, yea. That's Caldera and KDE (hence sys V style scripts)

Umm what else... The init of eth0 fails at boot as well, but it comes up fine after ejecting and inserting socket 1.

None I think it is really a Toshiba issue

Re: Question Xircom CE2 not identified on Toshiba 4030CDT (Tony Kerr)
Date: 2000, Mar 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It might be useful to see the kernel messages.  Also, what does
"cardctl status" report, right after booting with the card in?

One option (not really a fix, but a workaround) might be to play with
the PCMCIA bridge mode in your BIOS setup menu.  You should be able to
choose between three modes: "PCIC", "Auto", and "CardBus".  Try each
setting.  The "PCIC" mode should be ok, but will prevent you from
using 32-bit CardBus cards.  Which may not even be a concern.

-- Dave

More Here are the kernel messages.

Re: None I think it is really a Toshiba issue (David Hinds)
Date: 2000, Mar 22
From: Tony Kerr tkerr

Hi, David.

I tried setting the BIOS to PCIC, but the card would not come up at all. When I set it to cardbus/16 bit, it came up as usual, i.e still not recognised until I eject and insert it.

The report from cardctl straight after boot is:

Socket 0:
  5V 16-bit PC Card
  function 0: [ready], [bat dead], [bat low]
Socket 1:
  5V 16-bit PC Card
  function 0: [ready]

I have a Xircom modem card in socket 0

and the report from the kernel is:

Mar 22 18:13:37 einstein kernel: Adding Swap: 208772k swap-space (priority -1) 
Mar 22 18:13:37 einstein kernel: Linux PCMCIA Card Services 3.1.13 
Mar 22 18:13:37 einstein kernel:   kernel build: 2.2.14 #5 Wed Mar 15 09:26:43 EST 2000 
Mar 22 18:13:37 einstein kernel:   options:  [pci] [cardbus] [apm] 
Mar 22 18:13:37 einstein kernel: PCI routing table version 1.0 at 0xf0180 
Mar 22 18:13:37 einstein kernel: Intel PCIC probe:  
Mar 22 18:13:37 einstein kernel:   Intel i82365sl B step ISA-to-PCMCIA at port 0x3e0 ofs 0x00 
Mar 22 18:13:37 einstein kernel:     host opts [0]: none 
Mar 22 18:13:37 einstein kernel:     host opts [1]: none 
Mar 22 18:13:37 einstein kernel:     ISA irqs (scanned) = 3,4,5,7,10 polling interval = 1000 ms 
Mar 22 18:13:37 einstein kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff 
Mar 22 18:13:37 einstein kernel: cs: IO port probe 0x0800-0x08ff: clean. 
Mar 22 18:13:37 einstein kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7 
Mar 22 18:13:37 einstein kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Mar 22 18:13:37 einstein kernel: bug: kernel timer added twice at c401e53b. 
Mar 22 18:13:37 einstein kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
Mar 22 18:13:37 einstein kernel: tty03 at 0x02e8 (irq = 3) is a 16550A 
Mar 22 18:13:38 einstein kernel: ypbind forgot to set AF_INET in udp sendmsg. Fix it! 
Mar 22 18:13:38 einstein ypbind[147]: unable to register (YPBINDPROG, YPBINDVERS, udp). : Invalid argument 
Mar 22 18:13:38 einstein amd[155]: AM-UTILS VERSION INFORMATION:
Mar 22 18:13:38 einstein amd[155]: Copyright (c) 1997-1998 Erez Zadok
Mar 22 18:13:38 einstein amd[155]: Copyright (c) 1990 Jan-Simon Pendry
Mar 22 18:13:38 einstein amd[155]: Copyright (c) 1990 Imperial College of Science, Technology & Medicine
Mar 22 18:13:38 einstein amd[155]: Copyright (c) 1990 The Regents of the University of California.
Mar 22 18:13:38 einstein amd[155]: am-utils version 6.0 (build 1).
Mar 22 18:13:38 einstein amd[155]: Built by root@knob.calderasystems.com on date Wed Apr 28 14:01:55 MDT 1999.
Mar 22 18:13:38 einstein amd[155]: cpu=i386 (little-endian), arch=i386, karch=i686.
Mar 22 18:13:38 einstein amd[155]: full_os=linux, os=linux, osver=2.2.0-final, vendor=pc.
Mar 22 18:13:38 einstein amd[155]: Map support for: root, passwd, union, nisplus, nis, ndbm, file, error.
Mar 22 18:13:38 einstein amd[155]: AMFS: nfs, link, nfsx, nfsl, host, linkx, program, union, inherit, 
Mar 22 18:13:38 einstein amd[155]:       ufs, cdfs, pcfs, auto, direct, toplvl, autofs, error.
Mar 22 18:13:38 einstein amd[155]: FS: autofs, iso9660, nfs, vfat, ext2.
Mar 22 18:13:38 einstein amd[155]: No networks.
Mar 22 18:13:38 einstein amd[155]: My ip addr is 0x0
Mar 22 18:13:38 einstein amd[156]: released controlling tty using setsid()

Tony

Idea Yes, swapping slots DOES make a difference!

Re: None I think it is really a Toshiba issue (David Hinds)
Date: 2000, Mar 24
From: Tony Kerr tkerr

Now I'm kicking myself that I didn't think to try it. The CE2 seems to be quite happy to come up in socket 0, but not in socket 1. I haven't tried the modem in socket 1 yet, though.

Tony

Question Xircom CEM 56 on CPt 400 GT

Date: 2000, Mar 24
From: GS giancarlo

I cannot use the Xircom CEM56 modem+ethernet PCMCIA card on my Latitude
CPt V400GT; Note that the same card works without problems on my CPt
466 GT (but it has differents sound and video cards).

The problem is that when I insert the card, I get a "failed IRQ3"
error; I tried to modify the setup in /etc/pcmcia/config.opts, and in
particular I used the same values of the Windows98 setup.
Unfortunantely evrerything was useless (..."failed IRQ x" ..."no
avaiable port"  ..."no avaiable memory" and many others errors!)

Thanks in advance for any suggestion. Giancarlo Sangalli. 

None Re: Question: Xircom CEM 56 on CPt 400 GT

Re: Question Xircom CEM 56 on CPt 400 GT (GS)
Date: 2000, Mar 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Please post the actual log messages, including the PCMCIA startup
messages.  Do you have any other PCMCIA cards that do (or do not)
work?

-- Dave

Question On compaq laptop 1530..PCMCIA hangs and ETH0 Fail.xircom rbe100 cardbus

Date: 2000, Apr 04
From: Johnny Page vmvse

I have a compaq armada 1530dm, with a xircom rbe100 cardbus ethernet card, and when i install redhat 6.0 the it hangs at pcmcia and I have to reboot

Then I attempt to install without PCMCIA and it startup fine but then ETH0 gets a failed during startup.

Do I need to install the pcmcia-cs-3.1.13 or is it just a PCMCIA problem? What do I do to resolve both problems with (PCMCIA and ETHO initializing)

I need help .

Johnny

None The first things to do

Re: Question On compaq laptop 1530..PCMCIA hangs and ETH0 Fail.xircom rbe100 cardbus (Johnny Page)
Date: 2000, Apr 04
From: David Hinds <dhinds@pcmcia.sourceforge.org>

There is a section in the PCMCIA-HOWTO specifically to help diagnose
startup problems like this.  You should also check the linux laptops
page to see if anyone has seen (and fixed) similar problems with this
particular laptop.

If the instructions in the HOWTO don't help, then a driver upgrade
might be the next thing to try.

-- Dave

Question Where can I found Linux driver for CBEM+100BTX ?

Date: 2000, Apr 05
From: Anthony BLONDEL toniob

I don't on the XIRCOM site where can I found a CreditCard (10/100 + Modem) driver ?

Is someone could help me ? on toniob@caramail.com

None It is with all the other drivers

Re: Question Where can I found Linux driver for CBEM+100BTX ? (Anthony BLONDEL)
Date: 2000, Apr 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It is included in the Linux PCMCIA package.  You don't get the driver
as a separate thing.  Check the PCMCIA-HOWTO section on "usage and
features" for how to use Linux PCMCIA.

-- Dave

Question RBE100, and insmod error

Date: 2000, Apr 06
From: Dolapo Falola qmac

during startup eth0 initialization fails. Whenever i insert the card, i get the high high seq, so i know it recognizes the card. but when checking the log, i'm getting an error, somehting like: insmod: /lib/modules/......../tulip.o: init_module: device or resource busy.

thanks.

None Not enough information

Re: Question RBE100, and insmod error (Dolapo Falola)
Date: 2000, Apr 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

More system log messages would help.  You could also mention what kind
of laptop this is, and what kernel version you're using.  And the
exact message may be more helpful than an approximation.

-- Dave

None Untitled

Re: None Not enough information (David Hinds)
Date: 2000, Apr 06
From: Dolapo Falola qmac

sorry, I have a thinkpad 600e with 2.2 kernel and the error is here's a couple lines before and after the error.

Dorm network: Bringing up interface lo succeeded Dorm insmod: /lib/modules/2.2.14-15mdk/net/tulip.0: init_module: Device or resource busy Dorm ifup: Delaying eth0 initialization. Dorm network: Bringing up interface eth0 failed Dorm portmap: portmap startup succeeded

thanks for your help

None The wrong driver is being loaded

Re: None Untitled (Dolapo Falola)
Date: 2000, Apr 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Sounds to me like you're trying to use a non-PCMCIA driver for your
card.  The tulip.o driver only supports PCI bus cards.

Do you hear beeps when you insert your Xircom card?

See the PCMCIA-HOWTO section describing your Linux distribution.  If
you are using Red Hat, when you run netconf, you should NOT pick a
name of a kernel module for your card: you should leave that field
blank.

-- Dave

None Untitled

Re: None The wrong driver is being loaded (David Hinds)
Date: 2000, Apr 06
From: Dolapo Falola qmac

yes i hear the two high beeps. I'm running mandrake 7.0; i'm going to try your suggestion right now. The only problem it's not letting me leave the kernel module blank. thank you again for all your help.

None Well, it doesn't really matter

Re: None Untitled (Dolapo Falola)
Date: 2000, Apr 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If it won't let you leave the module blank, and they don't give any
special instructions for PCMCIA, then I think that's a bug in their
system.  In any case, you could edit /etc/conf.modules or modules.conf
and just delete any lines that refer to eth0.

You should look at your system log after inserting the card and see
what it says.  Actually I don't think it should even matter if the
system first tries to load the wrong module.  It should eventually
load the right one when the PCMCIA system starts up.

-- Dave

None Untitled

Re: None Well, it doesn't really matter (David Hinds)
Date: 2000, Apr 06
From: Dolapo Falola qmac

ok, I've deleted those lines. It must be failing for some other reason. The light on my hub from my laptop is turning on now, so perhaps I have the wrong net settings? I don't think anything is wrong w/ the pcmcia. perhaps the network settings?

None msg after insertion

Re: None Untitled (Dolapo Falola)
Date: 2000, Apr 06
From: Dolapo Falola qmac

this is what dmesg says after i remove and insert the card
tulip_detach(eth0())
cs:cb_disable(bus 5)
cs:cb_release(bus 5)
cs: cb_free(bus 5)
tulip_reap()
cs: cb_alloc(bus 5): vendor 0x115d, device 0x003
ROM image dump:
  image 0:0x000000-0xffffffff, signature PCIR
cs: cb_config(bus 5)
  fn 0 bar 1: io 0x400-0x47f
  fn 0 bar 2: mem 0x60000d000-0x60000d7ff
  fn 0 bar 3: mem 0x60000c000-0x60000c7ff
  fn 0 rom: mem 0x6000080000-0x60000bfff
cs: cb_enable(bus 5)
  bridge io map 0 (flags 0x21): 0x400-0x47f
  bridge mem map 0 (flags 0x1): 0x6000080000-0x60000dfff
tulip_reap()
tulip_attach(bus 5, function 0)
tulip.c:v0.91g-ppc 7.16.99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x400, 00:10:A4:E0:24:69, IRQ 11.
eth0: MII transceive #0 config 3100 status 7809 advertising 01e1

hope that means something

Thanks

None Re: msg after insertion

Re: None msg after insertion (Dolapo Falola)
Date: 2000, Apr 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Your messages all appear to be fine.

Double check your network settings.

Then there is just the issue that the driver for the Xircom CardBus
cards is flaky and doesn't work at all for some people.  That is an
open issue; I recently got a Xircom card to work on but haven't had
much time to look at it yet.

-- Dave

None Xircom RBE 10/100 BTX cardbus

Re: None Re: msg after insertion (David Hinds)
Date: 2000, Jun 09
From: Paulo E. Abreu peabreu

Hello there,

I saw your posting that you had a cardbus from xircom working, can you tell us how you did it ? My card works well in 10BaseTx although under heavy traffic it spits out:

Jun 9 09:34:04 ervilha kernel: tulip.c: outl_CSR6 too many attempts,csr5=0x60208100

At home with a crossover cable and a LinkSys PNIC card on the other side I get transfer rates of 160Kb/s although the indicator of 100Mb/s lights up ...

I can beta test the driver. With the new drivers (pcmcia-cs.06-Jun-00.tar.gz) the card gets recognized as a CBEII 10/100 and the behaviour is still the same.

Did the specs relesead from Xircom didnt help or its just a matter of lack-of-time-to-develop ?

Thanks to everyone that is developing the pcmcia-cs package

Paulo E. Abreu

Question Xircom RBEM56G-100 stalls

Date: 2000, Apr 12
From: Sebastien Bailard <sbailard@physics.umd.edu>

  I've got a Dell Inspiron 3700 running Red Hat 6.1. When I use my RBEM56G-100 as a modem, it stalls when downloading big files, but doesn't seem to choke on small files or low-bandwidth websites. I istalled pcmcia-cs-3.1.13, but it didn't clear up the problem.
  Is this covered in the PCMCIA-HOWTO, and did I just miss it?

-Sebastien Bailard

Agree My Xircom CBE modem also stalls

Re: Question Xircom RBEM56G-100 stalls (Sebastien Bailard)
Date: 2000, Apr 22
From: Jeff Johann <jjohann@kiva.net>

The problem described above also happens on a Xircom CBE 10/100 Ethernet +modem. I am using a stock Redhat 6.2 installed on a gateway 9300.

The modem works for small transfers and normal ppp connections, but stalls on large transfers. While trying to load the helix gnome packages I found that I can download files up to 1 meg reliably, but large files of 2-3 meg stall after doing 63-66K download. Its very odd! the modem seems to realize that I started a big file and has given up.

Agree Mine stalls too !!!

Re: Agree My Xircom CBE modem also stalls (Jeff Johann)
Date: 2000, May 13
From: Mark Ambrose <caffeine23@hotmail.com>

Ah...I thought I was just having a bad experience..

When my modem / ethernet combo DECIDES to work (erratic) on
a HP OmniBook 4150, it also stalls in the low 60k range...

Seems to be a recurring and not-isolated problem....

Question Intel vs. Xircom cardbus?

Date: 2000, Apr 13
From: John Kilpatrick <john@hypergeek.net>

Is there any real difference/advantage of Intel vs. Xircom cardbus cards? I assume they all use the tulip driver, right? Any reason to get one over the other?

And is anyone sucessfully using one with a Tecra 8100 and RedHat 6.2? :-)

Thanks, John

Question xircom combocard on dellI7500

Date: 2000, Apr 13
From: france haardt france

I'm having probs with the Xircom CBEM56G-100 combo card on Dell I7500 running Linux 6.1. The ethernet part works, but not the modem. It seems to connect properly, but then something closes the connection. Notice that the same connection works properly when I run Windows98. Here is the message I got from the "debug" options of the dialup configuration tool:

WvDial: Internet dialer version 1.40 Initializing modem. Sending: ATZ ATZ OK Sending: ATM1L3 ATM1L3 OK Modem initialized. Sending: ATDT 0000000 Waiting for carrier. ATDT 0000000 CONNECT 115200 Carrier detected. Waiting for prompt.

** INFN ltd - Unauthorized access is prohibited. **

User Access Verification

Username: Looks like a login prompt.
Sending: haardt
haardt
Password: Looks like a password prompt.
Sending: (password)Please enter a hostname to connect to
a host, or 'quit' to end this connection:Hmm... a prompt.  Sending "ppp".
ppp
    Entering PPP Mode.
    IP address is 000.00.00.000
    MTU is 0000.
Looks like a welcome message.
Starting pppd at Thu Apr 13 09:21:24 2000
PPP daemon has died! (exit code = 1)
Disconnecting at Thu Apr 13 09:21:24 2000
Auto Reconnect will be attempted in 5 seconds
pppd error!  Look for an explanation in /var/log/messages.

In /var/log/messages the only relevant line I found is: Apr 13 09:21:24 gundam pppd[1153]: The remote system is required to authenticate itself but I couldn't find any secret (password) which would let it use an IP address.

This last message seems to indicate a problem of passwd, but the debug log seems ti indicate some other problem. Thanks in advance for helping.

France

Question RealPort2

Date: 2000, Apr 14
From: Mike Barry mike

Has there been a driver specifically written and tested for the R2M56GA (Ethernet + 56K) to be included the PCMCIA module or will the tulip_cb driver work? Has anyone tested this?

Sad Presario 1210 / RE-100 / debian 2.2 / kernel 2.2.12 / pcmcia 3.1.8

Date: 2000, Apr 18
From: Preston Landers planders

Hi there.

Just got a Xircom RealPort 10/100 (RE-100) and I'm trying to get it to work with my Compaq Presario 1210 laptop and the software version numbers mentioned above.

cardctl says the card is present but 'busy' and I can't initialize or use it. System beeps once when card is removed but not when it is inserted. no lights on card.

When card is inserted, after a few seconds, console prints:

 cs: socket 0 timed out during reset

cardctl status says:

Socket 0:
 5V 16 bit PC Card
 function 0: [busy]
Socket 1:
 no card

cardctl ident causes system hang until card is removed.

running debian 2.2 (frozen) with kernel 2.2.12 / pcmcia 3.1.8.

I'd upgrade software version but there are difficulties getting the neccesary software onto the laptop... anyway, from reading the lists it seems I'm relatively current for my hardware needs.

I had soundblaster enabled & working fine on irq 5 before I tried to install this xircom card. One of the first things I tried was disabling sound but it still didn't work.

I used to have a Linksys type I ethernet card that worked fine until the dongle / connector became munged. After that, it worked intermittently. I am pretty sure the actual PC card slot is fine and that my problem lies in softwareland.

If I can't get it to work in Linux I'm going to have to wipe out the disk and install Lose 98. :-(

Here are my config files: (typing them by hand)

 /etc/pcmcia.conf: 
 PCMCIA=yes
 PCIC=i82365
 PCIC_OPTS=
 CORE_OPTS=
 CARDMGR_OPTS= 

 /etc/pcmcia/config/opts:
 include port 0x100-0x4ff, port 0x1000-0x17ff
 include memory 0xc0000-0xfffff
 include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff 
 include port 0xa00-0xaff
 exclude port 0x2f8-0x2ff
 exclude irq 4
 exclude irq 3

 $ cat /proc/interrupts:
 0 timer
 1 keyboard 
 2 cascade
 8 rtc
 12 ps/2mouse
 13 fpu
 14 ide0
 15 ide1 
 NMI: 0

If you need any more information, please let me know.

I greatly appreciate any advice anyone can give.

thanks Preston Landers pbl@pbl.cx

None First suggestion would be a PCMCIA driver update

Re: Sad Presario 1210 / RE-100 / debian 2.2 / kernel 2.2.12 / pcmcia 3.1.8 (Preston Landers)
Date: 2000, Apr 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Try again with 3.1.14 and see if that sorts out the problem.  If not,
I have some other ideas...

-- Dave

Question RBEM56G-100 problems with pcmcia 3.1.14 and kern 2.2.14

Date: 2000, Apr 21
From: Brad Langhorst bwlang

I'm trying to get this card working...

When I insert it, I hear two high beeps very close together. The link light on the card is green and the activity light flashes. Cardinfo lists the card properly. eth0 exists and is bound to the proper address In other words it appears to be working.

However, when i ping any address except my own i get no response. Nothing seems to get logged in /var/log/messages and i get no visible errors - just no responses.

The card is using irq 1l and IO 0x400-0x487 it is listed as ready and has devices eth0, ttyS2

I get about 30 lines in /var/log/messages but nothing unusual.

Any suggestions?

thanks

brad

None Re: Question: RBEM56G-100 problems with pcmcia 3.1.14 and kern 2.2.14

Re: Question RBEM56G-100 problems with pcmcia 3.1.14 and kern 2.2.14 (Brad Langhorst)
Date: 2000, Apr 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

This driver is troublesome so you may just be out of luck for now.  An
obvious question would be, does the modem work?  What kind of laptop
is this?  Does the output of "ifconfig" show that the interface is
configured correctly?  Does it show any packets sent and/or received
successfully?  Does /proc/interrupts show any activity?

And something suggested in the BUGS file is to try setting eth0 to
promisc mode ("ifconfig eth0 promisc") and see if that has any effect.

-- Dave

Ok promisc mode worked!

Re: None Re: Question: RBEM56G-100 problems with pcmcia 3.1.14 and kern 2.2.14 (David Hinds)
Date: 2000, Apr 21
From: Brad Langhorst bwlang

Setting my eth0 to promisc mode worked solved the problem - i guess i missed the bugs file (*SHAME*)

thanks

brad

Question Untitled

Re: Ok promisc mode worked! (Brad Langhorst)
Date: 2000, Jun 20
From: kato

Is there any way to add the "promisc" option the the standard redhat/mandrake network init.d script so my Xircom get's an address via dhcpcd automagically?

I seem to have to let the dhcpcd process fail on system start-up, then use the method that Stewart mentions below to initiate the network script again, open up another terminal and initiate a /sbin/ifconfig eth0 promisc so the Xircom grabs the address properly from the server.

Is there an easier way?

Thanks,

sji

Angry still NOT fixed in latest 3.1.16 snapshot

Re: None Re: Question: RBEM56G-100 problems with pcmcia 3.1.14 and kern 2.2.14 (David Hinds)
Date: 2000, Jun 06
From: Stewart Allen mrallen

The problem with promiscuous mode still exists in the latest 3.1.16 alpha/beta. I've been using this Xircom under Redhat (up to 6.2) with no problems and now I need the latest PCMCIA package to support the RayLink (WebGear Aviator) wireless card. Unfortunately, this breaks the Xircom. My laptop is a dhcp client and dhcpcd resets the interface flags when it starts so the 'ifconfig eth0 promisc' workaround doesn't work. There is a clumsy solution where I can start dhcpcd, pause it, run ifconfig then resume dhcpcd (in a shell as root), but this is a MAJOR pain. It seems this is broken all the way back to 3.1.8 (7 months ago)! How hard is this to fix, really? If it is working under RedHat 6.[012], why can't the working code get merged back in?

None So maybe it is not actually as easy as you think

Re: Angry still NOT fixed in latest 3.1.16 snapshot (Stewart Allen)
Date: 2000, Jun 07
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Trust me, I'm not sitting on patches that fix the problem just to
annoy people.

There now seem to be at least three different versions of the Xircom
cards, and I don't know how to tell them apart.  And the differences
do not appear to be documented in the Xircom supplied documentation.
And I really would rather not be wasting my time trying to reverse
engineer broken hardware that I don't even have access to.  The one
Xircom CBEM56G-100 card that I do have access to, works without the
promisc workaround for the first time with 3.1.15.

I've already gone through several rounds of "this driver is broken;
here, this patch fixes it"... I apply the patch... and three months
later I start hearing from people who say the old driver worked and
the new one doesn't, and other people say the opposite.

I have always recommended not using these cards and the driver has
always been called "experimental".  And no one has stepped forward
to maintain this driver.  So I guess if no one actually cares enough
to see to it that the problems are fixed, they are unlikely to be
fixed.  That's how open source software works.

-- Dave

Question Xircom CBE2BTX

Date: 2000, Apr 30
From: Ram Prasad rampras

Can anyone please tell me how to configure Xircom CBE2-100BTX Network Card on IBM 600x thinkpad ?

Question Xircom RealPort 10/100 and loading module twice?

Date: 2000, May 01
From: Cody Pisto thunder

I have a Xircom RealPort 10/100 ethernet pcmcia card on my toshiba tecra 720cdt using pcmcia-cs and modules 3.1.14 when i boot or otherwise insert the card, the laptop beeps twice and i see in dmesg output that the driver module has been loaded twice, everything works, i just want to know if there is a way i can stop the driver from beeping twice and loading twice.

Thanks in advance

More forgot to note, its kernel 2.2.14

Re: Question Xircom RealPort 10/100 and loading module twice? (Cody Pisto)
Date: 2000, May 01
From: Cody Pisto thunder

topic

None You may just have to live with it

Re: Question Xircom RealPort 10/100 and loading module twice? (Cody Pisto)
Date: 2000, May 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You should normally get two beeps with the driver loading once: the
first beep indicates "card was identified" and the second beep
indicates "card was configured".  If the log indicates the driver was
loaded twice, then that's a problem.  But since this is a Toshiba
chipset, I'm inclined to say "sorry, just deal with it"; these chips
behave strangely and I don't have adequate documentation.  And there
are multiple chip versions that I don't know how to distinguish.

-- Dave

Feedback If you got that card to work in THAT machine at all, count your blessings.

Re: Question Xircom RealPort 10/100 and loading module twice? (Cody Pisto)
Date: 2000, Jul 13
From: Jasen Gibson jasen666

no text

Question What should I buy: CardBus or PCMCIA?

Date: 2000, May 03
From: Pieter Hollants fate

Which Xircom card would you currently recommend for buying: the CreditCard 10/100 + 56k CardBus Variant or the PCMCIA variant? I'm not sure if CardBus really offers that much more performance.

None CardBus is only faster if the driver works

Re: Question What should I buy: CardBus or PCMCIA? (Pieter Hollants)
Date: 2000, May 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The Linux driver for the Xircom CardBus cards is somewhat flaky, and I
don't recommend it at this time.

-- Dave

Question RBEM56G-100 & Red Hat 6.2

Date: 2000, May 03
From: Marco A. Calamari marcoc

I'm trying to use a Xircom Cardbus ethernet 10/100+modem 56 (RBEM56G-100) with an Acer Travelmate 515TE and RedHat 6.2 (kernel 2.2.14)

The card self initialize with tulip_ce, and seems to work, autoselecting irq2 & io200.

Ifconfig show hardware address and (using promiscuos mode, as suggested by another message here) I can see the packet count rise.

The problem is that ping doesn't work, and all packet read are
 dropped; packet written give an error.

I suspected that the card is working at 100Mb, and all my network is 10Mb, but if connect to a 100Mb port the amber light detect the change, bu the situation (dropped all packet) doesn't change

I updated firmware to 2.66, but without any change.

Also using xirc2ps_cs give no change

Any idea ? Thanks a lot for your time.

Have a good day. Marco

None Need more detailed information

Re: Question RBEM56G-100 & Red Hat 6.2 (Marco A. Calamari)
Date: 2000, May 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Some obvious questions:

You say you get "an error" when you transmit packets.  What does that
mean?  Is the error in your system log?  Are there any other messages
from the driver in your system log?

I don't understand how the packet count can rise, but also "all
packets read are dropped".

> Also using xirc2ps_cs give no change

That's not possible (that there could be no change): you can't use
xirc2ps_cs with a CardBus card.  You would get low beeps, error
messages in your system log, etc.

-- Dave

None Re: Need more detailed information

Re: None Need more detailed information (David Hinds)
Date: 2000, May 04
From: Marco A. Calamari marcoc

At 11.10 03/05/00 -0700, David Hinds wrote:f you reply to this message at 
HyperNews@pcmcia.sourceforge.org, include:
In-Reply-To: <20000503112308.K19394@valinux.com>

....

>You say you get "an error" when you transmit packets.  What does that
>mean?  Is the error in your system log?  Are there any other messages
>from the driver in your system log?
>
>I don't understand how the packet count can rise, but also "all
>packets read are dropped".

First, sorry for the bad style of my previous posting,
  that was written in hurry.

The firmware revision of the pcmcia is now 2.66, but nothing change.

I mean that, using ifconfig, I see the packet count of dropped packet
  rising.

Attached, the messages from ifconfig, the output from lsmod,
  and the boot messages about the pcmcia&network

[root@ef19 /root]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:10:A4:E9:5D:0B
           inet addr:161.27.167.181  Bcast:161.27.167.255  Mask:255.255.255.128
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:349 overruns:0 frame:0
           TX packets:0 errors:1 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:100
           Interrupt:3 Base address:0x200

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           UP LOOPBACK RUNNING  MTU:3924  Metric:1
           RX packets:15 errors:0 dropped:0 overruns:0 frame:0
           TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0


           [root@ef19 /root]# lsmod
           Module                  Size  Used by
           serial_cb               1080   1
           tulip_cb               30924   2
           cb_enabler              2568   4  [serial_cb tulip_cb]
           ds                      6696   2  [cb_enabler]
           i82365                 29800   2
           pcmcia_core            44480   0  [cb_enabler ds i82365]
           nls_iso8859-1           2240   1  (autoclean)
           nls_cp437               3748   1  (autoclean)
           vfat                    9276   1  (autoclean)
           fat                    30336   1  (autoclean) [vfat]
           esssolo1               20720   0
           soundcore               2628   4  [esssolo1]
           [root@ef19 /root]#


May  4 10:26:41 ef19 network: Setting network parameters succeeded
May  4 10:26:42 ef19 network: Bringing up interface lo succeeded
May  4 10:26:42 ef19 insmod: /lib/modules/2.2.14-5.0/pcmcia/ds.o: 
init_module: Device or resource busy
May  4 10:26:42 ef19 ifup: Delaying eth0 initialization.
May  4 10:26:42 ef19 network: Bringing up interface eth0 failed
May  4 10:26:42 ef19 portmap: portmap startup succeeded
May  4 10:26:42 ef19 random: Initializing random number generator succeeded
May  4 10:26:45 ef19 crond: crond startup succeeded
May  4 10:26:45 ef19 pcmcia: Starting PCMCIA services:
May  4 10:26:46 ef19 pcmcia:  modules
May  4 10:26:46 ef19 kernel: Linux PCMCIA Card Services 3.1.8
May  4 10:26:46 ef19 kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 
21:07:39 EST 2000
May  4 10:26:46 ef19 kernel:   options:  [pci] [cardbus] [apm]
May  4 10:26:46 ef19 kernel: Intel PCIC probe:
May  4 10:26:46 ef19 kernel:   O2Micro OZ6832/OZ6833 PCI-to-CardBus at bus 
0 slot 19, mem 0x68000000, 2 sockets
May  4 10:26:46 ef19 kernel:     host opts [0]: [a 44] [b a1] [c 20] [d 06] 
[mhpg 18] [fifo 00] [e 28] [no pci irq] [lat 32/176] [bus 32/34]
May  4 10:26:46 ef19 kernel:     host opts [1]: [a 44] [b ad] [c 20] [d 06] 
[mhpg 18] [fifo 00] [e 28] [no pci irq] [lat 32/176] [bus 35/37]
May  4 10:26:46 ef19 kernel:     ISA irqs (default) = 3,4,7,11,12 polling 
interval = 1000 ms
May  4 10:26:46 ef19 pcmcia:  cardmgr.
May  4 10:26:46 ef19 cardmgr[349]: starting, version is 3.1.8
May  4 10:26:46 ef19 rc: Starting pcmcia succeeded
May  4 10:26:46 ef19 cardmgr[349]: watching 2 sockets
May  4 10:26:46 ef19 kernel: cs: IO port probe 0x1000-0x17ff: clean.
May  4 10:26:46 ef19 kernel: cs: IO port probe 0x0100-0x04ff: excluding 
0x378-0x37f 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
May  4 10:26:46 ef19 kernel: cs: IO port probe 0x0a00-0x0aff: clean.
May  4 10:26:46 ef19 kernel: cs: cb_alloc(bus 35): vendor 0x115d, device 0x0003
May  4 10:26:46 ef19 cardmgr[349]: initializing socket 1
May  4 10:26:46 ef19 cardmgr[349]: socket 1: Xircom CardBus 10/100 Ethernet 
+ 56K Modem
May  4 10:26:46 ef19 lpd: lpd startup succeeded
May  4 10:26:46 ef19 lpd[363]: restarted
May  4 10:26:46 ef19 cardmgr[349]: executing: 'insmod 
/lib/modules/2.2.14-5.0/pcmcia/cb_enabler.o'
May  4 10:26:46 ef19 cardmgr[349]: executing: 'insmod 
/lib/modules/2.2.14-5.0/pcmcia/tulip_cb.o'
May  4 10:26:46 ef19 cardmgr[349]: executing: 'insmod 
/lib/modules/2.2.14-5.0/pcmcia/serial_cb.o'
May  4 10:26:46 ef19 kernel: cs: cb_config(bus 35)
May  4 10:26:46 ef19 kernel:   fn 0 bar 2: mem 0x60013000-0x600137ff
May  4 10:26:46 ef19 kernel:   fn 0 bar 3: mem 0x60012000-0x600127ff
May  4 10:26:46 ef19 kernel:   fn 1 bar 1: io 0x280-0x287
May  4 10:26:46 ef19 kernel:   fn 1 bar 2: mem 0x60011000-0x600117ff
May  4 10:26:46 ef19 kernel:   fn 1 bar 3: mem 0x60010000-0x600107ff
May  4 10:26:46 ef19 kernel:   fn 0 bar 1: io 0x200-0x27f
May  4 10:26:46 ef19 kernel:   fn 0 rom: mem 0x6000c000-0x6000ffff
May  4 10:26:47 ef19 kernel:   fn 1 rom: mem 0x60008000-0x6000bfff
May  4 10:26:47 ef19 kernel: tulip_attach(bus 35, function 0)
May  4 10:26:47 ef19 kernel: tulip.c:v0.91 4/14/99 
becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for 
XIRCOM CBE, fixed by Doug Ledford)
May  4 10:26:47 ef19 kernel: eth0: Xircom Cardbus Adapter (DEC 21143 
compatible mode) rev 3 at 0x200, 00:10:A4:E9:5D:0B, IRQ 3.
May  4 10:26:47 ef19 kernel: eth0:  MII transceiver #0 config 3100 status 
7809 advertising 01e1.
May  4 10:26:47 ef19 kernel: serial_attach(bus 35, fn 1)


> > Also using xirc2ps_cs give no change
>
>That's not possible (that there could be no change): you can't use
>xirc2ps_cs with a CardBus card.  You would get low beeps, error
>messages in your system log, etc.

I mean that in this situation nothing changed (I know that there
  are two pccard driver).

           [root@ef19 /root]# lsmod
           Module                  Size  Used by
           serial_cb               1080   1
           tulip_cb               30924   2
           cb_enabler              2568   4  [serial_cb tulip_cb]
           xirc2ps_cs             13856   0  (autoclean) (unused)
           ds                      6696   2  [cb_enabler xirc2ps_cs]
           i82365                 29800   2
           pcmcia_core            44480   0  [cb_enabler xirc2ps_cs ds i82365]
           nls_iso8859-1           2240   1  (autoclean)
           nls_cp437               3748   1  (autoclean)
           vfat                    9276   1  (autoclean)
           fat                    30336   1  (autoclean) [vfat]
           esssolo1               20720   0
           soundcore               2628   4  [esssolo1]

Thanks a lot and have a good day.   Marco





* Mac (Marco A. Calamari) marcoc@dada.it  www.dada.it/marcoc *
* PGP RSA: ED84 3839 6C4D 3FFE 389F 209E 3128 5698           *
* DSS/DH:  8F3E 5BAE 906F B416 9242 1C10 8661 24A9 BFCE 822B *

None SOLUTION !

Re: None Re: Need more detailed information (Marco A. Calamari)
Date: 2000, May 05
From: Marco A. Calamari marcoc

At 03.27 04/05/00 -0700, you wrote:

If you reply to this message at HyperNews@pcmcia.sourceforge.org, include:
In-Reply-To: <4.3.1.2.20000504101706.00a89cc0@mail.dada.it>

Upgrading to PCMCIA card manager & drivers solve the problem.

Just a minor quirks; in my case (RH 6.2) the delayed initialization
  due to the relative position of the pcmcia & network init
  file in rcX.d don't complete the route initialization.

Doing a network restart after every boot or renaming all occurrencies of 
S10network
  in S46network and reboot once obviously solve the problem.

Thanks a lot to David and have a good day.   Marco








* Mac (Marco A. Calamari) marcoc@dada.it  www.dada.it/marcoc *
* PGP RSA: ED84 3839 6C4D 3FFE 389F 209E 3128 5698           *
* DSS/DH:  8F3E 5BAE 906F B416 9242 1C10 8661 24A9 BFCE 822B *

Ok SOLUTION! (part two)

Re: None Need more detailed information (David Hinds)
Date: 2000, May 05
From: Marco A. Calamari marcoc

Oops. I missed the revison number 8-(

I mean Card Manager 3.1.14, as suggested by David.

Sorry for the double mailing. Marco

News Xircom CardBus driver update

Date: 2000, May 04
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The 04-May-00 beta on sourceforge.org in /pcmcia/NEW has a change in how the tulip_cb driver configures the receive filter for Xircom cards. It should fix cards that previously had to be put in promiscuous mode to receive packets.

I think there are some Xircom cards that behave differently, and this driver update may make things worse for them. If that's true, I want to hear about it, so I can figure out what is different about those cards, and hopefully come up with a driver that works for everyone.

-- Dave

Question Same linux kernel, but getting unresolved symbols with xirc2ps_cs.o

Date: 2000, May 11
From: Tony Sciortino tsciortino

I am using pcmcia 3.1.14 with kernel 2.2.13 When I am running under Caldera 2.3 and insert my Xircom CEM56-100 is works 100% When I am running under another linux brand same kernel with modules copied from the caldera side I get a page full of unresolved symbols. And this is only with the xirc2ps_cs.o module. The serial and ide modules work perfect. Any ideas?

-Tony

None Same kernel version, only different

Re: Question Same linux kernel, but getting unresolved symbols with xirc2ps_cs.o (Tony Sciortino)
Date: 2000, May 11
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Your two kernels were compiled with different networking settings.
Some of those settings affect kernel interfaces and change the version
information coded in the module symbols.  Kernel modules generally
need to be recompiled to match your kernel configuration, even if the
kernel version is unchanged.

-- Dave

Sad RBEM56G-100BTX w/ RedHat Linux 6.2

Date: 2000, May 13
From: Mark Ambrose <caffeine23@hotmail.com>

Hello...there seems to be a lot of problems with this card but
I thought I would throw a new problem in that I can't see has
happened before.

I have downloaded the latest pcmcia package from the 
sourceforge FTP site..(May 12 release) and installed it.
My modem and ethernet worked fine...even with multiple WARM
reboots. However, after a COLD startup, Linux failed to boot
as soon as it started the PCMCIA services. It said "OK"..then
it seemed to get stuck. (this was with the card inserted). I 
then COLD rebooted without the card in and everything loaded
fine. When I was in, I restarted PCMCIA services and inserted 
the card...there was 1 beep and the system froze...I couldn't
do anything except turn it off.

My system is an HP OmniBook 4150 PIII 650MHz..

Any help would be greatly appreciated...

Thanks, Mark

Question Same Problem using Mandrake 7.0 and Omnibook 4150

Re: Sad RBEM56G-100BTX w/ RedHat Linux 6.2 (Mark Ambrose)
Date: 2000, May 15
From: Mike Brekke mbrekke

We are using the 2.2.14 Kernel and the Ethernet works fine after a warm reboot, but not on a cold boot. I did not install a new version of PCMCIA. I have tried changing the order of services in rc.d and no combination works successfully on a cold start up. Normally on a laptop startup I will get an error when network starts before PCMCIA services, but the network starts up fine eventually once the PCMCIA starts. I have another Ositech Jack O' Spades CardBus card that works fine once I change the services start order in the appropriate rc.d directory. Should I update PCMCIA? Is there a specific driver available for this card? Any suggestions would be greatly appreciated.

Sad Me too! must be something with Omnibook 4150s...

Re: Sad RBEM56G-100BTX w/ RedHat Linux 6.2 (Mark Ambrose)
Date: 2000, May 15
From: Mauro Cicognini mcicogni

I have been having the same problem for some time, now. I was really glad the card worked out of the box, but I soon discovered the cold-boot problem which invariably hangs the machine no matter what I try.

I'm running a plain RedHat 6.2 system on the Omnibook 4150B, Pentium II 450, 128 MB RAM, 4GB HD partitioned to let Win98 coexist with Linux (1GB to Windows, 3GB to LINUX, and the hybernation partition, with LILO taking care of all boots)

I have not yet had a chance to upgrade PCMCIA; I meant to, but right now I'm starting to wonder if the issue couldn't be on how the Omnibook 4150 deals with PCI interrupts.

Unfortunately I obviously cannot look into interrupts when things don't work... :(

Does anyone have a clue?

Thanx in advance Mauro Cicognini

Agree OmniBook 4150 problem ???

Re: Sad Me too! must be something with Omnibook 4150s... (Mauro Cicognini)
Date: 2000, May 15
From: Mark Ambrose <caffeine23@hotmail.com>

Yes...your symptoms sound exactly the same as mine. I have an
OmniBook PIII 650MHz, 256MB RAM, 18.1GB HDD...seems that the
version of OmniBook doesn't make a difference.

I have successfully used this card under both Windows '98 and
Windows 2000...no problems with either of those. I have also
installed the latest PCMCIA drivers (May 12 release) and this
didn't fix it either...so I can't see any point in either of
you trying this...but by all means do if you think it will 
help.

I compiled the PCMCIA driver with both PnP support and no PnP
support and this didn't change anything either. 
/var/log/messages shows that the card was detected fine (1st
beep) but it fails to configure it properly (no 2nd beep).

If anyone has any other ideas with this, I would certainly 
appreciate the input....

Like before, I am running a stock RedHat 6.2 kernel with the
latest PCMCIA package installed (May 12 release from 
sourceforge FTP)....

Thanks 

Mark

None I don't think I quite understand the issue

Re: Agree OmniBook 4150 problem ??? (Mark Ambrose)
Date: 2000, May 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You're saying that the card works fine if you warm boot... from
windows maybe?  (no one actually said)

The most obvious thing to do would be to compare the PCMCIA startup 
messages for a cold boot versus a warm boot.

-- Dave

Feedback Tried diff'ing the messages, but no clues

Re: None I don't think I quite understand the issue (David Hinds)
Date: 2000, May 16
From: Mauro Cicognini mcicogni

Hi David,

It doesn't matter if I warm boot from Linux or Win98, the effect is the same. If I try to cold boot Linux with the card inserted, the system freezes (even ctrl-alt-del doesn't work) after the first cardmgr beep. Inserting the card after the boot is complete has the same effect (i.e. the system freezes instantly, although sometimes it manages to emit both beeps).

However, if I warm boot, either from Win98 or from Linux (with no card inserted, in this case) everything works fine and the card is completely functional (i.e. Eth 10/100 autosense, 56K modem, etc.), either letting the cardmanager discover the card during boot or inserting it afterwards.

I followed your advice and tried to compare the messages from a cold boot vs. a warm boot. I obviously have no messages from a situation where the system freezes :)

And sadly this gave me no clue: the messages appear to be exactly the same, apart from a slightly different order at times, which I think could be perfectly normal, and a marked difference in the detected CPU speeds, which I don't know to make of, but I doubt could be relevant in this case.

I also captured /proc/interrupts, /proc/ioports and /proc/pci after a cold boot, after warm boot and after inserting the card and could find no difference (obviously there are differences after I insert the card, but only to show the card being there).

I am not attaching anything, since I don't think there could be any relevant information in my data. It looks like we're just out of luck and the Omnibook 4150 with Linux doesn't like the RBEM56G-100TX until after a warm boot.

If anyone has any advice, please let me know.

Best regards Mauro

Feedback 4150B's flakier than 4150A's

Re: Feedback Tried diff'ing the messages, but no clues (Mauro Cicognini)
Date: 2000, Jun 14
From: Dave Worthy <dave_worthy@hp.com>

I'm building images for Omnibook 4150B's and they are seeing this hanging at pcmcia startup. These machines are dual booted(RH6.1 and NT) and strangely enough after booting to NT 4.0sp5, if you reboot to linux, the freeze symptom goes away and pcmcia starts right up.

We're running RH6.1. I had tried RH6.2 but when it froze on pcmcia and the promiscuous mode didn't work, I went back to the version I'm running personally on a 4150A(RH6.1); which (other than the modem) works fine(pcmcia-3.1.3-10). On the 4150B not as much luck. I've not downloaded the latest and greatest pcmcia bits, however from what I've read, this sounds like a longshot anyway.

I've been battling the modem on the RBEM56G-100 for a couple of months and per David's advice on this troublesome beast, have recently sent an order for both the non-cardbus REM56G AND the 3com card that made his approved list.

-Dave-

Question Something new to try?

Re: Sad RBEM56G-100BTX w/ RedHat Linux 6.2 (Mark Ambrose)
Date: 2000, Jul 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

First get the 13-Jul-00 beta from sourceforge.org in /pcmcia/NEW. That may help by itself. Then try setting:

    CORE_OPTS="reset_time=1000 unreset_delay=100"

in /etc/sysconfig/pcmcia and see if that changes anything.

-- Dave

Question Xircom CBE-10/100BTX woes

Date: 2000, May 14
From: Andrew Branch AndyB

Hi,

I hope someone can point me in the right direction with this.

Distribution: SuSE 6.4 Kernel: Stock SuSE 6.4 - 2.2.14 PCMCIA version: 3.1.15 Card: Xircom CBE-10/100BTX

I now have a recognised card after adding
card "Xircom CardBus 10/100 Ethernet"
  manfid 0x0105, 0x0102
  bind "tulip_cb"

to the /etc/pcmcia/config file

I can ping my address on the laptop, however when I can't ping any other address it just sits there doing nothing.

I had a look in /var/log/messages and I was getting the following lines repeated continuously:

May 14 09:01:41 legolas kernel: eth0: Tx hung, 25 vs. 1.
May 14 09:01:41 legolas kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 fffbffff 8ff00008, resetting...
May 14 09:01:47 legolas kernel: eth0: Tx hung, 25 vs. 1.
May 14 09:01:47 legolas kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 fffbffff 8ffa0008, resetting...
May 14 09:01:53 legolas kernel: eth0: Tx hung, 25 vs. 1.
May 14 09:01:53 legolas kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 fffbffff 8ff00008, resetting...

When I removed the card and re-inserted it I got the following (I don't know if it is relevant):

May 14 09:02:28 legolas kernel: tulip_detach(eth0)
May 14 09:02:28 legolas kernel: cs: cb_disable(bus 32)
May 14 09:02:28 legolas kernel: cs: cb_release(bus 32)
May 14 09:02:28 legolas kernel: cs: cb_free(bus 32)
May 14 09:02:28 legolas cardmgr[474]: shutting down socket 0
May 14 09:02:28 legolas cardmgr[474]: executing: './network stop eth0'
May 14 09:02:28 legolas cardmgr[474]: + ./network: /etc/pcmcia/wireless.opts: line 61: syntax error near unexpected token `(N'
May 14 09:02:28 legolas cardmgr[474]: + ./network: /etc/pcmcia/wireless.opts: line 61: `    INFO="Netwave example (Netwave default settings)'
May 14 09:02:28 legolas cardmgr[474]: executing: 'modprobe -r tulip_cb'
May 14 09:03:23 legolas kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019
May 14 09:03:23 legolas cardmgr[474]: initializing socket 0
May 14 09:03:23 legolas kernel: ROM image dump:
May 14 09:03:23 legolas kernel:   image 0: 0x000000-0x0001ff, signature PCIR
May 14 09:03:23 legolas cardmgr[474]: socket 0: Xircom CardBus 10/100 Ethernet
May 14 09:03:24 legolas cardmgr[474]: executing: 'modprobe tulip_cb'
May 14 09:03:24 legolas kernel: cs: cb_config(bus 32)
May 14 09:03:24 legolas kernel:   fn 0 bar 1: io 0x400-0x47f
May 14 09:03:24 legolas kernel:   fn 0 bar 2: mem 0x600c0000-0x600c007f
May 14 09:03:24 legolas kernel:   fn 0 rom: mem 0x60080000-0x600bffff
May 14 09:03:24 legolas kernel: cs: cb_enable(bus 32)
May 14 09:03:24 legolas kernel:   bridge io map 0 (flags 0x21): 0x400-0x47f
May 14 09:03:24 legolas kernel:   bridge mem map 0 (flags 0x1): 0x60080000-0x600c0fff
May 14 09:03:24 legolas kernel: tulip_attach(device 20:00.0)
May 14 09:03:24 legolas kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
May 14 09:03:24 legolas kernel: eth0: Digital DS21143 Tulip rev 48 at 0x400, EEPROM not present, 00:4C:69:6E:75:79, IRQ 11.
May 14 09:03:24 legolas cardmgr[474]: executing: './network start eth0'
May 14 09:03:24 legolas cardmgr[474]: + ./network: /etc/pcmcia/wireless.opts: line 61: syntax error near unexpected token `(N'
May 14 09:03:24 legolas cardmgr[474]: + ./network: /etc/pcmcia/wireless.opts: line 61: `    INFO="Netwave example (Netwave default settings)'

If anyone needs any extra information please ask. I have never been able to get this card going under Linux (I have tried previously)

Thanks, Andrew Branch.

None This card is not supported and just does not work

Re: Question Xircom CBE-10/100BTX woes (Andrew Branch)
Date: 2000, May 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You will not be able to get this to work.  This card is expliclty
listed as unsupported in the supported-cards list.

-- Dave

Question Trouble with Xircom 10/100 & IrDA (Thinkpad 390X)

Date: 2000, May 18
From: Roberto Totaro roto

Hi.

I installed Linux on a IBM Thinkpad 390X and I am experiencing some trouble when I try to use both the IrDA interface and my Xircom CreditCard Ethernet 10/100.

First of all, I am using Linux version 2.2.15 with the latest IrDA patches, irda-utils 0.9.9 and version 3.1.14 of the PCMCIA drivers.

Normally (i.e. when I do not try to use the IrDA if) the network card driver allocates irq 3, although on the 390X the IrDA uart (16550A) is set up by default as /dev/ttyS1 (port 0x2f8, irq 3). This means that if I start the IrDA subsystem AFTER the network and try to attach the IrDA interface to /dev/ttyS1, irattach will fail with an obscure error message ("tcsetattr: Input/output error").

When I realized there was a hw conflict, I cleverly (sic!) thought of starting the IrDA daemon and calling irattach before I started the PCMCIA software. Now the network card driver was forced to use irq 9 and, though the IrDA interface now works fine, the network does not any more.

Has anyone already had a similar problem? any ideas about how to solve it?

Thanks in advance for your help!

Roberto

None /etc/pcmcia/config.opts settings

Re: Question Trouble with Xircom 10/100 & IrDA (Thinkpad 390X) (Roberto Totaro)
Date: 2000, May 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Your /etc/pcmcia/config.opts file lets you specify interrupts that
should not be used for PCMCIA cards.  It sounds like you need to add
"exclude irq 3" to that file.

If irq 9 doesn't work, then add an "exclude irq 9" line also.
Hopefully you'll find one that works before you run out of interrupts.

-- Dave

Ok Success - RealPort2 10/100BTX

Date: 2000, May 18
From: Tony Hoyle TonyHoyle

I thought I'd post here (apologies if this is old news, but I couldn't find any reference elsewhere). I have a Xircom RealPort2 Cardbus Ethernet 10/100.

Details from syslog: "Xircom", "RealPort2 CardBus Ethernet 10/100", "R2BE-100BTX", "1.00" manfid: 0x0105, 0x0103 function: 6 (network)

I have this working successfully using the tulib_cb driver. I'm not sure of the format of the 'config' file but the following worked for me:

card "Xircom RealPort2 CardBus Ethernet 10/100"
  manfid 0x0105, 0x0103
  bind "tulip_cb"

Hope this helps.

Tony

Question Problem with Xircom CE3-100BTX

Date: 2000, May 19
From: Ralf Boettger perabo

Hi everybody,

I just bought a used Xircom Credit-Card 10/100 Ethernet
(CE3B-100BTX) and I have problems with this card under
Linux. Using the card with Windows 98 makes no problems, 
10MBit-Lan with Hub, 100Mbit with a cross-over-cable, 
everything works fine and I think there is no problem with
the card itself.

I have the following problem:card is recognized under Linux,
the right driver is loaded (xirc2ps_cs), IRQ/IO/Memory are OK 
and there are no conflicts with other hardware, the interface
eth0 is set up right, routing is built up, everything looks fine and OK.
 
The Xircom-Cable has 2 LEDs, in 10MBit-Mode one LED is 
shining green (with 10MBit the notebook is connected to a
hub), making a ping to another computer resulting to a short
shining of the yellow LED of the card. So, everything is OK
as it should be.
 
BUT: the hub never receives anything from the credit-card,
even the LED at the hub for the notebook-cable is not shining.
I.e. for the hub the notebook is not connected and no signal
is coming to the hub. I tried everything: different IRQs, IOs,
Memory-settings, nothing helps. Output of the various tools
(cardctl, cardmgr, ifconfig) is correct, I can't find any
error, even in the system-log no failure is shown.
 
I tried to use a cross-over-cable, same behaviour, card is
recognized and initialised,network is built up correctly, ping
works, the LED is shining yellow for a short time, but the
other computer gets nothing.
 
My configuration:
 - SuSE 6.4 with Kernel 2.2.14
 - pcmcia 3.1.14
 
Is there anybody making similiar experiences and maybe having
a solution ?!?! I have absolutely no idea what the problem is
and I am very grateful about every hint. Unfortunately I
have no possibility to put the system log today, but maybe
somebody have a hint for me.
 
Bye, Ralf.

Sad Again my problem with the Xircom-Card

Re: Question Problem with Xircom CE3-100BTX (Ralf Boettger)
Date: 2000, May 21
From: Ralf Boettger perabo

Hi again,
 
I have done some further examinations about my
problem with the Xircom-Card. Here are the result
from the german jury:
- A setting with ifport eth0 never works, every
  time the message comes back (independent if a
  switch to 100BaseT, 10BaseT, ... should be done):
  eth0: media 10Base2, silicon revision 4 (see system
  log below).
- I took a look at xirc2ps_cs.c. The problem
  is the function init_mii(dev), this function
  ever returns false (0), so the detection of
  other than 10Base2 can't be possible (what the
  hell is MII ?!?!).
- Is it possible with that driver to use a
  Xircom CE3-10/100 ? Is there anybody with a running
  card of that type ?
 
Is there anybody outthere who can help me with
the xirc2ps_cs driver ? In the code the URL
xirc2ps.linuxbox.com is mentioned but this URL
is not valid. Is there any existing and valid
mailing-adress or URL about this driver ?
 
Kind regards,
Ralf.
 
A cut of the system log:
 
May 21 21:01:27 soeren rcpcmcia: /sbin/insmod /lib/modules/2.2.14/pcmcia/pcmcia_core.o
May 21 21:01:27 soeren kernel: Linux PCMCIA Card Services 3.1.15
May 21 21:01:27 soeren kernel:   kernel build: 2.2.14 #1 Sat Mar 25 00:45:35 GMT 2000
May 21 21:01:27 soeren kernel:   options:  [pci] [cardbus]
May 21 21:01:27 soeren kernel: PCI routing table version 1.0 at 0xfd890
May 21 21:01:27 soeren kernel:   unknown PCI interrupt router 1045:c701
May 21 21:01:27 soeren rcpcmcia: /sbin/insmod /lib/modules/2.2.14/pcmcia/i82365.o
May 21 21:01:28 soeren kernel: Intel PCIC probe:
May 21 21:01:28 soeren kernel:   O2Micro OZ6836/60 rev 60 PCI-to-CardBus at slot 00:07, mem 0x68000000
May 21 21:01:28 soeren kernel:     host opts [0]: [ring] [pci/way] [pci irq 10] [lat 168/176] [bus 32/34]
May 21 21:01:28 soeren kernel:     host opts [1]: [ring] [pci/way] [pci irq 10] [lat 168/176] [bus 35/37]
May 21 21:01:28 soeren kernel:     ISA irqs (default) = 3,4,7,9 PCI status changes
May 21 21:01:28 soeren rcpcmcia: /sbin/insmod /lib/modules/2.2.14/pcmcia/ds.o
May 21 21:01:28 soeren cardmgr[632]: starting, version is 3.1.15
May 21 21:01:28 soeren cardmgr[632]: watching 2 sockets
May 21 21:01:28 soeren kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
May 21 21:01:28 soeren kernel: cs: IO port probe 0x0800-0x08ff: clean.
May 21 21:01:28 soeren kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x398-0x39f 0x3f8-0x3ff 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
May 21 21:01:28 soeren cardmgr[632]: initializing socket 0
May 21 21:01:28 soeren kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa00fffff
May 21 21:01:28 soeren cardmgr[632]: socket 0: Xircom CE3-10/100 Fast Ethernet
May 21 21:01:28 soeren cardmgr[632]: executing: 'modprobe xirc2ps_cs'
May 21 21:01:29 soeren kernel: xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh)
May 21 21:01:29 soeren kernel: eth0: Xircom: port 0x300, irq 7, hwaddr 00:80:C7:71:EA:93
May 21 21:01:29 soeren cardmgr[632]: executing: './network start eth0'
May 21 21:01:29 soeren kernel: eth0: switching to 100BaseT port
May 21 21:01:29 soeren kernel: eth0: media 10Base2, silicon revision 4
May 21 21:01:30 soeren kernel: eth0: media 10Base2, silicon revision 4
May 21 21:01:30 soeren PCMCIA: Shutting down Name Service Cache Daemon^[[71G^[[32mdone^[[m
May 21 21:01:32 soeren PCMCIA: Starting Name Service Cache Daemon^[[71G^[[32mdone^[[m
May 21 21:01:32 soeren cardmgr[632]: initializing socket 1
May 21 21:01:32 soeren cardmgr[632]: socket 1: Serial or Modem
May 21 21:01:32 soeren cardmgr[632]: executing: 'modprobe serial_cs'
May 21 21:01:32 soeren kernel: Serial driver version 4.27 with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ enabled
May 21 21:01:32 soeren kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
May 21 21:01:32 soeren kernel: tty01 at 0x02f8 (irq = 9) is a 16550A
May 21 21:01:32 soeren cardmgr[632]: executing: './serial start ttyS1'
May 21 21:02:31 soeren kernel: eth0: switching to 100BaseT port
May 21 21:02:32 soeren kernel: eth0: media 10Base2, silicon revision 4
May 21 21:02:35 soeren kernel: eth0: switching to 10BaseT port
May 21 21:02:36 soeren kernel: eth0: media 10Base2, silicon revision 4
May 21 21:02:38 soeren kernel: eth0: switching to AUI port
May 21 21:02:38 soeren kernel: eth0: media 10Base2, silicon revision 4

Question New experiences

Re: Question Problem with Xircom CE3-100BTX (Ralf Boettger)
Date: 2000, May 22
From: Ralf Boettger perabo

Hello,
 
today I borrow another Xircom-Card from my
company (a CEM33, 10Mbit Ethernet plus 33.6 
Modem), put it into my Notebook (no changing
of the configuration) and it is running without 
problems.
 
Result: The configuration of notebook and xircom-
            device is allright.
 
But now it is going heavy: The CE3-10/100 has 3 
connectors (2 x 16 Bit connector and one 2-Pin-
Connector). I got my CE3-100BTX with an LAN-
Adapter using all of the 3 connectors and with
that adapter the card is not running.
 
The card of my company has an adapter using only
the 16 Bit connector left of the card. Using the company-
adapter with my CE3-100BTX lead to a running card !!!!
Only 10Mbit speed, but better than nothing.
 
Now I have several questions:
- What is the function of the adapter, especially
  of the 3 connectors ?!?!
- Has Linux a problem with the 3 connectors or
  the adapter ?
- Is my adapter with 3 connectors defect ?
 
Has anybody made similiar experiences ?
 
Kind regards, Ralf

Feedback Same problem with RH6.1& CE3B-100BTX

Re: Question Problem with Xircom CE3-100BTX (Ralf Boettger)
Date: 2000, May 23
From: Thomas Nielsen thomanie

Hi,

I'm experiencing the same problems with my card. All looks OK. The laptop (Compaq LTE 4/75CX, RH6.1, kernel 2.2.12-20, xirc2ps_cs) brings up the network just fine, the green led is lit - but GW and other machines does never reply on ping...

Pinging my own ip works fine (because the driver never physically runs the packet through the card?)

Has anyone found/made a working solution for the CE3B-100BTX?

Thomas

Ok Solution for CE3B-100BTX :-)

Re: Question Problem with Xircom CE3-100BTX (Ralf Boettger)
Date: 2000, May 24
From: Thomas Nielsen thomanie

Hi,

Found a website describing who to modify the xirc2ps_cs driver to work with the CE3B-100BTX card. I implemented the (small!) change to the driver and recompiled it. Worked like magic :-)

Running RH6.1 on Compaq LTE 4/75CX, kernel 2.2.12-20 and pcmcia-cs-3.0.14 (from RH6.1).

Solution described at:

http://linux.comp.nus.edu.sg/support/doc/SoC-HOWTO/mini/SoC-Xircom-Patch-mini-HOWTO/

Thomas

None I think your problem was different and already fixed

Re: Ok Solution for CE3B-100BTX :-) (Thomas Nielsen)
Date: 2000, May 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The bug in the 3.0.14 drivers is fixed in newer PCMCIA driver
releases.  The problem described on that web page should not exist in
the current (3.1.15) package.

-- Dave

Feedback Patch is not working with my card

Re: None I think your problem was different and already fixed (David Hinds)
Date: 2000, May 25
From: Ralf Boettger perabo

Hi,

I think David is right. I take a look at the patch
suggested on the URL provided by Thomas. All 
changes in this patch are already included in
the current pcmcia-package.

Nevertheless I tried this patch (never give up),
but as expected my problem is not solved by the
patch.

In general, what is the difference between a
Xircom-Card CE3-100BTX and CE3B-100BTX ?!?
The single character 'B' seems to make a
great difference.....

On the back of my card I can find only the
text "CE3-10/100", is it a CE3 or CE3B ?
I suspect it's a CE3 and it will never 
run with my Linux-System.

Bye, Ralf.

Feedback label on card

Re: Feedback Patch is not working with my card (Ralf Boettger)
Date: 2000, May 25
From: Thomas Nielsen thomanie

Hi,

My card is labeled "CE3B-100BTX"on the back. It might be that you have the non-B (whatever it stands for - "Bulk"?) version... Couldn't find any info about it at xircom.com

Sorry about those false hopes I gave - my problems actually were identical to those you described earlier.

Thomas

None Re: Feedback: Patch is not working with my card

Re: Feedback Patch is not working with my card (Ralf Boettger)
Date: 2000, May 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

So your card is a CE3-100BTX, and not a CE3B-100BTX?  (your first
message specifically said you had a CE3B)

Both cards should work fine under Linux.  I have multiple reports of
the CE3 and CE3B working fine.

Try editing xirc2ps_cs.c and in init_mii(), take out the the part that
says "if ((status & 0xff00) != 0x7800) return 0;".

A "mii" is a media independent interface chip; it is a chip that
automatically senses the network speed and configures the card for
10baseT or 100baseT, at full or half duplex.  Your card should have
one, but it isn't being detected properly for some reason.

-- Dave

Question RBEM100-56 and 3.0.14 compared to 3.1.x driver

Date: 2000, May 19
From: Uwe Hahn uwe

Hi,

funny for me to have noticed all the time that the last driver that has worked with every kernel and this card is the 3.0.14 version. I have had perfect results with it every time. None of the 3.1.x drivers seem to work without a bugfix (promisc, etc.) What happened since the and why is this?

Greetings,

	<uwe>

Note Rougly same problem

Re: Question RBEM100-56 and 3.0.14 compared to 3.1.x driver (Uwe Hahn)
Date: 2000, Jun 05
From: Bas van der Linden JanJoost

I have rougly the same experience.

I had my Xircom RBEM-56G-100 working nicely under 
RH 5.1, running 2.0.36 and pcmcia-3.0.14. Everything worked,
both 10 and 100 MBit, as well as the 56K modem. I even managed
to poke some friends' eyes out with my setup :)

Then I upgraded to Mandrake 7.02, with a custom 2.2.14 kernel,
and patched pcmcia-3.1.14 in. That worked, but only for a
short period of time.

When downloading a big file (my homedir.tar wich is rougly 600
megabytes) onto my laptop I got these errors in
var/log/messages: 

kernel: tulip.c: outl_CSR6 too many attempts,csr5=0x600e8002

And after a while (after downloading 100-200 megabytes) the
download would stop and had to be restarted with an ifdown;
ifup.

And the modem refused to work, to even be initialised.

I haven't done anything with /etc/pcmcia/config.opts, because
the settings I had on my old setup (standard config, with
enlarged window) worked nicely.

I then downgraded to pcmcia-3.0.14 and upgraded the kernel to
2.2.15, wich produces the same errors in /var/log/messages.
However, the card doesn't seem to stall after a while. 
But the modem still refuses to work.

I understand that there are a whole lot of issues to be solved
with this card for it to work properly.

David: if you read this, tell me what information I can give
you concerning my card, apart from actually sending it to you
:)

I don't mind fsck-ing up my setup, as I currently have another
setup on my laptop wich allows for this card to work, so if
you want me to run software wich can crash my computer / eat
my /, that's fine with me. As long as you get the information
you want :)

Is there any way I can check the internal revision level of
this card?

Oh: and thanks for all the work so far!

Bas

Sad 10/100+56K (RBEM56G-100) initializes, looks good, but no traffic

Date: 2000, May 26
From: Robert Harris nomad

Kernel 2.2.16-pre2 (reports as 2.2.15 for sound) pcmcia 3.1.15 and may.25 Debian woody

On my 10/100 switch at home, the pcmcia lights up at 100mb full duplex, looks good, communicates great.

On my 10mb hub at work, it lights up, looks clean, but won't pass traffic, my messages file reports "icmp destination unreachable."

Putting a Megahertz 10mb card in with the same config looks good.

Robert

Question Can anyone advise a newbie on getting RBEN56G working ?

Date: 2000, Jun 03
From: Gordon Licence idxtb

I'm currently reasonably new to Linux, and am running SuSE 6.4 on a Dell Latitude CPi 400XT with a RBEM56G 10/100 Ethernet + Modem 56 PCMCIA card. SuSE has installed OK, but has not picked up the Ether or Modem card - I'm not too fussed about the ISDN.

Would any helpful soul out there care to tell me

(a) Whether the RBEM56G card is supported ?
(b) If it is, what do I need to do to get it working ?
    In simple terms :)

Thanx,

Gordon

Ok Newbie advise for Xircom RBEM56G

Re: Question Can anyone advise a newbie on getting RBEN56G working ? (Gordon Licence)
Date: 2000, Jun 10
From: Alberto Gonzalez Palomo matmota

> [...] am running SuSE 6.4 on a Dell Latitude CPi 400XT with
> a RBEM56G 10/100 Ethernet + Modem 56 PCMCIA card.
> SuSE has installed OK, but has not
> picked up the Ether or Modem card - I'm not too fussed about the
> ISDN.
> [...]
> (a) Whether the RBEM56G card is supported ?

  Sure as hell ;) I'm using one right now to send this message.

> (b) If it is, what do I need to do to get it working ?

  A few days ago I tried SuSE 6.4 and it got my card perfectly. I don't remember if I chose any special option in the install menu. Some Linux distros have an option in the install menu for activating PCMCIA support before installing, to be able to get the packages through it.

  You only need a recent version of pcmcia-cs. The one in SuSE 6.4 is more than adequate.
  Browse the SuSE help (in KDE, the chamaleon icon) for instructions on installing PCMCIA support.

  Once installed, insert the card, and it will make one 'beep', wich means the card has been recognized. A while later it will make another one: it if it sounds the same as the first, it's OK. If it has a lower pitch, or doesn't sound at all (will do if given enough time), you still have to configure your Ethernet connection.

  That's it: the card works. Read some docs and you will have it working right. The only quirk is that you could have to make a 'ifconfig eth0 promisc' (as root) to make the Ethernet part working right. This is documented in various messages above.

  And, of course, don't forget to "Read Those Fine Manuals" ;) (PCMCIA-Howto, SuSE Help, and the other messages in this list, at least)

Question Same problem

Re: Ok Newbie advise for Xircom RBEM56G (Alberto Gonzalez Palomo)
Date: 2000, Jun 12
From: Vincent Nijs Vincent

I have almost the same set-up as Gordon does. I have gotten the modem to work but haven't been able use the network card.

A question to alberto. Does SUSE 6.4 recognize your card as a CBEM or an RBEM card and would that make any difference?

My card is recognized (after playing around a bit) as a CBEM (instead of an RBEM). Could you please tell how i can be sure that not getting a connection is due to the card and not due to doing something wrong with the IP numbers etc.

regards,

Vincent

None Try setting promiscuous mode

Re: Question Same problem (Vincent Nijs)
Date: 2000, Jun 12
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Try doing:

    ifconfig eth0 promisc

and see if things start working after that.  Whether the card is
recognized as CBEM or RBEM should be irrelevant.

-- Dave

Question Xircom CEM56-100 not resuming

Date: 2000, Jun 05
From: Andrew Pickin <Andrew.Pickin@bullgod.co.uk>

I have a problem with my Xircom not resuming.
This is not a problem with my unbranded NE2000,
under RH 6.1 & 6.2.
If i restart cardmgr the card wakes-up.
I'm lost, the follow output has the xircom in
slot 1.

[root@wintermute pcmcia-cs-3.0.14]# cardctl config
Socket 0:
  Vcc = 5.0, Vpp1 = 0.0, Vpp2 = 0.0
  Interface type is memory and I/O
  IRQ 9 is exclusive, level mode, enabled
  Function 0:
    Config register base = 0x03f8
      Option = 0x61, status = 0000
    I/O window 1: 0x0320 to 0x033f, auto sized
Socket 1:
  Vcc = 5.0, Vpp1 = 0.0, Vpp2 = 0.0
  Interface type is memory and I/O
  IRQ 3 is dynamic shared, level mode, enabled
  Speaker output is enabled
  Function 0:
    Config register base = 0xff80
      Option = 0x67, status = 0x08, pin = 0000
    I/O window 1: 0x0300 to 0x030f, 16 bit
    I/O window 2: 0x02e8 to 0x02ef, 8 bit

Do I need to reset the IRQ (to 9) if so how?

THX 

Andrew Pickin

None Known bug

Re: Question Xircom CEM56-100 not resuming (Andrew Pickin)
Date: 2000, Jun 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It is a known bug in the xirc2ps_cs driver, and there is no fix;
someone needs to modify the driver to correctly reset the card when
the system is resumed.  I'm somewhat averse to messing with the driver
myself since I don't have any of these cards, and would hope that
someone would step forward to maintain the driver and fix things like
this.

-- Dave

Question Xircom CBE2-10/100BTX Support

Date: 2000, Jun 07
From: Nizar Ibrahim JoyToy

Is the Xircom CBE2-10/100BTX supported? If so, where can I find the Linux drivers for it? Thank you.

Question scheffer

Re: Question Xircom CBE2-10/100BTX Support (Nizar Ibrahim)
Date: 2000, Jun 26
From: Nicolas Scheffer scheffer

Does someone arrive to install properly this card under linux Suse 6.4 ? Does it mean that for the moment it is impossible to use a laptop with a Xircom Cardbus for ethernet, modem and isdn ?

Can someone help me how to have this card working ?

Thanks

Nicolas Scheffer

Agree Come on guy's he is not the only one looking for this driver

Re: Question Xircom CBE2-10/100BTX Support (Nizar Ibrahim)
Date: 2000, Oct 26
From: Hans van den Boomen bumke

You are not the only one looking for a driver for the Xircom CBE2-10/100.

Hopefully someone can help us !

Bumke

None Re: Agree: Come on guy's he is not the only one looking for this driver

Re: Agree Come on guy's he is not the only one looking for this driver (Hans van den Boomen)
Date: 2000, Oct 26
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> You are not the only one looking for a driver for the Xircom
> CBE2-10/100.

The driver for the CBE2-10/100 card has been included in the PCMCIA
package for almost 18 months.  It has been in Red Hat since their 6.1
release.

-- Dave

None Has anyone tested CBE2 with NEC VesaLite ?

Date: 2000, Jun 09
From: TeeJin TeeJin

I have a case of a CBE2 on an NEC Vesa Lite having suspend/ resume issue. The network is dead after resume.

However by doing a "cardctl eject" and then" cardctl resume" the network came alive again.

I am using redhat 6.2 with 2.2.14 kernel and pcmcia 3.1.8.

No problems faced with IBM thinkpads though.

I have a IBM thinkpad 600 using kernel 2.2.15 and pcmcia 3.1.15 and no problems with suspend / resume though.

Any ideas ?

Thanks TJ

None It is a known limitation of the driver

Re: None Has anyone tested CBE2 with NEC VesaLite ? (TeeJin)
Date: 2000, Jun 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The tulip_cb driver shouldn't be able to gracefully recover from a
suspend.  So I'm not sure why it is working on your Thinkpad...

-- Dave

Sad Xircom CE3-10/100 Issue...

Date: 2000, Jun 11
From: Heffer Heffer

I've been working on this for a week now and still no luck.
I'm using a Compaq LTE Elite 4/40CX Laptop (old school :) with
a Xircom CE3-10/100 Ethernet card. I've been trying everything
I can to get it working because my laptop has no cdrom, and I
can't upgrade to RedHat 6.1 from 5.0 without doing it between
the laptop and my desktop. Using a PCMCIA boot disk failed to
work, the lights on the PCMCIA to RJ45 connector were on and
flashing, but the HUB lights wern't, and no communcication
was making it to my other machines. I decided that I would
try to locate the problem by attempting to network the laptop
with 5.0 on it to my other machines. I've overcome most
obsticles involving memory problems (resulting in reboots on
card insertion), and some other issue where I got a high beep
low beep pattern on card insertion. Now it all seems ok, the
card goes in, there are 2 high tone beeps, the network.opts
file is run, and eth0 appears (when checked with ifconfig)
and it has the correct gateway, ip, and netmask all set up.
I'm not sure what broadcast is so i set it to the value my
other boxes use. Since I'm using Redhat 5.0, I don't have any
fancy tools like linuxconf to do it all for me, and hence
im not 100% (altho I am 99%), sure that I've performed all the
necessary tasks to set up a network manually. Everything seems
to be perfect. When I ping another box however, the converter
lights flash again, and theres no response on the HUB, and
it silently fails. Just like the boot disk. Any ideas? Thanks.

None Installation problems are hard; RH5.0 drivers are really old

Re: Sad Xircom CE3-10/100 Issue... (Heffer)
Date: 2000, Jun 12
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Network installs with PCMCIA devices are "tricky" and there is not
much I can do when it doesn't work.  I can't really diagnose the
problem without system log messages, and I can't easily propose a fix
since you can't modify the installation disks.

Whatever Xircom driver is included in Red Hat 5.0 is almost certainly
too old to work correctly with the CE3 card.

-- Dave

Sad Upgrade to 6.1 + Latest PCMCIA package, no fix :(

Re: None Installation problems are hard; RH5.0 drivers are really old (David Hinds)
Date: 2000, Jun 14
From: Heffer Heffer

Just upgraded (with a lot of effort) to rh 6.1, and i also
installed the latest pcmcia package but i still have the same
problem. It's all configured perfectly, and its rigged up to
a 10mbit HUB. I've read previous problems of some ppl saying
the CE3-10/100 only worked at 100 mbit's, and other ppl
saying it only worked at 10mbits. Either way, these ppl said
it was corrected by upgrading their pcmcia package, which
didnt work for me :( If you need any log files to help
diagnose the error, tell me which ones and ill post 'em.

Sad RCBEM problems... Not detecting duplexing properly

Date: 2000, Jun 12
From: Edward Spidre EdSpidre

I was curious as to wether or not some of the driver issues have been ironed out. NT had the same problem as I have now and was forcing the card to 100/FDX and not autonegotiating even though it is supposed to be 100/FDX. One of the tell tale lines when I do an ifconfig is this: TX packets:274 errors:4853 dropped:0 overruns:0 carrier:4853 There are no errors when the driver gets loaded. I am now running Mandrake 7.1 and the modem finally works. The laptop is a Dell Latitude CPx 500.

Any help is greatly appreciated

Question I have lot of problemas with an Intel Conmpatible Card (Mentor 10/100 PCMCIA Card)

Date: 2000, Jun 13
From: Cesar Gonzalez Cesar

Hi all:

I have a Mentor PCMCIA 10/100 Adapter. I paste what the disk driver said about the PCMCIA Card: " The 10/100M Fast-Ethernet PCMCIA Adapter works with the INTEL PCMCIA (PCIC) or compatible controler. " At the first time it /var/log/messages said that the card were not suported, and i added an entry on /etc/pcmcia/config with my card manid and especify bind "xirc2cs_ps" but the xirc2_ps_cs.o module doesnt want to install itself. /var/log/messages said that:

Jun 13 17:00:02 Bolo cardmgr[1418]: Initializing socket 1
Jun 13 17:00:02 Bolo Kernel: cs: memory probe 0xa0000000-0xa0fffffff: clean
Jun 13 17:00:02 Bolo cardmgr[1418]: socket 1: PCMCIA FAST-Ethernet ,
Jun 13 17:00:02 Bolo cardmgr[1418]: executing: `modprobe xirc2ps_cs`
Jun 13 17:00:02 Bolo kernel: cs: xirc2ps_cs: xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh)
Jun 13 17:00:02 Bolo kernel: cs: xirc2ps_cs: Unknown Card Manufactured ID: 0xffff
Jun 13 17:00:02 Bolo cardmgr[1418]: get dev info on socket 1 failed: No such device

Can anybody help me to install properly this f***** card? I think there must be a way to tell the module to not check manid of the card, but i dont know how. Thanks in advance.

Regards.

Bolo.

None This is not a Xircom card

Re: Question I have lot of problemas with an Intel Conmpatible Card (Mentor 10/100 PCMCIA Card) (Cesar Gonzalez)
Date: 2000, Jun 13
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You might be more likely to be successful with the pcnet_cs or
smc91c92_cs driver.

The comment about a "Intel compatible controller" is describing the
PCMCIA bridge chip in your laptop, not the hardware in the card.

-- Dave

Question 56k Modem Almost Working

Date: 2000, Jun 14
From: Dannie Stanley danimal

I have a Xircom Ethernet 10/100 + Modem 56 and a Dell Inspiron 7500 running RH6.2

I have the Ethernet portion working fine however when I try to configure the modem it connects but the quickly disconnects with the following in /var/log/messages

Jun 14 12:47:24 spinweb12 pppd[2488]: pppd 2.3.11 started by root, uid 0
Jun 14 12:47:24 spinweb12 ifup-ppp: pppd started for ppp1 on /dev/modem at 57600
Jun 14 12:47:37 spinweb12 pppd[2488]: Connect script failed
Jun 14 12:47:38 spinweb12 pppd[2488]: Exit.

Please Help! DS

-- Dannie M Stanley SpinWeb Net Designs, Inc.

More Additional Information

Re: Question 56k Modem Almost Working (Dannie Stanley)
Date: 2000, Jun 14
From: Dannie Stanley danimal

The chat handshake seems to be working fine.  I turned on
debug mode for pppd and found that the script terminated in
the same place everytime here are the last two lines before
hangup:

rcvd [IPCP ConfReq id=0x4 <compress VJ 0f 00> <addr 207.205.227.119>]
sent [IPCP ConfAck id=0x4 <compress VJ 0f 00> <addr 207.205.227.119>]

I am not an expert on pppd but it looks like the server asks
to assign me an IP and then when I reply it says I don't
understand and pukes on me...


Thanks for any help!
DS




---begin full log output---
Using interface ppp0
Connect: ppp0 <--> /dev/ttyS1
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xea080495> <pcomp> <accomp>]
rcvd [LCP ConfNak id=0x1 <asyncmap 0xffffffff>]
sent [LCP ConfReq id=0x2 <magic 0xea080495> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x2 <magic 0xea080495> <pcomp> <accomp>]
rcvd [LCP ConfReq id=0x2 <mru 1514> <asyncmap 0xffffffff> <magic 0xcb4d18b8> <pcomp> <accomp> < 11 04 05 ea> < 13 03 00>]
sent [LCP ConfRej id=0x2 < 11 04 05 ea> < 13 03 00>]
rcvd [LCP ConfReq id=0x3 <mru 1514> <asyncmap 0xffffffff> <magic 0xcb4d18b8> <pcomp> <accomp>]
sent [LCP ConfAck id=0x3 <mru 1514> <asyncmap 0xffffffff> <magic 0xcb4d18b8> <pcomp> <accomp>]
sent [IPCP ConfReq id=0x1 <addr 192.168.0.12> <compress VJ 0f 01> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
rcvd [IPCP ConfReq id=0x4 <compress VJ 0f 00> <addr 207.205.227.119>]
sent [IPCP ConfAck id=0x4 <compress VJ 0f 00> <addr 207.205.227.119>]
Hangup (SIGHUP)
Modem hangup
Connection terminated.

None I think this is a PPP issue

Re: More Additional Information (Dannie Stanley)
Date: 2000, Jun 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I think that if you've gotten this far, the PCMCIA drivers are
probably operating correctly.  You could confirm by seeing if you can
establish regular terminal sessions with something like minicom or
seyon.  I'm not an expert on debugging pppd connection issues.  There
might be some hints in the PPP-HOWTO.

-- Dave

Question Init Strings for Xircom RealPort GSM

Date: 2000, Jun 15
From: Fabien fabien

I have a problem with calling when I am using a gsm connection kit. The xircom card works very well, and I can use ethernet, modem, isdn without problems. The gsm is a nokia 6150 When I try to call my provider, using just "atd telephoneumber", I receive a "NO CARRIAGE". I can see on the GSM "calling number" and after an error.

I've tried to use init strings from windows driver : in windows : ============================

06-15-2000 15:43:11.54 - Modem of Xircom CreditCard Ethernet 100 + Modem 56 closed.

06-15-2000 15:43:42.78 - Modem of Xircom CreditCard Ethernet 100 + Modem 56 in use.

06-15-2000 15:43:42.78 - Modem type: Modem of Xircom CreditCard Ethernet 100 + Modem 56

06-15-2000 15:43:42.78 - Modem inf path: MDMCEM56.INF

06-15-2000 15:43:42.78 - Modem inf section: Modem1

06-15-2000 15:43:43.02 - 115200,N,8,1

06-15-2000 15:43:43.06 - 115200,N,8,1

06-15-2000 15:43:43.07 - Initializing modem.

06-15-2000 15:43:43.07 - Send: AT<cr>

06-15-2000 15:43:43.08 - Recv: AT<cr>

06-15-2000 15:43:43.08 - Recv: <cr><lf>OK<cr><lf>

06-15-2000 15:43:43.08 - Interpreted response: Ok

06-15-2000 15:43:43.08 - Send: AT &F E0 &C1 &D2 V1 S0=0 S95=45 W2<cr>

06-15-2000 15:43:43.11 - Recv: AT &F E0 &C1 &D2 V1 S0=0 S95=45 W2<cr>

06-15-2000 15:43:43.11 - Recv: <cr><lf>OK<cr><lf>

06-15-2000 15:43:43.11 - Interpreted response: Ok

06-15-2000 15:43:43.11 - Send: ATS7=60S30=0M1S7=90 S10=100 S40=2 \N4<cr>

06-15-2000 15:43:43.11 - Recv: <cr><lf>OK<cr><lf>

06-15-2000 15:43:43.11 - Interpreted response: Ok

06-15-2000 15:43:43.11 - Send: AT%C3&K3B0N1X4<cr>

06-15-2000 15:43:43.13 - Recv: <cr><lf>OK<cr><lf>

06-15-2000 15:43:43.13 - Interpreted response: Ok

06-15-2000 15:43:43.13 - Dialing.

06-15-2000 15:43:43.13 - Send: ATDT;<cr>

06-15-2000 15:43:43.13 - Recv: <cr><lf>OK<cr><lf>

06-15-2000 15:43:43.13 - Interpreted response: Ok

06-15-2000 15:43:43.13 - Dialing.

06-15-2000 15:43:43.13 - Send: ATDT##########<cr>

06-15-2000 15:44:07.75 - Recv: <cr><lf>CARRIER 9600<cr><lf>

06-15-2000 15:44:07.75 - Interpreted response: Informative

06-15-2000 15:44:07.75 - Recv: <cr><lf>PROTOCOL: RLP<cr><lf>

06-15-2000 15:44:07.75 - Interpreted response: Informative

06-15-2000 15:44:07.75 - Recv: <cr><lf>COMPRESSION: NONE<cr><lf>

06-15-2000 15:44:07.75 - Interpreted response: Informative

06-15-2000 15:44:07.76 - Recv: <cr><lf>CONNECT 9600<cr><lf>

06-15-2000 15:44:07.76 - Interpreted response: Connect

06-15-2000 15:44:07.76 - Connection established at 9600bps.

06-15-2000 15:44:07.76 - Error-control on.

06-15-2000 15:44:07.76 - Data compression off or unknown.

06-15-2000 15:44:07.80 - 115200,N,8,1

06-15-2000 15:53:47.92 - Hanging up the modem.

06-15-2000 15:53:47.92 - Hardware hangup by lowering DTR.

06-15-2000 15:53:47.92 - Recv: <cr><lf>NO CARRIER<cr><lf>

06-15-2000 15:53:47.92 - Interpreted response: No Carrier

06-15-2000 15:53:47.92 - Send: ATH E1<cr>

06-15-2000 15:53:47.94 - Recv: <cr><lf>OK<cr><lf>

06-15-2000 15:53:47.94 - Interpreted response: Ok

06-15-2000 15:53:47.98 - Session Statistics:

06-15-2000 15:53:47.98 - Reads : 509579 bytes

06-15-2000 15:53:47.98 - Writes: 22298 bytes

06-15-2000 15:53:47.98 - Modem of Xircom CreditCard Ethernet 100 + Modem 56 closed.

===================== So in linux, I use :

ABORT BUSY

ABORT "NO CARRIER"

ABORT VOICE

ABORT "NO DIALTONE"

ABORT "NO ANSWER"

"" ATZ

OK

AT&FE0&C1&D2V1S0=0S95=45W2

OK

ATS7=60S30=0M1S7=90S10=100S40=2

OK

AT%C3&K3B0N1X4

OK

ATDT;

OK

ATDTmy_number

CONNECT \d\c

But I have the same "NO CARRIER"

Any solution ?

Thanks in advance...

--------------- Fabien SALVI

Ok success with RealPort2 R2E

Date: 2000, Jun 17
From: Mattias Amnefelt mattiasa

I have gotten the Xircom RealPort2 R2E 10/100BASE-T card to work with pcmcia-cs-3.1.8 on a IBM Thinkpad 570E running redhat 6.2 by adding the following line to the configfile:

	card "Xircom RealPort2 Ethernet 10/100 Adapter"
	  manfid 0x0105, 0x010a
	  bind "xirc2ps_cs"

cardmgr generates the following logentry for the card:

	Jun 17 18:53:26 lapetus cardmgr[449]:   product info: 		"Xircom", "RealPort2 Ethernet 10/100 Adapter", 			"R2E-100BTX", "1.00"
	Jun 17 18:53:26 lapetus cardmgr[449]:   manfid: 		0x0105, 0x010a  function: 6 (network)

Question Promisc mode in redhat/mandrake network script?

Date: 2000, Jun 20
From: kato

Is there any way to add the "promisc" option the the standard redhat/mandrake network init.d script so my Xircom get's an address via dhcpcd automagically? I have the infamous RBEM56G-100TX carbus xircom card

 I seem to have to let the dhcpcd process fail on system start-up, then use the method that Stewart mentions below to initiate the network script again, open up another terminal and initiate a /sbin/ifconfig eth0 promisc so
 the Xircom grabs the address properly from the server. 

 Is there an easier way? 

 Thanks, 

 sji 

Note Toshiba IPC5008A does not work(Including patch)

Date: 2000, Jun 22
From: Junichiro Kita kitaj

I have Toshiba IPC5008A 10/100 Ethernet PC Card.

I found that my PC card is supported by xirc2ps_cs.o in 
pcmcia-cs-3.1.12 and pcmcia-cs-3.1.16 while reading
UPPORTED.CARDS. But it does not work.

The reason is followed.
1. manfid of Toshiba IPC5008A is 0x0098.
2. In xirc2ps_cs.c, there is no routine for this manfid.

I made a patch for xirc2ps_cs.c.
It seems to work.


^--------------------------------------------------------
--- xirc2ps_cs.c-orig	Thu Feb 17 23:18:31 2000
+++ xirc2ps_cs.c	Tue Jun 20 02:56:06 2000
@@ -131,6 +131,9 @@
 #ifndef MANFID_INTEL
   #define MANFID_INTEL		   0x0089
 #endif
+#ifndef MANFID_TOSHIBA
+  #define MANFID_TOSHIBA	   0x0098
+#endif
 
 #include <pcmcia/ds.h>
 
@@ -983,6 +986,10 @@
       case MANFID_INTEL:
 	local->manf_str = "Intel";
 	DEBUG(0, "found Intel card\n");
+	break;
+      case MANFID_TOSHIBA:
+	local->manf_str = "Toshiba";
+	DEBUG(0, "found Toshiba card\n");
 	break;
       default:
 	printk(KNOT_XIRC "Unknown Card Manufacturer ID: 0x%04x\n",

$----------------------------------------------------------

None Thanks for the patch

Re: Note Toshiba IPC5008A does not work(Including patch) (Junichiro Kita)
Date: 2000, Jun 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'll fold this into 3.1.17.

-- Dave

Note I have another request.

Re: None Thanks for the patch (David Hinds)
Date: 2000, Jun 23
From: Junichiro Kita kitaj

Please add the following entry to /etc/pcmcia/config.
This if for TOSHIBA CD-ROM Drive PA2673UJ and it's PC Card I/F.

^--------------------------------------
card "Toshiba CD-ROM Drive"
  version "LOOKMEET", "CBIDE2      "
  bind "ide_cs"
$--------------------------------------

Sad Xircom RBEM56G 100 doesn't work in Linux Mandrake

Date: 2000, Jun 22
From: Aishvarya Kr. Sharma aishvar

hi!

care to help a newbie. I have a Dell Latitude with xircom card, and after downloading the latest pcmcia path (3.1.15) linux can atleast detect the card ( 2 reassuring beeps ). BUt it can not detect the ethernet card . tried ifconfig eth0 promisc & other stuff

please help me

thanx

with regards

aish

Feedback Re: Xircom RBEM56G 100 doesn't work in Linux Mandrake

Re: Sad Xircom RBEM56G 100 doesn't work in Linux Mandrake (Aishvarya Kr. Sharma)
Date: 2000, Jun 23
From: kato

As root, when you type ifconfig, what is the output?

I have a Dell Inspiron 7500 and the way I get it to work is the following:

1) On bootup, card doesn't/isn't able to get an IP address from my main Linux box, so I let it error out.

2) At the logon screen I logon

3) I su to root and restart the network init.d script by typing :

/etc/rc.d/init.d/network restart

4) While that is working I hit ctl+alt+F2 to get to another tty/terminal window and logon as root. I then type

ifconfig eth0 promisc

Then I exit out of that terminal

5) When I alt+ctrl+F1 back to the first terminal window, I see the dhcpcd command complete. But at this time the card is still in promisc mode so I just use the up arrow key to re-enter the same command in as above:

/etc/rc.d/init.d/network restart

Type "exit" to get back to your normal user status.

The network restarts, the card re-inits and is no longer in promiscuous mode. Everthings works fine. You can double check the card by typing in:

/sbin/ifconfig

I know this sounds like alot, but I can perform the steps in under 10 seconds. Not a big deal and at least the card works without alot of acrobatics.

There probably is an easier way to do this via the standard Mandrake network scripts via modification but I haven't had the time to figure it out yet.

I just got the card RBEM56G-100TX this week and it works like a charm. Hope this helps....

sji

Ok RBEM100G + 56K working now

Re: Sad Xircom RBEM56G 100 doesn't work in Linux Mandrake (Aishvarya Kr. Sharma)
Date: 2000, Jun 29
From: Aishvarya Kr. Sharma aishvar

hi!

I got the card working all fine on Dell Latitude. I downloaded the PCMCIA package after which it atleast started recognising the card.

Even after this I had lot of troubles 'coz the eth0 always used to give a failed message but pcmcia used to work fine ( I know, 'coz the 2 beeps on inserting the card means that all's well). at bootup.

then I noticed something. Aftr booting up & login as root, if I started network (/etc/rc.d/init.d/network )start it worked.

I saw that during boot up the network was executed first then pcmcia was executed.

this is absurd, 'coz the network requires pcmcia to be runnig to be able to access the card.

I changed the sequence (by swapping the numbers, I had S10network@ and S45pcmcia, and I made them S44pcmcia & S45network). These links are there in the /etc/rc.d/rc.d directory.

it worked like a charm. So all of u ppl, who have similar prob, try this one out. no need to do anything after this.

All the best.

Aishvarya

None This is an issue with the Red Hat PCMCIA scripts, not init order

Re: Ok RBEM100G + 56K working now (Aishvarya Kr. Sharma)
Date: 2000, Jul 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You do not need to reorder the init scripts.  Think about what happens
if the card is not even present at boot time: the boot-time order
should not matter.

Your specific issue is covered in the PCMCIA-HOWTO section that
describes the Red Hat distribution.

-- Dave

Question Xircom Realport REM56G-10 on debian potato on a Dell Inspiron

Date: 2000, Jun 22
From: Claudio HaMMeR h4mm3r

hi, i must admit that i've 0 experience with pcmcia, i just want to know how to install a pcmcia card with multifunction like mine. give me an url to a doc, explain, give experiences, everyhing is accepted... is it possible to use both the functions (eth+modem) at the same time???

tnx

Claudio

None Check out my exp.

Re: Question Xircom Realport REM56G-10 on debian potato on a Dell Inspiron (Claudio HaMMeR)
Date: 2000, Jun 30
From: Aishvarya Kr. Sharma aishvar

hi!

check out my prev. message. download the pcmcia package from the net. it's documented in quite some messages above.

all the best

aish

Question Force full duplex on xirc2ps ?

Date: 2000, Jun 23
From: Stefan Hoffmeister shoffmeister

I cannot find any documentation on how to force the Xircom CEM33 (xirc2ps) into full duplex mode.

Apparently I must have full duplex enabled in order to get through my 10/100 hub - at least that's my experience with that card being driven by Xircom's own drivers under Win95 and NT4.

TIA, Stefan

Question Status on the development of the driver for the RBE 10/100 BTX

Date: 2000, Jun 27
From: Paulo E. Abreu peabreu

Hello there
I just wanted to know if a driver is being developed
for the Xircom Cardbus 10/100 RBE. Using the latest drivers
I cant get it to work in a 10 Half duplex hub, but at home
using a crosslink cable and using a Lite-On LC82c168 PNIC 
(which also uses the tulip driver) I can only get something
like 160Kbs... My computer also freezes under heavy traffic.
I know that xircom provided specs for this card, so its just
 a matter of time ? I bought the xircom card because I was 
told it was supported. Oh well, life goes on ....
Paulo E. Abreu

Note Untitled

Re: Question Status on the development of the driver for the RBE 10/100 BTX (Paulo E. Abreu)
Date: 2000, Jun 27
From: Paulo E. Abreu peabreu

I meant that in a 10Mb half duplex hub it works...

Question Intermediate stalls with serial port at higher load (Xircom CEM56)

Date: 2000, Jun 27
From: Andreas Stuebinger andreas.stuebinger

I'm using linux-2.2.16 together with pcmcia-cs-3.1.16 on
a Scenic Mobile 710. The ethernet part is working well,
the serial part is well if working on small data transfers
or working interactivly.

But on trying to download some larger files (i.e. larger
than about 30kB) the connection seems to be interupted.
The connection stops, starts again, receives some data,
stops again, .... The overall transfer rate drops down
to about 1.5kB/s. 

There are no changes to serial.opts, in /var/log/messages
appear the following messages:


kernel: Linux PCMCIA Card Services 3.1.16
kernel:   kernel build: 2.2.16 #10 Fri Jun 23 14:46:24 CEST 2000
kernel:   options:  [pci] [cardbus] [apm]
kernel: PCI routing table version 1.0 at 0xf5ec0
kernel: Intel PCIC probe:
kernel:   Cirrus PD6832 rev c1 PCI-to-CardBus at slot 00:14, mem 0x68000000
kernel:     host opts [0]: [ring] [0/7/4] [3/17/4] [no pci irq] [lat 64/176] [bus 32/34]
kernel:     host opts [1]: [ring] [0/7/4] [3/17/4] [no pci irq] [lat 64/176] [bus 35/37]
kernel:     ISA irqs (scanned) = 3,4,7,11 polling interval = 1000 ms
cardmgr[717]: starting, version is 3.1.16
cardmgr[717]: watching 2 sockets
kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
kernel: cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x807
kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x300-0x307 0x370-0x37f 0x398-0x39f 0x4d0-0x4d7
cardmgr[717]: initializing socket 1
kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
cardmgr[717]: socket 1: Xircom CEM56 Ethernet/Modem
cardmgr[717]: executing: 'modprobe xirc2ps_cs'
kernel: xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh)
cardmgr[717]: executing: 'modprobe serial_cs'
kernel: eth0: MII link partner: 0021
kernel: eth0: MII selected
kernel: eth0: media 10BaseT, silicon revision 5
kernel: eth0: Xircom: port 0x320, irq 11, hwaddr 00:10:A4:D0:C5:B0
kernel: tty03 at 0x02e8 (irq = 11) is a 16550A
cardmgr[717]: executing: './network start eth0'
kernel: eth0: MII link partner: 0021
kernel: eth0: MII selected
kernel: eth0: media 10BaseT, silicon revision 5
cardmgr[717]: executing: './serial start ttyS3'


Thanks a lot for any help

News Xircom CardBus CBEM56G 10/100 is working now...!!!!!!!

Date: 2000, Jun 28
From: Nicolas Scheffer scheffer

Hi All,

I just upgrade my laptop with latest update from Suse, i use Suse Linux 6.4 and upgrade the following : - kernel 2.2.16 for laptop - pcmcia 3.1.16-1

Make some test and now everything is working : - modem is working - ethernet card is working with or without dhcp, 10 and 100 and also half and full duplex

I am very happy, thanks to Suse team for this upgrade because before my cardbus didn't work and now yes....

Nicolas Scheffer

Question Even after Suspend/Resume?

Re: News Xircom CardBus CBEM56G 10/100 is working now...!!!!!!! (Nicolas Scheffer)
Date: 2000, Jul 10
From: Andrew Pickin <Andrew.Pickin@bullgod.co.uk>

I'm having problems with my CEM56 & REM56.

Both of these cards work 10 & 100.
But after closing the lid and then resuming, the cards fail to auto-negociate.
I have to eject and re-insert the card in order to re-establish connection.

I believe that this is a problem with the memory area known as MII.
Unfortunately the spec which Xircom have made public mentions this area only in passing.

Have mailed Xircom twice now requesting information about how this area is initialised but have received no response.

Has anyone managed to get either of these cards to re-negociate 100 BaseT after a resumne event?
Or does anyone have info on how MII in initialise or how to get this info out of Xircom?

AMP

None RE-100 not init on startup

Date: 2000, Jul 04
From: David Hammerton crazney

I have a RE-100 10/100 realport card which was not working under linux until I got the latest PCMCIA package. Now, whenever i boot the init of eth0 fails. To get the card to work I have to eject the card, put it back in and run "/etc/pcmcia/network.O start eth0". I havent tried the card at 100mb, but I dont really care about speed YET, I just want it to work...

any help apprieciated.

Thanks heaps

regards

David

Idea Probably your init scripts

Re: None RE-100 not init on startup (David Hammerton)
Date: 2000, Jul 05
From: Edward Spidre EdSpidre

All that's wrong seems to be the order your init scripts are starting up. For me in Mandrake, when /etc/rc.d/init.d/network runs, if eth0 doesn't come up immediately it sleeps for a 10 seconds perhaps, by that time pcmcia starts up and all is good.

What distribution are you using?

- Ed

None Re: Idea: Probably your init scripts

Re: Idea Probably your init scripts (Edward Spidre)
Date: 2000, Jul 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

No, that's not what's wrong, and you should not need to reorder the
init scripts.  The network init issue is mentioned in the PCMCIA-HOWTO
in the section about Red Hat.

-- Dave

None It's mentioned in the HOWTO

Re: None RE-100 not init on startup (David Hammerton)
Date: 2000, Jul 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Move /etc/pcmcia/network.O to /etc/pcmcia/network, and read the
PCMCIA-HOWTO notes about Red Hat.

-- Dave

Sad RBE-100 freezes system on startup and insertion

Date: 2000, Jul 07
From: Julian Smith julian

hi there. I am running Red Hat 6.2 on an IBM Thinkpad 600e. If my RBE-100 is inserted when I boot up the system freezes around the sendmail startup point. If I boot up without the card, it all starts fine, however if I insert the card at any time after that,I hear 1 beep and the system freezes.

Here's an excerpt of the log.

"Jul 6 17:17:29 localhost keytable: Loading system font:

Jul  6 17:17:29 localhost rc: Starting keytable succeeded
Jul  6 17:17:30 localhost sendmail: sendmail startup succeeded
Jul  6 17:17:31 localhost gpm: gpm startup succeeded
Jul  6 17:17:33 localhost httpd: httpd startup succeeded
Jul  6 17:17:35 localhost xfs: xfs startup succeeded
Jul  6 17:17:36 localhost linuxconf: Linuxconf final setup
Jul  6 17:17:37 localhost rc: Starting linuxconf succeeded
Jul  6 17:19:46 localhost ifup: Delaying eth1 initialization.
Jul  6 17:19:46 localhost network: Bringing up device eth1 failed
Jul  6 17:19:47 localhost ypbind: ypbind startup failed
Jul  6 17:25:03 localhost rc: Stopping keytable succeeded
Jul  6 17:25:04 localhost xfs: xfs shutdown succeeded
Jul  6 17:25:04 localhost gpm: gpm shutdown succeeded
Jul  6 17:25:09 localhost httpd: httpd shutdown succeeded
Jul  6 17:25:09 localhost sendmail: sendmail shutdown succeeded
Jul  6 17:25:10 localhost inet: inetd shutdown succeeded
Jul  6 17:25:10 localhost atd: atd shutdown succeeded
Jul  6 17:25:10 localhost crond: crond shutdown succeeded
Jul  6 17:25:10 localhost lpd: lpd shutdown succeeded"

I have tried with Tulip and cs 89. I'm sure I must be missing something basic.

Hope you can help me..

None I'd first try a PCMCIA driver upgrade

Re: Sad RBE-100 freezes system on startup and insertion (Julian Smith)
Date: 2000, Jul 07
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The drivers in RH6.2 are version 3.1.8; the latest are 3.1.17.

-- Dave

Note Tried that...no good...

Re: None I'd first try a PCMCIA driver upgrade (David Hinds)
Date: 2000, Jul 09
From: Julian Smith julian

Could I be using the wrong driver?. Or wrong start up options?. This thing is freezing completely...

None You can try a suggestion from the HOWTO

Re: Note Tried that...no good... (Julian Smith)
Date: 2000, Jul 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The PCMCIA-HOWTO does say:

o On IBM ThinkPad 600 and 770 models with internal modems, exclude port
  0x2f8-0x2ff.

which is certainly worth a try.

-- Dave

Ok David defeats Goliath

Re: None You can try a suggestion from the HOWTO (David Hinds)
Date: 2000, Jul 12
From: Julian Smith julian

David,

You do know you are a legend. Don't you? I re-installed latest drivers and addressed exclusion on memory and bingo. 2 beeps. The card is happy and so am I.

Many many thanks. Julian

Sad Problem installing a Xircom CBE2-100 on an IBM Thinkpad 1400 i-sries

Date: 2000, Jul 08
From: Khalid HASSANI khalid1

Hi everybody !

I am trying to install a Xircom CBE2-100BTX, on my Laptop (a Thinkpad IBM 1400, with Redhat 6.0) my card seems to be recognised, here is the log from /var/log/messages :

(sorry for the formating of the log messages !)

Jul 16:03:18 localhost kernel: tulip_attach(bus 32, function 0)

Jul  8 16:03:18 localhost kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Jul  8 16:03:18 localhost kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0xa00, 00:10:A4:BC:D7:64, IRQ 3.
Jul  8 16:03:18 localhost kernel: eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1.
Jul  8 16:03:18 localhost kernel: XIRCOM init

But when I try to connect to my ISP with DSL, with a script called start-pppoe (which issue among other things an ifconfig eth0 0.0.0.0 up -broadcast -arp) I get the following messages in /var/log/messges :

Jul  8 16:19:02 localhost kernel: PPP: version 2.3.7 (demand dialling)
Jul  8 16:19:02 localhost kernel: PPP line discipline registered.
Jul  8 16:19:02 localhost kernel: registered device ppp0
Jul  8 16:19:02 localhost pppd[674]: pppd 2.3.10 started by root, uid 0
Jul  8 16:19:02 localhost pppd[674]: Using interface ppp0
Jul  8 16:19:02 localhost pppd[674]: Connect: ppp0 <--> /dev/pts/2
Jul  8 16:19:02 localhost pppoed[675]: pppoed 1.300.000 started
Jul  8 16:19:02 localhost pppoed[677]: Related PIDs: 674 675 677
Jul  8 16:19:02 localhost pppoed[675]: Sending PADI.
Jul  8 16:19:03 localhost pppoed[675]: No PADO responses received.
Jul  8 16:19:03 localhost pppoed[675]: Re-sending PADI.
Jul  8 16:19:05 localhost pppoed[675]: No PADO responses received.
Jul  8 16:19:05 localhost pppoed[675]: Re-sending PADI.
Jul  8 16:19:09 localhost pppoed[675]: No PADO responses received.
Jul  8 16:19:09 localhost pppoed[675]: Re-sending PADI.
Jul  8 16:19:11 localhost kernel: eth0: Transmit timed out, status 68678107, CSR12 000000c2, resetting...
Jul  8 16:19:16 localhost kernel: eth0: Transmit timed out, status 68678107, CSR12 000000c2, resetting...
Jul  8 16:19:17 localhost pppoed[675]: No PADO responses received.
Jul  8 16:19:17 localhost pppoed[675]: Could not connect to requested network resource.
Jul  8 16:19:17 localhost pppoed[675]: Exit.
Jul  8 16:19:17 localhost pppd[674]: Hangup (SIGHUP)
Jul  8 16:19:17 localhost pppd[674]: Modem hangup
Jul  8 16:19:17 localhost pppd[674]: Connection terminated.
Jul  8 16:19:17 localhost pppd[674]: Exit.

Can someone please help !?

I understand, that according to "Linux PCMCIA Supported Device List" of 2000/06/23, the XIRCOM CBE2-100BTX is still experimental ! but maybe someone has already solved this problem.

Thanks for reading

Khalid HASSANI

None Can you try using the card some other way?

Re: Sad Problem installing a Xircom CBE2-100 on an IBM Thinkpad 1400 i-sries (Khalid HASSANI)
Date: 2000, Jul 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I think pppoe is a difficult thing to use for diagnosis if you don't
yet know if the card is operating properly.  I would try simpler
things like using the modem as a regular modem, and using the ethernet
on a regular ethernet.

-- Dave

Question IBM T20 & Xircom RBE-100

Date: 2000, Jul 09
From: Brian Pavane bpavane

I've recently received an IBM T20 laptop, and a Xircom RBE-100 CardBus Ethernet adapter. Now it's time to get this card working under Linux (Slakware 7.1.0 / Kernel 2.2.16).

Is there a FAQ or document floating around about how to make this cardbus device to work, or am I better off waiting for a driver to come out of beta or get a 3com card?

None There is not much specific information

Re: Question IBM T20 & Xircom RBE-100 (Brian Pavane)
Date: 2000, Jul 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

There is no specific reference about this particular card.  You should
follow the guidelines in the PCMCIA-HOWTO and see if it works.  And
there is a specific note about the card in the BUGS file.

I have no idea when/if the problems with these cards will get fixed.

-- Dave

Sad CBEM 10/100 recognized only if SCSI is inserted before

Date: 2000, Jul 10
From: Christoph Blaue cb

My System is
 - Dell Inspiron 3700
 - SuSE 6.4 
 - PCMCIA 3.1.11 (I don't really want to upgrade, because I had problems with
   the token ring and newer versions)
 - Xircom CBEM56G-100 (Combined Cardbus for Ethernet/Modem)


After inserting the Card I get one high and one low beep. It says 'unsupported
card'.

Ejecting and reinserting does not help.

Here comes the weird thing:
If I insert a SCSI-Card first (Adaptec 1460B) and the Xircom later the card
is recognised.

swapping slots does not change the behaviour

What can I do do get the card working without the pretty expensive SCSI-helper?


system Log after restarting PCMCIA:
Jul 10 13:48:33 lapcb kernel: Linux PCMCIA Card Services 3.1.11
Jul 10 13:48:33 lapcb kernel:   kernel build: 2.2.14 #1 Mon Mar 13 10:51:48 GMT 
2000
Jul 10 13:48:33 lapcb kernel:   options:  [pci] [cardbus]
Jul 10 13:48:33 lapcb kernel: PCI routing table version 1.0 at 0xfbd70
Jul 10 13:48:33 lapcb kernel: Intel PCIC probe: 
Jul 10 13:48:33 lapcb kernel:   TI 1225 PCI-to-CardBus at slot 00:03, mem 0x6800
0000
Jul 10 13:48:33 lapcb kernel:     host opts [0]: [ring] [serial pci & irq] [pci 
irq 11] [lat 32/176] [bus 32/34]
Jul 10 13:48:33 lapcb kernel:     host opts [1]: [ring] [serial pci & irq] [pci 
irq 11] [lat 32/176] [bus 35/37]
Jul 10 13:48:33 lapcb kernel:     ISA irqs (scanned) = 3,4,7,9,10 PCI status cha
nges
Jul 10 13:48:33 lapcb cardmgr[845]: starting, version is 3.1.11
Jul 10 13:48:33 lapcb cardmgr[845]: watching 2 sockets
Jul 10 13:48:33 lapcb kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0
xcff
Jul 10 13:48:33 lapcb kernel: cs: IO port probe 0x0800-0x08ff: excluding 0x800-0
x84f
Jul 10 13:48:33 lapcb kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x280-0
x287 0x378-0x37f 0x4d0-0x4d7
Jul 10 13:48:33 lapcb kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Jul 10 13:48:34 lapcb kernel: cs: cb_alloc(bus 32): vendor 0x115d, device 0x0003
Jul 10 13:48:34 lapcb cardmgr[845]: initializing socket 0
Jul 10 13:48:34 lapcb kernel: ROM image dump:
Jul 10 13:48:34 lapcb kernel:   image 0: 0x000000-0x00ffff, signature PCIR
Jul 10 13:48:34 lapcb cardmgr[845]: unsupported card in socket 0
Jul 10 13:48:34 lapcb cardmgr[845]:   no product info available

None Memory probe issue

Re: Sad CBEM 10/100 recognized only if SCSI is inserted before (Christoph Blaue)
Date: 2000, Jul 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Insert the SCSI card.  Check your system log for "memory probe"
messages.  Edit /etc/pcmcia/config.opts and exclude any memory range
that the probe says it is excluding.  Then reboot and the other card
should work when inserted first.

-- Dave

None Re: Memory probe issue

Re: None Memory probe issue (David Hinds)
Date: 2000, Jul 11
From: Christoph Blaue cb

I tried this, but it does not work, I only found, that I get a warning in my
syslog 'no high memory space available!', when inserting the SCSI card. I have
excluded things to get the token ring adapter working.

here is a complete syslog from the start of my pcmcia services

----------------------------------------
1. start of pcmcia

Jul 11 10:04:51 lapcb kernel: Linux PCMCIA Card Services 3.1.11
Jul 11 10:04:51 lapcb kernel:   kernel build: 2.2.14 #1 Mon Mar 13 10:51:48 GMT 2000
Jul 11 10:04:51 lapcb kernel:   options:  [pci] [cardbus]
Jul 11 10:04:51 lapcb kernel: PCI routing table version 1.0 at 0xfbd70
Jul 11 10:04:51 lapcb kernel: Intel PCIC probe: 
Jul 11 10:04:51 lapcb kernel:   TI 1225 PCI-to-CardBus at slot 00:03, mem 0x68000000
Jul 11 10:04:51 lapcb kernel:     host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 32/176] [bus 32/34]
Jul 11 10:04:51 lapcb kernel:     host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat 32/176] [bus 35/37]
Jul 11 10:04:51 lapcb kernel:     ISA irqs (scanned) = 3,4,7,9,10 PCI status changes
Jul 11 10:04:51 lapcb cardmgr[718]: starting, version is 3.1.11
Jul 11 10:04:51 lapcb cardmgr[718]: watching 2 sockets
Jul 11 10:04:51 lapcb kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
Jul 11 10:04:51 lapcb kernel: cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x84f
Jul 11 10:04:51 lapcb kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x378-0x37f 0x4d0-0x4d7
Jul 11 10:04:51 lapcb kernel: cs: IO port probe 0x0a00-0x0aff: clean.

----------------------------------------
2. inserting Xircom as first card

Jul 11 10:05:47 lapcb kernel: cs: cb_alloc(bus 32): vendor 0x115d, device 0x0003
Jul 11 10:05:47 lapcb cardmgr[718]: initializing socket 0
Jul 11 10:05:47 lapcb kernel: ROM image dump:
Jul 11 10:05:47 lapcb kernel:   image 0: 0x000000-0x00ffff, signature PCIR
Jul 11 10:05:47 lapcb cardmgr[718]: unsupported card in socket 0
Jul 11 10:05:47 lapcb cardmgr[718]:   no product info available

----------------------------------------
3. ejecting Xircom

Jul 11 10:06:47 lapcb kernel: cs: cb_free(bus 32)

----------------------------------------
4. inserting SCSI, there is no device attached, thus the messages

Jul 11 10:07:23 lapcb cardmgr[718]: initializing socket 1
Jul 11 10:07:23 lapcb cardmgr[718]: socket 1: Adaptec APA-1460 SlimSCSI
Jul 11 10:07:23 lapcb kernel: cs: warning: no high memory space available!
Jul 11 10:07:23 lapcb kernel: cs: memory probe 0x0d0000-0x0dffff: clean.
Jul 11 10:07:23 lapcb cardmgr[718]: executing: 'insmod /lib/modules/2.2.14/pcmcia/aha152x_cs.o'
Jul 11 10:07:24 lapcb kernel: aha152x: processing commandline: ok
Jul 11 10:07:24 lapcb kernel: aha152x: BIOS test: passed, detected 1 controller(s)
Jul 11 10:07:24 lapcb kernel: aha152x0: vital data: PORTBASE=0x140, IRQ=3, SCSI ID=7, reconnect=enabled, parity=enabled, synchronous=disabled, delay=100, extended translation=disabled
Jul 11 10:07:24 lapcb kernel: aha152x: trying software interrupt, ok.
Jul 11 10:07:24 lapcb kernel: scsi0 : Adaptec 152x SCSI driver; $Revision: 1.7 $
Jul 11 10:07:24 lapcb kernel: scsi : 1 host.
Jul 11 10:07:26 lapcb kernel: aha152x_cs: no SCSI devices found
Jul 11 10:07:26 lapcb cardmgr[718]: get dev info on socket 1 failed: Kein passendes Gerät gefunden
Jul 11 10:07:26 lapcb kernel: scsi : 0 hosts.

----------------------------------------
5. inserting Xircom and everything works fine

Jul 11 10:09:04 lapcb cardmgr[718]: initializing socket 0
Jul 11 10:09:04 lapcb cardmgr[718]: socket 0: Xircom CardBus 10/100 Ethernet + 56K Modem
Jul 11 10:09:04 lapcb kernel: cs: cb_alloc(bus 32): vendor 0x115d, device 0x0003
Jul 11 10:09:04 lapcb kernel: ROM image dump:
Jul 11 10:09:04 lapcb kernel:   image 0: 0x000000-0x0001ff, signature PCIR
Jul 11 10:09:04 lapcb cardmgr[718]: executing: 'insmod /lib/modules/2.2.14/pcmcia/cb_enabler.o'
Jul 11 10:09:04 lapcb cardmgr[718]: executing: 'insmod /lib/modules/2.2.14/pcmcia/tulip_cb.o'
Jul 11 10:09:04 lapcb cardmgr[718]: executing: 'insmod /lib/modules/2.2.14/pcmcia/serial_cb.o'
Jul 11 10:09:04 lapcb kernel: cs: cb_config(bus 32)
Jul 11 10:09:04 lapcb kernel:   fn 0 bar 2: mem 0xfb000-0xfb7ff
Jul 11 10:09:04 lapcb kernel:   fn 0 bar 3: mem 0xfa000-0xfa7ff
Jul 11 10:09:04 lapcb kernel:   fn 1 bar 1: io 0x480-0x487
Jul 11 10:09:04 lapcb kernel:   fn 1 bar 2: mem 0xf9000-0xf97ff
Jul 11 10:09:04 lapcb kernel:   fn 1 bar 3: mem 0xf8000-0xf87ff
Jul 11 10:09:04 lapcb kernel:   fn 0 bar 1: io 0x400-0x47f
Jul 11 10:09:04 lapcb kernel:   fn 0 rom: mem 0xf4000-0xf7fff
Jul 11 10:09:04 lapcb kernel:   fn 1 rom: mem 0xf0000-0xf3fff
Jul 11 10:09:04 lapcb kernel: cs: cb_enable(bus 32)
Jul 11 10:09:04 lapcb kernel:   bridge io map 0 (flags 0x21): 0x400-0x487
Jul 11 10:09:04 lapcb kernel:   bridge mem map 0 (flags 0x1): 0xf0000-0xfbfff
Jul 11 10:09:04 lapcb kernel: tulip_reap()
Jul 11 10:09:04 lapcb kernel: tulip_attach(bus 32, function 0)
Jul 11 10:09:04 lapcb kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Jul 11 10:09:04 lapcb kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x400, 00:10:A4:DF:7D:6F, IRQ 11.
Jul 11 10:09:04 lapcb kernel: eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1.
Jul 11 10:09:04 lapcb kernel: serial_attach(bus 32, fn 1)
Jul 11 10:09:04 lapcb kernel: tty02 at 0x0480 (irq = 11) is a 16550A
Jul 11 10:09:04 lapcb cardmgr[718]: executing: './network start eth0'
Jul 11 10:09:04 lapcb kernel: eth0: Promiscuous mode enabled.
Jul 11 10:09:04 lapcb kernel: device eth0 entered promiscuous mode
Jul 11 10:09:04 lapcb cardmgr[718]: executing: './serial start ttyS2'

Ok Problem (almost) solved

Re: None Memory probe issue (David Hinds)
Date: 2000, Jul 13
From: Christoph Blaue cb

The problem is solved due to Dave's hints.
If I include the line 
include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff
in my config.opts the Xircom card is recognized correctly.

I am afraid that my token ring adapter won't work but I will
see this next week, when I have a token ring available.

Thanks so far
Christoph

Question rbe-100, almost works

Date: 2000, Jul 10
From: visnu pitiyanuvath visnu

hello. i have a xircom rbe-100 on a toshiba tecra 8000, running redhat 6.2 (2.2.14 kernel). my card is recognized as a CBEII-10/100, and all pertinent drivers seem to load correctly, but when it looks for the dhcp server, it gets nothing.

i looked at the network, and the card is sending out dhcp discover packets and my dhcp server is sending out offers, but pump doesn't seem to want to cooperate, so it sends out yet another discover packet.

i've tried configuring the interface statically and also in promiscuous mode, but i still don't get any response from my pings of the gateway or computers on the subnet. again, i can see broadcasts coming out of my laptop, but it doesn't want to hear the responses.

everything works under w2k, and i've tried the latest tulip_cb drivers that come in the 3.1.17 tarball, but no change.

any suggestions??

here's a log file for fun:

Jul 10 10:48:13 visnup pcmcia: Starting PCMCIA services:
Jul 10 10:48:13 visnup pcmcia: modules
Jul 10 10:48:13 visnup kernel: Linux PCMCIA Card Services 3.1.8
Jul 10 10:48:13 visnup kernel: kernel build: 2.2.14-12 #1 Tue Apr 25 13:04:07 EDT 2000
Jul 10 10:48:13 visnup kernel: options: [pci] [cardbus] [apm]
Jul 10 10:48:13 visnup kernel: Intel PCIC probe:
Jul 10 10:48:13 visnup kernel: Toshiba ToPIC97 PCI-to-CardBus at bus 0 slot 11, mem 0x68000000, 2 sockets
Jul 10 10:48:13 visnup kernel: host opts [0]: [slot 0xf0] [ccr 0x10] [cdr 0x86] [rcr 0x02] [no pci irq] [lat 168/176] [bus 20/20]
Jul 10 10:48:13 visnup kernel: host opts [1]: [slot 0xf0] [ccr 0x20] [cdr 0x86] [rcr 0x02] [no pci irq] [lat 168/176] [bus 21/21]
Jul 10 10:48:13 visnup kernel: ISA irqs (default) = 3,4,5,7,9,10,12 polling interval = 1000 ms
Jul 10 10:48:14 visnup pcmcia: cardmgr.
Jul 10 10:48:14 visnup rc: Starting pcmcia succeeded
Jul 10 10:48:14 visnup cardmgr[452]: starting, version is 3.1.8
Jul 10 10:48:14 visnup apmd[331]: Now using AC Power
Jul 10 10:48:14 visnup cardmgr[452]: watching 2 sockets
Jul 10 10:48:14 visnup kernel: cs: IO port probe 0x1000-0x17ff: clean.
Jul 10 10:48:14 visnup kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7
Jul 10 10:48:14 visnup kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Jul 10 10:48:14 visnup kernel: cs: cb_alloc(bus 20): vendor 0x115d, device 0x0003
Jul 10 10:48:14 visnup cardmgr[452]: initializing socket 0
Jul 10 10:48:14 visnup kernel: ROM image dump:
Jul 10 10:48:14 visnup kernel: image 0: 0x000000-0xffffffff, signature PCIR
Jul 10 10:48:14 visnup cardmgr[452]: socket 0: Xircom CardBus 10/100 Ethernet
Jul 10 10:48:14 visnup cardmgr[452]: executing: 'insmod /lib/modules/2.2.14-12/pcmcia/cb_enabler.o'
Jul 10 10:48:14 visnup cardmgr[452]: executing: 'insmod /lib/modules/2.2.14-12/pcmcia/tulip_cb.o'
Jul 10 10:48:14 visnup kernel: cs: cb_config(bus 20)
Jul 10 10:48:14 visnup kernel: fn 0 bar 1: io 0x400-0x47f
Jul 10 10:48:14 visnup kernel: fn 0 bar 2: mem 0x6000d000-0x6000d7ff
Jul 10 10:48:14 visnup kernel: fn 0 bar 3: mem 0x6000c000-0x6000c7ff
Jul 10 10:48:14 visnup kernel: fn 0 rom: mem 0x60008000-0x6000bfff
Jul 10 10:48:14 visnup kernel: cs: cb_enable(bus 20)
Jul 10 10:48:14 visnup kernel: bridge io map 0 (flags 0x21): 0x400-0x47f
Jul 10 10:48:14 visnup kernel: bridge mem map 0 (flags 0x1): 0x60008000-0x6000dfff
Jul 10 10:48:14 visnup kernel: tulip_attach(bus 20, function 0)
Jul 10 10:48:14 visnup kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Jul 10 10:48:14 visnup kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x400, 00:10:A4:E9:62:DB, IRQ 3.
Jul 10 10:48:14 visnup kernel: eth0: MII transceiver #0 config 3100 status 7809 advertising 01e1.
Jul 10 10:48:14 visnup cardmgr[452]: executing: './network start eth0'
Jul 10 10:48:15 visnup pumpd[519]: starting at (uptime 0 days, 0:00:30) Mon Jul 10 10:48:15 2000
Jul 10 10:48:30 visnup kernel: eth0: Transmit timed out, status 686980c7, CSR12 000000c4, resetting...
Jul 10 10:48:40 visnup last message repeated 2 times
Jul 10 10:49:15 visnup cardmgr[452]: + Determining IP information for eth0...Operation failed.
Jul 10 10:49:15 visnup cardmgr[452]: + failed.
Jul 10 10:49:15 visnup cardmgr[452]: start cmd exited with status 1
Jul 10 10:49:31 visnup gpm: gpm startup succeeded
Jul 10 10:49:31 visnup gpm[570]: Skipping a data packet (?)
Jul 10 10:49:31 visnup gpm[570]: Error in protocol
Jul 10 10:49:32 visnup last message repeated 64 times
Jul 10 10:49:52 visnup PAM_pwdb[646]: (login) session opened for user root by LOGIN(uid=0)
Jul 10 10:50:41 visnup kernel: eth0: Promiscuous mode enabled.
Jul 10 10:50:41 visnup kernel: device eth0 entered promiscuous mode
Jul 10 10:51:05 visnup kernel: eth0: Transmit timed out, status 686980c7, CSR12 000000c4, resetting...
Jul 10 10:51:40 visnup last message repeated 7 times

None What about the messages with the newer drivers?

Re: Question rbe-100, almost works (visnu pitiyanuvath)
Date: 2000, Jul 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> everything works under w2k, and i've tried the latest tulip_cb drivers
> that come in the 3.1.17 tarball, but no change.

Try showing messages for 3.1.17.  In your message log:

> Jul 10 10:48:30 visnup kernel: eth0: Transmit timed out, status
> 686980c7, CSR12 000000c4, resetting...

you have an interupt delivery problem.  Drivers after 3.1.8 configure
interrupts differently and they should not behave the same.

-- Dave

Ok Untitled

Re: None What about the messages with the newer drivers? (David Hinds)
Date: 2000, Jul 10
From: visnu pitiyanuvath visnu

yeah! things work now. tried installing 3.1.17 again, and now i'm happy.

Question Problems with serial on CEM56

Date: 2000, Jul 11
From: Pål Løberg pallo

After I upgraded the kernel (2.2.9 to 2.2.16) and pcmcia-cs (3.0.14 to 3.1.18) on my Asus F7400 laptop, the serial port stopped working.

If I edit /etc/pcmcia/config so that only xirc2ps_cs is loaded, and not serial_cs, it works fine. However, if I include serial_cs I get the following error when it is loaded:

serial_cs: register_serial() at 0x0ae8, irq 3 failed

I have tried to add "irq_list=0" to the module options, but it still try to use IRQ 3.

The IRQ (3) should be correct - I think - the network card uses it, and serial and ethernet used to share it before I upgraded.

Of course, I may have accidentally overwritten one of the old config files, but I don't remember making any changes like this last time I installed. But that is a long time ago, and I could just have forgotten what I did then....

Any suggestions on how to get this working again?

None The IO port allocations are done differently now

Re: Question Problems with serial on CEM56 (Pål Løberg)
Date: 2000, Jul 11
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> serial_cs: register_serial() at 0x0ae8, irq 3 failed

I'd try removing the 0xa00-0xaff port window in
/etc/pcmcia/config.opts and see if that helps.  You can also remove
the 0x1000-0x17ff window if needed.

-- Dave

None Re: The IO port allocations are done differently now

Re: None The IO port allocations are done differently now (David Hinds)
Date: 2000, Jul 11
From: =?iso-8859-1?Q?P=E5l_L=F8berg?= pallo

> > serial_cs: register_serial() at 0x0ae8, irq 3 failed
> 
> I'd try removing the 0xa00-0xaff port window in
> /etc/pcmcia/config.opts and see if that helps.  You can also remove
> the 0x1000-0x17ff window if needed.

I've tried to change the port windows a bit, but when I remove both
0x1000-0x17ff and 0xa00-0xaff I get the error:

  xirc2ps_cs: no ports available

and notthing works. If I add or change the port windows, I get the same
message as before "serial_cs: register_serial() at 0xXXXX, irq 3 failed"
with different IO addresses.

Any suggestions on how to find the right port windows to use?

 -- Pål

None Do you still have your old log files?

Re: None Re: The IO port allocations are done differently now (=?iso-8859-1?Q?P=E5l_L=F8berg?=)
Date: 2000, Jul 11
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> 
> Any suggestions on how to find the right port windows to use?

I'd find out what was used before you did the driver upgrade.

-- Dave

None Re: Do you still have your old log files?

Re: None Do you still have your old log files? (David Hinds)
Date: 2000, Jul 13
From: =?iso-8859-1?Q?P=E5l_L=F8berg?= pallo

[David Hinds]
> > 
> > Any suggestions on how to find the right port windows to use?
> 
> I'd find out what was used before you did the driver upgrade.

It was 0x300-0x30f for eth0 and 0x02f8-0x02ff for ttyS1, but when I edit
/etc/pcmcia/config.opts and only include the lines:

 include port 0x300-0x3ff
 include port 0x2f8-0x2ff
 include memory 0xc0000-0xfffff 
 include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff

the ethernet drivers fail to load with the error "no ports available",
and the serial is not attempted.

Any ideas? Maybe I could force xirc2ps_cs to use 0x300-0x3ff and serial_cs
to use 0x2f8-0x2ff somehow?

 -- Pål

Ok Xircom RealPort2 CardBus Ethernet 10/100 (R2BE-100BTX)

Date: 2000, Jul 15
From: Ron Pinz rpinz

I have gotten the Xircom RealPort2 CardBus Ethernet 10/100 (R2BE-100TX) 10/100BASE-T card to work with pcmcia-cs-3.1.8 on a IBM Thinkpad 600X running redhat 6.2 by adding the following line to the configfile:

card "Xircom CardBus RealPort2 Ethernet 10/100" version "Xircom", "*", "R2BE-100TX"
    bind "tulip_cb"

cardmgr generates the following logentry for the card:

Jul 14 17:29:17 duhbox cardmgr[406]:   product info: "Xircom", "RealPort2 CardBus Ethernet 10/100", "R2BE-100BTX", "1.00"
Jul 14 17:29:17 duhbox cardmgr[406]:   manfid: 0x0105, 0x0103  function: 6 (network)

Question pcmcia driver update

Date: 2000, Jul 18
From: Ricardo Conde rconde

My xircom modem 33.6 don´t work with linux mandrake 7 on my Satellite 4090xcdt. Davis said this is a kernel bug and sugest to upgrade my driver. I have a new driver (3.1.18) and I need help to install it. What I must to do?

Regards Ricardo Conde

Question Xircom RealPort 10/100 with RedHat 6.2

Date: 2000, Jul 28
From: Thomas Dlouhy tomtom

Hi,
sure I'm new to linux but after serveral tries I think I'm too stupid to get the Xircom RealPort 10/100 running under RedHat 6.2 (with Suse 6.4 it worked fine).

At startup I receive the messages:

Bringing up interface eth0 insmod: /lib/modules/2.2.14-5.0/net/tulip.o: insmod eth0 failed
Delaying eth0 initialization

Do I need newer drivers (where do I get them) which files do I have to modify (and how) .... ???

I'm working on a Toshiba Satellite 4080XCDT with RedHat 6.2

Hope that somebody can help me.
Thanks
tomtom

None Untitled

Re: Question Xircom RealPort 10/100 with RedHat 6.2 (Thomas Dlouhy)
Date: 2000, Jul 28
From: Paulo E. Abreu peabreu

Hiya Well you are trying to insert the module for the pci/isa cards. You should install kernel-pcmcia-cs package and configure the pcmcia script to start at boot If you need more help mail me

Idea Configuration problem?

Re: Question Xircom RealPort 10/100 with RedHat 6.2 (Thomas Dlouhy)
Date: 2000, Aug 02
From: Hester Van Rooyen hester

I had the same messages when I (wrongly) selected a driver when configuring the network using netconf (or linuxconf). Leave the driver, port and irq fields empty, the correct drivers will be picked up automatically. Check the help. I don't know how to erase these once they had been selected, all attempts were ignored and I just reinstalled the Linux.

Hester van Rooyen

Sad Got CBEM56G-100 working (once), now cannot start pcmcia at all

Date: 2000, Jul 28
From: Jason Pringle jpringle

After grabbing the new version (3.1.19) and playing with the port includes, I got the "beep-beep" rather than the "beep-boop". test_network showed the card was up, but no eth0 config'ed. Ok, I thought, let's reboot and have the network (previously configured via netconf) come up on its own.

Uh, uh. Now the base modules won't load (with or without a card inserted). I've tried reverting to includes that previously allowed the base services to load. No dice. It hangs because it's trying to access the CD-ROM!! Here is the "it's failing" log messages:

(Mandrake 7.1, so kernel 2.2.15, pcmcia 3.1.19)

Is it getting hung up on the port scan or the memory scan? Why would either cause a write to the hdb?

Jul 28 04:14:57 jpringle_laptop kernel: Linux PCMCIA Card Services 3.1.19
Jul 28 04:14:57 jpringle_laptop kernel:   kernel build: 2.2.15-4mdk #1 Wed May 10 15:31:30 CEST 2000
Jul 28 04:14:57 jpringle_laptop kernel:   options:  [pci] [cardbus] [apm]
Jul 28 04:14:57 jpringle_laptop kernel: PCI routing table version 1.0 at 0xf0990
Jul 28 04:14:57 jpringle_laptop kernel:   unknown PCI interrupt router 0e11:ae69
Jul 28 04:14:57 jpringle_laptop kernel: Intel PCIC probe:
Jul 28 04:14:57 jpringle_laptop kernel:   TI 1250A rev 02 PCI-to-CardBus at slot 00:0c, mem 0x7fffe000
Jul 28 04:14:57 jpringle_laptop kernel:     host opts [0]: [pci + serial irq] [no pci irq] [lat 66/176] [bus 2/2]
Jul 28 04:14:57 jpringle_laptop kernel:     host opts [1]: [pci + serial irq] [no pci irq] [lat 66/176] [bus 3/3]
Jul 28 04:14:57 jpringle_laptop kernel:     ISA irqs (scanned) = 7,9 polling interval = 1000 ms
Jul 28 04:14:58 jpringle_laptop kernel: hdb: packet command error: status=0x51 { DriveReady SeekComplete Error } 
Jul 28 04:14:58 jpringle_laptop kernel: hdb: packet command error: error=0x54
Jul 28 04:14:58 jpringle_laptop kernel: ATAPI device hdb:
Jul 28 04:14:58 jpringle_laptop kernel:   Error: Illegal request -- (Sense key=0x05)
Jul 28 04:14:58 jpringle_laptop kernel:   Invalid field in command packet -- (asc=0x24, ascq=0x00)
Jul 28 04:14:58 jpringle_laptop kernel:   The failed "Start Stop Unit" packet command was:
Jul 28 04:14:58 jpringle_laptop kernel:   "1b 00 00 00 03 00 00 00 00 00 00 00 "
Jul 28 04:14:58 jpringle_laptop kernel:   Error in command packet byte 38086 bit 0
Jul 28 04:14:58 jpringle_laptop kernel: cdrom: open failed.
Jul 28 04:15:33 jpringle_laptop kernel: end_request: I/O error, dev 02:00 (floppy), sector 0
Jul 28 04:16:07 jpringle_laptop kernel: end_request: I/O error, dev 02:00 (floppy), sector 0
Jul 28 04:17:14 jpringle_laptop last message repeated 2 times                                                   

Also, here's the log from the single time it did work:

Jul 28 02:17:09 jpringle_laptop kernel:     host Jul 28 02:17:09 jpringle_laptop kernel: Linux PCMCIA Card Services 3.1.19
Jul 28 02:17:09 jpringle_laptop kernel:   kernel build: 2.2.15-4mdk #1 Wed May 10 15:31:30 CEST 2000
Jul 28 02:17:09 jpringle_laptop kernel:   options:  [pci] [cardbus] [apm]
Jul 28 02:17:09 jpringle_laptop kernel: PCI routing table version 1.0 at 0xf0990
Jul 28 02:17:09 jpringle_laptop kernel:   unknown PCI interrupt router 0e11:ae69
Jul 28 02:17:09 jpringle_laptop kernel: Intel PCIC probe:
Jul 28 02:17:09 jpringle_laptop kernel:   TI 1250A rev 02 PCI-to-CardBus at slot 00:0c, mem 0x7fffe000
Jul 28 02:17:09 jpringle_laptop kernel:     host opts [0]: [pci + serial irq] [no pci irq] [lat 66/176] [bus 2/2]
Jul 28 02:17:09 jpringle_laptop kernel:     host opts [1]: [pci + serial irq] [no pci irq] [lat 66/176] [bus 3/3]
Jul 28 02:17:09 jpringle_laptop kernel:     ISA irqs (scanned) = 3,4,7,9,10,15 status change on irq 15
Jul 28 02:17:09 jpringle_laptop cardmgr[2967]: starting, version is 3.1.19
Jul 28 02:17:09 jpringle_laptop cardmgr[2967]: watching 2 sockets
Jul 28 02:17:09 jpringle_laptop kernel: cs: IO port probe 0x1480-0x1487: clean.
Jul 28 02:17:09 jpringle_laptop kernel: cs: IO port probe 0x1200-0x147f: clean.
Jul 28 02:17:10 jpringle_laptop kernel: cs: cb_alloc(bus 2): vendor 0x115d, device 0x0003
Jul 28 02:17:10 jpringle_laptop cardmgr[2967]: initializing socket 0
Jul 28 02:17:10 jpringle_laptop cardmgr[2967]: socket 0: Xircom CBEM56G-100 CardBus 10/100 Ethernet + 56K Modem
Jul 28 02:17:10 jpringle_laptop cardmgr[2967]: executing: 'modprobe cb_enabler'
Jul 28 02:17:10 jpringle_laptop cardmgr[2967]: executing: 'modprobe tulip_cb'
Jul 28 02:17:10 jpringle_laptop cardmgr[2967]: executing: 'modprobe serial_cb'
Jul 28 02:17:10 jpringle_laptop kernel: cs: cb_config(bus 2)
Jul 28 02:17:10 jpringle_laptop kernel:   fn 0 bar 2: mem 0x60013000-0x600137ff
Jul 28 02:17:10 jpringle_laptop kernel:   fn 0 bar 3: mem 0x60012000-0x600127ff
Jul 28 02:17:10 jpringle_laptop kernel:   fn 1 bar 1: io 0x1280-0x1287
Jul 28 02:17:10 jpringle_laptop kernel:   fn 1 bar 2: mem 0x60011000-0x600117ff
Jul 28 02:17:10 jpringle_laptop kernel:   fn 1 bar 3: mem 0x60010000-0x600107ff
Jul 28 02:17:10 jpringle_laptop kernel:   fn 0 bar 1: io 0x1200-0x127f
Jul 28 02:17:10 jpringle_laptop kernel:   fn 0 rom: mem 0x6000c000-0x6000ffff
Jul 28 02:17:10 jpringle_laptop kernel:   fn 1 rom: mem 0x60008000-0x6000bfff
Jul 28 02:17:10 jpringle_laptop kernel:   irq 10
Jul 28 02:17:10 jpringle_laptop kernel: tulip_attach(device 02:00.0)
Jul 28 02:17:10 jpringle_laptop kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Jul 28 02:17:10 jpringle_laptop kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x1200, 00:10:A4:05:4B:9D, IRQ 10.
Jul 28 02:17:10 jpringle_laptop kernel: eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1.
Jul 28 02:17:10 jpringle_laptop kernel: serial_attach(device 02:00.1)
Jul 28 02:17:10 jpringle_laptop kernel: tty02 at 0x1280 (irq = 10) is a 16550A
Jul 28 02:17:10 jpringle_laptop cardmgr[2967]: executing: './network start eth0'
Jul 28 02:17:10 jpringle_laptop cardmgr[2967]: + ************************************************
Jul 28 02:17:10 jpringle_laptop cardmgr[2967]: + ***** In the /etc/pcmcia/network script!!! *****
Jul 28 02:17:10 jpringle_laptop cardmgr[2967]: + ************************************************
Jul 28 02:17:10 jpringle_laptop cardmgr[2967]: + Can't find a dhcp client
Jul 28 02:17:10 jpringle_laptop cardmgr[2967]: executing: './serial start ttyS2'

More More config info: this is on a Compaq Armada 7400 <eom>

Re: Sad Got CBEM56G-100 working (once), now cannot start pcmcia at all (Jason Pringle)
Date: 2000, Jul 28
From: Jason Pringle jpringle

None Maybe interrupt scan troubles

Re: Sad Got CBEM56G-100 working (once), now cannot start pcmcia at all (Jason Pringle)
Date: 2000, Jul 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Fri, Jul 28, 2000 at 04:38:26AM -0700, Jason Pringle wrote:
> 
> Is it getting hung up on the port scan or the memory scan? Why would
> either cause a write to the hdb?

The memory scan is only done when a card is inserted.  However I don't
think it is the port scan either (since you say you've already tried
fiddling with the port windows in config.opts).

I think it is an interrupt scan problem, since the interrupt probe
results are coming out different now, compared to the time that
worked.  There are some suggestions in the HOWTO for dealing with
interrupt scan problems.

-- Dave

None Tried some stuff, still broken (kernal panic!)

Re: Sad Got CBEM56G-100 working (once), now cannot start pcmcia at all (Jason Pringle)
Date: 2000, Jul 31
From: Jason Pringle jpringle

Two parts to this message...first: what's happening now, second: more background details

FIRST: The reason the results of the interrupt scan look different is because I'd already started trying to limit the irq's via the config.opts "exclude" directives and the PCIC_OPTS setting for "irq-list". Neither seems to do any good. This last time I set "do_scan=0", ran /etc/rc.d/init.d/pcmcia start and it immediately rebooted the system! On the reboot I didn't catch the LILO prompt to go into single user, so it booted normally (run level 5) and when it got to the pcmcia driver load, I got a kernel panic! Doh!

BACKGROUND: Initially I was having NO problems getting the initial card drivers to load, I just wasn't able to get the cards configured correctly (either the CBEM56G-100 or a older 3com/megahertz 3CCFE574BT, which should be supported). When I got the Xircom to finally be configured, I rebooted. On the shutdown, the system hung when unloading the PCMCIA services - with the same message about attempting to access the DVD drive. Since then, I have not been able to start the cardmgr services (manually or on boot) and keep getting the DVD access error.

Since the system hangs during boot and shutdown required a hard reboot (power off), the system came up and did the disk check. I'm wondering if there's damage to the file system that's causing this problem. Other than a clean install (which is just a time headache, since this is an initial attempt to get this thing up, so no data to lose yet), is there a way to verify this and/or clean things up?

(Newbie question: if the boot or shutdown hangs, is there a key combination to reach a root console and try again (like shutting down the pcmcia services manually and then shutdown/reboot)? Or is it just the big power switch?)

Please help - I'm a bit mystified about what's going on here.

--jason

None Maybe we should back up to the beginning

Re: None Tried some stuff, still broken (kernal panic!) (Jason Pringle)
Date: 2000, Aug 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Can you show me the messages you got back before you started fiddling
with any of the config files?  I am now mostly curious about your
original problem (which you say existed with both the CBEM and a
3CCFE574BT card).

It is not an issue with filesystem damage.  Do not waste your time
reinstalling linux.

You cannot get back to a console prompt after initiating a shutdown.
If you get a lockup there, you are pretty much out of luck.  You can
try doing alt-sysrq-s and alt-sysrq-u to sync and unmount your
filesystems; these may work even if the system seems dead.

-- Dave

Sad RBEM56G-100BTX on HP Omnibook 4150

Date: 2000, Jul 29
From: Hester Van Rooyen hester

I am trying to install RedHat 6.2 Linux kernel 2.2.14-5.0 on an HP Omnibook 4150 with Xircom RealPort Cardbus Ethernet 10/100 + Modem 56. Sometimes it boots fine and both network and modem works. But most of the time the notebook hangs solidly during boot with the card inserted, card insertion or card removal. It worked fine with a borrowed 3Com card, also my card worked on a friend's (no-name!) laptop.

I have complete log files, but dont' know how to pull it all in here! In essence, in the log of a failed boot, I get the following after cardmgr has started:

  cs:cb_alloc(bus 32): vendor 0x115d, device 0x0003
  kmem_grow: Called nonatomically from int - size - 128

It then probes the ports (apparently successfully), identifies the Xircom on socket 0 and loads the modules. The last message is:

  executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/serial_cb.o'

In cases where it boots successfully, the kmem_grow message does not appear. Also it then uses irq3 for the network and modem, and irq 11 for card detection. I also have an ESS Maestro PCI Audio card on irq 10. I tried various irq settings, with no effect.

I got rev 3.1.8 of cardctl with the RedHat, but also downloaded 3.1.19 - same problem.

I am fairly new to Linux and hope I am not just being stupid, bu I have to get this working for a client urgently, so I hope somebody will help me!

None It seems to be a common problem

Re: Sad RBEM56G-100BTX on HP Omnibook 4150 (Hester Van Rooyen)
Date: 2000, Jul 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I have had several identical reports for the combination of this
particular laptop model and this card.  I can't reproduce the problem
on my systems.  I suggested that someone try:

  CORE_OPTS="reset_time=1000 unreset_delay=100"

but he never replied.

-- Dave

Idea Possible solution

Re: Sad RBEM56G-100BTX on HP Omnibook 4150 (Hester Van Rooyen)
Date: 2000, Aug 02
From: Hester Van Rooyen hester

In-Reply-To: <20000731123704.B12995@valinux.com>

I tried the above suggestion by David Hinds, but it had no effect.

I then read in Rel 0.89 of the HP-HOWTO (p69) that on an Omnibook XE there is an i/o port conflict between the sound card and PCMCIA card, and that line 6 in the file /etc/pcmcia/config.opts shoulds be modified as follows:

  include port 0x300-0x4ff, port 0x1000-0x17ff

This seems to solve the problem! I have booted the notebook with the Xircom card inserted several times and have had no further problems.

The reason is not quite clear though, because according to the system log, the ESS Maestro sound card uses port 0xf800. I have sent e-mail to the author of the HP-HOWTO to ask for more information, which I will post here when I reaceive something.

I would also appreciate some advice on installing a new version of the pcmcia drivers. When I boot with rev 3.1.8 which came with the RedHat, driver modules are loaded using insmod and everything seems fine. When I installed rev 3.1.19 following the instructions in the HOWTO, I see the following in the system log :

 cardmgr: Card services does not match

It then loads the driver modules using modprobe, and the network starts up as inactive. Attempts to use the network result in the following messages in the log:

 modprobe: Can't locate module block-major-22

I guess I must do something extra to introduce the new modules to the kernel, but what?

Thanks

Hester van Rooyen

None That's good news

Re: Idea Possible solution (Hester Van Rooyen)
Date: 2000, Aug 02
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> 
> This seems to solve the problem! I have booted the notebook with the
> Xircom card inserted several times and have had no further problems.

That's very interesting.  You might try reconfiguring the PCMCIA
drivers with "PnP BIOS support" enabled.  Then look at the output of
"lspnp -v" to get a detailed resource listing for all your devices.

Regarding installing the new PCMCIA drivers, go to the 3.1.19
directory and do "make config" again and carefully check the output.
I suspect that you've got some sort of mismatch between your kernel
tree and the kernel you're running.  You can also run the "test_setup"
script in the debug-tools directory.

>  modprobe: Can't locate module block-major-22

My guess is that this message has nothing to do with the network
device.  Block major device 22 is an IDE device.

-- Dave

Feedback Experiments with driver revisions

Re: Sad RBEM56G-100BTX on HP Omnibook 4150 (Hester Van Rooyen)
Date: 2000, Aug 11
From: Hester Van Rooyen hester

I managed to install the 3.1.19 PCMCIA drivers, not sure what went wrong the first time.

Some corrections to my previous messages:

 - the kmem_grow message sometimes appear with a successful boot as well, seems to be unrelated 
 - the missing block-major-22 is related to removing the CD-ROM module.

I experimented with various driver revisions and found the following:

(i) 3.1.8: I can boot successfully with I/O ports in the range 0x300-0x4ff (uses 0x400-0x47f, 0x480-0x487) or 0x200-0x4ff (uses 0x200-0x27f, 0x280-0x287). When allowing the range 0x100-0x4ff, it usually hangs, but uses 0x200-0x27f, 0x280-0x287 when successful. Network is active after boot and works fine.

(ii) 3.1.19 without pnp: similar to above, but network is always inactive after boot.

(iii) 3.1.19 with pnp: It seems to always use I/O port range 0x1000-0x1087 and differnet IRQs from the other two revisions. However, the network is also inactive after boot. I never had it hung.

I am sending mail with some attachments to David which I hope will be useful. I will for now settle for 3.1.8 with restricted ports, maybe experiment more later-on.

Hester van Rooyen

Question Xircom R2E100 and Kernel Question ?

Date: 2000, Aug 01
From: Leszek Szychowski leszek

1. Has anyone managed to get the new R2E100 Xircom working with the ti8225 chipset as in the Compaq Armada 500 laptops.

2. How do I install the latest Kernel - currently running 2.2.14-5.0, going to 2.2.16-3. After using RPM, it appeared to install, but now after booting the system points to the previous location of /lib/modules/2.2.14-5.0 not /lib/modules/2.2.16-3.

Any Ideas ?

TIA

Feedback Update so far ..

Re: Question Xircom R2E100 and Kernel Question ? (Leszek Szychowski)
Date: 2000, Aug 01
From: Leszek Szychowski leszek

I managed to get problem 2. sorted out by changing the lilo kernel name to boot from.

I also managed to get the PCMCIA 3.1.18 module to recognise the R2E100BTX. using the xirc2ps_cs driver. However, I don't know how to get eth0 configured to use this device. I know I'm close, just need a hint or two !

Any Ideas ?

Sad RBEM56G-100 Ethernet OK, Modem failing

Date: 2000, Aug 01
From: Don Myroon dmyroon

Hi,

I have a RBEM56G-100 PCMCIA card in a DELL Inspiron 7500.

The ethernet portion works quite well.  It's not perfect as I do get RX errors:

drizzt:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:10:A4:C4:52:BA  
          inet addr:192.168.0.8  Bcast:192.168.0.255 mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:56 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:11 Base address:0x200 

The modem, on the other hand, it quite flawed.  It will
connect and work fine until it decides to stop.  It will only
stop on certain things - like a web page or ftp site.

When it stops, I go somewhere else and it works fine. 
Example, whenever I try to download the file:
ftp://metalab.unc.edu/pub/Linux/distributions/redhat/updates/6.2/i386/kernel-source-2.2.16-3.i386.rpm
it will get about the first 30K and then stall....
but I can go to a different ftp site and get a different file
in the same session.   It will ALWAYS fail on that particular
file.
There are certain web pages that do the same thing.

Does anyone know what the problem might be?  I wrote to Xircom
and they told me that they are actively working with the open
source community to develop tulip_cb.c.  True?

Thanks for the help.

Don

Note Untitled

Re: Sad RBEM56G-100 Ethernet OK, Modem failing (Don Myroon)
Date: 2000, Aug 01
From: Don Myroon dmyroon

Oh.. I see there were no RX errors in eth0 in the message I posted...  Now I'm not sure if I saw errors there or not....

This is the output from ppp0 though:


ppp0      Link encap:Point-to-Point Protocol  
          inet addr:161.184.192.147  P-t-P:198.161.157.70  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:728 errors:19 dropped:0 overruns:0 frame:19
          TX packets:677 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10 

Thanks again everyone.

Don

None Maybe a modem init string issue?

Re: Sad RBEM56G-100 Ethernet OK, Modem failing (Don Myroon)
Date: 2000, Aug 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> 
> Does anyone know what the problem might be?  I wrote to Xircom
> and they told me that they are actively working with the open
> source community to develop tulip_cb.c.  True?

Not to my knowledge.  But since the tulip_cb (ethernet) driver is
working ok, that is not your problem.  The modem is unrelated and just
uses the regular kernel serial driver.

I'm afraid I don't really know what to suggest regarding the modem
problem.  Maybe it is a matter of choosing the right modem init
string.  The pamphlet that came with my CBEM card doesn't have any
suggestions.  But looking at the .INF file for the modem on the driver
disk, I'd try the following init string:

    AT &F E0 &C1 &D2 V1 S0=0 S95=45 W2

-- Dave

Disagree It maybe a interupt sharing issue

Re: None Maybe a modem init string issue? (David Hinds)
Date: 2000, Aug 05
From: Jeff Johann <jjohann@kiva.net>

This is the same problem that was discussed earlier in topic 59. Using the latest rev 3.1.19 i am still getting intermittant hangs with the serial ppp links. Sometimes the transfer of a large file will hang at 5-7 K downloaded for for 3-5 minutes and then continue on to completion. on older versions of the pcmcia tools(~3.1.16) the downloads completely stalled after about ~70K download.

looking at the discussion forums at http://pcmcia.sourceforge.org/cgi-bin/HyperNews/get/pcmcia/serial.html there are duscissions of interupt conflicts and ioport problems. Thread 12 covers this in some detail.

I am willing to capture logs and recompile changes if someone has any suggestions.

None I still don't see any evidence

Re: Disagree It maybe a interupt sharing issue (Jeff Johann)
Date: 2000, Aug 07
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Yes, the problem has been reported by lots of people.  I still don't
see anything in those threads to make me think it is an interrupt
sharing issue.

Did you try the modem init string I suggested?

-- Dave

None Re: Maybe a modem init string issue?

Re: None Maybe a modem init string issue? (David Hinds)
Date: 2000, Aug 16
From: Don Myroon dmyroon

David,

I tried the init string and I still have the same problem.  My problem
seems the same as the one that Jeff Johann is having.  It seems that it
is happening to more people than just me - and very similar problems.

I, like Jeff, am willing to help out in any way I can.  I have the time
- just let me know.

Thanks very much David.

Sincerely,

Don Myroon


David Hinds wrote:
> 
> If you reply to this message at HyperNews@pcmcia.sourceforge.org, include:
> In-Reply-To: <20000801103856.G14391@valinux.com>
> 
> >
> > Does anyone know what the problem might be?  I wrote to Xircom
> > and they told me that they are actively working with the open
> > source community to develop tulip_cb.c.  True?
> 
> Not to my knowledge.  But since the tulip_cb (ethernet) driver is
> working ok, that is not your problem.  The modem is unrelated and just
> uses the regular kernel serial driver.
> 
> I'm afraid I don't really know what to suggest regarding the modem
> problem.  Maybe it is a matter of choosing the right modem init
> string.  The pamphlet that came with my CBEM card doesn't have any
> suggestions.  But looking at the .INF file for the modem on the driver
> disk, I'd try the following init string:
> 
>     AT &F E0 &C1 &D2 V1 S0=0 S95=45 W2
> 
> -- Dave
> 
> -------------------------------------------------------------
> Visit this HyperNews at pcmcia.sourceforge.org message (to reply or unsubscribe) at:
> http://pcmcia.sourceforge.org/cgi-bin/HyperNews/get/pcmcia/xircom/111/2.html

Question Anything new on RBE-100 Problem?

Date: 2000, Aug 01
From: Mathias de Riese deriese

I have a RBE-100 Card with the usual Problem: Everything looks fine, but nothing goes thru. Once set to promisc, it works. The problem is, that im not allowed to do that on my site. I would be REALLY happy, when the problem would be solved.

Maybe i can help somehow. I dont want to bore You with the usual stuff as mentioned in the HOWTO, because its in here somehow. Maybe i can do some more special tests. Tell me what to do. Would send You the card if i were in the States and wouldnt need it for a while, but both is not the case.

Hope to hear something. Thanx, Mathias

Question New card: XE2000, doesn't work, what do I do?

Date: 2000, Aug 02
From: Rob Landley landley

/var/log/messages says it's an unrecognized card.

The thing identifies itself as "Xircim", "10/100 PC Network Card", "XE2000", "1.00".

Manufacturer ID 0x0105, 0x0108, function 6

xirc2ps_cs can be forcibly insmodded but this does nothing useful. I've tried to load tulip_cb but it complains that unregister_driver and register_driver are unresolved symbols. (It compiled the module, gave me the .o file, but it won't work. I dunno...)

This is all stock red hat 6.2, pcmcia 3.1.18 I think.

I'd like to get this card working rather than return it to the store, but I have only a vague idea about what I'm doing.

Help? Anybody?

Rob

None Loading a driver by hand won't do any good

Re: Question New card: XE2000, doesn't work, what do I do? (Rob Landley)
Date: 2000, Aug 02
From: David Hinds <dhinds@pcmcia.sourceforge.org>

There is a section in the PCMCIA-HOWTO about how to handle unsupported
cards.

You can't just insmod a driver: you need to add an entry to
/etc/pcmcia/config first to tell cardmgr which driver to use for this
card.  After that, the driver will be loaded for you.

Based on the "XE2000" name, I would try both the xirc2ps_cs and
pcnet_cs drivers (the pcnet_cs driver is for "NE2000 compatible
cards", and I suspect this Xircom card may be one of them).

-- Dave

Question Xircom re-100 and Linux 6 compared to 7.1

Date: 2000, Aug 03
From: Daniel Gericke artagel_99

Hi, I recently instealled the Linux Mandrake 7.1 OS and My PCMCIA Xircom RE-100 card didn't work. I had an old copy of Mandrake 6.0 laying around and I tried it..and it detected my network card. Why would my card work in an older version but not in a new one? Isn't that kind of backwards. Anyone have any ideas? I did download the pcmcia-cs files and compiled them. With no luck. I would really like to use the 7.1 version of mandrake. Thanks a lot -Dan

None Not a useful bug report without more details

Re: Question Xircom re-100 and Linux 6 compared to 7.1 (Daniel Gericke)
Date: 2000, Aug 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

What does "didn't work" mean exactly?

And when you downloaded the new drivers what did "no luck" mean?

What kind of laptop is this?

etc.

-- Dave

More More details

Re: None Not a useful bug report without more details (David Hinds)
Date: 2000, Aug 04
From: Daniel Gericke artagel_99

Hi again, I have a Gateway solo 9300. When I install mandrake 7.1. It doesn't detect the network card at all. I don't hear the beeps from carmgr or anything. I do ifconfig and it doesn't show a network card present in my system. I installed the latest version of pcmcia-cs and still no cards under ifconfig. Now when I reinstalled with the 6.0. It will detect my pcmcia card right away and I can configure it....it will show up on ifconfig and I can ping/traceroute etc. I didn't even have to install your pcmcia-cs package. I hope that's enough info. I'm just wondering why it works in the older version but not the newer. -Dan

None Still not nearly enough information

Re: More More details (Daniel Gericke)
Date: 2000, Aug 04
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You say you don't hear beeps when you insert the card.

The reason for that might be that PCMCIA services are turned off in
your /etc/sysconfig/pcmcia file.  I can't really guess; there is a
section in the PCMCIA-HOWTO about Red Hat and Mandrake that has a few
tips like checking this file.  You could also check your system log.

The new drivers generally work significantly better than older ones.

-- Dave

Question How to install Xircom R2BE-100BTX Realport 2 (newbie Caldera 6.4)

Date: 2000, Aug 07
From: Nicholas Graham nickg

Hi folks,

I've just installed linux for the first time on my laptop. Went surprisingly well except for a few peripherals, (USB (can almost live without), modem (only a winmodem), & ethernet (which I need)

I need help installing my Cardbus card; it's a Xircom R2BE-100BTX Realport 2. I am using Caldera 6.x, kernel 2.2.14 on a Sony Vaio PCG-F430 with 64MB RAM.

Normally I'd RTFM, but the links from this page were down!

Basically, if someone could help me install (bearing in mind I'm a linux newbie, I'd be very grateful!! I'm sure what Ron Pinz said below makes sense to most of you...

Thanks!

Nick

rlinz wrote: Xircom RealPort2 CardBus Ethernet 10/100 (R2BE-100BTX) Forum: Xircom PCMCIA Ethernet Adapter Issues Date: Jul 15, 12:21 From: Ron Pinz rpinz

I have gotten the Xircom RealPort2 CardBus Ethernet 10/100 (R2BE-100TX) 10/100BASE-T card to work with pcmcia-cs-3.1.8 on a IBM Thinkpad 600X running redhat 6.2 by adding the following line to the configfile:

card "Xircom CardBus RealPort2 Ethernet 10/100" version "Xircom", "*", "R2BE-100TX"
    bind "tulip_cb"
cardmgr generates the following logentry for the card: 

Jul 14 17:29:17 duhbox cardmgr[406]:   product info: "Xircom", "RealPort2 CardBus Ethernet 10/100", "R2BE-100BTX", "1.00"
Jul 14 17:29:17 duhbox cardmgr[406]:   manfid: 0x0105, 0x0103  function: 6 (network)

Sad Xircom RealPort 10/100 RBEM56G-100 with RedHat 6.1

Date: 2000, Aug 18
From: Marco serra serra

Hi all,
I'm running on my Dell Inspiron 3700 Linux RedHat 6.1 (2.2.12-20) and I have a Xircom RealPort 10/100 RBEM56G-100.
I was running with this configuration for the last 6 months connected (with a static IP address) to a 10 Mb LAN without any problem .... but the last week the network
amministrators changed the configuration of "some switch"
and after that I have an error at the startup
(Bringing up the eth0 interface .... failed)
and now my card doesn't work.
If now for example I try to activate the eth0 interface from the contro-panel I have:
....
ipcalc: ip address expected
ipcalc: ip address expected
ipcalc: ip address expected
ipcalc: ip address expected
broadcast: Host name lookup failure
Usage: grep [OPTION] ... PATTERN [FILE] ...
Try 'grep --help' for more information.
netmask: Host name lookup failure
SIOCADDRT: Network is unreachable
expr: syntax error

??????????????????????????????????????????????????????
??????????????????????????????????????????????????????

I am fairly new to Linux but I really have no idea
what I can do ?

I hope somebody can help me.

      thanks, Marco
p.s.
With Win the card works fine :-(( GRRRRRRR

None Strange script errors

Re: Sad Xircom RealPort 10/100 RBEM56G-100 with RedHat 6.1 (Marco serra)
Date: 2000, Aug 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> ipcalc: ip address expected
> ipcalc: ip address expected
> ipcalc: ip address expected
> ipcalc: ip address expected
> broadcast: Host name lookup failure
> Usage: grep [OPTION] ... PATTERN [FILE] ...
> Try 'grep --help' for more information.
> netmask: Host name lookup failure
> SIOCADDRT: Network is unreachable
> expr: syntax error

I don't really understand how someone changing a setting on a switch
could cause these sorts of errors with the Red Hat network startup
script.

Maybe you should ask them exactly what they changed.  Are you quite
sure that whatever change they made is what caused this problem, and
it isn't just a coincidence?  Looking at the messages, it looks like
there is something really wrong with your network settings.

Do you get the same series of errors if you just type "ifup eth0"?  If
so, then you could post the output of "sh -x /sbin/ifup eth0".

-- Dave

Question No network using Xircom RBEM56G-100

Date: 2000, Aug 25
From: Stuart Pedler <stuart.pedler@sbs.siemens.co.uk>

I have a Siemens Scenic 510 Mobile and a Xircom RBEM56G-100 CardBus. I am running Red Hat 2.2.5-15 and cannot get the card to see the network. The distribution package of card services always tried to set IRQ 0 on the card and failed to start the network. I therefore installed card services 3.1.19 and the card now configures. I cannot however ping anything on the network. Everything looks ok so I have included the syslog and the output of ifconfig,
Any ideas anyone.

Aug 25 13:58:11 SBS_ESCOM network: Bringing up interface lo succeeded
Aug 25 13:58:18 SBS_ESCOM kernel: Linux PCMCIA Card Services 3.1.19
Aug 25 13:58:18 SBS_ESCOM kernel: kernel build: 2.2.5-15 #1 Mon Apr 19 23:00:46 EDT 1999
Aug 25 13:58:18 SBS_ESCOM kernel: options: [pci] [cardbus] [apm] [pnp]
Aug 25 13:58:18 SBS_ESCOM kernel: PCI routing table version 1.0 at 0xf57d0
Aug 25 13:58:18 SBS_ESCOM kernel: PnP: PNP BIOS installation structure at 0xc00fdab0
Aug 25 13:58:18 SBS_ESCOM kernel: PnP: PNP BIOS version 1.0, entry at f0000:3cb7, dseg at f0000
Aug 25 13:58:18 SBS_ESCOM kernel: Intel PCIC probe:
Aug 25 13:58:18 SBS_ESCOM kernel: O2Micro OZ6832/33 rev 02 PCI-to-CardBus at slot 00:0a, mem 0x68000000
Aug 25 13:58:18 SBS_ESCOM kernel: host opts [0]: [pci irq 9] [lat 168/176] [bus 32/34]
Aug 25 13:58:18 SBS_ESCOM kernel: host opts [1]: [pci irq 10] [lat 168/176] [bus 35/37]
Aug 25 13:58:18 SBS_ESCOM kernel: PCI card interrupts, PCI status changes
Aug 25 13:58:18 SBS_ESCOM kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Aug 25 13:58:18 SBS_ESCOM kernel: cs: IO port probe 0x0800-0x08ff: clean.
Aug 25 13:58:18 SBS_ESCOM kernel: cs: IO port probe 0x0100-0x04ff: clean.
Aug 25 13:58:18 SBS_ESCOM kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Aug 25 13:58:18 SBS_ESCOM cardmgr[923]: starting, version is 3.1.19
Aug 25 13:58:18 SBS_ESCOM cardmgr[923]: watching 2 sockets
Aug 25 13:58:19 SBS_ESCOM kernel: cs: cb_alloc(bus 32): vendor 0x115d, device 0x0003
Aug 25 13:58:19 SBS_ESCOM cardmgr[923]: initializing socket 0
Aug 25 13:58:19 SBS_ESCOM cardmgr[923]: socket 0: Xircom CBEM56G-100 CardBus 10/100 Ethernet + 56K Modem
Aug 25 13:58:19 SBS_ESCOM cardmgr[923]: product info: "Xircom", "CardBus Ethernet 10/100 + Modem 56", "CBEM56G", "1.03"
Aug 25 13:58:19 SBS_ESCOM cardmgr[923]: manfid: 0x0105, 0x0103 function: 6 (network)
Aug 25 13:58:19 SBS_ESCOM cardmgr[923]: executing: 'modprobe cb_enabler'
Aug 25 13:58:19 SBS_ESCOM cardmgr[923]: executing: 'modprobe tulip_cb'
Aug 25 13:58:19 SBS_ESCOM cardmgr[923]: executing: 'modprobe serial_cb'
Aug 25 13:58:19 SBS_ESCOM kernel: cs: cb_config(bus 32)
Aug 25 13:58:19 SBS_ESCOM kernel: fn 0 bar 2: mem 0x60013000-0x600137ff
Aug 25 13:58:19 SBS_ESCOM kernel: fn 0 bar 3: mem 0x60012000-0x600127ff
Aug 25 13:58:19 SBS_ESCOM kernel: fn 1 bar 1: io 0x480-0x487
Aug 25 13:58:19 SBS_ESCOM kernel: fn 1 bar 2: mem 0x60011000-0x600117ff
Aug 25 13:58:19 SBS_ESCOM kernel: fn 1 bar 3: mem 0x60010000-0x600107ff
Aug 25 13:58:19 SBS_ESCOM kernel: fn 0 bar 1: io 0x400-0x47f
Aug 25 13:58:19 SBS_ESCOM kernel: fn 0 rom: mem 0x6000c000-0x6000ffff
Aug 25 13:58:19 SBS_ESCOM kernel: fn 1 rom: mem 0x60008000-0x6000bfff
Aug 25 13:58:19 SBS_ESCOM kernel: irq 9
Aug 25 13:58:19 SBS_ESCOM kernel: tulip_attach(device 20:00.0)
Aug 25 13:58:19 SBS_ESCOM kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Aug 25 13:58:19 SBS_ESCOM kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x400, 00:10:A4:C5:BB:F1, IRQ 9.
Aug 25 13:58:19 SBS_ESCOM kernel: eth0: MII transceiver #0 config 3100 status 7809 advertising 01e1.
Aug 25 13:58:19 SBS_ESCOM kernel: serial_attach(device 20:00.1)
Aug 25 13:58:19 SBS_ESCOM kernel: tty01 at 0x0480 (irq = 9) is a 16550A
Aug 25 13:58:19 SBS_ESCOM cardmgr[923]: executing: './network start eth0'
Aug 25 13:58:19 SBS_ESCOM cardmgr[923]: executing: './serial start ttyS1'
Aug 25 13:58:20 SBS_ESCOM cardmgr[923]: exiting


IFCONFIG--------------------------------------------

eth0 Link encap:Ethernet HWaddr 00:10:A4:C5:BB:F1
          inet addr:51.128.176.9 Bcast:51.128.176.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:9 Base address:0x400

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:3924 Metric:1
          RX packets:59 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

Feedback Here is how it worked for me

Re: Question No network using Xircom RBEM56G-100 (Stuart Pedler)
Date: 2000, Aug 25
From: Stefan Kluth Stefan

Hi, I had similar problems with this card. I edited
the script /etc/pcmcia/network to contain the line

ifconfig $DEVICE down up

after the line

/sbin/ifconfig $DEVICE up $IPADDR $NM $BC $MTU

in the "$IPADDR" section and also in the function
bootp_setup  to get dhcp working. The trick is somehow
to restart the card/driver. To be honest, I don't know
why this works. If somebody does know, please tell me,
this is bothering me now since 1/2 year. 

cheers, Stefan

Sad Untitled

Re: Feedback Here is how it worked for me (Stefan Kluth)
Date: 2000, Aug 25
From: Stuart Pedler <stuart.pedler@sbs.siemens.co.uk>

Thanks for your response. Unfortunately I have tried what you suggested but I still cannot tx or rx on the network. Anymore suggestions will be gratefully accepted.

News here is more detail of my setup

Re: Sad Untitled (Stuart Pedler)
Date: 2000, Aug 25
From: Stefan Kluth Stefan

Hi, 

damn, I thought I could do some magic here. The symtoms I 
had matched your description, i.e. ifconfig looked ok. One
thing I noticed was that "route" wasn't set up correctly,
it did not have a default route. Check the output of 
"route" to see what happens in your case. If there is a 
problem you can try to add a default route by hand. 

My setup is like this; I have
a DELL I3700 and a RBEM56G 10/100 card. I run Debian potato
(its just out, see www.debian.org) with kernel 2.2.17 and 
pcmcia-cs 3.1.19. My trick already worked with 2.2.13 and
pcmcia-cs 3.1.8. 

If you are still stuck and you are willing to play a bit
more you could have a look at

http://www.scyld.com/network/updates.html and
http://www.scyld.com/network

There seems to be a way to drive a tulip based CardBus pcmcia
card with the normal tulip driver in the kernel. I did
not try this since my card works :) but perhaps it helps
you.

BTW, to the general public on this list, has anybody ever 
tried this? Should this approach be a part of the pcmcia-cs
package?

cheers, Stefan

None That tulip driver won't help you

Re: News here is more detail of my setup (Stefan Kluth)
Date: 2000, Aug 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Donald Becker's tulip driver doesn't support the Xircom CardBus cards
at all.

-- Dave

Question Is there anything we can do?

Re: None That tulip driver won't help you (David Hinds)
Date: 2000, Aug 25
From: Stefan Kluth Stefan

Hm, that's too bad, it looked good at the beginning.
Are the tulip chips in the Xircom RBEM56G CB cards 
different from the tulip chips on regular ethernet cards?

Anyway, do you have ideas as to what we could actively do
to improve the tulip_cb driver? 

None Well, there are always things you can do

Re: Question Is there anything we can do? (Stefan Kluth)
Date: 2000, Aug 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> Are the tulip chips in the Xircom RBEM56G CB cards 
> different from the tulip chips on regular ethernet cards?

Yes, they are a somewhat weird almost-clone.

> Anyway, do you have ideas as to what we could actively do
> to improve the tulip_cb driver? 

You can get the datasheet from Xircom's web site and work on the
driver if you're up for that.

-- Dave

News similiar problem solved

Re: Sad Untitled (Stuart Pedler)
Date: 2000, Sep 13
From: Sven Höfer sven

hi,

i've a similiar problem with my rbem-56g100.

because i have to use some windows-software in my lab i reboot
often my laptop to switch between windows98 and linux (2.2.16
and pcmcia 3.1.20). everytime i had a problem to recognize the
network after a reboot from windows. 
the logs showed that network and route service failed but 
network looked ok. the route service wasn't started. after two 
(!) reboots everything is ok and i can work without problems
with network and modem (independent from further reboots of
linux). one boot of windows is enough to destroy this behavior!

some restarts from network and route should solve this
problem: at the moment i have a script which restarts two
times the network service and then it starts the route service
and everything is fine.

the network script is from suse linux and interweaved with 
other system scripts. my next goal is to find the thing what 
changes the behavior.

i have no experience with the pcmcia bus but it's strange for 
me that some things can survive a cold reboot (init of pcmcia 
bus from windows?).

greetings,
sven

None You can try putting the card in promisc mode

Re: Question No network using Xircom RBEM56G-100 (Stuart Pedler)
Date: 2000, Aug 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

That work-around is mentioned in the BUGS file.

-- Dave

Angry Frustrated newbie plees for help

Date: 2000, Aug 28
From: Dan Yamauchi DYamauchi

i have a Compaq Armada v300 with a Xircom RealPort CardBus 10/100, I'm running Mandrake 7.0, and I'm having real problems connecting to my school network. One problem I have is that I don't have all of the network info (the sys admin hates all linux users and won't release any information)But I think I have gotten most of the information of a friends computer. But I'm not sure if the reason I can't connect to the network is because of lack of info, or a misconfigured card. My system does recognize the card, but I'm not sure if it is configured right. Are there any tools that I can use to automaticaly detect LAN info? Or is there any tool to tell if my card is configured right for my LAN? Please help, any advice would be greatly appreciated.

Sad RB100 - ping itself ok, ping outside no response, arp no h/w address

Date: 2000, Aug 28
From: Alan Tam dogwheel

hi,

I have just upgraded from RedHat 6.0 to 6.2 Then upgraded kernel to 2.2.16 and pcmcia package to 3.1.19

The system and pcmcia boot up normally and successfully, eth0 come up successfully. The xircom realport cardbus 10/100+56 can ping its own IP address. But when it fails to ping an IP on the LAN. Typing "arp -a" even shows incomplete hardware address.

I've also tried changing the "pcmcia" startup script order with "network" - no improvements. I've tried using pcmcia 3.1.8 with my new kernel - no improvements.

I used to use kernel 2.2.9 and pcmcia 3.0.12 before. Everything is working fine. I can now boot back this old kernel with old pcmcia package. The LAN card work normally when booted back.

Any idea? Any body here successfully in making it with 2.2.16 & 3.1.19?

Regards, Alan

Note more info

Re: Sad RB100 - ping itself ok, ping outside no response, arp no h/w address (Alan Tam)
Date: 2000, Aug 28
From: Alan Tam dogwheel

hi,

After enable the card with promiscous mode, I got it successfully in pinging outside world and "arp -a" shows correct MAC address of other computer on the LAN

I read from the "known problems" that tulip_cb.c is unstable with Xircom Cardbus Realport because there are so many chip version of Digital Tulip chip.

???Any hints on modifying the tulip_cb.c such that I don't need to enable promiscous for my card (it's too cpu intensive because i am in a very busy hub segment of my office)??? Alternatively, if you have experience, which OLD pcmcia-cs package works to me?

Thanks Alan

P.S. "known problems" URL is http://pcmcia-cs.sourceforge.net/ftp/BUGS

Note more info

Re: Sad RB100 - ping itself ok, ping outside no response, arp no h/w address (Alan Tam)
Date: 2000, Aug 28
From: Alan Tam dogwheel

Summary of my Findings (all the following is under kernel 2.2.16, and my card is probed as DEC 21143 compatible mode revision 3)

pcmcia-cs 3.0.14:
  compile tulip_cb.c v0.91 4/14/99
  probed my eth0 at 0xa00
  probed my ttyS0 at 0xa80
  *result: two high beeps during boot, eth0 UP and responds to pings from attaching network

pcmcia-cs 3.1.19:
  compile tulip_cb.c v0.91g 7/16/99
  probed my card as DEC 21143 compatible mode revision 3
  probed my eth0 at 0x100
  probed my ttyS0 at 0x180
  *result: two high beeps during boot, eth0 UP but NOT responds to pings from attaching network
  *resolution: after enabled promiscous mode it can be ping

Any idea? Is 3.1.19 wrongly probed the address?

Regards, Alan

Ok more info - ok now

Re: Note more info (Alan Tam)
Date: 2000, Aug 31
From: Alan Tam dogwheel

well, seems that my problem is too bored since no one respond...

finally i managed to get all things work. just added one line inside the bootp() call in the /etc/pcmcia/network script, enabling my xircom card enter promisc mode then dhcp can now get an IP successfully. later on the card leave promiscous mode BUT it still receive and transmit packets. this is what i wanted and achieved:

1. dhcp works 2. no need to be in promisc mode

still not perfect are the quite serious TX errors which populate my "dmesg"

having used this xircom cardbus realport for over a year, the card really shines - but with quite a lot of effort in making it work in its area.

dogwheel

Question RBEM56G100 TX carrier errors on 100baseT network

Date: 2000, Sep 01
From: Stefan Kluth Stefan

Hi,

I recently got an upgraded network connection to 100baseT.
Now I get 100% TX packets carries errors, i.e. there is an
carier error for every TX packet. Here is the output of
ifconfig (I blanked my addresses):

lapkluth:/home/skluth# ifconfig
eth0      Link encap:Ethernet  HWaddr  
          inet addr: Bcast:  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20679 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:3185 dropped:0 overruns:0 carrier:3185
          collisions:0 

Then I got Donald Becker diagnostic programs and ran
tulip_diag.c (see output below). What I think is inconsistent
is that at the top we read:

"Port selection is MII, half-duplex"

while at the bottom we have

"Auto-negotiation complete, 100Mbps full duplex."

Any hints here?

cheers, Stefan


************************************************************

lapkluth:/home/skluth/scratch/pcidiag# ./tulip-diag -t 0 -p 0xa00 -mm -ee -aa 
tulip-diag.c:v2.03 7/31/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Assuming a Digital Tulip series adapter at 0xa00.
Digital Tulip series chip registers at 0xa00:
  fea08000 ffffffff ffffffff 0009d810 0009da10 60000106 324c0000 e3fe0000
  e0000000 fffd8384 00000000 fffe0000 000000c4 ffff0000 ffffffff 880f0000
 Port selection is MII, half-duplex.
 Transmit stopped, Receive stopped, half-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  The transmit threshold is 72.
EEPROM size is 6.
  * An old-style EEPROM layout was found.
  * The old-style layout does not contain transceiver control information.
  * This board may not work, or may work only with a subset of transceiver
  * options or data rates.
EEPROM contents:
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
 ID block CRC 0xe3 (vs. 00).
  Full contents CRC 0x6523 (read as 0x0000).
 MII PHY found at address 0, status 0x782d.
 MII PHY #0 transceiver registers:
   3100 782d 0300 e54a 01e1 45e1 0001 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0140 0000 0f00 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 Basic mode status register 0x782d ... 782d.
   Link status: established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Vendor ID is 00:c0:39:--:--:--, model 20 rev. 10.
   Vendor/Part: TDK transceiver (unknown type).
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 45e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Negotiation  completed.
  TDK format vendor-specific registers 16..18 are 0x0140 0x0000 0x0f00
      Link polarity is detected as normal.
      Auto-negotiation complete, 100Mbps full duplex.
      Rx link in pass state, PLL slipped since last read.
      No new link status events.

None Fixed?

Re: Question RBEM56G100 TX carrier errors on 100baseT network (Stefan Kluth)
Date: 2000, Sep 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I finally got annoyed enough with this to try to figure out what was
wrong.  There are two problems; one is that the driver was not setting
the NIC for full duplex operation, the other is that even when that is
fixed, the chip still reports bogus carrier errors.  Try the 01-Sep-00
beta on projects.sourceforge.net in /pub/pcmcia-cs/NEW.

-- Dave

None Re: Fixed?

Re: None Fixed? (David Hinds)
Date: 2000, Sep 04
From: Stefan Kluth Stefan

On Fri, 1 Sep 2000, David Hinds wrote:

> If you reply to this message at HyperNews@pcmcia.sourceforge.org, include:
> In-Reply-To: <20000901121315.A5979@valinux.com>
> 
> I finally got annoyed enough with this to try to figure out what was
> wrong.  There are two problems; one is that the driver was not setting
> the NIC for full duplex operation, the other is that even when that is
> fixed, the chip still reports bogus carrier errors.  Try the 01-Sep-00
> beta on projects.sourceforge.net in /pub/pcmcia-cs/NEW.

That worked well, thanks a lot! I now get consistent 100Mbps full
duplex and the TX packet carrier errors are gone. 

As a bonus, the card comes up directly without need for an
additional "ifconfig eth0 down up" or setting promiscous mode. Currently I
think that it sometimes failes to come up, but I need to observe the
situation a little longer. 

Cheers, Stefan

---Stefan Kluth---------------Wissenschaftlicher Mitarbeiter-----------
-  MPI fuer Physik         -  phone:  +49 89 32354 468  -      OPAL&  -
-  Foehringer Ring 6       -  fax:    +49 89 32354 305  -      ATLAS  -
---D-80805 Munich, Germany----e-mail: skluth@mppmu.mpg.de--------------

Question CE3B-100BTX, a Dell Latitude XPiCD, and Mandrake 6

Date: 2000, Sep 01
From: Kagenin

Hello. I recently bought a Xircom 10/100 Ready CreditCard Ethernet PCMCIA adapter. The number on the back is CE3B-100BTX. It doesn't seem to work in my notebook, a Dell Latitude XPiCD with a P166MMX, and 64M of ram, stock mandrake 6 kernel 2.2.9 (haven't been able to get 2.2.16 onto it yet without losing sound support), and the stock PCMCIA-cs package.

The network is a simple cat5 crossover cable to a USB-to-Ethernet adapter installed in my Win95(OSR2.1 w/USB Supp). I can't get either box to even ping each other.

Any Suggestions? Other than Sneakernet(and lots of floppys), my hands are kind of tied.

Thank you for any consideration,

Kagenin

None The way forward seems clear

Re: Question CE3B-100BTX, a Dell Latitude XPiCD, and Mandrake 6
Date: 2000, Sep 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Well, you know that you have an old set of PCMCIA drivers.  That
suggests one line of attack.  The PCMCIA BUGS file also has some
comments about Xircom cards.

-- Dave

Question XIRCOM

Date: 2000, Oct 13
From: David Stephenson achille

looking for someone who can tell me how to make my xircom realport 10/100 ETHER 56 KB modem work. ethernet ok but modem can't be used. i have a thinkpad 600

Question Xircom help with 10/100 using RH 6.2

Date: 2000, Oct 25
From: adacosta trickydic

Im trying to install my 10/100 xircom PCMCIA card, but with sevre difficulty.

Im using a toshiba tecra 740CDT laptop. PCMCIA boots fine when i start my machine.

I was wondering if someone could give me a quick step by step procedure for installing this new card.

If i insert the card when the machine is on (after reading the man pages for cardmgr) it makes two beeps the second one being the low beep thus telling me that the card was not initialized prperly.

I am hoping that all i need is a driver. And if so could you point me to where i could get this driver and how to go about installing it.

Please, if i have not given you enough info email me @ adacosta@sympatico.ca and i assure you a quick response, for i am in dire need to get this working.

thanx

td

Warning VALinux and RBE-100

Date: 2000, Nov 29
From: Jeremy Welling jwelling

Just for those who may run into this- VALinux 7.0.1 uses kernel rev 2.2.18-pre11 and it breaks the xircom rbe-100 and who knows what else. I tried upgrading to pcmcia-cs 3.1.22 and also recompiled the kernel with no luck. For shitz and grins I did a default rh7 install and that worked. I then did an rpm -U --oldpackage to downgrade the kernel to standard rh7 under VA, fixed lilo and it works fine now. This problem may affect all 2.2.18- don't know.

Hope this saves someone some time...

Jeremy Welling

None It is a bigger issue

Re: Warning VALinux and RBE-100 (Jeremy Welling)
Date: 2000, Nov 29
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The RBE-100 driver is fundamentally broken and has always been so.  It
may have worked ok for your configuration before, and not work now;
but it was just as broken before, just not for you.  When you switched
to the RH7 kernel you got an older version of PCMCIA that behaves
differently, but neither is really more or less broken.

The BUGS file in the current PCMCIA distribution explains the issue.

- Dave
Xircom PCMCIA Ethernet Adapter Issues


Add Message to: "Xircom PCMCIA Ethernet Adapter Issues"

Members Subscribe Admin Mode Show Frames Help for HyperNews at pcmcia-cs.sourceforge.net 1.10