Use this forum to discuss general problems installing and configuring the PCMCIA driver package. Do not use this forum for issues that seem specific to a particular card: pick a more specific forum instead. 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; your linux distribution; and, of course, any relevant system log messages.

Messages Inline: 0 1

Question Unresolved symbols

Date: 1999, Nov 01
From: Joseph Turian Turian

I installed the PCMCIA modules from 3.1.3, but when I start my computer they fail to load. When I run /etc/init.d/pcmcia start, I get the following error messages:

Starting PCMCIA services: modules/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol strcat
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol inb
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol ioremap
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol __constant_memcpy
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol __constant_c_memset
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol ffs
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol strcmp
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol strcpy
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol __memcpy
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol strlen
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol signal_pending
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol __constant_c_and_count_memset
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol strncpy
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol strncmp
/lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol __memset_generic

etc.
Any ideas?

None Bad CFLAGS during compilation

Re: Question Unresolved symbols (Joseph Turian)
Date: 1999, Nov 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Sun, Oct 31, 1999 at 11:56:44PM -0800, Joseph Turian wrote:
> 
> I installed the PCMCIA modules from 3.1.3, but when I start my
> computer they fail to load. When I run /etc/init.d/pcmcia start, I get
> the following error messages: 
> 
> Starting PCMCIA services: modules
> /lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol strcat
> /lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol inb
> /lib/modules/2.2.13/pcmcia/pcmcia_core.o: unresolved symbol ioremap

This most likely means that you've set CFLAGS in your environment,
which is overriding the setting in the PCMCIA Makefile... and your
CFLAGS does not specify optimization.  These missing symbols are all
inline functions, that only get inlined properly if compiled with
optimization.

So, the quick workaround is to unset the CFLAGS variable before
building PCMCIA.  I'm fixing the Makefiles for 3.1.4 to not allow
CFLAGS overrides from the environment.  It was meant to be a feature,
but I've never really used it, and it confuses people.

-- Dave

None Problems with Vadem VG-469 isa bridge

Date: 1999, Nov 02
From: Steve Kann stevek

I've been having a heck of a time trying to get a Lucent Wavelan IEEE -compatible (actually a cabletron roamabout DS) working on a linux PC.

I think that it is some kind of hardware conflict or something like that, because I've gotten it working on two other machines (one a laptop, and another desktop machine), using the exact same methodologies, with no problems.

The PC card comes with a PCMCIA->ISA bridge card. What happens is this: After a clean boot, the first time I load the PCMCIA modules, they will properly detect an insertion and load the correct card service module. The module doesn't work, though -- the wavelan2_cs module loads and identifies the card, but it can't communicate properly with it. I've tried blocking out different io port ranges to get the card onto either 0x100, 0x300, or 0x400 (+40), all of which seem to be free on my machine. I've tried different interrupts also, including 3 and 7 (com2 and lpt1, both disabled in my bios), and no difference.

The next symptom, is that after stopping and restarting the pcmcia subsystem, after inserting a card, I always get the message "socket timed out during reset".

I am using kernel 2.2.13, and have tried both the 3.0.14 and 3.1.3 PCMCIA releases, as well as both the lucent wavelan2 4.00 and Andreas Neuhaus' wvlan_cs 1.0.1 package. Both seem to have similar problems.

I have enabled debugging via PCMCIA_DEBUG, and various pc_debug settings. The results of that can be found at http://www.stevek.com/debug

I've tried changing all kinds of different parameters, including most of the timing parameters for pcmcia_core reset stuff, using async_clock for the i82365, etc. Nothing seems to have any affect other than changing how long it takes for the pcmcia driver to give up resetting the socket.

TIA for any advice!

None No good ideas, unfortunately

Re: None Problems with Vadem VG-469 isa bridge (Steve Kann)
Date: 1999, Nov 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Can you maybe try swapping the Wavelan card and/or the ISA-to-PCMCIA
bridge card with one of the other systems you say you've set up
successfully?  That would help to rule out some possible hardware
failures.

Otherwise, nothing jumps out at me.

-- Dave

Ok Older version(s) seems to work.

Re: None Problems with Vadem VG-469 isa bridge (Steve Kann)
Date: 1999, Dec 15
From: Dan dan

My symptoms :

kernel - 2.0.34
pcmcia - 3.1.x
card - lucent ISA to pcmcia, single slot, based on vadem 469 chip
computer - old 486-s 33/66/100 ...

default setup/boot hung-up on cardmgr - I went to 'by-hand' mode...

insmod of 'pcmcia_core' (no opts) worked
insmod of 'i82365' (no opts) hangs, but machine OK, <CR> ok, ^C-s nogo
(try many timing options consider debugging - nogo)

lsmod at this point (from another window...) shows i82365 there, but not initialized.

reboot...(often)


My solution :

peruse web and see many using this card OK, others not OK.
try three different ISA motherboard machines, all same.
try late 2.x.x release of pcmcia_cs from archives - my client drivers need 3.x.x (ug)
try 3.0.13 pcmcia - wa-la - works so far...

Thoughts from web notes (from others):

somewhere between vadem support enabled and the current 3.x releases that some 'feature' was added (for 2.2.x+ kernels?) that busts the initialization of the vadem chip in this case.

Thanks to all for help and advice. I hope this will save some others as much time as you all have saved me!

Thanks for a great tool-kit Dave!

--danno

Question Untitled

Date: 1999, Nov 02
From: Joseph Turian Turian

I get the following error message when I run /etc/init.d/pcmcia start:

Starting PCMCIA services: modules/lib/modules/2.2.13/pcmcia/i82365.o: init_module: Device or resource busy
/lib/modules/2.2.13/pcmcia/ds.o: init_module: Device or resource busy
 cardmgr.

My syslog reads:
Nov  2 01:25:41 wish kernel: Linux PCMCIA Card Services 3.1.3
Nov  2 01:25:41 wish kernel:   kernel build: 2.2.13 #3 Thu Oct 21 20:14:33 EDT 1999
Nov  2 01:25:41 wish kernel:   options:  [pci] [cardbus] [pnp]
Nov  2 01:25:41 wish kernel: PnP: PNP BIOS installation structure at 0xc00f7670
Nov  2 01:25:41 wish kernel: PnP: PNP BIOS version 1.0, entry at f0000:6d14, dseg at f0000
Nov  2 01:25:41 wish kernel: Intel PCIC probe: not found.
Nov  2 01:25:41 wish kernel: ds: no socket drivers loaded!

Any help would be greatly appreciated!

None PCIC probe: not found.

Re: Question Untitled (Joseph Turian)
Date: 1999, Nov 02
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Mon, Nov 01, 1999 at 10:29:40PM -0800, Joseph Turian wrote:

> Nov  2 01:25:41 wish kernel: Intel PCIC probe: not found.
> Nov  2 01:25:41 wish kernel: ds: no socket drivers loaded!

The drivers are not finding your PCMCIA bridge.  What kind of laptop
is this?  How old?

If it is a particularly old laptop (five years or older, probably 486
based), you might have a Databook TCIC bridge, in which case, you
could try loading the "tcic.o" module instead of "i82365.o".  Another
possibility would be that you've got a Cirrus PD6722 bridge, which can
be powered down at boot time: in this case, you would need to use a
startup option of PCIC_OPTS="wakeup=1" as discussed in the
PCMCIA-HOWTO.

A third possibility: some systems have a BIOS setup option to disable
PCMCIA.  And a fourth possibility is that you're using a desktop
system with a PCMCIA adapter on a Plug and Play card, and need to use
the isapnp tools to activate it before loading the PCMCIA drivers.

-- Dave

Question memory probe failure?

Date: 1999, Nov 09
From: Thomas Schaefer schaefer

Hi:

 I'm trying to install a MultiTech PCMCIA card modem in my
Compaq Presario 1650 notebook. I am running Red Hat Linux
version 5.2 (kernel 2.0.36). The card is identified as
'anonymous memory' and the system log shows that various
memory ranges have been excluded. According to the
PCMCIA-HOWTO, the likely cause of this problem is a
memory probe failure. The suggested solution is to change
the included memory ranges in the /etc/pcmcia/config.opts
file. I have tried several different ranges, e.g.
0xd0000-0xdfff, 0xd8000-0xdffff, but to no avail.

 The card works fine, I have been able to use it under
Windows 98 (I also tried to deduce the memory range
those drivers use, but that didn't help either).


  Thomas

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

probe
PCI bridge probe: TI 1131 found, 2 sockets
probe -m
i82365

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

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

/etc/sysconfig/pcmcia
PCMCIA=yes
PCIC=i82365
PCIC_OPTS=
CORE_OPTS=

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

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

Compaq Presario 1650
linux kernel version 2.0.36
Linux PCMCIA Card Services 3.0.5
MultiTech 33.6K Modem (MT3400ZLX)

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

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

/var/log/messages
Nov 8 22:28:12 localhost kernel: Linux PCMCIA Card Services 3.0.5
Nov 8 22:28:12 localhost kernel: kernel build: 2.0.36 unknown
Nov 8 22:28:12 localhost kernel: options: [pci] [cardbus]
Nov 8 22:28:13 localhost kernel: Intel PCIC probe:
Nov 8 22:28:13 localhost kernel: TI 1131 CardBus at mem 0x68000000, 2 sockets
Nov 8 22:28:13 localhost kernel: host opts [0]: [ring] [pci + serial irq] [no pci irq] [lat 168/176] [bus 32/34]
Nov 8 22:28:13 localhost kernel: host opts [1]: [ring] [pci + serial irq] [no pci irq] [lat 168/176] [bus 35/37]
Nov 8 22:28:13 localhost kernel: ISA irqs (scanned) = 3,4,7,10 status change on irq 10
Nov 8 22:28:13 localhost cardmgr[219]: starting, version is 3.0.5
Nov 8 22:28:13 localhost cardmgr[219]: watching 2 sockets
Nov 8 22:28:13 localhost kernel: cs: IO port probe 0x1000-0x17ff: excluding nothing: probe failed.
Nov 8 22:28:13 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7
Nov 8 22:28:13 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Nov 8 22:28:13 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff
Nov 8 22:28:13 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Nov 8 22:28:13 localhost cardmgr[219]: initializing socket 1
Nov 8 22:28:13 localhost cardmgr[219]: socket 1: Anonymous Memory
Nov 8 22:28:13 localhost cardmgr[219]: executing: 'insmod /lib/modules/preferred/pcmcia/memory_cs.o'
Nov 8 22:28:13 localhost kernel: memory_cs: mem0: anonymous: unknown size
Nov 8 22:28:13 localhost cardmgr[219]: executing: './memory start mem0'

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

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

/var/run/stab
Socket 0: empty
Socket 1: Anonymous Memory

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


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

/etc/pcmcia/config.opts
#
# Local PCMCIA Configuration File
#
# System resources available for PCMCIA devices
#
include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff, memory 0xa0000000-0xa0ffffff
#

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

None That's some old stuff...

Re: Question memory probe failure? (Thomas Schaefer)
Date: 1999, Nov 11
From: David Hinds <dhinds@pcmcia.sourceforge.org>

First, you should be aware that you're using a terribly outdated
release of Red Hat (and likewise, a terribly out of date version of
the PCMCIA driver package).  It is likely that your problem does not
exist in current releases.

That said, I would edit /etc/pcmcia/config.opts and delete the
0xa0000000-0xa0ffffff memory range.  List only one memory range: first
try the 0xc0000-0xfffff range, then try the shorter subsets of that
which you tried earlier.  From your system log messages, it is clear
that (at least for the config.opts file you give), the problem is with
the 0xa0000000 range.

If fiddling with the memory ranges doesn't solve the problem, then I
think the only thing to do is to get some more recent software.

-- Dave

Question sorry, more problems

Re: Question memory probe failure? (Thomas Schaefer)
Date: 1999, Nov 16
From: Thomas Schaefer schaefer

 Hi:

 I'm still having problems trying to install a MultiTech 
PCMCIA card modem in my Compaq Presario 1650 notebook. I 
upgraded the system to Red Hat Linux version 6.0 (kernel 
2.2.5, PCMCIA card services 3.1.3). The card is now 
correctly identified (in the mean time, I also bought 
a 3COM ethernet card which works just fine), but I can't 
get it to work. I have been trying to use minicom. 
Minicom attempts to dial, but there is no connection, 
and minicom hangs when I try to exit. 

 I suspect it might be some sort of interrupt conflict. 
Windows 98 has the built in (Win)modem on COM2 (IRQ 3) 
and the PCMCIA modem on COM3 (IRQ 10). With the standard
/etc/pcmcia/config.opts the PCMCIA card modem is assigned
ttyS1 and IRQ 3. I tried to exclude IRQ3 rather than 
IRQ4, but that doesn't seem to help. Neither does changing
the IRQ of /dev/modem to something like 0 or 10 using
the setserial command. (IRQ10 has an interesting effect:
Minicom claims that I am already on line). 


-------------------------------------------------------------
probe
PCI bridge probe: TI 1131 found, 2 sockets
probe -m
i82365
-------------------------------------------------------------

-------------------------------------------------------------
/etc/sysconfig/pcmcia
PCMCIA=yes
PCIC=i82365
PCIC_OPTS=
CORE_OPTS=
-------------------------------------------------------------

-------------------------------------------------------------
Compaq Presario 1650
linux kernel version 2.2.5-15
Linux PCMCIA Card Services 3.1.3
MultiTech 33.6K Modem (MT3400ZLX)
-------------------------------------------------------------

-------------------------------------------------------------
/var/log/messages
Nov 16 10:33:00 localhost pcmcia: Starting PCMCIA services:
Nov 16 10:33:00 localhost pcmcia:  modules
Nov 16 10:33:00 localhost kernel: Linux PCMCIA Card Services 3.1.3 
Nov 16 10:33:00 localhost kernel:   kernel build: 2.2.5-15 #1 Mon Apr 19 23:00:46 EDT 1999 
Nov 16 10:33:00 localhost kernel:   options:  [pci] [cardbus] [apm] 
Nov 16 10:33:00 localhost kernel: Intel PCIC probe:  
Nov 16 10:33:00 localhost kernel:   TI 1131 PCI-to-CardBus at bus 0 slot 10, mem 0x68000000, 2 sockets 
Nov 16 10:33:00 localhost kernel:     host opts [0]: [ring] [pci + serial irq] [no pci irq] [lat 168/176] [bus 32/34] 
Nov 16 10:33:00 localhost kernel:     host opts [1]: [ring] [pci + serial irq] [no pci irq] [lat 168/176] [bus 35/37] 
Nov 16 10:33:00 localhost kernel:     ISA irqs (scanned) = 3,4,7,10 status change on irq 10 
Nov 16 10:33:00 localhost pcmcia:  cardmgr.
Nov 16 10:33:01 localhost rc: Starting pcmcia succeeded
Nov 16 10:33:01 localhost cardmgr[321]: starting, version is 3.1.3
Nov 16 10:33:01 localhost cardmgr[321]: watching 2 sockets
Nov 16 10:33:01 localhost kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Nov 16 10:33:01 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7 
Nov 16 10:33:01 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Nov 16 10:33:01 localhost inet: inetd startup succeeded
Nov 16 10:33:01 localhost cardmgr[321]: initializing socket 1
Nov 16 10:33:01 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. 
Nov 16 10:33:01 localhost cardmgr[321]: socket 1: Serial or Modem
Nov 16 10:33:01 localhost cardmgr[321]: executing: 'insmod /lib/modules/2.2.5-15/pcmcia/serial_cs.o'
Nov 16 10:33:01 localhost kernel: tty01 at 0x02f8 (irq = 4) is a 16550A 
Nov 16 10:33:01 localhost cardmgr[321]: executing: './serial start ttyS1'

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



-------------------------------------------------------------
/etc/pcmcia/config.opts 
#
# Local PCMCIA Configuration File
#
# System resources available for PCMCIA devices
#
include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff, memory 0xa0000000-0xa0ffffff
#
# 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
-------------------------------------------------------------


-------------------------------------------------------------
setserial -a /dev/modem
/dev/modem, Line 1, UART: 16550A, Port: 0x02f8, IRQ: 3
	Baud_base: 115200, close_delay: 50, divisor: 0
	closing_wait: 3000, closing_wait2: infinte
	Flags: spd_normal skip_test

ls -l /dev/modem
lrwxrwxrwx   1 root     root           10 Nov 13 20:41 /dev/modem -> /dev/ttyS1
-------------------------------------------------------------

Note in case 3.1.2 or higher is hanging your system....

Date: 1999, Nov 10
From: Adam Di Carlo aph

On my Dell Inspiron 3000, when I upgraded from 3.1.1 to 3.1.2 (and from the changelog, I assume this would still hold with 3.1.3), I got sudden hangs when loading the card services (i82365.o). It's described in the HOWTO as in IRQ issue.

I was able to work-around this problem by adding PCIC_OPTS="pci_csc=0" in /etc/pcmcia.conf, thereby disabling the PCI IRQ scan, which was hanging my box.

Just FYI. David, I don't know if this is common, but it was a few days of distress for me. Hope this helps some other poor soul...

Question Which is *preferred*, PnP or not?

Date: 1999, Nov 11
From: Steve Snyder SteveSnyder

I currently do not have PnP enabled in my Linux v2.2.1x kernel, but can enable it if needed. So... which state does pcmcia-cs v3.1.x prefer, PnP enabled or disabled?

Thank you.

None Kernel PnP settings shouldn't matter

Re: Question Which is *preferred*, PnP or not? (Steve Snyder)
Date: 1999, Nov 11
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Thu, Nov 11, 1999 at 01:35:24PM -0800, Steve Snyder wrote:
> If you reply to this message at HyperNews@pcmcia.sourceforge.org, include:
> In-Reply-To: <"/pcmcia/install/8"@pcmcia.sourceforge.org>
> 
> I currently do not have PnP enabled in my Linux v2.2.1x kernel, but can
> enable it if needed. So... which state does pcmcia-cs v3.1.x prefer, PnP
> enabled or disabled?

It should almost never matter.  The PnP support in the Linux kernel is
for handling ISA PnP devices... and most laptops don't have any of
these.  The 3.1 PCMCIA packages have optional PnP BIOS support, which
is somewhat different: this is a mechanism for talking to the BIOS to
get resource information about non-PnP devices.  Laptops generally
have lots of non-PnP devices, so this is often a useful capability;
however, PnP BIOS access causes trouble on some systems, so I don't
enable this by default.

-- Dave

Question external scsi pcmcia card reader/writer

Date: 1999, Nov 15
From: Eric Bourque ericb

Hi,

I need to purchase an external scsi (ide is full on my
machine) pcmcia card reader/writer for use with a smart media
card (once it's in its pcmcia card adapter). I know that the
adapted smart media cards are themselves supported in linux,
but I can't find any information anywhere about whether these
external readers for desktops are supported, particularly if
they are scsi devices. Specifically I'm looking at purchasing
a microtech dpa-scsi-pc (http://www.d-store.com). If anybody
has any information about whether this is supported in linux
or not, it would be greatly appreciated.

Thanks,

Eric

None Actually, these just work like SCSI drives

Re: Question external scsi pcmcia card reader/writer (Eric Bourque)
Date: 1999, Nov 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

This kind of SCSI PCMCIA reader doesn't actually require any special
drivers at all: it is designed to make an ATA PCMCIA device look like
a SCSI disk drive.  It doesn't use or interact with the PCMCIA driver
subsystem.  You just treat your cards like a removable SCSI disk
drive.

-- Dave

Question No Power on Sycard PCChost 1200?

Date: 1999, Nov 25
From: Patrick Osterloh p_osterloh

I just migrated from a Sycard PCChost 1100 Bridge with a TI 1131 socket controller to a Sycard PCChost 1200 Bridge with a TI 1220 socket controller on board. The problem is: The new Bridge does not power up its sockets. I can trace the problem down to the on board socket power switch. For some reasons this device is not powering up the sockets. Does anyone share this experience with me?

David: Is the the TI 1220 supported by the current software version?

Regards,

Patrick

Warning Patch for TI1220 on Sycard´s PCChost1200 PCI-Cardbus Adapter

Re: Question No Power on Sycard PCChost 1200? (Patrick Osterloh)
Date: 1999, Nov 28
From: Patrick Osterloh p_osterloh

There´s a problem with the TI PCI1220 socket controller
on the Sycard PCChost1200 PCI-CardBus Host Adapter when 
using the current version 3.1.4 of the PCMCIA package: 
The sockets are not powered up after the insertion of a
PC Card. This is due to the fact that the on board power
switch does not receive a clock signal. In order to solve
this problem, the P2CCLK Bit (#27) in the TI1220´s System
Control Register (offset 80h) must be set. When this bit
is set, the power switch clock is generated by the PCI
clock and driven by the TI PCI1220.

The following changes are required in the PCMCIA software:

Add a bit definition for the P2CCLK bit in the file
"pcmcia-cs-3.14/modules/ti113x.h":

...
/* System Control Register */
#define TI113X_SYSTEM_CONTROL		0x0080	/* 32 bit */
#define  TI113X_SCR_SMIROUTE		0x04000000
#define  TI113X_SCR_SMISTATUS		0x02000000
#define  TI113X_SCR_SMIENB		0x01000000
#define  TI113X_SCR_VCCPROT		0x00200000
#define  TI113X_SCR_REDUCEZV		0x00100000
#define  TI113X_SCR_CDREQEN		0x00080000
#define  TI113X_SCR_CDMACHAN		0x00070000
#define  TI113X_SCR_SOCACTIVE		0x00002000
#define  TI113X_SCR_PWRSTREAM		0x00000800
#define  TI113X_SCR_DELAYUP		0x00000400
#define  TI113X_SCR_DELAYDOWN		0x00000200
#define  TI113X_SCR_INTERROGATE		0x00000100
#define  TI113X_SCR_CLKRUN_SEL		0x00000080
#define  TI113X_SCR_PWRSAVINGS		0x00000040
#define  TI113X_SCR_SUBSYSRW		0x00000020
#define  TI113X_SCR_CB_DPAR		0x00000010
#define  TI113X_SCR_CDMA_EN		0x00000008
#define  TI113X_SCR_ASYNC_IRQ		0x00000004
#define  TI113X_SCR_KEEPCLK		0x00000002
#define  TI113X_SCR_CLKRUN_ENA		0x00000001  

#define  TI122X_SCR_SER_STEP		0xc0000000
#define  TI122X_SCR_INTRTIE		0x20000000
/*-- Changes for TI1220 by Patrick Osterloh on 11/28/99 -- */
#define  TI122X_SCR_P2CCLK              0x08000000
/*-------------------------------------------------------- */
#define  TI122X_SCR_CBRSVD		0x00400000
#define  TI122X_SCR_MRBURSTDN		0x00008000
#define  TI122X_SCR_MRBURSTUP		0x00004000
#define  TI122X_SCR_RIMUX		0x00000001
...  


Then adjust the "ti113x_set_opts" function within the module
"pcmcia-cs-3.14/modules/i82365.c" as follows:

...
static u_int __init ti113x_set_opts(u_short s, char *buf)
{
    socket_info_t *t = &socket[s];
    ti113x_state_t *p = &t->state.ti113x;
    u_int mask = 0xffff;
    int old = (t->type <= IS_TI1131);

/*-- Changes for TI1220 by Patrick Osterloh on 11/28/99 --*/ 
    int p2c_patch = (t->type == IS_TI1220);
/*--------------------------------------------------------*/
    
    flip(p->sysctl, TI113X_SCR_CLKRUN_ENA, has_clkrun);
    flip(p->sysctl, TI113X_SCR_CLKRUN_SEL, clkrun_sel);
    flip(p->cardctl, TI113X_CCR_RIENB, has_ring);
    p->cardctl &= ~TI113X_CCR_ZVENABLE;
    switch (irq_mode) {
    case 1:
	p->devctl &= ~TI113X_DCR_IMODE_MASK;
	p->devctl |= TI113X_DCR_IMODE_ISA;
	break;
    case 2:
	p->devctl &= ~TI113X_DCR_IMODE_MASK;
	p->devctl |= TI113X_DCR_IMODE_SERIAL;
	break;
    case 3:
	p->devctl &= ~TI113X_DCR_IMODE_MASK;
	p->devctl |= TI12XX_DCR_IMODE_ALL_SERIAL;
	break;
    default:
	if ((p->devctl & TI113X_DCR_IMODE_MASK) == 0)
	    p->devctl |= TI113X_DCR_IMODE_ISA;
    }
    if (p->cardctl & TI113X_CCR_RIENB) {
	strcat(buf, " [ring]");
	if (old) mask &= ~0x8000;
    }
    if (old && (p->sysctl & TI113X_SCR_CLKRUN_ENA)) {
	if (p->sysctl & TI113X_SCR_CLKRUN_SEL) {
	    strcat(buf, " [clkrun irq 12]");
	    mask &= ~0x1000;
	} else {
	    strcat(buf, " [clkrun irq 10]");
	    mask &= ~0x0400;
	}
    }
    if (p->sysctl & TI113X_SCR_PWRSAVINGS)
	strcat(buf, " [pwr save]");

/*-- Changes for TI1220 by Patrick Osterloh on 11/28/99--*/ 
    if (p2c_patch)
        p->sysctl |= TI122X_SCR_P2CCLK;
/*-------------------------------------------------------*/

    switch (p->devctl & TI113X_DCR_IMODE_MASK) {
    case TI12XX_DCR_IMODE_PCI_ONLY:
	strcat(buf, " [pci only]");
	mask = 0;
	break;
    case TI113X_DCR_IMODE_ISA:
	strcat(buf, " [isa irq]");
	if (old) mask &= ~0x0018;
	break;
    case TI113X_DCR_IMODE_SERIAL:
	strcat(buf, " [pci + serial irq]");
	mask = 0xffff;
	break;
    case TI12XX_DCR_IMODE_ALL_SERIAL:
	strcat(buf, " [serial pci & irq]");
	mask = 0xffff;
	break;
    }
    return mask;
}
...

That´s all! Don´t forget to recompile and reinstall!

Patrick

--
Patrick Osterloh
Chair of Electrical Engineering and Computer Systems (EECS)
University of Technology RWTH Aachen
phone: +49-241-807588
fax:   +49-241-8888-282
email: osterloh@eecs.rwth-aachen.de

Question Kernel source tree from RPMs

Date: 1999, Nov 26
From: Peter Townsend Pete

I'm new to this area and have run into a snag -- the folks at redhat keep telling to post to new groups for help!?

Problem: I'm trying to compile the pcmcia package. 'make config' asks for linux src. I only have headers installed (rehat 6.1). I copy kernel source rpm from CD2 and install (rpm -ivh ...). Nothing appears to install in /usr/src/linux. /usr/source/redhat/SOURCES appears to have the kernal source. I can't figure-out how to create the source tree. THere are many files including "patches" which I'm unfamiliar with. I know I can get the source in tar format from other locations; but this particular machine isn't on the internet yet.

Any hints on creating the kernel source tree from the redhat distributed rpms?

Thanks

None RPM's versus SRPM's

Re: Question Kernel source tree from RPMs (Peter Townsend)
Date: 1999, Nov 29
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You want to install the kernel-source RPM, not Red Hat's SRPM for the
kernel.  That's somewhat nonintuitive... the kernel-source RPM puts
the plain kernel source tree in /usr/src/linux, but an SRPM is a
special thing just for creating RPM's, and it puts the kernel source
tree (plus various other things) in unusual places.

-- Dave

Question additional info

Re: None RPM's versus SRPM's (David Hinds)
Date: 1999, Nov 29
From: Peter Townsend Pete

Thanks, I figured that one out last night. I installed the kernel-source....rpm file and did a 'make dep'. I walked out and noticed a few errors (don't have them now). Despite the errors, I tried to build the rangeland drivers for a wireless symphony card (PCMCIA).

This driver needs the PCMCIA header files. I believe the make dep produced most but the 'config.h' is still elusive. I see a config.h link to '../pcmcia' in the '/usr/src/linux/pcmcia-cs-3.0.14/include/linux' directory. Howeverthere isn't a config.h file in ''/usr/src/linux/pcmcia-cs-3.0.14/include/pcmcia' directory. I'm lost! Any suggestions how to proceed would be appreciated!

Question success but PCMCIA hangs

Re: Question additional info (Peter Townsend)
Date: 1999, Nov 29
From: Peter Townsend Pete

I had some success. Following the README in /usr/src/linux , I did

make mrproper make config (defaulted thru most questions) make dep

this created the config.h that I was lookign for. However, I had to add a #endif in config.h to get the Symphony driver to compile:

#ifndef _PCMCIA_CONFIG.H
#define _PCMCIA_CONFIG_H
#endif
#define AUTOCONF_INCLUDED
#define LINUX "/usr/src/linux/kernel"

This compiled with no errors. I edited etc/sysconfig/pcmcia PCMCIA=yes PCIC=i82365 PCIC_OPTS=poll_interval=100 CORE_OPTS=

When I reboot the startup of PCMCIA services hangs! ANy suggestions?

None That's strange...

Re: Question success but PCMCIA hangs (Peter Townsend)
Date: 1999, Nov 29
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> #ifndef _PCMCIA_CONFIG.H
> #define _PCMCIA_CONFIG_H
> #endif
> #define AUTOCONF_INCLUDED
> #define LINUX "/usr/src/linux/kernel"

I don't know where you got this or exactly what it's supposed to do,
but it looks completely bogus to me.

-- Dave

None make config

Re: Question additional info (Peter Townsend)
Date: 1999, Nov 29
From: David Hinds <dhinds@pcmcia.sourceforge.org>

In the PCMCIA source directory, do "make config", as discussed in the
PCMCIA-HOWTO.  The resulting config file is NOT supposed to be the
same as the kernel config.h file.

-- Dave

Warning cardmgr.c Patch - Linux 2.2.14pre9 patch to /usr/src/linux/include/scsi/scsi.h adds spinlocks

Date: 1999, Nov 27
From: Todd A. Wood tawman

Question Machine Reboots on high volume network traffic

Date: 1999, Nov 29
From: Jason M. Sullivan Jason0x21

Basic Information

  • Texas Instruments TravelMate 5200
  • RedHat 6.0
  • Kernel Version 2.2.5-22 (i586)
  • PCMCIA Version 3.0.9
  • D-Link DE-660

So I got the PCMCIA package and cardmgr running (I needed to turn off IO probing. It took a while to figure it out because the message that the pcmcia core was loading correctly didn't make it into the messages log before the cardmgr caused the machine to hang with the io probe). Now that I have the core and cardmgr running, I have a new problem.

I can pop my Network card in, the core recongnizes it, I get two high beeps, and the network starts up fine. I can rlogin, mount, and open an ftp session. I can probably start a bunch of other things, but when the traffic starts getting heavy (like when I start to transfer a file: 'cat' in rlogin, 'get' in ftp, or simply 'cp' from a mounted directory), the machine immediately reboots. No warning, no messages.

I tried a few options (fast_pci, and cmd_time), to no avail. The kernel did have some strange messages on insertion and removal, summarized below..

Nov 22 22:03:00 billbee kernel: eth0: NE2000 Compatible: port 0x1000, irq 10, hw_addr 00:80:C8:8C:0A:E5
Nov 22 22:03:00 billbee cardmgr[370]: executing: './network start eth0'
Nov 22 22:03:01 billbee inet: inetd startup succeeded
Nov 22 22:03:01 billbee kernel: Hw. address read/write mismap 3
Nov 22 22:03:01 billbee kernel: Hw. address read/write mismap 5
Nov 22 22:03:01 billbee nfs: Starting NFS services:  succeeded
Nov 22 22:03:01 billbee cardmgr[370]: + SIOCADDRT: Invalid argument
...
Nov 22 22:03:57 billbee kernel: eth0: unexpected TX-done interrupt, lasttx=0.
Nov 22 22:03:57 billbee last message repeated 3 times
Nov 22 22:03:57 billbee kernel: eth0: Too much work at interrupt, status 0x20
Nov 22 22:03:58 billbee kernel: eth0: interrupt from stopped card
Nov 22 22:03:58 billbee cardmgr[370]: shutting down socket 1
Nov 22 22:03:58 billbee cardmgr[370]: executing: './network stop eth0'
Nov 22 22:03:58 billbee kernel: alloc_skb called nonatomically from interrupt c016aebd
Nov 22 22:03:58 billbee kernel: alloc_skb called nonatomically from interrupt c01509b9
Nov 22 22:03:58 billbee cardmgr[370]: executing: 'rmmod pcnet_cs'
Nov 22 22:03:58 billbee cardmgr[370]: executing: 'rmmod 8390'
Any clues out there? Thanks in advance.

None Disabling IO probing is a bad idea

Re: Question Machine Reboots on high volume network traffic (Jason M. Sullivan)
Date: 1999, Nov 29
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> So I got the PCMCIA package and cardmgr running (I needed to turn off IO
> probing.

Disabling IO port probing is a very bad idea unless you're very sure
about what you're doing.  My guess is that you've now got an IO port
conflict, which is causing reads and writes to the card to sometimes
have unexpected results.

Rather than disabling the IO probe, it would be much better to play
with the IO port windows in /etc/pcmcia/config.opts to find a setting
that doesn't cause a freeze.

-- Dave

More Working now, but one last question

Re: None Disabling IO probing is a bad idea (David Hinds)
Date: 1999, Nov 30
From: Jason M. Sullivan Jason0x21

Ok, I got the card working with a minimal amount of frittering around, but one question remains. The port scan picked up a port that seemed to work (or worked much better than the previous ones), but my memory map lists that as in use by MIDI. I suppose I need to check and see if I can play a MIDI tune while accssing the nextwork, but the question is this:

How does the port actually get asigned? Does it just look for a "free" port?, and tell the card where to respond?

If that's the case, I'm guessing I should probably exclude the MIDI port?

Thanks!

None Clean resource allocation is hard

Re: More Working now, but one last question (Jason M. Sullivan)
Date: 1999, Nov 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The drivers try to avoid clashes with known devices, but the Linux
kernel currently does not make this particularly easy.  If you have a
fairly recent PCMCIA package and compile it with PnP BIOS support
enabled, it will generally do a better job of this, because the BIOS
may know more about the resources used by your devices than the Linux
kernel.  However, PnP BIOS calls cause problems on some systems, so I
don't enable this by default.

You should exclude the MIDI ports if the PCMCIA drivers are trying to
reuse them.  

-- Dave

More Time for me to talk to TI/Acer

Re: None Clean resource allocation is hard (David Hinds)
Date: 1999, Nov 30
From: Jason M. Sullivan Jason0x21

Thanks for the info. I did more checking on the websites that TI/Acer have for the TravelMate series, and in their doumentation for setting up a PCMCIA ethernet card, they say to use the very port that the linux pcmcia package is picking, so it looks like there's a conflict in their documentation as well. :-)

Looks like I'm gonna be bugging Acer now. Thanks again!

Question PCMCIA Configuration on ThinkPad 760XD with docking station

Date: 1999, Dec 07
From: Adam Czezowski adas

Hi:

 I just went through lottery type game with the range of the
 addresses aceptable in /etc/pcmcia/config.opts in order 
 to make my pcmcia card to be recognised.

 I have ThinkPad 760XD and a SelectaDock I which offers SCSI.
 Both laptop has two PCMCIA slots and the docking station 
 has two slots.

 I run Linux 6.0 with the kernel version 2.2.5-15 and the
 card manager 3.09 .

 With the default config.opts, and computer undocked I had
 no problems.

 /etc/pcmcia/config.opts 
 #
 # Local PCMCIA Configuration File
 #
 # System resources available for PCMCIA devices
 #
 include port 0x100-0x4ff, port 0x1000-0x17ff
 include memory 0xc0000-0xfffff, memory 0xa0000000-0xa0ffffff
 #

 With the docked laptop during boot process after pcmcia 
 was initilised computer hanged. I have figured out that the 
 problem is with the memory ranges. 

 After many guess work,the workable memory range in the 
 config.opts is (include memory 0xc000-0xcffff) but when I 
 load pcmcia by /etc/rc.d/init.d/pcmcia start I get 
 cs: warning: no high memory space available.

 Is there any way to get rid of the guess work and being
 able to use some tool which will show the memory ranges   available or what is used by which device? I still don't
 know with which device in the docking station the conflict
 was!

 Why I am warned of lack of high memory if everything is    working now? If it is needed then why?

 My frustration with setting up the cards went for few days.
 I was using different address range in high memory since
 I thought it is neccesary to use them. The solution was 
 much simpler though.

 Is there any procedure to deal with such cases.

 Cheers

 Adam Czezowski
  
 
 

None It is not a simple problem

Re: Question PCMCIA Configuration on ThinkPad 760XD with docking station (Adam Czezowski)
Date: 1999, Dec 07
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Is there a way to solve this problem without guesswork?  I wish.  I
don't know of a foolproof way.  Newer versions of the PCMCIA package
try to be more careful about choosing memory windows, but I would not
really expect that to help in this case.  Choosing the memory window
addresses is hard: it depends on how transactions are forwarded
between the PCI devices in your laptop and the dock, and I don't know
of any easy way to deduce this information.

There is a section in the PCMCIA-HOWTO that discusses the "no high
memory space" warning.  Depending on what cards you want to use, it
may be important; CardBus cards in particular sometimes need large
memory windows.

-- Dave

Question Error compile 3.1.6 !

Date: 1999, Dec 12
From: J.P jeepee

Trying to compile 3.1.6 gives me :

lex_config.l: In function `do_source':

lex_config.l:190: `GLOB_NOMAGIC' undeclared (first use this function)

lex_config.l:190: (Each undeclared identifier is reported only once

lex_config.l:190: for each function it appears in.)

make[1]: *** [lex_config.o] Error 1

make[1]: Leaving directory `/downloads/pcmcia-cs-3.1.6/cardmgr'

make: *** [all] Error 2

Who can tell me how to fix this...

Thanks J.P...

jeepee@gids.nl

None Sorry, my fault...

Re: Question Error compile 3.1.6 ! (J.P)
Date: 1999, Dec 13
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It will be fixed in 3.1.7... the 3.1.6 update unfortunately used a
feature that is in glibc but not the old libc5.

-- Dave

Question Any advantage (possible) to disable 2nd PCMCIA host?

Date: 1999, Dec 17
From: Steve Snyder SteveSnyder

Compaq, in their finite wisdom, put only a single CardBus slot in my Presario 1260. So while the PCMCIA controller supports 2 slots only one can actually be used.

So, my questions is this: is it desireable, or even possible, to disable the second host on the PCMCIA controller?

The current (pcmcia-cs-3.1.7) is working fine with my 3Com 3C575 NIC. I'm thinking in terms of system resources saved, rather than fixing any specific problem.

My configuration:

 Intel PCIC probe:
   TI 1131 PCI-to-CardBus at bus 0 slot 10, mem 0x68000000, 2 sockets
     host opts [0]: [ring] [pci + serial irq] [no pci irq] [lat 168/176] [bus 32/34]
     host opts [1]: [ring] [pci + serial irq] [no pci irq] [lat 168/176] [bus 35/37]
     ISA irqs (scanned) = 3,4,7,9,12 polling interval = 1000 ms
 3c59x.c:v0.99L 5/28/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
 cs: IO port probe 0x1000-0x17ff: clean.
 cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x388-0x38f 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
 cs: IO port probe 0x0a00-0x0aff: clean.
 cs: cb_alloc(bus 32): vendor 0x10b7, device 0x5157
 cs: cb_config(bus 32)
   fn 0 bar 1: io 0x280-0x2ff
   fn 0 bar 2: mem 0xa0021000-0xa002107f
   fn 0 bar 3: mem 0xa0020000-0xa002007f
   fn 0 rom: mem 0xa0000000-0xa001ffff
 eth0: 3Com 3CCFE575 Cyclone CardBus at 0x280,  00:10:4b:f6:49:8f, IRQ 3
 eth0: CardBus functions mapped a0020000->c683e000

Thank you.

None Not really, as far as I know

Re: Question Any advantage (possible) to disable 2nd PCMCIA host? (Steve Snyder)
Date: 1999, Dec 17
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The second socket does not really consume any significant resources.
It uses a 4K memory window for mapping the sockets, and a couple
kernel data structures... probably not more than 1K or so.  You can't
really power off that half of the bridge... but it draws negligible
power, with no card present.

-- Dave

Sad Problems with 3.1.7 kernel 2.2.13 Redhat 6.0

Date: 1999, Dec 19
From: dave_sneddon

I am having problems with an ISA to PCMCIA card, in that my
Netwave card is always recognised as a memory card. I've
followed the various instructions in the HOWTO and man pages
but no success.
Here is the output from the syslog for the initial load:

Intel PCIC probe:
  Ricoh RF5C296/396 ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 1 socket
    host opts [0]: none
    ISA irqs (default) = 3 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: excluding 0x1330-0x1337 0x1388-0x138f 0x1730-0x
1737 0x1788-0x178f
cs: IO port probe 0x0100-0x04ff: excluding 0x388-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: unable to map card memory!
cs: unable to map card memory!
memory_cs: RequestWindow: Resource in use

And here is the output from dump_i365:

RicIntel PCIC probe: i82365sl B step found, 1 sockets
Socket 0:
  Identification and revision = 0x83
  Interface status = 0xff
    [bvd1/stschg] [bvd2/spkr] [detect] [wrprot] [ready] [poweron] [gpi]
  Power control = 0xd5
    [output] [Vcc=5v] [Vpp=5v]
  Interrupt and general control = 0x40
    [irq=0]
  Card status change = 00
   
  Card status change interrupt control = 0x08
    [detect] [irq = 0]
  Card detect and general control = 00
   
  Global control = 00
   
  Memory window 0: [OFF]
    start = 0000, stop = 0000, offset = 0000
  Memory window 1: [OFF]
    start = 0000, stop = 0000, offset = 0000
  Memory window 2: [OFF]
    start = 0000, stop = 0000, offset = 0000
  Memory window 3: [OFF]
    start = 0000, stop = 0000, offset = 0000
  Memory window 4: [OFF]
    start = 0000, stop = 0000, offset = 0000
  I/O window 0: [OFF]
    start = 0000, stop = 0x0001
  I/O window 1: [OFF]
    start = 0000, stop = 0x0001

Please help me.

None Looks like a goofed up /etc/pcmcia/config.opts file

Re: Sad Problems with 3.1.7 kernel 2.2.13 Redhat 6.0
Date: 1999, Dec 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> cs: unable to map card memory!

This implies that you have commented out or otherwise messed up all of
the memory window definitions in the default /etc/pcmcia/config.opts
file.  How, exactly, have you modified this file?

-- Dave

Sad What should it be?

Re: None Looks like a goofed up /etc/pcmcia/config.opts file (David Hinds)
Date: 1999, Dec 20
From: dave_sneddon

As I said, I've followed your advice in the HOWTO and tried
various addresses, to no avail. I've tried having the
netwave_cs line at the bottom uncommented, and this makes no
difference either.

This is my current file.

#
# Local PCMCIA Configuration File
#
# System resources available for PCMCIA devices
#
include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff, 0xa0000000-0xa0ffffff
#
# 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
#
# 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"

Question PCMCIA modules fail to load during bootup

Date: 1999, Dec 21
From: anup ochani anupochani

hi
 i a using a siemens nixdorf, pii with redhat 6.0. when i bootup my machine the system hangs with the following message

starting pcmcia.

using linux single at lilo prompt i disable the pcmcia services, then it boots up normally.

now i have a pcmcia modem. and i cannot configure internet on my laptop without making the pcmcia thing work.

can anyone help me out with this? anup

None Maybe an interrupt probe problem

Re: Question PCMCIA modules fail to load during bootup (anup ochani)
Date: 1999, Dec 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The PCMCIA-HOWTO has advice for debugging startup problems with the
PCMCIA drivers.  You can narrow down the problem by booting with no
cards inserted... if you still get a lock-up, the most likely problem
is an interrupt probe failure.  The HOWTO says how to deal with this.

-- Dave

Question SIGHUP to cardmgr fixes break, why?

Date: 1999, Dec 23
From: Dan dan

Howzit,

running kernel 2.0.34, cs 3.0.14 (my vadem 469 won't work with newer cs versions)

scenario :

  boot = OK
  load pcmcia_core, i82365, ds = OK
  start cardmgr (wavelan card inserted) socket 0 is seen and treated as anonymous memory. fails with "unable to map card memory..."

then :

  cardctl eject = OK
  kill -HUP `cat /var/run/cardmgr.pid` = OK (rescans)
  cardctl insert = OK

repeat :
  cardctl eject = OK
  cardctl insert = OK...

Everything works after SIGHUP to cardmgr.

Question : How can I get my 'system' to boot in the 'SIGHUP' state to start with? Which module load options would show this kind of effect?

I know we're close here...

thanks in advance,

--danno@mindsong.com

Ok Fixed that problem... (jeez)

Re: Question SIGHUP to cardmgr fixes break, why? (Dan)
Date: 2000, Jan 16
From: Dan dan

howzit all,

In an effort to 'shrink' my system, I 'cleaned' out the last line :

  source ./config.opts

from my '/etc/pcmcia/config' file... sigh. I now have cause, effect, and a cure.

Interesting to note that the cardmgr program acts like it loads (?) this particular file on sig-hup, but not on startup?

I'm feeling dumb for having wasted y'alls time... back to real problems!

Hope this helps other anal-retentives who like to (over)- clean out cruft! ...

thanks for all (dave),

--danno

Question Oops on mistaken identity

Date: 1999, Dec 24
From: John Langford jcl

I just upgraded my brother's laptop to redhat-6.1 (pcmcia-3.0.14) from redhat-5.1 and am having problems with pcmcia. When the ethernet card or modem card are inserted a kernel oops occurs. I read through the messages and it appears that the wrong device is being detected leading to the wrong module being inserted and the kernel oops.

Unfortunately, I can't tell you much about the ethernet amd modem cards. They are some variety of generic "made in taiwan". They worked under redhat-5.1 (pcmcia?? I forget). The pathetic users guide claims that the ethernet card is ne2000 compatible. The 'faxmodem' has FCC ID "MGAFM336C-KF" and the ethernet card has part number BEN0012-TF 9830 and serial number 00A00jC123A67.

Is upgrading to the latest pcmcia likely to help? Is there a "right" way to disable automatic card detection and force driver loading?

Here are the relevant parts of the message log:

Dec 23 20:43:00 localhost pcmcia: Starting PCMCIA services:
Dec 23 20:43:00 localhost pcmcia:  modules
Dec 23 20:43:00 localhost kernel: Linux PCMCIA Card Services 3.0.14 
Dec 23 20:43:00 localhost kernel:   kernel build: 2.2.12-20 #1 Mon Sep 27 10:25:54 EDT 1999 
Dec 23 20:43:00 localhost kernel:   options:  [pci] [cardbus] [apm] 
Dec 23 20:43:00 localhost kernel: Intel PCIC probe:  
Dec 23 20:43:00 localhost kernel:   Cirrus PD6729 PCI-to-PCMCIA at bus 0 slot 4, port 0x3e0, 2 sockets

Dec 23 20:43:00 localhost kernel:     host opts [0]: [ring] [1/3/2] [1/9/2] 
Dec 23 20:43:00 localhost kernel:     host opts [1]: [ring] [1/3/2] [1/9/2] 
Dec 23 20:43:00 localhost kernel:     ISA irqs (default) = 3,4,5,7,9,10,11,12 polling interval = 1000 
ms
Dec 23 20:43:00 localhost pcmcia:  cardmgr.
Dec 23 20:43:00 localhost cardmgr[337]: starting, version is 3.0.14
Dec 23 20:43:01 localhost cardmgr[337]: watching 2 sockets
Dec 23 20:43:01 localhost kernel: cs: IO port probe 0x0100-0x03ff: excluding 0x220-0x22f 0x330-0x337 0
x378-0x37f 0x388-0x38f Dec 23 20:43:01 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean.

Dec 24 00:44:55 localhost cardmgr[337]: initializing socket 0
Dec 24 00:44:55 localhost cardmgr[337]: socket 0: SVEC 10/100 Fast Ethernet
Dec 24 00:44:55 localhost kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
Dec 24 00:44:55 localhost cardmgr[337]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/cb_enabler.o'
Dec 24 00:44:55 localhost cardmgr[337]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/tulip_cb.o'

Dec 24 00:44:55 localhost kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000004

Dec 24 00:44:55 localhost kernel: current->tss.cr3 = 01753000, %cr3 = 01753000 
Dec 24 00:44:55 localhost kernel: *pde = 00000000 
Dec 24 00:44:55 localhost kernel: Oops: 0000 
Dec 24 00:44:55 localhost kernel: CPU:    0 
Dec 24 00:44:55 localhost kernel: EIP:    0010:[fat:fat_esc2uni_Rdf8b5a1e+33252/75913592] 
Dec 24 00:44:55 localhost kernel: EFLAGS: 00010246 
Dec 24 00:44:55 localhost kernel: eax: 00000000   ebx: c21c5140   ecx: c27deda0   edx: 00000000 
Dec 24 00:44:55 localhost kernel: esi: 00000000   edi: c2620000   ebp: c171fad8   esp: c171fad0 
Dec 24 00:44:55 localhost kernel: ds: 0018   es: 0018   ss: 0018 
Dec 24 00:44:55 localhost kernel: Process cardmgr (pid: 337, process nr: 17, stackpage=c171f000) 
Dec 24 00:44:55 localhost kernel: Stack: c27deda0 c2620000 c171faec c301d8a7 c27deda0 00000000 0000000
0 c171fb6c Dec 24 00:44:55 localhost kernel: c30302e9 0000002d c27deda0 00000000 c27deec0 00000000 c30306e 0 4d000000 Dec 24 00:44:55 localhost kernel: c30306e0 c171fb00 00000000 00000032 00000032 00000032 49434d4 3 41432041 Dec 24 00:44:55 localhost kernel: Call Trace: [fat:fat_esc2uni_Rdf8b5a1e+35719/75911125] [fat:fat_esc2 uni_Rdf8b5a1e+112073/75834771] [fat:fat_esc2uni_Rdf8b5a1e+113088/75833756] [fat:fat_esc2uni_Rdf8b5a1e+ 113088/75833756] [fat:fat_esc2uni_Rdf8b5a1e+112589/75834255] [fat:fat_esc2uni_Rdf8b5a1e+112428/7583441 6] [fat:fat_esc2uni_Rdf8b5a1e+31167/75915677] Dec 24 00:44:55 localhost kernel: [fat:fat_esc2uni_Rdf8b5a1e+70681/75876163] [fat:fat_esc2uni_R df8b5a1e+36302/75910542] [fat:fat_esc2uni_Rdf8b5a1e+35591/75911253] [fat:fat_esc2uni_Rdf8b5a1e+111666/ 75835178] [fat:fat_esc2uni_Rdf8b5a1e+113092/75833752] [fat:fat_esc2uni_Rdf8b5a1e+112428/75834416] [fat :fat_esc2uni_Rdf8b5a1e+40344/75906500] [fat:fat_esc2uni_Rdf8b5a1e+111418/75835426] Dec 24 00:44:55 localhost kernel: [fat:fat_esc2uni_Rdf8b5a1e+100560/75846284] [fat:fat_esc2uni_ Rdf8b5a1e+103049/75843795] [alloc_skb+113/220] [sock_wmalloc+35/72] [wake_up_process+58/68] [__wake_up +59/72] [sock_def_readable+39/44] [unix_dgram_sendmsg+622/716] Dec 24 00:44:55 localhost kernel: [unix_dgram_sendmsg+0/716] [sock_sendmsg+136/172] [write_intr +247/292] [write_intr+0/292] [write_intr+247/292] [write_intr+0/292] [merge_segments+27/364] [unmap_fi xup+102/280]
Dec 24 00:44:55 localhost kernel:        [do_munmap+541/568] [sys_ioctl+421/448] [system_call+52/56]  
Dec 24 00:44:55 localhost kernel: Code: 8b 56 04 f6 c2 05 75 0d 66 83 7e 0a 00 74 0d f6 46 0c 05 74  

-John

None It's a bug in /etc/pcmcia/config

Re: Question Oops on mistaken identity (John Langford)
Date: 1999, Dec 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The mistaken-identity problem is fixed in more recent releases of the
PCMCIA package.  You can also fix the problem by just editing
/etc/pcmcia/config and removing the entry for the SVEC card.

-- Dave

Question Failure to identify cards on a Toshiba 425CDS

Date: 1999, Dec 27
From: Alexander Garden alecg

I am debugging a Toshiba 425CDS Satellite Pro for a friend. The problem I have is that the PCMCIA cards are not identified. Not in Win '98, not in Linux 2.0.35.

I realize I am using old software, but my question is simple: Is the problem probably a hardware problem (such as a surge came down the phone line over the PCMCIA modem and damaged the motherboard), or a software problem? The cards ( an IBM Token Ring, Xircom Credit Card ethernet/28.8 Modem combo, and a US Robotics Megahertz 28.8 modem) work fine on another laptop.

An insertion of a card is followed by a low beep, than a high beep. The system logs show that multiple memory regions were excluded and, along with /var/run/stab shows that the card was misidentified as an Anonymous Memory card.

I tried everything in the HOWTO under memory probe failures, but nothing succeded. Though under a few configurations card insertion would be followed by a very low beep succeeded by a low beep.

If anyone knows if this is a hardware problem or a software problem I would be much obliged. Thanks!

Alexander Garden

None With old code, debugging options are very limited

Re: Question Failure to identify cards on a Toshiba 425CDS (Alexander Garden)
Date: 1999, Dec 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I would not want to guess what's going on with such old software.
Toshiba laptops have known problems with Linux PCMCIA, but the fact
that Windows also bombs does point towards a hardware problem.  Newer
drivers might behave differently; also see the notes about Toshiba
laptops in the PCMCIA "BUGS" file.  There may be a BIOS setting you
can fiddle with.

-- Dave

Question Problem compiling 3.1.8

Date: 1999, Dec 31
From: Jim Liedeka <jliedeka@facstaff.wisc.edu>

I had a compile failure with cardinfo.

I am using a stock Red Hat 6.1 distro with Xforms added on an IBM Thinkpad i1412. I received the following error:

cc  -MD -O -Wall -Wstrict-prototypes -pipe -I../include -I/usr/src/linux/include -I../modules -I/usr/X11R6/include -I/usr/X11/include -I/usr/X11R6/include/X11 -c cardinfo.c
cc   -o cardinfo cardinfo.o \
    -L/usr/X11R6/lib -L/usr/X11/lib -lforms -lX11 -lm
/usr/bin/ld: cannot open -lforms: No such file or directory
collect2: ld returned 1 exit status
make[1]: *** [cardinfo] Error 1
make[1]: Leaving directory `/root/pcmcia-cs-3.1.8/cardmgr'
make: *** [all] Error 2

Can someone tell me what lforms is and where to find it? Or, is this really some other problem?

Feedback Try this

Re: Question Problem compiling 3.1.8 (Jim Liedeka)
Date: 2000, Jan 05
From: Stephen Davies <scldad@sdc.com.au>

I don't have my laptop here just now but I fixed the same problem 
by creating a link between libforms.so.?? and either libforms.so or libforms.so.1.

HTH,
Stephen

Question Help with an Ricoh ISA-to-PCMCIA bridge card

Date: 1999, Dec 31
From: Jin Yang jyang

Hi, Happy New Year!

It drives me nuts trying to get a WebGear Aviator2.4 Wireless card to work with my Pentium 60MHz Linux desktop through an ISA-to-PCMCIA adapter Webgear provides.

The machine recognizes the adapter during booting but fails to recognizes any PCMCIA card plugged in. It always identifies the card as "anonymous memory". Here is detailed information:

  o The linux kernel is 2.0.35.

  o The adapter card is recognized as:

     Ricoh RF5C296/396 ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 1 socket
       host opts [0]: none
       ISA irqs (scanned) = 3,7,11,14,15 status cha

  o I've tried two different PCMCIA releases without success.

    When I tried "cardctl ident":

    - release 3.0.14 reports no product information available.
    - release 3.0.4 reports the weired manfid (I forgot exactly what it is,
      something like 0x2010 0x1000) for all types of PCMCIA cards that I
      have.

  o I've tried many different memory and io port settings without success.

This adapter works fine on another Linux desktop which is Pentium 133 MMX.

Any help will be greatly appreciated!!!

Thanks a million!

- Jin

Idea Re: Help with an Ricoh ISA-to-PCMCIA bridge card

Re: Question Help with an Ricoh ISA-to-PCMCIA bridge card (Jin Yang)
Date: 2000, Jan 14
From: Ovidiu Predescu ovidiu

Hi,

I had the same problem as you have: everything worked fine when I plugged the WebGear card into a cheap AMD computer that had all the devices (video, audio, ethernet) on board, but failed to work when I moved the card into a more expensive computer with all these devices as external PCI cards.

I scratched my head for about 1 week, installing various kernels, playing with various PCMCIA versions, until I realized that something must be wrong with the interrupts. I took a look at the laptop I'm using as the other wireless computer to see what interrupt the WebGear card uses and observed a difference. The laptop is using irq 3 while the new computer was using irq 9. So I went ahead and I disabled the onboard serial port 2 in BIOS which was using irq 3. Voila, the whole thing started to work again!

BTW, it may help to try disable all the unused controllers that eat up irqs, as it appears that disabling only COM2 somehow doesn't solve the problem.

I hope this helps.

Good luck, Ovidiu

Question PCMCIA will not co-exist with CDROM

Date: 2000, Jan 02
From: Stephen Davies <scldad@sdc.com.au>

Platform: Mandrake 6.1 on Philips TravelNote 580 (2.2.13)
PCMCIA version: 3.1.8
Cards: generic NE200 compatible and generic modem
Controller: Cirrus PD7629
Problem:
Having built 3.1.8 from source to overcome the problems with
the version included in Mandrake 6.1, I have a system where
my PCMCIA setup seems to work perfectly so long as I do not try and touch the CD.

Conversely, if I turn PCMCIA off using /etc/sysconf/pcmcia, 
the CD works properly.

I have tried following the advice in the HOWTO and have 
added PCIC_OPTS=irq_list=9,10 to /etc/sysconf/pcmcia and
have tried several exclude commands in /etc/pcmcia/config.opts
to restrict both ports and memory with no success.

While PCMCIA is active, any attempt to mount /dev/cdrom 
"freezes" that session. Other sessions continue normally.
If the mount attempt is via KDE/KFM, the Cancel button
can be used to recover.

Some time after a command line mount, the whole system hangs 
and must be powered off to recover.


dmesg produces the following:

Intel PCIC probe:
 Cirrus PD6729 PCI-to-PCMCIA at bus 0 slot 19, port oxfcec, 2 sockets
  host opts [0]: [ring] [1/3/2] [1/9/2]
  host opts [1]: [ring] [1/3/2] [1/9/2]
  ISA rqs (default)=9,10 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: clean
cs: IO port probe 0x0100-0x04ff; excluding 0x200-0x207 0x378-0x37f ox398-0x39f ox4d0-0x4d7
cs: memory probe 0xc0000-0xcffff: excluding 0xc0000-0xcbfff
eth0: NE2000 Compatible: io 0x300, irq 9, hw_addr 00:80:C8:8B:29:CF

The CD is on hdc (ide1) and is using the usual adresses and irq.

Hoping there is a simple solution.

Cheers and thanks,
Stephen Davies

None A possible fix

Re: Question PCMCIA will not co-exist with CDROM (Stephen Davies)
Date: 2000, Jan 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Try setting

   PCIC_OPTS="irq_list=9,10 has_ring=0"

-- Dave

Ok That works:-))

Re: None A possible fix (David Hinds)
Date: 2000, Jan 04
From: Stephen Davies <scldad@sdc.com.au>

G'day Dave and thank you very much for your input.

My laptop now seems to do everything that I want.

I checked the doco but could not see what "has_ring" does.
Care to elaborate?

Cheers and thanks,
Stephen

None lockups on insertion or ejection

Date: 2000, Jan 05
From: Jacek Polewczak jacek

Hi everyone,

I have Sony PCG-XG9 notebook (Pentium III 500, 128MB) using Mandrake 6.1 (kernel 2.2.13-22mdk). PCMCIA services (3.1.9) worked fine (so far using only Megahertz XJack 28 V.34 modem) until I installed sound drivers from OSS, 4Front Technologies. I don't seem to get more help from them (claim that it is PCMCIA problem). Below is the description of my problems:

!!! None of the below problems occur if sound is not on !!!

PCMCIA services start at boot; if I insert the modem card and then run "soundon" command everything is OK, no error messages, sound and modem work.

However, after turning sound on any attempts to insert or remove PC card (modem in my case) lock completely the system. I even tried "cardctl eject" or "cardctl insert" before physically removing the card. The system locks upon invocation of cardctl eject.

I have to power off the computer (Ctr+ALt+Del doesn't work).

What works (after soundon is invoked) is the following:

with card still inserted I shut down PCMCIA services and then remove the card. Furthermore, while PCMCIA services are shut down I can insert another PC card, start PCMCIA services and everything seems to be working.

I read in PCMCIA-HOWTO that locking the system during insertion or removal of cards are due to memory probe failures and/or timing register problem. I restricted the memory window corresponding to what I found in Windows/DOS PCMCIA drivers, it accepts it OK but the same problem (lockup) occurs.

I tried to change various configurations of PCMCIA setup (irq_list, cs_irq, poll_interval, do_pci_probe, pci_csc, pci_int, cmd_time, setup_time) without any success. I restricted probed IRQ to just one free interrupt, restricted interrupt used for card status changes (cs_irq), nothing seems to work.

There is one parameter specific to Ricoh Cardbus (from man i82365)

 irq_mode=n
               Selects the interrupt routing method.  A value of 1
               selects ISA interrupt routing, and 2 selects inter-
               rupt  routing via an external serial interrupt con-
               troller.  The default is to  use  whatever  routing
               method is already enabled.

If I set it to irq_mode=2 (although I am not entirely certain what I am doing here) then I don't have lockups with card insertion and/or injection. Sound works, but my modem DOES NOT !!! I found it by accident and I hope that it might help.

Finally, if PNP is activated in BIOS, I don't have the above lockups but, sound doesn't work correctly (the same sound or part of a sound clip is being repeated).

I use defaults config.opts with irq5 excluded.

Starting PCMCIA services not at boot time also doesn't help !

Thanks for any suggestions.

Jacek

Below, I provide outputs of "cat /proc/pci, /proc/interrupts, /proc/modules, /proc/ioports", "cardctl config", and "dmesg"

               "cat /proc/pci"

PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: Intel 440BX - 82443BX Host (rev 3).
      Medium devsel.  Master Capable.  Latency=64.  
      Prefetchable 32 bit memory at 0x40000000 [0x40000008].
  Bus  0, device   1, function  0:
    PCI bridge: Intel 440BX - 82443BX AGP (rev 3).
      Medium devsel.  Master Capable.  Latency=128.  Min Gnt=140.
  Bus  0, device   7, function  0:
    ISA bridge: Intel 82371AB PIIX4 ISA (rev 2).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  No bursts.  
  Bus  0, device   7, function  1:
    IDE interface: Intel 82371AB PIIX4 IDE (rev 1).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  Latency=64.  
      I/O at 0xfc90 [0xfc91].
  Bus  0, device   7, function  2:
    USB Controller: Intel 82371AB PIIX4 USB (rev 1).
      Medium devsel.  Fast back-to-back capable.  IRQ 9.  Master Capable.  Latency=64.  
      I/O at 0xfca0 [0xfca1].
  Bus  0, device   7, function  3:
    Bridge: Intel 82371AB PIIX4 ACPI (rev 3).
      Medium devsel.  Fast back-to-back capable.  
  Bus  0, device   8, function  0:
    FireWire (IEEE 1394): Unknown vendor Unknown device (rev 2).
      Vendor id=104d. Device id=8039.
      Medium devsel.  IRQ 9.  Master Capable.  Latency=64.  Min Gnt=4.Max Lat=4.
      Non-prefetchable 32 bit memory at 0xfedf7000 [0xfedf7000].
      Non-prefetchable 32 bit memory at 0xfedf7c00 [0xfedf7c00].
  Bus  0, device   9, function  0:
    Multimedia audio controller: Unknown vendor Unknown device (rev 2).
      Vendor id=1073. Device id=10.
      Medium devsel.  IRQ 9.  Master Capable.  Latency=64.  Min Gnt=5.Max Lat=25.
      Non-prefetchable 32 bit memory at 0xfedf8000 [0xfedf8000].
      I/O at 0xfcc0 [0xfcc1].
      I/O at 0xfc8c [0xfc8d].
  Bus  0, device  10, function  0:
    Communication controller: Unknown vendor Unknown device (rev 1).
      Vendor id=127a. Device id=2005.
      Medium devsel.  Fast back-to-back capable.  IRQ 9.  Master Capable.  Latency=64.  
      Non-prefetchable 32 bit memory at 0xfede0000 [0xfede0000].
      I/O at 0xfc78 [0xfc79].
  Bus  0, device  12, function  0:
    CardBus bridge: Ricoh Unknown device (rev 128).
      Vendor id=1180. Device id=478.
      Medium devsel.  Master Capable.  Latency=168.  Min Gnt=128.Max Lat=4.
  Bus  0, device  12, function  1:
    CardBus bridge: Ricoh Unknown device (rev 128).
      Vendor id=1180. Device id=478.
      Medium devsel.  Master Capable.  Latency=168.  Min Gnt=128.Max Lat=4.
  Bus  1, device   0, function  0:
    VGA compatible controller: Neomagic Unknown device (rev 32).
      Vendor id=10c8. Device id=5.
      Medium devsel.  Fast back-to-back capable.  IRQ 9.  Master Capable.  Latency=128.  Min Gnt=16.Max Lat=255.
      Prefetchable 32 bit memory at 0xfd000000 [0xfd000008].
      Non-prefetchable 32 bit memory at 0xfe800000 [0xfe800000].
      Non-prefetchable 32 bit memory at 0xfec00000 [0xfec00000].

                    "cat /proc/interrupts"

           CPU0
  0:      24669          XT-PIC  timer
  1:       1436          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  5:          0          XT-PIC  MPU-401 UART
  8:          1          XT-PIC  rtc
  9:          0          XT-PIC  Yamaha DS-XG
 12:          0          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:      53286          XT-PIC  ide0
 15:          4          XT-PIC  ide1
NMI:          0
ERR:          0                  

                     "cat /proc/modules"   

 ymf724                 23396   0
 audiobuf               11088   0 [ymf724]
 opl3                   13912   0 [ymf724]
 uart401                 6892   0 [ymf724]
 midi                   28732   0 [opl3 uart401]
 ac97                    4656   0 [ymf724]
 soundbase             483584   0 [ymf724 audiobuf opl3     uart401 midi ac97]
 sndshield               5356   0 [ymf724 audiobuf opl3    uart401 midi ac97 soundbase]
 serial_cs               5296   0 (unused)
 ds                      6348   2 [serial_cs]
 i82365                 21700   2
 pcmcia_core            41984   0 [serial_cs ds i82365]
 nls_iso8859-1           2052   2 (autoclean)
 nls_cp437               3548   2 (autoclean)
 vfat                   11100   2 (autoclean)
 fat                    33664   2 (autoclean) [vfat]    

                   "cat /proc/ioports"

 0000-001f : dma1
 0020-003f : pic1
 0040-005f : timer
 0060-006f : keyboard
 0070-007f : rtc
 0080-008f : dma page reg
 00a0-00bf : pic2
 00c0-00df : dma2
 00f0-00ff : fpu
 0170-0177 : ide1
 01f0-01f7 : ide0
 0330-0333 : MPU-401 UART
 0376-0376 : ide1
 03c0-03df : vga+
 03e8-03ef : serial(auto)
 03f6-03f6 : ide0
 03f8-03ff : serial(auto)
 13f8-13ff : serial_cs
 fc90-fc97 : ide0
fc98-fc9f : ide1                    

                    "cardctl config"

Socket 0:
  not configured
Socket 1:
  Vcc 5.0V  Vpp1 0.0V  Vpp2 0.0V
  interface type is "memory and I/O"
  irq 3 [exclusive] [level]
  Speaker output is enabled
  function 0:
    config base 0x0100
      option 0x60 status 0x08 pin 0x00 copy 0x00
    io 0x13f8-0x13ff [8bit]       

                    "dmesg"

Linux version 2.2.13-22mdk (root@kenobi.mandrakesoft.com) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 SMP Fri Oct 22 02:06:33 CEST 1999
mapped APIC to ffffe000 (00298000)
Detected 496317320 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 494.80 BogoMIPS
Memory: 127664k/131008k available (1172k kernel code, 424k reserved, 1668k data, 80k init, 0k bigmem)
DENTRY hash table entries: 262144 (order: 9, 2097152 bytes)
Buffer-cache hash table entries: 131072 (order: 7, 524288 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
VFS: Diskquotas version dquot_6.4.0 initialized
Enabling extended fast FPU save and restore...done.
Not enabling KNI unmasked exception support
Exception 19 error handler not integrated yet
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au)
per-CPU timeslice cutoff: 0.00 usecs.
CPU0: Intel Pentium III (Coppermine) stepping 01
SMP motherboard not detected. Using dummy APIC emulation.
PCI: PCI BIOS revision 2.10 entry at 0xfd99e
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 131072 bhash 65536)
Initializing RT netlink socket
Starting kswapd v 1.5 
Detected PS/2 Mouse Port.
Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS02 at 0x03e8 (irq = 4) is a 8250
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9)
Real Time Clock Driver v1.09
RAM disk driver initialized:  16 RAM disks of 20480K size
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xfc90-0xfc97, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xfc98-0xfc9f, BIOS settings: hdc:DMA, hdd:pio
hda: IBM-DARA-218000, ATA DISK drive
hdc: TOSHIBA DVD-ROM SD-C2202, ATAPI CDROM drive
ide2: ports already in use, skipping probe
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: IBM-DARA-218000, 17301MB w/418kB Cache, CHS=2205/255/63
hdc: ATAPI 24X DVD-ROM drive, 128kB Cache
Uniform CDROM driver Revision: 2.56
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
raid5: KNI detected, trying cache-avoiding KNI checksum routine
   pIII_kni  :   995.172 MB/sec
raid5: MMX detected, trying high-speed MMX checksum routines
   pII_mmx   :  1236.345 MB/sec
   p5_mmx    :  1298.448 MB/sec
   8regs     :   609.600 MB/sec
   32regs    :   347.853 MB/sec
using fastest function: pIII_kni (995.172 MB/sec)
scsi : 0 hosts.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
 hda: hda1 hda2 < hda5 > hda3 hda4
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 80k freed
Adding Swap: 104416k swap-space (priority -1)
Linux PCMCIA Card Services 3.1.9
  kernel build: 2.2.13-22mdk #1 SMP Fri Oct 22 02:06:33 CEST 1999
  options:  [pci] [cardbus] [apm]
Intel PCIC probe: 
  Ricoh RL5C478 PCI-to-CardBus at bus 0 slot 12, mem 0x68000000, 2 sockets
    host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 168/176] [bus 32/34]
    host opts [1]: [isa irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 168/176] [bus 35/37]
    ISA irqs (default) = 3,4,5,7,10,11,12 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: excluding 0x1040-0x104f
cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
tty01 at 0x13f8 (irq = 3) is a 16550A

None Re: lockups on insertion or ejection

Re: None lockups on insertion or ejection (Jacek Polewczak)
Date: 2000, Jan 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The problem can be worked around by building the PCMCIA package with
"PnP BIOS support" enabled, for systems that don't get messed up by
that.  A better fix will be in the 3.1.9 PCMCIA package.

-- Dave

Question Sony Vaio PCG-N505VE Config

Date: 2000, Jan 10
From: Tim Jones BruMeister

Has anyone gotten PCMCIA support functioning on a Vaio 505? I can get the CD5 working using the ATA interface of IDE2, but I can't get PCMCIA services working if the CD-ROM is attached (lost interrupt) and, without the CD, cardctl seems to work, but I can't get my Megahertz combo card to work with either the MODEM or the Ethernet.

Stock Red Hat 6.1 install.

Tim

None System log messages help a lot

Re: Question Sony Vaio PCG-N505VE Config (Tim Jones)
Date: 2000, Jan 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Without the log messages, I can only guess, maybe an interrupt
conflict.  You should say exactly what model of card you're using.
Also, it is always a good idea to check the Linux Laptop page, which
has links to maybe 20 pages with info about various Vaio 505 models
under linux.

-- Dave

Ok Turns out PNP in BIOS the Problem

Re: None System log messages help a lot (David Hinds)
Date: 2000, Jan 13
From: Tim Jones BruMeister

Hi David,

It turns out that a combination of the "PNP OS" setting (must be NO) in the BIOS and the "exclude irq" settings in the /etc/pcmcia/config.opts file were the culprets. Here is my final discoveries -- thaks to Jeremy at Sony engineering (friends in low places....) for pointers:

Make sure that /etc/sysconfig/pcmcia is set to include the following:

  • PCMCIA=no
  • PCIC_OPTS="irq_list=10,11 has_ring=0"

And add the folloing to /etc/pcmcia/config.opts:

  • exclude irq 5
  • exclude irq 7
  • exclude irq 9

Unfortunately, cardmgr doesn't seem to work if you just pop cards, but by simply stopping pcmcia, swap cards, and starting pcmcia, all is well.

As an additional note - the commercial OSS drivers support the Yamaha sound chip, but (again) are effected by the "PNP OS" setting in the BIOS -- make sure that it is set to NO!

Tim Jones
Very Happy VAIO 505VE user.

Question 3.1.8 not finding interrupts

Date: 2000, Jan 18
From: Ian Soboroff isoboroff

I tried upgrading from 3.1.2 to 3.1.8 today (kernel version is 2.2.14). Under 3.1.2, there are no problems:

Linux PCMCIA Card Services 3.1.2
  kernel build: 2.2.14 #1 Thu Jan 6 10:07:52 EST 2000
  options:  [pci] [cardbus] [apm] [pnp]
PnP: PNP BIOS installation structure at 0xc00fdae0
PnP: PNP BIOS version 1.0, entry at f0000:423d, dseg at f0000
PCI routing table version 1.0 at 0xf5cd0
  00:0a.0 -> irq 10
  00:0a.1 -> irq 10
Intel PCIC probe: 
  Cirrus PD6832 PCI-to-CardBus at bus 0 slot 10, mem 0x68000000, 2 sockets
    host opts [0]: [ring] [0/7/4] [3/17/4] [pci irq 10] [lat 168/176] [bus 32/34]
    host opts [1]: [ring] [0/7/4] [3/17/4] [pci irq 10] [lat 168/176] [bus 35/37]
    ISA irqs (scanned) = 3,4,5,7 PCI status changes
  Cirrus PD6729 PCI-to-PCMCIA at bus 1 slot 10, port 0xecfc, 2 sockets
    host opts [2]: [ring] [1/3/2] [1/9/2]
    host opts [3]: [ring] [1/3/2] [1/9/2]
    ISA irqs (default) = 3,4,5,7,12 polling interval = 1000 ms

but with 3.1.8, it only finds irq 5. the compile options are the same with both versions, as are the PCIC_OPTS, which are just "cs_irq=9". i tried adding "do_scan=0 irq_list=5,7,9,10" to the PCIC_OPTS for 3.1.8, but this didn't cure the problem.

any ideas?

None Other devices are using those interrupts

Re: Question 3.1.8 not finding interrupts (Ian Soboroff)
Date: 2000, Jan 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It would be useful to also include the messages for 3.1.8, since that
is the version you're having trouble with.

If you enable PnP BIOS support, then 3.1.8 is going to be more
aggressive about excluding interrupts that are known to be committed
to other devices.  Check /proc/bus/pccard/irq to see what devices are
supposed to be using these interrupts.

-- Dave

Sad 3c574 and RH6.0 on a Compaq 1260....

Date: 2000, Jan 21
From: Peter J. Milanese pmilano1

Strange...

It finds irq 9.

Link light is blinking erratically (On hub, since the one on the card is silly).

Don't pass traffic, don't come up automatically.

Everything else looks fine.

The new PCMCIA Subset is on it.

Rrrr... I just noticed a fault.. It isn't autonegotiating. Anyone know how to force it?

P

None The usual request: system log messages?

Re: Sad 3c574 and RH6.0 on a Compaq 1260.... (Peter J. Milanese)
Date: 2000, Jan 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

A bug report without system log messages is not useful.

> Rrrr... I just noticed a fault.. It isn't autonegotiating. Anyone know
> how to force it?

If you're connecting to a hub, that's what you expect: hubs generally
do not autonegotiate.  It should still pick the correct speed.

-- Dave

Question lock up with message "kmem_alloc: Bad slab magic (...)" after insmoding pcmcia_core

Date: 2000, Jan 26
From: Tim Johann t1m

Hi

I´ve got a problem installing pcmcia support at all!

System is a Pentium 120 running Red Hat under kernel 2.2.13 PCMCIA adapter is a VG468 as the probe tells

first I tried to install the whole precompiled kernel .RPM It locked up while trying to install the pcmcia modules on from the startup script. Sometimes it told (a thousand times):

kmem_alloc: Bad slab magic (name=size-128)

I looked up the script and simply found that it was the insmod pcmcia_core line that was making trouble

So I went for compiling the modules myself for a custom kernel (for a couple of times!).

the problem remaind the same =8(.

who has an idea 8-?
		thx, T1M

None Seems to be solved

Re: Question lock up with message "kmem_alloc: Bad slab magic (...)" after insmoding pcmcia_core (Tim Johann)
Date: 2000, Feb 11
From: David Hinds <dhinds@pcmcia.sourceforge.org>

This appeared to be due to use of an older (3.1.3) PCMCIA driver release, and is fixed in current drivers.

-- Dave

Question TP390X, 512MB, and PCMCIA

Date: 2000, Feb 02
From: Andrew Newton <lfs@eskimo.com>

I have a ThinkPad 390X (2626-MOU) with Mandrake 7.0. The kernel is 2.2.14 and pcmcia-cs is 3.1.9 (I know 3.1.10 is the latest, but the release notes didn't say anything that looked relevant to my problem). Cardmgr says I have a TI 1251B PCIC.

Anyway, cardmgr doesn't recognize any cards and constantly spits out "i82365; infinite loop in interrupt handler". In an effort to fix the problem, I have tried several options in /etc/sysconfig/pcmcia. Currently the PCIC_OPTS read "irq_list=3,7 pci_csc=1 pci_int=1 pci_irq_list=4,5,9,10". But they don't seem to make a difference at all.

I do have two workarounds.

The first is to boot into Win98 first. It does recognize the PCMCIA cards. Then I tell Win98 to reboot and have LILO boot Linux. Now the cardmgr has no problems.

The second workaround is based on the following link I found on IBM's web site with CardWizard under Windows (ftp://ftp.pc.ibm.com/pub/pccbbs/mobiles/pctpitfix.txt). Basically, there seems to be some sort of hardware problem with ThinkPad 390X,600E, and 600X and 512MB of memory. So I put "mem=64m" on the append line in lilo and rebooted. No dice. Then I took out one of the 256MB DIMMS giving the sytem just 256MB and rebooted. IT WORKED!

Any ideas?

None It's a flaky BIOS problem

Re: Question TP390X, 512MB, and PCMCIA (Andrew Newton)
Date: 2000, Feb 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I know what's wrong.  The ThinkPad BIOS configures the CardBus bridge
at address 0x10000000 regardless of how much memory is installed.
This address happens to equal 256MB, so if you've got 512MB installed,
the bridge is configured to sit in the middle of your system memory.

Get the latest (09-Feb-00) beta PCMCIA package from sourceforge.org in 
/pcmcia/NEW, and set:

    CORE_OPTS="cb_mem_base=0x20000000"

in /etc/sysconfig/pcmcia and it should work with 512MB installed.

-- Dave

Sad same problem, fixed, but now xircom card wont work

Re: None It's a flaky BIOS problem (David Hinds)
Date: 2000, May 25
From: Dan Trevino dantrevino

I had the same problem, same configuration TP390X 2626MOU, w/512MB RAM. Found this fix, and it works great. No more "infinite loop...." messages, apm problems, etc..But, if I make this change, my xircom card no longer works. Commenting out the line and restarting pcmcia enables my card, but I get the same problems (obviously)....any ideas?

None That doesn't make much sense

Re: Sad same problem, fixed, but now xircom card wont work (Dan Trevino)
Date: 2000, May 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'm not sure I understand.  If you had the original problem, your
system should have barely been functional, but you say your Xircom
card worked??

You should include much more detail.  What Xircom card is this, and
what are your system log messages in the good and bad configurations?

Also you say that just commenting out the fix and restarting PCMCIA
makes your card work.  That shouldn't be possible: commenting out that
line should have no effect until you do a cold boot.  Maybe just
restarting PCMCIA is what "fixed" things?

-- Dave

Idea Actually you only did part of the fix

Re: Sad same problem, fixed, but now xircom card wont work (Dan Trevino)
Date: 2000, May 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You added the startup parameter... but you missed the part about upgrading your PCMCIA drivers. The cb_mem_base parameter is not available in your 3.1.8 PCMCIA drivers. It will work better if you upgrade (3.1.15 is current)

-- Dave

Ok fixed

Re: Idea Actually you only did part of the fix (David Hinds)
Date: 2000, May 25
From: Dan Trevino dantrevino

I'm a bonehead...everything works great! thanks

Question Unresolved symbols vs configuration parameters in 2.3.42

Date: 2000, Feb 07
From: Peter pfolk

So I got kernel 2.3.42 so that I could use netfilter and keep people from hijacking my 'net connection (the machine acts as a bridge between an ad-hoc 802.11 wireless network and the DSL line). Is 3.1.10 supposed to work with the new kernel, as a module?

Compiling it as a static part of the kernel appears to work, except it doesn't find my PCMCIA adapter because I have to pass a configuration parameter (extra_sockets=1) to the i82365 driver. Is there a way to pass this information other than with insmod?

Since afaik I have to use it as a module, I configured it as such using menuconfig, but I get unresolved symbols. In particular, depmod -ae sez:

depmod: *** Unresolved symbols in /lib/modules/2.3.42/pcmcia/ds.o
depmod:         pcmcia_lookup_bus
depmod: *** Unresolved symbols in /lib/modules/2.3.42/pcmcia/i82365.o
depmod:         dead_socket
depmod: *** Unresolved symbols in /lib/modules/2.3.42/pcmcia/yenta.o
depmod:         pci_find_parent_resource
depmod:         probe_irq_mask

I solved the dead_socket problem by defining it in i82365.c (it's just a static struct, normally resolved by linking with cs.o I assume), and got around the pcmcia_lookup_bus problem by not configuring CardBus support. The other two symbols are defined in arch/i386/kernel/irq.c and drivers/pci/pci.c (respectively) but I don't know what to do to get it to link against them. Is this a known problem, or something wrong with my system, or just a normal bug?

Appologies for my lack of kernel-hacker savvy,

Peter

Question Me too; please tell me exactly what you did

Re: Question Unresolved symbols vs configuration parameters in 2.3.42 (Peter)
Date: 2000, Feb 08
From: cosmos

I experienced what you described on my Olivetti Echos 133DM
with Xircom REM56G, compiling 2.3.42 and pcmcia-cs 3.1.10.

Compiling kernel 2.3.X I set:

General setup -> PCMCIA/CardBus support -> PCMCIA/CardBus support M
General setup -> PCMCIA/CardBus support -> i82365 support Y
Network device support -> Network device support Y
Network device support -> Ethernet (10 or 100Mbit) Y
Character device -> PCMCIA character device support -> PCMCIA serial device support M
Character device -> PCMCIA character device support -> PCMCIA serial device support M

But there is a problem with loading the module (during boot phase) i823565.o,
there is an unresolved symbol: dead_socket

Please tell me how to modify i82365.c to go forward (and solve
next problems!).

Thank you very much.

More What I did

Re: Question Me too; please tell me exactly what you did
Date: 2000, Feb 08
From: Peter pfolk

I copied from cs.c the lines defining dead_socket....something like:

  blah blah dead_socket =
    { 0, 0, SS, 0 };

into the equivalent place in ds.c (after all the #includes). I'd give you a diff but the machine is inaccessible right now.

Pete

Warning 3.1.10 does no longer work on DELL Inspiron 7500

Date: 2000, Feb 11
From: Ronny Bremer rbremer

Hardware: DELL Inspiron 7500

The PCMCIA release 3.1.8 works and gives the following message at startup:

Feb 11 08:56:27 fghamw07 kernel: Linux PCMCIA Card Services 3.1.8 
Feb 11 08:56:27 fghamw07 kernel:   kernel build: 2.2.14 #4 Wed Feb 9 09:28:40 CET 2000 
Feb 11 08:56:27 fghamw07 kernel:   options:  [pci] [cardbus] [apm] [pnp] 
Feb 11 08:56:27 fghamw07 kernel: PnP: PNP BIOS installation structure at 0xc00f7210 
Feb 11 08:56:27 fghamw07 kernel: PnP: PNP BIOS version 1.0, entry at f0000:a776, dseg at 400 
Feb 11 08:56:27 fghamw07 kernel: PCI routing table version 1.0 at 0xfdf50 
Feb 11 08:56:27 fghamw07 kernel:   00:04.0 -> irq 11 
Feb 11 08:56:27 fghamw07 kernel:   00:04.1 -> irq 11 
Feb 11 08:56:27 fghamw07 kernel: Intel PCIC probe:  
Feb 11 08:56:27 fghamw07 kernel:   TI 1225 PCI-to-CardBus at bus 0 slot 4, mem 0x68000000, 2 sockets 
Feb 11 08:56:27 fghamw07 kernel:     host opts [0]: [ring] [pwr save] [serial pci & irq] [pci irq 11] [lat 168/32] [bus 32/34] 
Feb 11 08:56:27 fghamw07 kernel:     host opts [1]: [ring] [pwr save] [serial pci & irq] [pci irq 11] [lat 168/32] [bus 35/37] 
Feb 11 08:56:27 fghamw07 kernel:     ISA irqs (scanned) = 9,10 polling interval = 1000 ms 
Feb 11 08:56:28 fghamw07 cardmgr[434]: starting, version is 3.1.8

When using 3.1.10 however, the output stops with the line:

ISA irqs (scanned) = 3,4,7,9,10

and the systems freezes. I cannot interrupt anything, it is dead stopped. I tried multiple times, same effect. As you can see, the list of detected interrupts did change, I do no know why, since my config files are identical (in terms of the excluded and included resources).

Any help would be appreciated.

Ronny

Warning 3.1.9 / 3.1.10 Broken for IBM ThinkPad i1460

Re: Warning 3.1.10 does no longer work on DELL Inspiron 7500 (Ronny Bremer)
Date: 2000, Feb 15
From: Kenny Jansson kenson

I have the exact same problem as Ronny but with my ThinkPad i1460. It works with 3.1.8 but freezes while (or after) scanning IRQ's in 3.1.9 and 3.1.10.

This is during insmod of i82365.o

With 3.1.8 it detects a O2Micro OZ6812 PCI-to-CardBus at slot 19 and with 3.1.10 it detects the same thing at slot 00:13. and after the IRQ (defaults) the machine freezes.

/Kenny

Note PnP is enabled

Re: Warning 3.1.9 / 3.1.10 Broken for IBM ThinkPad i1460 (Kenny Jansson)
Date: 2000, Feb 17
From: Ronny Bremer rbremer

David,

as you can see ::points up:: I am not alone ;)

anyway, I tried it with both PnP enabled and disabled, same effect.

Ronny

Ok tried beta, works :)

Re: Note PnP is enabled (Ronny Bremer)
Date: 2000, Feb 25
From: Ronny Bremer rbremer

David,

I tried the beta from 2/18 and it does work :) Thanks a bunch man !!

Ronny

Question Compile-errors in 3.1.10

Date: 2000, Feb 15
From: Rolf Rander Naess rolfn

I am trying to compile 3.1.10 on a RedHat 6.1 system, currently running 2.2.12.
#gcc --version
2.8.1
#ld -v
GNU ld version 2.9.1 (with BFD 2.9.1.0.25)
and I get:
gcc -MD -c -O2 -I../include -I/usr/src/linux/include -D__KERNEL__ -DEXPORT_SYMTAB -DMODVERSIONS -include /usr/src/linux/include/linux/modversions.h -DMODULE -DCARDBUS 3c575_cb.c
3c575_cb.c: In function `vortex_up':
3c575_cb.c:1206: structure has no member named `tbusy'
3c575_cb.c:1207: structure has no member named `interrupt'
3c575_cb.c:1208: structure has no member named `start'
3c575_cb.c: In function `vortex_tx_timeout':
3c575_cb.c:1430: structure has no member named `tbusy'
3c575_cb.c: In function `vortex_start_xmit':
3c575_cb.c:1532: structure has no member named `tbusy'
3c575_cb.c:1552: structure has no member named `tbusy'
3c575_cb.c: In function `boomerang_start_xmit':
3c575_cb.c:1589: structure has no member named `tbusy'
3c575_cb.c:1634: structure has no member named `tbusy'
3c575_cb.c: In function `vortex_interrupt':
3c575_cb.c:1653: structure has no member named `interrupt'
3c575_cb.c:1656: structure has no member named `interrupt'
3c575_cb.c:1667: structure has no member named `interrupt'
3c575_cb.c:1697: structure has no member named `tbusy'
3c575_cb.c:1698: `NET_BH' undeclared (first use in this function)
3c575_cb.c:1698: (Each undeclared identifier is reported only once
3c575_cb.c:1698: for each function it appears in.)
3c575_cb.c:1720: structure has no member named `tbusy'
3c575_cb.c:1729: structure has no member named `tbusy'
3c575_cb.c:1770: structure has no member named `interrupt'
3c575_cb.c: In function `vortex_down':
3c575_cb.c:1945: structure has no member named `start'
3c575_cb.c:1946: structure has no member named `tbusy'
3c575_cb.c: In function `vortex_close':
3c575_cb.c:1980: structure has no member named `start'
3c575_cb.c: In function `vortex_get_stats':
3c575_cb.c:2021: structure has no member named `start'
make[1]: *** [3c575_cb.o] Error 1
make[1]: Leaving directory `/export/a/src/pcmcia-cs-3.1.9/clients'
make: *** [all] Error 2

None Some more info!

Re: Question Compile-errors in 3.1.10 (Rolf Rander Naess)
Date: 2000, Feb 15
From: Rolf Rander Naess rolfn

Forgot to say: I'm compiling against kenel 2.3.45, I suppose this might be a problem. (I need to upgrade pcmcia to use this kernel, so I figured I should compile against it as well)

None You left out the part about a 2.3.* development kernel

Re: Question Compile-errors in 3.1.10 (Rolf Rander Naess)
Date: 2000, Feb 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

So... it looks like you're compiling 3.1.9 (not 3.1.10), and you're
not actually building it for the 2.2.12 kernel you mention, you're
building it against a 2.3.43 or newer development kernel.

This combination won't work, due to API changes in the latest
development kernels.  You can try the latest beta on sourceforge.org
in /pcmcia/NEW.

-- Dave

Question better combination?

Re: None You left out the part about a 2.3.* development kernel (David Hinds)
Date: 2000, Feb 16
From: Luis Villa luge

David-

I am having the same problem, and need a 2.3.x for the USB code. So:

1) How stable are those "NEW" packages? Will I have any luck with them at all or am I just wasting my time?

2) If they aren't particularly usable, how far back into the 2.3.x tree do I have to go to get a kernel that doesn't have the "improved" API? Obviously, this isn't the ideal solution, but if that is what it'll take...

Thanks a bunch for everything you've done-

Luis Villa (long time user, first time luser :)

Question One other question

Re: Question better combination? (Luis Villa)
Date: 2000, Feb 16
From: Luis Villa luge

One more thing:

How does this package interface with the stuff in the kernel? Should I leave all that stuff compiled out, or does the package now depend on it, assuming that it is there? I'll be testing this shortly, but that kernel re-compile will take a while :)

Luis

None For post-2.3.36, you must use the modules from the kernel tree

Re: Question One other question (Luis Villa)
Date: 2000, Feb 17
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If you have a post-2.3.36 kernel, and the latest PCMCIA beta release,
then you must use the PCMCIA stuff in the kernel; the PCMCIA package
itself will only build the user-level PCMCIA utilities.

-- Dave

Question Card works in slot 1 but not slot 0

Date: 2000, Feb 16
From: John Ruttenberg rutt

I have some memory of this issue begin covered in the HOWTO or somewhere, but I can't find it now.

Can someone please jog my memory about where to read about trouble shooting this kind of problem?

None I'd want to see more information

Re: Question Card works in slot 1 but not slot 0 (John Ruttenberg)
Date: 2000, Feb 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'd first want to see system log messages.

-- Dave

Question Problems with Netgear FA510 PCMCIA card on a Toshiba 4080 XCDT computer

Date: 2000, Feb 18
From: Fred Mckenzie Fredmac

I am trying to install a NETGEAR FA310 PCMCIA ethernet card into my Toshiba 4080XCDT notebook computer. Has anyone successfully installed this card into a similar Toshiba? Does anyone have a driver that works? I can't seem to find one for it. I'm using Redhat 6.1.

None Err, which of those is it?

Re: Question Problems with Netgear FA510 PCMCIA card on a Toshiba 4080 XCDT computer (Fred Mckenzie)
Date: 2000, Feb 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Is it a FA510, or a FA310?

Neither is on the supporte cards list.  The NetGear FA410TXC is on the
list.

-- Dave

Question inb outb, compile failure with Redhat 6.1 please help.

Date: 2000, Feb 20
From: ehlarson

I am having difficulty compiling the PCMCIA card services under RedHat 6.1 - kernel 2.2.12-20 smb, versions 3.0.14 and 3.1.10, 3.1.11. In each case the compilation fails with the following series of errors:

obe.c -o probe probe.c: In function `i365_get':

probe.c:157: warning: implicit declaration of function `outb'

probe.c:157: warning: implicit declaration of function `inb'

probe.c: In function `tcic_getw':

probe.c:284: warning: implicit declaration of function `inw'

probe.c: In function `tcic_setw':

probe.c:290: warning: implicit declaration of function `outw'

/tmp/ccnlFJoj.o: In function `i365_get':

/tmp/ccnlFJoj.o(.text+0x289): undefined reference to `outb'

/tmp/ccnlFJoj.o(.text+0x295): undefined reference to `inb'

/tmp/ccnlFJoj.o: In function `i365_set':

/tmp/ccnlFJoj.o(.text+0x2bd): undefined reference to `outb'

/tmp/ccnlFJoj.o(.text+0x2cd): undefined reference to `outb'

/tmp/ccnlFJoj.o: In function `i365_probe':

/tmp/ccnlFJoj.o(.text+0x491): undefined reference to `outb'

/tmp/ccnlFJoj.o(.text+0x49e): undefined reference to `outb'

/tmp/ccnlFJoj.o: In function `tcic_getb':

/tmp/ccnlFJoj.o(.text+0x5a3): undefined reference to `inb'

/tmp/ccnlFJoj.o: In function `tcic_setb':

/tmp/ccnlFJoj.o(.text+0x5c4): undefined reference to `outb'

/tmp/ccnlFJoj.o: In function `tcic_getw':

/tmp/ccnlFJoj.o(.text+0x5db): undefined reference to `inw'

/tmp/ccnlFJoj.o: In function `tcic_setw':

/tmp/ccnlFJoj.o(.text+0x5fc): undefined reference to `outw'

collect2: ld returned 1 exit status etc.

My config dialog goes like:

    -------- Linux PCMCIA Configuration Script --------

The default responses for each question are correct for most users. Consult the PCMCIA-HOWTO for additional info about each option.

Linux source directory [/usr/src/linux]:

The kernel source tree is version 2.2.12-20. WARNING: the current kernel is actually version 2.2.12-20smp. The current kernel build date is Mon Sep 27 10:34:45 1999.

Alternate target install directory []: 
  Module install directory [/lib/modules/2.2.12-20]: 
Build 'trusting' versions of card utilities (y/n) [n]: 
Include 32-bit (CardBus) card support (y/n) [y]: 
Include PnP BIOS resource checking (y/n) [n]: 

Kernel configuration options:
    Symmetric multiprocessing support is enabled.
    PCI BIOS support is enabled.
    Advanced Power Management (APM) support is enabled.
    SCSI support is enabled.
    Networking support is enabled.
     Radio network interface support is enabled.
     Token Ring device support is enabled.
     Fast switching is disabled.
    Module version checking is enabled.
    /proc filesystem support is enabled.
    Maximum physical memory: 1GB

It looks like you have a System V init file setup.

X Windows include files found. /usr/X11/lib/libforms.so and /usr/X11/include/forms.h found.

Configuration successful.

This is with the standard Redhat 6.1 kernel RPMs, and a version of XForms (0.88-1) which I downloaded from the Redhat contrib directory.

Question PCMCIA modem under Mandrake 7.0

Date: 2000, Feb 20
From: Chris Sleightholme <sleightholme@email.com>

I had my pcmcia modem working fine under RedHat 5.1

Having installed Mandrake 7 I can't get it to work. pcmcia support is enabled and the file /etc/sysconfig/pcmcia is set up the same way as I set it up for redhat.

Any ideas ?

None Bad drivers

Re: Question PCMCIA modem under Mandrake 7.0 (Chris Sleightholme)
Date: 2000, Feb 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The PCMCIA drivers in Mandrake 7.0 are particularly broken.  You can
try to get and install a newer PCMCIA driver release.

-- Dave

Sad Frustrations with kernel versions

Date: 2000, Feb 21
From: ehlarson

Well, after spending about 6 hours working through include files and reinstalls of system components to determine that my previous compile problems were due to a glibc upgrade via autorpm (I don't know yet if it is a compatability issue with PCMCIA and the new GLIBC or if it was a install failure), I was able to get PCMCIA to compile.

HOWEVER I have found that I am not out of the woods by a long shot. I am installing PCMCIA on a Redhat 6.1 smp machine in order to test/use a wireless network card (via an IDE card with a Ricoh controller - according to the HOWTO this SHOULD work). The kernel version I am running is the stock RedHat 2.2.12-20smp supplied with their distro. However, whatever I do - including using ./Configure --current I get complaints that my source tree is 2.2.12-20 whilst the kernel I am running is 2.2.12-20smp. Now color me idiot or something, but AFAIK there is no such thing as a 2.2.12-20smp source tree. In my experience smp kernels are generated via compilation with a particular make option set during the configuration process. After setting this bit and performing the compilation I end up with 'symbols not found' during the install and errors like:

Starting PCMCIA services: modules/lib/modules/2.2.12-20smp/pcmcia/pcmcia_core.o: kernel-module version mismatch
        /lib/modules/2.2.12-20smp/pcmcia/pcmcia_core.o was compiled for kernel version 2.2.12-20
        while this kernel is version 2.2.12-20smp.
/lib/modules/2.2.12-20smp/pcmcia/i82365.o: kernel-module version mismatch
        /lib/modules/2.2.12-20smp/pcmcia/i82365.o was compiled for kernel version 2.2.12-20
        while this kernel is version 2.2.12-20smp.
/lib/modules/2.2.12-20smp/pcmcia/ds.o: kernel-module version mismatch
        /lib/modules/2.2.12-20smp/pcmcia/ds.o was compiled for kernel version 2.2.12-20
        while this kernel is version 2.2.12-20smp.
 cardmgr.

Now I read the statement about CONFIG_MODVERSIONS in the HOWTO - the question is, is this a problem with the version checking mechanism, and my installation is actually ok, or is there some other problem that I need to take care of to get a working PCMCIA...??

In the meantime the version that I compiled or my single CPU laptop seems to be at least recognizing the card, and enabling eth0, so I am at least part way there.

None It is a problem in the PCMCIA Configure script

Re: Sad Frustrations with kernel versions
Date: 2000, Feb 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The Configure script for PCMCIA is getting confused by the difference
in the kernel version names (2.2.12-20 vs 2.2.12-20smp), and I didn't
catch this before because I guess few people have tried building
PCMCIA on a new Red Hat SMP kernel with the "smp" embedded in the
version information.

Try the 21-Feb-00 beta on sourceforge.org in /pcmcia/NEW and see if
that works better.

-- Dave

None Configure Script ?

Re: None It is a problem in the PCMCIA Configure script (David Hinds)
Date: 2000, Feb 27
From: ehlarson

Hi -

I tried the beta with the configure script changes, and found that it has the problem of placing the resulting modules in the wrong directory. After some further experimentation it seems to me that the best way to deal with it is to edit the kernel makefile version string. This way everybody agrees on exactly what is going on.

Also - I found that when compiling for SMP the resulting PCMIA modules are looking for APM functions - this can be fixed by also turning off APM in the kernel makefile, but methinks that PCMCIA should not be looking for them as APM is not going to be around when SMP is active.

Thanks.

None I'll fix module placement; I disagree on the APM thing

Re: None Configure Script ?
Date: 2000, Feb 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I can also fix the problem with module placement, easily enough.  I
didn't notice that when I made the other changes.  Editing the kernel
Makefile isn't really an acceptable work-around; I've tried pretty
hard to make it so that you can avoid having to touch anything in the
kernel source tree, to build PCMCIA.

For APM, all that PCMCIA does is to see how your kernel is configured.
I think it would be wrong for PCMCIA to ignore APM on an SMP kernel.
You've got an APM kernel config option: that is the only sensible
thing for PCMCIA to check.  Some people might want to build a kernel
with SMP and APM, so that they can run the same kernel on their
laptops and their desktop SMP boxes.

-- Dave

Sad Modules not compiling properly with 2.3.47 kernel and pcmcia-cs-3.1.11 .

Date: 2000, Feb 22
From: Steven J. Hill <sjhill@cotw.com>

Greetings.

I have spent a good 1-2 hours trying to get the 'pcmcia-cs' stuff to
compile and am pretty frustrated at this point. I have read all the
documentation including the 'README' and 'PCMCIA-HOWTO' supplied with
the source code. I am running version 2.3.47 of the kernel. I am
using version 3.1.11 of the 'pcmcia-cs' source code.

1) I do the standard 'Configure' and use the following options:

     Linux source directory [/usr/src/linux]: 

     The kernel source tree is version 2.3.47.
     The current kernel build date is Mon Feb 21 17:05:08 2000.

     Alternate target install directory []: 
       Module install directory [/lib/modules/2.3.47]: 
     Build 'trusting' versions of card utilities (y/n) [n]: 
     Include 32-bit (CardBus) card support (y/n) [y]: 

     Kernel configuration options:
         Kernel-tree PCMCIA support is enabled.
         Symmetric multiprocessing support is disabled.
         PCI BIOS support is enabled.
         Advanced Power Management (APM) support is enabled.
         SCSI support is disabled.
         Networking support is enabled.
          Radio network interface support is disabled.
          Token Ring device support is disabled.
          Fast switching is disabled.
         Module version checking is enabled.
         /proc filesystem support is enabled.

     It looks like you have a System V init file setup.

2) I then do a make and everything builds just fine. Only
   problem is that I have PCMCIA supported in the kernel which
   the Configure script told me I had to have using a 2.3.x
   kernel. Because PCMCIA is selected, the make does not enter
   the modules, clients and wireless subdirectories.

3) I do a 'make install' and it installs the new card utilities
   but of course no new drivers. I reboot and of course none
   of my devices are detected because no pcmcia modules were
   built and installed in my '/lib/modules/2.3.47/pcmcia'
   directory.

4) I decided to edit the top level Makefile and force it to
   go into the modules, clients and wireless subdirectories.
   As soon as it goes into the 'modules' subdirectory I get
   the following mess:

    make[1]: Entering directory `/data/pcmcia-cs-3.1.11/modules'
    cc   -MD -O2 -Wall -Wstrict-prototypes -pipe -I../include/static -I/usr/src/linux/include -I../include  -D__KERNEL__ -DMODULE -c i82365.c
    i82365.c: In function `cb_get_state':
    i82365.c:972: structure has no member named `cardbus'
    i82365.c: In function `cb_set_state':
    i82365.c:999: structure has no member named `cardbus'
    i82365.c: In function `cb_set_opts':
    i82365.c:1040: structure has no member named `cardbus'
    i82365.c: In function `add_cb_bridge':
    i82365.c:1640: structure has no member named `cb_bus'
    i82365.c: At top level:
    i82365.c:1810: parse error before `ss_callback_t'
    i82365.c:1811: warning: function declaration isn't a prototype
    i82365.c: In function `pcic_register_callback':
    i82365.c:1812: `call' undeclared (first use in this function)
    i82365.c:1812: (Each undeclared identifier is reported only once
    i82365.c:1812: for each function it appears in.)
    i82365.c:1813: `s' undeclared (first use in this function)
    i82365.c: In function `proc_read_info':
    i82365.c:2384: structure has no member named `cardbus'
    i82365.c: In function `pcic_service':
    i82365.c:2542: `SS_GetStatus' undeclared (first use in this function)
    i82365.c:2553: `SS_GetSocket' undeclared (first use in this function)
    i82365.c:2555: `SS_SetSocket' undeclared (first use in this function)
    i82365.c: In function `init_i82365':
    i82365.c:2620: warning: passing arg 2 of `register_ss_entry_R63d4edac' from incompatible pointer type
    i82365.c: In function `exit_i82365':
    i82365.c:2639: warning: passing arg 1 of `unregister_ss_entry_R7c9ae117' from incompatible pointer type
    make[1]: *** [i82365.o] Error 1
    make[1]: Leaving directory `/data/pcmcia-cs-3.1.11/modules'
    make: *** [all] Error 2

   I get similar errors when I try to go into the 'clients' and
   'wireless' directories.

I would like to point out that I am not an idiot. I followed the
directions, hacked at the makefiles, tried version '3.0.14' with
the same results and have yet to get anything to install modules
so that my PCMCIA cards are recognized. What the heck am I doing
wrong? Thank you in advance. I am booting back to my 2.2.14 kernel
where things work, but I am doing some advanced wireless stuff
and such and really need to be working with the 2.3.x kernel.
Cheers.

-Steve

P.S. I also tried downloading beta stuff from the 'NEW' directory and that did not work either.

None You can't build those modules on a 2.3.* kernel

Re: Sad Modules not compiling properly with 2.3.47 kernel and pcmcia-cs-3.1.11 . (Steven J. Hill)
Date: 2000, Feb 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

For now, with the new 2.3.* kernels, you must use the PCMCIA support
in the kernel, period.  The PCMCIA modules in the standalone package
will not build correctly.

If you require a client driver that has not yet been ported to the
2.3.* kernels, then you are stuck: there is no trick, those drivers
simply cannot be built on 2.3.* at this time.

-- Dave

Question Problems installing 3.1.12 on Madrake 7.0

Date: 2000, Feb 22
From: jong chung quietkey

I jhave followed the HOWTO down to the dot but still stuck. I am a newbie so I could be missing the most obvious.

I ahve so far reached down to:

) I do the standard 'Configure' and use the following options:

       Linux source directory [/usr/src/linux]: 

       The kernel source tree is version 2.2.14.
       The current kernel build date is Mon Jan 17 22:05:08 2000.

       Alternate target install directory []: 
         Module install directory [/lib/modules/2.3.47]: 
       Build 'trusting' versions of card utilities (y/n) [n]: 
       Include 32-bit (CardBus) card support (y/n) [y]: 

       Kernel configuration options:
           Kernel-tree PCMCIA support is enabled.
           Symmetric multiprocessing support is disabled.
           PCI BIOS support is enabled.
           Advanced Power Management (APM) support is enabled.
           SCSI support is disabled.
           Networking support is enabled.
            Radio network interface support is disabled.
            Token Ring device support is disabled.
            Fast switching is disabled.
           Module version checking is enabled.
           /proc filesystem support is enabled.

       It looks like you have a System V init file setup.

So I am back to my prompt somewhat happy this has all worked now when I try to 'Make all' or 'make install' there is no such command. I have to apologize for my ingnorance in Linux. I have just started 2 weeks ago and is still a bit of a mystery to me.

So am i suppose to have literlly typed make all??

I ahve a DELL CPI and it seemed to have worked quite okay on RH 6.1 Oh and also I have the 3cFe575t card from 3Com. Just nudge me in the right way please.

Appreciate any assistance.

None Missing "make" command??

Re: Question Problems installing 3.1.12 on Madrake 7.0 (jong chung)
Date: 2000, Feb 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If

  make all

says

  bash: make: command not found

then your system is incomplete: you have no "make" program, which is a
fairly crucial tool if you want to compile any software.

-- Dave

Warning Toshiba Tecra 8100, 3.1.10 works, 3.1.11 fails

Date: 2000, Feb 22
From: Roger E Critchlow Jr <rec@elf.org>

I spent some hours last night getting pcmcia working
with redhat 6.1 kernel-2.2.12 on a Toshiba Tecra 8100.

Note first that SuSE 6.3 runs out of the box on this machine:

Feb  2 22:18:49 elf8 kernel: Linux PCMCIA Card Services 3.1.3
Feb  2 22:18:49 elf8 kernel:   kernel build: 2.2.13 #1 Mon Nov 8 18:28:35 GMT 1999
Feb  2 22:18:49 elf8 kernel:   options:  [pci] [cardbus] [pnp]

But the pcmcia shipping with RedHat 6.1 didn't work.

I first tried pcmcia-cs-3.1.11, in all configurations tried,
with all sorts of imaginative values for cb_mem_base, the
result was essentially:

Feb 22 03:06:33 localhost pcmcia: Starting PCMCIA services:
Feb 22 03:06:33 localhost pcmcia:  modules
Feb 22 03:06:34 localhost kernel: Linux PCMCIA Card Services 3.1.11 
Feb 22 03:06:34 localhost kernel:   kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 
Feb 22 03:06:34 localhost kernel:   options:  [pci] [cardbus] [apm] [pnp] 
Feb 22 03:06:34 localhost kernel: PCI routing table version 1.0 at 0xf0130 
Feb 22 03:06:34 localhost kernel:   00:0b.0 -> irq 11 
Feb 22 03:06:34 localhost kernel:   00:0b.1 -> irq 11 
Feb 22 03:06:34 localhost kernel: PnP: PNP BIOS installation structure at 0xc00f46c0 
Feb 22 03:06:34 localhost kernel: PnP: PNP BIOS version 1.0, entry at f0000:927f, dseg at 0 
Feb 22 03:06:34 localhost kernel: Intel PCIC probe:  
Feb 22 03:06:34 localhost kernel:   Bridge register mapping failed: check cb_mem_base setting 
Feb 22 03:06:34 localhost kernel: not found. 
Feb 22 03:06:34 localhost pcmcia: /lib/modules/2.2.12-20/pcmcia/i82365.o: 
Feb 22 03:06:34 localhost kernel: ds: no socket drivers loaded! 
Feb 22 03:06:34 localhost pcmcia: init_module: Device or resource busy
Feb 22 03:06:34 localhost pcmcia:  cardmgr.
Feb 22 03:06:34 localhost pcmcia: /lib/modules/2.2.12-20/pcmcia/ds.o: init_module: Device or resource busy
Feb 22 03:06:34 localhost rc: Starting pcmcia succeeded
Feb 22 03:06:34 localhost cardmgr[340]: starting, version is 3.1.11
Feb 22 03:06:34 localhost cardmgr[340]: no pcmcia driver in /proc/devices
Feb 22 03:06:34 localhost cardmgr[340]: exiting

I then tried pcmcia-cs-3.1.10, and immediately succeeded:

Feb 22 03:18:12 localhost pcmcia: Starting PCMCIA services:
Feb 22 03:18:13 localhost pcmcia:  modules
Feb 22 03:18:13 localhost kernel: Linux PCMCIA Card Services 3.1.10 
Feb 22 03:18:13 localhost kernel:   kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 
Feb 22 03:18:13 localhost kernel:   options:  [pci] [cardbus] [apm] [pnp] 
Feb 22 03:18:13 localhost kernel: PCI routing table version 1.0 at 0xf0130 
Feb 22 03:18:13 localhost kernel:   00:0b.0 -> irq 11 
Feb 22 03:18:13 localhost kernel:   00:0b.1 -> irq 11 
Feb 22 03:18:13 localhost kernel: PnP: PNP BIOS installation structure at 0xc00f46c0 
Feb 22 03:18:13 localhost kernel: PnP: PNP BIOS version 1.0, entry at f0000:927f, dseg at 0 
Feb 22 03:18:13 localhost kernel: Intel PCIC probe:  
Feb 22 03:18:13 localhost kernel:   Toshiba ToPIC100 PCI-to-CardBus at slot 00:0b, mem 0x68000000 
Feb 22 03:18:13 localhost kernel:     host opts [0]: [slot 0xf0] [ccr 0x10] [cdr 0x86] [rcr 0xc000000] [pci irq 11] [lat 64/176] [bus 20/20] 
Feb 22 03:18:13 localhost kernel:     host opts [1]: [slot 0xf0] [ccr 0x20] [cdr 0x86] [rcr 0xc000000] [pci irq 11] [lat 64/176] [bus 21/21] 
Feb 22 03:18:13 localhost kernel:     ISA irqs (default) = 5,10 PCI status changes 
Feb 22 03:18:13 localhost pcmcia:  cardmgr.
Feb 22 03:18:13 localhost cardmgr[340]: starting, version is 3.1.10
Feb 22 03:18:13 localhost rc: Starting pcmcia succeeded
Feb 22 03:18:13 localhost cardmgr[340]: watching 2 sockets
Feb 22 03:18:13 localhost kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1330-0x1337 0x1388-0x138f 0x1730-0x1737 0x1788-0x178f 
Feb 22 03:18:13 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x330-0x337 0x388-0x38f 
Feb 22 03:18:13 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Feb 22 03:18:13 localhost inet: inetd startup succeeded
Feb 22 03:18:13 localhost cardmgr[340]: initializing socket 1
Feb 22 03:18:13 localhost kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
Feb 22 03:18:13 localhost cardmgr[340]: socket 1: 3Com 572/574 Fast Ethernet
Feb 22 03:18:14 localhost cardmgr[340]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/3c574_cs.o'
Feb 22 03:18:14 localhost kernel: 3c574_cs.c v1.08 9/24/98 Donald Becker/David Hinds, becker@cesdis.gsfc.nasa.gov. 
Feb 22 03:18:14 localhost kernel: eth0: Megahertz 574B at io 0x300, irq 10, hw_addr 00:00:86:3C:58:26. 
Feb 22 03:18:14 localhost kernel:   ASIC rev 1, 64K FIFO split 1:1 Rx:Tx, autoselect MII interface. 
Feb 22 03:18:14 localhost cardmgr[340]: executing: './network start eth0'

I haven't yet gotten the network up under RedHat, getting
the services started at all was enough for last night.

I needed a "tired face" for this message, I got four hours
of sleep last night.

-- rec --

None Fixed in beta

Re: Warning Toshiba Tecra 8100, 3.1.10 works, 3.1.11 fails (Roger E Critchlow Jr)
Date: 2000, Feb 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It is fixed in today's (22-Feb-00) beta on sourceforge.org in
/pcmcia/NEW.

-- Dave

Agree Yes, it's fixed.

Re: None Fixed in beta (David Hinds)
Date: 2000, Feb 23
From: Roger E Critchlow Jr <rec@elf.org>

Yes, the beta works fine.  Thanks.

-- rec --

Sad Pcmcia problems on Fujitsu lifebook (TI PCI1225)

Date: 2000, Feb 25
From: Wolfgang Wegner Wolfgang

Hello experts, :-)

i am having trouble installing pcmcia card services on a Fujitsu/Siemens Lifebook C6325. This is a PII laptop with Intel BX chipset using the TI PCI1225 PCI/CardBus Bridge.

The setup is attached below. Some other files can be found on http://berta.e-technik.uni-dortmund.de/m_ww/pcmcia/ I am now running kernel 2.2.14 and pcmcia 3.1.11

I just managed to avoid complete lockups by including only one memory region in config.opts, but the card is still not usable. I had one success after having Windows 98 running with the card and forgot to remove the card. The card services started, but the card could not be configured. After re-insertion of the card, it worked - but i could not reproduce this. Also, in this case "lspci -v" showed different results, but unfortunately i did not save this. The system log of this can be found in the file "log_running" (this was still with old kernel and pcmcia-package).

I am not sure if this could be a BIOS problem (look at the
memory regions in lspci!). Under Win98, the resources listed
for PCMCIA bridge and card are as follows:
Socket0: IRQ 11
         mem 08000000-08000fff
Socket1: IRQ 11
         mem 08001000-08001fff
         mem 08040000-08080fff
         i/o 1080-10ff
Network Card: IRQ 11
              mem 0808000-080803ff
              i/o 1080-10ff
              mem 08040000-0807ffff
(This is why i included this memory region in config.opts)
The complete lspci -v output can be found in the file
"lspci".

lspci -v (only PCI1225 portion):
00:04.0 CardBus bridge: Texas Instruments PCI1225 (rev 01)
        Subsystem: Texas Instruments: Unknown device ac1c
        Flags: bus master, medium devsel, latency 168, IRQ 11
        Memory at <ignored> (32-bit, non-prefetchable)
        Bus: primary=00, secondary=20, subordinate=22, sec-latency=32
        I/O window 0: 00000000-00000003
        I/O window 1: 00000000-00000003
        16-bit legacy interface ports at 0007

00:04.1 CardBus bridge: Texas Instruments PCI1225 (rev 01)
        Subsystem: Texas Instruments: Unknown device ac1c
        Flags: bus master, medium devsel, latency 168, IRQ 11
        Memory at <ignored> (32-bit, non-prefetchable)
        Bus: primary=00, secondary=23, subordinate=25, sec-latency=32
        I/O window 0: 00000000-00000003
        I/O window 1: 00000000-00000003
        16-bit legacy interface ports at 0007

uname -rv: 2.2.14 #1 Thu Feb 24 17:08:13 CET 2000

config.opts:#

# Local PCMCIA Configuration File
#
# System resources available for PCMCIA devices
#
include port 0x100-0x4ff, port 0x1000-0x17ff include memory 0x8000000-0x8080fff
# 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 #

when including the two lower memory lines, the system locks up completely upon card insertion! (Not very useful, but can be found in "log_lock").

I hope i supplied enough information to find anything out about this strange thing and did not miss anything in the documentation this time. Or perhaps anyone else already went through this and can help me.

Best regards, Wolfgang

None Memory window is too small

Re: Sad Pcmcia problems on Fujitsu lifebook (TI PCI1225) (Wolfgang Wegner)
Date: 2000, Feb 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

With 3.1.3, you're seeing a bug in the CardBus resource allocation
code.  With 3.1.11, you get an error message that's quite specific:
the card is asking for 260K of memory space, and your memory window
setting is too small.

Enlarge your memory window.  I'd try 0x8000000-0x8ffffff.

-- Dave

Feedback Not yet...

Re: None Memory window is too small (David Hinds)
Date: 2000, Feb 28
From: Wolfgang Wegner Wolfgang

Thanks alot for the tip about the memory space.

Unfortunately, this does not completely solve the issue. I compared the ioport regions reported by /proc/ioports and those given in /etc/pcmcia/config.opts and split the regions in more smaller regions, excluding the ide ports.

This and the larger memory region in fact led to another case of an almost-working pcmcia subsystem. Upon card insertion, the system locked up as usual after the first high beep. No keystroke could be seen on the screen. After removing the card, all pending activities (the second beep, the keystrokes) were issued and the system was running. From now on, the card could be inserted and was usable up to the next reboot. Unfortunately, i could not reproduce this behaviour after reboot... :-(

I post the modified /etc/pcmcia/config.opts and the dmesg output of the almost-working case (the two card insertions can be seen. In the first case, the card's eeprom was not seen by the driver).

Another thing perhaps worth to be mentioned: Whenever the system locked up and could not be reactivated by removing the card, the system log (/var/log/messages) was filled with a number of binary zero's...?! (That is why i suspected the ide port regions) After changing the ioport regions, this could not be reproduced, so perhaps one more issue is solved.

config.opts:

#
# Local PCMCIA Configuration File
#
# System resources available for PCMCIA devices
#
# include port 0x100-0x4ff, port 0x1000-0x17ff
include port 0x100-0x16f, port 0x200-0x36f, port 0x1000-0x103f, port 0x1050-0x17 ff include memory 0x8000000-0x8ffffff
# 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 #

dmesg output (two subsequent card insertions):
Linux PCMCIA Card Services 3.1.11
  kernel build: 2.2.14 unknown
  options:  [pci] [cardbus] [apm] [pnp]
PCI routing table version 1.0 at 0xfdf60
PnP: PNP BIOS installation structure at 0xc00f7170
PnP: PNP BIOS version 1.0, entry at f0000:a554, dseg at 400
Intel PCIC probe: 
  TI 1225 PCI-to-CardBus at slot 00:04, mem 0x68000000
    host opts [0]: [serial pci & irq] [pci irq 11] [lat 64/32] [bus 32/34]
    host opts [1]: [serial pci & irq] [pci irq 11] [lat 64/32] [bus 35/37]
    ISA irqs (scanned) = 3,9,10 PCI status changes
cs: IO port probe 0x1050-0x17ff: clean.
cs: IO port probe 0x1000-0x103f: clean.
cs: IO port probe 0x0200-0x036f: clean.
cs: IO port probe 0x0100-0x016f: clean.
cs: IO port probe 0x0a00-0x0aff: clean.cs: cb_alloc(bus 35): vendor 0x1011, device 0x0019
cs: cb_config(bus 35)
  fn 0 bar 1: io 0x200-0x27f
  fn 0 bar 2: mem 0x80c0000-0x80c03ff
  fn 0 rom: mem 0x8080000-0x80bffff
cs: cb_enable(bus 35)
  bridge io map 0 (flags 0x21): 0x200-0x27f
  bridge mem map 0 (flags 0x1): 0x8080000-0x80c0fff
tulip_reap()
tulip_attach(bus 35, function 0)
tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.un
i-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
eth0: Digital DS21143 Tulip rev 65 at 0x200,<7>cs: cb_disable(bus 35)
cs: cb_release(bus 35)
 EEPROM not present, 00:4C:69:6E:75:79, IRQ 11.
eth0:  Missing EEPROM, this interface may not work correctly!
cs: cb_free(bus 35)
cs: cb_alloc(bus 35): vendor 0x1011, device 0x0019
cs: cb_config(bus 35)
  fn 0 bar 1: io 0x280-0x2ff
  fn 0 bar 2: mem 0x80c0000-0x80c03ff
  fn 0 rom: mem 0x8080000-0x80bffff
cs: cb_enable(bus 35)
  bridge io map 0 (flags 0x21): 0x280-0x2ff
  bridge mem map 0 (flags 0x1): 0x8080000-0x80c0fff
tulip_reap()
tulip_attach(bus 35, function 0)
eth1: Digital DS21143 Tulip rev 65 at 0x280, 00:E0:98:75:08:67, IRQ 11.
eth1:  EEPROM default media type Autosense.
eth1:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
eth1:  MII transceiver #0 config 3000 status 7809 advertising 01e1.

I really do not know what i am doing wrong here. And i also do not know what is the difference in the rare cases it works.

Clueless, Wolfgang

Ok Seems to be solved...(Fujitsu C6325 now working)

Re: None Memory window is too small (David Hinds)
Date: 2000, Mar 03
From: Wolfgang Wegner Wolfgang

Hi all,

The problem seems to be solved now.

I think i was a bit blind again... In the rare cases the system "un-freezed" after removing the card, the tulip_cb module was still used (and thus not unloaded), and all subsequent card insertions did not use the ioport 0x200 used upon first card insetion but port 0x280 instead.

So i just changed the config to not use the port range from 0x200 but from 0x280 and now all works. I am still not sure what conflict i ran into, but whatever it was, it is in the region 0x200-0x27f.

Best regards, Wolfgang

Sad Problems with PCMCIA(TI 1225) on a Compaq Armada 1500C and SuSE 6.3 Kernel 2.2.13

Date: 2000, Feb 25
From: Knut-Perry G. Brumoen Kavkazz

When I installed PCMCIA on my laptop the first time I was
using kernel 2.2.5 and then everything but sound was working
excelent, BUT when I bought SuSE 6.3 with kernel 2.2.13 I got
everything except PCMCIA to work. The system freezes or even
reboots when it is

Starting PCMCIA services : modules_

_ is a blinking cursor.


Even with card inserted and without
It is a TI 1225 slot. i82365 compatible.

Please help me........

I have tried a lots of things, turning of scanning and other
resource related stuff.

None It is a problem with SuSE 6.3

Re: Sad Problems with PCMCIA(TI 1225) on a Compaq Armada 1500C and SuSE 6.3 Kernel 2.2.13 (Knut-Perry G. Brumoen)
Date: 2000, Feb 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You need to turn off PnP support in the pcmcia_core module.  SuSE
should not have turned it on by default.  See:

    http://sdb.suse.de/sdb/en/html/mneden_6.3_pcmcia-start.html

for instructions.

-- Dave

Sad Nope... It wasn't that easy.

Re: None It is a problem with SuSE 6.3 (David Hinds)
Date: 2000, Feb 25
From: Knut-Perry G. Brumoen Kavkazz

It wasn't that easy and I have tried something like that
before. I have even tried to install the 2.2.5 kernel when
running SuSE 6.3 and it works fine, but the soundcard is
creating some errors that makes everything up side down!!!

But running on 2.2.13 the PCMCIA doesn't work. Not even with
2.2.14. Only with 2.2.5!

None Re: Sad: Nope... It wasn't that easy.

Re: Sad Nope... It wasn't that easy. (Knut-Perry G. Brumoen)
Date: 2000, Feb 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The kernel version is not relevant.  There are no differences between
a 2.2.5 and 2.2.13 kernel that should affect PCMCIA.

If it isn't the SuSE issue, and you say you've already tried "lots of
things" which I guess include all the suggestions in the PCMCIA-HOWTO
chapter on installation problems, then my next suggestion would be to
upgrade your PCMCIA drivers.

-- Dave

None Already upgraded

Re: None Re: Sad: Nope... It wasn't that easy. (David Hinds)
Date: 2000, Feb 25
From: Knut-Perry G. Brumoen Kavkazz

Yes HOWTO documentation is already well read.
Their are already upgraded. Even tried older versions but
with no luck. Sorry, but my Compaq ain't easy to live with!!

But thanks anyway..

Question Partial card functionality, memory port probs?

Date: 2000, Feb 26
From: Ben hoyt <ben@spectrumwireless.net>

First, vital statistics:
   Linux version 2.2.13
   Linux PCMCIA Card Services 3.1.10
   ...
   Intel i82365sl A step ISA-to-PCMCIA at port 0x3e0 ofs 0x00
    host opts [0]: none
    host opts [1]: none
    ISA irqs (default) = 3,5,7,9,10,12,14,15 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: excluding 0x11f0-0x1207 0x12f8-0x1307 0x1378-0x1387 0x13f0-0x13ff
cs: IO port probe 0x0100-0x04ff: excluding 0x1f0-0x207 0x378-0x387 0x3f0-0x3ff
cs: IO port probe 0x0a00-0x0aff: excluding 0xaf8-0xaff
cs: memory probe 0x0d0000-0x0dffff: clean.

And: swlr# cat /proc/bus/pccard/memory 000d0000-000d0fff : card services

With that out of the way, I have an interesting problem with
multiple cards.  The hardware is an embedded system board with an onboard PCMCIA controller.  The processor is an AMD Elan
SC400 (http://www.amd.com/products/lpd/elan400/21026b.html) that has PCMCIA functionality 'built-in'.  I've had
3c589_cs working on older kernel versions and older pcmcia-cs
 versions, but with my existing software, I have a problem
 running 3c589_cs, and more specifically Elmer Joandi's
 Aironet 4800 driver.  I have never been able to make the
 Aironet 4800 card work on this hardware, no matter what
 software versions I've used.  With both cards/drivers, the
 card is found, but the driver has a problem doing anything
 with it.  I can configure it with an address, and try
 pinging, but I get errors, such as these with 3c589:

eth1: 3Com 3c589, io 0x310, irq 3, hw_addr FF:FF:FF:F9:FF:FA
  32K FIFO split 3:5 Rx:Tx, auto xcvr
eth1: interrupt(s) dropped!
eth1: interrupt(s) dropped!
eth1: interrupt(s) dropped!
eth1: interrupt(s) dropped!
eth1: command 0x5800 did not complete!
eth1: command 0x5800 did not complete!
eth1: command 0x5800 did not complete!
eth1: interrupt(s) dropped!

.... and so on. Note the hw_addr - probably bad! This is the same thing that happens with the 4800 card, I get a bogus MAC address, and various error messages when I try to read/write to it.

Pulling the card I'm using and trying to load the drivers produces the logical response - card not found. I tried loading X driver for Y card to see if that was a problem/possibility, and that produced the logical response as well - wrong driver for the card. It seems that the cards are being seen and identified, and I can "kind of" communicate with them, but not all the way.

Memory addresses 0xd0000-0xdffff are shown free by the system, and the probe, and I have verified vigorously with the hardware manufacturer that this is the case.

Anyone have any ideas?

None Maybe an IO port issue?

Re: Question Partial card functionality, memory port probs? (Ben hoyt)
Date: 2000, Feb 26
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I think I'd reclassify this as a development issue, just because it is
an oddball platform... (and one that I didn't know worked at all until
now)

The first thought I have is that it would be very useful to determine
which PCMCIA releases worked, and when problems started to appear.
And compare the startup messages from the working configuration with
the current one, if that is possible.  I take it that you didn't need
to use any out-of-the-ordinary settings with the older drivers?

I don't know anything about Elmer Joandi's Aironet driver.  The
current PCMCIA release includes Ben Reed's driver for these cards.

> eth1: 3Com 3c589, io 0x310, irq 3, hw_addr FF:FF:FF:F9:FF:FA

My first guess here would be that maybe you're seeing an IO port
conflict.  The hw_addr is read using IO ports.

-- Dave

More IO Mapping

Re: None Maybe an IO port issue? (David Hinds)
Date: 2000, Feb 28
From: Ben hoyt <ben@spectrumwireless.net>

OK, here is the info that I used to (in my mind) eliminate the possibility of an IO overlap, other than bugging the HW manufacturer. I may have missed something, so here it is:

swlr# cat interrupts ioports
           CPU0
  0:   25356934          XT-PIC  timer
  1:          0          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  4:       2107          XT-PIC  serial
  8:          2          XT-PIC  rtc
 11:      30250          XT-PIC  SMC9194
 13:          0          XT-PIC  fpu
NMI:          0
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
02f8-02ff : serial(auto)
0300-030f : SMC9194
03d4-03d5 : cga
03f8-03ff : serial(auto)
swlr# insmod /lib/modules/pcmcia_core.o;insmod /lib/modules/i82365.o ignore=1
swlr# insmod /lib/modules/ds.o
swlr# cat interrupts ioports
           CPU0
  0:   25364560          XT-PIC  timer
  1:          0          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  4:       2107          XT-PIC  serial
  8:          2          XT-PIC  rtc
 11:      30697          XT-PIC  SMC9194
 13:          0          XT-PIC  fpu
NMI:          0
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
02f8-02ff : serial(auto)
0300-030f : SMC9194
03d4-03d5 : cga
03e0-03e1 : i82365
03f8-03ff : serial(auto)
swlr# # Inserting Aironet modules.  You can find them in the 2.3.newest kernel, I'm using the 2.2.13 version.

swlr# cat interrupts
           CPU0
  0:   25374716          XT-PIC  timer
  1:          0          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  3:          0          XT-PIC  aironet4500_cs
  4:       2107          XT-PIC  serial
  8:          2          XT-PIC  rtc
 11:      31301          XT-PIC  SMC9194
 13:          0          XT-PIC  fpu
NMI:          0
swlr# cat ioports
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0100-013f : aironet4500_cs
02f8-02ff : serial(auto)
0300-030f : SMC9194
03d4-03d5 : cga
03e0-03e1 : i82365
03f8-03ff : serial(auto)

As you can see, I'm running at IRQ 3, IO 0x100. This is on my 'special' hardware. Now, the stats from a different HW platform running 2.0.37, and a slightly older pcmcia-cs:

dts-dtn-rtr# cat interrupts ioports
 0: 1026540671   timer
 1:          8   keyboard
 2:          0   cascade
 3: 2552978658   aironet4500_cs
 4:         10 + serial
 8:          0 + rtc
11: 2409110548   eth0
13:          0   math error
15:          2   i82365
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-009f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : npu
0100-013f : aironet4500_cs
03b0-03bb : mda
03bf-03bf : mda
03e0-03e1 : i82365
03f8-03ff : serial(set)
ff80-ff9f : eth0

As you can see CS assigns the HW the same IO/IRQ for both platforms. Both platforms have been verified by the HW manufacturer to have no IO conflicts at these addresses.

I'll let you guys puzzle over that. In the meantime, I'm going to upgrade to kernel 2.3.latest and see what happens re: these cards.

None Not a kernel issue; maybe timing?

Re: More IO Mapping (Ben hoyt)
Date: 2000, Feb 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Ok, I'm a little confused about exactly what worked and what does not
work.  It sounds like the 3c589 card worked on this box with [some
earlier driver version].  I'd like to see the kernel messages from
that case.  And both cards work on another box, but you don't really
say how that box is different from the one that doesn't work.

As for the potential for an IO overlap, you cannot tell much by
looking at /proc.  Those files show what resources Linux knows are in
use.  But you can have a conflict with a device Linux doesn't know
about.  Excluding resources in /etc/pcmcia/config.opts is an easy
thing to try.  I suspect it won't help, but you should try.

I don't believe that changing kernels is likely to make any difference
at all.

Another thing to try is to load the pcmcia_core module with an option
like "io_speed=300" to change the timing of IO accesses.

-- Dave

None Clarification

Re: None Not a kernel issue; maybe timing? (David Hinds)
Date: 2000, Feb 28
From: Ben hoyt <ben@spectrumwireless.net>

To clarify what does and doesn't work:

With an older kernel and pcmcia-cs, 3c589 was functioning on my 'new' hardware. With 2.2.12 and pcmcia-cs 3.1.10, 3c589 does not work. The Aironet driver that worked on all kernel/pcmcia versions on my 'old' hardware has not worked yet on the 'new' hardware, regardless of software versions.

I've tried excluding, no luck.

I just tested pcmcia_core with different io_speed parameters, including 300, no help.

I'm going to revert back to something that does work on my new hardware - an older kernel and pcmcia-cs. Then, I'll move up from there, and hopefully identify if it is the different kernel version, or pcmcia-cs version that is making the difference.

Question Install and config of Linksys desktop PCMRDWR reader writer and PCM100H1 card

Date: 2000, Feb 26
From: Jeff Gembler jeffrey.gembler

CONTENTS

  WHAT I WANT
    [ PCMCIA DEVICES THAT I WANT TO USE ]

  MY QUESTIONS

  SOME BACKGROUND
    [ WHY I BELIVE I HAVE A CHANCE OF MAKING THIS WORK ]
    [ WHAT I HAVE DONE SO FAR ]
    [ A NOTE ABOUT THE VIA VT83C469 ]

  COMMAND OUTPUT  &  FILE LISTINGS  &  DIRECTORY LISTINGS
    [ Command output: probe -v ]
    [ Command output: probe -m ]
    [ Command output: lsmod ]

    [ File listing: /proc/modules ]
    [ File listing: /proc/ioports ]
    [ File listing: /proc/devices ]
    [ File listing: /proc/interrupts ]
    [ File listing: /etc/pcmcia/config ]
    [ File listing: /etc/pcmcia/config.opts ]

    [ File listing: /var/log/messages ]

    [ Dir listing: /lib/modules/pcmcia,  using ls -lF ]



***************************************************************************
*  WHAT I WANT
*    [ PCMCIA DEVICES THAT I WANT TO USE ]
***************************************************************************

[ PCMCIA DEVICES THAT I WANT TO USE ]
I need help in installing and configuring the following two items

1) PC desktop internal dual-slot PCMCIA reader writer 
   ( Linksys ProConnect(r) PCMCIA Card Reader/Writer,  Model No. PCMRDWR )
   This device uses the VIA VT83C469 controller  -  
   I verified this by looking at the chip on the board.

   Note: This is a two-slot reader writer

2) PCMCIA card
   ( Linksys HomeLink(tm) Phoneline + 10/100 Network PC Card, 
   Model No. PCM100H1 )
   This is an Eth network PCMCIA card that also does HomePNA (HPNA).



**************************************************************************
*  MY QUESTIONS
*
**************************************************************************

What help can you give me here, how do I get this working?

Are the PCMCIA drivers stable and usable for what I want to do?

Where, specifically, are the driver modules or files that support
the Linksys internal PCMCIA reader writer Model No. PCMRDWR

Where, specifically, are the driver modules or files that support
the Linksys Eth/HPNA card Model No. PCM100H1

I didn't rebuild the kernel (at least don't thing I did).
The only make commands that I executed where for the PCMCIA build.
So, the kernel and PCMCIA should be in sync ?
So no need to look into the CONFIG_MODVERSIONS kernel option?

The way things are right now, I don't get any beeps on plugging in
or removing a PCMCIA card.  Should I?

I've been looking at all the HOWTO's and man pages that I can find
that might help.  Are there some that I should be reading?

Doesn't seem to be any books on Linux that go into PCMCIA in much
detail, even less on desktop (instead of laptop) PCMCIA.
Is there anything out there?

Should I be able to 
verify the PCMCIA reader/writer is present (by reading registers, etc.),
verify that the PCMCIA card is present (by reading registers, etc.) ?

In  /etc/sysconfig/pcmcia

If there is more that one option for PCIC_OPTS, should they be 
comma separated on the same line,  or should/can different lines
be used like:
  PCIC_OPTS="   "
  PCIC_OPTS="   "
  PCIC_OPTS="   "



**************************************************************************
*  SOME BACKGROUND
*    [ WHY I BELIVE I HAVE A CHANCE OF MAKING THIS WORK ]
*    [ WHAT I HAVE DONE SO FAR ]
*    [ A NOTE ABOUT THE VIA VT83C469 ]
**************************************************************************

[ WHY I BELIVE I HAVE A CHANCE OF MAKING THIS WORK ]
I believe that I have a chance in doing this (install and configure. . .) 
PCMCIA because 

1) PCMCIA card services 3.1.11  has the file PCMCIA-HOWTO 
   (Linux PCMCIA HOWTO v2.52 18 Feb 2000),  and in Section 1.4 
   is says that the VIA VT83C469 controller is recognized by the 
   supplied socket drivers.

2) PCMCIA card services 3.1.11  has the file SUPPORTED.CARDS 
   (Linux PCMCIA Supported Device List  2000 02 18  01:24:13)
   which lists (as a supported device):

     Fast Ethernet (10/100baseT) 
       Linksys PCMPC100 EtherFast, PCM100H1 HomeLink 10/100
       (guess that's two different Linksys cards)
 

[ WHAT I HAVE DONE SO FAR ]
So far,  I have done the following:

1) Installed Redhat Linux 6.0 onto a PC using the
   AMD K6-2 450 MHz processor.
2) Installed an Ethernet card which has the 
   Pcnet(tm)-FAST+  AMD  Am79C972  Eth controller.
3) Installed an Eth/HPNA card which has the 
   PCnet(tm)-Home  AMD  Am79C978  controller.

   (the PCI Eth cards are working, so is the IP MASQ and ipchains stuff)

4) Physically installed the Linksys internal PCMCIA reader writer

5) Physically plugged a Linksys PCM100H1 PCMCIA card into the reader writer

6) Downloaded source and built objects for PCMCIA
   (I have listings of the build process if anyone want to see them)
   - download pcmcia-cs-3.1.11.tar.gz   to /usr/src
   - gunzip -d pcmcia-cs-3.1.11.tar.gz
   - tar -xvf pcmcia-cs-3.1.11.tar
     ( So now the PCMCIA sources exist in /usr/src/pcmcia-cs.3.1.11 )

   - from /usr/src/pocmcia-cs-3.1.11
       make config   (enter)
       ...
       Configuration successful

       make all      (enter)
       (looks like it went ok)

       make install  (enter)
       (looks like it went ok)


7) Changed /etc/sysconfig/pcmcia

   PCMCIA="Yes"
   PCIC="i82365"
   PCIC_OPTS="extra_sockets=1"
   CORE_OPTS=



[ A NOTE ABOUT THE VIA VT83C469 ]
In the VT83C469 PCMCIA Socket Controller Data Sheet,
it says "Register - compatible with INTEL 82365SL"

So,  I thing that I did the correct thing in /etc/sysconfig/pcmcia
in entering  PCIC="i82365" 



**************************************************************************
*  COMMAND OUTPUT  &  FILE LISTINGS  &  DIRECTORY LISTINGS
*    
*   [ Command output: probe -v ]
*   [ Command output: probe -m ]
*   [ Command output: lsmod ]
*
*   [ File listing: /proc/modules ]
*   [ File listing: /proc/ioports ]
*   [ File listing: /proc/devices ]
*   [ File listing: /proc/interrupts ]
*   [ File listing: /etc/pcmcia/config ]
*   [ File listing: /etc/pcmcia/config.opts ]
*
*   [ File listing: /var/log/messages ]
*
*   [ Dir listing: /lib/modules/pcmcia,  using ls -lF ]
*
**************************************************************************

[ Command output: probe -v ]
PCI bridge probe: not found
Intel PCIC probe:
  ident(0)=0xff
  not found.
Databook TCID-2 probe: not found


[ Command output: probe -m ]
(There is no output from this command).


[ Command output: lsmod ]
Module                  Size  Used by
nfsd                  150936   8  (autoclean)
lockd                  30856   1  (autoclean) [nfsd]
sunrpc                 52356   1  (autoclean) [nfsd lockd]
pcmcia_core            42624   0 
pcnet32                 7784   1  (autoclean)
pcnethme               15152   1  (autoclean)


[ File listing: /proc/modules ]
nfsd                  150936   8 (autoclean)
lockd                  30856   1 (autoclean) [nfsd]
sunrpc                 52356   1 (autoclean) [nfsd lockd]
pcmcia_core            42624   0
pcnet32                 7784   1 (autoclean)
pcnethme               15152   1 (autoclean)


[ File listing: /proc/ioports ]
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
e000-e007 : ide0
e008-e00f : ide1
e800-e81f : PCnet/Home 79C978
ec00-ec17 : PCnet/FAST+ 79C972


[ File listing: /proc/devices ]
Character devices:
  1 mem
  2 pty
  3 ttyp
  4 ttyS
  5 cua
  7 vcs
 10 misc
 29 fb
 36 netlink
128 ptm
136 pts

Block devices:
  1 ramdisk
  2 fd
  3 ide0
  9 md
 22 ide1


[ File listing: /proc/interrupts ]
CPU0       
  0:     294018          XT-PIC  timer
  1:       4023          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  5:         31          XT-PIC  PCnet/Home 79C978
  8:          2          XT-PIC  rtc
 10:      60107          XT-PIC  PCnet/FAST+ 79C972
 12:      26798          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:      90483          XT-PIC  ide0
 15:          7          XT-PIC  ide1
NMI:          0



[ File listing: /etc/pcmcia/config ]
#
# PCMCIA Card Configuration Database
#
# config 1.111 2000/02/11 04:43:10 (David Hinds)
#

# config.opts is now included at the very end

#
# Device driver definitions
#
device "3c589_cs"
  class "network" module "3c589_cs"

device "ibmtr_cs"
  class "network" module "ibmtr_cs"

device "nmclan_cs"
  class "network" module "nmclan_cs"

device "oti12_cs"
  class "cdrom" module "oti12_cs"

device "pcnet_cs"
  class "network" module "net/8390", "pcnet_cs"

device "smc91c92_cs"
  class "network" module "smc91c92_cs"

device "wavelan_cs"
  class "network" module "wavelan_cs"

device "wvlan_cs"
  class "network" module "wvlan_cs"

device "memory_cs" needs_mtd
  class "memory" module "memory_cs"

device "ftl_cs" needs_mtd
  class "ftl" module "ftl_cs"

device "serial_cs"
  class "serial" module "serial_cs"

device "parport_cs"
  class "parport" module "parport_cs"

device "qlogic_cs"
  class "scsi" module "qlogic_cs"

device "aha152x_cs"
  class "scsi" module "aha152x_cs"

device "fdomain_cs"
  class "scsi" module "fdomain_cs"

device "sym53c500_cs"
  class "scsi" module "sym53c500_cs"

device "ide_cs"
  class "ide" module "ide_cs"

device "fmvj18x_cs"
  class "network" module "fmvj18x_cs" 

device "netwave_cs"
  class "network" module "netwave_cs"

device "xirc2ps_cs"
  class "network" module "xirc2ps_cs"

device "iscc_cs"
  class "iscc" module "iscc_cs"

device "3c574_cs"
  class "network" module "3c574_cs"

device "teles_cs"
  class "teles" module "teles_cs"

device "3c575_cb"
  class "network" module "cb_enabler", "3c575_cb"

device "apa1480_cb"
  class "scsi" module "cb_enabler", "apa1480_cb"

device "tulip_cb"
  class "network" module "cb_enabler", "tulip_cb"

device "memory_cb"
  class "memory" module "cb_enabler", "memory_cb"

device "epic_cb"
  class "network" module "cb_enabler", "epic_cb"

device "serial_cb"
  class "serial" module "cb_enabler", "serial_cb"

device "ray_cs"
  class "network" module "ray_cs"

device "airo_cs"
  class "network" module "airo", "airo_cs"
#
# Ethernet adapter definitions
#
card "2412LAN Ethernet"
  version "2412LAN"
  bind "pcnet_cs"

card "3Com 589 Ethernet"
  manfid 0x0101, 0x0589
  bind "3c589_cs"

card "Accton EN2212 Ethernet"
  version "ACCTON", "EN2212"
  bind "pcnet_cs"

card "Accton EN2216 Ethernet"
  version "ACCTON", "EN2216-PCMCIA-ETHERNET"
  bind "pcnet_cs"

card "Accton UE2212 Ethernet"
  version "PCMCIA", "UE2212"
  bind "pcnet_cs"

card "Accton UE2216 Ethernet"
  version "PCMCIA", "PCMCIA-ETHERNET-CARD", "UE2216"
  bind "pcnet_cs"

card "Allied Telesis LA-PCM Ethernet"
  manfid 0xc00f, 0x0002
  cis "cis/LA-PCM.dat"
  bind "pcnet_cs"

card "AmbiCom AMB8002 Ethernet"
  version "AmbiCom Inc", "AMB8002"
  bind "pcnet_cs"

card "AmbiCom AMB8002T Ethernet"
  version "AmbiCom Inc", "AMB8002T"
  bind "pcnet_cs"

card "AmbiCom AMB8010 Ethernet"
  version "AmbiCom Inc", "AMB8010"
  bind "pcnet_cs"

card "AnyCom ECO Ethernet"
  version "AnyCom", "ECO Ethernet"
  bind "pcnet_cs"

card "Argosy EN210 Ethernet"
  version "PCMCIA LAN", "Ethernet"
  bind "pcnet_cs"

card "Asante FriendlyNet Ethernet"
  version "ASANTE", "FriendlyNet PC Card"
  bind "pcnet_cs"

card "Billionton LNT-10TB"
  version "Billionton", "LNT-10TB"
  bind "pcnet_cs"

card "Billionton LNT-10TN"
  version "PCMCIA", "LNT-10TN"
  bind "pcnet_cs"

card "California Access Ethernet"
  version "PCMCIAs", "ComboCard"
  bind "pcnet_cs"

card "CeLAN Ethernet"
  version "PCMCIA", "ETHERNET V1.0"
  bind "pcnet_cs"

card "CentreCOM LA-PCM V2 Ethernet"
  version "Allied Telesis, K.K.", "CentreCOM LA-PCM_V2"
  bind "pcnet_cs"

card "CNet CN30BC Ethernet"
  version "CNet  ", "CN30BC", "ETHERNET"
  bind "pcnet_cs"

card "CNet CN40BC Ethernet"
  version "CNet", "CN40BC Ethernet"
  bind "pcnet_cs"

card "Compaq Ethernet"
  version "Compaq", "Ethernet LAN Card"
  bind "xirc2ps_cs"

card "Compaq Netelligent 10/100 Ethernet"
  version "Compaq", "Netelligent 10/100 PC Card"
  bind "xirc2ps_cs"

card "COMPU-SHACK BASEline Ethernet"
  version "COMPU-SHACK", "BASEline PCMCIA 10 MBit Ethernetadapter"
  bind "pcnet_cs"

card "Connectware LANdingGear Ethernet"
  manfid 0x0057, 0x1004
  bind "pcnet_cs"

card "CONTEC Ethernet"
  version "CONTEC Co.,Ltd."
  bind "fmvj18x_cs"

card "Corega PCC-T Ethernet"
  version "corega K.K.", "corega Ether PCC-T"
  bind "pcnet_cs"

card "Corega PCC-T Ethernet"
  version "corega,K.K.", "Ethernet LAN Card"
  bind "pcnet_cs"

card "Corega PCM-T Ethernet"
  version "Corega,K.K.", "Ethernet LAN Card"
  bind "pcnet_cs"

card "CyQ've 10baseT Ethernet"
  version "CyQ've 10 Base-T LAN CARD"
  bind "pcnet_cs"

card "CyQ've ELA-010 Ethernet"
  version "CyQ've", "ELA-010"
  bind "pcnet_cs"

card "Danpex EN-6200P2 Ethernet"
  version "*", "EN-6200P2"
  bind "pcnet_cs"

card "DataTrek NetCard Ethernet"
  version "DataTrek.", "NetCard "
  bind "pcnet_cs"

card "Dayna Commnunications CommuniCard E Ethernet"
  version "Dayna Communications, Inc.", "CommuniCard E"
  bind "pcnet_cs"

card "Digital DEPCM-BA Ethernet"
  version "DIGITAL", "DEPCM-XX"
  bind "pcnet_cs"

card "Digital PCP78-AC Ethernet"
  version "Digital", "Ethernet", "Adapter"
  bind "pcnet_cs"

card "D-Link DE-650 Ethernet"
  version "D-Link", "DE-650"
  bind "pcnet_cs"

card "D-Link DFE-650 Ethernet"
  version "D-Link", "DFE-650"
  bind "pcnet_cs"

card "D-Link DE-660 Ethernet"
  version "D-Link", "DE-660"
  bind "pcnet_cs"

card "D-Link DE-650 Ethernet"
  tuple 0x40, 0x0009, "D-Link PC Ethernet Card"
  bind "pcnet_cs"

card "DynaLink L10C Ethernet"
  version "DYNALINK", "L10C"
  bind "pcnet_cs"

card "E2000 NE2000-Compatible Ethernet"
  version "Ethernet Adapter", "E2000 PCMCIA Ethernet"
  bind "pcnet_cs"

card "Eagle NE200 Ethernet"
  manfid 0x0004, 0x0004
  bind "fmvj18x_cs"

card "Edimax Ethernet Combo"
  version "Edimax Technology Inc.", "PCMCIA", "Ethernet Card"
  bind "pcnet_cs"

card "EFA 207 Ethernet"
  version "EFA   ", "EFA207", "ETHERNET"
  bind "pcnet_cs"

card "Eiger Labs EPX-ET10T2 Ethernet"
  version "EIGER Labs Inc.", "Ethernet Combo card"
  bind "pcnet_cs"

card "Eiger Labs EPX-ET10BT Ethernet"
  version "EIGER Labs Inc.", "Ethernet 10BaseT card"
  bind "pcnet_cs"

card "Eiger Labs EPX-10BT Ethernet"
  version "Eiger Labs,Inc", "EPX-10BT PC Card Ethernet 10BT"
  bind "fmvj18x_cs"

card "Eiger Labs EPX-ET 10BT Ethernet"
  version "Eiger labs,Inc.", "EPX-10BT PC Card Ethernet 10BT"
  bind "fmvj18x_cs"

card "ELECOM Laneed LD-CDF"
  version "Laneed", "LD-CDF"
  bind "pcnet_cs"

card "EZLink 4109 Ethernet"
  version "PCMCIA", "Ethernet Card"
  bind "pcnet_cs"

card "EP-210 Ethernet"
  version "Ethernet PCMCIA adapter", "EP-210"
  bind "pcnet_cs"

card "EP-210 Ethernet"
  version "EP-210 PCMCIA LAN CARD."
  bind "pcnet_cs"

card "EP-220 Ethernet"
  version "PCMCIA", "ETHERNET"
  bind "pcnet_cs"

card "Epson EEN10B Ethernet"
  version "Seiko Epson Corp.", "Ethernet"
  bind "pcnet_cs"

card "Farallon ENet"
  version "Farallon", "ENet"
  bind "3c589_cs"

card "Fujitsu FMV-J181 Ethernet"
  version "PCMCIA MBH10302"
  bind "fmvj18x_cs"

card "Fujitsu FMV-1080 Ethernet"
  version "FUJITSU", "MBH10308"
  bind "fmvj18x_cs"

card "Fujitsu FMV-J182 Ethernet"
  version "FUJITSU", "LAN Card(FMV-J182)"
  bind "fmvj18x_cs"

card "Fujitsu Towa LA501 Ethernet"
  version "FUJITSU TOWA", "LA501"
  bind "fmvj18x_cs"

card "Grey Cell GCS2000 Ethernet"
  version "Grey Cell", "GCS2000"
  bind "pcnet_cs"

card "Grey Cell GCS2220 Ethernet"
  version "Grey Cell", "GCS2220"
  bind "pcnet_cs"

card "GVC NIC-2000P Ethernet"
  version "GVC", "NIC-2000p"
  bind "pcnet_cs"

card "GVC NIC-2000P Ethernet"
  version "PCMCIA", "Ethernet Combo card"
  bind "pcnet_cs"

card "Hitachi HT-4840-11 Ethernet"
  version "HITACHI", "HT-4840-11"
  bind "fmvj18x_cs"

card "Hypertec EP401 Ethernet"
  version "Hypertec", "*", "EP401"
  bind "pcnet_cs"

card "IBM Credit Card Ethernet"
  version "IBM Corp.", "Ethernet"
  bind "pcnet_cs"

card "IC-Card Ethernet"
  version "IC-CARD", "IC-CARD"
  bind "pcnet_cs"

card "IC-Card Plus Ethernet"
  version "IC-CARD+", "IC-CARD+"
  bind "pcnet_cs"

card "Kansai KLA-PCM/T Ethernet"
  version "KANSAI ELECTRIC CO.,LTD", "KLA-PCM/T"
  bind "pcnet_cs"

card "Katron PE-520 Ethernet"
  version "KCI", "PE520 PCMCIA Ethernet Adapter"
  bind "pcnet_cs"

card "KingMax Technology Ethernet"
  version "KingMax Technology Inc.", "EN10-T2", "PCMCIA Ethernet Card"
  bind "pcnet_cs"

card "KingMax Technology Ethernet"
  version "KingMax Technology Inc.", "*", "Ethernet Card"
  bind "pcnet_cs"

card "KingMax Technology Ethernet"
  version "KINGMAX", "EN10T2T"
  bind "pcnet_cs"

card "Kingston KNE-PCM/x Ethernet"
  version "Kingston Technology Corp.", "EtheRx PC Card Ethernet Adapter"
  bind "pcnet_cs"

card "Kingston KNE-PC2 Ethernet"
  version "Kingston", "KNE-PC2"
  bind "pcnet_cs"

card "KTI PE-520 Plus Ethernet"
  version "KTI", "PE520 PLUS"
  cis "cis/PE520.dat"
  bind "pcnet_cs"

card "Linksys Ethernet"
  tuple 0x40, 0x0009, "E-CARD PC Ethernet Card"
  cis "cis/E-CARD.dat"
  bind "pcnet_cs"

card "Linksys Ethernet"
  version "LINKSYS", "E-CARD"
  bind "pcnet_cs"

card "Linksys Ethernet"
  version "E-CARD", "E-CARD"
  bind "pcnet_cs"

card "Linksys Ethernet"
  version "Linksys", "Combo PCMCIA EthernetCard (EC2T)"
  bind "pcnet_cs"

card "Longshine ShineNet LCS-8534 Ethernet"
  version "LONGSHINE", "PCMCIA Ethernet Card"
  bind "pcnet_cs"

card "Longshine ShineNet LCS-8534 Ethernet"
  version "LONGSHINE", "*", "EP401"
  bind "pcnet_cs"

card "Logitec LPM-LN10BA Ethernet"
  version "Cardwell", "PCMCIA", "ETHERNET"
  bind "pcnet_cs"

card "Logitec LPM-LN20T Ethernet"
  version "Logitec", "LPM-LN20T"
  bind "pcnet_cs"

card "MACNICA Ethernet"
  version "MACNICA", "ME1-JEIDA"
  bind "pcnet_cs"

card "Maxtech PCN2000 Ethernet"
  version "MAXTECH", "PCN2000"
  bind "pcnet_cs"

card "Megahertz CC10BT/2 Ethernet"
  version "Megahertz", "CC10BT/2"
  bind "smc91c92_cs"

card "Melco LPC2-T Ethernet"
  manfid 0x01bf, 0x2216
  bind "pcnet_cs"

card "Microdyne NE4200 Ethernet"
  version "Microdyne", "NE4200"
  bind "pcnet_cs"

card "Midori LT-PCMT Ethernet"
  version "MIDORI ELEC.", "LT-PCMT"
  bind "pcnet_cs"

card "National Semiconductor InfoMover 4100 Ethernet"
  version "National Semiconductor", "InfoMover 4100"
  bind "pcnet_cs"

card "National Semiconductor InfoMover NE4100 Ethernet"
  version "National Semiconductor", "InfoMover NE4100"
  bind "pcnet_cs"

card "NEC PC-9801N-J12 Ethernet"
  version "NEC", "PC-9801N-J12"
  bind "pcnet_cs"

card "New Media Ethernet"
  version "New Media Corporation", "Ethernet"
  bind "nmclan_cs"

card "New Media BASICS Ethernet"
  version "BASICS by New Media Corporation", "Ethernet", "SMC91C94"
  bind "smc91c92_cs"

card "New Media LanSurfer"
  manfid 0x0057, 0x0021
  bind "pcnet_cs"

card "NextCom NC5310 Ethernet"
  version "NextComK.K.", "NC5310 Ver1.0        "
  bind "fmvj18x_cs"

card "NE2000 Compatible Ethernet"
  version "PCMCIA", "Ethernet"
  bind "pcnet_cs"

card "NE2000 Compatible Ethernet"
  version "PCMCIA", "Ethernet 10BaseT Card"
  bind "pcnet_cs"

card "NE2000 Compatible Ethernet"
  version "NE2000 Compatible", "PCMCIA", "Ethernet Card"
  bind "pcnet_cs"

card "NE2000 Compatible Ethernet"
  version "Ethernet", "Adapter"
  bind "pcnet_cs"

card "NE2000 Compatible Ethernet"
  manfid 0x0149, 0xc1ab
  bind "pcnet_cs"

card "NDC Instant-Link Ethernet"
  version "NDC", "Ethernet"
  cis "cis/NE2K.dat"
  bind "pcnet_cs"

card "Novell Eagle 200T Ethernet"
  version "EAGLE Technology", "NE200 ETHERNET LAN MBH10302 04"
  bind "fmvj18x_cs"

card "Ositech Four of Diamonds Ethernet"
  version "Ositech", "Trumpcard:Four of Diamonds Ethernet"
  bind "smc91c92_cs"

card "IO DATA PCLA/T Ethernet"
  version "I-O DATA", "PCLA", "ETHERNET"
  bind "pcnet_cs"

card "IO DATA PCLA/TE Ethernet"
  version "IO DATA", "PCLATE", "ETHERNET"
  bind "pcnet_cs"

card "Panasonic CF-VEL211 Ethernet"
  version "Matsushita Electric Industrial Co.,LTD.", "CF-VEL211"
  bind "pcnet_cs"

card "PreMax PE-200 Ethernet"
  version "PMX   ", "PE-200"
  cis "cis/PE-200.dat"
  bind "pcnet_cs"

card "Psion Gold Card Ethernet"
  version "Psion Dacom", "Gold Card Ethernet"
  bind "pcnet_cs"

card "RATOC Ethernet"
  version "PCMCIA LAN MBH10304  ES"
  bind "fmvj18x_cs"

card "RATOC REX-R280 Ethernet"
  version "RATOC System Inc.", "10BASE_T CARD R280"
  bind "fmvj18x_cs"

card "Relia RE2408T Ethernet"
  version "PCMCIA LAN", "Ethernet"
  bind "pcnet_cs"

card "Reliasys 2400A Ethernet"
  version "=RELIA==", "Ethernet"
  bind "pcnet_cs"

card "RPTI EP400 Ethernet"
  version "RPTI LTD.", "EP400"
  bind "pcnet_cs"

card "RPTI EP400 Ethernet"
  version "RPTI", "EP400 Ethernet NE2000 Compatible"
  bind "pcnet_cs"

card "RPTI EP401 Ethernet"
  version "RPTI", "EP401 Ethernet NE2000 Compatible"
  bind "pcnet_cs"

card "RPTI 1625B Ethernet"
  version "RP", "1625B Ethernet NE2000 Compatible"
  bind "pcnet_cs"

card "SCM Ethernet Combo"
  version "SCM", "Ethernet Combo card"
  bind "pcnet_cs"

card "Sky Link Express"
  version "2408LAN", "Ethernet"
  bind "pcnet_cs"

card "SMC EtherEZ Ethernet"
  version "SMC", "EtherEZ Ethernet 8020"
  bind "smc91c92_cs"

card "SMC EZCard-10 Ethernet"
  version "SMC", "EZCard-10-PCMCIA"
  bind "pcnet_cs"

card "Socket EA Ethernet"
  version "Socket Communications Inc",
    "Socket EA PCMCIA LAN Adapter Revision D"
  bind "pcnet_cs"

card "Socket EA Ethernet"
  version "Socket Communications Inc",
    "Socket EA PCMCIA LAN Adapter Revision E"
  bind "pcnet_cs"

card "Socket LP-E Ethernet"
  manfid 0x0104, 0x000d
  bind "pcnet_cs"

card "Socket LP-E CF+ Ethernet"
  manfid 0x0104, 0x0075
  bind "pcnet_cs"

card "SuperSocket Ethernet"
  version "Telecom Device K.K.", "SuperSocket RE450T"
  bind "pcnet_cs"

card "Surecom Ethernet"
  version "TAMARACK", "Ethernet"
  bind "pcnet_cs"

card "TDK LAC-CD02x Ethernet"
  version "TDK", "LAC-CD02x"
  bind "fmvj18x_cs"

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

card "Xircom RE-10 Ethernet"
  version "Xircom", "*", "RE-10"
  bind "xirc2ps_cs"

#
# 10/100baseT network adapters
#
card "3Com 572/574 Fast Ethernet"
  manfid 0x0101, 0x0574
  bind "3c574_cs"

card "Abocom LinkMate FE1000 Fast Ethernet"
  version "Fast Ethernet", "Adapter"
  bind "pcnet_cs"

card "Accton Fast EtherCard-16"
  manfid 0x01bf, 0x010a
  bind "xirc2ps_cs"

card "AnyCom ECO 10/100 Fast Ethernet"
  version "AnyCom", "ECO Ethernet 10/100"
  bind "pcnet_cs"

card "Argosy EN220 Fast Ethernet"
  version "ARGOSY", "Fast Ethernet PCCard"
  bind "smc91c92_cs"

card "COMPU-SHACK FASTline 10/100 Fast Ethernet"
  version "COMPU-SHACK", "FASTline PCMCIA 10/100 Fast-Ethernet"
  bind "pcnet_cs"

card "Corega PCC-TX Fast Ethernet"
  version "corega K.K.", "corega FastEther PCC-TX"
  bind "pcnet_cs"

card "D-Link Fast Ethernet"
  version "ETHER-C16"
  bind "pcnet_cs"

card "Dynalink L100C Fast Ethernet"
  version "DYNALINK", "L100C"
  bind "smc91c92_cs"

card "Farallon Enet"
  version "Farallon", "Farallon Enet"
  bind "smc91c92_cs"

card "Intel EtherExpress PRO/100"
  version "Intel", "EtherExpress(TM) PRO/100 PC Card Mobile Adapter16"
  bind "xirc2ps_cs"

card "IO DATA PCET/TX Fast Ethernet"
  version "IO DATA", "PCETTX"
  bind "pcnet_cs"

card "KTI ETHER-C16 Fast ethernet"
  manfid 0x0149, 0x0230
  bind "pcnet_cs"

card "Laneed LD-10/100CD Fast Ethernet"
  version "Laneed", "LD-10/100CD"
  bind "pcnet_cs"

card "Linksys EtherFast 10/100 Fast Ethernet"
  version "Linksys", "EtherFast 10/100 PC Card (PCMPC100)"
  bind "pcnet_cs"

card "Logitec LPM-LN100TX Fast Ethernet"
  version "Logitec", "LPM-LN100TX"
  bind "pcnet_cs"

card "Melco LPC2-TX Fast Ethernet"
  version "MELCO", "LPC2-TX"
  bind "pcnet_cs"

card "Melco/SMC LPC-TX Fast Ethernet"
  version "MELCO/SMC", "LPC-TX"
  bind "smc91c92_cs"

card "Microcom C.E. Travel Card 10/100 Fast Ethernet"
  version "Microcom C.E.", "Travel Card LAN 10/100"
  bind "pcnet_cs"

card "NetGear FA410TXC Fast Ethernet"
  version "NETGEAR", "FA410TX"
  bind "pcnet_cs"

card "Ositech Seven of Diamonds Fast Ethernet"
  version "Ositech", "Trumpcard:Seven of Diamonds Ethernet"
  bind "smc91c92_cs"

card "NE2000 Compatible Fast Ethernet"
  version "PCMCIA", "10/100 Ethernet Card"
  bind "pcnet_cs"

card "NE2000 Compatible Fast Ethernet"
  version "PCMCIA", "FAST ETHERNET CARD"
  bind "pcnet_cs"

card "Planex FNW-3600T Fast Ethernet"
  version "Fast Ethernet", "Adapter"
  bind "pcnet_cs"

card "Toshiba Advanced Network Fast Ethernet"
  version "Toshiba Information Systems", "*", "TPCENET"
  bind "xirc2ps_cs"

card "Toshiba 10/100 Fast Ethernet"
  version "Toshiba", "10/100 Ethernet PC Card"
  bind "xirc2ps_cs"

#Conflicts with Kingston KNE-PC2!
#card "WiseCom WC-PC400 Fast Ethernet"
#  manfid 0x0186, 0x0100
#  bind "smc91c92_cs"

card "Xircom CE3-10/100 Fast Ethernet"
  version "Xircom", "*", "CE3-10/100"
  bind "xirc2ps_cs"

#
# Wireless network adapters
#
card "Aironet PC4500"
  manfid 0x015f, 0x0005
  bind "airo_cs"

card "Aironet PC4800"
  manfid 0x015f, 0x0007
  bind "airo_cs"

card "AT&T WaveLAN Adapter"
  version "AT&T", "WaveLAN/PCMCIA"
  bind "wavelan_cs"

card "Cabletron RoamAbout 802.11 DS"
  version "Cabletron", "RoamAbout 802.11 DS"
  bind "wvlan_cs"

card "Digital RoamAbout/DS"
  version "Digital", "RoamAbout/DS"
  bind "wavelan_cs"

card "Lucent Technologies WaveLAN Adapter"
  version "Lucent Technologies", "WaveLAN/PCMCIA"
  bind "wavelan_cs"

card "Lucent Technologies WaveLAN/IEEE Adapter"
  version "Lucent Technologies", "WaveLAN/IEEE"
  bind "wvlan_cs"

card "Melco WLI-PCM-L11"
  manfid 0x0156, 0x0002
  bind "wvlan_cs"

card "NCR WaveLAN Adapter"
  version "NCR", "WaveLAN/PCMCIA"
  bind "wavelan_cs"

card "NCR WaveLAN/IEEE Adapter"
  version "NCR", "WaveLAN/IEEE"
  bind "wvlan_cs"

card "RayLink PC Card WLAN Adapter"
  manfid 0x01a6, 0x0000
  bind "ray_cs"

card "Xircom CreditCard Netwave"
  version "Xircom", "CreditCard Netwave"
  bind "netwave_cs"

#
# Modems and other serial devices
#
# NOTE: most modems do not need explicit entries here, because they
# are correctly identified using the following generic entry.
#
card "Serial or Modem"
  function serial_port
  bind "serial_cs"

card "Angia Fax/Modem"
  version "Intelligent", "ANGIA FAX/MODEM"
  bind "serial_cs"

card "Cirrus Logic 14.4K Fax Modem"
  version "CIRRUS LOGIC", "FAX MODEM"
  bind "serial_cs"

card "Compaq 28.8K Modem"
  version "COMPAQ", "PCMCIA 28800 FAX/DATA MODEM"
  bind "serial_cs"

card "Compaq 33.6K Modem"
  version "COMPAQ", "PCMCIA 33600 FAX/DATA MODEM"
  bind "serial_cs"

card "Dr. Neuhaus 14.4K FURY Card"
  version "Dr. Neuhaus", "FURY CARD 14K4"
  bind "serial_cs"

card "E.TECH Bullet 33.6K Modem"
  version "PCMCIA   ", "C336MX     "
  bind "serial_cs"

card "Gateway 2000 TelePath Fax Modem"
  version "GATEWAY2000", "CC3144", "*", "PCMCIA MODEM"
  bind "serial_cs"

card "Intel-compatible Modem"
  version "Intel", "MODEM 2400+"
  bind "serial_cs"

card "Macronix Fax/Modem"
  version "MACRONIX", "FAX/MODEM"
  bind "serial_cs"

card "Megahertz PCMCIA Modem"
  version "MEGAHERTZ", "*", "*", "PCMCIA MODEM"
  bind "serial_cs"

card "Megahertz V.34 Modem"
  version "MEGAHERTZ", "*", "V.34 PCMCIA MODEM"
  bind "serial_cs"

card "MultiTech MultiModem"
  version "Multi-Tech", "MT1432LT"
  bind "serial_cs"

card "MultiTech V.34 Modem"
  version "Multi-Tech", "MT2834LT"
  bind "serial_cs"

card "MultiTech MT5634ZLX"
  version "MultiTech", "PCMCIA 56K DataFax"
  cis "cis/MT5634ZLX.dat"
  bind "serial_cs"

card "Toshiba T144PF Modem"
  version "TOSHIBA", "T144PF", "*", "PCMCIA MODEM"
  bind "serial_cs"

card "Advantech COMpad-32/85"
  version "ADVANTECH", "COMpad-32/85", "1.0"
  cis "cis/COMpad.dat"
  bind "serial_cs"

card "Advantech COMpad-32/85"
  version "ADV", "*", "TECH", "COMpad-32/85"
  bind "serial_cs"

card "Argosy Dual Serial I/O"
  version "*", "RS-COM 2P"
  cis "cis/RS-COM-2P.dat"
  bind "serial_cs"

card "Computerboards PCM-COM422"
  version "Computerboards, Inc.", "PCM-COM422"
  bind "serial_cs"

card "Fujitsu FMV-JMD711"
  version "FUJITSU", "FC14F ", "MBH10213"
  bind "serial_cs"

card "IOTech Dual RS-232"
  version "IOTech Inc ", "PCMCIA Dual RS-232 Serial Port Card"
  bind "serial_cs"

card "National Instruments PCMCIA-232"
  manfid 0x10b, 0x0d50
  bind "serial_cs"

card "National Instruments PCMCIA-232/2"
  manfid 0x10b, 0x0d51
  bind "serial_cs"

card "National Instruments PCMCIA-485"
  manfid 0x10b, 0x0d52
  bind "serial_cs"

card "National Instruments PCMCIA-485/2"
  manfid 0x10b, 0x0d53
  bind "serial_cs"

card "National Instruments PCMCIA-232/4"
  manfid 0x10b, 0xd180
  bind "serial_cs"

card "Omega Engineering QSP-100"
  manfid 0x0137, 0x0025
  bind "serial_cs"

card "Quatech Dual RS-232"
  version "Quatech Inc", "PCMCIA Dual RS-232 Serial Port Card"
  bind "serial_cs"

card "Quatech Quad RS-232"
  manfid 0x0137, 0x001b
  bind "serial_cs"

card "Silicom 2S100 Dual Serial"
  manfid 0x0089, 0x0301
  bind "serial_cs"

card "Socket Communications Dual RS-232"
  manfid 0x0104, 0x0006
  bind "serial_cs"

#
# Memory cards
#
card "Anonymous Memory"
  anonymous
  bind "memory_cs"

card "Memory Card"
  function memory_card
  bind "memory_cs"

card "IBM 2MB SRAM"
  version "IBM", "2MB SRAM"
  bind "memory_cs"

card "IBM 4MB Series 1 Flash"
  version "IBM", "4MB FLASH"
  bind "memory_cs", "ftl_cs"

card "IBM 8MB Series 2 Flash"
  version "IBM", "8MB FLASH"
  bind "memory_cs", "ftl_cs"

card "Intel Series 2 2MB Flash"
  version "intel", "SERIES2-02 "
  bind "memory_cs", "ftl_cs"

card "Intel Series 2 4MB Flash"
  version "intel", "SERIES2-04 "
  bind "memory_cs", "ftl_cs"

card "Intel Series 2 20MB Flash"
  version "intel", "SERIES2-20 "
  bind "memory_cs", "ftl_cs"

card "Intel Series 2+ 8MB Flash"
  version "Intel", "S2E8 SW"
  bind "memory_cs", "ftl_cs"

card "Intel Series 2+ 20MB Flash"
  version "Intel", "S2E20SW"
  bind "memory_cs", "ftl_cs"

card "Intel Series 100 Flash"
  version "intel", "VALUE SERIES 100 "
  bind "memory_cs", "ftl_cs"

card "IO DATA 2MB SRAM"
  version "IO DATA", "PCS-2M", "2MB SRAM"
  bind "memory_cs"

card "Maxtor MobileMax Flash"
  version "Maxtor", "MAXFL MobileMax Flash Memory Card"
  bind "memory_cs", "ftl_cs"

card "Seiko/Epson WWB101EN20"
  version "SEIKO EPSON", "WWB101EN20"
  bind "memory_cs"

card "Seiko/Epson WWB513EN20"
  version "SEIKO EPSON", "WWB513EN20"
  bind "memory_cs"

card "Franklink/Rolodex REX-3000"
  version "Starfish, Inc.", "REX-3000"
  bind "memory_cs"

card "Franklink/Rolodex REX-4100"
  version "Starfish, Inc.", "REX-4100"
  bind "memory_cs"

card "RATOC SmartMedia Adapter"
  version "RATOC Systems,Inc.", "SmartMedia ADAPTER PC Card"
  bind "memory_cs", "ftl_cs"

#
# Memory Technology Drivers
#
region "Generic or SRAM"
  default
  mtd "sram_mtd"

region "Intel Series 2 Flash"
  jedec 0x89 0xa2
  mtd "iflash2_mtd"

region "Intel Series 100 Flash"
  jedec 0x89 0xaa
  mtd "iflash2_mtd"

region "Intel Series 2+ Flash"
  jedec 0x89 0xa0
  mtd "iflash2+_mtd"

#
# Token Ring adapters
#
card "3Com TokenLink Velocity Adapter"
  version "3Com", "TokenLink Velocity PC Card"
  bind "ibmtr_cs"

card "IBM Token Ring Adapter"
  version "IBM", "TOKEN RING"
  bind "ibmtr_cs"

#
# SCSI host adapters
#
card "Adaptec APA-1460 SlimSCSI"
  version "Adaptec, Inc.", "APA-1460 SCSI Host Adapter"
  bind "aha152x_cs"

card "Eiger Labs SCSI"
  version "EIger Labs", "PCMCIA-to-SCSI Adapter"
  bind "qlogic_cs"

card "Epson SC200 SCSI"
  version "EPSON", "SCSI-2 PC Card SC200"
  bind "qlogic_cs"
  
card "IBM SCSI"
  version "IBM Corp.", "SCSI PCMCIA Card"
  bind "fdomain_cs"

card "IBM SCSI"
  version "SCSI PCMCIA Adapter Card"
  bind "fdomain_cs"

#card "MACNICA mPS100 SCSI"
#  version "MACNICA", "MIRACLE SCSI", "mPS100"
#  bind "qlogic_cs"

card "MACNICA mPS110 SCSI"
  version "MACNICA", "MIRACLE SCSI-II mPS110"
  bind "qlogic_cs"

card "Midori CN-SC43 SCSI"
  version "MIDORI ELECTRONICS ", "CN-SC43"
  bind "qlogic_cs"

card "NEC PC-9801N-J03R SCSI"
  version "NEC", "PC-9801N-J03R"
  bind "qlogic_cs"

card "New Media Bus Toaster SCSI"
  version "New Media", "SCSI", "Bus Toaster"
  bind "aha152x_cs"

card "New Media Toast & Jam Sound/SCSI"
  version "New Media Corporation", "Multimedia Sound/SCSI"
  bind "aha152x_cs"

card "Noteworthy Bus Toaster SCSI"
  version "NOTEWORTHY", "SCSI", "Bus Toaster"
  bind "aha152x_cs"

card "New Media BASICS SCSI"
  version "BASICS by New Media Corporation", "SCSI Sym53C500"
  bind "sym53c500_cs"

card "New Media Bus Toaster SCSI"
  version "New Media Corporation", "SCSI Bus Toaster Sym53C500"
  bind "sym53c500_cs"

card "Panasonic KXLC003"
  version "KME ", "KXLC003"
  bind "qlogic_cs"

card "Panasonic KXLC004"
  version "KME ", "KXLC004"
  bind "qlogic_cs"

card "Qlogic FastSCSI"
  version "QLOGIC CORPORATION", "pc05"
  bind "qlogic_cs"

card "Qlogic FastSCSI"
  version "QLOGIC CORPORATION", "pc05 rev 1.10"
  bind "qlogic_cs"

card "Raven CD-Note SCSI"
  version "KME", "KXLC002", "00"
  bind "qlogic_cs"

card "RATOC REX-9530 SCSI-2"
  version "RATOC System Inc.", "SCSI2 CARD 37"
  bind "qlogic_cs"

card "SIMA TECH SCSI9000"
  version "*", "SCSI9000"
  bind "sym53c500_cs"

card "Simple Technology SCSI"
  version " SIMPLE TECHNOLOGY Corporation",
    "SCSI PCMCIA Credit Card Controller"
  bind "fdomain_cs"

card "Toshiba SCSC200A SCSI"
  version "TOSHIBA", "SCSC200A PC CARD SCSI"
  bind "qlogic_cs"

card "Toshiba SCSC200B SCSI"
  version "TOSHIBA", "SCSC200B PC CARD SCSI-10"
  bind "qlogic_cs"

#
# Multifunction cards
#
card "3Com 3c562/3c563 Ethernet/Modem"
  manfid 0x0101, 0x0562
  bind "3c589_cs" to 0, "serial_cs" to 1

card "3Com/Megahertz 3CXEM556 Ethernet/Modem"
  manfid 0x0101, 0x0035
  cis "cis/3CXEM556.dat"
  bind "3c589_cs" to 0, "serial_cs" to 1

card "3Com/Megahertz 3CXEM556 B-INT Ethernet/Modem"
  manfid 0x0101, 0x003d
  cis "cis/3CXEM556.dat"
  bind "3c589_cs" to 0, "serial_cs" to 1

card "3Com/Megahertz 3CCFEM556 Ethernet/Modem"
  manfid 0x0101, 0x0556
  cis "cis/3CCFEM556.dat"
  bind "3c574_cs" to 0, "serial_cs" to 1

card "Accton EN2218 LAN/Modem"
  version "PCMCIA", "EN2218-LAN/MODEM"
  cis "cis/PCMLM28.dat"
  bind "pcnet_cs", "serial_cs"

card "Accton UE2218 LAN/Modem"
  version "PCMCIA", "UE2218-LAN/MODEM"
  cis "cis/PCMLM28.dat"
  bind "pcnet_cs", "serial_cs"

card "AnyCom Fast Ethernet/Modem"
  version "AnyCom", "Fast Ethernet + 56K COMBO"
  bind "pcnet_cs", "serial_cs"

card "Apex MultiCard Ethernet/Modem"
  version "APEX DATA", "MULTICARD", "ETHERNET-MODEM"
  bind "pcnet_cs" to 0, "serial_cs" to 1

card "Billionton LM5LT-10B Ethernet/Modem"
  manfid 0x021b, 0x0101
  bind "pcnet_cs", "serial_cs"

card "Compaq Microcom CPQ550 Ethernet/Modem"
  manfid 0x0138, 0x110a
  bind "xirc2ps_cs", "serial_cs"

card "Dayna Communicard Ethernet/Modem"
  version "DAYNA COMMUNICATIONS", "LAN AND MODEM MULTIFUNCTION"
  cis "cis/DP83903.dat"
  bind "pcnet_cs" to 0, "serial_cs" to 1

card "D-Link DME336T Ethernet/Modem"
  version "D-Link", "DME336T"
  bind "pcnet_cs", "serial_cs"

card "D-Link DMF560TX Ethernet/Modem"
  manfid 0x0143, 0xc0ab
  bind "pcnet_cs", "serial_cs"

card "Gateway Telepath Ethernet/Modem"
  version "Gateway 2000", "XJEM3336"
  bind "smc91c92_cs", "serial_cs"

card "Grey Cell GCS3400 Ethernet/Modem"
  version "Grey Cell", "GCS3000"
  bind "pcnet_cs", "serial_cs"

card "IBM Home and Away Ethernet/Modem"
  version "IBM", "Home and Away Credit Card Adapter"
  bind "pcnet_cs" to 0, "serial_cs" to 1

card "IBM Home and Away 28.8 Ethernet/Modem"
  version "IBM", "Home and Away 28.8 PC Card       "
  bind "pcnet_cs" to 0, "serial_cs" to 1

card "IBM w95 Home and Away Ethernet/Modem"
  version "IBM", "w95 Home and Away Credit Card "
  bind "pcnet_cs" to 0, "serial_cs" to 1

card "Intel EtherExpress PRO/100 LAN/Modem"
  manfid 0x0089, 0x110a
  bind "xirc2ps_cs", "serial_cs"

card "No-Name Ethernet/Modem"
  version "*", "FAX/Modem/Ethernet Combo Card "
  bind "pcnet_cs" to 0, "serial_cs" to 1

card "Linksys LANmodem 28.8"
  version "LINKSYS", "PCMLM28"
  cis "cis/PCMLM28.dat"
  bind "pcnet_cs", "serial_cs"

card "Linksys LANmodem 33.6"
  version "LINKSYS", "PCMLM336"
  bind "pcnet_cs", "serial_cs"

card "Linksys EtherFast LANmodem 56K"
  version "Linksys", "EtherFast 10&100 + 56K PC Card (PCMLM56)"
  bind "pcnet_cs", "serial_cs"

card "Megahertz CC/XJEM1144 Ethernet/Modem"
  version "MEGAHERTZ", "XJEM1144/CCEM1144", "PCMCIA MODEM"
  bind "smc91c92_cs", "serial_cs"

card "Megahertz CC/XJEM1144 Ethernet/Modem"
  version "MEGAHERTZ", "XJEM1144/CCEM1144"
  bind "smc91c92_cs", "serial_cs"

card "Megahertz EM1144T Ethernet/Modem"
  version "MEGAHERTZ", "EM1144T", "PCMCIA MODEM"
  bind "smc91c92_cs", "serial_cs"

card "Megahertz CC/XJEM3288 Ethernet/Modem"
  version "MEGAHERTZ", "CC/XJEM3288", "DATA/FAX/CELL ETHERNET MODEM"
  bind "smc91c92_cs", "serial_cs"

card "Megahertz CC/XJEM3336 Ethernet/Modem"
  version "MEGAHERTZ", "CC/XJEM3336", "DATA/FAX/CELL ETHERNET MODEM"
  bind "smc91c92_cs", "serial_cs"

card "Motorola Marquis Ethernet/Modem"
  version "Motorola MARQUIS"
  bind "3c589_cs" to 0, "serial_cs" to 1

card "Motorola Mariner Ethernet/Modem"
  manfid 0x0109, 0x0501
  bind "smc91c92_cs", "serial_cs"

card "NSC DP83903-based Ethernet/Modem"
  version "*", "*", "*", "NSC MF LAN/Modem"
  cis "cis/DP83903.dat"
  bind "pcnet_cs" to 0, "serial_cs" to 1

card "Ositech Jack of Diamonds Ethernet/Modem"
  version "Ositech", "Trumpcard:Jack of Diamonds Modem+Ethernet"
  bind "smc91c92_cs", "serial_cs"

card "Ositech Jack of Hearts Ethernet/Modem"
  version "Ositech", "Trumpcard:Jack of Hearts Modem+Ethernet"
  bind "smc91c92_cs", "serial_cs"

card "Ositech Jack of Hearts Ethernet/Modem"
  manfid 0x0140, 0x000a
  bind "smc91c92_cs", "serial_cs"

card "Psion Gold Card V34 Ethernet"
  version "Psion Dacom", "Gold Card V34 Ethernet"
  cis "cis/PCMLM28.dat"
  bind "pcnet_cs", "serial_cs"

card "Psion Gold Card V34 Ethernet"
  version "Psion Dacom", "Gold Card V34 Ethernet GSM"
  cis "cis/PCMLM28.dat"
  bind "pcnet_cs", "serial_cs"

card "Psion Gold Card Netglobal 56K+10Mb Ethernet"
  manfid 0x016c, 0x0020
  bind "smc91c92_cs" to 0, "serial_cs" to 1

card "Rover ComboCard Ethernet/Modem"
  version "PCMCIAs", "ComboCard"
  bind "pcnet_cs", "serial_cs"

card "TDK Global Networker Ethernet/Modem"
  version "TDK", "GlobalNetworker 3410/3412"
  bind "serial_cs"

card "TDK 3000/3400/5670 Fast Ethernet/Modem"
  manfid 0x0143, 0x3341
  bind "pcnet_cs", "serial_cs"

card "TDK DFL5610WS Ethernet/Modem"
  manfid 0x0105, 0xea15
  bind "pcnet_cs", "serial_cs"

card "Telecom Device SuperSocket LM336 Ethernet/Modem"
  version "PCMCIAs", "LanModem"
  bind "pcnet_cs", "serial_cs"

card "Xircom CE II Ethernet/Modem"
  version "Xircom", "CreditCard Ethernet+Modem II"
  bind "serial_cs"

card "Xircom CEM28 Ethernet/Modem"
  version "Xircom", "*", "CEM28"
  bind "xirc2ps_cs", "serial_cs"

card "Xircom CEM33 Ethernet/Modem"
  version "Xircom", "*", "CEM33"
  bind "xirc2ps_cs", "serial_cs"

card "Xircom CEM56 Ethernet/Modem"
  version "Xircom", "*", "CEM56"
  bind "xirc2ps_cs", "serial_cs"

card "Xircom RealPort REM10BT Ethernet/Modem"
  version "Xircom", "*", "REM10"
  bind "xirc2ps_cs", "serial_cs"

#
# ATA/IDE fixed disk devices
#
card "ATA/IDE Fixed Disk"
  function fixed_disk
  bind "ide_cs"

card "ACE DoubleFlash 20MB"
  version "IBM", "IBM17JSSFP20"
  bind "ide_cs"

card "Argosy EIDE CD-ROM"
  version "ARGOSY", "CD-ROM"
  bind "ide_cs"

card "Caravelle CD-36N/CD-36E CD-ROM"
  version "Caravelle", "PSC-IDE ", "PSC000"
  bind "ide_cs"

card "CNF CARDport CD-ROM"
  version "CNF CD-M", "CD-ROM"
  bind "ide_cs"

card "Creative Technology CD-ROM"
  version "Creative Technology Ltd.", "PCMCIA CD-ROM Interface Card"
  bind "ide_cs"

card "Digital Mobile Media CD-ROM"
  version "Digital Equipment Corporation.", "Digital Mobile Media CD-ROM"
  bind "ide_cs"

card "EXP CD940 CD-ROM"
  version "EXP   ", "CD-ROM"
  bind "ide_cs"

card "EXP Traveler 620 CD-ROM"
  version "EXP", "CD+GAME", "C1"
  bind "ide_cs"

card "Freecom IQ-drive"
  version "FREECOM", "PCCARD-IDE"
  bind "ide_cs"

card "Generic ATAPI CD-ROM"
  version "PCMCIA", "CD-ROM"
  bind "ide_cs"

card "IBM Max Portable CD-ROM"
  manfid 0x00a4, 0x002d
  bind "ide_cs"

card "IO DATA CDP-TX/PCIDE"
  version "IO DATA", "PCIDE"
  bind "ide_cs"

card "IO DATA PCIDE II"
  version "IO DATA", "PCIDEII"
  bind "ide_cs"

card "IO DATA CBIDE"
  version "WIT", "IDE16"
  bind "ide_cs"

card "MCD601p CD-ROM"
  version "CDROM", "IDE", "MCD-601p"
  bind "ide_cs"

card "Ninja ATA"
  version " ", "NinjaATA-"
  bind "ide_cs"

card "Simple Tech Compact Flash"
  version "STI Flash"
  bind "ide_cs"

#
# Non-ATA/IDE CD-ROM's
#
card "Innovative Communications CyberRom CD"
  version "Innovative Communications", "CyberRom CD"
  bind "oti12_cs"

#
# Miscellaneous card definitions
#
#card "Canon FDCard"
#  version "Canon Electronics INC.", "FDCard Ver. 1.00"
#
#card "New Media .WAVjammer"
#version "New Media Corporation", ".WAVjammer"

card "IBM Smart Capture Card"
  version "IBM Corp.", "Video Capture"
  bind "iscc_cs"

card "Parallel Port Card"
  function parallel_port
  bind "parport_cs"

card "Quatech SPP-100 Parallel Port Card"
  manfid 0x0137, 0x0003
  bind "parport_cs"

card "TELES S0/PC ISDN"
  version "TELES", "S0/PC"
  bind "teles_cs"

#
# CardBus cards
#
card "3Com 3c575-TX Fast EtherLink XL"
  manfid 0x0101, 0x5057
  bind "3c575_cb"

card "3Com 3CCFE575B/3CXFE575B Fast EtherLink XL"
  manfid 0x0101, 0x5157
  bind "3c575_cb"

card "3Com 3CCFE575CT/3CXFE575CT Fast EtherLink XL"
  manfid 0x0101, 0x5257
  bind "3c575_cb"

card "3Com 3CCFEM656B w/Winmodem"
  manfid 0x0102, 0x6560
  bind "3c575_cb"

card "3Com 3CCFEM656B w/Winmodem"
  manfid 0x0102, 0x6562
  bind "3c575_cb"

card "Accton EN2220 Fast Ethernet"
  version "Accton", "EN2220 CardBus Fast Ethernet Card"
  bind "tulip_cb"

card "Adaptec APA-1480 SCSI Host Adapter"
  manfid 0x012f, 0xcb01
  bind "apa1480_cb"

#Conflicts with corega PCC-T!
#card "Allied Telesyn AT-2800 10/100 Fast Ethernet"
#  manfid 0xc00f, 0x0000
#  bind "tulip_cb"

card "Ambicom AMB8100 Fast Ethernet"
  manfid 0x9513, 0x0081
  bind "tulip_cb"

card "Asante FriendlyNET 10/100 CardBus"
  version "Asante", "FriendlyNET 10/100 CardBus"
  bind "tulip_cb"

card "Tulip-based CardBus Fast Ethernet"
  version "CardBus", "10/100Mbps LAN Card"
  bind "tulip_cb"

card "D-Link DFE-660 Fast Ethernet"
  manfid 0x50c7, 0xcafe
  bind "tulip_cb"

card "Genius MF3000 Fast Ethernet"
  version "CardBus", "10/100Mbps LanCard"
  bind "tulip_cb"

card "IBM 10/100 EtherJet CardBus"
  manfid 0x00a4, 0x0113
  bind "tulip_cb"

card "Intel EtherExpress PRO/100 CardBus Mobile Adapter32"
  manfid 0x0089, 0x0102
  bind "tulip_cb"

card "Kingston KNE-CB4TX Fast Ethernet"
  manfid 0x0186, 0x0101
  bind "tulip_cb"

card "Linksys EtherFast 10/100"
  manfid 0x0149, 0x0231
  bind "tulip_cb"

card "Linksys EtherFast 10/100"
  manfid 0x0149, 0xc2ab
  bind "tulip_cb"

card "SMC EZ 10/100 Fast Ethernet"
  manfid 0x01bf, 0x2220
  bind "tulip_cb"

card "SMC EZ 10/100 Fast Ethernet"
  manfid 0x01bf, 0x2225
  bind "tulip_cb"

#card "SVEC 10/100 Fast Ethernet"
#  manfid 0x8a01, 0x0100
#  bind "tulip_cb"

card "TDK NetworkFlyer 10/100 Fast Ethernet"
  manfid 0x0105, 0x0500
  bind "tulip_cb"

card "UMAX Technologies UMAX250 Fast Ethernet"
  manfid 0x9513, 0x0081
  bind "tulip_cb"

card "Ositech Seven of Spades Fast Ethernet"
  manfid 0x0140, 0x0011
  bind "epic_cb"

card "Ositech Jack of Spades Fast Ethernet/Modem"
  manfid 0x0140, 0x000f
  bind "epic_cb" to 0, "serial_cb" to 1

card "Ositech Jack of Spades Fast Ethernet/Modem"
  manfid 0x0140, 0x0012
  bind "epic_cb" to 0, "serial_cb" to 1

card "Psion Gold Card Netglobal 56K+10/100Mb CardBus"
  manfid 0x016c, 0x0021
  bind "epic_cb" to 0, "serial_cb" to 1

card "Xircom CardBus 10/100 Ethernet"
  version "Xircom", "*", "CBEII-10/100"
  bind "tulip_cb"

card "Xircom CardBus 10/100 Ethernet + 56K Modem"
  version "Xircom", "*", "CBEM56G"
  bind "tulip_cb" to 0, "serial_cb" to 1

# Include configuration files for add-on drivers

source ./*.conf

# Include local configuration settings

source ./config.opts



[ File listing: /etc/pcmcia/config.opts ]
#
# Local PCMCIA Configuration File
#
# System resources available for PCMCIA devices
#
include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff, memory 0xa0000000-0xa0ffffff
#
# 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
#
# 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"


[ File listing: /var/log/messages ]
// MY NOTE: HERE IS SOME SHUT DOWN STUFF

Feb 25 09:23:16 rdlab16 gnome-name-server[813]: name server was running 
on display, exiting
Feb 25 09:45:13 rdlab16 gnome-name-server[807]: input condition is: 16, exiting
Feb 25 09:45:15 rdlab16 innd: control:14 closed
Feb 25 09:45:15 rdlab16 innd: localconn:16 closed
Feb 25 09:45:15 rdlab16 innd: remconn:5 closed
Feb 25 09:45:15 rdlab16 innd: SERVER perl filtering disabled
Feb 25 09:45:16 rdlab16 innd: SERVER shutdown received signal 15
Feb 25 09:45:16 rdlab16 innd: innd shutdown succeeded
Feb 25 09:45:16 rdlab16 innd: actived -9 succeeded
Feb 25 09:45:16 rdlab16 xfs: xfs shutdown succeeded
Feb 25 09:45:17 rdlab16 gpm: Shutting down gpm mouse services: 
Feb 25 09:45:17 rdlab16 gpm: gpm
Feb 25 09:45:17 rdlab16 gpm: 
Feb 25 09:45:17 rdlab16 rc: Stopping gpm succeeded
Feb 25 09:45:17 rdlab16 httpd: httpd shutdown succeeded
Feb 25 09:45:17 rdlab16 sound: Saving sound configuration: 
Feb 25 09:45:17 rdlab16 sound: sound
Feb 25 09:45:17 rdlab16 sound: 
Feb 25 09:45:17 rdlab16 rc: Stopping sound succeeded
Feb 25 09:45:17 rdlab16 nfs: Shutting down NFS services:  succeeded
Feb 25 09:45:17 rdlab16 mountd[495]: Caught signal 15, un-registering and exiting. 
Feb 25 09:45:17 rdlab16 nfs: rpc.mountd shutdown succeeded
Feb 25 09:45:22 rdlab16 kernel: nfsd: terminating on signal 9 
Feb 25 09:45:22 rdlab16 last message repeated 7 times
Feb 25 09:45:22 rdlab16 kernel: nfsd: last server exiting 
Feb 25 09:45:22 rdlab16 nfs: nfsd shutdown succeeded
Feb 25 09:45:22 rdlab16 nfs: rpc.rquotad shutdown succeeded
Feb 25 09:45:22 rdlab16 rpc.statd[473]: Caught signal 15, un-registering and exiting.
Feb 25 09:45:22 rdlab16 nfs: rpc.statd shutdown succeeded
Feb 25 09:45:23 rdlab16 sendmail: sendmail shutdown succeeded
Feb 25 09:45:23 rdlab16 named[442]: named shutting down
Feb 25 09:45:23 rdlab16 named[442]: USAGE 951500723 951499264 CPU=0.01u/0s
CHILDCPU=0u/0s
Feb 25 09:45:23 rdlab16 named[442]: NSTATS 951500723 951499264
Feb 25 09:45:23 rdlab16 named[442]: XSTATS 951500723 951499264 RR=0 RNXD=0 RFwdR=0 RDupR=0 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=1 SAns=0 SFwdQ=0 SDupQ=286 SErr=0 RQ=0 RIQ=0 RFwdQ=0 RDupQ=0 RTCP=0 SFwdR=0 SFail=0 SFErr=0 SNaAns=0 SNXD=0
Feb 25 09:45:23 rdlab16 named: named shutdown succeeded
Feb 25 09:45:24 rdlab16 inet: inetd shutdown succeeded
Feb 25 09:45:24 rdlab16 atd: atd shutdown succeeded
Feb 25 09:45:24 rdlab16 crond: crond shutdown succeeded
Feb 25 09:45:25 rdlab16 lpd: lpd shutdown succeeded
Feb 25 09:45:25 rdlab16 dd: 1+0 records in
Feb 25 09:45:25 rdlab16 dd: 1+0 records out
Feb 25 09:45:25 rdlab16 random: Saving random seed succeeded
Feb 25 09:45:25 rdlab16 portmap: portmap shutdown succeeded
Feb 25 09:45:25 rdlab16 network: Shutting down interface eth0 succeeded
Feb 25 09:45:25 rdlab16 network: Shutting down interface eth1 succeeded
Feb 25 09:45:26 rdlab16 network: Disabling IPv4 packet forwarding succeeded
Feb 25 09:45:26 rdlab16 apmd[102]: Exiting
Feb 25 09:45:26 rdlab16 apmd: apmd shutdown succeeded
Feb 25 09:45:26 rdlab16 pcmcia: Shutting down PCMCIA services:
Feb 25 09:45:26 rdlab16 pcmcia: .
Feb 25 09:45:26 rdlab16 rc: Stopping pcmcia succeeded
Feb 25 09:45:26 rdlab16 kernel: Kernel logging (proc) stopped.
Feb 25 09:45:26 rdlab16 kernel: Kernel log daemon terminating.
Feb 25 09:45:27 rdlab16 syslog: klogd shutdown succeeded
Feb 25 09:45:27 rdlab16 exiting on signal 15


// MY NOTE:  HERE IS THE RESTART

Feb 25 09:46:19 rdlab16 syslogd 1.3-3: restart.
Feb 25 09:46:19 rdlab16 syslog: syslogd startup succeeded
Feb 25 09:46:19 rdlab16 syslog: klogd startup succeeded
Feb 25 09:46:19 rdlab16 kernel: klogd 1.3-3, log source = /proc/kmsg started.
Feb 25 09:46:19 rdlab16 kernel: Inspecting /boot/System.map-2.2.5-15
Feb 25 09:46:19 rdlab16 kernel: Loaded 6721 symbols from /boot/System.map-2.2.5-15.
Feb 25 09:46:19 rdlab16 kernel: Symbols match kernel version 2.2.5.
Feb 25 09:46:19 rdlab16 kernel: Loaded 7 symbols from 2 modules.
Feb 25 09:46:19 rdlab16 kernel: Linux version 2.2.5-15 
 (root@porky.devel.redhat.com) 
 (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) 
 #1 Mon Apr 19 22:21:09 EDT 1999 
Feb 25 09:46:19 rdlab16 kernel: Detected 451031025 Hz processor. 
Feb 25 09:46:19 rdlab16 kernel: Console: colour VGA+ 80x25 
Feb 25 09:46:19 rdlab16 kernel: Calibrating delay loop... 897.84 BogoMIPS 
Feb 25 09:46:19 rdlab16 kernel: Memory: 63140k/65536k available 
 (996k kernel code, 412k reserved, 928k data, 60k init) 
Feb 25 09:46:19 rdlab16 kernel: VFS: Diskquotas version dquot_6.4.0 initialized 
Feb 25 09:46:19 rdlab16 kernel: CPU: AMD AMD-K6(tm) 3D processor stepping 0c 
Feb 25 09:46:19 rdlab16 kernel: Checking 386/387 coupling... OK, 
 FPU using exception 16 error reporting. 
Feb 25 09:46:19 rdlab16 kernel: Checking 'hlt' instruction... OK. 
Feb 25 09:46:19 rdlab16 kernel: POSIX conformance testing by UNIFIX 
Feb 25 09:46:19 rdlab16 kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb290 
Feb 25 09:46:19 rdlab16 kernel: PCI: Using configuration type 1 
Feb 25 09:46:19 rdlab16 kernel: PCI: Probing PCI hardware 
Feb 25 09:46:19 rdlab16 kernel: PCI: 00:38 [1106/0586]: Work around 
 ISA DMA hangs (00) 
Feb 25 09:46:19 rdlab16 kernel: Activating ISA DMA hang workarounds. 
Feb 25 09:46:19 rdlab16 kernel: Linux NET4.0 for Linux 2.2 
Feb 25 09:46:19 rdlab16 kernel: Based upon Swansea 
 University Computer Society NET3.039 
Feb 25 09:46:19 rdlab16 kernel: NET4: Unix domain sockets 1.0 for Linux NET4.0. 
Feb 25 09:46:19 rdlab16 kernel: NET4: Linux TCP/IP 1.0 for NET4.0 
Feb 25 09:46:19 rdlab16 kernel: IP Protocols: ICMP, UDP, TCP, IGMP 
Feb 25 09:46:19 rdlab16 kernel: Initializing RT netlink socket 
Feb 25 09:46:19 rdlab16 kernel: Starting kswapd v 1.5  
Feb 25 09:46:19 rdlab16 kernel: Detected PS/2 Mouse Port. 
Feb 25 09:46:19 rdlab16 kernel: Serial driver version 4.27 with 
 MANY_PORTS MULTIPORT SHARE_IRQ enabled 
Feb 25 09:46:19 rdlab16 kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A 
Feb 25 09:46:19 rdlab16 kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A 
Feb 25 09:46:19 rdlab16 kernel: pty: 256 Unix98 ptys configured 
Feb 25 09:46:19 rdlab16 kernel: apm: BIOS version 1.2 Flags 0x07 
 (Driver version 1.9) 
Feb 25 09:46:19 rdlab16 kernel: Real Time Clock Driver v1.09 
Feb 25 09:46:19 rdlab16 kernel: RAM disk driver initialized:  16 RAM 
 disks of 4096K size 
Feb 25 09:46:19 rdlab16 kernel: VP_IDE: IDE controller on PCI bus 00 dev 39 
Feb 25 09:46:19 rdlab16 kernel: VP_IDE: not 100% native mode: will probe irqs later 
Feb 25 09:46:19 rdlab16 kernel:     ide0: BM-DMA at 0xe000-0xe007, 
 BIOS settings: hda:DMA, hdb:DMA 
Feb 25 09:46:19 rdlab16 kernel:     ide1: BM-DMA at 0xe008-0xe00f, 
 BIOS settings: hdc:DMA, hdd:DMA 
Feb 25 09:46:19 rdlab16 kernel: hda: QUANTUM FIREBALL EX3.2A, ATA DISK drive 
Feb 25 09:46:19 rdlab16 kernel: hdc: CD-ROM 40X/AKU, ATAPI CDROM drive 
Feb 25 09:46:19 rdlab16 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 
Feb 25 09:46:19 rdlab16 kernel: ide1 at 0x170-0x177,0x376 on irq 15 
Feb 25 09:46:19 rdlab16 kernel: hda: QUANTUM FIREBALL EX3.2A, 
 3079MB w/418kB Cache, CHS=782/128/63 
Feb 25 09:46:19 rdlab16 kernel: hdc: ATAPI 40X CD-ROM drive, 128kB Cache 
Feb 25 09:46:19 rdlab16 kernel: Uniform CDROM driver Revision: 2.54 
Feb 25 09:46:19 rdlab16 kernel: Floppy drive(s): fd0 is 1.44M 
Feb 25 09:46:19 rdlab16 kernel: FDC 0 is a post-1991 82077 
Feb 25 09:46:19 rdlab16 kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 
Feb 25 09:46:19 rdlab16 kernel: raid5: measuring checksumming speed 
Feb 25 09:46:19 rdlab16 kernel: raid5: using high-speed MMX checksum routine 
Feb 25 09:46:19 rdlab16 kernel:    pII_mmx   :   939.165 MB/sec 
Feb 25 09:46:19 rdlab16 kernel:    p5_mmx    :   843.915 MB/sec 
Feb 25 09:46:19 rdlab16 kernel:    8regs     :   646.557 MB/sec 
Feb 25 09:46:19 rdlab16 kernel:    32regs    :   467.487 MB/sec 
Feb 25 09:46:19 rdlab16 kernel: using fastest function: pII_mmx (939.165 MB/sec) 
Feb 25 09:46:19 rdlab16 kernel: scsi : 0 hosts. 
Feb 25 09:46:19 rdlab16 kernel: scsi : detected total. 
Feb 25 09:46:19 rdlab16 kernel: md.c: sizeof(mdp_super_t) = 4096 
Feb 25 09:46:19 rdlab16 kernel: Partition check: 
Feb 25 09:46:19 rdlab16 kernel:  hda: hda1 hda2 < hda5 hda6 > 
Feb 25 09:46:19 rdlab16 kernel: autodetecting RAID arrays 
Feb 25 09:46:19 rdlab16 kernel: autorun ... 
Feb 25 09:46:19 rdlab16 kernel: ... autorun DONE. 
Feb 25 09:46:19 rdlab16 kernel: VFS: Mounted root (ext2 filesystem) readonly. 
Feb 25 09:46:19 rdlab16 kernel: Freeing unused kernel memory: 60k freed 
Feb 25 09:46:19 rdlab16 kernel: Adding Swap: 100764k swap-space (priority -1)
 
Feb 25 09:46:19 rdlab16 kernel: PCnet-Home: PCI bios is 
 present, checking for devices... 
Feb 25 09:46:19 rdlab16 kernel: PCnet-Home: Found PCnet/PCI at 0xe800, irq 5. 
Feb 25 09:46:19 rdlab16 kernel: PCnet-Home: pcnet32 media value 0x8081. 
Feb 25 09:46:19 rdlab16 kernel: PCnet-Home: pcnet32 media reset to 0x8081. 
Feb 25 09:46:19 rdlab16 kernel: eth0: PCnet/Home 79C978 at 0xe800, 
 00 90 00 03 bb 10 assigned IRQ 5. 
Feb 25 09:46:19 rdlab16 kernel: PCnet-Home: Total of 1 AMD PCnetHome 
 Family Card(s) found. 

Feb 25 09:46:19 rdlab16 kernel: pcnet32.c: PCI bios is present, 
 checking for devices... 
Feb 25 09:46:19 rdlab16 kernel: PCI Master Bit has not been set. Setting... 
Feb 25 09:46:19 rdlab16 kernel: Found PCnet/PCI at 0xec00, irq 10. 
Feb 25 09:46:19 rdlab16 kernel: eth1: PCnet/FAST+ 79C972 at 0xec00, 
 00 00 1a 18 42 c3 assigned IRQ 10. 
Feb 25 09:46:19 rdlab16 kernel: pcnet32.c:v1.11 17.1.99 
 tsbogend@alpha.franken.de 

Feb 25 09:46:20 rdlab16 atd: atd startup succeeded
Feb 25 09:46:20 rdlab16 crond: crond startup succeeded
Feb 25 09:46:08 rdlab16 rc.sysinit: Loading default keymap succeeded 
Feb 25 09:46:08 rdlab16 rc.sysinit: Setting default font succeeded 
Feb 25 09:46:08 rdlab16 swapon: swapon: warning: /dev/hda5 has 
 insecure permissions 0660, 0600 suggested 
Feb 25 09:46:08 rdlab16 rc.sysinit: Activating swap partitions succeeded 
Feb 25 09:46:08 rdlab16 rc.sysinit: Setting hostname rdlab16.amd.com succeeded 
Feb 25 09:46:08 rdlab16 fsck: /dev/hda6: clean, 56497/759808 files, 
 802119/3032032 blocks 
Feb 25 09:46:08 rdlab16 rc.sysinit: Checking root filesystem succeeded 
Feb 25 09:46:08 rdlab16 rc.sysinit: Remounting root filesystem in 
 read-write mode succeeded 
Feb 25 09:46:12 rdlab16 rc.sysinit: Finding module dependencies succeeded 
Feb 25 09:46:13 rdlab16 fsck: /dev/hda1: clean, 23/5040 files, 2920/20128 blocks 
Feb 25 09:46:13 rdlab16 rc.sysinit: Checking filesystems succeeded 
Feb 25 09:46:13 rdlab16 rc.sysinit: Mounting local filesystems succeeded 
Feb 25 09:46:13 rdlab16 rc.sysinit: Turning on user and group 
 quotas for local filesystems succeeded 
Feb 25 09:46:15 rdlab16 date: Fri Feb 25 09:46:15 PST 2000 
Feb 25 09:46:15 rdlab16 rc.sysinit: Setting clock  (utc): Fri 
 Feb 25 09:46:15 PST 2000 succeeded 
Feb 25 09:46:15 rdlab16 rc.sysinit: Enabling swap space succeeded 
Feb 25 09:46:15 rdlab16 init: Entering runlevel: 3 
Feb 25 09:46:15 rdlab16 apmd[102]: Version 3.0beta4 
 (APM BIOS 1.2, Linux driver 1.9) 
Feb 25 09:46:16 rdlab16 apmd: apmd startup succeeded 
Feb 25 09:46:16 rdlab16 network: Enabling IPv4 packet forwarding succeeded 
Feb 25 09:46:18 rdlab16 network: Bringing up interface lo succeeded 
Feb 25 09:46:18 rdlab16 ifup: SIOCADDRT: Network is unreachable 
Feb 25 09:46:18 rdlab16 network: Bringing up interface eth0 succeeded 
Feb 25 09:46:19 rdlab16 network: Bringing up interface eth1 succeeded 
Feb 25 09:46:19 rdlab16 portmap: portmap startup succeeded 
Feb 25 09:46:19 rdlab16 netfs: Mounting other filesystems succeeded 
Feb 25 09:46:19 rdlab16 random: Initializing random number generator succeeded 


Feb 25 09:46:21 rdlab16 kernel: Linux PCMCIA Card Services 3.1.11 
Feb 25 09:46:21 rdlab16 kernel:   kernel build: 2.2.5-15 #1 Mon 
 Apr 19 22:21:09 EDT 1999 
Feb 25 09:46:21 rdlab16 kernel:   options:  [pci] [cardbus] [apm] 
Feb 25 09:46:21 rdlab16 kernel: PCI routing table version 1.0 at 0xfdc40 
Feb 25 09:46:21 rdlab16 kernel:   unknown PCI interrupt router 1106:0586 
Feb 25 09:46:21 rdlab16 kernel: Intel PCIC probe: not found. 
Feb 25 09:46:21 rdlab16 kernel: ds: no socket drivers loaded! 
Feb 25 09:46:20 rdlab16 pcmcia: Starting PCMCIA services:
Feb 25 09:46:21 rdlab16 pcmcia:  modules
Feb 25 09:46:21 rdlab16 pcmcia: /lib/modules/2.2.5-15/pcmcia/i82365.o: 
Feb 25 09:46:21 rdlab16 pcmcia: init_module: Device or resource busy
Feb 25 09:46:21 rdlab16 pcmcia: 
Feb 25 09:46:21 rdlab16 pcmcia: /lib/modules/2.2.5-15/pcmcia/ds.o: 
Feb 25 09:46:21 rdlab16 pcmcia:  cardmgr.
Feb 25 09:46:21 rdlab16 pcmcia: init_module: Device or resource busy
Feb 25 09:46:21 rdlab16 rc: Starting pcmcia succeeded
Feb 25 09:46:21 rdlab16 cardmgr[414]: starting, version is 3.1.11
Feb 25 09:46:21 rdlab16 cardmgr[414]: no pcmcia driver in /proc/devices
Feb 25 09:46:21 rdlab16 cardmgr[414]: exiting


Feb 25 09:46:21 rdlab16 inet: inetd startup succeeded
Feb 25 09:46:22 rdlab16 named[441]: starting.  named 8.2 Wed 
 Mar 31 10:57:12 EST 1999 ^Iroot@porky.devel.redhat.com:
 /usr/src/bs/BUILD/bind-8.2/src/bin/named
Feb 25 09:46:22 rdlab16 named[441]: cache zone "" 
 (IN) loaded (serial 0)
Feb 25 09:46:22 rdlab16 named[441]: Zone "0.0.127.in-addr.arpa" 
 (file named.local): No default TTL set using SOA minimum instead
Feb 25 09:46:22 rdlab16 named[441]: master zone "0.0.127.in-addr.arpa" 
 (IN) loaded (serial 1997022700)
Feb 25 09:46:22 rdlab16 named[441]: listening on [127.0.0.1].53 (lo)
Feb 25 09:46:22 rdlab16 named[441]: listening on [10.10.0.1].53 (eth0)
Feb 25 09:46:22 rdlab16 named[441]: listening on [139.95.79.165].53 (eth1)
Feb 25 09:46:22 rdlab16 named[441]: Forwarding source address 
 is [0.0.0.0].1024
Feb 25 09:46:22 rdlab16 named: named startup succeeded
Feb 25 09:46:22 rdlab16 named[442]: Ready to answer queries.
Feb 25 09:46:22 rdlab16 lpd: lpd startup succeeded
Feb 25 09:46:22 rdlab16 nfs: Starting NFS services:  succeeded
Feb 25 09:46:23 rdlab16 nfs: rpc.statd startup succeeded
Feb 25 09:46:23 rdlab16 nfs: rpc.rquotad startup succeeded
Feb 25 09:46:24 rdlab16 nfs: rpc.mountd startup succeeded
Feb 25 09:46:24 rdlab16 kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de). 
Feb 25 09:46:24 rdlab16 nfs: rpc.nfsd startup succeeded
Feb 25 09:46:24 rdlab16 keytable: Loading keymap: 
Feb 25 09:46:24 rdlab16 keytable: Loading 
 /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
Feb 25 09:46:25 rdlab16 keytable: Loading system font: 
Feb 25 09:46:25 rdlab16 rc: Starting keytable succeeded
Feb 25 09:46:25 rdlab16 sendmail: sendmail startup succeeded
Feb 25 09:46:26 rdlab16 gpm: gpm startup succeeded
Feb 25 09:46:26 rdlab16 httpd: httpd startup succeeded
Feb 25 09:46:27 rdlab16 sound: Starting sound configuration: sound
Feb 25 09:46:27 rdlab16 rc: Starting sound succeeded
Feb 25 09:46:27 rdlab16 PAM_pwdb[610]: (su) session opened for 
 user xfs by (uid=0)
Feb 25 09:46:27 rdlab16 pam_xauth[610]: do_file: could not create dir /etc/X11/fs/.xauth
Feb 25 09:46:28 rdlab16 PAM_pwdb[610]: (su) session closed for user xfs
Feb 25 09:46:28 rdlab16 pam_xauth[610]: do_file: could not 
 create dir /etc/X11/fs/.xauth
Feb 25 09:46:28 rdlab16 xfs: xfs startup succeeded
Feb 25 09:46:29 rdlab16 smb: smbd startup succeeded
Feb 25 09:46:29 rdlab16 smb: nmbd startup succeeded
Feb 25 09:46:29 rdlab16 PAM_pwdb[643]: (su) session opened for 
 user news by (uid=0)
Feb 25 09:46:29 rdlab16 kernel: 139.95.74.18 sent an 
 invalid ICMP error to a broadcast. 
Feb 25 09:46:29 rdlab16 kernel: 139.95.74.30 sent an 
 invalid ICMP error to a broadcast. 
Feb 25 09:46:29 rdlab16 kernel: 139.95.74.18 sent an 
 invalid ICMP error to a broadcast. 
Feb 25 09:46:29 rdlab16 kernel: 139.95.74.30 sent an 
 invalid ICMP error to a broadcast. 
Feb 25 09:46:29 rdlab16 kernel: 139.95.74.18 sent an 
 invalid ICMP error to a broadcast. 
Feb 25 09:46:29 rdlab16 kernel: 139.95.74.30 sent an 
 invalid ICMP error to a broadcast. 
Feb 25 09:46:29 rdlab16 kernel: 139.95.71.220 sent an 
 invalid ICMP error to a broadcast. 
Feb 25 09:46:29 rdlab16 kernel: 139.95.71.220 sent an 
 invalid ICMP error to a broadcast. 
Feb 25 09:46:29 rdlab16 kernel: 139.95.73.113 sent an 
 invalid ICMP error to a broadcast. 
Feb 25 09:46:29 rdlab16 kernel: 139.95.73.113 sent an 
 invalid ICMP error to a broadcast. 
Feb 25 09:46:31 rdlab16 actived[691]: started
Feb 25 09:46:31 rdlab16 innd: SERVER descriptors 1024
Feb 25 09:46:31 rdlab16 innd: SERVER outgoing 1011
Feb 25 09:46:31 rdlab16 innd: SERVER ccsetup control:14
Feb 25 09:46:31 rdlab16 innd: SERVER lcsetup localconn:16
Feb 25 09:46:31 rdlab16 innd: SERVER rcsetup remconn:5
Feb 25 09:46:31 rdlab16 innd: SERVER bad_newsfeeds no feeding sites
Feb 25 09:46:31 rdlab16 innd: SERVER perl filtering enabled
Feb 25 09:46:31 rdlab16 innd: SERVER starting
Feb 25 09:46:31 rdlab16 PAM_pwdb[643]: (su) session closed for user news
Feb 25 09:46:31 rdlab16 linuxconf: Linuxconf final setup
Feb 25 09:46:31 rdlab16 rc: Starting linuxconf succeeded
Feb 25 09:46:32 rdlab16 rc: Starting local succeeded
Feb 25 09:46:39 rdlab16 PAM_pwdb[734]: (login) session opened 
 for user root by (uid=0)



[ Dir listing: /lib/modules/pcmcia,  using ls -lF ]
total 752
-rw-r--r--   1 root     root        14144 Feb 23 06:53 3c574_cs.o
-rw-r--r--   1 root     root        26788 Feb 23 06:53 3c575_cb.o
-rw-r--r--   1 root     root        12048 Feb 23 06:53 3c589_cs.o
-rw-r--r--   1 root     root        33836 Feb 23 06:53 aha152x_cs.o
-rw-r--r--   1 root     root        27284 Feb 23 06:53 airo.o
-rw-r--r--   1 root     root         5352 Feb 23 06:53 airo_cs.o
-rw-r--r--   1 root     root       121225 Feb 23 06:53 apa1480_cb.o
-rw-r--r--   1 root     root         4728 Feb 23 06:53 cb_enabler.o
-rw-r--r--   1 root     root        10892 Feb 23 06:53 ds.o
-rw-r--r--   1 root     root         5480 Feb 23 06:53 dummy_cs.o
-rw-r--r--   1 root     root        14964 Feb 23 06:53 epic_cb.o
-rw-r--r--   1 root     root        24070 Feb 23 06:53 fdomain_cs.o
-rw-r--r--   1 root     root         9708 Feb 23 06:53 fmvj18x_cs.o
-rw-r--r--   1 root     root        17144 Feb 23 06:53 ftl_cs.o
-rw-r--r--   1 root     root        31780 Feb 23 06:53 i82365.o
-rw-r--r--   1 root     root        21049 Feb 23 06:53 ibmtr_cs.o
-rw-r--r--   1 root     root         5644 Feb 23 06:53 ide_cs.o
-rw-r--r--   1 root     root        13180 Feb 23 06:53 iflash2+_mtd.o
-rw-r--r--   1 root     root        10764 Feb 23 06:53 iflash2_mtd.o
-rw-r--r--   1 root     root         5276 Feb 23 06:53 memory_cb.o
-rw-r--r--   1 root     root        13652 Feb 23 06:53 memory_cs.o
-rw-r--r--   1 root     root        13204 Feb 23 06:53 netwave_cs.o
-rw-r--r--   1 root     root         8584 Feb 23 06:53 nmclan_cs.o
-rw-r--r--   1 root     root         5812 Feb 23 06:53 parport_cs.o
-rw-r--r--   1 root     root        61488 Feb 23 06:53 pcmcia_core.o
-rw-r--r--   1 root     root        13012 Feb 23 06:53 pcnet_cs.o
-rw-r--r--   1 root     root        11307 Feb 23 06:53 qlogic_cs.o
-rw-r--r--   1 root     root        21932 Feb 23 06:53 ray_cs.o
-rw-r--r--   1 root     root         2640 Feb 23 06:53 serial_cb.o
-rw-r--r--   1 root     root         8036 Feb 23 06:53 serial_cs.o
-rw-r--r--   1 root     root        19988 Feb 23 06:53 smc91c92_cs.o
-rw-r--r--   1 root     root         5508 Feb 23 06:53 sram_mtd.o
-rw-r--r--   1 root     root        11832 Feb 23 06:53 tcic.o
-rw-r--r--   1 root     root        41764 Feb 23 06:53 tulip_cb.o
-rw-r--r--   1 root     root        30392 Feb 23 06:53 wavelan_cs.o
-rw-r--r--   1 root     root        25951 Feb 23 06:53 wvlan_cs.o
-rw-r--r--   1 root     root        19152 Feb 23 06:53 xirc2ps_cs.o

None The reader is an ISA PnP device and needs to be activated

Re: Question Install and config of Linksys desktop PCMRDWR reader writer and PCM100H1 card (Jeff Gembler)
Date: 2000, Feb 26
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> Are the PCMCIA drivers stable and usable for what I want to do?

should be.

> Where, specifically, are the driver modules or files that support
> the Linksys internal PCMCIA reader writer Model No. PCMRDWR

It's the i82365 module.

> Where, specifically, are the driver modules or files that support
> the Linksys Eth/HPNA card Model No. PCM100H1

It's the pcnet_cs module, as shown in the supported cards list.

> So, the kernel and PCMCIA should be in sync ?
> So no need to look into the CONFIG_MODVERSIONS kernel option?

correct.

> The way things are right now, I don't get any beeps on plugging in
> or removing a PCMCIA card.  Should I?

yes.

> Should I be able to 
> verify the PCMCIA reader/writer is present (by reading registers, etc.),

yes.

> If there is more that one option for PCIC_OPTS, should they be 
> comma separated on the same line,  or should/can different lines
> be used like:
>   PCIC_OPTS="   "

One line, space separated, like PCIC_OPTS="x=1 y=2 z=3".  The
PCMCIA-HOWTO says this in section 2.3.

> 7) Changed /etc/sysconfig/pcmcia
> 
>    PCMCIA="Yes"

Use "yes".  It is case sensitive.

>    PCIC_OPTS="extra_sockets=1"

You don't have any extra sockets, but it doesn't matter.

> [ A NOTE ABOUT THE VIA VT83C469 ]

This is your main problem.  The VT83C469 in the Linksys card is a
"Plug and Play" device.  You have to use the Linux isapnp package to
configure the card before it can be detected and used by the PCMCIA
drivers.  After that, the "probe" command will see it.

-- Dave

Question Used pnpdump to produce isapnp.conf, still not there yet

Re: Question Install and config of Linksys desktop PCMRDWR reader writer and PCM100H1 card (Jeff Gembler)
Date: 2000, Mar 25
From: Jeff Gembler jeffrey.gembler

Continuing on . . .


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

In /etc/sysconfig/pcmcia,  I have:


PCMCIA="yes"
PCIC="i82365"
PCIC_OPTS="extra_sockets=1 check_pnp_irq=1"
CORE_OPTS=


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

I used  pnpdump > isapnp.conf  to produce file:  /etc/isapnp.conf:


# $Id: pnpdump.c,v 1.18 1999/02/14 22:47:18 fox Exp $
# This is free software, see the sources for details.
# This software has NO WARRANTY, use at your OWN RISK
#
# For details of this file format, see isapnp.conf(5)
#
# For latest information and FAQ on isapnp and pnpdump see:
# http://www.roestock.demon.co.uk/isapnptools/
#
# Compiler flags: -DREALTIME -DNEEDSETSCHEDULER -DABORT_ONRESERR
#
# Trying port address 0203
# Board 1 has serial identifier 21 05 00 00 00 18 30 21 59

# (DEBUG)
(READPORT 0x0203)
(ISOLATE PRESERVE)
(IDENTIFY *)
(VERBOSITY 2)
(CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING

# Card 1: (serial identifier 21 05 00 00 00 18 30 21 59)
# Vendor Id VIA3018, Serial Number 83886080, checksum 0x21.
# Version 1.0, Vendor version 0.0
# ANSI string -->VIA PCMCIA CARD<--
#
# Logical device id PNP0e00
#     Device support I/O range check register
#
# Edit the entries below to uncomment out the configuration required.
# Note that only the first value of any range is given, this may be changed if required
# Don't forget to uncomment the activate (ACT Y) when happy

(CONFIGURE VIA3018/83886080 (LD 0
#     Compatible device id PNP0e00
#     Logical device decodes 16 bit IO address lines
#         Minimum IO base address 0x03e0
#         Maximum IO base address 0x03e3
#         IO base alignment 2 bytes
#         Number of IO addresses required: 2
# (IO 0 (SIZE 2) (BASE 0x03e0) (CHECK))
 (NAME "VIA3018/83886080[0]{VIA PCMCIA CARD     }")
# (ACT Y)
))
# End tag... Checksum 0x00 (OK)

# Returns all cards to the "Wait for Key" state
(WAITFORKEY)



= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Without making changes to isapnp.conf  if I enter isapnp isapnp.conf,  I get:

# isapnp  isapnp.conf  
Board 1 has Identity 21 05 00 00 00 18 30 21 59:  VIA3018 Serial No 83886080 [checksum 21]



If I uncomment the line
   # (ACT Y)
and enter  isapnp  isapnp.conf,   I get:

# isapnp  isapnp.conf  
Board 1 has Identity 21 05 00 00 00 18 30 21 59:  VIA3018 Serial No 83886080 [checksum 21]
VIA3018/83886080[0]{VIA PCMCIA CARD     }: --- Enabled OK



If I also uncomment the line
   # (IO 0 (SIZE 2) (BASE 0x03e0) (CHECK))
and enter  isapnp  isapnp.conf,   I get:

# isapnp  isapnp.conf  
Board 1 has Identity 21 05 00 00 00 18 30 21 59:  VIA3018 Serial No 83886080 [checksum 21]
isapnp.conf:41 -- Fatal - resource conflict allocating 2 bytes of IO at 3E0 (see isapnp.conf)
isapnp.conf:41 -- Fatal - IO range check attempted while device activated
isapnp.conf:41 -- Fatal - Error occurred executing request '<IORESCHECK> ' --- further action aborted



= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

In /proc,  cat ioports   gives:

0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
e000-e007 : ide0
e008-e00f : ide1
e800-e81f : PCnet/Home 79C978
ec00-ec17 : PCnet/FAST+ 79C972



In /proc,  cat interrupts   gives:

           CPU0       
  0:     615522          XT-PIC  timer
  1:      43551          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  5:         97          XT-PIC  PCnet/Home 79C978
  8:          2          XT-PIC  rtc
 10:     140335          XT-PIC  PCnet/FAST+ 79C972
 12:      23777          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:      91415          XT-PIC  ide0
 15:          7          XT-PIC  ide1
NMI:          0



In /proc,  cat interrupts   gives:

 4: cascade


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

This is what /var/log/messages looks like on rebooting :


Mar 24 08:12:58 rdlab16 apmd[106]: Exiting
Mar 24 08:12:59 rdlab16 apmd: apmd shutdown succeeded
Mar 24 08:12:59 rdlab16 pcmcia: Shutting down PCMCIA services:
Mar 24 08:12:59 rdlab16 pcmcia: .
Mar 24 08:12:59 rdlab16 rc: Stopping pcmcia succeeded
Mar 24 08:12:59 rdlab16 kernel: Kernel logging (proc) stopped.
Mar 24 08:12:59 rdlab16 kernel: Kernel log daemon terminating.
Mar 24 08:13:00 rdlab16 syslog: klogd shutdown succeeded
Mar 24 08:13:00 rdlab16 exiting on signal 15


Mar 24 08:13:52 rdlab16 syslogd 1.3-3: restart.
Mar 24 08:13:52 rdlab16 syslog: syslogd startup succeeded
Mar 24 08:13:52 rdlab16 syslog: klogd startup succeeded
Mar 24 08:13:52 rdlab16 kernel: klogd 1.3-3, log source = /proc/kmsg started.
Mar 24 08:13:52 rdlab16 kernel: Inspecting /boot/System.map-2.2.5-15
Mar 24 08:13:53 rdlab16 kernel: Loaded 6721 symbols from /boot/System.map-2.2.5-15.
Mar 24 08:13:53 rdlab16 kernel: Symbols match kernel version 2.2.5.
Mar 24 08:13:53 rdlab16 kernel: Loaded 7 symbols from 2 modules.
Mar 24 08:13:53 rdlab16 kernel: Linux version 2.2.5-15 (root@porky.devel.redhat.com) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Apr 19 22:21:09 EDT 1999 
Mar 24 08:13:53 rdlab16 kernel: Detected 451035619 Hz processor. 
Mar 24 08:13:53 rdlab16 kernel: Console: colour VGA+ 80x25 
Mar 24 08:13:53 rdlab16 kernel: Calibrating delay loop... 897.84 BogoMIPS 
Mar 24 08:13:53 rdlab16 kernel: Memory: 63140k/65536k available (996k kernel code, 412k reserved, 928k data, 60k init) 
Mar 24 08:13:53 rdlab16 kernel: VFS: Diskquotas version dquot_6.4.0 initialized 
Mar 24 08:13:53 rdlab16 kernel: CPU: AMD AMD-K6(tm) 3D processor stepping 0c 
Mar 24 08:13:53 rdlab16 kernel: Checking 386/387 coupling... OK, FPU using exception 16 error reporting. 
Mar 24 08:13:53 rdlab16 kernel: Checking 'hlt' instruction... OK. 
Mar 24 08:13:53 rdlab16 kernel: POSIX conformance testing by UNIFIX 
Mar 24 08:13:53 rdlab16 kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb290 
Mar 24 08:13:53 rdlab16 kernel: PCI: Using configuration type 1 
Mar 24 08:13:53 rdlab16 kernel: PCI: Probing PCI hardware 
Mar 24 08:13:53 rdlab16 kernel: PCI: 00:38 [1106/0586]: Work around ISA DMA hangs (00) 
Mar 24 08:13:53 rdlab16 kernel: Activating ISA DMA hang workarounds. 
Mar 24 08:13:53 rdlab16 kernel: Linux NET4.0 for Linux 2.2 
Mar 24 08:13:53 rdlab16 kernel: Based upon Swansea University Computer Society NET3.039 
Mar 24 08:13:53 rdlab16 kernel: NET4: Unix domain sockets 1.0 for Linux NET4.0. 
Mar 24 08:13:53 rdlab16 kernel: NET4: Linux TCP/IP 1.0 for NET4.0 
Mar 24 08:13:53 rdlab16 kernel: IP Protocols: ICMP, UDP, TCP, IGMP 
Mar 24 08:13:53 rdlab16 kernel: Initializing RT netlink socket 
Mar 24 08:13:53 rdlab16 kernel: Starting kswapd v 1.5  
Mar 24 08:13:53 rdlab16 kernel: Detected PS/2 Mouse Port. 
Mar 24 08:13:53 rdlab16 kernel: Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled 
Mar 24 08:13:53 rdlab16 kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A 
Mar 24 08:13:53 rdlab16 kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A 
Mar 24 08:13:53 rdlab16 kernel: pty: 256 Unix98 ptys configured 
Mar 24 08:13:53 rdlab16 kernel: apm: BIOS version 1.2 Flags 0x07 (Driver version 1.9) 
Mar 24 08:13:53 rdlab16 kernel: Real Time Clock Driver v1.09 
Mar 24 08:13:53 rdlab16 kernel: RAM disk driver initialized:  16 RAM disks of 4096K size 
Mar 24 08:13:53 rdlab16 kernel: VP_IDE: IDE controller on PCI bus 00 dev 39 
Mar 24 08:13:53 rdlab16 kernel: VP_IDE: not 100% native mode: will probe irqs later 
Mar 24 08:13:53 rdlab16 kernel:     ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA 
Mar 24 08:13:53 rdlab16 kernel:     ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA 
Mar 24 08:13:53 rdlab16 kernel: hda: QUANTUM FIREBALL EX3.2A, ATA DISK drive 
Mar 24 08:13:53 rdlab16 kernel: hdc: CD-ROM 40X/AKU, ATAPI CDROM drive 
Mar 24 08:13:53 rdlab16 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 
Mar 24 08:13:53 rdlab16 kernel: ide1 at 0x170-0x177,0x376 on irq 15 
Mar 24 08:13:53 rdlab16 kernel: ide1: probed IRQ 15 failed, using default. 
Mar 24 08:13:53 rdlab16 kernel: hda: QUANTUM FIREBALL EX3.2A, 3079MB w/418kB Cache, CHS=782/128/63 
Mar 24 08:13:53 rdlab16 kernel: hdc: ATAPI 40X CD-ROM drive, 128kB Cache 
Mar 24 08:13:53 rdlab16 kernel: Uniform CDROM driver Revision: 2.54 
Mar 24 08:13:53 rdlab16 kernel: Floppy drive(s): fd0 is 1.44M 
Mar 24 08:13:53 rdlab16 kernel: FDC 0 is a post-1991 82077 
Mar 24 08:13:53 rdlab16 kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 
Mar 24 08:13:53 rdlab16 kernel: raid5: measuring checksumming speed 
Mar 24 08:13:53 rdlab16 kernel: raid5: using high-speed MMX checksum routine 
Mar 24 08:13:53 rdlab16 kernel:    pII_mmx   :   939.165 MB/sec 
Mar 24 08:13:53 rdlab16 kernel:    p5_mmx    :   843.534 MB/sec 
Mar 24 08:13:53 rdlab16 kernel:    8regs     :   646.557 MB/sec 
Mar 24 08:13:53 rdlab16 kernel:    32regs    :   467.487 MB/sec 
Mar 24 08:13:53 rdlab16 kernel: using fastest function: pII_mmx (939.165 MB/sec) 
Mar 24 08:13:53 rdlab16 kernel: scsi : 0 hosts. 
Mar 24 08:13:53 rdlab16 kernel: scsi : detected total. 
Mar 24 08:13:53 rdlab16 kernel: md.c: sizeof(mdp_super_t) = 4096 
Mar 24 08:13:53 rdlab16 kernel: Partition check: 
Mar 24 08:13:53 rdlab16 kernel:  hda: hda1 hda2 < hda5 hda6 > 
Mar 24 08:13:53 rdlab16 kernel: autodetecting RAID arrays 
Mar 24 08:13:53 rdlab16 kernel: autorun ... 
Mar 24 08:13:53 rdlab16 kernel: ... autorun DONE. 
Mar 24 08:13:53 rdlab16 kernel: VFS: Mounted root (ext2 filesystem) readonly. 
Mar 24 08:13:53 rdlab16 kernel: Freeing unused kernel memory: 60k freed 
Mar 24 08:13:53 rdlab16 kernel: Adding Swap: 100764k swap-space (priority -1) 
Mar 24 08:13:53 rdlab16 kernel: PCnet-Home: PCI bios is present, checking for devices... 
Mar 24 08:13:53 rdlab16 kernel: PCnet-Home: Found PCnet/PCI at 0xe800, irq 5. 
Mar 24 08:13:53 rdlab16 kernel: PCnet-Home: pcnet32 media value 0x8081. 
Mar 24 08:13:53 rdlab16 kernel: PCnet-Home: pcnet32 media reset to 0x8081. 
Mar 24 08:13:53 rdlab16 kernel: eth0: PCnet/Home 79C978 at 0xe800, 00 90 00 03 bb 10 assigned IRQ 5. 
Mar 24 08:13:53 rdlab16 kernel: PCnet-Home: Total of 1 AMD PCnetHome Family Card(s) found. 
Mar 24 08:13:53 rdlab16 kernel: pcnet32.c: PCI bios is present, checking for devices... 
Mar 24 08:13:53 rdlab16 kernel: PCI Master Bit has not been set. Setting... 
Mar 24 08:13:53 rdlab16 kernel: Found PCnet/PCI at 0xec00, irq 10. 
Mar 24 08:13:53 rdlab16 kernel: eth1: PCnet/FAST+ 79C972 at 0xec00, 00 00 1a 18 42 c3 assigned IRQ 10. 
Mar 24 08:13:53 rdlab16 kernel: pcnet32.c:v1.11 17.1.99 tsbogend@alpha.franken.de 
Mar 24 08:13:53 rdlab16 atd: atd startup succeeded
Mar 24 08:13:41 rdlab16 rc.sysinit: Loading default keymap succeeded 
Mar 24 08:13:42 rdlab16 rc.sysinit: Setting default font succeeded 
Mar 24 08:13:42 rdlab16 swapon: swapon: warning: /dev/hda5 has insecure permissions 0660, 0600 suggested 
Mar 24 08:13:42 rdlab16 rc.sysinit: Activating swap partitions succeeded 
Mar 24 08:13:42 rdlab16 rc.sysinit: Setting hostname rdlab16.amd.com succeeded 
Mar 24 08:13:42 rdlab16 fsck: /dev/hda6: clean, 73178/759808 files, 1694112/3032032 blocks 
Mar 24 08:13:42 rdlab16 rc.sysinit: Checking root filesystem succeeded 
Mar 24 08:13:42 rdlab16 isapnp: Board 1 has Identity 21 05 00 00 00 18 30 21 59:  VIA3018 Serial No 83886080 [checksum 21] 
Mar 24 08:13:42 rdlab16 isapnp: /etc/isapnp.conf:41 -- Fatal - resource conflict allocating 2 bytes of IO at 3E0 (see /etc/isapnp.conf) 
Mar 24 08:13:42 rdlab16 isapnp: /etc/isapnp.conf:41 -- Fatal - Error occurred executing request '<IORESCHECK> ' --- further action aborted 
Mar 24 08:13:42 rdlab16 rc.sysinit: Setting up ISA PNP devices failed 
Mar 24 08:13:42 rdlab16 rc.sysinit: Remounting root filesystem in read-write mode succeeded 
Mar 24 08:13:46 rdlab16 rc.sysinit: Finding module dependencies succeeded 
Mar 24 08:13:46 rdlab16 fsck: /dev/hda1: clean, 23/5040 files, 2920/20128 blocks 
Mar 24 08:13:46 rdlab16 rc.sysinit: Checking filesystems succeeded 
Mar 24 08:13:46 rdlab16 rc.sysinit: Mounting local filesystems succeeded 
Mar 24 08:13:46 rdlab16 rc.sysinit: Turning on user and group quotas for local filesystems succeeded 
Mar 24 08:13:48 rdlab16 date: Fri Mar 24 08:13:48 PST 2000 
Mar 24 08:13:48 rdlab16 rc.sysinit: Setting clock  (utc): Fri Mar 24 08:13:48 PST 2000 succeeded 
Mar 24 08:13:48 rdlab16 rc.sysinit: Enabling swap space succeeded 
Mar 24 08:13:48 rdlab16 init: Entering runlevel: 3 
Mar 24 08:13:48 rdlab16 apmd[105]: Version 3.0beta4 (APM BIOS 1.2, Linux driver 1.9) 
Mar 24 08:13:49 rdlab16 apmd: apmd startup succeeded 
Mar 24 08:13:49 rdlab16 network: Enabling IPv4 packet forwarding succeeded 
Mar 24 08:13:51 rdlab16 network: Bringing up interface lo succeeded 
Mar 24 08:13:51 rdlab16 ifup: SIOCADDRT: Network is unreachable 
Mar 24 08:13:51 rdlab16 network: Bringing up interface eth0 succeeded 
Mar 24 08:13:52 rdlab16 network: Bringing up interface eth1 succeeded 
Mar 24 08:13:52 rdlab16 portmap: portmap startup succeeded 
Mar 24 08:13:52 rdlab16 netfs: Mounting other filesystems succeeded 
Mar 24 08:13:52 rdlab16 random: Initializing random number generator succeeded 
Mar 24 08:13:54 rdlab16 crond: crond startup succeeded
Mar 24 08:13:54 rdlab16 pcmcia: Starting PCMCIA services:
Mar 24 08:13:54 rdlab16 pcmcia:  modules
Mar 24 08:13:54 rdlab16 kernel: Linux PCMCIA Card Services 3.1.11 
Mar 24 08:13:54 rdlab16 kernel:   kernel build: 2.2.5-15 #1 Mon Apr 19 22:21:09 EDT 1999 
Mar 24 08:13:54 rdlab16 kernel:   options:  [pci] [cardbus] [apm] [pnp] 
Mar 24 08:13:54 rdlab16 kernel: PCI routing table version 1.0 at 0xfdc40 
Mar 24 08:13:54 rdlab16 kernel:   unknown PCI interrupt router 1106:0586 
Mar 24 08:13:54 rdlab16 kernel: PnP: PNP BIOS installation structure at 0xc00fbea0 
Mar 24 08:13:54 rdlab16 kernel: PnP: PNP BIOS version 1.0, entry at f0000:bec8, dseg at f0000 
Mar 24 08:13:54 rdlab16 pcmcia: /lib/modules/2.2.5-15/pcmcia/i82365.o: 
Mar 24 08:13:54 rdlab16 pcmcia: invalid parameter check_pnp_irq
Mar 24 08:13:54 rdlab16 kernel: ds: no socket drivers loaded! 
Mar 24 08:13:54 rdlab16 pcmcia: 
Mar 24 08:13:54 rdlab16 pcmcia: /lib/modules/2.2.5-15/pcmcia/ds.o: 
Mar 24 08:13:54 rdlab16 pcmcia: init_module: Device or resource busy
Mar 24 08:13:54 rdlab16 pcmcia: 
Mar 24 08:13:54 rdlab16 pcmcia:  cardmgr.
Mar 24 08:13:54 rdlab16 rc: Starting pcmcia succeeded
Mar 24 08:13:54 rdlab16 cardmgr[417]: starting, version is 3.1.11
Mar 24 08:13:54 rdlab16 cardmgr[417]: no pcmcia driver in /proc/devices
Mar 24 08:13:54 rdlab16 cardmgr[417]: exiting
Mar 24 08:13:54 rdlab16 inet: inetd startup succeeded
Mar 24 08:13:55 rdlab16 named[444]: starting.  named 8.2 Wed Mar 31 10:57:12 EST 1999 ^Iroot@porky.devel.redhat.com:/usr/src/bs/BUILD/bind-8.2/src/bin/named
Mar 24 08:13:55 rdlab16 named[444]: cache zone "" (IN) loaded (serial 0)
Mar 24 08:13:55 rdlab16 named[444]: Zone "0.0.127.in-addr.arpa" (file named.local): No default TTL set using SOA minimum instead
Mar 24 08:13:55 rdlab16 named[444]: master zone "0.0.127.in-addr.arpa" (IN) loaded (serial 1997022700)
Mar 24 08:13:55 rdlab16 named[444]: listening on [127.0.0.1].53 (lo)
Mar 24 08:13:55 rdlab16 named[444]: listening on [10.10.0.1].53 (eth0)
Mar 24 08:13:55 rdlab16 named[444]: listening on [139.95.79.165].53 (eth1)
Mar 24 08:13:55 rdlab16 named[444]: Forwarding source address is [0.0.0.0].1024
Mar 24 08:13:55 rdlab16 named: named startup succeeded
Mar 24 08:13:55 rdlab16 named[445]: Ready to answer queries.
Mar 24 08:13:55 rdlab16 lpd: lpd startup succeeded
Mar 24 08:13:55 rdlab16 nfs: Starting NFS services:  succeeded
Mar 24 08:13:56 rdlab16 nfs: rpc.statd startup succeeded
Mar 24 08:13:56 rdlab16 nfs: rpc.rquotad startup succeeded
Mar 24 08:13:56 rdlab16 nfs: rpc.mountd startup succeeded
Mar 24 08:13:57 rdlab16 kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de). 
Mar 24 08:13:57 rdlab16 nfs: rpc.nfsd startup succeeded
Mar 24 08:13:57 rdlab16 dhcpd: Internet Software Consortium DHCPD $Name: V2-BETA-1-PATCHLEVEL-6 $
Mar 24 08:13:57 rdlab16 dhcpd: Copyright 1995, 1996, 1997, 1998 The Internet Software Consortium.
Mar 24 08:13:57 rdlab16 dhcpd: All rights reserved.
Mar 24 08:13:57 rdlab16 dhcpd: Internet Software Consortium DHCPD $Name: V2-BETA-1-PATCHLEVEL-6 $
Mar 24 08:13:57 rdlab16 dhcpd: Copyright 1995, 1996, 1997, 1998 The Internet Software Consortium.
Mar 24 08:13:57 rdlab16 dhcpd: Listening on Socket/eth1/139.95.79.0
Mar 24 08:13:57 rdlab16 dhcpd: Sending on   Socket/eth1/139.95.79.0
Mar 24 08:13:57 rdlab16 dhcpd: All rights reserved.
Mar 24 08:13:57 rdlab16 dhcpd: Listening on Socket/eth1/139.95.79.0
Mar 24 08:13:57 rdlab16 dhcpd: Sending on   Socket/eth1/139.95.79.0
Mar 24 08:13:57 rdlab16 dhcpd: dhcpd startup succeeded
Mar 24 08:13:58 rdlab16 keytable: Loading keymap: 
Mar 24 08:13:58 rdlab16 keytable: Loading /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
Mar 24 08:13:58 rdlab16 keytable: Loading system font: 
Mar 24 08:13:58 rdlab16 rc: Starting keytable succeeded
Mar 24 08:13:59 rdlab16 sendmail: sendmail startup succeeded
Mar 24 08:13:59 rdlab16 gpm: gpm startup succeeded
Mar 24 08:14:00 rdlab16 httpd: httpd startup succeeded
Mar 24 08:14:00 rdlab16 sound: Starting sound configuration: sound
Mar 24 08:14:00 rdlab16 rc: Starting sound succeeded
Mar 24 08:14:00 rdlab16 PAM_pwdb[628]: (su) session opened for user xfs by (uid=0)
Mar 24 08:14:01 rdlab16 pam_xauth[628]: do_file: could not create dir /etc/X11/fs/.xauth
Mar 24 08:14:01 rdlab16 PAM_pwdb[628]: (su) session closed for user xfs
Mar 24 08:14:01 rdlab16 pam_xauth[628]: do_file: could not create dir /etc/X11/fs/.xauth
Mar 24 08:14:01 rdlab16 xfs: xfs startup succeeded
Mar 24 08:14:02 rdlab16 smb: smbd startup succeeded
Mar 24 08:14:02 rdlab16 smb: nmbd startup succeeded
Mar 24 08:14:02 rdlab16 kernel: 139.95.71.220 sent an invalid ICMP error to a broadcast. 
Mar 24 08:14:02 rdlab16 kernel: 139.95.71.220 sent an invalid ICMP error to a broadcast. 
Mar 24 08:14:02 rdlab16 kernel: 139.95.73.113 sent an invalid ICMP error to a broadcast. 
Mar 24 08:14:02 rdlab16 kernel: 139.95.73.113 sent an invalid ICMP error to a broadcast. 
Mar 24 08:14:02 rdlab16 kernel: 139.95.71.220 sent an invalid ICMP error to a broadcast. 
Mar 24 08:14:02 rdlab16 kernel: 139.95.73.113 sent an invalid ICMP error to a broadcast. 
Mar 24 08:14:02 rdlab16 kernel: 139.95.71.220 sent an invalid ICMP error to a broadcast. 
Mar 24 08:14:02 rdlab16 kernel: 139.95.71.220 sent an invalid ICMP error to a broadcast. 
Mar 24 08:14:02 rdlab16 kernel: 139.95.73.113 sent an invalid ICMP error to a broadcast. 
Mar 24 08:14:02 rdlab16 kernel: 139.95.73.113 sent an invalid ICMP error to a broadcast. 
Mar 24 08:14:02 rdlab16 PAM_pwdb[661]: (su) session opened for user news by (uid=0)
Mar 24 08:14:04 rdlab16 actived[710]: started
Mar 24 08:14:04 rdlab16 innd: SERVER descriptors 1024
Mar 24 08:14:04 rdlab16 innd: SERVER outgoing 1011
Mar 24 08:14:04 rdlab16 innd: SERVER ccsetup control:14
Mar 24 08:14:04 rdlab16 innd: SERVER lcsetup localconn:16
Mar 24 08:14:04 rdlab16 innd: SERVER rcsetup remconn:5
Mar 24 08:14:04 rdlab16 innd: SERVER bad_newsfeeds no feeding sites
Mar 24 08:14:04 rdlab16 innd: SERVER perl filtering enabled
Mar 24 08:14:04 rdlab16 innd: SERVER starting
Mar 24 08:14:04 rdlab16 PAM_pwdb[661]: (su) session closed for user news
Mar 24 08:14:04 rdlab16 linuxconf: Linuxconf final setup
Mar 24 08:14:05 rdlab16 rc: Starting linuxconf succeeded
Mar 24 08:14:05 rdlab16 rc: Starting local succeeded
Mar 24 08:14:09 rdlab16 PAM_pwdb[753]: (login) session opened for user root by (uid=0)


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


The I/O port address (of 0x03e0) that pnpdump sees looks correct (according to the 
Linksys PCMCIA document).

Why am I getting a resource conflict with isapnp ?:
  isapnp.conf:41 -- Fatal - resource conflict allocating 2 bytes of IO at 3E0 (see isapnp.conf)

Any ideas on what I should try next ?

None Dump the PCIC_OPTS; some things to check

Re: Question Used pnpdump to produce isapnp.conf, still not there yet (Jeff Gembler)
Date: 2000, Mar 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> PCIC_OPTS="extra_sockets=1 check_pnp_irq=1"

check_pnp_irq is not a valid option for the i82365 module.  You also
don't need extra_sockets, unless you have multiple card readers.

/proc/bus/pccard/ioport may be a more complete map of your system IO
port usage.  You can also use "lspnp -v".

-- Dave

Question Changes to /etc/sysconfig/pcmcia and more I/O port information

Re: Question Used pnpdump to produce isapnp.conf, still not there yet (Jeff Gembler)
Date: 2000, Mar 25
From: Jeff Gembler jeffrey.gembler

I had thought that in  /etc/sysconfig/pcmcia   that I would want to use PCIC_OPTS="extra_sockets=1"
because I have a dual-slot PCMCIA reader/writer

and because the following refers to extra sockets in a docking station,
although I wasn't real clear on what that meant:

http://www.linux.ncsu.edu/LinuxDocProject/HOWTO/PCMCIA-HOWTO-2.html
2.3 Startup options
 . . .
This is not a timing issue, but if you have more than one ISA-to-PCMCIA controller in your
system or  <<<extra sockets in a docking station >>>,  the i82365 module should be loaded with the
extra_sockets parameter set to 1.  This should not be necessary for detection of PCI-to-
PCMCIA or PCI-to-CardBus bridges.


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

I made changes to  /etc/sysconfig/pcmcia

use to be:

PCMCIA="yes"
PCIC="i82365"
PCIC_OPTS="extra_sockets=1 check_pnp_irq=1"
CORE_OPTS=

now is:

PCMCIA="yes"
PCIC="i82365"
PCIC_OPTS=
CORE_OPTS=


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

/proc/bus/pccard/ioport looks like this:

0000-000f : pnp 01
0020-0021 : pnp 00
0040-0043 : pnp 02
0060-0060 : pnp 04
0061-0061 : pnp 05
0064-0064 : pnp 04
0070-0071 : pnp 03
0081-0083 : pnp 01
0087-0087 : pnp 01
0089-008b : pnp 01
008f-0091 : pnp 01
00a0-00a1 : pnp 00
00c0-00df : pnp 01
00f0-00ff : pnp 06
0208-020f : pnp 0b
02f8-02ff : pnp 0f
0378-037f : pnp 0e
03f2-03f5 : pnp 0d
03f8-03ff : pnp 0c
0480-048f : pnp 09
04d0-04d1 : pnp 09
0cf8-0cff : pnp 09
5000-507f : pnp 09
5080-50ff : pnp 09
d000-d0ff : pci 01:00.0
e000-e00f : pci 00:07.1
e400-e41f : pci 00:07.2
e800-e81f : pci 00:08.0
ec00-ec1f : pci 00:0a.0



= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

lnpnp -v results in:

00 PNP0000 AT programmable interrupt controller
        irq 2
        io 0x0020-0x0021
        io 0x00a0-0x00a1

01 PNP0200 AT DMA controller
        dma 4
        io 0x0000-0x000f
        io 0x0081-0x0083
        io 0x0087-0x0087
        io 0x0089-0x008b
        io 0x008f-0x0091
        io 0x00c0-0x00df

02 PNP0100 AT system timer
        irq 0
        io 0x0040-0x0043

03 PNP0b00 AT real-time clock
        irq 8
        io 0x0070-0x0071

04 PNP0303 IBM enhanced keyboard (101/102-key, PS/2 mouse support)
        irq 1
        io 0x0060-0x0060
        io 0x0064-0x0064

05 PNP0800 AT-style speaker sound
        io 0x0061-0x0061

06 PNP0c04 Math coprocessor
        irq 13
        io 0x00f0-0x00ff

07 PNP0c01 System board
        mem 0x00000000-0x0009ffff
        mem 0xfffe0000-0xffffffff
        mem 0x00100000-0x03ffffff

08 PNP0c02 Motherboard resources
        mem 0x000f0000-0x000f3fff
        mem 0x000f4000-0x000f7fff
        mem 0x000f8000-0x000fffff
        mem 0x000c8000-0x000c9fff

09 PNP0a03 PCI bus
        io 0x04d0-0x04d1
        io 0x0cf8-0x0cff
        io 0x0480-0x048f
        io 0x5000-0x507f
        io 0x5080-0x50ff

0a PNP0f13 PS/2 port for PS/2-style mice
        irq 12

0b PNP0c02 Motherboard resources
        io 0x0208-0x020f

0c PNP0501 16550A-compatible COM port
        irq 4
        io 0x03f8-0x03ff

0d PNP0700 PC standard floppy disk controller
        dma 2
        io 0x03f2-0x03f5
        irq 6

0e PNP0400 Standard LPT printer port
        irq 7
        io 0x0378-0x037f

0f PNP0501 16550A-compatible COM port
        irq 3
        io 0x02f8-0x02ff



= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

I still get the same message when I use   isapnp


# isapnp isapnp.conf

Board 1 has Identity 21 05 00 00 00 18 30 21 59:  VIA3018 Serial No 83886080 [checksum 21]
isapnp.conf:41 -- Fatal - resource conflict allocating 2 bytes of IO at 3E0 (see isapnp.conf)
isapnp.conf:41 -- Fatal - Error occurred executing request '<IORESCHECK> ' --- further action aborted



= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

I still don't see the conflict.
I'm wondering if I should be looking at disabling or enabling PNP at another level.

None More things to try

Re: Question Changes to /etc/sysconfig/pcmcia and more I/O port information (Jeff Gembler)
Date: 2000, Apr 04
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'm not sure what the problem is.  The obvious things I would do are:

-- before you uncommented out the IO resource line, when you ran
   isapnp, you got an "Enabled OK" message.  Run "probe" now and see
   if it finds anything.

-- not for any good reason, I'd try removing the "(CHECK)" from that
   IO resource line in the isapnp.conf file.  Because I know there
   should be no conflict, and because the error message is complaining
   about an IORESCHECK error.  The isapnp FAQ also suggests this.

-- Dave

None Getting close, get two beeps on inserting PCMCIA card, but can't ping

Re: Question Install and config of Linksys desktop PCMRDWR reader writer and PCM100H1 card (Jeff Gembler)
Date: 2000, Apr 05
From: Jeff Gembler jeffrey.gembler

/*****************************************************************************
*  CONTENTS OF THIS POSTING
*
*  NOTES
*   1) Changes made to files
*   2) Two High beeps
*   3) Output of probe command
*   4) Ping command
* 
* 
*  COMMAND OUTPUT
*    probe -v
*    probe -m
*    lsmod
*    ifconfig
*    ifconfig -a      (same as ifconfig)
*    cardctl config
*    cardctl ident
*    ping
* 
* 
*  FILE LISTINGS
*    isapnp.conf
*    resolv.conf
*    conf.modules
*    network.opts
*    pcmcia
*    modules
*    ioports
*    devices
*    interrupts
*    stab
*    messages
* 
*****************************************************************************/


/*=============================================================================
===  NOTES
===============================================================================

1) CHANGES MADE TO FILES
   In the file  /etc/isapnp.conf
   I removed the "(CHECK)" from the IO resource line

2) TWO HIGH BEEPS
   Now,  I get two high beeps  (not a high and a low).     Progress !!!
   The beeps happen 
     -  when I insert the Linksys PCM100H1 PCMCIA card into the 
        Linksys PCMRDWR reader/writer,  and
     -  on booting of Linux and starting PCMCIA services

3) OUTPUT OF probe -v COMMAND    (perhaps a trivial note)
   The output of the probe -v command is different now.
   It used to list information for
     -  PCI bridge probe:
     -  Intel PCIC probe: 
     -  Databook TCID-2 probe:

   Now it just lists information for:
     -  PCI bridge probe:
     -  Intel PCIC probe: 
   Maybe that is because it stops after finding something 
   (something other than "not found").

4) THE ping COMMAND
   Looks like I'm getting close (because now I get the two high beeps).

   Ping still doesn't work.
   The PC with the Linksys PCM100H1 PCMCIA card interfaces to a small local
   HPNA network,  of 3 PCs total.
   The other two PCs (they have PCI NICs for HPNA) can ping each other,
   but the PC with the PCMCIA interface can't ping or be pinged.

   From what I've read,  the /etc/pcmcia/network.opts  file should be suspect.


   The details of command outputs (including ping) and several file 
   listings are shown below.



/*=============================================================================
===  COMMAND OUTPUT
===============================================================================



===   OUTPUT OF  probe -v   ===================================================

PCI bridge probe: not found.
Intel PCIC probe: 
  ident(0)=0x82  ident(1)=0x82
  VIA VT83C469 found, 2 sockets.


===   OUTPUT OF  probe -m   ===================================================

i82365


===   OUTPUT OF  lsmod     ====================================================

Module                  Size  Used by
pcnet_cs                8248   1 
8390                    5892   0  [pcnet_cs]
ds                      6088   2  [pcnet_cs]
i82365                 20396   2 
pcmcia_core            42624   0  [pcnet_cs ds i82365]
pcnet32                 9628   2  (autoclean)


===   OUTPUT OF  ifconfig   ===================================================

eth0      Link encap:Ethernet  HWaddr 00:90:00:03:BB:10  
          inet addr:10.10.0.1  Bcast:10.255.255.255  Mask:255.0.0.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:5 Base address:0xe800 

eth1      Link encap:Ethernet  HWaddr 00:00:1A:18:42:C3  
          inet addr:139.95.79.165  Bcast:139.95.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18357 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:10 Base address:0xec00 

eth2      Link encap:Ethernet  HWaddr 00:E0:98:77:32:ED  
          inet addr:10.20.0.1  Bcast:10.20.255.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:3 Base address:0x300 

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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 


===   OUTPUT OF  ifconfig -a    (same as ifconfig)   ==========================

eth0      Link encap:Ethernet  HWaddr 00:90:00:03:BB:10  
          inet addr:10.10.0.1  Bcast:10.255.255.255  Mask:255.0.0.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:5 Base address:0xe800 

eth1      Link encap:Ethernet  HWaddr 00:00:1A:18:42:C3  
          inet addr:139.95.79.165  Bcast:139.95.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19190 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:10 Base address:0xec00 

eth2      Link encap:Ethernet  HWaddr 00:E0:98:77:32:ED  
          inet addr:10.20.0.1  Bcast:10.20.255.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:3 Base address:0x300 

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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 


===   OUTPUT OF  cardctl config   =============================================

Socket 0:
  Vcc 5.0V  Vpp1 0.0V  Vpp2 0.0V
  interface type is "memory and I/O"
  irq 3 [exclusive] [level]
  function 0:
    config base 0x0400
      option 0x50
    io 0x0300-0x031f [auto]
Socket 1:
  not configured


===   OUTPUT OF  cardctl ident   ==============================================

Socket 0:
  product info: "Linksys", "HomeLink Phoneline + 10/100 Network PC Card (PCM100H1)", "1.0", " "
  manfid: 0x0149, 0xc1ab
  function: 6 (network)
Socket 1:
  no product info available


===   OUTPUT OF  ping   =======================================================

[root@rdlab16 /etc]# ping 10.20.0.3
PING 10.20.0.3 (10.20.0.3) from 10.20.0.1 : 56(84) bytes of data.
From 10.20.0.1: Destination Host Unreachable
From 10.20.0.1: Destination Host Unreachable
From 10.20.0.1: Destination Host Unreachable

--- 10.20.0.3 ping statistics ---
5 packets transmitted, 0 packets received, +3 errors, 100% packet loss
[root@rdlab16 /etc]# 
[root@rdlab16 /etc]# 


 
/*=============================================================================
===  FILE LISTINGS
===============================================================================


===  FILE LISTING FOR   /etc/isapnp.conf   ====================================

# $Id: pnpdump.c,v 1.18 1999/02/14 22:47:18 fox Exp $
# This is free software, see the sources for details.
# This software has NO WARRANTY, use at your OWN RISK
#
# For details of this file format, see isapnp.conf(5)
#
# For latest information and FAQ on isapnp and pnpdump see:
# http://www.roestock.demon.co.uk/isapnptools/
#
# Compiler flags: -DREALTIME -DNEEDSETSCHEDULER -DABORT_ONRESERR
#
# Trying port address 0203
# Board 1 has serial identifier 21 05 00 00 00 18 30 21 59

# (DEBUG)
(READPORT 0x0203)
(ISOLATE PRESERVE)
(IDENTIFY *)
(VERBOSITY 2)
(CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING

# Card 1: (serial identifier 21 05 00 00 00 18 30 21 59)
# Vendor Id VIA3018, Serial Number 83886080, checksum 0x21.
# Version 1.0, Vendor version 0.0
# ANSI string -->VIA PCMCIA CARD<--
#
# Logical device id PNP0e00
#     Device support I/O range check register
#
# Edit the entries below to uncomment out the configuration required.
# Note that only the first value of any range is given, this may be changed if required
# Don't forget to uncomment the activate (ACT Y) when happy

(CONFIGURE VIA3018/83886080 (LD 0
#     Compatible device id PNP0e00
#     Logical device decodes 16 bit IO address lines
#         Minimum IO base address 0x03e0
#         Maximum IO base address 0x03e3
#         IO base alignment 2 bytes
#         Number of IO addresses required: 2
(IO 0 (SIZE 2) (BASE 0x03e0) )
 (NAME "VIA3018/83886080[0]{VIA PCMCIA CARD     }")
(ACT Y)
))
# End tag... Checksum 0x00 (OK)

# Returns all cards to the "Wait for Key" state
(WAITFORKEY)



===  FILE LISTING FOR   /etc/resolv.conf   ====================================

search amd.com 
nameserver 139.95.6.235
nameserver 139.95.27.235



===  FILE LISTING FOR   /etc/conf.modules   ===================================

alias eth0 pcnethme 
alias eth1 pcnet32 



===  FILE LISTING FOR   /etc/pcmcia/network.opts    ===========================

# Network adapter configuration
#
# The address format is "scheme,socket,instance,hwaddr".
#
# Note: the "network address" here is NOT the same as the IP address.
# See the Networking HOWTO.  In short, the network address is the IP
# address masked by the netmask.
#
case "$ADDRESS" in
*,*,*,*)
    INFO="Sample private network setup"
    # Transceiver selection, for some cards -- see 'man ifport'
    IF_PORT=""
    # Use BOOTP (via /sbin/bootpc, or /sbin/pump)? [y/n]
    BOOTP="n"
    # Use DHCP (via /sbin/dhcpcd, /sbin/dhclient, or /sbin/pump)? [y/n]
    DHCP="n"
    # Host's IP address, netmask, network address, broadcast address
    IPADDR="10.20.0.1"
    NETMASK="255.255.255.0"
    NETWORK="10.20.0.0"
    BROADCAST="10.20.255.255"
    # Gateway address for static routing
    GATEWAY="10.20.0.1"
    # Things to add to /etc/resolv.conf for this interface
    DOMAIN=""
    SEARCH=""
    DNS_1=""
    DNS_2=""
    DNS_3=""
    # NFS mounts, should be listed in /etc/fstab
    MOUNTS=""
    # For IPX interfaces, the frame type and network number
    IPX_FRAME=""
    IPX_NETNUM=""
    # Extra stuff to do after setting up the interface
    start_fn () { return; }
    # Extra stuff to do before shutting down the interface
    stop_fn () { return; }
    ;;
esac



===  FILE LISTING FOR   /etc/sysconfig/pcmcia    ==============================

PCMCIA=yes
PCIC=i82365
PCIC_OPTS=
CORE_OPTS=



===  FILE LISTING FOR   /proc/modules    ======================================

pcnet_cs                8248   1
8390                    5892   0 [pcnet_cs]
ds                      6088   2 [pcnet_cs]
i82365                 20396   2
pcmcia_core            42624   0 [pcnet_cs ds i82365]
pcnet32                 9628   2 (autoclean)



===  FILE LISTING FOR   /proc/ioports   =======================================

0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0300-031f : pcnet_cs
0376-0376 : ide1
03c0-03df : vga+
03e0-03e1 : i82365
03f6-03f6 : ide0
03f8-03ff : serial(auto)
e000-e007 : ide0
e008-e00f : ide1
e800-e81f : PCnet/Home 79C978
ec00-ec1f : PCnet/FAST+ 79C972



===  FILE LISTING FOR   /proc/devices   =======================================

Character devices:
  1 mem
  2 pty
  3 ttyp
  4 ttyS
  5 cua
  7 vcs
 10 misc
 29 fb
 36 netlink
128 ptm
136 pts
162 raw
254 pcmcia

Block devices:
  1 ramdisk
  2 fd
  3 ide0
  9 md
 22 ide1



===  FILE LISTING FOR   /proc/interrupts   ====================================

           CPU0       
  0:      71401          XT-PIC  timer
  1:       3202          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  3:          3          XT-PIC  pcnet_cs
  5:          4          XT-PIC  PCnet/Home 79C978
  8:          1          XT-PIC  rtc
 10:       9280          XT-PIC  PCnet/FAST+ 79C972
 12:       8201          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:      92367          XT-PIC  ide0
 15:       3703          XT-PIC  ide1
NMI:          0



===  FILE LISTING FOR   /var/state/pcmcia/stab    =============================

Socket 0: NE2000 Compatible Ethernet
0	network	pcnet_cs	0	eth2
Socket 1: empty



===  FILE LISTING FOR   /var/log/messages    ==================================

Apr  4 18:31:43 rdlab16 gnome-name-server[676]: input condition is: 0x10, exiting
Apr  4 18:31:44 rdlab16 rc: Stopping keytable succeeded
Apr  4 18:31:44 rdlab16 Font Server[568]: terminating 
Apr  4 18:31:44 rdlab16 xfs: xfs shutdown succeeded
Apr  4 18:31:44 rdlab16 gpm: Shutting down gpm mouse services: 
Apr  4 18:31:44 rdlab16 gpm: gpm
Apr  4 18:31:44 rdlab16 rc: Stopping gpm succeeded
Apr  4 18:31:45 rdlab16 httpd: httpd shutdown succeeded
Apr  4 18:31:45 rdlab16 sendmail: sendmail shutdown succeeded
Apr  4 18:31:45 rdlab16 inet: inetd shutdown succeeded
Apr  4 18:31:46 rdlab16 atd: atd shutdown succeeded
Apr  4 18:31:46 rdlab16 crond: crond shutdown succeeded
Apr  4 18:31:46 rdlab16 lpd: lpd shutdown succeeded
Apr  4 18:31:46 rdlab16 dd: 1+0 records in
Apr  4 18:31:46 rdlab16 dd: 1+0 records out
Apr  4 18:31:46 rdlab16 random: Saving random seed succeeded
Apr  4 18:31:47 rdlab16 apmd: apmd shutdown succeeded
Apr  4 18:31:47 rdlab16 portmap: portmap shutdown succeeded
Apr  4 18:31:47 rdlab16 network: Shutting down interface eth0 succeeded
Apr  4 18:31:47 rdlab16 network: Shutting down interface eth1 succeeded
Apr  4 18:31:47 rdlab16 network: Disabling IPv4 automatic defragmentation succeeded
Apr  4 18:31:47 rdlab16 pcmcia: Shutting down PCMCIA services:
Apr  4 18:31:47 rdlab16 cardmgr[432]: executing: './network check eth2'
Apr  4 18:31:47 rdlab16 pcmcia:  cardmgr
Apr  4 18:31:47 rdlab16 cardmgr[432]: shutting down socket 0
Apr  4 18:31:47 rdlab16 cardmgr[432]: executing: './network stop eth2'
Apr  4 18:31:48 rdlab16 cardmgr[432]: executing: 'rmmod pcnet_cs'
Apr  4 18:31:48 rdlab16 cardmgr[432]: executing: 'rmmod 8390'
Apr  4 18:31:48 rdlab16 cardmgr[432]: exiting
Apr  4 18:31:49 rdlab16 pcmcia:  modules
Apr  4 18:31:49 rdlab16 kernel: unloading PCMCIA Card Services 
Apr  4 18:31:49 rdlab16 pcmcia: .
Apr  4 18:31:49 rdlab16 rc: Stopping pcmcia succeeded
Apr  4 18:31:50 rdlab16 kernel: Kernel logging (proc) stopped.
Apr  4 18:31:50 rdlab16 kernel: Kernel log daemon terminating.



Apr  4 18:31:51 rdlab16 syslog: klogd shutdown succeeded
Apr  4 18:31:51 rdlab16 exiting on signal 15
Apr  4 18:32:46 rdlab16 syslogd 1.3-3: restart.
Apr  4 18:32:46 rdlab16 syslog: syslogd startup succeeded
Apr  4 18:32:46 rdlab16 syslog: klogd startup succeeded
Apr  4 18:32:46 rdlab16 kernel: klogd 1.3-3, log source = /proc/kmsg started.
Apr  4 18:32:46 rdlab16 kernel: Inspecting /boot/System.map-2.2.12-20
Apr  4 18:32:46 rdlab16 kernel: Loaded 6870 symbols from /boot/System.map-2.2.12-20.
Apr  4 18:32:46 rdlab16 kernel: Symbols match kernel version 2.2.12.
Apr  4 18:32:47 rdlab16 kernel: Loaded 1 symbol from 1 module.
Apr  4 18:32:47 rdlab16 kernel: Linux version 2.2.12-20 (root@porky.devel.redhat.com) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Sep 27 10:25:54 EDT 1999 
Apr  4 18:32:47 rdlab16 kernel: Detected 451036188 Hz processor. 
Apr  4 18:32:47 rdlab16 kernel: Console: colour VGA+ 80x25 
Apr  4 18:32:47 rdlab16 kernel: Calibrating delay loop... 897.84 BogoMIPS 
Apr  4 18:32:47 rdlab16 kernel: Memory: 62780k/65536k available (1008k kernel code, 412k reserved, 992k data, 64k init) 
Apr  4 18:32:47 rdlab16 kernel: DENTRY hash table entries: 262144 (order: 9, 2097152 bytes) 
Apr  4 18:32:47 rdlab16 kernel: Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes) 
Apr  4 18:32:47 rdlab16 kernel: Page-cache hash table entries: 16384 (order: 4, 65536 bytes) 
Apr  4 18:32:47 rdlab16 kernel: VFS: Diskquotas version dquot_6.4.0 initialized 
Apr  4 18:32:47 rdlab16 kernel: CPU: AMD AMD-K6(tm) 3D processor stepping 0c 
Apr  4 18:32:47 rdlab16 kernel: Checking 386/387 coupling... OK, FPU using exception 16 error reporting. 
Apr  4 18:32:47 rdlab16 kernel: Checking 'hlt' instruction... OK. 
Apr  4 18:32:47 rdlab16 kernel: POSIX conformance testing by UNIFIX 
Apr  4 18:32:47 rdlab16 kernel: mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au) 
Apr  4 18:32:47 rdlab16 kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb290 
Apr  4 18:32:47 rdlab16 kernel: PCI: Using configuration type 1 
Apr  4 18:32:47 rdlab16 kernel: PCI: Probing PCI hardware 
Apr  4 18:32:47 rdlab16 kernel: PCI: 00:38 [1106/0586]: Work around ISA DMA hangs (00) 
Apr  4 18:32:47 rdlab16 kernel: Activating ISA DMA hang workarounds. 
Apr  4 18:32:47 rdlab16 kernel: Linux NET4.0 for Linux 2.2 
Apr  4 18:32:47 rdlab16 kernel: Based upon Swansea University Computer Society NET3.039 
Apr  4 18:32:47 rdlab16 kernel: NET4: Unix domain sockets 1.0 for Linux NET4.0. 
Apr  4 18:32:47 rdlab16 kernel: NET4: Linux TCP/IP 1.0 for NET4.0 
Apr  4 18:32:47 rdlab16 kernel: IP Protocols: ICMP, UDP, TCP, IGMP 
Apr  4 18:32:47 rdlab16 kernel: TCP: Hash tables configured (ehash 65536 bhash 65536) 
Apr  4 18:32:47 rdlab16 kernel: Initializing RT netlink socket 
Apr  4 18:32:47 rdlab16 kernel: Starting kswapd v 1.5  
Apr  4 18:32:47 rdlab16 kernel: Detected PS/2 Mouse Port. 
Apr  4 18:32:47 rdlab16 kernel: Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled 
Apr  4 18:32:47 rdlab16 kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A 
Apr  4 18:32:47 rdlab16 kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A 
Apr  4 18:32:47 rdlab16 kernel: pty: 256 Unix98 ptys configured 
Apr  4 18:32:47 rdlab16 kernel: apm: BIOS version 1.2 Flags 0x07 (Driver version 1.9) 
Apr  4 18:32:47 rdlab16 kernel: Real Time Clock Driver v1.09 
Apr  4 18:32:47 rdlab16 kernel: RAM disk driver initialized:  16 RAM disks of 4096K size 
Apr  4 18:32:47 rdlab16 kernel: VP_IDE: IDE controller on PCI bus 00 dev 39 
Apr  4 18:32:47 rdlab16 kernel: VP_IDE: not 100% native mode: will probe irqs later 
Apr  4 18:32:47 rdlab16 kernel:     ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA 
Apr  4 18:32:47 rdlab16 kernel:     ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA 
Apr  4 18:32:47 rdlab16 kernel: hda: QUANTUM FIREBALL EX3.2A, ATA DISK drive 
Apr  4 18:32:47 rdlab16 kernel: hdc: CD-ROM 40X/AKU, ATAPI CDROM drive 
Apr  4 18:32:47 rdlab16 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 
Apr  4 18:32:47 rdlab16 kernel: ide1 at 0x170-0x177,0x376 on irq 15 
Apr  4 18:32:47 rdlab16 kernel: hda: QUANTUM FIREBALL EX3.2A, 3079MB w/418kB Cache, CHS=782/128/63 
Apr  4 18:32:47 rdlab16 kernel: hdc: ATAPI 40X CD-ROM drive, 128kB Cache 
Apr  4 18:32:47 rdlab16 kernel: Uniform CDROM driver Revision: 2.56 
Apr  4 18:32:47 rdlab16 kernel: Floppy drive(s): fd0 is 1.44M 
Apr  4 18:32:47 rdlab16 kernel: FDC 0 is a post-1991 82077 
Apr  4 18:32:47 rdlab16 kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 
Apr  4 18:32:47 rdlab16 kernel: raid5: measuring checksumming speed 
Apr  4 18:32:47 rdlab16 kernel: raid5: MMX detected, trying high-speed MMX checksum routines 
Apr  4 18:32:47 rdlab16 kernel:    pII_mmx   :   958.215 MB/sec 
Apr  4 18:32:47 rdlab16 kernel:    p5_mmx    :   838.581 MB/sec 
Apr  4 18:32:47 rdlab16 kernel:    8regs     :   650.748 MB/sec 
Apr  4 18:32:47 rdlab16 kernel:    32regs    :   454.152 MB/sec 
Apr  4 18:32:47 rdlab16 kernel: using fastest function: pII_mmx (958.215 MB/sec) 
Apr  4 18:32:47 rdlab16 kernel: scsi : 0 hosts. 
Apr  4 18:32:47 rdlab16 kernel: scsi : detected total. 
Apr  4 18:32:47 rdlab16 kernel: md.c: sizeof(mdp_super_t) = 4096 
Apr  4 18:32:47 rdlab16 kernel: Partition check: 
Apr  4 18:32:47 rdlab16 kernel:  hda: hda1 hda2 < hda5 hda6 > 
Apr  4 18:32:47 rdlab16 kernel: RAMDISK: Compressed image found at block 0 
Apr  4 18:32:47 rdlab16 kernel: autodetecting RAID arrays 
Apr  4 18:32:47 rdlab16 kernel: autorun ... 
Apr  4 18:32:47 rdlab16 kernel: ... autorun DONE. 
Apr  4 18:32:47 rdlab16 kernel: VFS: Mounted root (ext2 filesystem). 
Apr  4 18:32:47 rdlab16 kernel: autodetecting RAID arrays 
Apr  4 18:32:47 rdlab16 kernel: autorun ... 
Apr  4 18:32:47 rdlab16 kernel: ... autorun DONE. 
Apr  4 18:32:47 rdlab16 kernel: VFS: Mounted root (ext2 filesystem) readonly. 
Apr  4 18:32:47 rdlab16 kernel: change_root: old root has d_count=1 
Apr  4 18:32:47 rdlab16 kernel: Trying to unmount old root ... okay 
Apr  4 18:32:47 rdlab16 kernel: Freeing unused kernel memory: 64k freed 
Apr  4 18:32:47 rdlab16 kernel: Adding Swap: 100760k swap-space (priority -1) 
Apr  4 18:32:47 rdlab16 kernel: pcnet32.c: PCI bios is present, checking for devices... 
Apr  4 18:32:47 rdlab16 kernel: Found PCnet/PCI at 0xe800, irq 5. 
Apr  4 18:32:47 rdlab16 kernel: eth0: PCnet/Home 79C978 at 0xe800, 00 90 00 03 bb 10 assigned IRQ 5. 
Apr  4 18:32:47 rdlab16 kernel: pcnet32.c:v1.23 6.7.1999 tsbogend@alpha.franken.de 
Apr  4 18:32:47 rdlab16 kernel: PCI Master Bit has not been set. Setting... 
Apr  4 18:32:47 rdlab16 kernel: Found PCnet/PCI at 0xec00, irq 10. 
Apr  4 18:32:47 rdlab16 kernel: eth1: PCnet/FAST+ 79C972 at 0xec00, 00 00 1a 18 42 c3 assigned IRQ 10. 
Apr  4 18:32:47 rdlab16 kernel: pcnet32.c:v1.23 6.7.1999 tsbogend@alpha.franken.de 
Apr  4 18:32:47 rdlab16 atd: atd startup succeeded
Apr  4 18:32:47 rdlab16 crond: crond startup succeeded
Apr  4 18:32:48 rdlab16 pcmcia: Starting PCMCIA services:
Apr  4 18:32:48 rdlab16 pcmcia:  modules
Apr  4 18:32:48 rdlab16 kernel: Linux PCMCIA Card Services 3.1.11 
Apr  4 18:32:48 rdlab16 kernel:   kernel build: 2.2.12-20 #1 Mon Sep 27 10:25:54 EDT 1999 
Apr  4 18:32:48 rdlab16 kernel:   options:  [pci] [cardbus] [apm] 
Apr  4 18:32:48 rdlab16 kernel: PCI routing table version 1.0 at 0xfdc40 
Apr  4 18:32:48 rdlab16 kernel:   unknown PCI interrupt router 1106:0586 
Apr  4 18:32:48 rdlab16 kernel: Intel PCIC probe:  
Apr  4 18:32:48 rdlab16 kernel:   VIA VT83C469 ISA-to-PCMCIA at port 0x3e0 ofs 0x00 
Apr  4 18:32:48 rdlab16 kernel:     host opts [0]: [ring] 
Apr  4 18:32:48 rdlab16 kernel:     host opts [1]: [ring] 
Apr  4 18:32:48 rdlab16 kernel:     ISA irqs (default) = 3,4,7,9,12 polling interval = 1000 ms 
Apr  4 18:32:48 rdlab16 pcmcia:  cardmgr.
Apr  4 18:32:48 rdlab16 rc: Starting pcmcia succeeded
Apr  4 18:32:48 rdlab16 cardmgr[430]: starting, version is 3.1.11
Apr  4 18:32:48 rdlab16 cardmgr[430]: watching 2 sockets
Apr  4 18:32:48 rdlab16 kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Apr  4 18:32:48 rdlab16 kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7 
Apr  4 18:32:48 rdlab16 kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Apr  4 18:32:48 rdlab16 inet: inetd startup succeeded
Apr  4 18:32:48 rdlab16 cardmgr[430]: initializing socket 0
Apr  4 18:32:48 rdlab16 cardmgr[430]: socket 0: NE2000 Compatible Ethernet
Apr  4 18:32:48 rdlab16 kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
Apr  4 18:32:48 rdlab16 lpd: lpd startup succeeded
Apr  4 18:32:48 rdlab16 cardmgr[430]: executing: 'insmod /lib/modules/2.2.12-20/net/8390.o'
Apr  4 18:32:48 rdlab16 cardmgr[430]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/pcnet_cs.o'
Apr  4 18:32:49 rdlab16 kernel: eth2: NE2000 Compatible: io 0x300, irq 3, hw_addr 00:E0:98:77:32:ED 
Apr  4 18:32:49 rdlab16 cardmgr[430]: executing: './network start eth2'
Apr  4 18:32:49 rdlab16 keytable: Loading keymap: Loading system font: 
Apr  4 18:32:49 rdlab16 rc: Starting keytable succeeded
Apr  4 18:32:50 rdlab16 sendmail: sendmail startup succeeded
Apr  4 18:32:50 rdlab16 gpm: gpm startup succeeded
Apr  4 18:32:51 rdlab16 httpd: httpd startup succeeded
Apr  4 18:32:51 rdlab16 xfs: xfs startup succeeded
Apr  4 18:32:52 rdlab16 linuxconf: Linuxconf final setup
Apr  4 18:32:52 rdlab16 xfs: Warning: The directory "/usr/X11R6/lib/X11/fonts/100dpi" does not exist. 
Apr  4 18:32:52 rdlab16 xfs:          Entry deleted from font path. 
Apr  4 18:32:53 rdlab16 rc: Starting linuxconf succeeded
Apr  4 18:32:59 rdlab16 PAM_pwdb[606]: (login) session opened for user root by LOGIN(uid=0)

None I think you're right: bad network configuration

Re: None Getting close, get two beeps on inserting PCMCIA card, but can't ping (Jeff Gembler)
Date: 2000, Apr 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Your network configuration appears to be messed up.  eth0 has a mask
of 255.0.0.0, so it should capture addresses that match 10.*.*.*.
eth2, however, is also on the 10.*.*.* network.  And the broadcast and
netmask for eth2 are inconsistent: you have 10.20.255.255 and
255.255.255.0, but only the following combinations are legal:
10.20.255.255 and 255.255.0.0, or 10.20.0.255 and 255.255.255.0.

-- Dave

None Linksys PCM100H1 Ethernet connection works, but not HPNA

Re: Question Install and config of Linksys desktop PCMRDWR reader writer and PCM100H1 card (Jeff Gembler)
Date: 2000, Apr 05
From: Jeff Gembler jeffrey.gembler

Getting real close now.

I changed the IP addresses so that 

  -  On the Linux PC,  the Linksys PCMCIA card Model No. PCM100H1  has an IP address  
     of  172.16.0.1       ( instead of 10.20.0.1 )

  -  the Win 98 PC that I’m trying to ping has a Diamond Mulmedia  Eth / HPNA card,   
     I set the IP address there to  172.16.0.3

The Ethernet connection works,  both PCs can ping each other.

The HPNA connection does not work.  I unplug the Eth cable from both PCs and plug in the 
HPNA phone  line  (straight thru phone line).    When I try the pings with HPNA I get the 
destination host unreachable message.

Note:  The HPNA connection on the Win 98 machine does work with another Win 98 machine.


Does the Linksys PCM100H1 card need to be,  or can it be,   configured to auto-select the interface ?
Or can it be set to be HPNA only ?    
From Linux ?

From reading the Linksys documentation,  I had thought and hoped that the 
interface would auto-select.

None For HPNA, you are in uncharted territory

Re: None Linksys PCM100H1 Ethernet connection works, but not HPNA (Jeff Gembler)
Date: 2000, Apr 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I don't know how the HPNA stuff works.  I also thought that the card
autoselected the interface; I don't have a setup where I can test it.

-- Dave

Question Can I do something to get HPNA to work ?

Re: None Linksys PCM100H1 Ethernet connection works, but not HPNA (Jeff Gembler)
Date: 2000, Apr 06
From: Jeff Gembler jeffrey.gembler

I have another Linksys PCMRDWR reader / writer,   so I installed it into a Win 98 machine.
With the Linksys PCM100H1 PCMCIA card inserted,   I installed drivers for the reader / writer  and  card.
Also setup the IP address for the PCMCIA card.

The HPNA part of the card worked fine under Win 98.
Using the PCMCIA HPNA connection I was able to get two Win 98 PCs to ping each other.


Under  Network Neighborhood,  Properties,  Linksys PCMCIA TCP/IP,  Advanced Tab
there are settings for:

  Connection Type
     100 Mbps
     100 Mbps Full Duplex
     10 Mbps 
     10 Mbps Full Duplex
     Auto Sense
     HomeLAN

  Phone Line Config
     Auto Config
     High Power / High Speed (HPH         // line was truncated
     High Power / Low Speed (HPLS        //
     Low Power / High Speed (LPHS        //

I selected  Connection Type = Auto Sense,     Phone Line Config = Auto Config


Is there any way for me to configure this  ( Auto Sense / Auto Config )  under Linux ?
Or a way, at least for now, to write to registers, without using a config file ?

Do I have a chance of modifying the code to add this,  if it isn’t already there ?

Did you use a technical reference manual/spec in writing the code for the 
Linksys PCM100H1 PCMCIA card ?

None I don't have any specs for the HomeLink

Re: Question Can I do something to get HPNA to work ? (Jeff Gembler)
Date: 2000, Apr 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I have specs for the 16-bit 10/100 EtherFast cards, but that's all.
So I don't know how to explicitly enable the HomePNA transceiver.

-- Dave

Question Memory probe failures with kernels somewhat later 2.3.28

Date: 2000, Feb 29
From: Lutz <urc8@rz.DO_NOT_SPAM_ME.uni-karlsruhe.de>

I need some help. I have got kernel 2.3.28 up and running 
without problems, using pcmcia 3.1.11. /proc/iomem tells me:

20000000-20000fff : Texas Instruments PCI1131
  20000000-20000fff : i82365
20001000-20001fff : Texas Instruments PCI1131 (#2)
  20001000-20001fff : i82365
a0000000-a0000fff : card services

When I now try kernel 2.3.48 with modularized pcmcia (else apm
problems, see my post there), neither my NE2000 compatible
network card (8390) nor my scsi card (aha152x_cs) are no
longer accepted. The modules pcmcia_core, i82365, and ds
are loaded without problems. Inserting the card, all I get is
a high and low beep and /var/state/pcmcia/stab tells me that 
there is Anonyous Memory. I tried one memory range after
another:

0xd0000-0xdffff
0xc0000-0xcffff
(...)
0xa0000000-0xa0ffffff
0x60000000-0x60ffffff

I don't understand why even the 0xa0000000-0xa0ffffff range
is no longer accepted...

Why? Thank you for any hint...

More Problem no longer there...

Re: Question Memory probe failures with kernels somewhat later 2.3.28 (Lutz)
Date: 2000, Mar 01
From: Lutz <urc8@rz.DO_NOT_SPAM_ME.uni-karlsruhe.de>

Sorry for having bothered you. Today, I tried it once again, 
and (I really changed nothing!) suddenly the card services are
at 000d0000-000dffff. I don't understand. I have no idea why 
it did not work a few days ago...

But nevertheless, thank you for the pcmcia package!

Sad IRQ 11 wedged with 3.1.11/3.1.12 on Dell Inspiron 5000

Date: 2000, Mar 10
From: Scott Porter porter

Hi.

I have a peculiar problem with my Dell Inspiron 5000 running Redhat 6.1/kernel 2.1.14 (TI PCI-1225). I've tried running PCMCIA 3.1.11 and 3.1.12 with PNP on/off and I seem to be able to only use socket 0. Nothing happens when I insert a card in socket 1. The pcmcia drivers report that IRQ 11 is wedged and that the IRQ scan failed. Any help would be appreciated. Here is the log:

Linux PCMCIA Card Services 3.1.12
  kernel build: 2.2.14 #4 Tue Mar 7 23:26:06 EST 2000
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xfdf50
  00:04.0 -> irq 11
  00:04.1 -> irq 11
Intel PCIC probe: 
  TI 1225 PCI-to-CardBus at slot 00:04, mem 0x68000000
    host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 168/32] [bus 32/34]
    host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat 168/32] [bus 35/37]
    PCI irq 11 seems to be wedged!
    PCI irq 11 test failed
    ISA irqs (scanned) = 3,4,7,9,10 polling interval = 1000 ms
cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.

Anybody know what is going on? Thanks!

                        -- Scott.

None The wedged irq is not the main problem, anyway

Re: Sad IRQ 11 wedged with 3.1.11/3.1.12 on Dell Inspiron 5000 (Scott Porter)
Date: 2000, Mar 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The "PCI irq seems to be wedged!" message is telling you that a rogue
device is sharing that PCI interrupt, and is holding that interrupt
active, even though the driver for that device isn't loaded.  So the
PCMCIA drivers can't use the PCI interrupt: it will be continuously
triggered until that rogue device (whatever it is) is told to stop.

The wedged PCI interrupt is not really a problem, because the i82365
driver will automatically use ISA interrupts instead.  It does not
explain why one socket would not work.

If you insert a card in socket 1, what does "cardctl status" say?  You
say "nothing happens", so I assume you don't hear any beeps at all.
Does anything happen if you issue a "cardctl insert" command?

After a cold boot, with no cards inserted, can you also send me the
contents of /proc/bus/pccard/00/pci and /proc/bus/pccard/01/pci?

-- Dave

Question Was this ever resolved?

Re: None The wedged irq is not the main problem, anyway (David Hinds)
Date: 2000, Apr 02
From: John Ruttenberg rutt

I'm having similar problems.

Sad System hangs when starting pcmcia service...

Date: 2000, Mar 12
From: Eric Maes <eric.maes@wol.be>

Hi, I just downloaded version 3.1.12 of the pcmcia drivers and compiled it without a problem on my RedHat 6.1 system running kernel 2.2.12-20. I am using the PCMCIA-ISA adapter that came with my Webgear Aviator card. When I start the pcmcia service, my system completely hangs. First I thought this might be an IRQ issue, so I removed my SCSI adapter card (which I was not using anyway at the moment) and forced the driver to only probe for IRQ 12 which the card used (PCIC_OPTS='irq_list=12"), but the sysem still hangs. Here is part of /var/adm/messages (this still shows the original output (before I forced the IRQ). When my system hang, it probably trashed the messages file and I had to run fsck upon reboot...

Mar 12 17:32:48 bilbo kernel: Linux PCMCIA Card Services 3.1.12
Mar 12 17:32:48 bilbo kernel:   kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:35 E
DT 1999
Mar 12 17:32:48 bilbo kernel:   options:  [pci] [cardbus] [apm]
Mar 12 17:32:48 bilbo kernel: PCI routing table version 1.0 at 0xfd820
Mar 12 17:32:48 bilbo kernel: Intel PCIC probe:
Mar 12 17:32:48 bilbo kernel:   Ricoh RF5C296/396 ISA-to-PCMCIA at port 0x3e0 of
s 0x00
Mar 12 17:32:48 bilbo kernel:     host opts [0]: none
Mar 12 17:32:48 bilbo kernel:     ISA irqs (scanned) = 3,7,9 polling interval =
1000 ms Mar 12 17:32:48 bilbo cardmgr[1107]: starting, version is 3.1.12

This is what probe shows:

PCI bridge probe: not found. Intel PCIC probe: i82365sl B step found, 1 sockets.

cat ioports:
  0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0300-031f : NE2000
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
6800-683f : es1370
f000-f007 : ide0
f008-f00f : ide1        

Needless to say that much to my frustration, the installation of these cards went without a problem when I booted this system in NT mode....

Thanks for your help - Eric

None Not interrupts: either IO ports or memory

Re: Sad System hangs when starting pcmcia service... (Eric Maes)
Date: 2000, Mar 13
From: David Hinds <dhinds@pcmcia.sourceforge.org>

There are some very detailed instructions for diagnosing system hangs
in the PCMCIA-HOWTO.

The most important thing is to determine exactly when the hang is
happening.  Interrupts are not the problem, because even before you
forced the interrupt setting, the interrupt probe completed fine
(otherwise you would not have seen those system log messages).  The
next event that happens during the startup sequence is the IO port
probe.  After that, if a card is present in the adapter, the memory
probe is done.

So, you need to determine if the lockup depends on whether or not the
Webgear card is in the slot.  If it only happens with the card in the
slot, it is a memory probe failure, and you need to restrict the low
memory window (the 0xc0000-0xfffff window in /etc/pcmcia/config.opts).
If it happens whether or not a card is present, then you need to work
on the IO port windows in the config.opts file.

It is possible the problem would also go away if you recompiled PCMCIA
with "PnP BIOS support" switched on, since that gives better rules for
automatic resource allocation.

-- Dave

Feedback Some progress...

Re: None Not interrupts: either IO ports or memory (David Hinds)
Date: 2000, Mar 14
From: Eric Maes <eric.maes@wol.be>

David, Thanks for the tips. I have recompiled the package with Pnp bt that did not seem to make much difference. I then have experimented somewhat with ioport and memory ranges and even though I really did not know what I was doing, succeeded in getting to start the pcmcia service (I think). This is what I now see /var/log when starting up pcmcia:
Mar 14 20:17:41 bilbo kernel: Linux PCMCIA Card Services 3.1.12
Mar 14 20:17:41 bilbo kernel:   kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:35 E
DT 1999
Mar 14 20:17:41 bilbo kernel:   options:  [pci] [cardbus] [apm] [pnp]
Mar 14 20:17:41 bilbo kernel: PCI routing table version 1.0 at 0xfd820
Mar 14 20:17:41 bilbo kernel: PnP: PNP BIOS installation structure at 0xc00fb960

Mar 14 20:17:41 bilbo kernel: PnP: PNP BIOS version 1.0, entry at f0000:b988, ds eg at f0000

Mar 14 20:17:41 bilbo kernel: Intel PCIC probe:
Mar 14 20:17:41 bilbo kernel:   Ricoh RF5C296/396 ISA-to-PCMCIA at port 0x3e0 of
s 0x00
Mar 14 20:17:41 bilbo kernel:     host opts [0]: none
Mar 14 20:17:41 bilbo kernel:     ISA irqs (scanned) = 9,12 polling interval = 1
000 ms
Mar 14 20:17:41 bilbo cardmgr[1086]: starting, version is 3.1.12
Mar 14 20:17:41 bilbo cardmgr[1086]: watching 1 sockets
Mar 14 20:17:41 bilbo kernel: cs: IO port probe 0x1000-0x1300: excluding 0x1300-
0x1307
Mar 14 20:17:41 bilbo kernel: cs: IO port probe 0x0300-0x0370: clean.
Mar 14 20:17:43 bilbo cardmgr[1086]: initializing socket 0
Mar 14 20:17:43 bilbo kernel: cs: memory probe 0x0e0000-0x0effff: clean.  
Mar 14 20:17:43 bilbo cardmgr[1086]: socket 0: RayLink PC Card WLAN Adapter
Mar 14 20:17:43 bilbo cardmgr[1086]: executing: 'insmod /lib/modules/2.2.12-20/p
cmcia/ray_cs.o' Mar 14 20:17:43 bilbo kernel: ray_cs Detected: WebGear PC Card WLAN Adapter Vers ion 4.88 Jan 1999
Mar 14 20:17:43 bilbo kernel: eth1: RayLink, irq 12, hw_addr 00:00:F1:11:70:4E
Mar 14 20:17:43 bilbo cardmgr[1086]: executing: './network start eth1' 

At this point, my machine still worked! However when I try to bring up the interface either by running ifconfig by hand, or by customizing network.opts, I can just manage to enter a couple of commands after which my machine hangs... When I rebooted the machine with a non default network.opts and having set pc_debug=3 in /etc/pcmcia/ray_cs.opts, at the point where the pcmcia service was started, my console was flooded with messages: ray_dev_start_xmit busy At which point I had to reboot in single user mode to disable pcmcia at boot... So now I don't know whether I have a pcmcia or a Webgear problem...

Thanks for your help - Eric

Ok OK now!

Re: Feedback Some progress... (Eric Maes)
Date: 2000, Mar 15
From: Eric Maes <eric.maes@wol.be>

David,

I got the latest beta (which corrects a ray_cs bug) from the ftp site as you suggested, compiled, installed and now I seem to have a working system!

The only thing to do now is setup my network...

Thanks a lot for your help, much appreciated.

Cheers - Eric

Question unknown PCI interrupt router 1106:0586

Date: 2000, Mar 12
From: Guillaum Dallaire gd

Hi,

I have a PCI to PCMCIA bridge that come from wavelan (TI 1225). I'm able to use the adapter under some motherboards (intel, asus) but except under one using the VIA chipset.

here is what I get on boot:

-----------

Linux PCMCIA Card Services 3.1.11
  kernel build: 2.2.14 #3 SMP sam mar 11 11:17:27 EST 2000
  options:  [pci] [cardbus]
PCI routing table version 1.0 at 0xfde20
  unknown PCI interrupt router 1106:0586
Intel PCIC probe: not found.
ds: no socket drivers loaded!

----------

when I make lspci I don't see the device.

I have tried a lot of different bios setting but this do not change anyting...

any idea ?

None It seems to be a PCI problem, not a PCMCIA driver problem

Re: Question unknown PCI interrupt router 1106:0586 (Guillaum Dallaire)
Date: 2000, Mar 13
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If the card does not show up in "lspci", then there is no way for the
PCMCIA drivers to find the bridge device.  The "unknown PCI interrupt
router" message is not related to this problem.  I'm not sure what to
suggest: perhaps contact Martin Mares, mj@ucw.cz.  He is the PCI
maintainer and might have some ideas about why the device might not
show up.

-- Dave

Question RH6.1 with 2.2.14

Date: 2000, Mar 14
From: Duane Gustavus duane

Hello,

I am having problems getting PCMCIA services to work on my Redhat 6.1 Linux desktop system. I recently bought a "DataChute" ISA-PCMCIA controller which uses a VIA VT83C469. First, I did a new installation of RH6.1 on a spare pentium system, booted the new install and edited the /etc/sysconfig/pcmcia file to say yes. I then shutdown, put the adapter in the system and rebooted. The pcmcia services were started correctly, and I made a file system on a flash card just to make sure. Everything worked as advertised.

Next I put the same adapter into my "development" system which is also RH6.1 but upgraded to kernel 2.2.14 and pcmcia-cs-3.1.12. This system has the identical motherboard, but a faster K6 processor. Also, this system has had several different kernel builds done on it (ie is not pristine with the distribution kernel). When I install the 2.2.14 kernel with modules and then the 3.1.12 modules, I have the following results from dmesg:

Linux PCMCIA Card Services 3.1.12
  kernel build: 2.2.14 #2 Sun Mar 12 15:36:18 CST 2000
  options:  [pci] [cardbus] [pnp]
PCI routing table version 1.0 at 0xf0b40
  unknown PCI interrupt router 10b9:1533
PnP: PNP BIOS installation structure at 0xc00fcfb0
PnP: PNP BIOS version 1.0, entry at f0000:cfe0, dseg at f0000
Intel PCIC probe: 
  VIA VT83C469 ISA-to-PCMCIA at port 0x3e0 ofs 0x00
    host opts [0]: none
    host opts [1]: none
    ISA irqs (default) = 10 polling interval = 1000 ms

I have the PnP OS BIOS value set to no, and the secondary IDE controller disabled (the DC wants to use that). If I issue an lsmod command, it shows:

 Module                  Size  Used by
 ds                      6088   0  (unused)
 i82365                 21328   2 
 pcmcia_core            47712   0  [ds i82365]

Here is the portion of /var/log/messages that matches the boot messages shown above:

Mar 12 16:07:56 marvin pcmcia: Starting PCMCIA services:
Mar 12 16:07:56 marvin pcmcia:  modules
Mar 12 16:07:56 marvin kernel: Linux PCMCIA Card Services 3.1.12 
Mar 12 16:07:56 marvin kernel:   kernel build: 2.2.14 #2 Sun Mar 12 15:36:18 CST
 2000 
Mar 12 16:07:56 marvin kernel:   options:  [pci] [cardbus] [pnp] 
Mar 12 16:07:56 marvin kernel: PCI routing table version 1.0 at 0xf0b40 
Mar 12 16:07:56 marvin kernel:   unknown PCI interrupt router 10b9:1533 
Mar 12 16:07:56 marvin kernel: PnP: PNP BIOS installation structure at 0xc00fcfb
0 
Mar 12 16:07:56 marvin kernel: PnP: PNP BIOS version 1.0, entry at f0000:cfe0, d
seg at f0000 
Mar 12 16:07:56 marvin kernel: Intel PCIC probe:  
Mar 12 16:07:56 marvin kernel:   VIA VT83C469 ISA-to-PCMCIA at port 0x3e0 ofs 0x
00 
Mar 12 16:07:56 marvin kernel:     host opts [0]: none 
Mar 12 16:07:56 marvin kernel:     host opts [1]: none 
Mar 12 16:07:57 marvin kernel:     ISA irqs (default) = 10 polling interval = 10
00 ms 
Mar 12 16:07:56 marvin pcmcia:  cardmgr.
Mar 12 16:07:57 marvin rc: Starting pcmcia succeeded
Mar 12 16:07:56 marvin cardmgr[366]: starting, version is 3.1.12
Mar 12 16:07:57 marvin cardmgr[366]: open_sock(socket 0) failed: Permission deni
ed
Mar 12 16:07:57 marvin cardmgr[366]: no sockets found!
Mar 12 16:07:57 marvin cardmgr[366]: exiting

Finally, since this controller is a PnP device, I used pnpdump to build /etc/isapnp.conf that looks like this:

# Trying port address 0203
# Board 1 has serial identifier 21 05 00 00 00 18 30 21 59

# (DEBUG) (READPORT 0x0203) (ISOLATE PRESERVE) (IDENTIFY *) (VERBOSITY 2) (CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING

# Card 1: (serial identifier 21 05 00 00 00 18 30 21 59)
# Vendor Id VIA3018, Serial Number 83886080, checksum 0x21.
# Version 1.0, Vendor version 0.0
# ANSI string -->VIA PCMCIA CARD<--
#
# Logical device id PNP0e00
#     Device support I/O range check register
#
# Edit the entries below to uncomment out the configuration required.
# Note that only the first value of any range is given, this may be changed if required
# Don't forget to uncomment the activate (ACT Y) when happy

(CONFIGURE VIA3018/83886080 (LD 0
#     Compatible device id PNP0e00
#     Logical device decodes 16 bit IO address lines
#         Minimum IO base address 0x03e0
#         Maximum IO base address 0x03e3
#         IO base alignment 2 bytes
#         Number of IO addresses required: 2
#  (IO 0 (SIZE 2) (BASE 0x03e2) (CHECK))
 (NAME "VIA3018/83886080[0]{VIA PCMCIA CARD     }")
  (ACT Y)
))
# End tag... Checksum 0x00 (OK)

# Returns all cards to the "Wait for Key" state (WAITFORKEY)

I commented out the (IO ...) line above because it seemed to always have problems checking the device range (causing isapnp to abort execution).

Obviously, the distribution RH kernel (2.2.12-20) has some option turned on that I am unaware of, or there is some configuration I have done incorrectly. Sorry for the length of this message; I just wanted to provide enough information to encourage someone knowledgeable to give me some pointers. I really need to have confidence I can build new kernels with the pcmcia services working as I want to put Linux on a PC/104 computer on my robot which will only have pcmcia periperhals.

Thanks, Duane duane@denton.com

None That's a new one

Re: Question RH6.1 with 2.2.14 (Duane Gustavus)
Date: 2000, Mar 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I have not seen that error message before.

Could you try doing "strace -f cardmgr" and send me the output?  Were
you invoking cardmgr as root?  Is there anything else "odd" about this
system setup?

-- Dave

None It was a filesystem permissions issue

Re: Question RH6.1 with 2.2.14 (Duane Gustavus)
Date: 2000, Mar 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The problem was that /var was mounted "nodev", and cardmgr attempts to
create a device file in /tmp, which was linked to /var/tmp.

I will either fix cardmgr to do this differently or at least document
the requirement in the man page.

-- Dave

Ok Antec DataChute notes

Re: Question RH6.1 with 2.2.14 (Duane Gustavus)
Date: 2000, Mar 15
From: Duane Gustavus duane

Hello,

I just spent a long weekend and more getting pcmcia services running on my RedHat Linux system using the 2.2.14 kernel and pcmcia-services 3.1.12. I thought I would relate a few issues that might be of help to others (a trail of crumbs in the darksome forest as it were).

I am using an Antec DataChute ISA-PCMCIA device in my desktop. This device uses a VIA VT83C469 chip which is evidently compatible with the i82365 (ie it seems to work with the flash card I am using). It also expects to be the secondary IDE controller, so you will need to disable the secondary IDE controller on your motherboard to make it happy (yes that means you will have to move any IDE devices currently on the secondary channel off). My /etc/sysconfig/pcmcia file looks like:

 PCMCIA=yes
 PCIC=i82365
 PCIC_OPTS="irq_list=10,11 has_ring=0"
 CORE_OPTS=
 CARDMGR_OPTS=

The PCIC_OPTS line is set to the IRQs I want the adapter to use (in other words, you may well wish to change this). This is a PnP board, so while I set my BIOS to answer NO to the PnP OS question, I built an entry for isapnp.conf using pnpdump. I was able to comment out the IO line because it was causing problems during boot. If you don't use a PnP card, you will avoid this hassle.

Through the good offices of David Hinds, the last problem squashed was the mount specification for /tmp. I always use a separate partition for /tmp with the nosuid and nodev mount options for security purposes. The cardmgr makes a couple of device files in /tmp which will of course fail if you use the nodev option. David is considering the relocation of those files, but if you use the nodev mount option, you will need to make sure cardmgr doesn't try to open it's device files in that particular partition.

I would like to thank David Hinds for his speedy response to my m'aidez, not to mention the quick isolation of my problem. I hope these notes are of use to the next person down this path.

Cheers, Duane

Sad This has to be an easy one...

Date: 2000, Mar 16
From: Chris Hobbs LancerD

I'm attempting to build 3.1.13 on a RH6.0 box upgraded to kernel 2.2.14. When I try to 'make all', I get the following error, repeated for every file it tries to make:

make[1]: Entering directory `/usr/src/linux-2.2.14/pcmcia-cs-3.1.13/modules'
cc   -MD -O2 -Wall -Wstrict-prototypes -pipe -I../include -I/usr/src/linux/include  -D__KERNEL__ -DMODULE -c cs.c
In file included from /usr/src/linux/include/linux/capability.h:13,
                 from /usr/src/linux/include/linux/binfmts.h:5,
                 from /usr/src/linux/include/linux/sched.h:8,
                 from /usr/src/linux/include/linux/vmalloc.h:4,
                 from /usr/src/linux/include/asm/io.h:101,
                 from ../include/pcmcia/k_compat.h:203,
                 from cs.c:35:
/usr/src/linux/include/linux/fs.h:786: warning: `invalidate_buffers' redefined
/usr/src/linux/include/linux/modules/ksyms.ver:122: warning: this is the location of the previous definition
In file included from ../include/asm/uaccess.h:52,
                 from ../include/pcmcia/k_compat.h:248,
                 from cs.c:35:
/usr/src/linux/include/asm/uaccess.h:600: warning: `strlen_user' redefined
/usr/src/linux/include/linux/modules/i386_ksyms.ver:56: warning: this is the location of the previous definition


I have no trouble building 3.1.10, which is running now. Any ideas?

None What is the output of "make config"?

Re: Sad This has to be an easy one... (Chris Hobbs)
Date: 2000, Mar 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Also, does /usr/src/linux point to /usr/src/linux-2.2.14?

-- Dave

More make config

Re: None What is the output of "make config"? (David Hinds)
Date: 2000, Mar 17
From: Chris Hobbs LancerD

First:

lrwxrwxrwx   1 root     root           12 Mar  6 18:10 linux -> linux-2.2.14

Now, for 'make config':

    -------- Linux PCMCIA Configuration Script --------

The default responses for each question are correct for most users.
Consult the PCMCIA-HOWTO for additional info about each option.

Linux source directory [/usr/src/linux]: 

The kernel source tree is version 2.2.14.
The current kernel build date is Thu Mar 16 07:13:15 2000.

Alternate target install directory []: 
Build 'trusting' versions of card utilities (y/n) [n]: 
Include 32-bit (CardBus) card support (y/n) [y]: 
Include PnP BIOS resource checking (y/n) [n]: 
Module install directory [/lib/modules/2.2.14]: 

Kernel configuration options:
    Symmetric multiprocessing support is disabled.
    PCI BIOS support is enabled.
    Advanced Power Management (APM) support is enabled.
    SCSI support is disabled.
    Networking support is enabled.
     Radio network interface support is disabled.
     Token Ring device support is disabled.
     Fast switching is disabled.
    Module version checking is enabled.
    /proc filesystem support is enabled.
    Maximum physical memory: 2GB

It looks like you have a System V init file setup.

X Windows include files found.
/usr/X11R6/lib/libforms.a and /usr/include/forms.h found.

Configuration successful.

-----

All defaults accepted. Thanks for checking this out!

Ok Solved

Re: None What is the output of "make config"? (David Hinds)
Date: 2000, Mar 17
From: Chris Hobbs LancerD

I had some sort of wackiness with my kernel sources... noticed the sam problem trying to configure VM-ware, so redownloaded the kernel source, built a new kernel, pcmcia stuff compiled with no complaints afterwards. Thanks for the help though!

Question PCMCIA Problem with 3COM 3C562D/3C563D "eth0: interrupt(s) dropped"

Date: 2000, Mar 17
From: John Auld jxa

I have a working install of Linux (tomsrtbt) with networking enabled via PCMCIA services on a laptop. The networking works properly (e.g. I can ping hosts etc.) but the console is over-written with warning message "eth0: interrupt(s) dropped!", which makes the system very hard to use.

I have searched for a solution through the PCMCIA and Ethernet HOWTO's and www.dejanews.com with no success. I can't tell if this is a problem with the card configuration or the Net Card driver or what to do to clear it.

Your advice would be greatly appreciated.

John Auld

None Dropped interrupts

Re: Question PCMCIA Problem with 3COM 3C562D/3C563D "eth0: interrupt(s) dropped" (John Auld)
Date: 2000, Mar 17
From: David Hinds <dhinds@pcmcia.sourceforge.org>

What sort of laptop?  Can you capture the startup messages from the
PCMCIA drivers?

Interrupts are not being delivered to the card.  It is not a problem
with the driver for the card, it is a problem with the socket driver.
It could be that this would be fixed by upgrading the PCMCIA package,
but I don't know what version you've got.

-- Dave

None Hardware & Software details

Re: None Dropped interrupts (David Hinds)
Date: 2000, Mar 17
From: John Auld jxa

Thanks for the prompt reply.

The Laptop is a Twinhead Voyager.

dmesg reports a Cirrus PD6729 PCI-to-PCMCIA chip and the PCMCIA services load the following modules (listed from `cat /proc/modules`)

3c589_cs 1 0
serial_cs 2 1
ds 2 [serial_cs 3c589_cs] 2
i82365 5 2
pcmcia_core 9 [serial_cs 3c589_cs ds i82365] 8

Software versions
kernel = 2.0.37
PCMCIA Services = 3.0.12
3c589 driver = v0.99H

I have used a boot floppy version of Linux as a means to recover data on Win9x laptops at work that are un-bootable or too unstable for use (I will need to use this many times!!!) and I have not yet read all of the init and config scripts, but I can configure the PCMCIA start up options if I need to.

Thanks again for your help.


John Auld

None Probably just an interrupt conflict

Re: None Hardware & Software details (John Auld)
Date: 2000, Mar 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You probably just have an interrupt conflict with some other system
device.  I'd start by excluding interrupts in /etc/pcmcia/config.opts
and see if that fixes the problem.

-- Dave

Question Problem with TDK LAC-CD021AX

Date: 2000, Mar 26
From: Kenji Takahashi <takahash@wells.or.jp>

I am using TDK LAC-CD021AX with kernel 2.2.13, PCMCIA 3.1.1 but it is not identified.

/var/log/messages said as follows;

cardmgr[653]: socket 1: Anonymous Memory

cardmgr[653]:executing: 'insmod /lib/modules/2.2.13/pcmcia/memory_cs.o'

kernel: memory_cs: mem0: anonymous: unknown size.

my config.opts is as below;

include port 0x100-0x4ff, port 0x1000-0x17ff

include memory 0xc0000-0xfffff

exclude irq 4

exclude irq 7

I also tried with other memory range such as 0xd0000-0xdffff and so on which are mentined by PCMCIA-HOWTO but any ranges were failed.

The card works correctly on Windows98, so I cannot think this is the hardware problem.

Any idea I can try ?

None Your main problem is probably the 3.1.1 drivers

Re: Question Problem with TDK LAC-CD021AX (Kenji Takahashi)
Date: 2000, Mar 26
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You left out two of the more important bits of information:

-- the startup messages from the PCMCIA drivers
-- what kind of laptop this is

But my first advice is to upgrade, since 3.1.1 was not a particularly
good version of the PCMCIA drivers.  3.1.13 is current.

-- Dave

Sad lucent ISA-PCMCIA adapter problems with aic78xx scsi driver

Date: 2000, Mar 27
From: Douglas S. J. De Couto decouto

Hi,

I am having problems getting my lucent ISA-PCMCIA adapter to
work on my PC.

The driver seems to load fine, but all disk operations time
out after that. 

The ISA card is from lucent and uses a Vadem 469 chip, and is
at i/o address 0x3e0.

my kernel is 2.2.14, and my pcmcia version is 3.1.13

i use redhat 6.2

I have an adaptec aic 7896/7 on my motherboard, and i use the aic78xx driver as a kernel module.

after loading the pcmcia driver, the next part in the boot
process is to run the inet script (S50inet), whereupon the 
computer  hangs and the aic78xx driver periodically prints
a message reporting a timeout.

this happens with and without irg scanning enabled in the
pcmcia driver options, and with and without a lucent
wavelan ieee pcmcia card installed in the ISA adapter.

without the pcmica driver i have no problems with my scsi.

i am sorry, my logs disappeared as i had to hit the reset
switch to reboot, and the fsck wasn't very nice...

i see some people have had i/o port problems, i have yet to
try blocking out i/o ports (those other people's problems
seemed to be related to having a card in the slight, my
problem happens either way).

here is some output from my system with the card installed,
but not running the driver:

-------------------
% cat /proc/ioports 
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
01f0-01f7 : ide0
02f8-02ff : serial(auto)
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
1050-1057 : ide0
1058-105f : ide1
1080-109f : Intel Speedo3 Ethernet
1400-14be : aic7xxx
1800-18be : aic7xxx

----------------------------
% cat /proc/interrupts 
           CPU0       CPU1       
  0:      61902      49995    IO-APIC-edge  timer
  1:        133        119    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
  8:          0          1    IO-APIC-edge  rtc
 12:        110         19    IO-APIC-edge  PS/2 Mouse
 13:          1          0          XT-PIC  fpu
 14:          3          3    IO-APIC-edge  ide0
 19:       1890       1860   IO-APIC-level  aic7xxx, aic7xxx
 21:       1474       1459   IO-APIC-level  Intel EtherExpress Pro 10/100 Ethernet
NMI:          0
ERR:          0


i would be happy to hear of anyone else with a similar problem
or a similar setup.

thanks,

Douglas

More no more disk problems....

Re: Sad lucent ISA-PCMCIA adapter problems with aic78xx scsi driver (Douglas S. J. De Couto)
Date: 2000, Mar 28
From: Douglas S. J. De Couto decouto

hi.  i told the driver to exclude the ioports where my scsi
driver lives (in config.opts), and my machine boots fine now.

i.e.

# avoid adaptec adapter ports
exclude port 0x1400-0x18be


however, i think the wavelan driver doesn't work on the smp, 
as i get crashes when using the wireless tools.  but that's 
not a pcmcia problem.

thanks for a great package.

d

None Actually this is a bug in the aic7xxx driver

Re: More no more disk problems.... (Douglas S. J. De Couto)
Date: 2000, Mar 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

That's interesting.  I think this is a bug in the aic7xxx driver,
because it is reserving a smaller IO port window than the card uses.
And the PCMCIA IO port probe stomps on the unprotected bit.  (I bet if
you exclude just 0x1400-0x14ff and 0x1800-0x18ff, that will also work;
it should also work if you rebuild PCMCIA with "PnP BIOS support"
turned on)

-- Dave

Question Xircom ISDN Creditcard

Date: 2000, Mar 28
From: Ole andre olli

I have Xircom ISDN Creditcard and have no clue how to configure it and use it. Can somebody help me! I have a toshbia satellite 2060, slackware7 and kernel 2.2.13!

Sad Pcmcia Token Ring Card Problem!...

Date: 2000, Mar 28
From: Cesar Chavez yoannez

Hi...

I have a ThinkPad 760EL laptop with a token ring pcmcia card
my system works fine except for the network, during the sistem boot when the cardmgr start the pcmcia services every thing works until cardmgr reports the folowing 
Cardmgr [61]:get dev info on socket 0 failed: No such device               done
after this ifconfig causes segmentation fault and i can't get startx to work. If I remove the card startx boots fine...
The messege from dmesg is the folowing


Linux version 2.2.13 (root@Mandelbrot.suse.de) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Nov 8 15:37:25 CET 1999
Detected 119754905 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 47.82 BogoMIPS
Memory: 63804k/66556k available (1240k kernel code, 412k reserved, 1036k data, 64k init, 0k bigmem)
DENTRY hash table entries: 16384 (order: 5, 131072 bytes)
Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Intel Pentium 75 - 200 stepping 0c
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
Intel Pentium with F0 0F bug - workaround enabled.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfd930
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
Initializing RT netlink socket
Starting kswapd v 1.5 
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9a)
Real Time Clock Driver v1.09
RAM disk driver initialized:  16 RAM disks of 64000K size
loop: registered device at major 7
Uniform Multi-Platform E-IDE driver Revision: 6.20
PIIX: IDE controller on PCI bus 00 dev 08
PIIX: not 100% native mode: will probe irqs later
PIIX: neither IDE port enabled (BIOS)
hda: IBM-DPLA-25120, ATA DISK drive
hdb: SANYO CRD-S58P, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: IBM-DPLA-25120, 4887MB w/468kB Cache, CHS=662/240/63
hdb: ATAPI 8X CD-ROM drive, 256kB Cache
Uniform CDROM driver Revision: 2.56
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
LVM version 0.8i  by Heinz Mauelshagen  (02/10/1999)
lvm -- Driver successfully initialized
md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
linear personality registered
raid0 personality registered
raid1 personality registered
raid5 personality registered
scsi : 0 hosts.
scsi : detected total.
Partition check:
 hda: hda1 hda2 < hda5 hda6 >
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 64k freed
Adding Swap: 68004k swap-space (priority -1)
Serial driver version 4.27 with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ enabled
Linux PCMCIA Card Services 3.1.3
  kernel build: 2.2.13 #1 Mon Nov 8 18:28:35 GMT 1999
  options:  [pci] [cardbus] [pnp]
PnP: PNP BIOS installation structure at 0xc00fe700
PnP: PNP BIOS version 1.0, entry at f0000:e724, dseg at f0000
Intel PCIC probe: 
  TI 1130 PCI-to-CardBus at bus 0 slot 2, mem 0x10211000, 2 sockets
    host opts [0]: [ring] [isa irq] [no pci irq] [lat 168/176] [bus 1/3]
    host opts [1]: [ring] [isa irq] [no pci irq] [lat 168/176] [bus 4/6]
    ISA irqs (scanned) = 5,7,9,10 status change on irq 10
cs: memory probe 0xa0000000-0xa0ffffff: clean.
ibmtr_cs: RequestIO: Resource in use
Unable to handle kernel NULL pointer dereference at virtual address 00000044
current->tss.cr3 = 03d89000, %cr3 = 03d89000
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c016af91>]
EFLAGS: 00010282
eax: ffffffff   ebx: c3d966e0   ecx: c3d59f40   edx: ffffffff
esi: 00000044   edi: c3d59f40   ebp: bffffc20   esp: c3d59f04
ds: 0018   es: 0018   ss: 0018
Process ifconfig (pid: 72, process nr: 9, stackpage=c3d59000)
Stack: 00000000 c016b107 c3d59f40 c3d59f40 c016c12a c3d59f40 00008913 00008913 
       bffffc20 c197b020 00000001 c3d58000 c3d58000 c3d59f40 c3d59f50 00307274 
       bffffca8 bffffd28 00000000 bffffd38 0804a2e8 00000000 bffffca8 c018d216 
Call Trace: [<c016b107>] [<c016c12a>] [<c018d216>] [<c0167db1>] [<c012ed3d>] [<c0109e8c>] 
Code: ac ae 75 08 84 c0 75 f8 31 c0 eb 04 19 c0 0c 01 89 c2 85 d2 
Unable to handle kernel NULL pointer dereference at virtual address 00000001
current->tss.cr3 = 03fd0000, %cr3 = 03fd0000
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<00000001>]
EFLAGS: 00010202
eax: 00000001   ebx: c3d966e0   ecx: c18e510a   edx: c02101b6
esi: c18e5143   edi: 00000000   ebp: 00000001   esp: c3fcdf38
ds: 0018   es: 0018   ss: 0018
Process S07route (pid: 73, process nr: 8, stackpage=c3fcd000)
Stack: 00000143 c3d966e0 c016ba75 c18e5143 c3d966e0 c405f6f4 00000001 00000000 
       c18e5000 00000143 c015248a c18e5000 c3fcdf98 00000142 00000001 00000000 
       c405f6e0 ffffffea 00000000 00000001 00000001 c024a460 00000000 00000000 
Call Trace: [<c016ba75>] [<c015248a>] [<c0125822>] [<c0109e8c>] 
Code: <1>Unable to handle kernel NULL pointer dereference at virtual address 00000001
current->tss.cr3 = 03fd0000, %cr3 = 03fd0000
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c010a2ed>]
EFLAGS: 00010046
eax: 00000000   ebx: 00000000   ecx: 00000001   edx: 00000001
esi: 0000002b   edi: c3fce000   ebp: c4800000   esp: c3fcde78
ds: 0018   es: 0018   ss: 0018
Process S07route (pid: 73, process nr: 8, stackpage=c3fcd000)
Stack: 00000001 08048000 c027104e c18e5143 00000000 00000001 00000001 c3d966e0 
       c18e510a c02101b6 00000001 00010202 040ff000 c5000000 c010a350 c3fcdefc 
       c0200498 c0201b2e 00000000 00000000 c010f460 c0201b2e c3fcdefc 00000000 
Call Trace: [<c02101b6>] [<c5000000>] [<c010a350>] [<c0200498>] [<c0201b2e>] [<c010f460>] [<c0201b2e>] 
       [<c016ba14>] [<c0109f91>] [<c02101b6>] [<c016b9a4>] [<c016ba75>] [<c015248a>] [<c0125822>] [<c0109e8c>] 
Code: 8a 04 0b 89 44 24 38 50 68 90 04 20 c0 e8 c5 9c 00 00 83 c4 
Unable to handle kernel paging request at virtual address f307f204
current->tss.cr3 = 00264000, %cr3 = 00264000
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c018b9ad>]
EFLAGS: 00010286
eax: c3d966e0   ebx: bffff3c4   ecx: f307f200   edx: c018b98c
esi: 00000002   edi: c3d966e0   ebp: bffff3ec   esp: c0005e98
ds: 0018   es: 0018   ss: 0018
Process X (pid: 188, process nr: 39, stackpage=c0005000)
Stack: c3d966e0 00000020 c03bc024 c0004000 c012d18c c1023bc0 00000000 00000000 
       00000000 00006f6c 00000000 00000000 00000000 00000002 0100007f 00000000 
       00000000 c016b935 c3d966e0 bffff3ec 000007e0 00008912 00008912 bffff3c4 
Call Trace: [<c012d18c>] [<c016b935>] [<c016c02e>] [<c011b9a9>] [<c018d205>] [<c018d216>] [<c0167db1>] 
       [<c012ed3d>] [<c0109e8c>] 
Code: 8b 49 04 89 4c 24 28 85 c9 75 14 31 c0 e9 c8 00 00 00 90 b8 

None I think a driver upgrade might help

Re: Sad Pcmcia Token Ring Card Problem!... (Cesar Chavez)
Date: 2000, Mar 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The 3.1.3 drivers had various problems that are not token ring
related.

If you still have trouble with the latest (3.1.13) drivers, then try
checking http://www.linuxtr.net for more specific token ring info.

-- Dave

Question redhat 6.0 -> 6.1 upgrade breaks pcmcia?

Date: 2000, Mar 31
From: Michael Way mway

I just upgraded my toshiba 490xcdt from redhat 6.0
to 6.1. i'm experiencing strange behaviour from the
pcmcia utilties in relation to my pcmcia 3com 3c589
network card.

1.) upon boot the card is not recognized.
2.) once the machine is up, if i reload pcmcia it
    is still not recognized (/etc/rc.d/init.d/pcmcia restart)
3.) if i pull out the card and push it back in it _IS_
    recognized and the appropriate driver is loaded.
    all seems to work normally.

a peek in /var/log/messages on the the successful one (3)
shows the card to be loaded properly, name and all.
a similar look in /var/log/messages from attempts (1) and (2)
above show strange messages about an unknown memory
card that _dont'_ show up when i succeed with (3) above:

Mar 30 22:41:46 metis cardmgr[1615]: starting, version is 3.0.14
Mar 30 22:41:46 metis cardmgr[1615]: watching 2 sockets
Mar 30 22:41:46 metis kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Mar 30 22:41:46 metis kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0
x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7 
Mar 30 22:41:46 metis kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Mar 30 22:41:46 metis cardmgr[1615]: initializing socket 0
Mar 30 22:41:46 metis kernel: cs: memory probe 0x0d0000-0x0dffff: excluding 0xd0
000-0xdffff 
Mar 30 22:41:46 metis kernel: cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0
000-0xcffff 
Mar 30 22:41:46 metis cardmgr[1615]: socket 0: Anonymous Memory
Mar 30 22:41:46 metis cardmgr[1615]: executing: 'insmod /lib/modules/2.2.12-20/p
cmcia/memory_cs.o'


BUT i don't understand this since i DON'T have a memory
card in the machine. any ideas of what i can take
out or put into the pcmcia stuff to fix this?
the machine was running everything just fine under
redhat 6.0. if it were my machine i would have never
upgraded it... but i had to do it for my boss....

thanks,
mike

None This is fixed in newer PCMCIA packages

Re: Question redhat 6.0 -> 6.1 upgrade breaks pcmcia? (Michael Way)
Date: 2000, Mar 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

That's all.  The current release is 3.1.13.

-- Dave

Question [Help] Cannot make the driver work on my laptop

Date: 2000, Mar 31
From: Chih Wei Hsu beavish

Notebook:TwinHead Pentium-166
Memory: 32 MB
Disk: IDE
The probe shows
PCI bridge probe: not found.
Intel PCIC probe: i82365sl DF found, 2 sockets
Linux version: Redhat 5.0, Kernerl 2.0.36
No other special equipment attached to the notebook.

Because I have a project about mobile IP, I have to installed the old release of Linux on this machine and make it work with the PCMCIA ethernet card, D-Link DE-660.

I have tried several versions of the pcmcia drivers d/l
from this site. The first one I tried is 3.1.12 but I failed while it compiled the drivers. Thus, I tried some others like 3.0.12, 3.1.11, and 3.1.13. All of them came up with no problems when I compiled. However, the system always got halted while I booted the machine after the phrase, "modules" showed up. 

Therefore, I tried to debug by myself and traced the 
/etc/rc.d/init.d/pcmcia script. I followed it step by step. 

I found that the system never upload pcmcia_core.o successfully, but it didn't get halted. As it tried to insmod i82365.o, the system halted immediately.
When I tried "insmod -pvm i82365.o", it would show the
following messages,

i82365.o: unresolved symbol pci_set_power_state
i82365.o: unresolved symbol pci_find_class
i82365.o: unresolved symbol pci_enable_device
i82365.o: unresolved symbol request_mem_region
i82365.o: unresolved symbol release_mem_region
i82365.o: unresolved symbol unregister_ss_entry
i82365.o: unresolved symbol pci_find_slot
i82365.o: unresolved symbol pci_irq_mask
i82365.o: unresolved symbol register_ss_entry
i82365.o: unresolved symbol CardServices

If "insmod i82365.o", the system will halt immediately.

However, when I switch to single user mode, I can successfully upload pcmcia_core.o which gives me 8 pages and 0 used. It is of no problem to upload both
i82365.o and ds.o under  single user mode, but what I can see with "lsmod" is pcmcia_core.o. Thus, I don't think it is successfully installed.

I have tried to find out the answer by myself on this forum before I post this. I didn't set any CFLAGS on my system and it is a pure system without any other stuff but a mobile ip daemon developed by Stanford Univ.

May you guys be kind to do me a favor to solve the problem? I can provide as much as information about my system if the above are not enough yet.

Thank you in advance.

Chih

None Not sure, but sounds like an interrupt probe problem

Re: Question [Help] Cannot make the driver work on my laptop (Chih Wei Hsu)
Date: 2000, Mar 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I think you should check the PCMCIA-HOWTO chapter on resolving
installation problems.  If loading the i82365 module freezes your
system, then you've got a problem with the interrupt probe.  There are
instructions in the HOWTO for disabling or restricting the probe.

-- Dave

Question Re: "Not sure, but sounds like an interrupt probe problem"

Re: None Not sure, but sounds like an interrupt probe problem (David Hinds)
Date: 2000, Mar 31
From: Chih Wei Hsu beavish

Thank you for your quick relpy.

Yes. I did. I followed the How-To and tried whole the irq (0 - 15) one by one, but in vain.

May you let me know why I cannot see pcmcia_core.o with "lsmod" while I manually insmod this module. Also,
why did i82365 give me those messages while I manually
installed it by "insmod -pvm i82365.o"?

Thank you.

None I can't really tell what you're doing

Re: Question Re: "Not sure, but sounds like an interrupt probe problem" (Chih Wei Hsu)
Date: 2000, Mar 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I can't really reconstruct what you did from your messages.  Part of
it is a language issue: it might be better for you to be more exact
about what sequences of commands you used and exactly what output you
got.  Also please watch your system log while doing these things:
almost all interesting PCMCIA messages are recorded in the system log.
I don't know what it means to say you "tried whole the irq (0-15)".
What did you do, exactly?  (what files did you modify, and how?)

If you do "insmod pcmcia_core", and that gives no error message, and
your system log indicates that the module was loaded, then I don't
konw why it would not show up with "lsmod".

If you try to "insmod -pvm i82365" when pcmcia_core is not loaded,
then you will get the "unresolved symbol" errors you describe.  You
should get the same messages if you do "insmod i82365" in this same
situation, however.

Show me what output you get from running the following series of
commands:

    insmod pcmcia_core
    tail /var/log/messages
    lsmod
    insmod i82365 do_scan=0
    tail /var/log/messages
    lsmod
    
-- Dave

Sad eth0:interrupt(s) dropped!

Date: 2000, Mar 31
From: Ray jxray

Question d-link dfe-660tx cardbus: eth0: Tx hung, 9 vs. 0. ??????

Date: 2000, Apr 02
From: Jochen Kirsch cerise

Hello!

I can't get my network card d-link dfe-660tx work. It is recognized by the cardmgr and the correct (?) driver tulip_cb is loaded. The lan activity led is blinking but the full duplex led remains dark (under win98 it is on). Every few minutes I get the following error message on the console

eth0: Tx hung, 9 vs. 0.     or sometimes
eth0: Tx hung, 15 vs. 0.

Below I have included info about my system configuration and logging from /var/log/messages.

Could anyone help, please?

Merci.

Jochen Kirsch.

================================================

Computer model: Sony Vaio pcg-f190

pcmcia-card: d-link dfe-660tx, cardbus

Linux version: Redhat 6.2 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000

cardctl -V cardctl version 3.1.8

cardctl ident
Socket 0:
  product info: "D-Link", "DFE-660", "CardBus Ethernet", "10/100"
  manfid: 0x0149, 0x0231
  function: 6 (network)
Socket 1:
  no product info available

cardctl status
Socket 0:
  3.3V CardBus card
  function 0: [ready]
Socket 1:
  no card

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

/var/log/messages:

Apr  2 20:03:07 cerise pcmcia: Starting PCMCIA services:
Apr  2 20:03:07 cerise pcmcia:  modules
Apr  2 20:03:08 cerise kernel: Linux PCMCIA Card Services 3.1.8
Apr  2 20:03:08 cerise kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 21:07:39
EST 2000
Apr  2 20:03:08 cerise kernel:   options:  [pci] [cardbus] [apm]
Apr  2 20:03:08 cerise kernel: Intel PCIC probe:
Apr  2 20:03:08 cerise kernel:   Ricoh RL5C478 PCI-to-CardBus at bus 0 slot 10,
mem 0x68000000, 2 sockets
Apr  2 20:03:08 cerise kernel:     host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 168/176] [bus 32/34]
Apr  2 20:03:08 cerise kernel:     host opts [1]: [isa irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 168/176] [bus 35/37]
Apr  2 20:03:08 cerise kernel:     ISA irqs (default) = 3,4,5,7,10,11,12 polling interval = 1000 ms
Apr  2 20:03:08 cerise pcmcia:  cardmgr.
Apr  2 20:03:08 cerise cardmgr[426]: starting, version is 3.1.8
Apr  2 20:03:08 cerise rc: Starting pcmcia succeeded
Apr  2 20:03:08 cerise cardmgr[426]: watching 2 sockets
Apr  2 20:03:08 cerise kernel: cs: IO port probe 0x1000-0x17ff: clean.
Apr  2 20:03:08 cerise kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x140-0x147 0x378-0x37f 0x4d0-0x4d7
Apr  2 20:03:08 cerise kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr  2 20:03:08 cerise kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019
Apr  2 20:03:08 cerise cardmgr[426]: initializing socket 0
Apr  2 20:03:08 cerise cardmgr[426]: socket 0: Linksys EtherFast 10/100
Apr  2 20:03:08 cerise cardmgr[426]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/cb_enabler.o'
Apr  2 20:03:08 cerise cardmgr[426]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/tulip_cb.o'
Apr  2 20:03:08 cerise kernel: cs: cb_config(bus 32)
Apr  2 20:03:08 cerise kernel:   fn 0 bar 1: io 0x200-0x27f
Apr  2 20:03:08 cerise kernel:   fn 0 bar 2: mem 0x600c0000-0x600c03ff
Apr  2 20:03:08 cerise kernel:   fn 0 rom: mem 0x60080000-0x600bffff
Apr  2 20:03:08 cerise kernel: tulip_attach(bus 32, function 0)
Apr  2 20:03:08 cerise 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)
Apr  2 20:03:08 cerise kernel: eth0: Digital DS21143 Tulip rev 65 at 0x200, 00:E0:98:78:14:CE, IRQ 3.
Apr  2 20:03:08 cerise kernel: eth0:  EEPROM default media type Autosense.
Apr  2 20:03:08 cerise kernel: eth0:  Index #0 - Media MII (#11) described by a
21142 MII PHY (3) block.
Apr  2 20:03:08 cerise kernel: eth0:  MII transceiver #0 config 3000 status 7809 advertising 01e1.
Apr  2 20:03:08 cerise cardmgr[426]: executing: './network start eth0'
Apr  2 20:03:14 cerise kernel: eth0: Setting full-duplex based on MII#0 link partner capability of 4461.
Apr  2 20:03:14 cerise kernel: eth0: Tx hung, 9 vs. 0.
Apr  2 20:03:15 cerise rc: Starting linuxconf succeeded
Apr  2 20:04:14 cerise kernel: eth0: Tx hung, 9 vs. 0.
Apr  2 20:05:14 cerise kernel: eth0: Tx hung, 9 vs. 0.

Sad still same symptoms...

Re: Question d-link dfe-660tx cardbus: eth0: Tx hung, 9 vs. 0. ?????? (Jochen Kirsch)
Date: 2000, Apr 03
From: Jochen Kirsch cerise

Thanks David for your answer!

>It is an interrupt delivery problem, and it is likely to be fixed in
>more up to date PCMCIA drivers.  The current release is 3.1.13.
>
>-- Dave

I've installed the new release, but unfortunately the problem resists... (see /var/log/messages below) (and in addition I have to start the network by hand now: ifup eth0) Is it right that the problem has to be solved inside the file tulip_cb.c? And do I have to wait for the next release? :-(

Thanks for any hints.

Jochen Kirsch.

===================================================

/var/log/messages:

Apr  3 22:49:45 cerise pcmcia: Starting PCMCIA services:
Apr  3 22:49:45 cerise pcmcia:  modules
Apr  3 22:49:45 cerise kernel: Linux PCMCIA Card Services 3.1.13
Apr  3 22:49:45 cerise kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 21:07:39
EST 2000
Apr  3 22:49:45 cerise kernel:   options:  [pci] [cardbus] [apm]
Apr  3 22:49:45 cerise kernel: PCI routing table version 1.0 at 0xfdf60
Apr  3 22:49:45 cerise kernel:   00:0a.0 -> irq 9
Apr  3 22:49:45 cerise kernel: Intel PCIC probe:
Apr  3 22:49:45 cerise kernel:   Ricoh RL5C478 PCI-to-CardBus at slot 00:0a, mem 0x68000000
Apr  3 22:49:45 cerise kernel:     host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 32/34]
Apr  3 22:49:45 cerise kernel:     host opts [1]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 35/37]
Apr  3 22:49:45 cerise kernel:     PCI irq 9 test failed
Apr  3 22:49:45 cerise kernel:     ISA irqs (default) = 3,4,5,7,10,11,12 polling interval = 1000 ms
Apr  3 22:49:45 cerise pcmcia:  cardmgr.
Apr  3 22:49:45 cerise rc: Starting pcmcia succeeded
Apr  3 22:49:45 cerise cardmgr[423]: starting, version is 3.1.13
Apr  3 22:49:45 cerise cardmgr[423]: watching 2 sockets
Apr  3 22:49:45 cerise kernel: cs: IO port probe 0x1000-0x17ff: clean.
Apr  3 22:49:45 cerise kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x140-0x147 0x378-0x37f 0x4d0-0x4d7
Apr  3 22:49:45 cerise kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr  3 22:49:45 cerise kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019
Apr  3 22:49:45 cerise cardmgr[423]: initializing socket 0
Apr  3 22:49:45 cerise cardmgr[423]: socket 0: Linksys EtherFast 10/100
Apr  3 22:49:46 cerise cardmgr[423]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/cb_enabler.o'
Apr  3 22:49:46 cerise cardmgr[423]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/tulip_cb.o'
Apr  3 22:49:46 cerise kernel: cs: cb_config(bus 32)
Apr  3 22:49:46 cerise kernel:   fn 0 bar 1: io 0x200-0x27f
Apr  3 22:49:46 cerise kernel:   fn 0 bar 2: mem 0x600c0000-0x600c03ff
Apr  3 22:49:46 cerise kernel:   fn 0 rom: mem 0x60080000-0x600bffff
Apr  3 22:49:46 cerise kernel: tulip_attach(bus 32, function 0)
Apr  3 22:49:46 cerise 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)
Apr  3 22:49:46 cerise kernel: eth0: Digital DS21143 Tulip rev 65 at 0x200, 00:E0:98:78:14:CE, IRQ 5.
Apr  3 22:49:46 cerise kernel: eth0:  EEPROM default media type Autosense.
Apr  3 22:49:46 cerise kernel: eth0:  Index #0 - Media MII (#11) described by a
21142 MII PHY (3) block.
Apr  3 22:49:46 cerise kernel: eth0:  MII transceiver #0 config 3000 status 7809 advertising 01e1.
Apr  3 22:49:46 cerise cardmgr[423]: executing: './network start eth0'
Apr  3 22:51:03 cerise kernel: eth0: Setting full-duplex based on MII#0 link partner capability of 4461.
Apr  3 22:51:03 cerise kernel: eth0: Tx hung, 9 vs. 0.
Apr  3 22:52:03 cerise kernel: eth0: Tx hung, 9 vs. 0.
Apr  3 22:53:03 cerise kernel: eth0: Tx hung, 9 vs. 0.

None Another thing to try

Re: Sad still same symptoms... (Jochen Kirsch)
Date: 2000, Apr 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Try setting

  PCIC_OPTS="irq_mode=2"

-- Dave

Sad no luck...

Re: Question d-link dfe-660tx cardbus: eth0: Tx hung, 9 vs. 0. ?????? (Jochen Kirsch)
Date: 2000, Apr 03
From: Jochen Kirsch cerise

Thanks again for your immediate answer. But I have no luck: the problem persists...

Bonne nuit.

Jochen Kirsch.

Feedback dump_pirq output

Re: Question d-link dfe-660tx cardbus: eth0: Tx hung, 9 vs. 0. ?????? (Jochen Kirsch)
Date: 2000, Apr 04
From: Jochen Kirsch cerise

Hello again, here is the output of the dump_pirq script. I hope this helps...

Jochen Kirsch.

==================================================

Interrupt routing table found at address 0xfdf60:
  Version 1.0, size 0x0080
  Interrupt router is device 00:07.0
  PCI exclusive interrupt mask: 0x0000
  Compatible router: vendor 0x8086 device 0x122e

Device 00:01.0 (slot 0):
  INTA: link 0x60, irq mask 0x0200
  INTB: link 0x61, irq mask 0x0200
  INTC: link 0x62, irq mask 0x0200
  INTD: link 0x63, irq mask 0x0200

Device 00:07.0 (slot 0):
  INTD: link 0x63, irq mask 0x0200

Device 00:08.0 (slot 0):
  INTA: link 0x60, irq mask 0x0200
  INTB: link 0x61, irq mask 0x0200

Device 00:09.0 (slot 0):
  INTA: link 0x62, irq mask 0x0200

Device 00:0a.0 (slot 0):
  INTA: link 0x61, irq mask 0x0200
  INTB: link 0x62, irq mask 0x0200

Device 00:0b.0 (slot 0):
  INTA: link 0x60, irq mask 0x0200

Interrupt router: Intel 82371AB PIIX4/PIIX4E PCI-to-ISA bridge
  PIRQ1 (link 0x60): irq 9
  PIRQ2 (link 0x61): irq 9
  PIRQ3 (link 0x62): irq 9
  PIRQ4 (link 0x63): unrouted
  Serial IRQ: [enabled] [quiet] [frame=21] [pulse=4]

Feedback "PCI irq 9 test failed" again... :-(

Re: Question d-link dfe-660tx cardbus: eth0: Tx hung, 9 vs. 0. ?????? (Jochen Kirsch)
Date: 2000, Apr 05
From: Jochen Kirsch cerise

thank you very much for providing the 3.1.14 version of the pcmcia-package. I would have really preferred it to tell you a success story, but I'm sorry, unfortunately the irq 9 test still fails. I don't understand why this irq 9 is that important as irq 3 is actually assigned to the card!? Whereas under windows irq 9 is assigned to the card and (astonishingly) also to my soundcard/video chip (neomagic magicmedia 256av+ac97 driver(wdm)); and windows reports no conflicts!? But I noticed the following: since I have inserted the new d-ling card windows reports after booting that setting the soundcard to full duplex mode failed (and after that something like: IP:port already in use); but this behaviour persists even after taking the network card out of my computer and reinstalling the soundcard driver... I don't understand that, but perhaps it is useful for you.

====================================================

here once again the /var/log/messages output:

Apr  5 04:53:58 cerise pcmcia: Starting PCMCIA services:
Apr  5 04:53:58 cerise pcmcia:  modules
Apr  5 04:53:58 cerise kernel: Linux PCMCIA Card Services 3.1.14
Apr  5 04:53:58 cerise kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 21:07:39
EST 2000
Apr  5 04:53:58 cerise kernel:   options:  [pci] [cardbus] [apm]
Apr  5 04:53:58 cerise kernel: PCI routing table version 1.0 at 0xfdf60
Apr  5 04:53:58 cerise kernel:   00:0a.0 -> irq 9
Apr  5 04:53:58 cerise kernel: Intel PCIC probe:
Apr  5 04:53:58 cerise kernel:   Ricoh RL5C478 rev 80 PCI-to-CardBus at slot 00:0a, mem 0x68000000
Apr  5 04:53:58 cerise kernel:     host opts [0]: [serial irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 32/34]
Apr  5 04:53:58 cerise kernel:     host opts [1]: [serial irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 35/37]
Apr  5 04:53:58 cerise kernel:     PCI irq 9 test failed
Apr  5 04:53:58 cerise kernel:     ISA irqs (default) = 3,4,5,7,10,11,12 polling interval = 1000 ms
Apr  5 04:53:58 cerise pcmcia:  cardmgr.
Apr  5 04:53:59 cerise rc: Starting pcmcia succeeded
Apr  5 04:53:59 cerise cardmgr[423]: starting, version is 3.1.14
Apr  5 04:53:59 cerise cardmgr[423]: watching 2 sockets
Apr  5 04:53:59 cerise kernel: cs: IO port probe 0x1000-0x17ff: clean.
Apr  5 04:53:59 cerise kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x140-0x147 0x378-0x37f 0x4d0-0x4d7
Apr  5 04:53:59 cerise kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr  5 04:53:59 cerise kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019
Apr  5 04:53:59 cerise cardmgr[423]: initializing socket 0
Apr  5 04:53:59 cerise cardmgr[423]: socket 0: Linksys EtherFast 10/100
Apr  5 04:53:59 cerise cardmgr[423]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/cb_enabler.o'
Apr  5 04:53:59 cerise cardmgr[423]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/tulip_cb.o'
Apr  5 04:53:59 cerise kernel: cs: cb_config(bus 32)
Apr  5 04:53:59 cerise kernel:   fn 0 bar 1: io 0x200-0x27f
Apr  5 04:53:59 cerise kernel:   fn 0 bar 2: mem 0x600c0000-0x600c03ff
Apr  5 04:53:59 cerise kernel:   fn 0 rom: mem 0x60080000-0x600bffff
Apr  5 04:53:59 cerise kernel: tulip_attach(bus 32, function 0)
Apr  5 04:53:59 cerise 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)
Apr  5 04:53:59 cerise kernel: eth0: Digital DS21143 Tulip rev 65 at 0x200, 00:E0:98:78:14:CE, IRQ 3.
Apr  5 04:53:59 cerise kernel: eth0:  EEPROM default media type Autosense.
Apr  5 04:53:59 cerise kernel: eth0:  Index #0 - Media MII (#11) described by a
21142 MII PHY (3) block.
Apr  5 04:53:59 cerise kernel: eth0:  MII transceiver #0 config 3000 status 7809 advertising 01e1.
Apr  5 04:53:59 cerise cardmgr[423]: executing: './network start eth0'
Apr  5 04:57:34 cerise kernel: eth0: Setting full-duplex based on MII#0 link partner capability of 4461.
Apr  5 04:57:34 cerise kernel: eth0: Tx hung, 9 vs. 0.
Apr  5 04:58:34 cerise kernel: eth0: Tx hung, 9 vs. 0.
Apr 5 05:00:54 cerise last message repeated 2 times

Feedback same problem

Re: Feedback "PCI irq 9 test failed" again... :-( (Jochen Kirsch)
Date: 2000, Apr 19
From: Lincoln Stein lstein

I experienced exactly the same problem when updating from 3.1.11 to 3.1.14. In addition, the whole system freezes up and needs to be coldbooted on a card insertion.

vitals:

	Sony 505TR
	linux 2.2.13 (slackware)

Under 3.1.11 I would see irq 9 being shared by i82365 and the usb driver. Under 3.1.14 i82365 polls.

Lincoln

Question one last question

Re: Question d-link dfe-660tx cardbus: eth0: Tx hung, 9 vs. 0. ?????? (Jochen Kirsch)
Date: 2000, Apr 08
From: Jochen Kirsch cerise

Hi,

I would like to pose one more question: are there any chances to get my d-link card work with a future release of the pcmcia-cs package/tulip_cb driver, or is the problem due to my very combination of the Sony-notebook and the d-link card so that this will never be fixed and will never work (and I will have to look for a different card :-(( to get my Linux online)? As the d-link dfe-660 figures in the hardware compatibility list (though experimental) there must be some guys out there who have been luckier than me...!? Thanks for any comment.

Jochen Kirsch.

None The card is not the problem

Re: Question one last question (Jochen Kirsch)
Date: 2000, Apr 08
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The tulip driver is not the problem.  The problem is with the Cardbus
bridge in your laptop, which is not delivering interrupts properly.

-- Dave

Question buggy cardbus bridge - consequence for other cards; workaround?

Re: None The card is not the problem (David Hinds)
Date: 2000, Apr 08
From: Jochen Kirsch cerise

Thank you for your answer, David.

I'm sorry bothering you again, but here are two other questions (which perhaps may be of some interest for others, too; and I don't know anybody else knowing the answer).

1) As the cardbus bridge in my laptop has obviously problems in delivering the interrupt properly, is the problem likely to appear with other network cards, too? I.e., only with 32bit cardbus cards or also with 16bit pc cards; of which type should my next card be?

2) Facing the fact that the d-link card works under windoze (windoze or the win driver (?) obviously not taking care of the delivery problems...), the following came to my mind: ok, you said that the driver is not the problem. I admit that, as long as one has "normal" hardware (cardbus bridge) that behaves correctly. Would it be theoretically possible to either modify the driver or the piece of code in any other program concerned with receiving the improperly delivered interrupt, so that the hardware bug is ignored?

Thanx.

Jochen Kirsch.

None I don't know

Re: Question buggy cardbus bridge - consequence for other cards; workaround? (Jochen Kirsch)
Date: 2000, Apr 11
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Your bridge itself is fine.  The Linux driver for the bridge is the
problem.  And it is not obvious to me what specifically needs to be
fixed.  I also cannot tell if the problem will only affect Cardbus
cards, or 16-bit cards as well.

For the moment, all I can do is to tell you to be patient, and maybe
I'll be able to come up with some new things to try.

-- Dave

None ok

Re: None I don't know (David Hinds)
Date: 2000, Apr 12
From: Jochen Kirsch cerise

Thanks for your answer.

Jo.

Sad 25-Apr-00 beta results

Re: Question d-link dfe-660tx cardbus: eth0: Tx hung, 9 vs. 0. ?????? (Jochen Kirsch)
Date: 2000, Apr 26
From: Jochen Kirsch cerise

ok, I have installed the new version but the results are not very encouraging... as I tried to reboot I got the following:

depmod: unresolved symbols in /lib/modules/2.2.14-5.0/pcmcia/aha1542x_cs.o

~/apa1480_cb.o

~/fdomain_cs.o

~/ibmtr_cs.o

~/qlogig_cs.o

and when the kernel tried to load the pcmcia services this ended up with:

... [<c01ce2ce>] [<c010a1c1>] [<c011176a>] [<c01ce576>] code: 8b 4a 04 85 c9 74 22 8b 5a 18 8b 02 89 01 8b 0a 85 c9 74 08

Aiee, killing interrupt handler

Kernel panic: Attempted to kill the idle task!

In interrupt handler - not syncing

after that only a hard reset helps

And: I'm unable to boot with my bootdisk and after booting with a rescue disk I cannot mount the linux partition(s)!! (something like: wrong superblock, too many mounted filesystems...)

Any ideas how to recover?

Thank you.

Jochen Kirsch.

None Several issues

Re: Sad 25-Apr-00 beta results (Jochen Kirsch)
Date: 2000, Apr 26
From: David Hinds <dhinds@pcmcia.sourceforge.org>

To boot, at the lilo prompt, say something like "linux single" to boot
to single user mode.  Then you can disable PCMCIA and then boot
normally.  Saying "linux PCMCIA=no" may also work.

I don't understand the unresolved symbol issues.  Based on the list of
modules, it sounds like the PCMCIA configure script thought you had
SCSI support in your kernel, but it isn't actually present.  I'm not
sure how that sort of goof-up could happen.  You could re-do "make
config" for the PCMCIA stuff and check the output carefully.

As for why the kernel trap, I'm not sure.  I'll take a closer look at
the changes I made for this beta.

-- Dave

Feedback 26-Apr-00 beta - results

Re: Question d-link dfe-660tx cardbus: eth0: Tx hung, 9 vs. 0. ?????? (Jochen Kirsch)
Date: 2000, Apr 27
From: Jochen Kirsch cerise

With this version the kernel trap has fortunately disappeared and my system boots normally, but the "Tx hung, 9 vs. 0"-problem is still there... :-(

Nonetheless, thanks for the "linux single" hint.

Best regards,

Jo.

==========================================================

Here is my /var/log/messages:

Apr 27 20:40:40 cerise syslogd 1.3-3: restart.
Apr 27 20:40:40 cerise syslog: syslogd startup succeeded
Apr 27 20:40:40 cerise syslog: klogd startup succeeded
Apr 27 20:40:40 cerise kernel: klogd 1.3-3, log source = /proc/kmsg started.
Apr 27 20:40:40 cerise kernel: Inspecting /boot/System.map-2.2.14-5.0
Apr 27 20:40:40 cerise kernel: Loaded 6922 symbols from /boot/System.map-2.2.14-5.0.
Apr 27 20:40:40 cerise kernel: Symbols match kernel version 2.2.14.
Apr 27 20:40:40 cerise kernel: Loaded 81 symbols from 2 modules.
Apr 27 20:40:40 cerise kernel: Linux version 2.2.14-5.0 (root@cerise) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #5 Fri Apr 21 01:08:09 CEST 2000 
Apr 27 20:40:40 cerise kernel: Detected 364743644 Hz processor. 
Apr 27 20:40:40 cerise kernel: Console: colour VGA+ 80x25 
Apr 27 20:40:40 cerise kernel: Calibrating delay loop... 363.72 BogoMIPS 
Apr 27 20:40:40 cerise kernel: Memory: 63068k/65472k available (980k kernel code, 416k reserved, 948k data, 60k init, 0k bigmem) 
Apr 27 20:40:40 cerise kernel: Dentry hash table entries: 262144 (order 9, 2048k) 
Apr 27 20:40:40 cerise kernel: Buffer cache hash table entries: 65536 (order 6, 256k) 
Apr 27 20:40:40 cerise kernel: Page cache hash table entries: 16384 (order 4, 64k) 
Apr 27 20:40:40 cerise kernel: VFS: Diskquotas version dquot_6.4.0 initialized 
Apr 27 20:40:40 cerise kernel: CPU: Intel Mobile Pentium II stepping 0a 
Apr 27 20:40:40 cerise kernel: Checking 386/387 coupling... OK, FPU using exception 16 error reporting. 
Apr 27 20:40:40 cerise kernel: Checking 'hlt' instruction... OK. 
Apr 27 20:40:41 cerise kernel: POSIX conformance testing by UNIFIX 
Apr 27 20:40:41 cerise kernel: mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au) 
Apr 27 20:40:41 cerise kernel: PCI: PCI BIOS revision 2.10 entry at 0xfd9e4 
Apr 27 20:40:41 cerise kernel: PCI: Using configuration type 1 
Apr 27 20:40:41 cerise kernel: PCI: Probing PCI hardware 
Apr 27 20:40:41 cerise kernel: PCI: Enabling I/O for device 00:3a 
Apr 27 20:40:41 cerise kernel: PCI: Enabling memory for device 00:48 
Apr 27 20:40:41 cerise kernel: Linux NET4.0 for Linux 2.2 
Apr 27 20:40:41 cerise kernel: Based upon Swansea University Computer Society NET3.039 
Apr 27 20:40:41 cerise kernel: NET4: Unix domain sockets 1.0 for Linux NET4.0. 
Apr 27 20:40:41 cerise kernel: NET4: Linux TCP/IP 1.0 for NET4.0 
Apr 27 20:40:41 cerise kernel: IP Protocols: ICMP, UDP, TCP, IGMP 
Apr 27 20:40:41 cerise kernel: TCP: Hash tables configured (ehash 65536 bhash 65536) 
Apr 27 20:40:41 cerise kernel: Initializing RT netlink socket 
Apr 27 20:40:41 cerise kernel: Starting kswapd v 1.5  
Apr 27 20:40:41 cerise kernel: Detected PS/2 Mouse Port. 
Apr 27 20:40:41 cerise kernel: Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled 
Apr 27 20:40:41 cerise kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A 
Apr 27 20:40:41 cerise kernel: ttyS02 at 0x03e8 (irq = 4) is a 16550A 
Apr 27 20:40:41 cerise kernel: pty: 256 Unix98 ptys configured 
Apr 27 20:40:41 cerise kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9) 
Apr 27 20:40:41 cerise kernel: Real Time Clock Driver v1.09 
Apr 27 20:40:41 cerise kernel: RAM disk driver initialized:  16 RAM disks of 4096K size 
Apr 27 20:40:41 cerise kernel: PIIX4: IDE controller on PCI bus 00 dev 39 
Apr 27 20:40:41 cerise kernel: PIIX4: not 100% native mode: will probe irqs later 
Apr 27 20:40:41 cerise kernel:     ide0: BM-DMA at 0xfcf0-0xfcf7, BIOS settings: hda:DMA, hdb:pio 
Apr 27 20:40:41 cerise kernel:     ide1: BM-DMA at 0xfcf8-0xfcff, BIOS settings: hdc:pio, hdd:pio 
Apr 27 20:40:41 cerise kernel: hda: IBM-DBCA-206480, ATA DISK drive 
Apr 27 20:40:41 cerise kernel: hdc: TOSHIBA DVD-ROM SD-C2102, ATAPI CDROM drive 
Apr 27 20:40:41 cerise kernel: ide2: ports already in use, skipping probe 
Apr 27 20:40:41 cerise kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 
Apr 27 20:40:41 cerise kernel: ide1 at 0x170-0x177,0x376 on irq 15 
Apr 27 20:40:41 cerise kernel: hda: IBM-DBCA-206480, 6194MB w/420kB Cache, CHS=839/240/63 
Apr 27 20:40:41 cerise kernel: hdc: ATAPI 20X DVD-ROM drive, 128kB Cache 
Apr 27 20:40:41 cerise kernel: Uniform CDROM driver Revision: 2.56 
Apr 27 20:40:41 cerise kernel: Floppy drive(s): fd0 is 1.44M 
Apr 27 20:40:41 cerise kernel: FDC 0 is a post-1991 82077 
Apr 27 20:40:41 cerise kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 
Apr 27 20:40:41 cerise kernel: raid5: measuring checksumming speed 
Apr 27 20:40:41 cerise kernel: raid5: MMX detected, trying high-speed MMX checksum routines 
Apr 27 20:40:41 cerise kernel:    pII_mmx   :   845.058 MB/sec 
Apr 27 20:40:41 cerise kernel:    p5_mmx    :   897.255 MB/sec 
Apr 27 20:40:41 cerise kernel:    8regs     :   626.364 MB/sec 
Apr 27 20:40:41 cerise kernel:    32regs    :   351.282 MB/sec 
Apr 27 20:40:41 cerise kernel: using fastest function: p5_mmx (897.255 MB/sec) 
Apr 27 20:40:41 cerise kernel: md.c: sizeof(mdp_super_t) = 4096 
Apr 27 20:40:41 cerise kernel: Partition check: 
Apr 27 20:40:41 cerise kernel:  hda: hda1 hda2 hda3 < hda5 hda6 > hda4 
Apr 27 20:40:41 cerise kernel: autodetecting RAID arrays 
Apr 27 20:40:41 cerise kernel: autorun ... 
Apr 27 20:40:41 cerise kernel: ... autorun DONE. 
Apr 27 20:40:41 cerise kernel: VFS: Mounted root (ext2 filesystem) readonly. 
Apr 27 20:40:41 cerise kernel: Freeing unused kernel memory: 60k freed 
Apr 27 20:40:41 cerise kernel: Adding Swap: 105800k swap-space (priority -1) 
Apr 27 20:40:41 cerise identd: identd startup succeeded
Apr 27 20:40:41 cerise atd: atd startup succeeded
Apr 27 20:40:42 cerise crond: crond startup succeeded
Apr 27 20:40:42 cerise sound: Starting sound: 
Apr 27 20:40:42 cerise kernel: NeoMagic 256AV/256ZX audio driver, version 1.1 
Apr 27 20:40:42 cerise kernel: NM256: Congratulations. You're not running Eunice. 
Apr 27 20:40:42 cerise kernel: NM256: Found card signature in video RAM: 0x27ec00 
Apr 27 20:40:42 cerise kernel: NM256: Mapping port 1 from 0x266c00 - 0x27ec00 
Apr 27 20:40:42 cerise kernel: Initialized NeoMagic 256AV audio in PCI native mode 
Apr 27 20:40:42 cerise kernel: Initialized AC97 mixer 
Apr 27 20:40:42 cerise kernel: Done installing NM256 audio driver. 
Apr 27 20:40:42 cerise sound: 
Apr 27 20:40:42 cerise rc: Starting sound succeeded
Apr 27 20:40:42 cerise pcmcia: Starting PCMCIA services:
Apr 27 20:40:42 cerise pcmcia:  modules
Apr 27 20:40:42 cerise kernel: Linux PCMCIA Card Services 3.1.15 
Apr 27 20:40:42 cerise kernel:   kernel build: 2.2.14-5.0 #5 Fri Apr 21 01:08:09 CEST 2000 
Apr 27 20:40:42 cerise kernel:   options:  [pci] [cardbus] [apm] 
Apr 27 20:40:42 cerise kernel: PCI routing table version 1.0 at 0xfdf60 
Apr 27 20:40:42 cerise kernel:   00:0a.0 -> irq 9 
Apr 27 20:40:42 cerise kernel: Intel PCIC probe:  
Apr 27 20:40:42 cerise kernel:   Ricoh RL5C478 rev 80 PCI-to-CardBus at slot 00:0a, mem 0x68000000 
Apr 27 20:40:42 cerise kernel:     host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 32/34] 
Apr 27 20:40:42 cerise kernel:     host opts [1]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 35/37] 
Apr 27 20:40:42 cerise kernel:     ISA irqs (default) = 3,4,5,7,10,11,12 PCI status changes 
Apr 27 20:40:42 cerise pcmcia:  cardmgr.
Apr 27 20:40:42 cerise rc: Starting pcmcia succeeded
Apr 27 20:40:42 cerise cardmgr[428]: starting, version is 3.1.15
Apr 27 20:40:43 cerise cardmgr[428]: watching 2 sockets
Apr 27 20:40:43 cerise kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Apr 27 20:40:43 cerise kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x140-0x147 0x378-0x37f 0x4d0-0x4d7 
Apr 27 20:40:43 cerise kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Apr 27 20:40:43 cerise kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019 
Apr 27 20:40:43 cerise cardmgr[428]: initializing socket 0
Apr 27 20:40:43 cerise cardmgr[428]: socket 0: Linksys EtherFast 10/100
Apr 27 20:40:43 cerise cardmgr[428]: executing: 'modprobe cb_enabler'
Apr 27 20:40:43 cerise cardmgr[428]: executing: 'modprobe tulip_cb'
Apr 27 20:40:43 cerise kernel: cs: cb_config(bus 32) 
Apr 27 20:40:43 cerise kernel:   fn 0 bar 1: io 0x200-0x27f 
Apr 27 20:40:43 cerise kernel:   fn 0 bar 2: mem 0x600c0000-0x600c03ff 
Apr 27 20:40:43 cerise kernel:   fn 0 rom: mem 0x60080000-0x600bffff 
Apr 27 20:40:43 cerise kernel: tulip_attach(device 20:00.0) 
Apr 27 20:40:43 cerise 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) 
Apr 27 20:40:43 cerise kernel: eth0: Digital DS21143 Tulip rev 65 at 0x200, 00:E0:98:78:14:CE, IRQ 9. 
Apr 27 20:40:43 cerise kernel: eth0:  EEPROM default media type Autosense. 
Apr 27 20:40:43 cerise kernel: eth0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block. 
Apr 27 20:40:43 cerise kernel: eth0:  MII transceiver #0 config 3000 status 7809 advertising 01e1. 
Apr 27 20:40:43 cerise cardmgr[428]: executing: './network start eth0'
Apr 27 20:42:47 cerise network: Setting network parameters succeeded
Apr 27 20:42:48 cerise network: Bringing up interface lo succeeded
Apr 27 20:42:48 cerise network: Bringing up interface eth0 succeeded
Apr 27 20:42:51 cerise kernel: eth0: Setting full-duplex based on MII#0 link partner capability of 4461. 
Apr 27 20:42:51 cerise kernel: eth0: Tx hung, 9 vs. 0. 
Apr 27 20:43:51 cerise kernel: eth0: Tx hung, 9 vs. 0. 
Apr 27 20:45:51 cerise last message repeated 2 times
Apr 27 20:47:51 cerise last message repeated 2 times
Apr 27 20:49:51 cerise last message repeated 2 times

Feedback card insertions ok with 26-Apr-beta

Re: Feedback 26-Apr-00 beta - results (Jochen Kirsch)
Date: 2000, Apr 27
From: Jochen Kirsch cerise

yes, card hotswapping is correctly handled by the latest beta: one beep when taking card out and two beeps when inserting card. The relevant modules are correctly un/loaded.

irq_mode=2 or 0 or nothing doesn't change anything...

About one month ago I have tried a Xircom CreditCard 10/100 and that one worked without any problems (but it is 16bit).

Thanks for all your help and advice.

Jo

PS: I'm going to get such an old Xircom card...

Feedback mii-tool results

Re: Question d-link dfe-660tx cardbus: eth0: Tx hung, 9 vs. 0. ?????? (Jochen Kirsch)
Date: 2000, Apr 28
From: Jochen Kirsch cerise

Hi,

here is the output of the mii-tool:

eth0: negotiated 10baseT-FD, link ok
  registers for MII PHY 0: 
    1000 782d 0040 6212 01e1 4461 0003 0000
    0000 0000 0000 0000 0000 0000 0000 0000
    1000 0000 0000 0000 0000 0000 0500 0000
    0039 8236 0f00 ff00 0029 0000 10a0 000b
  product info: vendor 00:10:18, model 33 rev 2
  basic mode:   autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  link partner: 10baseT-FD 10baseT-HD flow-control

Everything seems to be fine, doesn't it?

Jo.

Question Modules don't install

Date: 2000, Apr 07
From: Robert Dalrymple raddal

Hi:  I have been trying to get PCMCIA-CS 3.1.13 to build with
the 2.3.99-pre3 kernel (I need USB) on a Sony VAIO Z505HE.  The problem is in installing pcmcia-cs.  When I do
 `make config; make all; make install'
everything works fine, no error messages.  It's just that
there are no modules appearing in modules directory. They
never get compiled--I looked in the clients directory for example and nothing has compiled there.  

I am running REDHAT 6.1.92. It came with 2.2.15 built and PCMCIA running fine, so it works fine with this machine.

I have PCMCIA = y and CARDBUS=y in the Linux configuration. On booting, dmesg reports Linux PCMCIA card services 3.1.11 and that it is adding card bus controller 0: Ricoh .... and Yenta IRQ list. So the built-in stuff seems fine.

When I install a card, say flash memory card, the log file indicates that /lib/modules/2.3.99-pre3/pcmcia/ide_cs.o is missing.

I have also tried building PCMCIA-CS 3.1.8 but I get compile errors.

Thanks for any help.
Tony
 rad@udel.edu

None The 2.3.* kernel stuff

Re: Question Modules don't install (Robert Dalrymple)
Date: 2000, Apr 07
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If you have enabled PCMCIA support in the 2.3.* kernel, then the
PCMCIA package will not build any of the kernel modules: they are
redundant (assuming the kernel stuff works).

If the kernel stuff is not working, then you can reconfigure the
kernel with PCMCIA turned off.  Then if you rebuild the standalone
PCMCIA package, all the modules will be built.

-- Dave

Sad pcmcia-cs-3.1.13 doesn't compile on 2.3.99-pre3

Date: 2000, Apr 09
From: Sean Harding sharding

pcmcia-cs-3.1.13 fails to compile on linux 2.3.99-pre3 for me. It bombs out in 3c575_cb.c with these errors:

cc -MD -c -O2 -I../include -I/usr/src/linux/include -D__KERNEL__ -DEXPORT_SYMTAB -DMODULE -DCARDBUS 3c575_cb.c In file included from /usr/src/linux/include/asm/hardirq.h:5, from /usr/src/linux/include/linux/interrupt.h:44, from 3c575_cb.c:76: /usr/src/linux/include/linux/irq.h:52: requested alignment is not a constant In file included from /usr/src/linux/include/linux/interrupt.h:44, from 3c575_cb.c:76: /usr/src/linux/include/asm/hardirq.h:12: requested alignment is not a constant In file included from 3c575_cb.c:76: /usr/src/linux/include/linux/interrupt.h:152: requested alignment is not a constant In file included from 3c575_cb.c:78: /usr/src/linux/include/linux/netdevice.h:150: requested alignment is not a constant In file included from 3c575_cb.c:78: /usr/src/linux/include/linux/netdevice.h:433: requested alignment is not a constant make[1]: *** [3c575_cb.o] Error 1 make[1]: Leaving directory `/usr/src/pcmcia-cs-3.1.13/clients' make: *** [all] Error 2

I dug around and couldn't find the problem. I found some stuff on Deja about this error when some of the kernel source files didn't include linux/cache.h (where SMP_CACHE_BYTES and friends are defined). But the important files all seemed to have that include, and the constants look to be defined. So I'm stuck.

Any ideas?

None This is fixed in the current beta for 3.1.14

Re: Sad pcmcia-cs-3.1.13 doesn't compile on 2.3.99-pre3 (Sean Harding)
Date: 2000, Apr 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

See /pcmcia/NEW on sourceforge.org

-- Dave

Question Problems Compiling 3.1.14 on 2.3.99-pre5

Date: 2000, Apr 21
From: Gordon Ross gtg

I'm trying to compile pcmcia-cs-3.1.14 for a 2.3.99-pre5
kernel. However, I get an awfull lot of errors. Can anyone
give me some pointers ?

Sample output from make all gives:

Configuration successful.

make[1]: Entering directory `/usr/src/pd/pcmcia-cs-3.1.14/modules'
cc   -MD -O2 -Wall -Wstrict-prototypes -pipe -I../include/static -I/usr/src/linux/include -I../include  -D__KERNEL__ -DMODULE -c cs.c
In file included from cs.c:66:
cs_internal.h:136: parse error before `ss_entry_t'
cs_internal.h:136: warning: no semicolon at end of struct or union
cs_internal.h:177: parse error before `}'
cs_internal.h:177: warning: data definition has no type or storage class
cs_internal.h:214: parse error before `*'
cs_internal.h:214: warning: function declaration isn't a prototype
cs_internal.h:215: parse error before `*'
cs_internal.h:215: warning: function declaration isn't a prototype
cs_internal.h:216: parse error before `*'
cs_internal.h:216: warning: function declaration isn't a prototype
cs_internal.h:216: `cb_config' redeclared as different kind of symbol
cs_internal.h:155: previous declaration of `cb_config'
cs_internal.h:217: parse error before `*'
cs_internal.h:217: warning: function declaration isn't a prototype
cs_internal.h:218: parse error before `*'
cs_internal.h:218: warning: function declaration isn't a prototype

None Do "make config", then "make all"

Re: Question Problems Compiling 3.1.14 on 2.3.99-pre5 (Gordon Ross)
Date: 2000, Apr 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

In this situation, if you do "make all" on a clean source tree, it
confuses the Makefile and it ends up building the modules directory
when it should not.

-- Dave

Question ISA adapter with Ricoh chipset

Date: 2000, Apr 21
From: Matthias Kattanek mattes

Just putting a system together (RH6.2) and added a PCMCIA ISAbus adapter (with a RICOH RF5C?96 chipset) to fit a wireless pcmcia card.

Everytime I launch pcmcia (/etc/rc.d/init.d/pcmcia start) I get:

 kernel: Linux PCMCIA Card Services 3.1.8
 kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 20:35:25 EST 2000
 kernel:   options:  [pci] [cardbus] [apm]
 kernel: Intel PCIC probe:
 kernel:   Ricoh RF5C296/396 ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 1 socket
 kernel:     host opts [0]: none
 kernel:     ISA irqs (default) = 3,7,9,10,11,12,15 polling interval = 1000 ms
 cardmgr[5248]: starting, version is 3.1.8

and the entire system crashes. Note, no pcmcia card is plugged in at this moment.

finally I figured out that my motherboard has a built-in LPT2 port, which to my knowledge is using the same base io-address 0x3e0, as the pcmcia ISA adapter.

unfortunately the motherboard does not allow to turn the lpt2 port :-((. From what I've learned so far the ricoh PCMCIA chipset allows memory remapping. Is this supported with the current pcmcia package? If so, how would I configure it?

mattes

None Sounds like an IO port scan failure

Re: Question ISA adapter with Ricoh chipset (Matthias Kattanek)
Date: 2000, Apr 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You have a parallel port at 0x3e0?  That would be quite odd: this is
not a standard location for a parallel port.  Also I don't think that
can be the problem, because it should have interfered with correct
identification of the Ricoh chip if it were true.

The PCMCIA-HOWTO has a section about diagnosing startup crashes.  Your
messages show that the interrupt probe succeeded, but you're getting
stuck when cardmgr loads, even with no card inserted.  That matches
the HOWTO description of an IO port scan failure (section 3.4).

Edit the IO port windows in /etc/pcmcia/config.opts.  I'd probably try
deleting the windows one by one until the lock-up goes away.  Another
option would be to try recompiling PCMCIA with "PnP BIOS support"
switched on, which may do a better job of automatically figuring out
IO port resources used by other system devices.

The memory mapping in the Ricoh bridge is for mapping PCMCIA cards
into the host address space.  It doesn't allow you to change the IO
address of the Ricoh bridge itself.  I don't think you can change
that.

-- Dave

Question PCI-PCMCIA can't get Interrupts (Wavelan's adapter)

Date: 2000, Apr 21
From: Timothy Hamlin thamlin

I've been trying to get the newest wavelan card (Orinoco 11Mb "silver") card to work. Resounding success when using in laptops with built-in pcmcia services. (On the Dell Inspiron 7000 and IBM ThinkPad 380D with pcmcia-cs-3.1.14, kernel 2.2.14-5.0 on RedHat 6.2, and wavelan2_cs-6.00.)

Now that I think I understand the cards themselves well enough, I need to get them working in desktops. I'm doing a large field campaign this summer using an array of stations which map lightning, and each station (15 of them) will telemeter data via the wavelans. I have to be ready in the next week and am quite stuck on getting the cards to go on desktops running older pci chipsets.

I'm trying to get the pci-pcmcia host adapter wavelan sells with their cards to work (it is only $60.00 versus ~ $200 for similar adapters I found), and was able to get it to work (with the irq_mode=0 option) on a newer machine. The wavelan card did not work (in fact, the machine would give a high beep then hang upon insertion of the card, but come back upon removal). This problem is corrected in the wavelan2_cs-6.01BETA which came out a few days ago. (I believe the problem was that the wavelan driver didn't know how to handle PCI only interrupts until this version.) So, it seems to work correctly with the PCI 440BX controller chip.

The problem is, the machines I'm using are older than this 
(a mix of pentium 1 motherboards.  When I try to start 
pcmcia on these, it finds the contoller, but does not 
assign an interrupt.  Here are the details:
------
dmesg:
------
Linux version 2.2.14-5.0 (root@porky.devel.redhat.com) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Tue Mar 7 20:53:41 EST 2000
relocating initrd image:
    initrd_start:0xc0f97000    initrd_end:0xc0fff4af
    mem_start:0xc0272000    mem_end:0xc1ff0000
    initrd_size:0x000684af     dest:0xc1f87000
Detected 166451974 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 66.36 BogoMIPS
Memory: 30080k/32704k available (1084k kernel code, 416k reserved, 640k data, 64k init, 0k bigmem)
Dentry hash table entries: 262144 (order 9, 2048k)
Buffer cache hash table entries: 32768 (order 5, 128k)
Page cache hash table entries: 8192 (order 3, 32k)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Intel Pentium 75 - 200 stepping 0c
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
Intel Pentium with F0 0F bug - workaround enabled.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfdba1
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 32768 bhash 32768)
Initializing RT netlink socket
Starting kswapd v 1.5 
Detected PS/2 Mouse Port.
Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
ttyS02 at 0x03e8 (irq = 4) is a 16550A
ttyS03 at 0x02e8 (irq = 3) is a 16550A
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9)
Real Time Clock Driver v1.09
RAM disk driver initialized:  16 RAM disks of 4096K size
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
hda: QUANTUM FIREBALL EL2.5A, ATA DISK drive
hdb: ST328040A, ATA DISK drive
ide2: ports already in use, skipping probe
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: QUANTUM FIREBALL EL2.5A, 2445MB w/418kB Cache, CHS=621/128/63
hdb: ST328040A, 27199MB w/512kB Cache, CHS=3467/255/63
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
   8regs     :   168.783 MB/sec
   32regs    :   123.825 MB/sec
using fastest function: 8regs (168.783 MB/sec)
scsi : 0 hosts.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
 hda: hda1 hda2 hda3 hda4
 hdb: hdb1
RAMDISK: Compressed image found at block 0
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem).
scsi0 : AdvanSys SCSI 3.2M: PCI Ultra 240 CDB: IO EC00/F, IRQ 10
scsi : 1 host.
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 64k freed
Adding Swap: 68536k swap-space (priority -1)
Adding Swap: 68536k swap-space (priority -2)
Linux PCMCIA Card Services 3.1.14
  kernel build: 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000
  options:  [pci] [cardbus] [apm]
Intel PCIC probe: 
  TI 1225 rev 01 PCI-to-CardBus at slot 00:13, mem 0x68000000
    host opts [0]: [pci only] [no pci irq] [lat 168/176] [bus 32/34]
    host opts [1]: [pci only] [no pci irq] [lat 168/176] [bus 35/37]
    NO card interrupts, polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: excluding 0x12e8-0x12ef 0x13e8-0x13ef
cs: IO port probe 0x0100-0x04ff: excluding 0x158-0x15f 0x170-0x177 0x290-0x297 0x370-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
unloading PCMCIA Card Services
Linux PCMCIA Card Services 3.1.14
  kernel build: 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000
  options:  [pci] [cardbus] [apm]
Intel PCIC probe: 
  TI 1225 rev 01 PCI-to-CardBus at slot 00:13, mem 0x68000000
    host opts [0]: [pci only] [no pci irq] [lat 168/176] [bus 32/34]
    host opts [1]: [pci only] [no pci irq] [lat 168/176] [bus 35/37]
    NO card interrupts, polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: excluding 0x12e8-0x12ef 0x13e8-0x13ef
cs: IO port probe 0x0100-0x04ff: excluding 0x158-0x15f 0x170-0x177 0x290-0x297 0x370-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
wavelan2_cs: RequestIRQ: Resource in use

----- /var/log/messages clip: -----

Apr 21 17:58:09 lma_e cardmgr[615]: watching 2 sockets
Apr 21 17:58:09 lma_e kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x12e8-0x12ef 0x13e8-0x13ef 
Apr 21 17:58:09 lma_e kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x158-0x15f 0x170-0x177 0x290-0x297 0x370-0x37f 0x4d0-0x4d7 
Apr 21 17:58:09 lma_e kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Apr 21 18:00:07 lma_e cardmgr[615]: initializing socket 0
Apr 21 18:00:07 lma_e kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. 
Apr 21 18:00:07 lma_e cardmgr[615]: socket 0: Lucent Technologies WaveLAN/IEEE
Apr 21 18:00:07 lma_e cardmgr[615]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/wavelan2_cs.o port_type=3 channel=5 network_name=LMA'
Apr 21 18:00:07 lma_e kernel: wavelan2_cs: RequestIRQ: Resource in use 
Apr 21 18:00:08 lma_e cardmgr[615]: get dev info on socket 0 failed: Resource temporarily unavailable

---
/proc/interrupts:
---
           CPU0       
  0:     117763          XT-PIC  timer
  1:       1178          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  8:          1          XT-PIC  rtc
 10:          7          XT-PIC  advansys
 12:          0          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:      62736          XT-PIC  ide0
NMI:          0

--- lspci: ---

00:00.0 Host bridge: Intel Corporation 430TX - 82439TX MTXC (rev 01)
00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 01)
00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 01)
00:12.0 SCSI storage controller: Advanced System Products, Inc ABP940-U / ABP960-U (rev 03)
00:13.0 CardBus bridge: Texas Instruments PCI1225 (rev 01)
00:13.1 CardBus bridge: Texas Instruments PCI1225 (rev 01)
00:14.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 01)

Any ideas?? - I'm really really getting getting nervous, much egg on face if I can't get these things going...

thanks!

Tim

More PS - PCI chipset bx works, but not tx

Re: Question PCI-PCMCIA can't get Interrupts (Wavelan's adapter) (Timothy Hamlin)
Date: 2000, Apr 24
From: Timothy Hamlin thamlin

just an additional note,

I mentioned that I got everything working on an "older" system (pentium II class motherboard) with the bx class of PCI chiptset.

What I forgot to mention was that the systems I really need to get to go are of the tx class of PCI sets.

thanks

tim

None PCI interrupt routing issues

Re: Question PCI-PCMCIA can't get Interrupts (Wavelan's adapter) (Timothy Hamlin)
Date: 2000, Apr 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The problem isn't with your PCI chipset; it is with your old BIOS.  It
is not providing a PCI interrupt routing table, so the PCMCIA drivers
can't figure out what irq to use for the CardBus bridge.

There are two missing pieces of information: the drivers need to know
how the PCI INT* lines for the CardBus bridge are connected to your
host bridge's PIRQ inputs, and then which CPU irq's are generated for
each PIRQ.  The interrupt routing table might say "for device X, PCI
INTA is connected to PIRQY", and then we can check the PCI bridge to
determine that PIRQY connects to irq Z.  The X->Y mapping is fixed by
how your boards are wired; the Y->Z mapping is programmable.

Try getting the 24-Apr-00 beta from sourceforge.org in /pcmcia/NEW and
run the 'dump_pirq' program in the debug-tools directory.  This will
dump your host bridge's routing information (the Y->Z mapping).  The
X->Y mapping can't be figured out by software.

-- Dave

Question Compaq Laptop M700 hangs when card is inserted or ejected

Date: 2000, Apr 22
From: Atanu Ghosh atanu

Hardware: 	Compaq laptop M700
PC card:	Lucent Wavelan/IEEE Silver card
Distribution:	Redhat 6.2
Kernel Version:	2.2.14-5.0
Pcmcia:		pcmcia-cs-3.1.14

Firstly I have the card working with this kernel with pcmcia-cs-3.1.8
and the wavelan driver wavelan2_cs-6.00 from Lucent. Insertion and
ejection of the card works.

I decided to upgrade to the new driver wvlan_cs which is in the later
pcmcia distributions. If I insert or remove the card then the machine
hangs up and requires a reboot. There are no clues in the log files.

Interestingly it is possible to stop the cardmgr insert the card and
restart the carmgr. The card is discovered correctly and works.

To remove the card it is necessary to stop the cardmgr before removing
the card.

On reboot if the card is in the machine it is correctly discovered and
works.

I believe the inserting/removing any card will cause a lockup with the
latest pcmcia-cs-3.1.14 release. I tried putting in a ethernet card
which also caused a hangup.

I have not made any significant changes to the scripts in "/etc/pcmcia".

Although the PCMCIA_HOWTO warns that insertion and ejection may be a
problem, it does work with an older version of the pcmcia code.

	Atanu.

----------------------------------------
Linux version 2.2.14-5.0 (root@lamb) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #2 Thu Apr 13 15:55:59 EST 2000
----------------------------------------

----------------------------------------
Linux PCMCIA Card Services 3.1.8
  kernel build: 2.2.14-5.0 #2 Thu Apr 13 15:55:59 EST 2000
  options:  [pci] [cardbus] [apm]
Intel PCIC probe: 
  TI 1450 PCI-to-CardBus at bus 0 slot 4, mem 0x7fffe000, 2 sockets
    host opts [0]: [pwr save] [pci + serial irq] [no pci irq] [lat 66/176] [bus 2/2]
    host opts [1]: [pwr save] [pci + serial irq] [no pci irq] [lat 66/176] [bus 3/3]
    ISA irqs (scanned) = 3,4,5,7,9,10,15 status change on irq 15
cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x10ff
cs: IO port probe 0x0100-0x04ff: excluding 0x100-0x107 0x170-0x177 0x370-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
eth1: WaveLAN/IEEE, io_addr 0x180, irq 3, mac_address 00:60:1D:F6:34:B0
----------------------------------------

----------------------------------------
Linux PCMCIA Card Services 3.1.14
  kernel build: 2.2.14-5.0 #2 Thu Apr 13 15:55:59 EST 2000
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xf0970
Intel PCIC probe: 
  TI 1450 rev 03 PCI-to-CardBus at slot 00:04, mem 0x7fffe000
    host opts [0]: [pci + serial irq] [no pci irq] [lat 66/176] [bus 2/2]
    host opts [1]: [pci + serial irq] [no pci irq] [lat 66/176] [bus 3/3]
    ISA irqs (scanned) = 3,4,7,9,15 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x10ff
cs: IO port probe 0x0100-0x04ff: excluding 0x100-0x107 0x170-0x177 0x370-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4
wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de>
wvlan_cs: index 0x01: Vcc 5.0, irq 3, io 0x0180-0x01bf
wvlan_cs: Registered netdevice wvlan0
wvlan_cs: Valid channels: 1 2 3 4 5 6 7 8 9 10 11 
wvlan_cs: MAC address on wvlan0 is 00 60 1d f6 34 b0 
----------------------------------------

----------------------------------------
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03)
00:04.0 CardBus bridge: Texas Instruments PCI1221 (rev 03)
00:04.1 CardBus bridge: Texas Instruments PCI1221 (rev 03)
00:07.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
----------------------------------------

Ok BIOS was not providing PCI interrupt information

Re: Question Compaq Laptop M700 hangs when card is inserted or ejected (Atanu Ghosh)
Date: 2000, May 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

This system's BIOS was not providing a complete PCI interrupt routing table, so the PCI drivers were not able to deduce the PCI interrupt assignment for the CardBus bridge. The bridge was still generating PCI interrupts, which locked up the system, because another device shared the same interrupt line, but that device's driver was unable to clear the CardBus bridge interrupt.

The problem was solved by explicitly telling the i82365 module the PCI interrupt assignment, with a startup option of:

  PCIC_OPTS="pci_irq_list=11,11"

(in this case, the bridge was configured for PCI irq 11)

-- Dave

Question PCIC probe failed (but worked fine yesterday)

Date: 2000, Apr 24
From: Shiv Sikand sikand

k 2.2.14, pcmcia 3.1.14, IBM TP 600x

Things were good yesterday:

Intel PCIC probe: TI 1450 rev03 PCI-to-CardBus at slot 00:02 mem 0x5013000

[snip, other good stuff]

Then, I installed OSS and things went bad next reboot:

Intel PCIC probe: Bad bridge mapping at 0x00003000! not found. ds: no socket drivers loaded

Please help, I'm going nuts !!

--Shiv

None First thing to do: disable OSS and reboot

Re: Question PCIC probe failed (but worked fine yesterday) (Shiv Sikand)
Date: 2000, Apr 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Can you uninstall OSS, or reconfigure it to not load any kernel
modules?  I don't understand why OSS would mess up your CardBus bridge
settings, but it would be worth verifying whether or not OSS is really
at fault here.

It appears that something has tried to remap your bridge at a base
address of 0x00003000, which is certainly bogus, since that address
would overlap the bridge with your system RAM.  I assume that you are
not specifying any unusual options for the PCMCIA modules?

-- Dave

None Re: disable OSS and reboot

Re: None First thing to do: disable OSS and reboot (David Hinds)
Date: 2000, Apr 24
From: Shiv Sikand sikand

I don't have OSS or ALSA running anymore and I didn't do anything with any of the pcmcia stuff. I rebuilt 1.1.14 and re-installed it just in case

The only other thing that I did change was in the IBM BIOS ( which doesn't give a lot of choices) I disable the "Easy Boot" section as advised by IBM's web page for non-windows OS.

Well, I've since restored the setting and also booted W98 and all seems to be well in there.

Any more clues ? This is driving me nuts.

Thanks, Shiv

Ok Problem resolved

Re: Question PCIC probe failed (but worked fine yesterday) (Shiv Sikand)
Date: 2000, Apr 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Starting up with CORE_OPTS="cb_mem_base=0x50103000" seems to have fixed the problem. I'm still not sure what caused it in the first place, but the BIOS seems to be mis-configuring the CardBus bridge.

-- Dave

Question Need help setting up pcmcia-cs-3.1.13 on Linux Mandrake

Date: 2000, Apr 25
From: Andrew Brackenbury abrackenbury

Hello. I have a Sony Vaio PCG-719 laptop. I have the hard drive partitioned into a windows and Linux section. Linux Mandrake will not recognize my PCMCIA cards. I need it to see my 3com EtherLink III PCMCIA 3C589D card and my Adaptec APA-1425/50/60 PCMCIA SCSI host adapter. I downloaded a driver file from this source: ftp://sourceforge.org/pcmcia/pcmcia-cs-3.1.13.tar.gz. I was using windows at the time and I put the relevent files on three floppies. I don't know how to install the software on Linux mandrake from a shell prompt but this is the way I need to do it. The fact that the files are spread across three disks frightens me. Can anyone help?

andrew

None Hard to tell, but you may not need to do this at all

Re: Question Need help setting up pcmcia-cs-3.1.13 on Linux Mandrake (Andrew Brackenbury)
Date: 2000, Apr 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The PCMCIA package (the *.tar.gz file) is only about 1 MB so it will
easily fit on a single floppy.  So I have no idea what you did to
split the files across three floppies.  If you tried to unpack the
package under Windows, you've probably messed it up sufficiently that
you should just start over.  The PCMCIA-HOWTO does have detailed
installation instructions.

However, backing up a step, you say that your linux setup "will not
recognize" your cards.  That sounds very fishy to me and sounds like
you've just not configured things properly, and there may be no need
to upgrade your drivers.  See the PCMCIA-HOWTO section on diagnosing
installation problems.  You need to check basic things like (1) is
PCMCIA turned on in /etc/sysconfig/pcmcia?  (2) are there PCMCIA
messages in your system log?  (3) do you hear beeps when you insert
cards?  etc.

-- Dave

Question Troubles with Vadem VG-469 - what am I doing wrong?

Date: 2000, Apr 26
From: Andrey Soplevenko stormbird

I'm installing the Vadem VG-469 isa pcmcia controller onto RedHat Linux 6.1 (kernel 2.2.12), but seems pcmcia package do not even see it. I have tried out two versions of them - the original version from RedHat distribution (3.0.14) and new one for this site (3.1.14). In both cases the controller and so the cards do not works. probe program detects no pcmcia platform and cardctl reports: "no pcmcia driver in /proc/devices". Also while starting pcmcia and pcmcia~ services this messages appears: "ds: no socket drivers loaded". At last here is some pcmcia related lines from log files:

>boot.log:
>^^^^^^^^^
>pcmcia: Starting PCMCIA srvices
>pcmcia: modules
>pcmcia: /lib/modules/2.2.12-20/pcmcia/i82365.o:
>pcmcia: cardmgr.
>pcmcia: init_module: Device or resource busy
>pcmcia: /lib/modules/2.2.12-20/pcmcia/ds.o:
>        init_module: Device or resource busy
>rc: Starting pcmcia succeeded
>pcmcia~: Starting PCMCIA services:
>pcmcia~: modules
>pcmcia~: /lib/modules/2.2.12-20/pcmcia/pcmcia_core.o:
>         a module named pcmcia_core already exist
>pcmcia~: /lib/modules/2.2.12-20/pcmcia/i82365.o:
>         init_module: Device or resource busy
>pcmcia~: cardmgr
>pcmcia~: /lib/modules/2.2.12-20/pcmcia/ds.o:
>         init_module: Device or resource busy
>rc: Starting pcmcia succeeded.

>messages.log
>^^^^^^^^^^^^
>kernel: options [pci][cardbus][apm]
>kernel: Intel PCIC probe: not found
>pcmcia: /lib/modules/2.2.12-20/pcmcia/i82365.o:
>kernel: ds: no socket drivers loaded!
>pcmcia: init_module: Device or resource busy
>pcmcia: /lib/modules/2.2.12-20/pcmcia/ds.o:
>        init_module: Device or resource busy
>cardmgr[330]: starting, version is 3.0.14
>cardmgr[330]: no pcmcia driver in /proc/devices
>cardmgr[330]: exiting

Will gratefully accept any assistance. Andrey.

None Several possibilities

Re: Question Troubles with Vadem VG-469 - what am I doing wrong? (Andrey Soplevenko)
Date: 2000, Apr 26
From: David Hinds <dhinds@pcmcia.sourceforge.org>

First, does this card have any jumpers for configuring the IO address
for the VG469?  The driver is looking at address 0x3e0 so if there is
a jumper for selecting between other addresses, you should select the
0x3e0 option.

If there is no such jumper, then perhaps this board is set up as an
ISA PnP device.  You can get the linux isapnptools package, and see if
it is able to detect and configure the card.  After that, the PCMCIA
modules should be able to find it.

If neither of these things seems to work, then I'm not sure what's
going on.  Maybe you have some other system device configured so that
it conflicts with the 0x3e0-0x3e1 IO ports needed by the VG-469.  If
you can verify this, you could try moving that other device to some
other IO address, if that's feasible.

-- Dave

Question Surecom PCMCIA Network Adapter

Date: 2000, Apr 27
From: Roman Seidl <rse@pvl.at>

I have a Surecom Network Apdapter (EP-427X). There are some Linux Files on the driver disk but the readme file says the following:

SURECOM EP-427X 10/100M PCMCIA Adapter LINUX DRIVER INSTALL
 Note: this driver for linux 2.0.30

 1. copy driver to /ep427x
    # mcopy a:/* /ep427x

 2. download pcmcia-cs-3.0.x.tar.gz from hyper.stanford.edu
    in the /pub/pcmcia directory
    readme PCMCIA-HOWTO file & install it 

 3. add the following lines into /etc/pcmcia/config
    card "SURECOM EP-427X 100/10M PCMCIA Adapter"
    version "PCMCIA", "100BASE"
    bind "pcnet_cs"

 4.# cd /ep427x
   # chmod +x gen1 gen2

 5.# gen1
   # gen2

 6.# reboot

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

hyper.stanford.edu no longer publishes the pcmcia package and the kernel version i´d like to use is 2.2.14

Do I just have to add the definitions to a newer kernel version or do i have to use some of the "patches" that might be included with the driver disk? are pcnet_cs.c and 8390.c just standard driver source?

there is some more files included with the driver disk:

Config: ---------

#
# config.sample 1.87 1999/02/16 01:33:35 (David Hinds)
#

# config.opts is now included at the very end

#
# Device driver definitions
#
device "3c589_cs"
  class "network" module "3c589_cs"
[...]
---------

gen1: ------ gcc -DMODULE -D__KERNEL__ -I/usr/src/linux -I/usr/src/pcmcia-cs-3.0.9/include -c -O6 pcnet_cs.c cp pcnet_cs.o /lib/modules/2.0.30/pcmcia/pcnet_cs.o ------

gen2: ------ gcc -DMODULE -D__KERNEL__ -I/usr/src/linux -I/usr/src/linux/drivers/net -c -O6 8390.c cp 8390.o /lib/modules/2.0.30/net/8390.o ------

8390.c:
-------
/* 8390.c: A general NS8390 ethernet driver core for linux. */
/*
	Written 1992-94 by Donald Becker.

[...] -------

pcnet_cs.c ------- /*======================================================================

    A PCMCIA ethernet driver for NS8390-based cards

   Copyright (C) 1998 David A. Hinds --   
   dhinds@hyper.stanford.edu
-------

None With a vendor driver, you should first check with that vendor

Re: Question Surecom PCMCIA Network Adapter (Roman Seidl)
Date: 2000, Apr 27
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You should certainly see if the card works with the existing PCMCIA
drivers; it is possible that the vendor provided driver is not needed
with a current PCMCIA distribution.  Alternatively, a newer version of
their driver might be available from their web site.  I cannot
reasonably do much to support drivers provided by third parties.

-- Dave

None Is the hyper.stanford package included with the current pcmcia drivers?

Re: None With a vendor driver, you should first check with that vendor (David Hinds)
Date: 2000, Apr 28
From: Roman Seidl <rse@pvl.at>

None It *is* the current pcmcia driver package

Re: None Is the hyper.stanford package included with the current pcmcia drivers? (Roman Seidl)
Date: 2000, Apr 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The site simply moved; it is the same software.

-- Dave

Question Can any one assist in multi wvlan card compiliations or setups under linux2.2x

Date: 2000, May 04
From: John Savage admin

Need help on configging multiple wavelan cards in linux 2.2X Please email me admin@tri-net.org or call collect 336 629 4247 John Savage

Question PCMCIA not working with a TI 1450 PCI-Cardbus

Date: 2000, May 09
From: Paul Hayton <pmh@robots.ox.ac.uk>

I've trying to get Linux 6.2 up and running on a Fieldworks 8000 Rugged Laptop. It uses a TI 1450 PCI-Cardbus Controller which probe happily identifies. The symptoms at face value match those of a memory probe failure and having read the previous list of problems and suggestions, I've tried restricting the probe range (many many combinations) to no avail.

The other symptom is that the ATA IDE disk I'm trying to get working (which works happily on other machines) doesn't get hot which implies it may not be getting any power, but I'm using Card Services 3.1.14 which has the TI 1220 power on bit set..

Many thanks in advance for any ideas ..

Paul

The messages log reports :

May  9 11:08:44 lafeu kernel: Linux PCMCIA Card Services 3.1.14 
May  9 11:08:44 lafeu kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 
May  9 11:08:44 lafeu kernel:   options:  [pci] [cardbus] [apm] 
May  9 11:08:44 lafeu kernel: PCI routing table version 1.0 at 0xfdcf0 
May  9 11:08:44 lafeu kernel: Intel PCIC probe:  
May  9 11:08:44 lafeu kernel:   TI 1450 rev 03 PCI-to-CardBus at slot 02:08, mem 0x76000000 
May  9 11:08:44 lafeu kernel:     host opts [0]: [isa irq] [no pci irq] [lat 64/176] [bus 3/3] 
May  9 11:08:44 lafeu kernel:     host opts [1]: [isa irq] [no pci irq] [lat 64/176] [bus 4/4] 
May  9 11:08:45 lafeu kernel:     ISA irqs (scanned) = 7,9 polling interval = 1000 ms 
May  9 11:08:45 lafeu cardmgr[5121]: starting, version is 3.1.14
May  9 11:08:45 lafeu cardmgr[5121]: watching 2 sockets
May  9 11:08:45 lafeu kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1028-0x102f 0x1060-0x1067 0x1158-0x115f 0x1378-0x137f 0x13f0-0x13f7 
May  9 11:08:45 lafeu kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x158-0x15f 0x378-0x37f 0x4d0-0x4d7 
May  9 11:08:45 lafeu kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
May  9 11:08:45 lafeu cardmgr[5121]: initializing socket 0
May  9 11:08:45 lafeu kernel: cs: memory probe 0xc0000000-0xc0ffffff: excluding 0xc0000000-0xc0ffffff 
May  9 11:08:45 lafeu kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff 
May  9 11:08:45 lafeu kernel: cs: memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff 
May  9 11:08:45 lafeu kernel: cs: warning: no high memory space available! 
May  9 11:08:45 lafeu kernel: cs: memory probe 0x0d0000-0x0dffff: excluding 0xd0000-0xdffff 
May  9 11:08:45 lafeu kernel: cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xcffff 
May  9 11:08:45 lafeu cardmgr[5121]: socket 0: Anonymous Memory
May  9 11:08:45 lafeu cardmgr[5121]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/memory_cs.o'
May  9 11:08:45 lafeu kernel: memory_cs: mem0: anonymous: unknown size 
May  9 11:08:45 lafeu cardmgr[5121]: executing: './memory start mem0'

Note Additional Information

Re: Question PCMCIA not working with a TI 1450 PCI-Cardbus (Paul Hayton)
Date: 2000, May 09
From: Paul Hayton <pmh@robots.ox.ac.uk>

Just in case it clarifies anything in the above problem,

dump_cis reports no Card Information Structures found:

#dump_cis
Socket 0:
  no CIS present

Socket 1:
  no CIS present

Also in my previous post, I said I thought it might be the power, but I've tried changing the p2cclk parameter and get the message `socket 0 timed out during reset' so that doesn't appear to have anything to do with it.

Any ideas ?

Paul

None Probably not a memory window issue

Re: Question PCMCIA not working with a TI 1450 PCI-Cardbus (Paul Hayton)
Date: 2000, May 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Do you have any other cards you can try?

I don't think it is a memory probe issue.  I agree it sounds like a
power issue, and with the card not powered up properly, the drivers
cannot read any CIS information, regardless of memory window settings.

What does "cardctl status" say?  Also I'd try booting with the card
out, and then insert it later.

-- Dave

More cardctl can see something....

Re: None Probably not a memory window issue (David Hinds)
Date: 2000, May 11
From: Paul Hayton <pmh@robots.ox.ac.uk>

Thanks for replying. cardctl reports the following :

#cardctl status
Socket 0:
  5V 16-bit PC Card
  function 0: [ready]
Socket 1:
  no card

I get exactly the same results with a D-Link DE-660 Ethernet PCMCIA card, and the same results if I start PCMCIA without the card in, then insert the card afterwards.

Just for comparison, the message log from another machine (same manufacturer, before they went and changed all their chipsets - this was a Cirrus PD6710 ISA-to-PCMCIA controller) reports the card as :

May 10 09:21:55 scarus cardmgr[282]: initializing socket 0
May 10 09:21:55 scarus cardmgr[282]: socket 0: ATA/IDE Fixed Disk
May 10 09:21:55 scarus cardmgr[282]: initializing socket 0
May 10 09:21:55 scarus cardmgr[282]: socket 0: ATA/IDE Fixed Disk
May 10 09:21:55 scarus cardmgr[282]: executing: 'insmod /lib/modules/2.2.5/pcmcia/ide_cs.o'
May 10 09:21:58 scarus kernel: hde: Calluna Technology CT1040RM, ATA DISK drive
May 10 09:21:58 scarus kernel: ide2 at 0x100-0x107,0x10e on irq 3
May 10 09:21:58 scarus kernel: hde: Calluna Technology CT1040RM, 992MB
w/128kB Cache, CHS=2016/16/63
May 10 09:21:58 scarus kernel:  hde: [PTBL] [1008/32/63] hde1
May 10 09:21:58 scarus kernel: ide_cs: hde: Vcc = 5.0, Vpp = 0.0
May 10 09:21:58 scarus cardmgr[282]: executing: './ide start hde'
May 10 09:21:58 scarus cardmgr[282]: + sh: ./ide: No such file or directory
May 10 09:21:58 scarus cardmgr[282]: start cmd exited with status 126 and cardctl (from card services 3.0.9 reports)

#cardctl status
Socket 0:
  5V 16-bit card present
  Function 0: ready, battery dead, battery low

Any ideas how to proceed in debugging ? I'm quite happy fiddling with the source if neccessary.

Regards

Paul

Ok Success

Re: Question PCMCIA not working with a TI 1450 PCI-Cardbus (Paul Hayton)
Date: 2000, May 31
From: Paul Hayton <pmh@robots.ox.ac.uk>

After much help from Dave, the solution was the following.

The /proc/pci showed the Cardbus bridge memory at 0x73000000. Dave suggested a memory window of 0x73010000-0x7301ffff which worked a treat and then card-services could recognise the card when inserted.

The next problem was that although card services recognised the device it had problems talking to it : The symptom was (on insertion of a D-link DE-660 ethernet card)

May 27 10:28:33 lafeu kernel: pcnet_cs: unable to read hardware net address for io base 0x300 
May 27 10:28:33 lafeu cardmgr[664]: get dev info on socket 0 failed: No such device

The same problem produced a misleading (to me at least) error from ide_register about IRQs on insertion of a ATA-IDE 1Gb hard disk.

The solution (thanks again Dave) was to remove the default IO-port range which was the problem and specify a new IO-port range

0xa000-0xa7ff

based on the IO-range of an ethernet card which was the only other device on the same bus (which had an IO address of 0xa800 from /proc/pci)

..... and finally it all works. !

Paul

Sad Problem with Lucent PCI-PCMCIA adapter

Date: 2000, May 09
From: Tommy Svensson tommy23

I have much problem to get my Lucnet PCI-PCMCIA Adapter to work under Linux.

I have read articel on this maillinglistor which address this issue, but it didn't help. I have upgrade to the latest version of both Linux kernel 2.2.15 and PCMCIA utils (have test both with the beta in 3.1.15 and the realse 3.1.14). I have test with both Lucent Wavelan driver (version 6.00 and 6.01BETA) and also the Andy GPL driver, but nothing work.

It find the PCI-PCMCIA adapter it find the wavelan card and load the right driver but the driver complain about missing resources etc.

How do I fix this problem or should I use other PCMCIA adapters, which is no problem for ous to buy new. But we running homemaid software for remote-monitoring of weather-equiment.

Please help me!

//Tommy

Question Infinite interrupt loop with DataChute (i82365)

Date: 2000, May 10
From: Matthew Kerr MattK

I've been working on cloning about 50 machines (surplus AST P-133's) with the Antec DataChute PCMCIA ("Via" i82365 compat. chips) controllers. All of the machines are identical (from BIOS settings and versions to hard drive images). I am working with CompactFlash PCMCIA devices.

On about 10% of the machines, I repeatedly get a nasty message on console when I insert a card: "i82365: infinite loop in interrupt controller". It's appeared (rarely) on some of the other machines, but consistently on that 10%.

I'm running kernel 2.2.14 and pcmcia-cs 3.1.14. I've played with the "cs_irq" and the "irq_list" options (I have more than 3 available IRQ's on the machine), to no avail.

As these machines will be unattended, stability is extremely important. :)

If anyone has experienced this before, or has any ideas on what to do, I would really appreciate it!

Thanks!
-Matt

News One solution, more to come

Re: Question Infinite interrupt loop with DataChute (i82365) (Matthew Kerr)
Date: 2000, May 25
From: Matthew Kerr MattK

We've purchased just about every desktop PCMCIA dock available and are currently testing the different models to see which ones work and which ones don't. Here's some preliminary information:

-The LinkSys ProConnect (model "PCMRDWR") is the exact same unit as the Antec DataChute, down to the PCB traces and packaging.

-The SCM "SBP-D2P PCI" (TI PCI1221) generates all kinds of lost interrupts and does not work on our hardware.

-The SCM "SBI-D2P" (ISA) appears to work perfectly and is being burned in. (Vadem VG-469)

To make sure this isn't taken out of context, we appear to have some flaky AST hardware, and have had unusual difficulties with every PCMCIA reader we've used. On a unit with a bug-free interrupt controller, I'm sure these readers would work fine.

We are still waiting for final results, and some of our readers haven't arrived yet to be tested. I'll post my final results here.

Question What's the most trouble-free desktop PCMCIA interface?

Date: 2000, May 12
From: Matthew Kerr MattK

I've been working with 35+ identical systems that have so far refused to work consistently with the Antec DataChute desktop PCMCIA interface.

Are there any desktop products available that have worked flawlessly under Linux? I do suspect that I am working with flaky hardware, although the ISA modem and PCI net card all work just fine in these systems.

Any recommendations or tips for working with the DataChutes would be very much appreciated.

Thanks -Matt

Sad DataChute 'dies' and needs isapnp rerun

Date: 2000, May 15
From: Matthew Kerr MattK

I've discovered another problem with the Antec DataChutes that seems to behave in the same way on every CPU/motherboard I've tested it on.

After a random amount of time (usually several hours), the DataChute 'dies' and disappears from pcmcia-cs's view. The only solution I've been able to find is to stop pcmcia, re-run isapnp (with strangely will reconfigure the device, where it otherwise fails if the DataChute is still working correctly), and then start pcmcia back up.

This is a very odd problem, but it seems limited to the DataChute and not any of the other hardware I'm working with. Is there anything funky I need to add to isapnp.conf to 'keep' it configured correctly?

thanks, -Matt

Question how to find a PC104 PCMCIA adapter?

Date: 2000, May 15
From: c. chris erway cce

Hello. I'm from the Cornell BRAIN project, developing an "autonomous underwater vehicle" (read: robot submarine) for a competition in July. We are using Linux on a small single-board computer to accomplish this task.

My team bought a PCM-3115B (http://www.aaeon.com/html/pcm3115b.htm), which is a PC104 module with two PCMCIA slots on it. They did not consult with me ("the Linux guy") first, so we don't have any Linux drivers for it right now.

I am trying to figure out if I can get it to work with the Linux PCMCIA package. My dream is this: that I can magically start using the PCMCIA slots by simply pointing the PCMCIA kernel modules at some specific IO address and IRQ (and memory area?). However, I don't know if that would work.

Has anyone heard of any success using ANY kind of PC104 adapter for PCMCIA support? Even experiences using one of those PCI-to-PCMCIA adapters would be relevant here. Any input anyone has would be very useful. Thanks.

None This dock should work

Re: Question how to find a PC104 PCMCIA adapter? (c. chris erway)
Date: 2000, May 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I checked their web site and it appears that the PCM-3115B uses a
Vadem VG-468 chipset, which is supported by the linux drivers.

I've had people tell me they've used PC104 cards with VG-468 chipsets,
as well as Cirrus PD672x chipsets, successfully.  I have not kept
track of specific vendors and product codes.

What happens when you load the Linux PCMCIA drivers?  Does the i82365
module fail out with a "not found" message?  There is only one setting
that is relevant for this type of controller: the i365_base parameter
has to point to the card's base IO address, which is normally 0x3e0.
The documentation for the PCM-3115B should indicate if there are any
jumpers for configuring the IO address.

-- Dave

Question PCMCIA modem unresponsive

Date: 2000, May 17
From: Johan Mellberg mellberg

Question Unresolved symbols installing pcmcia.12-May-00 under RedHat 6.2

Date: 2000, May 18
From: Michael Barton mgbarton

The pcmcia package that installed with RedHat 6.2 doesn't
correctly handle my 3Com 3CCFEM656BT Ethernet card (I'll post
another thread about that...), so I decided to try the latest
version from pcmcia.sourceforge.org: pcmcia-12-May-00.tar.gz.

The config went fine:

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

    -------- Linux PCMCIA Configuration Script --------

The default responses for each question are correct for most users.
Consult the PCMCIA-HOWTO for additional info about each option.

Linux source directory [/usr/src/linux]: 

The kernel source tree is version 2.2.14-5.0.
The current kernel build date is Tue Mar 7 21:07:39 2000.

Alternate target install directory []: 
Build 'trusting' versions of card utilities (y/n) [n]: 
Include 32-bit (CardBus) card support (y/n) [y]: 
Include PnP BIOS resource checking (y/n) [n]: 
Module install directory [/lib/modules/2.2.14-5.0]: 

Kernel configuration options:
    Symmetric multiprocessing support is disabled.
    PCI BIOS support is enabled.
    Power management (APM) support is enabled.
    SCSI support is enabled.
    Networking support is enabled.
     Radio network interface support is enabled.
     Token Ring device support is enabled.
     Fast switching is disabled.
    Module version checking is enabled.
    /proc filesystem support is enabled.
    Maximum physical memory: 1GB

It looks like you have a System V init file setup.

X Windows include files found.
Forms library not installed.
    If you wish to build the 'cardinfo' control panel, you need the Forms
    library and the X Windows include files.  See the HOWTO for details.

Configuration successful.


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

The make went file too:

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

make[1]: Entering directory `/home/mgb/additions/pcmcia/pcmcia-cs-3.1.15/modules'
cc   -MD -O2 -Wall -Wstrict-prototypes -pipe -I../include -I/usr/src/linux/include  -D__KERNEL__ -DMODULE -c cs.c
cc   -MD -O2 -Wall -Wstrict-prototypes -pipe -I../include -I/usr/src/linux/include  -D__KERNEL__ -DMODULE -c cistpl.c
.....

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

But when I tried to install it, I got the following error:

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

-> Running depmod...
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/pcmcia/3c575_cb.o


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

SO I tried to install the module manually:

/sbin/insmod /lib/modules/2.2.14-5.0/pcmcia/3c575_cb.o

and was told:

/lib/modules/2.2.14-5.0/pcmcia/3c575_cb.o: unresolved symbol outsl_ns
/lib/modules/2.2.14-5.0/pcmcia/3c575_cb.o: unresolved symbol unregister_driver
/lib/modules/2.2.14-5.0/pcmcia/3c575_cb.o: unresolved symbol insl_ns
/lib/modules/2.2.14-5.0/pcmcia/3c575_cb.o: unresolved symbol register_driver


Did I miss something?
Michael

None Well, it is a beta, after all

Re: Question Unresolved symbols installing pcmcia.12-May-00 under RedHat 6.2 (Michael Barton)
Date: 2000, May 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You should expect the possibility of breakages; the 3.1.15 release
would probably be a better thing to try.

That particular bug is fixed in a newer beta.

-- Dave

Question Using dhcpcd with pcmcia-cs

Date: 2000, May 20
From: Uwe Hahn uwe

Hi,

with RedHat Linux 6.1, what is the cleanest way of implementing dhcpcd into the boot scripts? I mean: Where do I start the daemon and safely start pcmcia after that? Is there an option for this in the pcmcia.conf or do I have to manually create a rc file? Thank you for any help given.

Greetings,

	<uwe>

None Not in the boot scripts

Re: Question Using dhcpcd with pcmcia-cs (Uwe Hahn)
Date: 2000, May 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You don't want to start dhcpcd from the boot scripts.

You want it to be started when your network card is configured, right?
If you are using the Red Hat network setup scripts, those scripts are
set up to use "pump" for DHCP configuration.  If you want to use
dhcpcd instead, then edit /sbin/ifup and replace the call to "pump"
with an appropriate dhcpcd command.

-- Dave

Question only one socket recognized on a machine with 2 Type II's

Date: 2000, May 20
From: Jesse calig007

Hi - I have been trying to get PCMCIA support up and running
with Caldera OpenLinux, build 2.0.35 -- right now only socket
0 is even being recognized. An excerpt from the boot messages 
is :


.
.
.
Intel PCIC Probe
  VIA VT83C469 at port 0x3e0 ofs 0x00, 1 socket
  host opts [0]: ring
  ISA irqs (scanned) = 3,4,5,7,9,11,12 status change on irq 11
.
.
.

I have CD-ROM successfully mounted on socket 0. Any ideas on 
what is keeping socket 1 from getting seen? Thanks in advance 
- Jesse

None This setup sounds strange to me

Re: Question only one socket recognized on a machine with 2 Type II's (Jesse)
Date: 2000, May 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

So... what kind of machine is this, exactly?

You can try specifying PCIC_OPTS="extra_sockets=1" in your PCMCIA
startup options (/etc/sysconfig/pcmcia for Red Hat).  I'm not sure how
else the probe could misdetect the number of sockets.

-- Dave

Sad things don't sound good if Hinds doesn't know...

Re: None This setup sounds strange to me (David Hinds)
Date: 2000, May 21
From: Jesse calig007

I put the extra_sockets=1 in /etc/sysconfig/pcmcia, but 
rebooting the system got me the same messages. I used to use 
this laptop with Win 95 and both slots. The computer is a AST
Ascentia 910N (486DX4/75Mhz 8Mb + 4Mb addition module). Linux
is build 2.0.35, Caldera Openlinux 1.3. Thanks for your help-
 Jesse

Question Redhat 6.2 pcmcia boot disk

Date: 2000, May 21
From: Joao Marques jpdmarques

Hi!

My problem it’s quite simple. I want to install RH6.2 from ftp with a PCMCIA Ethernet Card. But when I tried to install using the pcmcia boot disk the card wasn’t detected.

In the card box is written WISECOM 10/100MBPS PCMCIA Ethernet Card, but there is no indication about the model. I don’t really know if it’s a WC-PC400 or simply an OEM card with the same name.

But because the card came with Linux drivers (well, more a patch to pcmcia-cs-3.0.9) it should by now be supported.

If the card is in fact a WS-PC400, the smc91c92_cs driver is included in the pcmcia boot disk? Or I need to create a driver disk? How can I do that?

The PCMCIA controller is based on the chipset TI-1211 (Compaq Presario 1200)

Joao Marques

Question Untitled

Re: Question Redhat 6.2 pcmcia boot disk (Joao Marques)
Date: 2000, May 22
From: Joao Marques jpdmarques

Hi again!

I installed RH6.1 by CD (to make a copy of RH6.2 in my hard disk with wget) but now the problem is different.

(pcmcia-cs-3.1.15 drivers)

#dmesg

Linux PCMCIA Card Services 3.1.15
  kernel build: 2.2.12-20 #1 Mon Sep 27 10:25:54 EDT 1999
  options:  [pci] [apm]
PCI routing table version 1.0 at 0xfdf70
Intel PCIC probe:
  TI 1211 rev 00 PCI-to-CardBus at slot 00:0a, mem 0x68000000
    host opts [0]: [ring] [pci + serial irq] [pci irq 9] [lat 32/176] [bus
32/34]
    ISA irqs (scanned) = 3 PCI status changes
cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x10ff 0x1400-0x14ff
cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x378-0x37f
0x388-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.

By default it detects a ne2000 compatible card:

eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr 00:A0:0C:40:99:4C

But,

#/etc/rc.d/init.d/network start Bringing up interface lo [ OK ] Bringing up interface eth0

eth0: Reentering the interrupt handler! isr=0x0 imr=0x0.
eth0: Reentering the interrupt handler! isr=0x0 imr=0x0.
eth0: Reentering the interrupt handler! isr=0x0 imr=0x0.
...

It almost works, but that message is always appearing. (it does the dhcp; ping also works).

So the only explanation is that this card is not ne2000 100% compatible, which a search to the file /etc/pcmcia/config confirmed:

(...)
card "WiseCom WC-PC400 Fast Ethernet"
  manfid 0x8a01, 0xc1ab
  bind "smc91c92_cs"

This is my card (so i thinked; now i don't know :) ):

#cardctl ident
Socket 0:
  product info: "PCMCIA", "10/100 Ethernet Card", "", ""
  manfid: 0x8a01, 0xc1ab
  function: 6 (network)

After replacing this entry by the one that conflits with this one, the card was successfull detected

#dmesg

(...) smc91c92_cs: using 8-bit IO window. eth0: smc91c??? rev 13: io 0x100, irq 3, hw_addr FF:FF:FF:FF:FF:FF

but badly configured. So this card probably doesn't use a smc91c92/94/95/96/100/100-FD/110 chipset. Is there any way to see if this card in fact uses a different chipset or this is result of a bug / conflit / error ?

Joao

Sad pcmcia-cs-3.1.13 and 15 can't cross-compile for powerpc

Date: 2000, May 22
From: Tom Eden tome

None pcmcia-3.1.14 - error during 'make all' ..

Date: 2000, Jun 01
From: Rene Mikkelsen k2OS

In pcmcia-cs-3.1.14

After 'make config' I do a 'make all' .. but when Make goes into '/cardmgr'
I instantly get this error ..

<snip>
cc  -MD -O -Wall -Wstrict-prototypes -pipe -I../include
-I/usr/src/linux/include -I../modules -c cardmgr.c
cardmgr.c: In function `lookup_dev':
cardmgr.c:156: `ENODEV' undeclared (first use in this function)
cardmgr.c:156: (Each undeclared identifier is reported only once
cardmgr.c:156: for each function it appears in.)
cardmgr.c:157: warning: control reaches end of non-void function
cardmgr.c: In function `do_insert':
cardmgr.c:915: `EBUSY' undeclared (first use in this function)
cardmgr.c:933: `EAGAIN' undeclared (first use in this function)
cardmgr.c: In function `init_sockets':
cardmgr.c:1252: `ENODEV' undeclared (first use in this function)
cardmgr.c:1265: `ENOENT' undeclared (first use in this function)
cardmgr.c: In function `main':
cardmgr.c:1415: `EINTR' undeclared (first use in this function)
cardmgr.c:1427: `EAGAIN' undeclared (first use in this function)
make: *** [cardmgr.o] Error 1
</snip>

I compared the libraries with my other machine, at it seems 
that I need to upgrade glibc to version 2.1.3-15 .. a certain 
errno.h-file that contains declaraions of ENODEV (and other 
return-msgs are declared in this one) .. but why doesn't ake 
complain about this file missing?.. 

I'm currently using 2.1.1-6 on the labtop .. the problem is.. 
that the glibcrpm is about 9megs .. and the only link I have 
to the labtop is the net-adapter... 

My system :  Olivetti P100E - redhat 6.0 ..
                     3c589D-pcmcia-adapter ..

in advance..

Thanx..

/René

None This is not really a PCMCIA problem

Re: None pcmcia-3.1.14 - error during 'make all' .. (Rene Mikkelsen)
Date: 2000, Jun 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Without a valid errno.h, you can't really compile any user level code.
Red Hat 6.0 certainly comes with a set of libraries and header files
that allow things to be compiled successfully.  So something is messed
up on your system, and it isn't obvious to me what it would be.  Maybe
you did a kernel upgrade without checking the glibc requirements?

-- Dave

Sad adding #include <asm/errno.h> seems to help..

Re: None This is not really a PCMCIA problem (David Hinds)
Date: 2000, Jun 01
From: Rene Mikkelsen k2OS

hmm I added #include <asm/errno.h> to all complaining files and everything compiled ok, but. . after 'make install' and restarting pcmcia the card still didn't work.. for some reason the card is detected as memorycard? This appears *very* strange as I have been using thhe same card in this machine running Linux for almost two years now without any trouble..I can even install via net without any trouble..

this is what /var/log/messages says when starting pcmcia and inserting the card:

<snip>

Jun  3 14:28:50 slet cardmgr[4818]: starting, version is 3.1.14
Jun  3 14:28:50 slet cardmgr[4818]: no pcmcia driver in /proc/devices
Jun  3 14:28:50 slet cardmgr[4818]: exiting
Jun  3 14:29:44 slet kernel: Linux PCMCIA Card Services 3.1.14 
Jun  3 14:29:44 slet kernel:   kernel build: 2.2.14 #1 Fri Jun 2 18:24:36 CEST 2000 
Jun  3 14:29:44 slet kernel:   options:  [pci] [apm] [pnp] 
Jun  3 14:29:44 slet kernel: Intel PCIC probe:  
Jun  3 14:29:44 slet kernel:   Cirrus PD672x rev 00 ISA-to-PCMCIA at port 0x3e0 ofs 0x00 
Jun  3 14:29:44 slet kernel:     host opts [0]: [ring] [65/6/0] [1/15/0] 
Jun  3 14:29:44 slet kernel:     host opts [1]: [ring] [65/6/0] [1/15/0] 
Jun  3 14:29:44 slet kernel:     ISA irqs (default) = 3,4,5,7,9,10,11 polling interval = 1000 ms 
Jun  3 14:29:44 slet cardmgr[4833]: starting, version is 3.1.14
Jun  3 14:29:44 slet cardmgr[4833]: watching 2 sockets
Jun  3 14:29:44 slet kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x11f0-0x11f7 0x1240-0x124f 0x1388-0x138f 0x13f0-0x13f7 0x15f0-0x15f7 0x1640-0x164f 0x1788-0x178f 0x17f0-0x17f7 
Jun  3 14:29:44 slet kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x240-0x24f 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x3b0-0x3e7 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7 
Jun  3 14:29:44 slet kernel: cs: IO port probe 0x0a00-0x0aff: excluding 0xa40-0xa4f 
Jun  3 14:30:37 slet cardmgr[4833]: initializing socket 1
Jun  3 14:30:37 slet kernel: cs: memory probe 0x0d0000-0x0dffff: excluding 0xd0000-0xdffff 
Jun  3 14:30:37 slet kernel: cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xcffff 
Jun  3 14:30:37 slet cardmgr[4833]: socket 1: Anonymous Memory
Jun  3 14:30:38 slet cardmgr[4833]: executing: 'insmod /lib/modules/2.2.14/pcmcia/memory_cs.o'
Jun  3 14:30:38 slet kernel: memory_cs: mem0: anonymous: unknown size 
Jun  3 14:30:38 slet cardmgr[4833]: executing: './memory start mem0'
</snip>

this is what used to happen..

<snip>

May 12 12:30:44 slet cardmgr[647]: initializing socket 1
May 12 12:30:44 slet cardmgr[647]: socket 1: 3Com 3c589D Ethernet
May 12 12:30:44 slet cardmgr[647]: executing: 'insmod /lib/modules/2.2.14/pcmcia/3c589_cs.o'
May 12 12:30:44 slet kernel: eth0: 3Com 3c589, io 0x300, irq 3, hw_addr 00:60:97:8F:1F:9F 
May 12 12:30:44 slet kernel:   8K FIFO split 5:3 Rx:Tx, auto xcvr 
May 12 12:30:44 slet cardmgr[647]: executing: './network start eth0'
May 12 12:30:47 slet kernel: eth0: flipped to 10baseT 
May 12 12:30:56 slet kernel: eth0: flipped to 10baseT 
</snip>

veeeeery strange... I hope not that my pcmcia-card has been toasted :((

/René

Question Adaptec 1480 SCSI not quite working, other PCMCIA does

Date: 2000, Jun 06
From: S. Allen allen18

Red Hat 6.2 running on Vivante SE laptop (PII 333). PCMCIA services work, as 3C ethernet card works fine, can plug and unplug, etc.
 
1. Trying to get Adaptec 1480 SCSI to work. During boot, get message about PCMCIA at 35/0/0 AIC-7xxx memory allocation

SCSI:0

After booting, when I run card diagnostics,
2. cardctl ident -- correctly identifies both cards, the netword and the SCSI
3. cardctl status -- says both cards working, IRQ 3 and 9

4. lspci -

lists 20, the 3Com 10/100 Ethernet card.
lists 23, the Adaptec 1480 SCSI card -I tried each card individually in the slots, and switched slots.

Called Red Hat, who basically walked me through the SCSI section of your HOW-TO, but they were also a little vague about exact addresses, etc.

I added two lines to PCMCIA file--

#Extra Port range for Adaptec 1480
include port 0x500-ox6af

--The HOWTWO says that a large range is required
for this card
(This is supposed to start on a 256 boundary and be 256).

5. Same result. Error message on boot, SCSI:0

I have an HP T20 tape drive, Yamaha CD ROM writer, and Seagate Hard drive hooked to SCSI card with a External terminator on the Hard Drive. These work fine under Windows 2000. (Should I make the chain simpler, or is it the
SCSI card?)

I know you are busy, so would appreciate help from someone. I need the room on the external harddrive as the laptop HD is only 4 GB and is nearly full.

Thanks a lot, also pardon any lack of knowledge as I am only about 3 days into LINUX.

None Kernel compatibility issue: fixed in current drivers

Re: Question Adaptec 1480 SCSI not quite working, other PCMCIA does (S. Allen)
Date: 2000, Jun 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The APA-1480 card does not work with the kernel & driver combination
in Red Hat 6.2.  The current PCMCIA driver package solves the problem.

-- Dave

Question Obvious that I am a newbie

Re: None Kernel compatibility issue: fixed in current drivers (David Hinds)
Date: 2000, Jun 07
From: S. Allen allen18

Sorry to bother you!
1. I should have noticed that the 1480 is in your list of updates, and that there is a separate SCSI forum with postings about it. Thanks for the very prompt response.

2. However, I have spent several hours trying (and
a call) to execute
the simple command

make config in the new pcmcia directory! (I used version 3.1.15 because of your posting on May 15 to Barton).


--the question is about getting the source. I used the red hat upgrade manager to install the kernal tree, and it looked like it was in /usr/src/redhat/SOURCES (but I didn't check carefully for files, as there are a lot of them--did
I miss the directory?). (Note: turned off kernal* exceptions
in the upgrade manager, it looked like the package
was installed properly).

2a. Then ran config in the pcmcia directory and it said the tree was incomplete (I typed /usr/src/redhat/SOURCES) in the first question. The config quit at this point.

3. Then tried the manual method--
followed your download instructions (the HOWTO is
invaluable) and had a /usr/src/linux directory. My kernel is
2.2.14-5.0 so I downloaded the 2.2.14 tar. Put the /linux
directory in /usr/src/ -- and used the default for the answer
to the first question. I got a warning about version conflict
between subtree 14.0 and 14-5.0, so stopped.

3a. Noticed that the printout in the posting above by Barton
on May 18 did not have this warning message and he was using
Redhat 6.2. i.e. it verfied the 2.2.14-5.0 subtree.
--So, how should I proceed?

Sorry to be so uninformed!

None Wrong kernel source package

Re: Question Obvious that I am a newbie (S. Allen)
Date: 2000, Jun 07
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Red Hat has a kernel SRPM file (kernel-2.2.14-5.0.src.rpm) that will
install stuff in a subdirectory of /usr/src/redhat/SOURCES, but this
is not what you want.  The SRPM files are used if you want to create a
kernel RPM for distribution, which is not what you want to do.  The
kernel source is all in there, but it is in an odd place and you would
need to do additional steps to get it extracted in a useful form.

There are also kernel sources in a regular RPM that installs them in
/usr/src/linux.  This RPM is kernel-source-2.2.14-5.0.i386.rpm and is
the one you want.

-- Dave

Ok SCSI working, now on to the next! Thanks

Re: None Wrong kernel source package (David Hinds)
Date: 2000, Jun 08
From: S. Allen allen18

MANY thanks for your patient help.

Summary: SCSI card recognized (cheers heard as far
as the neighbors), 2 devices found, cannot
seem to mount.

There is a hard drive (formatted for windows2000, sorry),
HPt20 drive, and a Yamaha 4x4x16 tape drive on the chain.
It looks like the first two were detected, but could not
figure out how to mount. Mounting this particular hard
drive is not a big issue as today
I am adding a second (new, empty) hard drive that will be dedicated to LINUX. When I can mount this, I would like
to move the root (not boot)
over to this hard drive--I have started
to study your (coffee stained) HOWTO on this subject.
 
At the very least,
I will have a user directory on this external drive.

I also tried
cd /dev
./MAKEDEV st0 (should I have used sd--something?).

Anyway, if there were a mouse with lots of LINUX
experience in the corner of my room, I'm sure he would
be selling tickets for a comedy show --
to witness my "experiences" (i.e. the response
to "make all" was cc: not recognized! - to conserve disk
space, I had not installed the C-compiler).

fstab and the dmesg are reproduced below.

[allens@allen allens]$ more /etc/fstab
/dev/hda6 / ext2 defaults 1 1
/dev/hda3 /boot ext2 defaults 1 2
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
none /proc proc defaults 0 0
none /dev/pts devpts gid=5,mode=620 0 0
/dev/hda5 swap swap defaults 0 0
[allens@allen allens]$

apa1480_attach(device 23:00.0)
aic7xxx: <Adaptec PCMCIA SCSI controller> at PCI 35/0/0
aic7xxx: MMAPed I/O failed, reverting to Programmed I/O.
(scsi0) <Adaptec PCMCIA SCSI controller> found at PCI 35/0/0
(scsi0) Narrow Channel, SCSI ID=7, 3/255 SCBs
(scsi0) Downloading sequencer code... 423 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.28/3.2.4
       <Adaptec PCMCIA SCSI controller>
scsi : 1 host.
  Vendor: HP Model: T20 Rev: 3.00
  Type: Sequential-Access ANSI SCSI revision: 02
(scsi0:0:5:0) Synchronous at 20.0 Mbyte/sec, offset 15.
  Vendor: IBM Model: DNES-309170W Rev: SAH0
  Type: Direct-Access ANSI SCSI revision: 03
Detected scsi disk sda at scsi0, channel 0, id 5, lun 0
SCSI device sda: hdwr sector= 512 bytes. Sectors= 17916240 [8748 MB] [8.7 GB]
 sda: sda1 < sda5 >
[allens@allen allens]$ mount sda1
mount: can't find sda1 in /etc/fstab or /etc/mtab
[allens@allen allens]$

Note A second issue, also

Re: Ok SCSI working, now on to the next! Thanks (S. Allen)
Date: 2000, Jun 08
From: S. Allen allen18

A side effect of all this success is that my parallel
printer is not detected, and sound is not recognized--
both were before.

I am not convinced that this has anything to do with the
PCMCIA, rather perhaps a download of RPMs from Red Had
and forgetting to turn on (don't touch configuration).

I ran printtools, and the HP855 printer is not recongized.

I understand if this is the subject for a different forum.

Thanks again.

None I think the driver side is all fine

Re: Ok SCSI working, now on to the next! Thanks (S. Allen)
Date: 2000, Jun 08
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> cd /dev
> ./MAKEDEV st0 (should I have used sd--something?).

I'm pretty sure you already have appropriate st (tape) and sd (disk)
devices in /dev.

>   Vendor: HP Model: T20 Rev: 3.00
>   Type: Sequential-Access ANSI SCSI revision: 02
> (scsi0:0:5:0) Synchronous at 20.0 Mbyte/sec, offset 15.
>   Vendor: IBM Model: DNES-309170W Rev: SAH0
>   Type: Direct-Access ANSI SCSI revision: 03
> Detected scsi disk sda at scsi0, channel 0, id 5, lun 0
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 17916240 [8748 MB]
> [8.7 GB]
>  sda: sda1 < sda5 >

This all looks good to me.  But I think maybe you don't have the SCSI
tape driver loaded?

> [ allens@allen allens]$ mount sda1
> mount: can't find sda1 in /etc/fstab or /etc/mtab

I'm not sure what you expected from this: "mount sda1" is not a well
formed mount command.  You can say "mount /dev/sda1 /mnt" (replace
/mnt with wherever you want to mount the device).

-- Dave

None Problem w/Thinkpad 390

Date: 2000, Jun 07
From: John Auer jaa

 System: IBM Thinkpad 390
 OS: Debian 2.2.14
 cardctl version 3.1.15
 PCMCIA card: 3COM 3CXEM556 NIC/modem

 Current config.opts settings:
   include port 0x108-0x4ff, port 0x1000-0x17ff
   include memory 0xc0000-0xfffff
   include memory 0xa0000000-0xa0ffffff
   exclude irq 3
   exclude irq 4
   exclude irq 5
   exclude irq 7

 Also tried:
   include memory 0xa0000000-0xa0ffffff,
           memory 0x60000000-0x60ffffff

If I boot into Linux directly from powerup, I consistently get "timed out during reset" errors. Booting into 98 first, and then rebooting into Linux doesn't work the first time (bridge register mapping failed). Rebooting (into Linux) again DOES work. I've tried different high mem settings, interrupt exclusion, etc., but I can't make heads or tails of this. Any help will be greatly appreciated.

-John-

First (cold) boot:

Jun  7 12:49:47 debian kernel: Linux PCMCIA Card Services 3.1.15
Jun  7 12:49:47 debian kernel:   kernel build: 2.2.14 #1 Thu Apr 13 18:21:46 EST
 2000
Jun  7 12:49:47 debian kernel:   options:  [pci]
Jun  7 12:49:47 debian kernel: PCI routing table version 1.0 at 0xfdf80
Jun  7 12:49:47 debian kernel:   00:03.0 -> irq 11
Jun  7 12:49:47 debian kernel:   00:03.1 -> irq 11
Jun  7 12:49:47 debian kernel: Intel PCIC probe:
Jun  7 12:49:47 debian kernel:   TI 1250A rev 02 PCI-to-CardBus at slot 00:03, m
em 0x8000000
Jun  7 12:49:47 debian kernel:     host opts [0]: [serial pci & irq] [pci irq 11
] [lat 168/176] [bus 32/34]
Jun  7 12:49:47 debian kernel:     host opts [1]: [serial pci & irq] [pci irq 11
] [lat 168/176] [bus 35/37]
Jun  7 12:49:47 debian kernel:     ISA irqs (scanned) = 3,5,7,9,10 PCI status ch
anges
Jun  7 12:49:47 debian cardmgr[123]: starting, version is 3.1.15
Jun  7 12:49:47 debian cardmgr[123]: watching 2 sockets
Jun  7 12:49:47 debian kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1000
-0x104f
Jun  7 12:49:47 debian kernel: cs: IO port probe 0x0108-0x04ff: excluding 0x120-
0x127 0x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7
Jun  7 12:49:50 debian kernel: cs: socket 1 timed out during reset

First boot after using Windows 98:

Jun  7 12:55:23 debian kernel: Linux PCMCIA Card Services 3.1.15
Jun  7 12:55:23 debian kernel:   kernel build: 2.2.14 #1 Thu Apr 13 18:21:46 EST
 2000
Jun  7 12:55:23 debian kernel:   options:  [pci]
Jun  7 12:55:23 debian kernel: PCI routing table version 1.0 at 0xfdf80
Jun  7 12:55:23 debian kernel:   00:03.0 -> irq 11
Jun  7 12:55:23 debian kernel:   00:03.1 -> irq 11
Jun  7 12:55:23 debian kernel: Intel PCIC probe:
Jun  7 12:55:23 debian kernel:   Bridge register mapping failed: check cb_mem_ba
se setting
Jun  7 12:55:23 debian kernel: not found.
Jun  7 12:55:23 debian kernel: ds: no socket drivers loaded!
Jun  7 12:55:23 debian cardmgr[123]: starting, version is 3.1.15
Jun  7 12:55:23 debian cardmgr[123]: no pcmcia driver in /proc/devices
Jun  7 12:55:23 debian cardmgr[123]: exiting

2nd Linux boot (after using 98):

Jun  7 12:58:10 debian kernel: Linux PCMCIA Card Services 3.1.15
Jun  7 12:58:10 debian kernel:   kernel build: 2.2.14 #1 Thu Apr 13 18:21:46 EST
 2000
Jun  7 12:58:10 debian kernel:   options:  [pci]
Jun  7 12:58:10 debian kernel: PCI routing table version 1.0 at 0xfdf80
Jun  7 12:58:10 debian kernel:   00:03.0 -> irq 11
Jun  7 12:58:10 debian kernel:   00:03.1 -> irq 11
Jun  7 12:58:10 debian kernel: Intel PCIC probe:
Jun  7 12:58:10 debian kernel:   TI 1250A rev 02 PCI-to-CardBus at slot 00:03, m
em 0x8000000
Jun  7 12:58:10 debian kernel:     host opts [0]: [pci + serial irq] [pci irq 11
] [lat 168/176] [bus 32/34]
Jun  7 12:58:10 debian kernel:     host opts [1]: [pci + serial irq] [pci irq 11
] [lat 168/176] [bus 35/37]
Jun  7 12:58:10 debian kernel:     ISA irqs (scanned) = 3,5,7,9,10 PCI status ch
anges
Jun  7 12:58:10 debian cardmgr[123]: starting, version is 3.1.15
Jun  7 12:58:10 debian cardmgr[123]: watching 2 sockets
Jun  7 12:58:10 debian kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1000
-0x104f
Jun  7 12:58:10 debian kernel: cs: IO port probe 0x0108-0x04ff: excluding 0x120-
0x127 0x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7
Jun  7 12:58:49 debian cardmgr[123]: socket 1: 3Com/Megahertz 3CXEM556 Ethernet/
Modem
Jun  7 12:58:49 debian cardmgr[123]: executing: 'modprobe 3c589_cs'
Jun  7 12:58:49 debian cardmgr[123]: executing: 'modprobe serial_cs'
Jun  7 12:58:49 debian kernel: eth0: 3Com 3c589, io 0x310, irq 9, hw_addr 00:00:
86:1F:D8:9B
Jun  7 12:58:49 debian kernel:   8K FIFO split 5:3 Rx:Tx, auto xcvr
Jun  7 12:58:49 debian kernel: tty00 at 0x03f8 (irq = 9) is a 16550A
Jun  7 12:58:49 debian cardmgr[123]: executing: './network start eth0'
Jun  7 12:58:49 debian cardmgr[123]: executing: './serial start ttyS0'
Jun  7 12:58:50 debian kernel: eth0: flipped to 10baseT

None It is a BIOS bug; there is a workaround

Re: None Problem w/Thinkpad 390 (John Auer)
Date: 2000, Jun 07
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It is a BIOS bug and the fix is given in thread #42 on this list.  You
want to set:

  CORE_OPTS="cb_mem_base=0x20000000"

in /etc/sysconfig/pcmcia, because your BIOS has mapped your CardBus
bridge into the middle of your system memory.  You also need to have a
fairly new set of PCMCIA drivers to handle this fix; 3.1.15 is
current.

-- Dave

None That fixed one thing, the other is still broken

Re: None It is a BIOS bug; there is a workaround (David Hinds)
Date: 2000, Jun 07
From: John Auer jaa

Thanks, Dave. The cb_mem_base problem is now gone. But I still get "timed out during reset" errors like:

Jun 7 12:49:50 debian kernel: cs: socket 1 timed out during reset

Rebooting (into Linux) hasn't fixed this.

Ok solved

Re: None That fixed one thing, the other is still broken (John Auer)
Date: 2000, Jun 07
From: John Auer jaa

Found the problem. Yet another thing the BIOS isn't taking care of:

PCIC_OPTS="p2cclk=1"

Question Memory range suggestions for IBM 760EL

Date: 2000, Jun 11
From: KC KC

Hi,
I am using kernel 2.2.10 with PCMCIA Card services 3.0.14.
Trying to install two PC cards (IBM Credit Card II and 3Com 
Megahertz) but only one works when installed.  Separately, 
they work fine.

PCMCIA HOWTO's indicated resource issue and looking at the sys 
logs, it is specific for memory windows.  I have tried a WIDE 
variety of memory inclusions but I can still only get one to 
work when both are installed.  The latest sys log indicates:

(socket 0 = IBM CC II)
Initializing socket 0
Memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff
Memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff
warning: no high memory space available!
Memory probe 0x0d0000-0x0dffff: excluding 0x0d0000-0x0dffff
Memory probe 0x0c0000-0x0cffff: excluding 0x0c0000-0x0cffff
socket 0: Anonymous Memory
.
.
Memroy_cs: mem0: anonymjous: unknown size
executing: './memory start mem0

Then Socket 1 initialized successfully with the 3Com PC lan 
card.

Any suggestion on the ranges that I can try for this 
combination???

Thanks in advance!!

None I think your diagnosis is incorrect

Re: Question Memory range suggestions for IBM 760EL (KC)
Date: 2000, Jun 12
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It is almost definitely not a memory window issue.  It is 99% likely
an interrupt issue.  Undo whatever you've done to the default memory
settings.  The defaults work fine on a 760EL; I have one myself.

There is a section in the PCMCIA-HOWTO about exactly this situation;
see section 3.9, "Resource conflict only with two cards inserted".

-- Dave

Question Help with PCMCIA 3.1.16 and kernel 2.2.16

Date: 2000, Jun 13
From: Dave Persing dave_p

Greetings guys,

This is my first post, and I'm hoping y'all can tell me what I'm missing here..

I'm running SuSE 6.4 on my Dell Latitude CP. I downloaded the new 2.2.16 kernel and compiled it. The kernel works fine until it tries to load my PCMCIA card stuff. I downloaded the newest version of PCMCIA and configured/compiled it and got everything installed. Now, when I boot up in my new kernel, I get a segmentation fault errors when I try to load the base modules. One of the errors: /sbin/init.d/rc2.d/S03pcmcia line154 68 Segmentation fault /sbin/modprobe -nv $PCMCIA $PCMCIA_PCIC_OPTS

But when I load up my previous kernel (2.2.14) it works fine with PCMCIA 3.1.16. Everything boots up and configures.

That's it. Thanks!

Any thoughts?

Thanks a ton!

Dave

None Not sure: 2.2.16 works for me

Re: Question Help with PCMCIA 3.1.16 and kernel 2.2.16 (Dave Persing)
Date: 2000, Jun 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> One of the errors: /sbin/init.d/rc2.d/S03pcmcia
> line154 68 Segmentation fault /sbin/modprobe -nv $PCMCIA
> $PCMCIA_PCIC_OPTS

I don't have an answer for you; it works for me with 2.2.16.  My
version of modprobe does not even offer a "-n" option.  If modprobe is
seg faulting (and you are not seeing kernel traps), then I wonder if
it is actually a modutils problem.  Such things should not happen with
stable kernels but I don't have an alternative explanation.

-- Dave

None Still not working...

Re: Question Help with PCMCIA 3.1.16 and kernel 2.2.16 (Dave Persing)
Date: 2000, Jun 14
From: Dave Persing dave_p

I still got the segmentation fault when I tried to execute the start up script for PCMCIA. I tried taking out the -n option for modprobe, and it booted up in 2.2.14 (not in 2.2.16) but when I tried 2.2.16, it gave me the same error again. Then, when I tried taking out the lines completely, I still got a segmentation fault!

I'm still examining the script to make sure there aren't other faults that I'm missing..Could the fact that I'm running SuSE with a precompiled kernel mean anything? perhaps my laptop just hates me? Other thoughts? Suggestions? Flames about my stupid laptop?

Just an afterthought, thanks to the guy(s?) who made the script for making the Netgear FA410TXC. you guys are a godsend.

Thanks a ton! Dave

Ok Fix for Dell I7K freezing on resume with 3.1.9+

Date: 2000, Jun 13
From: Piete Brooks pb

I found that using any pcmcia-cs version post 3.1.8 caused my Dell Inspiron 7000s to freeze when resumed (e.g. on opening lid). Dave does not understand why it is needed, but it appear to be related to the change of defaults for i82365. The fix is to change /etc/sysconfig/pcmcia to have
PCIC_OPTS="pci_csc=0 pci_int=0"
to set it back to using ISA interrupts (the BIOS does not allow the card type to be set).

Question Configuring ethernet card based on interface allocated

Date: 2000, Jun 14
From: Paul Moore pmoore

I have a laptop with two ethernet cards - one in the docking station and one on a PCMCIA card. I have a fixed IP address allocated to the laptop, and a DHCP server available to me.

What I'd like to do is to have the docking station card get the fixed address whenever I'm docked, and the PCMCIA card get it when I'm not docked.

I can do this with schemes, but that means that I have to select manually on boot-up.

What I'd prefer is to say to the PCMCIA setup, "if the ethernet card is allocated to eth0, give it the fixed IP address, otherwise grab an address via DHCP". This way, when I'm docked, the docking station card gets eth0 (as its module is loaded first, on boot-up) and the PCMCIA card gets eth1 and looks on DHCP (and almost certainly gets nothing, as there will be no cable connected). When I'm undocked, the PCMCIA card gets eth0 and the fixed IP address.

Is this possible? And if not, is it a reasonable thing to request as a new feature?

Thanks, Paul Moore.

None Sure it's possible...

Re: Question Configuring ethernet card based on interface allocated (Paul Moore)
Date: 2000, Jun 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The device name is visible in the network.opts script: it is in
$DEVICE.  You could select what to do based on this variable, instead
of deciding based on $ADDRESS.

-- Dave

Ok Thanks - it's obvious now

Re: None Sure it's possible... (David Hinds)
Date: 2000, Jun 15
From: Paul Moore pmoore

Aaargh - it's so obvious now. I totally missed the $DEVICE variable, possibly because the HOWTO and all the documentation I've seen (as well as the Debian example network.conf) uses $ADDRESS as the example of how to check for different configs.

Thanks for the help, and apologies for the dumb question.

Paul

Sad "Bad address mapping" on Sony N505VE

Date: 2000, Jun 18
From: toby cabot toby

I've been using Mandrake 6.1 on a VAIO N505-VE for almost 6 months now and everything worked OK until recently. I've got a Linksys Etherfast 10/100 ethernet card.

Last thursday I started getting strange messages about infinite loops in eth0 interrupts. I used this as an excuse to upgrade to a newer kernel from Mandrake 7.1: kernel 2.2.15 with pcmcia services 3.1.15 as built by Mandrake. This eliminated the problem and things were a-ok for a couple of days.

This afternoon, after a reboot, I started to get "Bad bridge mapping at 0x000000dc" messages when I try to load i82365.o.

I notice in the "known problems" page that this error is caused by some 2.3.x kernels, but I'm not that cutting edge, I'm seeing it with the 2.2 series so I can't revert as a workaround.

Any ideas appreciated; this is the first time in three years of my using Linux that something worked for a while and then stopped working mysteriously. I doubt it's a hardware failure since win98 still works fine on the same machine.

Thanks,
Toby

None A strange problem

Re: Sad "Bad address mapping" on Sony N505VE (toby cabot)
Date: 2000, Jun 19
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I don't understand how something like this could develop all of a
sudden.  Does it matter if you cold boot linux, versus warm booting
from windows?  If the reported bridge mapping address is 0x000000dc,
that would certainly be a problem; the BIOS is supposed to fill this
in, and it is putting it in space used by your system RAM.

The pcmcia_core module has a parameter, cb_mem_base, that lets you
override the bridge address selected by the BIOS.  You could try using
that as a workaround, assuming this isn't just a symptom of something
more serious.  My first guess was "hardware failure" until you said it
still works under Windows.

-- Dave

Sad you're not kidding

Re: None A strange problem (David Hinds)
Date: 2000, Jun 20
From: toby cabot toby

Dave,

It sure is a strange problem. I can't for the life of me figure out what changed between "working fine" for the last five months since the machine was new and "FUBAR" now. I've tried warm-booting from Windows, cold boot, remove battery and power then re-boot, and nothing seems to work (except for win98, which works fine, which really pisses me off).

I scanned my messages log and found that the bridge mapping used to be 0x68000000 when things were working. So I tried setting the cb_mem_base to 0x68000000 but then get "Bad bridge mapping at 0x680000dc!".

I've also tried kernel 2.2.16 with pcmcia-cs 3.1.16 with the same results.

I looked for BIOS upgrades on the Sony website and no luck.

I guess I could try a pre-2.4 kernel but I'm not usually that cutting-edge.

Regards,
Toby

None Maybe a very particular hardware fault

Re: Sad you're not kidding (toby cabot)
Date: 2000, Jun 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> I scanned my messages log and found that the bridge mapping used to be
> 0x68000000 when things were working. So I tried setting the cb_mem_base
> to 0x68000000 but then get "Bad bridge mapping at 0x680000dc!".

This smells like a hardware failure.  The PCMCIA drivers are writing
0x68000000 to a register, and it is reading back as 0x680000dc.  Maybe
Windows works because it only writes to this register and never relies
on reading it back.

Just for kicks, you could try editing modules/i82365.c, find the line
that says:

 pci_readl(s, PCI_BASE_ADDRESS_0, &s->cb_phys);

and add right after that:

 s->cb_phys &= ~0x0fff;

-- Dave

Agree looks like you're right

Re: None Maybe a very particular hardware fault (David Hinds)
Date: 2000, Jun 21
From: toby cabot toby

Dave,

Great suggestion! When we meet the beer is on me.

By hard-wiring i82365.c I'm now back online. I went for the full-bore hardcoded memory address:

s->cb_phys = 0x68000000;

Thanks,
Toby

PS. I'm also seeing the dropped ethernet interrupts after a suspend/resume. I'm not a driver programmer but if you need someone to guinea pig some new code on a N505VE please give me a shout.

Question Cardbus interface in a desktop pc ?

Date: 2000, Jun 20
From: Geir Thomassen geir

Is anyone aware of any Cardbus interfaces which can be installed in a standard desktop PC ? I have found the Actiontec PC750 (http://www.actiontec.com/products/readers/pc750/pc750_overview.html), which looks nice, but it doesn't support cardbus devices (even though it has a PCI interface). Actiontec claims Linux support, can anyone verify this ?

-- Geir

None SCM makes a CardBus card reader

Re: Question Cardbus interface in a desktop pc ? (Geir Thomassen)
Date: 2000, Jun 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It seems to be somewhat hard to find.

-- Dave

Question 2.4 test2 and cs4232

Date: 2000, Jun 29
From: Brad Langhorst bwlang

I've just installed 2.4test2 on my redhat 6.2 system I compiled PCMCIA into the kernel. Card services seems to work just fine but it is camping out on irq 5

/proc/interrupts  says
 ...
 5:    0     XT-PIC  Texas Insturments PCI1250
 ...
 11:   3456  XT-PIC  Texas Instruments PCI1250

Since my crystal audio 4232 must use irq5 I want to move card services to 10 (which is not listed in /proc/interrupts). However when i add

 PCIC_OPTS= "cs_irq=10 irq_list=11"

to /etc/sysconfig/pcmcia nothing changes. I also tried

 PCIC_OPTS= "pci_csc=1 pci_int=1 do_scan=1 irq_list=11"

also to no avail

any suggestions?

None You probably can't change this

Re: Question 2.4 test2 and cs4232 (Brad Langhorst)
Date: 2000, Jul 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The PCI interrupt assignment is probably not changeable at all.  This
is determined by how your PCI devices are wired up, and is not
software programmable.

In some cases, there is some configurability here, but I have no user
tools for doing it.  You could check your BIOS setup menus to see if
there are any interrupt sharing options.

The dump_pirq script in the debug-tools directory will dump out your
BIOS interrupt routing table.  This shows which PCI interrupt lines
are shared.  Any devices sharing the same interrupt link value are
physically wired together.

-- Dave

Question Problems with PCI-PCMCIA Adapter

Date: 2000, Jun 30
From: Derek Sims interdart

Hi, I am trying out out a PCI-PCMCIA adapter which uses a TI chip (Elan P111). Using RedHat 6.1 + PCMCIA 3.1.8 My problem is the response time is poor - the cards install ok but ethernet ping is 20ms (ne) and Wireless Lan (Breezecom) can be anything from 120 ms to 1000 ms. The same cards in an old 486 laptop Win95) give respectively normal ping times.

I suspect the problem is associated with the adapter PCI interrupt, /proc/interrupts shows the PCMCIA card, but nothing for the adapter (is this normal?). lspci shows the following for the adapter:

00:12.0 CardBus bridge: Texas Instruments: unknown device ac50 (rev 01)

I have tried PCIC_OPTS="pci_int=1 irq_mode=3" and a number of other combinations - nothing seems to make any difference.

Can anyone suggest where I am going wrong?

TIA,

None Should try newer drivers

Re: Question Problems with PCI-PCMCIA Adapter (Derek Sims)
Date: 2000, Jul 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

For PCI card docks, you need a newer set of PCMCIA drivers.  The
latest release is 3.1.17.  You also need to then specify irq_mode=0.

-- Dave

Question Seek laptop recommendation for 2 PCMCIA cards

Date: 2000, Jul 01
From: A. N. Chari chari

Hi !

I'm thinking of buying a cheap laptop on which I would want to run Linux. I plan to use 2 PCMCIA cards - a wavelan card and an ethernet card. I understand that there are issues with configuring 2 PCMCIA cards on Toshiba laptops - in fact I'm trying to help a friend sort through precisely that problem.

Does anyone have any suggestions on problem-free laptops in terms of installing 2 cards ?

Thanks !

-Chari.

None I haven't heard of that sort of problem before

Re: Question Seek laptop recommendation for 2 PCMCIA cards (A. N. Chari)
Date: 2000, Jul 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I know of no problems with Toshiba or other laptops having to do with
handling two cards at once.

You can sometimes run into interrupt conflicts that only show up when
two cards are in use, but that is just a matter of adding the right
interrupt constraints to /etc/pcmcia/config.opts.  There is a section
in the PCMCIA-HOWTO about that issue.

-- Dave

Feedback RE : problems with multiple cards

Re: None I haven't heard of that sort of problem before (David Hinds)
Date: 2000, Jul 05
From: A. N. Chari chari

Hi Dave,

	Thanks for getting back to me.

I tried setting "poll_interval=100", and also separately restricting the irq_list to the interrupts reported as unused in /proc/interrupts, and combinations of these, as you suggested in the HOWTO, but my Toshiba 1625 still fails to configure both cards. The first inserted card does okay, but the second one generates "RequestIRQ : Resource in use".

	Same problem with Compaq Presario 1925.

	With Toshiba 2180CDT, both cards worked after I downloaded the pcmcia3.1.17 version (which is now installed on all three)

	Any suggestions would be much appreciated.

	Thanks again,

-Chari.

None Re: Feedback: RE : problems with multiple cards

Re: Feedback RE : problems with multiple cards (A. N. Chari)
Date: 2000, Jul 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'd need to see the PCMCIA driver messages in each case.  You may want
to comment out some of the default interrupt exclusions from your
/etc/pcmcia/config.opts file.  Basically you just need to get the
appropriate number of free interrupts.  The i82365 driver reports
which interrupts seem to be available for its use.

-- Dave

Question Lucent PCI bridge problems

Date: 2000, Jul 04
From: Philippe Clérié pclerie

Hi everyone:

I am having a difficult time installing a Lucent WavelanIEEE card. I am stuck because an irq test failed. Previous attempts with pcmcia-cs 3.1.13 failed with "unknown PCI interrupt router".

I have tried several options mentionned in some of the messages on this forum and none works. Specifically, it does not matter what irq_mode value I use. No irq_list has worked. I also tried cb_pci_irq=11. Always the same results.

The computer is an AcerPower Sn with RedHat 6.0. Hope someone can give me a clue.

Thanks, Philippe

From /var/log/messages
========================
Linux PCMCIA Card Services 3.1.17
  kernel build: 2.2.5-15 #1 Mon Apr 19 21:39:28 EDT 1999
  options:  [pci] [cardbus] [apm] [pnp]
PCI routing table version 1.0 at 0xf7900
PnP: PNP BIOS installation structure at 0xc00f5f50
PnP: PNP BIOS version 1.0, entry at f9e00:0, dseg at f0000
Intel PCIC probe: 
  TI 1225 rev 01 PCI-to-CardBus at slot 00:10, mem 0x68000000
    host opts [0]: [pci only] [pci irq 11] [lat 168/176] [bus 0/34]
    host opts [1]: [pci only] [pci irq 11] [lat 168/176] [bus 0/37]
    PCI irq 11 test failed
    *NO* card interrupts, polling interval = 1000 ms
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.

Dump_irq
=========
Interrupt routing table found at address 0xf7900:
  Version 1.0, size 0x00a0
  Interrupt router is device 00:07.0
  PCI exclusive interrupt mask: 0x0000
  Compatible router: vendor 0x10b9 device 0x1533

Device 00:01.0 (slot 0):
  INTA: link 0x01, irq mask 0x1ef8
  INTB: link 0x02, irq mask 0x1ef8
  INTC: link 0x03, irq mask 0x1ef8
  INTD: link 0x04, irq mask 0x1ef8

Device 00:0b.0 (slot 0):
  INTA: link 0x04, irq mask 0x1ef8

Device 00:02.0 (slot 0):
  INTA: link 0x59, irq mask 0x1ef8

Device 00:0f.0 (slot 0):

Device 00:03.0 (slot 0):

Device 00:14.0 (slot 1):
  INTA: link 0x01, irq mask 0x1ef8
  INTB: link 0x02, irq mask 0x1ef8
  INTC: link 0x03, irq mask 0x1ef8
  INTD: link 0x04, irq mask 0x1ef8

Device 00:13.0 (slot 2):
  INTA: link 0x02, irq mask 0x1ef8
  INTB: link 0x03, irq mask 0x1ef8
  INTC: link 0x04, irq mask 0x1ef8
  INTD: link 0x01, irq mask 0x1ef8

Device 00:10.0 (slot 3):
  INTA: link 0x03, irq mask 0x1ef8
  INTB: link 0x04, irq mask 0x1ef8
  INTC: link 0x01, irq mask 0x1ef8
  INTD: link 0x02, irq mask 0x1ef8

Interrupt router at 00:07.0: AcerLabs Aladdin M1533 PCI-to-ISA bridge
  INT1 (link 1): irq 9
  INT2 (link 2): irq 10
  INT3 (link 3): irq 11
  INT4 (link 4): irq 5
  INT5 (link 5): unrouted
  INT6 (link 6): unrouted
  INT7 (link 7): unrouted
  INT8 (link 8): unrouted
  Serial IRQ: [disabled] [quiet] [frame=21] [pulse=12]

Ok Untitled

Re: Question Lucent PCI bridge problems (Philippe Clérié)
Date: 2000, Jul 05
From: Philippe Clérié pclerie

OK! It's fixed. As a last ditch measure before going into panic mode, I cleaned the contacts on the card. That did it!

Silly, isn't it?

Thanks Philippe

Question cardinfo install

Date: 2000, Jul 06
From: mike thomas mikeyt1

Where can I find some info on installing cardinfo. I just installed pcmcia-cs-3.1.17, and I think I should have installed the updated cardinfo first. Where do I get cardinfo? Is it part of the download? How do I install it?

Thanks

Mike

None You've got the source code, at least

Re: Question cardinfo install (mike thomas)
Date: 2000, Jul 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

cardinfo is in the package you installed.  If a new one was not built
for you, then you don't have the "xforms" library installed.  Get the
0.88.1 RPM for that and install that, then re-configure and re-build
the PCMCIA tree (when you do "make config" for PCMCIA, at the end it
will tell you if xforms is installed).

cardinfo also hasn't changed in quite a long time, so an old one
should still be quite ok.

-- Dave

Question Untitled

Re: None You've got the source code, at least (David Hinds)
Date: 2000, Jul 07
From: mike thomas mikeyt1

David,

I get the error, Card Services release does not match. When I run cardinfo.

I have installed xforms (Is this the Forms Library?). At the end of make config, it says that I need the X windows include files. The help file says normal X header files. What files are these?

Thanks

Mike

None Re: Question: Untitled

Re: Question Untitled (mike thomas)
Date: 2000, Jul 07
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The X header files are in the XFree86-devel package.  You need to
install this to compile any graphical program.

-- Dave

Ok Success

Re: None Re: Question: Untitled (David Hinds)
Date: 2000, Jul 07
From: mike thomas mikeyt1

Its working.

Thanks for the help.

Mike

Question ADVICE: Configuring my PCMCIA GSM Modem

Date: 2000, Jul 09
From: F FrankC

Warning bug in Configure script for alternate root directory in 3.1.17

Date: 2000, Jul 11
From: Hughes MALPHETTES hughesma

Hi,

configuring with the "--target=/myAlternateDir" comment has no effect on the various 'config.*' files generated with version 3.1.17.

I have checked the script with Jean II and ended with a workaround: we added manually to each of the files generated by the configure script the line "PREFIX=/myAlternateDirectory".
I have not tried 3.1.18 yet though.

regards
Hughes

None Already fixed

Re: Warning bug in Configure script for alternate root directory in 3.1.17 (Hughes MALPHETTES)
Date: 2000, Jul 11
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> I have not tried 3.1.18 yet though.

It is fixed in 3.1.18.

-- Dave

Question installing a Quatech spp-100 pcmcia card with 3.1.14 on kernel 2.3.99pre8

Date: 2000, Jul 11
From: fletch

I have a Quatech spp-100 parallel port card that I would like to use with ppdev user-drivers, but cannot get the pcmcia card services to work correctly. I am using pcmcia-cs-3.1.14 and kernel 2.3.99-pre8 with parport, parport_pc,ppdev made as modules (they are shown in /lib/modules/2.3.99-pre8/misc as parport.o parport_pc.o, ppdev.o). When I attempt to start pcmcia services I receive a high beep followed by a low beep. The cardctl ident shows the correct card "Quatech Spp-100 enhanced parallel port card." I did the make config,make all, and make install in the /usr/src/pcmcia-cs-3.1.14. But I did not see the parport_cs.o in /lib/modules/2.3.99-pre8/pcmcia.

Is there something else that I have missed to install this pcmcia card? Any help would be very much appreciated.

If anyone has or is using the Quatech spp-100 card in the 2.3 kernel, I would like any information about the installation and/or configuration of the card. Thanks

None That combo won't work, for now

Re: Question installing a Quatech spp-100 pcmcia card with 3.1.14 on kernel 2.3.99pre8
Date: 2000, Jul 11
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The parport_cs driver has not been adapted to work with 2.3 kernels;
that is documented in the BUGS file.

I haven't had time to work on it, and since I never use the Quatech
card, it has slipped pretty low on my list of things to do.

-- Dave

Question what combo will work with parport_cs driver

Re: None That combo won't work, for now (David Hinds)
Date: 2000, Jul 16
From: fletch

Question Orinoco/WaveLan ISA adapter -- problems on 486 w/2.0.35 kernel

Date: 2000, Jul 13
From: David D. Johnson ddj

I bought a pair of 11mb/s pc cards and an ISA adapter, and
have had some problems getting the thing set up on the old
system I'm using as my firewall.

The system is a 486 DX/66 with 64MB ram.  I have aha 1542b
scsi controller, two ne200 clone NIC cards, crappy VGA, etc.
The system was originally slackware, with the kernel at 2.0.35.
The BIOS is AMD, and I have the feeling it doesn't support PnP.

This morning I built pcmcia-cs-3.1.15 and plugged in the card.
When I did make install, the etc/install-etc script hung the
system when it called ../cardmgr/probe.  After hitting reset
and waiting forever for it to check the disks, I grabbed the
pcmcia-cs-3.1.18 and built that.  This time I did chmod -x
on cardmgr/probe before doing the make install, and things
completed.

I checked lsmod, and the i82365 and ds modules were loaded.

Then I did some reading here, and saw a mention of isapnp and
pnpdump, so of course I had to try them out.
Pnpdump also hung the system dead.

Until I get home to reboot, that's where things stand.

My questions:

0) Is there a search facility for HyperNews?
1) Is anyone up and running with similarly antiquated HW/SW?
2) Can I set things up without running probe?
3) Should I pack the cards up and send them back?

Thanks,

	-- ddj
	Dave Johnson
	ddj@brown.edu

None "probe" isn't required for anything

Re: Question Orinoco/WaveLan ISA adapter -- problems on 486 w/2.0.35 kernel (David D. Johnson)
Date: 2000, Jul 13
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Do you happen to know if any of your ISA hardware is likely to
conflict with the PCMCIA card reader at IO address 0x3e0?

> I checked lsmod, and the i82365 and ds modules were loaded.

If the i82365 module is loaded, check "dmesg" to see what it had to
say about your card reader.  The only purpose for running "probe" is
to identify your PCMCIA card reader, but if you already know the
i82365 driver is working, then that is moot.

-- Dave

Ok Re: "probe" isn't required for anything

Re: None "probe" isn't required for anything (David Hinds)
Date: 2000, Jul 13
From: David D. Johnson ddj

David Hinds wrote:
> Do you happen to know if any of your ISA hardware is likely to
> conflict with the PCMCIA card reader at IO address 0x3e0?
 
It looks clean -- net cards at 0240/0340, scsi at 330,
and vga at 3c0.  The i82365 showed up at 03e2/03e3.

Here is the dmesg output:
----------------
Linux PCMCIA Card Services 3.1.18
  kernel build: 2.0.35 #14 Thu May 6 09:05:12 EDT 1999
  options:  [pci] [apm]
Intel PCIC probe: 
  Vadem VG-469 rev 00 ISA
    host opts [0]: none
    host opts [1]: none
    ISA irqs (scanned) = 3,4,7,9,10,12 status change on irq 10
cs: IO port probe 0x0100-0x03ff: excluding 0x1c8-0x1cf 0x200-0x207 0x240-0x25f 0x340-0x34f 0x378-0x37f
cs: IO port probe 0x0a20-0x0a27: clean.
cs: memory probe 0x0d0000-0x0dffff: excluding 0xdc000-0xddfff
cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xc7fff
----------------


So, this looks ok to me....  Time to poke at the PC card.
Thanks for the help,

	-- ddj

Warning 3.1.18 & Kernel 2.4.0-test4

Date: 2000, Jul 18
From: Alan Shutko AlanShutko

test4 has some of the same header files as pcmcia-cs, but without the same contents. If I try to build, dump_cis fails because it can't find all sorts of things. Changing config.mk to -I ../include before the linux kernel directory seems to cure it (although I haven't tried using it yet).

Sample brokenness:

 make[1]: Entering directory  `/usr/src/pcmcia-cs-3.1.18/debug-tools'
 cc  -MD -O -Wall -Wstrict-prototypes -pipe -I../include/static -I/usr/src/linux/include -I../include -I../modules -c dump_cis.c
 dump_cis.c:785: parse error before `*'
 dump_cis.c:786: warning: function declaration isn't a  prototype
 dump_cis.c: In function `print_format':
 dump_cis.c:787: `fmt' undeclared (first use in this function)
 dump_cis.c:787: (Each undeclared identifier is reported only  once 
 dump_cis.c:787: for each function it appears in.)
 dump_cis.c:787: `CISTPL_FORMAT_DISK' undeclared (first use in  this function)
 dump_cis.c:789: `CISTPL_FORMAT_MEM' undeclared (first use in  this function) 

None This should be fixed in the current beta

Re: Warning 3.1.18 & Kernel 2.4.0-test4 (Alan Shutko)
Date: 2000, Jul 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It is fixed in the current beta on sourceforge.org in /pcmcia/NEW.

It is always a good idea to check the beta directory if you are using
an experimental kernel release.

-- Dave

Question install pcmcia on twinhead p79tx

Date: 2000, Jul 20
From: liu liqun happydog

I installed redhat 6.2 on my twinhead p79tx (about two years old). The PCMCIA control IC is TI PCI1131. I try to use a xircom creditcard ethernet card on my laptop. Under win98, all the hardware work well. Under win98, the IRQ for the net card is 11, port 1000-100f, mem 02003000 to 02003fff , 02004000-02004ff the IRQ for the PCI1131 is 10, mem 02000000-02000fff, 02003000 -02004fff. the mem for card service is 02001000-02001fff

At first, I let the linux probe the information for me. But it lock up at boot time. I set the PCIC_OPTS="irq_list=10,11" in /etc/sysconfig/pcmcia and exclude all the irq except 10 ,11 in config.opt. The system still lock up at boot time. I find this in the log file.

Jul 19 00:36:02 newstart pcmcia: Starting PCMCIA services:
Jul 19 00:36:03 newstart pcmcia:  modules
Jul 19 00:36:03 newstart kernel: Linux PCMCIA Card Services 3.1.8 
Jul 19 00:36:03 newstart kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000 
Jul 19 00:36:03 newstart kernel:   options:  [pci] [cardbus] [apm] 
Jul 19 00:36:03 newstart pcmcia: /lib/modules/2.2.14-5.0/pcmcia/i82365.o: 
Jul 19 00:36:03 newstart pcmcia: invalid parameter parm_irq-LIST
Jul 19 00:36:03 newstart kernel: ds: no socket drivers loaded! 
Jul 19 00:36:03 newstart pcmcia:  cardmgr.
Jul 19 00:36:03 newstart pcmcia: /lib/modules/2.2.14-5.0/pcmcia/ds.o: init_module: Device or resource busy
Jul 19 00:36:03 newstart rc: Starting pcmcia succeeded
Jul 19 00:36:03 newstart cardmgr[414]: starting, version is 3.1.8
Jul 19 00:36:03 newstart cardmgr[414]: no pcmcia driver in /proc/devices
Jul 19 00:36:03 newstart cardmgr[414]: exiting

Then I set the do_scan=0,include the new mem window (0x68000000-0x68000fff). the system can not boot too. If I remove the card from the socket, the system can boot successfuly. But I will lock again after I inset the card.

Below is waht I found in the log file.

Jul 20 03:10:49 newstart pcmcia: Starting PCMCIA services:
Jul 20 03:10:49 newstart pcmcia:  modules
Jul 20 03:10:49 newstart kernel: Linux PCMCIA Card Services 3.1.8 
Jul 20 03:10:49 newstart kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000 
Jul 20 03:10:49 newstart kernel:   options:  [pci] [cardbus] [apm] 
Jul 20 03:10:49 newstart kernel: Intel PCIC probe:  
Jul 20 03:10:49 newstart kernel:   TI 1131 PCI-to-CardBus at bus 0 slot 15, mem 0x68000000, 2 sockets 
Jul 20 03:10:49 newstart kernel:     host opts [0]: [pci + serial irq] [no pci irq] [lat 64/176] [bus 1/5] 
Jul 20 03:10:49 newstart kernel:     host opts [1]: [pci + serial irq] [no pci irq] [lat 64/176] [bus 6/10] 
Jul 20 03:10:49 newstart kernel:     ISA irqs (default) = 3,4,7,9,10,11,12 polling interval = 1000 ms 
Jul 20 03:10:49 newstart pcmcia:  cardmgr.
Jul 20 03:10:49 newstart cardmgr[431]: starting, version is 3.1.8
Jul 20 03:10:49 newstart rc: Starting pcmcia succeeded
Jul 20 03:10:50 newstart cardmgr[431]: watching 2 sockets
Jul 20 03:10:50 newstart kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Jul 20 03:10:50 newstart kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x378-0x37f 0x398-0x39f 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7 
Jul 20 03:10:50 newstart inet: inetd startup succeeded

Can you tell me what shall I do next?

More Do not lockup now. But can not receive data.

Re: Question install pcmcia on twinhead p79tx (liu liqun)
Date: 2000, Jul 21
From: liu liqun happydog

I set the PCIC_IPT="irq_mod=3", then everything seem ok. But I can not still receive any data from my xircom CE3B network card. I ping the local gateway and see the yellow LED twinkle. But all the packets are losed.

Below are the log file entries.

Jul 21 14:23:05 newstart pcmcia: Starting PCMCIA services:
Jul 21 14:23:05 newstart pcmcia:  modules
Jul 21 14:23:05 newstart kernel: Linux PCMCIA Card Services 3.1.8 
Jul 21 14:23:05 newstart kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000 
Jul 21 14:23:05 newstart kernel:   options:  [pci] [cardbus] [apm] 
Jul 21 14:23:05 newstart kernel: Intel PCIC probe:  
Jul 21 14:23:05 newstart kernel:   TI 1131 PCI-to-CardBus at bus 0 slot 15, mem 0x68000000, 2 sockets 
Jul 21 14:23:05 newstart kernel:     host opts [0]: [serial pci & irq] [no pci irq] [lat 64/176] [bus 1/5] 
Jul 21 14:23:05 newstart kernel:     host opts [1]: [serial pci & irq] [no pci irq] [lat 64/176] [bus 6/10] 
Jul 21 14:23:05 newstart kernel:     ISA irqs (default) = 3,4,7,9,10,11,12 polling interval = 1000 ms 
Jul 21 14:23:05 newstart pcmcia:  cardmgr.
Jul 21 14:23:05 newstart cardmgr[460]: starting, version is 3.1.8
Jul 21 14:23:05 newstart rc: Starting pcmcia succeeded
Jul 21 14:23:06 newstart cardmgr[460]: watching 2 sockets
Jul 21 14:23:06 newstart kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Jul 21 14:23:06 newstart cardmgr[460]: initializing socket 1
Jul 21 14:23:06 newstart kernel: cs: memory probe 0x68000000-0x68ffffff: excluding 0x68000000-0x680fffff 
Jul 21 14:23:06 newstart cardmgr[460]: socket 1: Xircom CE3-10/100 Fast Ethernet
Jul 21 14:23:06 newstart inet: inetd startup succeeded
Jul 21 14:23:06 newstart cardmgr[460]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/xirc2ps_cs.o'
Jul 21 14:23:06 newstart kernel: xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh) 
Jul 21 14:23:06 newstart kernel: eth0: Xircom: port 0x1300, irq 11, hwaddr 00:80:C7:48:AA:A6 
Jul 21 14:23:06 newstart cardmgr[460]: executing: './network start eth0'
Jul 21 14:23:09 newstart kernel: eth0: MII link partner: 0021 
Jul 21 14:23:09 newstart kernel: eth0: MII selected 
Jul 21 14:23:09 newstart kernel: eth0: media 10BaseT, silicon revision 4 

Waht is wrong? should I compile the newer pcmcia code?

None Everything is not ok

Re: More Do not lockup now. But can not receive data. (liu liqun)
Date: 2000, Jul 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It doesn't work because "irq_mode=3" is wrong for this system.

-- Dave

None One thing at a time...

Re: Question install pcmcia on twinhead p79tx (liu liqun)
Date: 2000, Jul 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I think you should back up and start from scratch: restore all the
original settings.

> At first, I let the linux probe the information for me. But it lock up
> at boot time.

Was this with the card inserted, or not inserted?  Start with no
special settings and see if the system will boot.  If it does, then
insert the card.  If it does not boot, then try "do_scan=0"; do not
use the Windows interrupt settings: they are *wrong* for Linux.

> Jul 19 00:36:03 newstart pcmcia: invalid parameter parm_irq-LIST

You mis-spelled "irq_list" as "irq-LIST".

> Then I set the do_scan=0,include the new mem window
> (0x68000000-0x68000fff). the system can not boot too.

Do not set the memory window to this.  Put the original settings back.

-- Dave

More Do it step by step

Re: Question install pcmcia on twinhead p79tx (liu liqun)
Date: 2000, Jul 22
From: liu liqun happydog

1. default config.opts and /etc/sysconfig/pcmcia can not boot not matter has or not has card in the socket.

2. set do_scan=0
 2.1 has card in the socket.
 The laptop gives a high beep and display PCMCIA [OK], then  lockup. The log is:
Jul 22 03:50:33 newstart pcmcia: Starting PCMCIA services:
Jul 22 03:50:33 newstart pcmcia:  modules
Jul 22 03:50:33 newstart kernel: Linux PCMCIA Card Services 3.1.8 
Jul 22 03:50:33 newstart kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000 
Jul 22 03:50:33 newstart kernel:   options:  [pci] [cardbus] [apm] 
Jul 22 03:50:33 newstart kernel: Intel PCIC probe:  
Jul 22 03:50:33 newstart kernel:   TI 1131 PCI-to-CardBus at bus 0 slot 15, mem 0x68000000, 2 sockets 
Jul 22 03:50:33 newstart kernel:     host opts [0]: [pci + serial irq] [no pci irq] [lat 64/176] [bus 1/5] 
Jul 22 03:50:33 newstart kernel:     host opts [1]: [pci + serial irq] [no pci irq] [lat 64/176] [bus 6/10] 
Jul 22 03:50:33 newstart kernel:     ISA irqs (default) = 3,4,7,9,10,11,12 polling interval = 1000 ms 
Jul 22 03:50:33 newstart pcmcia:  cardmgr.
Jul 22 03:50:33 newstart rc: Starting pcmcia succeeded

 2.2 no card in the socket.
 can boot, But lockup again after insert the card.
the log is:
Jul 22 03:53:13 newstart pcmcia: Starting PCMCIA services:
Jul 22 03:53:13 newstart pcmcia:  modules
Jul 22 03:53:14 newstart kernel: Linux PCMCIA Card Services 3.1.8 
Jul 22 03:53:14 newstart kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000 
Jul 22 03:53:14 newstart kernel:   options:  [pci] [cardbus] [apm] 
Jul 22 03:53:14 newstart kernel: Intel PCIC probe:  
Jul 22 03:53:14 newstart kernel:   TI 1131 PCI-to-CardBus at bus 0 slot 15, mem 0x68000000, 2 sockets 
Jul 22 03:53:14 newstart kernel:     host opts [0]: [pci + serial irq] [no pci irq] [lat 64/176] [bus 1/5] 
Jul 22 03:53:14 newstart kernel:     host opts [1]: [pci + serial irq] [no pci irq] [lat 64/176] [bus 6/10] 
Jul 22 03:53:14 newstart kernel:     ISA irqs (default) = 3,4,7,9,10,11,12 polling interval = 1000 ms 
Jul 22 03:53:14 newstart pcmcia:  cardmgr.
Jul 22 03:53:14 newstart rc: Starting pcmcia succeeded
Jul 22 03:53:14 newstart cardmgr[466]: starting, version is 3.1.8
Jul 22 03:53:14 newstart cardmgr[466]: watching 2 sockets
Jul 22 03:53:14 newstart kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Jul 22 03:53:14 newstart kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x378-0x37f 0x398-0x39f 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7 

....

Jul 22 03:59:02 newstart cardmgr[466]: initializing socket 1
Jul 22 03:59:02 newstart cardmgr[466]: socket 1: Xircom CE3-10/100 Fast Ethernet
Jul 22 03:59:02 newstart kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. 
Jul 22 03:59:02 newstart cardmgr[466]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/xirc2ps_cs.o'
Jul 22 03:59:02 newstart kernel: xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh) 

None Work on this interrupt issue

Re: More Do it step by step (liu liqun)
Date: 2000, Aug 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Ok, if do_scan=0 helps, then I'd replace it with things like:

  PCIC_OPTS="irq_list=3,4,7,9,10"
  PCIC_OPTS="irq_list=3,4,7,11,12"
  PCIC_OPTS="irq_list=3,4,7"

until you can get the system to boot cleanly.  One or more interrupts
is causing a problem at boot time; it also might be the cause of the
problem when you insert your card.

It might also be a good idea to upgrade to the latest (3.1.19) PCMCIA
driver package.

-- Dave

Ok It works

Re: Question install pcmcia on twinhead p79tx (liu liqun)
Date: 2000, Aug 03
From: liu liqun happydog

irq_list=3,4,7,11,12 works.

I can use my linux box ftp, telnet ....now. But when I ping other hosts, all the packets but one lost. Maybe a configuration problem! THanks a lot, David.

Sad Wavelen(Lucent) PCI-PCMCIA adapter problems

Date: 2000, Jul 27
From: Stuart Butterfield ButterfieldS

I'm having problems trying to remotely configure wireless
networking for a colleague in Eindhoven! He's got a Lucent
Wavelan Turbo 11mb card and one of their PCI-PCMCIA 
adapters.

I have the same equipment working on a PC on my desk,
but cannot get it going on his machine. I've tried the
latest PCMCIA sources (3.1.19) and the ones that are 
working for me (3.1.14), with the same result:

kernel: Linux PCMCIA Card Services 3.1.14 
kernel:   options:  [pci] [cardbus] [apm] 
kernel: PCI routing table version 1.0 at 0xf6740 
kernel:   unknown PCI interrupt router 8086:2420 

I've seen a few other folks post messages with similar
problems, but I'm not sure if the previous suggested
causes apply here.

The device in question shows up in /proc/pci

  Bus  0, device  31, function  0:
    ISA bridge: Intel Unknown device (rev 1).
      Vendor id=8086. Device id=2420.
      Medium devsel. Fast back-to-back capable.
      Master Capable.  No bursts.

and from lspci

00:1f.0 ISA bridge: Intel Corporation 82801AB 82810 Chipset
        ISA Bridge (LPC) (rev 01)


Any advice greatly appreciated.

Stuart.Butterfield@philips.com

None Unknown interrupt router

Re: Sad Wavelen(Lucent) PCI-PCMCIA adapter problems (Stuart Butterfield)
Date: 2000, Jul 27
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Thu, Jul 27, 2000 at 08:33:24AM -0700, Stuart Butterfield wrote:

> kernel: PCI routing table version 1.0 at 0xf6740 
> kernel:   unknown PCI interrupt router 8086:2420 

Try the 27-Jul-00 beta on projects.sourceforge.net in
/pub/pcmcia-cs/NEW.  That should fix at least this part.

-- Dave

Feedback Re: Unknown interrupt router

Re: None Unknown interrupt router (David Hinds)
Date: 2000, Jul 28
From: Stuart Butterfield ButterfieldS

Thanks for that David, you are correct in that it has fixed 'at least
this part'. Any idea now how to gert it to see the controller?
Starting Card Services gives the following messages:

# /etc/rc.d/init.d/pcmcia restart
Shutting down PCMCIA services:.
Starting PCMCIA services:
    modules/lib/modules/2.2.14-5.0/pcmcia/i82365.o:
       init_module: Device or resource busy
    /lib/modules/2.2.14-5.0/pcmcia/ds.o:
       init_module: Device or resource busy cardmgr.

And in /var/log/messages:

kernel: Linux PCMCIA Card Services 3.1.20
kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000
kernel:   options:  [pci] [cardbus] [apm]
kernel: PCI routing table version 1.0 at 0xf6740
kernel: Intel PCIC probe: not found.
kernel: ds: no socket drivers loaded!
cardmgr[23072]: starting, version is 3.1.20
cardmgr[23072]: no pcmcia driver in /proc/devices
cardmgr[23072]: exiting
kernel: unloading PCMCIA Card Services


I suppose there's always a chance my colleague hasn't actually
inserted the PCI-PCMCIA cards correctly ... :-(

--
Stuart

dhinds@valinux.com writes:
 > On Thu, Jul 27, 2000 at 08:33:24AM -0700, Stuart Butterfield wrote:
 >
 > > kernel: PCI routing table version 1.0 at 0xf6740
 > > kernel:   unknown PCI interrupt router 8086:2420
 >
 > Try the 27-Jul-00 beta on projects.sourceforge.net in
 > /pub/pcmcia-cs/NEW.  That should fix at least this part.
 >
 > -- Dave

None That is not a good sign

Re: Feedback Re: Unknown interrupt router (Stuart Butterfield)
Date: 2000, Jul 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> kernel: Intel PCIC probe: not found.

Oof, that is bad.  I've had a few reports of systems that refuse to
notice that these PCI cards even exist.  Check to see if the card
shows up in /proc/pci or "lspci".  If the linux PCI system does not
see the card, then there's no way for the PCMCIA drivers to do
anything about it.

If this is the case, try contacting Martin Mares, mj@ucw.cz.  He is
the Linux PCI maintainer.

-- Dave

Agree Yep, it's a PCI failure

Re: None That is not a good sign (David Hinds)
Date: 2000, Jul 31
From: Stuart Butterfield ButterfieldS

David, you're assumption was correct. There's no sign of the Lucent bridge in /proc/pci or lspci. I'll take it to the PCI guy.

Many thanks for your help.

Stuart.Butterfield@philips.com

Agree Yep, it's a PCI failure

Re: None That is not a good sign (David Hinds)
Date: 2000, Jul 31
From: Stuart Butterfield ButterfieldS

David, your assumption was correct. There's no sign of the Lucent bridge in /proc/pci or lspci. I'll take it to the PCI guy.

Many thanks for your help.

Stuart.Butterfield@philips.com

Note Got another PCI adaptor working

Re: Sad Wavelen(Lucent) PCI-PCMCIA adapter problems (Stuart Butterfield)
Date: 2000, Jul 29
From: Brian Candler <b.candler@pobox.com>

I recently bought a 'Melco/Buffalo' card, which appears to be a rebadged WaveLan Silver. It came with its own PCI adaptor card, which the kernel identifies as a Ricoh RL5c475.

With older versions of pcmcia-cs I could not get the interrupt handling to work (i.e. it would send one packet and then time out). With 3.1.19 it now works fine if I use

 PCIC_OPTS="irq_mode=0 pci_irq_list=11"

Thanks David!! The reason I had to manually give the PCI interrupt appears to be a bug in the kernel PCI code, because I think it is in the configuration table. See below.

Regards,

Brian.

 # lspci -vvxx
 00:08.0 CardBus bridge: Ricoh Co Ltd RL5c475 (rev 80)
         Subsystem: Melco Inc: Unknown device 030a
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
         Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 32 set
         Interrupt: pin A routed to IRQ 0
                                    ^^^^^
         Region 0: Memory at <ignored> (32-bit, non-prefetchable)
         Bus: primary=00, secondary=20, subordinate=22, sec-latency=176
         I/O window 0: 00000000-00000003
         I/O window 1: 00000000-00000003
         BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+
         16-bit legacy interface ports at 0001
 00: 80 11 75 04 07 00 10 02 80 00 07 06 00 20 02 00
 10: 00 00 00 68 dc 00 00 02 00 20 22 b0 00 00 00 00
 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 80 07
                                         ^^
 40: 54 11 0a 03 01 00 00 00 00 00 00 00 00 00 00 00
 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Question i82365 and wvlan_cs with 2.4.0-test5?

Date: 2000, Jul 29
From: Peter pfolk

I must not understand something. When I try to build either 3.1.19 or the .20 beta against kernel 2.4.0-test5, it doesn't build most of the stuff. In particular, it doesn't build either of the i82365.o or wvlan_cs.o modules, or anything in the modules or wireless subdirectories.

In kernel test5's drivers/pcmcia/Config.in, the configure option for i82365 support is commented out so I can't enable it in that location, but if I do I get no problems. Similarly, I can manually build the wvlan_cs module. In- stalling it causes no problems that I can see, and this is not listed as a bug as far as I can tell...

So is this a relic, or am I doing something wrong, or does it only seem like it's working fine, or what?

Pete

None If you want those modules, then turn off PCMCIA in your kernel

Re: Question i82365 and wvlan_cs with 2.4.0-test5? (Peter)
Date: 2000, Jul 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

In general, you either build the kernel-tree PCMCIA support, or you
build the standalone PCMCIA modules.  The Configure script checks to
see if CONFIG_PCMCIA is turned on in your kernel; if it is, then it
will only build cardmgr and the other user tools.  If CONFIG_PCMCIA is
off, then it will build all the kernel modules.

The reason for this is that there may be version skew between the
PCMCIA stuff in the kernel tree, and what is in the separate package.
If the kernel PCMCIA is on, then cardmgr etc are built against the
kernel PCMCIA headers, not the headers included in the PCMCIA
package.  Building the modules, when you've also built stuff into the
kernel, is messy: we don't want to build stuff that conflicts.

-- Dave

Ok Cool, perhaps that could be made more clear in the HOWTO?

Re: None If you want those modules, then turn off PCMCIA in your kernel (David Hinds)
Date: 2000, Jul 30
From: Peter pfolk

I know you say it for the individual devices and device types, but maybe before that section, make it clear that you can only use ONE of the two for the modules.

Pete

Question Why ?

Re: Question i82365 and wvlan_cs with 2.4.0-test5? (Peter)
Date: 2000, Aug 16
From: Serge Wagener Foxi

I have the same problem with test6 and 3.1.19. The i82365 doesn't show up in modules directory.

I now know why (reading this thread) but can someone tell me WHY the i82365 is turned off in test6 kernel tree ??

Is it safe to uncomment it in Config.in or is it safer to disable pcmcia support and completely use the pcmcia-cs package ?

Serge

None You can't just uncomment the config option

Re: Question Why ? (Serge Wagener)
Date: 2000, Aug 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You cannot use the i82365 module in test6 and later, because the way
the pcmcia_core module interacts with socket drivers was changed
drastically, and the i82365 and tcic modules were not fixed to use the
new system.  Only the yenta driver was updated.  I didn't make these
changes.

-- Dave

Question IRQ problem with Ricoh R5C476II PCI-Cardbus bridge

Date: 2000, Aug 06
From: Leonard Ye leonardye

I tried to make a wireless LAN card working on my Desktop. There are two adaptors: ISA-PCMCIA adaptor and PCI-PCMCIA adaptor (Ricoh R5C476II PCI-Cardbus bridge). RedHat 6.2 - pcmcia-cs-3.1.19 are used.

If the wireless card is in the ISA adaptor slot, everything works fine. But when this card is inserted into PCI adaptor, it can be configured successfully, but does not receive any packets afterwards. After reading the PCMCIA-HOWTO, I tried to set the irq_mode in PCIC_OPTS. But done of them sees to be working:

logging for irq_mode = 0:
/******************************************/
Aug  6 19:38:42 localhost kernel: Linux PCMCIA Card Services 3.1.19 
Aug  6 19:38:42 localhost kernel:   kernel build: 2.2.14-5.0 #5 Sat Jun 24 14:01:44 SGT 2000 
Aug  6 19:38:42 localhost kernel:   options:  [pci] [cardbus] [apm] [pnp] 
Aug  6 19:38:42 localhost kernel: PCI routing table version 1.0 at 0xf0c70 
Aug  6 19:38:42 localhost kernel: PnP: PNP BIOS installation structure at 0xc00fc130 
Aug  6 19:38:42 localhost kernel: PnP: PNP BIOS version 1.0, entry at f0000:c160, dseg at f0000 
Aug  6 19:38:42 localhost kernel: Intel PCIC probe:  
Aug  6 19:38:42 localhost kernel:   Ricoh RL5C476 rev 80 PCI-to-CardBus at slot 00:0c, mem 0x68000000 
Aug  6 19:38:42 localhost kernel:     host opts [0]: [pci only] [io 3/6/1] [mem 3/6/1] [pci irq 11] [lat 32/176] [bus 32/34] 
Aug  6 19:38:42 localhost kernel:     host opts [1]: [pci only] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 32/176] [bus 35/37] 
Aug  6 19:38:42 localhost kernel:     *NO* card interrupts, polling interval = 1000 ms 
/******************************************/

in this case, the wireless LAN card driver cannot find any IRQ available.

logging for irq_mode = 1
/******************************************/
Aug  6 19:40:20 localhost kernel: Linux PCMCIA Card Services 3.1.19 
Aug  6 19:40:20 localhost kernel:   kernel build: 2.2.14-5.0 #5 Sat Jun 24 14:01:44 SGT 2000 
Aug  6 19:40:20 localhost kernel:   options:  [pci] [cardbus] [apm] [pnp] 
Aug  6 19:40:20 localhost kernel: PCI routing table version 1.0 at 0xf0c70 
Aug  6 19:40:20 localhost kernel: PnP: PNP BIOS installation structure at 0xc00fc130 
Aug  6 19:40:20 localhost kernel: PnP: PNP BIOS version 1.0, entry at f0000:c160, dseg at f0000 
Aug  6 19:40:20 localhost kernel: Intel PCIC probe:  
Aug  6 19:40:20 localhost kernel:   Ricoh RL5C476 rev 80 PCI-to-CardBus at slot 00:0c, mem 0x68000000 
Aug  6 19:40:20 localhost kernel:     host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 11] [lat 32/176] [bus 32/34] 
Aug  6 19:40:20 localhost kernel:     host opts [1]: [isa irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 32/176] [bus 35/37] 
Aug  6 19:40:20 localhost kernel:     ISA irqs (default) = 5,9 polling interval = 1000 ms 
/******************************************/

in this case, the card can be successfully configured, and IRQ 5 is registered for use. But after that, no interrupt can be received by the wireless card.

logging for irq_mode=2
/******************************************/
Aug  6 19:43:33 localhost kernel:   Ricoh RL5C476 rev 80 PCI-to-CardBus at slot 00:0c, mem 0x68000000 
Aug  6 19:43:33 localhost kernel:     host opts [0]: [serial irq] [io 3/6/1] [mem 3/6/1] [pci irq 11] [lat 32/176] [bus 32/34] 
Aug  6 19:43:33 localhost kernel:     host opts [1]: [serial irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 32/176] [bus 35/37] 
Aug  6 19:43:33 localhost kernel:     PCI irq 11 seems to be wedged! 
Aug  6 19:43:33 localhost kernel:     ISA irqs (<6>    PCI irq 9 seems to be wedged! 
Aug  6 19:43:33 localhost kernel: default) = 5,9 polling interval = 1000 ms 
/******************************************/

the behaviour of the wireless card is the same as that of irq_mode=1.

I have been working on this problem for 1 week with heavy casualities of my hair. Any hints or advices will be really appreciated.

Regards,
Leonard Ye

Question wvlan_cs and 2.4.0-test5

Date: 2000, Aug 07
From: Jon Lasser jonlasser

OK, I've built the modules correctly and can get the wvlan_cs module loaded under 2.4.0test5 and the latest pcmcia-cs 3.1.20 beta (27 July, if I'm correct).

I had everything working with 2.3.99pre6 or something like that, and 3.1.11 or thereabouts.

However, I'm not able to actually connect to anything with my new kernel and pcmcia-cs package: I've tried both managed (my usual mode) and ad-hoc, and in either case the card looks like it's connected but:

   1. The access point addr is 44:44:44:44...
   2. It's picked some random encryption key (I don't use the
      encryption)
   3. DHCP doesn't find any address (multiple environments
      where it used to work)
   4. After configuring wvlan0 manually, I can't see anyone on
      a broadcast ping. Even after playing around with routing
      some.

Admittedly, I don't think I've rebuild wireless-tools v20, so it's possible that the problem lies elsewhere. The newer kernel performs much more happily with my system in other respects, so I'd like to get it working with this.

And the killer is that now it doesn't work when I boot my older kernel, either. Fails the same way, too. So presumably the change is in the utils rather than in the module (or diffs between the two versions cause the old module to fail with the new pcmcia-cs utils with the same symptoms as the new version does...)

Tnx for any help,
Jon

Question Unresolved symbols in pcmcia-cs-3.1.19

Date: 2000, Aug 07
From: Wenhua Xing Eric

No problem while building 3.1.19, but when I load the module pcnet_cs, there shows "unresolved symbol" messages for below function call,

ei_open
ethdev_init
register_pccard_driver
unregister_pccard_driver
ei_interrupt
NS8390_init

I tried it in linux kernel 2.2.15 and 2.2.36.

And I have seen "CFLAGS" solution, the same? How to do?

Any idea? Thanks!

None Don't load PCMCIA modules by hand

Re: Question Unresolved symbols in pcmcia-cs-3.1.19 (Wenhua Xing)
Date: 2000, Aug 07
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> No problem while building 3.1.19, but when I load the module
> pcnet_cs, there shows "unresolved symbol" messages for below function
> call, 

That looks normal to me; the pcnet_cs module depends on the 8390
module, which has to be loaded first.  And why are you trying to load
this module by hand, anyway?

(loading PCMCIA modules by hand is almost never productive, so it is
almost certainly true that whatever you are trying to do is wrong)

-- Dave

More PCMCIA under pci-pcmcia bridge

Re: None Don't load PCMCIA modules by hand (David Hinds)
Date: 2000, Aug 08
From: Wenhua Xing Eric

I get a board with CL-PD6729 as controler to control two pcmcia cards, one sandisk memory card, one linksys pcm100 NIC. 

And the trouble is there are two other pci NICs in the same pci-bus with CL-PD6729. 

That is to say, there are three pci-devicees under the same pci-bridge, and one device is a pci-pcmcia-bridge.

Now I want to make them work together.

And the basic questions are: 
1. Unknow Memory Size;
2. Delay ether0 (conflict?)

Thanks!

Question Any conflict on this board?

Re: None Don't load PCMCIA modules by hand (David Hinds)
Date: 2000, Aug 08
From: Wenhua Xing Eric

I mention detailed info in "PCMCIA under pci-pcmcia bridge", are there any conflict on this board? But they work well in Win98.

Thanks!

Question Unknown memory size

Date: 2000, Aug 07
From: Wenhua Xing Eric

I use a 32MB flash memory card from SanDisk. Initialization seems OK! But I couldn't operate this card.
When I check /var/log/messages, there show some error messages as below,

cardmgr[345]: initializing socket 0
kernel: memory_cs:mem0:anonymous;unknown size
cardmgr[345]: socket 0: anonymous memory

How to fix it?

Thanks!

Question Sycard PCChost 1200 supported?

Date: 2000, Aug 09
From: Paul Graham grahamp

I have a Sycard PCChost 1200 and a system running RedHat 6.2 with the "stock" version of the kernel (2.2.14-5.0) and pcmcia-cs (version 3.1.8). Does this (or any) version of pcmcia-cs work with the PCChost 1200 board? If so, are there any special settings that are required to get the board working? I noticed an earlier comment on this list that seemed to indicate that some people have worked with the board under Linux.

 Thanks,

 Paul
 ==================
 grahamp@ee.byu.edu

None Yes, but there is a trick

Re: Question Sycard PCChost 1200 supported? (Paul Graham)
Date: 2000, Aug 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You should specify:

  PCIC_OPTS="p2cclk=1"

in your startup options.  This will be mentioned in the HOWTO.

-- Dave

Question Trick for IRQ's on Sycard PCChost 1200??

Re: None Yes, but there is a trick (David Hinds)
Date: 2000, Aug 11
From: Paul Graham grahamp

Thanks for the configuration info--the PCChost 1200 is working well except for interrupts. Is there something additional I must do to get CardBus interrupts to work with the PCChost 1200? With the no irq_mode defined, /proc/interrupts claims that my CardBus device(s) have irqs 3 and 5, but I am not convinced that things are working properly since /proc/interrupts tells me that 0 interrupts have occurred when I know several should have taken place. Further, my diagnostic tests on the interrupts never receive their expected interrupts, timing out long after the interrupts should have occurred.

On boot, I get the following:

 Aug 10 15:03:52 shmack kernel: Linux PCMCIA Card Services 3.1.19 
 Aug 10 15:03:52 shmack kernel:   kernel build: 2.2.5-15 #1 Mon Apr 19 23:00:46 EDT 1999 
 Aug 10 15:03:52 shmack kernel:   options:  [pci] [cardbus] [apm] 
 Aug 10 15:03:52 shmack kernel: PCI routing table version 1.0 at 0xfdf30 
 Aug 10 15:03:52 shmack kernel:   00:0f.1 -> irq 9 
 Aug 10 15:03:52 shmack kernel: Intel PCIC probe:  
 Aug 10 15:03:52 shmack kernel:   TI 1220 rev 02 PCI-to-CardBus at slot 00:0f, mem 0x68000000 
 Aug 10 15:03:52 shmack kernel:     host opts [0]: [serial pci & irq] [no pci irq] [lat 168/176] [bus 32/34] 
 Aug 10 15:03:52 shmack kernel:     host opts [1]: [serial pci & irq] [pci irq 9] [lat 168/176] [bus 35/37] 
 Aug 10 15:03:52 shmack kernel:     ISA irqs (default) = 3,4,5,7,10,12 polling interval = 1000 ms 

I changed the irq_mode to 0,1,2,3 and no improvement, though, for mode 0, the controller could not assign any interrupts.

Before asking you, I asked Sycard about Linux support and here is something that may explain what needs to be done:

> 2.  What is required to enable the PCChost 1200 for Linux? 
> 
> The HOST1200.SYS driver is used to initialize the PCI1220 CardBus controller 
> for use with  
> Windows 9x. HOST1200.SYS also configures the programmable I/O pins for use 
> with the  
> indicator LEDs, interrupt type and power switch chip (TPS2206). HOST1200.SYS 
> will do  
> this initialization on boot-up. HOST1200.SYS performs the following:   
> Enable PCIC Legacy address at 3E0H by setting PCI configuration space 44H = 
> 03E0 and 46H = 0000H.  
> Enable I/O and memory accesses by setting bits 0 and 1 in the PCI Command 
> register at offset 04H in PCI Configuration space.  
> Enable clock to external voltage switch chip (TPS2206) by setting bit 27 in 
> the System Control register at PCI configuration offset 80H.  
> Configure multifunction pins for PCChost 1200 by setting the multifunction 
> routing register at PCI configuration space offset 8CH to 1DC7H and offset 
> 8EH to 0007H.  
> Enable ExCA legacy interrupts by setting bit 7 in the bridge control register 
> at PCI configuration space offset 3EH.  
> A similar initialization routine will be required for Linux.  Let know if you 
> have any questions or problems. 

Unfortunately, I don't know the anatomy of the i82365.c module or any of the pcmcia-cs code well enough to implement any of these configuration steps without some hints. If these initialization steps aren't being taken care of by version 3.1.19, how might I add them (and where)?

Thanks,

 Paul
 ==================
 grahamp@ee.byu.edu

Question Compilation doesn't create a /pcmcia directory, but no errors were reported

Date: 2000, Aug 09
From: Pierre Bedel pbedel

I tried to compile pcmcia-cs-3.1.8 on my RH 6.2 laptop : everything seems to run fine, however after installation my /lib/modules/2.2.14-5.0/ directory doesn't contain /pcmcia. Did I miss something ?

None Well, they are going somewhere

Re: Question Compilation doesn't create a /pcmcia directory, but no errors were reported (Pierre Bedel)
Date: 2000, Aug 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Look at the definition of MODDIR in config.out; that is where your
modules were installed.

Or redo "make install" and see where it is putting things.

-- Dave

Sad It must be some obvious mistake but I can't figure it out

Re: None Well, they are going somewhere (David Hinds)
Date: 2000, Aug 10
From: Pierre Bedel pbedel

I am now pretty sure i did a stupid mistake somewhere, is it due to the "CONFIG_PCMCIA is not defined" line ?

Here is my config.out file, thanks for helping. Pierre.

#
# Automatically generated by 'make config' -- don't edit!
#
LINUX="/usr/src/linux" PREFIX="/var/tmp/kernel-2.2.14-5.0-root" MODDIR="/lib/modules/2.2.14-5.0" KFLAGS="" UFLAGS="" PCDEBUG="" USE_APM=y
# UNSAFE_TOOLS is not defined
# CONFIG_CARDBUS is not defined
# CONFIG_PNP_BIOS is not defined
CONF_SRC=1 # Options from current kernel CHECK="/proc/version" CKSUM="2576201644 149"
# CONFIG_PCMCIA is not defined
# CONFIG_SMP is not defined
CONFIG_PCI=y CONFIG_PCI_QUIRKS=y CONFIG_APM=y # CONFIG_SCSI is not defined CONFIG_INET=y
# CONFIG_NET_RADIO is not defined
# CONFIG_TR is not defined
# CONFIG_NET_FASTROUTE is not defined
CONFIG_MODVERSIONS=y CONFIG_PROC_FS=y MEMMAX=1GB CONFIG_1GB=y
# CONFIG_2GB is not defined
# CONFIG_3GB is not defined
CONFIG_ISA=y UTS_RELEASE="2.2.14-5.0" UTS_VERSION="#1 lun aoû 7 23:31:54 CEST 2000" LINUX_VERSION_CODE=131598 NEW_QLOGIC=y HAS_PROC_BUS=y SYSV_INIT=y RC_DIR="/etc/rc.d" INSTALL_DEPMOD=y # HAS_FORMS is not defined

None PREFIX setting

Re: Sad It must be some obvious mistake but I can't figure it out (Pierre Bedel)
Date: 2000, Aug 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Thu, Aug 10, 2000 at 05:14:52AM -0700, Pierre Bedel wrote:
> 
> LINUX="/usr/src/linux" PREFIX="/var/tmp/kernel-2.2.14-5.0-root"

This was your problem: everything was being installed under
/var/tmp/kernel-2.2.14-5.0-root.

-- Dave

Ok Problem solved

Re: None Well, they are going somewhere (David Hinds)
Date: 2000, Aug 10
From: Pierre Bedel pbedel

I downloaded the 3.1.19 modules, they installed perfectly and everything is now working smoothly. Nice work David.

Question PCMCIA won't start (Kernel 2.4.0-test5, pcmcia-cs-3.1.20)

Date: 2000, Aug 10
From: Talei McLeod talei

Hi,

I am having terrible troubles getting the PCMCIA package to work on my PC.

I have kernel 2.4.0-test5 installed. I originally compiled this with all of the PCMCIA options, but after reading a previous message, I have since compiled the kernel with no PCMCIA options.

Instead I have compiled the pcmcia-cs-3.1.20 package.

I should point out that I am using a PCMCIA internal ISA card reader for a desktop with a VIA VT83C479 controller chip. This should be OK.

Also, isapnp detects this PCMCIA reader.

On startup, these are the messages that are written to the log :

Aug 10 15:02:02 sydhcp131216 kernel: isapnp: Scanning for Pnp cards... 
Aug 10 15:02:02 sydhcp131216 kernel: isapnp: Card 'VIA PCMCIA CARD' 
Aug 10 15:02:02 sydhcp131216 kernel: isapnp: 1 Plug & Play card detected total 

Aug 10 15:02:03 sydhcp131216 pcmcia: Starting PCMCIA services:
Aug 10 15:02:03 sydhcp131216 kernel: Linux PCMCIA Card Services 3.1.20 
Aug 10 15:02:03 sydhcp131216 kernel:   kernel build: 2.4.0-test5 #16 SMP Thu Aug 10 12:59:18 EST 2000 
Aug 10 15:02:03 sydhcp131216 kernel:   options:  [pci] [cardbus] [apm] 
Aug 10 15:02:03 sydhcp131216 kernel: Intel PCIC probe: not found. 
Aug 10 15:02:03 sydhcp131216 pcmcia:  modules
Aug 10 15:02:03 sydhcp131216 kernel: ds: no socket drivers loaded! 
Aug 10 15:02:03 sydhcp131216 pcmcia: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
Aug 10 15:02:03 sydhcp131216 pcmcia: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
Aug 10 15:02:03 sydhcp131216 cardmgr[472]: starting, version is 3.1.20
Aug 10 15:02:03 sydhcp131216 pcmcia:  cardmgr.
Aug 10 15:02:03 sydhcp131216 pcmcia: /lib/modules/2.4.0-test5/pcmcia/i82365.o: init_module: No such device
Aug 10 15:02:03 sydhcp131216 pcmcia: /lib/modules/2.4.0-test5/pcmcia/ds.o: init_module: Operation not permitted
Aug 10 15:02:03 sydhcp131216 rc: Starting pcmcia succeeded
Aug 10 15:02:04 sydhcp131216 cardmgr[472]: no pcmcia driver in /proc/devices
Aug 10 15:02:04 sydhcp131216 cardmgr[472]: exiting

If I run "pcmcia status" this states that the cardmgr is not running.

If i try "pcmcia start" here is the error mesg :

Starting PCMCIA services: modulesinsmod: a module named pcmcia_core already exists
/lib/modules/2.4.0-test5/pcmcia/i82365.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.0-test5/pcmcia/ds.o: init_module: Operation not permitted
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
 cardmgr.       

If anyone can offer any suggestions it would be much appreciated.

Thanks in advance, Talei.

None I don't think the PnP card has been activated

Re: Question PCMCIA won't start (Kernel 2.4.0-test5, pcmcia-cs-3.1.20) (Talei McLeod)
Date: 2000, Aug 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> Also, isapnp detects this PCMCIA reader.

I'm not really familiar with how the kernel isapnp subsystem works.  I
think that the fact the card was detected does not mean that it was
turned on.

Use the pnpdump and isapnp utilities to configure the card, then start
PCMCIA after that, and you should have better luck.

I should figure out how to hook the i82365 driver into the kernel
isapnp interface, but at the moment, they don't talk to each other.

-- Dave

Question Now all my cards are being detected as "Anonymous Memory"

Re: None I don't think the PnP card has been activated (David Hinds)
Date: 2000, Aug 10
From: Talei McLeod talei

Thanks for your help.

I now have the problem that all my pcmcia cards are being detected as Anonymous Memory.

I have tried :

Netcomm Card Modem 56 Compaq WL100 (WLAN card - I have installed the driver for this including config files) Nokia Card Phone (2 different versions).

Is this a pnp issue again ??

Thanks very much, Talei.

None This is not a PnP issue

Re: Question Now all my cards are being detected as "Anonymous Memory" (Talei McLeod)
Date: 2000, Aug 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It could be a memory window setup issue (which is discussed in the
HOWTO).  I would want to see your system log messages.

-- Dave

More Here are my system log messages when I insert the WLAN card.

Re: None This is not a PnP issue (David Hinds)
Date: 2000, Aug 10
From: Talei McLeod talei

Aug 11 09:53:24 sydhcp131216 cardmgr[478]: shutting down socket 0
Aug 11 09:53:24 sydhcp131216 cardmgr[478]: executing: './memory stop mem0'
Aug 11 09:53:24 sydhcp131216 cardmgr[478]: unbind MTD 'sram_mtd' from socket 0 failed: No such device
Aug 11 09:53:24 sydhcp131216 cardmgr[478]: executing: 'modprobe -r memory_cs'
Aug 11 09:53:24 sydhcp131216 cardmgr[478]: executing: 'modprobe -r sram_mtd'
Aug 11 09:53:26 sydhcp131216 cardmgr[478]: initializing socket 0
Aug 11 09:53:26 sydhcp131216 cardmgr[478]: socket 0: Anonymous Memory
Aug 11 09:53:26 sydhcp131216 cardmgr[478]:   Attribute memory region at 0x0: Generic or SRAM
Aug 11 09:53:26 sydhcp131216 cardmgr[478]: bind MTD 'sram_mtd' to socket 0 failed: Device or resource busy
Aug 11 09:53:26 sydhcp131216 cardmgr[478]: executing: 'modprobe memory_cs'
Aug 11 09:53:26 sydhcp131216 cardmgr[478]: executing: './memory start mem0'
Aug 11 09:53:26 sydhcp131216 kernel: memory_cs: mem0: attribute 1 kb 

Once again, thanks for your help.

Talei.

More Some more detailed information about above problem.

Re: Question Now all my cards are being detected as "Anonymous Memory" (Talei McLeod)
Date: 2000, Aug 10
From: Talei McLeod talei

I am getting the messages about "Anonymous Memory" from the cardinfo utility and from the system log. It also appears in /var/lib/pcmcia/stab

However, When I run "cardctl ident" I appear to get the correct card information.

Thanks, Talei.

More I now have 1 card working. But not Compaq WLAN card.

Re: Question Now all my cards are being detected as "Anonymous Memory" (Talei McLeod)
Date: 2000, Aug 11
From: Talei McLeod talei

I have found one card that is correctly identified. (However I don't have a linux driver for this card so I don't know whether it would have been 100% successful).

I still cannot get my WLAN card to work. It is a Compaq WL100 card.

When the card is inserted there is a low beep followed by a high beep.

I have tried adjusting the memory ranges as suggested in the HOWTO but to no luck. (I have only succeeded in creating configurations which don't recognise the card that was being recognised).

I have also tried excluding different irq's.

I have these details about the card and reader from Windows :

PC Card Reader :

Memory range : 0c002000-0c002fff

WLAN Card :

IRQ : 10 I/O : 1800-1835

Any suggestions on how to get this card going would be much appreciated.

Thanks, Talei.

Question Problems with PCI to PCMCIA Adpater

Date: 2000, Aug 10
From: Nicolas Malsch nick

Question Something broke after test6-pre7 ( same for 3.1.18-20 )

Date: 2000, Aug 11
From: Philip Langdale philipl

Hi,

I've been tracking the 2.4.0 development releases very closely and from test6-pre7 onward ( now at test6 ) something changed in the kernel which has broken the core pcmcia drivers. I've tried 3.1.18, .19 and the 7/8 .20 prerelease. All with the same results. The pcmcia_core driver reports a failure to detect the i82365 chip which it could always do before. Then, of course the i82365 driver can't load because it can't find the device to drive.

The error message is:

Intel PCIC Probe: Bridge register mapping failed: Check cb_mem_base setting.

But, of course, cb_mem_base isn't even compiled in for this kernel ( and compiling it back in didn't help ). I'm afraid I'm not knowledgable enough about these things to track down what's happened.

Hopefully you can shed some light on this.

thanks,

--phil

None I don't know where the problem is

Re: Question Something broke after test6-pre7 ( same for 3.1.18-20 ) (Philip Langdale)
Date: 2000, Aug 11
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I saw a report of this on linux-kernel.  It is quite strange: it would
appear to mean that the PCI layer is not assigning an address to the
CardBus bridge when the i82365 module calls pci_enable_device().  As
you figured out, the mention of cb_mem_base doesn't apply for 2.4
kernels.

-- Dave

None Looks like it has been sorted out

Re: None I don't know where the problem is (David Hinds)
Date: 2000, Aug 11
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Linus posted a PCI patch on linux-kernel late this morning.

-- Dave

None Re: Looks like it has been sorted out

Re: None Looks like it has been sorted out (David Hinds)
Date: 2000, Aug 12
From: Langdale, Philip philipl

David Hinds wrote:

> Linus posted a PCI patch on linux-kernel late this morning.
>
> -- Dave

Yes, this has sorted it out. ( I used the test7-pre1 diff which
includes this patch )

--phil

Sad Hang when inserting card on Sony VAIO Z505S

Date: 2000, Aug 13
From: Liam Quinn LiamQ

I am having the problem described (by someone else) at <http://www.uglx.org/sony-hang.html>: my Sony VAIO Z505S hangs when inserting a PCMCIA card (specifically for a CD-ROM drive in my case). There are no beeps prior to the hang.

I am using pcmcia-cs-3.1.14 as shipped with Linux-Mandrake 7.1's updated 2.2.16 kernel.

I've tried all sorts of PCIC_OPTS, including the suggested fix on the uglx.org site and setting pci_irq_list=9, as well as narrowing the memory (as suggested by the PCMCIA-HOWTO in Section 3.5) to what Windows uses, but I always get the hang.

I can't find anything in my system logs immediately before the hang occurs. Here's what is logged on boot-up (with no card inserted):

Aug 11 01:31:01 localhost pcmcia: Starting PCMCIA services:
Aug 11 01:31:01 localhost pcmcia:  modules
Aug 11 01:31:01 localhost kernel: Linux PCMCIA Card Services 3.1.14 
Aug 11 01:31:01 localhost kernel:   kernel build: 2.2.15-4mdk #1 Wed May 10 15:31:30 CEST 2000 
Aug 11 01:31:01 localhost kernel:   options:  [pci] [cardbus] [apm] 
Aug 11 01:31:01 localhost kernel: PCI routing table version 1.0 at 0xfdf50 
Aug 11 01:31:01 localhost kernel:   00:0a.0 -> irq 9 
Aug 11 01:31:02 localhost kernel: Intel PCIC probe:  
Aug 11 01:31:02 localhost kernel:   Ricoh RL5C475 rev 00 PCI-to-CardBus at slot 00:0a, mem 0x68000000 
Aug 11 01:31:02 localhost kernel:     host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 32/34] 
Aug 11 01:31:02 localhost kernel:     PCI irq 9 test failed 
Aug 11 01:31:02 localhost kernel:     ISA irqs (default) = 3,4,5,7,10,11,12,15 polling interval = 1000 ms 
Aug 11 01:31:02 localhost pcmcia:  cardmgr.
Aug 11 01:31:02 localhost rc: Starting pcmcia succeeded
Aug 11 01:31:02 localhost cardmgr[987]: starting, version is 3.1.14
Aug 11 01:31:02 localhost cardmgr[987]: watching 1 sockets
Aug 11 01:31:02 localhost kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff 
Aug 11 01:31:02 localhost kernel: cs: IO port probe 0x0800-0x08ff: clean. 
Aug 11 01:31:02 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x140-0x147 0x170-0x177 0x370-0x37f 0x4d0-0x4d7 
Aug 11 01:31:02 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean. 

None A driver upgrade may help

Re: Sad Hang when inserting card on Sony VAIO Z505S (Liam Quinn)
Date: 2000, Aug 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I think this was fixed in 3.1.15.  The problem is the "PCI irq 9 test
failed".

-- Dave

Ok Thanks, works great with pcmcia-cs-3.1.19

Re: None A driver upgrade may help (David Hinds)
Date: 2000, Aug 14
From: Liam Quinn LiamQ

Upgrading to pcmcia-cs-3.1.19 fixed the problem. Thank you very much for your help!

Sad Sony VAIO F-409: Bridge register mapping failed: check cb_mem_base

Date: 2000, Aug 16
From: Serge Wagener Foxi

I had the Webgear Aviator 2.4 working on my Sony VAIO F-409 laptop. (uses the Ricoh pcmcia bridge). I used kernel 2.4.0-test2 with build-in kernel pcmcia support and pcmcia-cs utils (don't remember version)

I upgrade to 2.4.0-test6 and pcmcia-2.3.20 (11 jul.)

When starting PCMCIA it says:

Bridge register mapping failed: check cb_mem_base setting

I use the i82365 PCIC ...

Any hints ?

Thanks,

Serge

None This is a kernel PCI bug

Re: Sad Sony VAIO F-409: Bridge register mapping failed: check cb_mem_base (Serge Wagener)
Date: 2000, Aug 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Get a newer kernel and the problem will go away.

-- Dave

Ok New kernel really solved the problem

Re: None This is a kernel PCI bug (David Hinds)
Date: 2000, Aug 17
From: Serge Wagener Foxi

Thanks !

I now have test7-pre4 with 2.1.20 11 Jul and everything works fine ! (except that it complains that the card uses a strange interrupt 7 or something like that, but as long as it works ... ;-) )

Thanks again,

Serge

Question What is the deal with pcmcia and 2.4 kernels

Date: 2000, Aug 20
From: Henrik Nordstrom hno

What is the deal with PCMCIA modules in the 2.4 kernels? Is the kernel parts of pcmcia-cs being integrated into the kernel tree finally?

Why I am asking is because I noticed there is no tulip_cb driver in the kernel tree, and pcmcia-cs does not build the drivers at all when the kernel is configured with PCMCIA support.. also the interface drivers (such as i82365) is not selectable in the 2.4.0-test6 configuration menus and won't be build unless manually overridden..

Very confusing.

None Here is a draft of a new README about 2.4

Re: Question What is the deal with pcmcia and 2.4 kernels (Henrik Nordstrom)
Date: 2000, Aug 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

  Notes about PCMCIA in the 2.4 kernel

PCMCIA kernel driver support is now included in the 2.4 linux kernel
tree.  While it shares most of the same code with the standalone
PCMCIA driver package, there are some important differences.  The
kernel PCMCIA support is also still evolving.  This README is up to
date as of the 2.4test7-pre* kernels.

The kernel PCMCIA support does not eliminate the need to install the
pcmcia-cs package.  Kernel PCMCIA still requires the same user tools
(cardmgr, cardctl, /etc/pcmcia/* files).

To use the kernel PCMCIA drivers, configure the kernel with
CONFIG_PCMCIA ("CardBus support") enabled.  In this case, "CardBus"
really refers to the type of host bridge supported: both 16-bit and
CardBus card support is included.  The drivers can either be built
into the kernel or built as modules.  For now, only PCI-to-CardBus
bridges are supported, so there are no options for choosing bridge
drivers.  PCMCIA client driver options are listed in their regular
driver categories; thus, PCMCIA network drivers are in a submenu of
network drivers, and PCMCIA serial drivers are in a submenu of
character drivers.

The CardBus socket driver in the 2.4 tree is the "yenta_socket"
driver.  In your PCMCIA startup options, this driver should be
specified in place of the old i82365 driver.

When compiling the standalone PCMCIA package, the Configure script
decides whether or not to build any kernel modules by looking at the
value of the CONFIG_PCMCIA option.  If CONFIG_PCMCIA is enabled, then
no kernel components are built.  If CONFIG_PCMCIA is disabled, then
all the modules will be built and installed.  It is safe to compile
the user tools (cardmgr, cardctl, etc) in a PCMCIA package whose
version number differs from the PCMCIA version number in the kernel
source tree.  The kernel PCMCIA header files take precedence over the
ones included in the PCMCIA package, if CONFIG_PCMCIA is enabled.

The following tables show the correspondence between PCMCIA client
driver names, and kernel configuration options.

Network drivers:

  3c589_cs     3Com 3c589                CONFIG_PCMCIA_3C589
  3c574_cs     3Com 3c574                CONFIG_PCMCIA_3C574
  fmvj18x_cs   Fujitsu FMV-J18x          CONFIG_PCMCIA_FMVJ18X
  pcnet_cs     NE2000 compatible         CONFIG_PCMCIA_PCNET
  nmclan_cs    New Media                 CONFIG_PCMCIA_NMCLAN
  smc91c92_cs  SMC 91Cxx                 CONFIG_PCMCIA_SMC91C92
  xirc2ps_cs   Xircom 16-bit             CONFIG_PCMCIA_XIRC2PS
  ibmtr_cs     IBM PCMCIA tokenring      CONFIG_PCMCIA_IBMTR
  ray_cs       Aviator/Raytheon 2.4MHz   CONFIG_PCMCIA_RAYCS
  netwave_cs   Xircom Netwave AirSurfer  CONFIG_PCMCIA_NETWAVE
  wavelan_cs   AT&T/Lucent Wavelan       CONFIG_PCMCIA_WAVELAN

Character drivers:

  serial_cs    PCMCIA serial device      CONFIG_PCMCIA_SERIAL_CS
  serial_cb    CardBus serial device     CONFIG_PCMCIA_SERIAL_CB

SCSI low-level drivers:

  aha152x_cs   Adaptec AHA152X           CONFIG_PCMCIA_AHA152X
  qlogic_cs    Qlogic                    CONFIG_PCMCIA_QLOGIC
  fdomain_cs   Future Domain             CONFIG_PCMCIA_FDOMAIN
  apa1480_cb   Adaptec APA1480 CardBus   CONFIG_PCMCIA_APA1480

The CardBus network drivers (3c575_cb, tulip_cb, epic_cb) have been
folded into the corresponding PCI drivers using the new hot plug PCI
interface.  The tulip_cb driver has been partially merged into the
tulip driver ('DECchip Tulip (dc21x4x)', CONFIG_TULIP).  Xircom
CardBus cards are supported by a separate driver ('Xircom Tulip-like
CardBus', CONFIG_PCMCIA_XIRTULIP).  The 3c575_cb driver is merged into
the 3c59x driver ('3C590/3c900 series (592/595/597) "Vortex/Boomerang"
support', CONFIG_VORTEX).  And the epic_cb driver has been folded into
the epic100 driver ('SMC EtherPower II', CONFIG_EPIC100).

Known problems and limitations:

o ISA-to-PCMCIA and PCI-to-PCMCIA bridges are not supported.  The
  bridge driver interface in 2.4 is significantly different, and the
  tcic and i82365 drivers have not been ported to the new interface.
o Some of the less popular client drivers, like the memory card
  drivers, have not been ported into the 2.4 driver tree yet.
o The yenta_socket driver does not have the /proc interface of the
  i82365 driver, so the dump_exca and dump_cardbus tools do not work.
  It actually has no debugging support at all.
o The kernel PCMCIA package cannot be configured to use PnP BIOS calls
  for resource management.  This will not be fixed, but this is rarely
  a serious issue.
o There is a somewhat serious API issue with the new "PCI hot plug"
  interface used by the new tulip and 3c59x drivers.  It is unable to
  pass device name information to cardmgr, so the PCMCIA configuration
  scripts don't work.  Fixing this properly is non-trivial, because
  the new API is not intended to be tightly linked to the PCMCIA card
  control interface at all.  A substitute for that interface, but for
  PCI hot plug, has not really been sketched out yet.

Answers to some common questions:

Q: Are these two versions of PCMCIA both going to continue with active
   development?
A: The way I see things now, the kernel PCMCIA subsystem will probably
   be too unstable for widespread deployment, at least in the early
   days of 2.4.  So the standalone package will probably be widely
   used for some time yet.  However, the kernel PCMCIA subsystem
   should eventually stabilize and be the focus of new development.
   So, I think development for the standalone kernel modules will
   shift away from adding functionality, towards mainly bug fixes.

Q: Which should I use / which is better?  The kernel PCMCIA, or the
   standalone PCMCIA?
A: It really depends.  The client drivers should generally behave the
   same.  Some of the internals of the kernel PCMCIA system are very
   different and less mature than the standalone drivers.  Some legacy
   hardware is currently only supported by the standalone drivers.  At
   this point, I'd recommend using the kernel drivers if you have a
   specific need or if you are interested in helping test and debug.
   If you mainly just want something that works, then the standalone
   subsystem is probably a better bet at the moment.

Q: What should I do as a driver developer?
A: Again it really depends.  I will probably be really picky about
   including significant new functionality in the standalone PCMCIA
   package; I expect that the kernel PCMCIA package will stabilize and
   take over perhaps in the 2.5 kernel timeframe.  It might make the
   most sense to develop contributed drivers for the standalone
   package first because it is a stable platform; and then port to
   2.4.

Q: I'm using the kernel PCMCIA subsystem but want to use a driver that
   isn't included in the kernel yet.  Why can't I compile that driver
   from the standalone PCMCIA package?
A: The Makefiles are set up to discourage this, mainly to prevent
   people from trying combinations that don't make sense.  Things in
   the "modules" directory of the standalone package will not work
   with the kernel PCMCIA subsystem.  However, you can build client
   drivers by doing a "make" in either the "clients" or "wireless"
   subdirectories.

Q: Who is maintaining the kernel PCMCIA subsystem?
A: I am not playing as central a role in maintaining the kernel
   modules as I have with the standalone package.  I have periodically
   updated some of the core modules and client drivers with fixes from
   the standalone package.  Linus Torvalds wrote the yenta_socket
   driver more or less from scratch and he has been maintaining that
   bit.  Jeff Garzik has been working on the hot plug PCI adaptations
   for the tulip_cb, 3c575_cb, and epic_cb drivers.

Question Misidentifying 'D-Link DFE-650' as 'KTI Ether-C16'

Date: 2000, Aug 22
From: William Crandall WilliamCrandall

Question Which driver for a KXL-810 external scsi cdrom?

Date: 2000, Aug 26
From: Tom Halladay Xeviousceo

I'm trying to install linux on a Z-Note Flex laptop as the only operating system, I'm using a panasonic KXL-810A cdrom, what driver am i supposed to specify as the scsi adapter in the scsi configuration? or am i doing it wrong altogether?

None Not sure if this installation method is supported

Re: Question Which driver for a KXL-810 external scsi cdrom? (Tom Halladay)
Date: 2000, Aug 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The installation method depends on what version of Linux you are
using.  Some Linux distributions do not support installation from
PCMCIA devices at all; others only support PCMCIA network installs.

I think, for Red Hat, if you are prompted for a driver name, then the
PCMCIA device probe has already failed, and you are stuck.  (PCMCIA
devices are always autodetected, and the correct driver is loaded for
you: you generally never explicitly specify that a particular driver
should be loaded)

-- Dave

None Tried Mandrake and Redhat

Re: None Not sure if this installation method is supported (David Hinds)
Date: 2000, Aug 28
From: Tom Halladay Xeviousceo

I've tried Mandrake and Redhat, Mandrake always asks which cdrom i want to use, and which scsi adapter. But when i Redhat and use Rawwrite to boot the pcmcia.img, it starts up, asks for driver disk, tells me it doesn't have any special device drivers loaded for my system, and if i would like to load additional ones now.(at this point, my external cdrom is actually being read) If i click Done, I get the blue "welcome to red hat linux, but there are no longer any windows or choices, (more cdrom reading) and eventually the cdrom dies, and i get a flashing prompt at the bottom of the screen. This is as far as i get, as it stays this way indefinately

Question "no valid ROM images found"?

Date: 2000, Sep 01
From: Darin Davis dadavis

I'm trying to get a "Xircom RealPort Cardbus Ethernet 10/100
RBE-100" to work on my IBM ThinkPad 600X.  I installed RedHat
6.0 and compiled my own 2.2.5-15 kernel.  I compiled and
installed pcmcia-cs-3.1.20.  But on bootup, I get the
message "no valid ROM images found".  I'm sure I've
missed something really obvious, but I'm coming up blank
finding an explanation of that message.

Below is the output of several commands that may be relevant.

Thanks for any assistance.
Darin

===== lsmod =====
Module                  Size  Used by
nls_iso8859-1           2020   1  (autoclean)
ds                      6120   2 
i82365                 21436   2 
pcmcia_core            44000   0  [ds i82365]

===== cardctl config =====
Socket 0:
  not configured
Socket 1:
  Vcc 3.3V  Vpp1 3.3V  Vpp2 3.3V
  interface type is "cardbus"
  function 0:

===== cardctl ident =====
Socket 0:
  no product info available
Socket 1:
  no product info available

===== /var/log/messages =====
Sep  1 11:24:20 kernel: Linux PCMCIA Card Services 3.1.20 
Sep  1 11:24:20 kernel:   kernel build: 2.2.5-15 #2 Thu Jul 6 19:30:05 PDT 2000 
Sep  1 11:24:20 kernel:   options:  [pci] [cardbus] [apm] 
Sep  1 11:24:20 kernel: PCI routing table version 1.0 at 0xf9d00 
Sep  1 11:24:20 kernel:   00:02.0 -> irq 11 
Sep  1 11:24:20 kernel:   00:02.1 -> irq 11 
Sep  1 11:24:19 pcmcia: Starting PCMCIA services:
Sep  1 11:24:20 kernel: Intel PCIC probe:  
Sep  1 11:24:20 kernel:   TI 1450 rev 03 PCI-to-CardBus at slot 00:02, mem 0x50103000 
Sep  1 11:24:20 kernel:     host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 168/176] [bus 2/4] 
Sep  1 11:24:20 kernel:     host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat 168/176] [bus 5/7] 
Sep  1 11:24:20 kernel:     ISA irqs (scanned) = 3,4,5,7,9,10 PCI status changes 
Sep  1 11:24:21 kernel: cs: cb_alloc(bus 5): vendor 0x115d, device 0x0003 
Sep  1 11:24:21 kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x15e8-0x15ef 
Sep  1 11:24:21 kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x3b8-0x3df 0x4d0-0x4d7 
Sep  1 11:24:21 kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Sep  1 11:24:21 kernel: cs: no valid ROM images found! 
Sep  1 11:24:20 pcmcia:  cardmgr.
Sep  1 11:24:04 depmod: /lib/modules/2.2.5-15/pcmcia/fdomain_cs.o: unresolved symbol(s) 
Sep  1 11:24:04 depmod: /lib/modules/2.2.5-15/pcmcia/apa1480_cb.o: unresolved symbol(s) 
Sep  1 11:24:04 depmod: /lib/modules/2.2.5-15/pcmcia/aha152x_cs.o: unresolved symbol(s) 
Sep  1 11:24:20 cardmgr[326]: starting, version is 3.1.20
Sep  1 11:24:21 cardmgr[326]: watching 2 sockets
Sep  1 11:24:21 cardmgr[326]: initializing socket 1
Sep  1 11:24:21 cardmgr[326]: unsupported card in socket 1
Sep  1 11:24:21 cardmgr[326]:   no product info available
Sep  1 11:24:21 cardmgr[326]:   PCI id: 0x115d, 0x0003

===== dmesg =====
Linux version 2.2.5-15 (root@localhost.localdomain) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release))
Linux PCMCIA Card Services 3.1.20
  kernel build: 2.2.5-15 #2 Thu Jul 6 19:30:05 PDT 2000
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xf9d00
  00:02.0 -> irq 11
  00:02.1 -> irq 11
Intel PCIC probe: 
  TI 1450 rev 03 PCI-to-CardBus at slot 00:02, mem 0x50103000
    host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 168/176] [bus 2/4]
    host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat 168/176] [bus 5/7]
    ISA irqs (scanned) = 3,4,5,7,9,10 PCI status changes
cs: cb_alloc(bus 5): vendor 0x115d, device 0x0003
cs: IO port probe 0x1000-0x17ff: excluding 0x15e8-0x15ef
cs: IO port probe 0x0100-0x04ff: excluding 0x3b8-0x3df 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
ROM image dump:
cs: no valid ROM images found!

None I think this is a memory window problem

Re: Question "no valid ROM images found"? (Darin Davis)
Date: 2000, Sep 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

In /etc/pcmcia/config.opts, try changing:

  include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff

to just:

  include memory 0x60000000-0x60ffffff

and see if that helps.  If not, try some other ranges like
0xe0000000-0xe0fffffff, or 0x40000000-0x40fffffff.

-- Dave

More You're a genius!

Re: None I think this is a memory window problem (David Hinds)
Date: 2000, Sep 01
From: Darin Davis dadavis

Dave,

Never in a million years would I have guessed that!
My config.opts file contained:

   include memory 0xc0000-0xfffff, memory 0xa0000000-0xa0ffffff

I changed it to:

   include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff

and the card now gets detected.

However, in order to successfully ping another
device on the network, I have to "ifconfig eth0 down"
(which deletes the default route)and "ifconfig eth0 up".
With this done, my machine can communicate.  Any ideas
on why I have to manually down/up the interface?

Something else that seems odd is that while the
label on the physical card itself says it's a RBE,
'cardctl ident' says:

Socket 0:
  no product info available
Socket 1:
  product info: "Xircom", "CardBus Ethernet II 10/100", "CBEII-10/100", "1.03"
  manfid: 0x0105, 0x0103
  function: 6 (network)

I thought CBE wasn't supported.  But, I'm not complaining!

Many thanks for your help.
Darin

None The latest beta might have some effect

Re: More You're a genius! (Darin Davis)
Date: 2000, Sep 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You can try the 01-Sep-00 beta on projects.sourceforge.net in
/pub/pcmcia-cs/NEW.  It has several Xircom CardBus driver fixes.

> I thought CBE wasn't supported.  But, I'm not complaining!

The CBE is not supported.  The CBE II is supported.

-- Dave
PCMCIA Installation and Configuration Issues


Add Message to: "PCMCIA Installation and Configuration Issues"

Members Subscribe Admin Mode Show Frames Help for HyperNews at pcmcia-cs.sourceforge.net 1.10