Hello Josep, hello Matt
Welcome in the team of the people who have some problems with PCMCIA and
Linux 64 bits :-)) !!!!
Well, as Matt wrote it, you can find in this mailing list some
informations that can help you, in particular
my two messages :
http://lists.suse.com/archive/suse-amd64/2005-Jan/0204.html
http://lists.suse.com/archive/suse-amd64/2005-Jan/0205.html
in which there are a solution. But I can explain how I could get my
cards working fine after several tests
with the help of Matt and David Hinds the "father" of the PCMCIA kit for
linux.
So my laptop : an Asus of the L5D series, the first one of Asus with
Athlon 64. It is built with nVidia
chipsets. On it : Win XP Pro SP2, SuSE AMD64 9.0 (kernel 2.4.21) and
SuSE AMD64 9.1 with kernel
(a 2.6.8-24.10 one) and PCMCIA package of the SuSE AMD64 9.2.
What are your PCMCIA cards you want to use ? My cards are a Com One
modem card (Platinium 56k),
a Netgear ethernet FA411 card and a Hayes modem card (Optima 288).
Accordind to "lspci -vv", hereafter the data about the PCMCIA port :
0000:02:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ab)
Subsystem: Asustek Computer, Inc.: Unknown device 1854
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
Reset- 16bInt-
PostWrite+
16-bit legacy interface ports at 0001
0000:02:01.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ab)
Subsystem: Asustek Computer, Inc.: Unknown device 1854
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
Reset- 16bInt+
PostWrite+
16-bit legacy interface ports at 0001
As you can see, it is different from your PCMCIA device ... but the
problem seems the same :-).
So with a full SuSE 9.2 AMD64, the basis is correct : kernel and PCMCIA
package. At first, verify that your card
is defined in the /etc/pcmcia/config file. If not, go to the next step,
we will see after.
Now, have a look on I/O windows and memory window above. These datas are
required in the config.opts file in
the /etc/pcmcia directory under this form :
# range of port addresses :
#####################
include port 0xb000-0xb7ff
include port 0xb800-0xbfff
include port 0xc000-0xc7ff
include port 0xc800-0xcfff
# range of memory addresses :
########################
include memory 0xf8a00000-0xfd1ff000
Take the min and max of the memory for defining one range and take all
the ranges of port. Accordind to your
"lspci -vv", it should give this :
# range of port addresses :
#####################
include port 0x3000-0x33ff
include port 0x3400-0x37ff
# range of memory addresses :
########################
include memory 0xd0200000-0xd03ff000
Copy the original config.opts and rename it, modify the config.opts by
suppressing all datas concerning port and memory
and add this above. Reboot your PC. Insert a card and see the results
with "dmesg" and tell us what you get. I think
you can see at this level an improvement :-). No ?? Then with
"/sbin/cardctl info", see the character strings after "PRODID_1"
and "PRODID_2". With this, make an entry in the /etc/pcmcia/config file.
If you don't know how to do, tell it us. If an
entry is already defined, forget this step. Go to the following. Now,
see what give /sbin/lsmod. Are there some
loaded modules such as "pcmcia_core", "yenta_socket", "ds" and the
module depending on the type of PCMCIA card
(for example : serial_cs if modem) ? If a modem card, see if you have in
/dev directory a symbolic link modem --> ttySYx where
x = 0, 1, 2, ... it depends. If yes, perharps the problem is solved. If
modem card, try "wvdial". If OK messages, it seems
good !!!
If wrong, don't worry, try this : with /sbin/lspci -vv, find the datas
about PCI bridge with secondary=02. In my cas, here
what I get :
0000:00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2)
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
Reset- FastB2B-
Take the min and max of the memory behind brigde and put them in the
config.opts file. Reboot your PC and see the
results. Verify all the above steps after boot. Better or not ? If not,
I thing that the solution should only come from ....
Windows XP !!! Sorry :-). This is the first time that Win XP can help
Linux !!!!! In my case, I took the datas given by
Win XP for PCMCIA port and used them as following in the config.opts file :
# range of port addresses :
#####################
include port 0xcc00-0xccff
include port 0xd000-0xd0ff
include port 0xd400-0xd4ff
include port 0xdc00-0xdcff
# range of memory addresses :
########################
include memory 0xfa200000-0xfeafcfff
As you can see, there is a significant differente between my previous
and actual config.opts files. With such a file,
under SuSE 9.0 and SuSE 9.1, I can use my Com One modem card (not the
Hayes and I can't explain why) and
the FA411 card.
So, if Win XP is not installed on your laptop, well try do it in order
to get the right date for PCMCIA port. If
you can try a dual installation, Win XP and SuSE 9.2, the boot being
managed by Win XP (lilo for linux on the
boot partition). Perhaps with Grub.
Well, it's up to you : try and tell us what you get.
Regards
Pascal
=============================================
Message-Id:
Date: Tue, 08 Feb 2005 22:01:35 +0100
From: "jm macip"
Subject: [suse-amd64] PCMCIA
I recentlly installed suse 9.2 pro 64 on my Acer Aspire 1513lmi laptop
and I'm unable to get any pcmcia card working, it always says memory_cs
not found.
Any help will be apreciated.
Thanks in advance.
Josep Maria Macip