LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   PCMCIA not detected after compile (https://www.linuxquestions.org/questions/slackware-14/pcmcia-not-detected-after-compile-359393/)

adds2one 09-02-2005 01:51 AM

PCMCIA not detected after compile
 
I have compiled my kernel(2.6.13) several times but I can't seem to get my PCMCIA card to be detected. With the 2.4.x kernel that came with Slackware 10.1 my card is found during bootup and it gets powered.(a little blue light lights up on my card)

This is what I read when 2.6.13 boots up:

Probing for PCIC: edit /et/rd.d/rc.pcmcia
no pcmcia driver in proc/devices
Activating Hardware Detection: etc/rc.d/rc.hotplug start

Anyone know what setting I may be missing in my kernel configuration? Or is it something else?

crazytigger 09-03-2005 12:25 AM

Ive been doing a bit of reading about this.. and basically i read this recently which may help:

Make sure ou have the pcmcia package (slakware/all/pcmcia.tgz) installed Upon installation the pcmcia package will create an rc.pcmcia file in /etc/rc.d and an /etc/pcmcia directory, and will install drivers to /lib/modules/<kernel version>/pcmcia.

So when you compile a new kernel version you'll have to recompile pcmcia-cs to get the driver updated..

It may just be a case of copying you original pcmcia driver from /lib/modules/<kernel> to the new /lib/modules/<kernel>/pcmcia and calling it from rc.modules at boot..

Hope that helps .. i am a bit of a newb so sorry if its not explained well.. im not too hot on slack and laps.. ;)

cheers and good luck

:study:
CT




xenon2000 01-05-2006 10:50 AM

still searching..
 
adds2one's original post here is exactly my same issue. Though I am now using kernel 2.6.15 from a pre 2.6.13 kernel. Anyways, I noticed that dmesg was saying that the older cardctl system was going to be taken out of the kernel soon and to update to newer tools. It suggested pcmciautils. So I downloaded pcmciautils-012, downloaded sysfsutils 2.0.0 and installed those.

I am running Slackware 10.2 with kernel 2.6.15 (found out that these changes have affect 2.6.13+ kernels)

I am working with an IBM Thinkpad 390X laptop. 500Mhz P3, 128Megs ram, have working PCI ethernet via the docking station. Trying to get either or both old 3COM ethernet cards working.

lspci shows both the PCI docking station ethernet and the 3COM CardBus card detected. 3cCFE575CT CardBus is in the slot right now. I also have the 3COM 3C589D in the 2nd PCMCIA card slot, but for some reason that is not showing up with lspci. One card is cardbus and the other PCMCIA. So I guess that is why.

Anyways, I would like both card slot ethernet adapters to work since I will use this laptop as a compact router box. But at this point, if I can just get 1 of the cards to work, I can keep using the docking station's intel Pro 100 NIC for the 2nd NIC.

some lines from Dmesg:
pccard: PCMCIA card inserted into slot 0 (I think this is the 3C589D card)
Yenta: cardbus bridge found....
pccard: CardBus card inserted into slot 1 (I think this is the newer 3cCFE575CT card)

So it seems that it sees the cards just fine and the bus is working... but can't seem to get the new tools to work and make the cards active. Note: dmseg updates everytime I eject or insert the cards. So hardware seems to be fine.

I have been searching all other the net and across 3 linux forums. Hard to filter through TONS of wireless card slot help out there. And the stuff I have found for ethernet cards has been for kernel 2.4.x and pre 2.6.13 kernels using the older tools.

If I figure it out, I will post again. But I am really hoping that someone can help me out before I figure it out. :)

xenon2000 01-05-2006 03:39 PM

I give up....
 
I have spend 2 days on this... seems no matter what I do, I can see the cards on the bus using multiple commands. But I can't seem to get them to use drivers and start working. So much for trying to use the new tools.

If anyone can post a clear way to use old PCMCIA and CardBus ethernet cards with Yenta_socket using the new pcmciatools-012 or higher and kernel 2.6.13 or higher. I would love to try it out again in the future.

But I have tried my brains out. Sorry I could not solve this on my own.

kak 01-05-2006 06:58 PM

Had the same issue on my Dell 600m.
Slack & 2.6 kernel with no PCMCIA
What fixed it? Recompile the kernel with the PCMCIA stuff as modules not built directly into the kernel.
And now rc.pcmcia finds both sockets. :)

zhy2111314 01-05-2006 07:18 PM

I am using "Compaq PRESARIO 1681" with SlackWare 10.2 and Kernel 2.6.12. That is an old old laptop even no usb port and ethernet port. So I also used PCMCIA ethernet card. And I recompiled the new kernel 2.6.12, fortunately it works.
I think the most important thing is that you missed something during the kernel compiling. So check the options about PCMCIA or Cardbus in your kernel compiling. Then try again. (And the pcmcia-cs in SlackWare 10.2 is also working)

xenon2000 01-06-2006 10:11 AM

Quote:

Originally Posted by kak
Had the same issue on my Dell 600m.
Slack & 2.6 kernel with no PCMCIA
What fixed it? Recompile the kernel with the PCMCIA stuff as modules not built directly into the kernel.
And now rc.pcmcia finds both sockets. :)

First off, let me remind people that it works fine with the latest kernel 2.6.15 using the stock old tools "cardmgr".

The problem is that if you look in dmesg or during boot, you will see that the kernel is telling you that you are using the old school tools and that it will break soon when they remove those tools from a near future kernel release and recommends that you get and use the new tools "pcmciautils".

I figure I would try to use the new tools now since they have been available since 2.6.13 and that I was going to eventually have to move to the new tools in order to have the latest kernel in the future. That is what my post is all about, my troubles trying to get the new tools to work.

kak, you just say you are using Slackware with kernel 2.6, but you didn't state if it is 2.6.13+ or not. And you also didn't mention if you are using the new tools "pcmciautils-008 or higher", which also requires module-init-tools-3.2+, sysfsutils (can't remember version), etc. Also, does your bus use Yenta_sockets? According to the howto, Yenta is one of the most difficult to setup with the new tools. So that would be good to know about your setup as well.

So right now I am back to using kernel 2.6.15 with the stock "old cardmgr tools" and it works fine as expected. But one day I would like to use the new pcmciautils.

kak, if you are using the new tools and have a Yenta_socket bus with kernel 2.6.13+, I would love to hear how your files are configured and how your experience was.

zhy2111314, as for your laptop, you are using kernel 2.6.12 and if you read my post, I mentioned several times that the new tools are for kernel 2.6.13+, so you can only be using the old "cardmgr" tools and those work fine even in the latest 2.6.15 kernel.

hlenderk 04-08-2006 11:06 AM

I am having a similar? problem and just posted over at linux-hardware if you care to read it. 2.6. udev sure seems to have some complaints out there. growing pains...........

kak 04-08-2006 02:03 PM

xenon2000,
Here is what i have going.
Kernel 2.6.15.6 using slackware's udev
rc.acpi as shipped in slackware
And yes it is a yenta socket, but I am using the stock tools for it.
Also I am letting hotplug load the modules.....in other words no modification to rc.modules or modules.conf
It is pretty much the default Slack settings other than the stuff to get the Ati driver installed.
this is the output of lsmod:
Quote:

keith@slack:~$ lsmod
Module Size Used by
fglrx 450956 7
snd_pcm_oss 46176 0
snd_mixer_oss 15744 1 snd_pcm_oss
ip_conntrack_irc 5360 0
ip_conntrack_ftp 6384 0
ohci_hcd 18692 0
pcspkr 1732 0
rtc 7316 0
intel_agp 18908 1
agpgart 28360 2 fglrx,intel_agp
shpchp 43968 0
pci_hotplug 25652 1 shpchp
snd_intel8x0 27740 1
snd_ac97_codec 86112 1 snd_intel8x0
snd_ac97_bus 1984 1 snd_ac97_codec
snd_pcm 78280 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 20356 1 snd_pcm
snd 46308 8 snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
snd_page_alloc 8392 2 snd_intel8x0,snd_pcm
pcmcia 31660 4
yenta_socket 23628 4
rsrc_nonstatic 11392 1 yenta_socket
pcmcia_core 35280 3 pcmcia,yenta_socket,rsrc_nonstatic
ipw2200 98604 0
ieee80211 42536 1 ipw2200
ieee80211_crypt 4864 1 ieee80211
b44 21836 0
joydev 8000 0
tsdev 6016 0

xenon2000 04-08-2006 10:01 PM

Quote:

Originally Posted by kak
xenon2000,
Here is what i have going.
Kernel 2.6.15.6 using slackware's udev
rc.acpi as shipped in slackware
And yes it is a yenta socket, but I am using the stock tools for it.
Also I am letting hotplug load the modules.....in other words no modification to rc.modules or modules.conf
It is pretty much the default Slack settings other than the stuff to get the Ati driver installed.
this is the output of lsmod:

Well, as I already said. I too have a working stock setup. It's not the stock setup that I am trying to get working. It's that the stock setup warns that it will break in the near kernel future. And to use pcmciautils. Anyways. Doesn't matter, I gave up on that project already. Not using any pcmcia anymore for now in my current project.


All times are GMT -5. The time now is 05:11 PM.