LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 04-22-2007, 11:57 PM   #1
abend
LQ Newbie
 
Registered: Apr 2007
Posts: 7

Rep: Reputation: 0
Angry PCMCIA insert locks Slackware 11 on a CF-27


Hi,

I have a CF-27 toughbook, which has two PCMCIA slots. I installed Slackware 11. Now inserting a PCMCIA card causes the system to completely lock. It will not respond to mouse or keyboard input. The only button that does anything is the one marked "power".

I suspect that the problem is an IRQ issue with the PCMCIA modules.

dmesg includes the following lines:

Intel ISA PCIC probe : not found
Databook TCIC-2 PCMCIA probe : not found
PCI: Found IRQ 9 for device 00:0c.0
IRQ routing conflict for 00:0c.0, have IRQ 11, want IRQ 9
PCI: Sharing IRQ 9 with 00:0d.0
PCI: Found IRQ 9 for device 00:0c.1
IRQ routing conflict for 00:0c.1, have IRQ 11, want IRQ 9
PCI: Found IRQ 9 for device 00:0a.0
PCI: Sharing IRQ 9 with 00:0a.0

Any typos in the above are from my typing it.

00:0c.0 and 00:0c.0 are my PCMCIA bridge. lspci describes it as "CardBus bridge: Ricoh Co Ltd RL5c478 (rev 03)"

00:0a.0 is the sound chip, which lspci describes as "Multimeda audio controller: Yamaha Corporation YMF-744B [DS-1S Audio Controller] (rev 02)"

00:0d.0 is the modem, "Communication controller: Connexant HCF 56k Data/Fax/Voice/Spkp Modem (rev 08)"

The ISA bridge is an Intel 82371AB/EB/MB, according to lspci.

lsmod shows 16 sound related modules, all starting with snd-*
There is also:
soundcore
ds
yenta_socket
pcmcia_core
ide_scsi
uhci
usbcore
gameport

I'm not sure what the point of the ide_scsi module is, since the laptop does not have scsi.
So far, I have tried disabling ACPI by telling the kernel "acpi=off noacpi", and tried "pci=assign-busses". Neither of these fixed the problem.

In the BIOS, the serial port is on IRQ 4 and the parallel port on IRQ 7. The IrDA port is on IRQ 11. I added "exclude irq 11" to /etc/pcmcia/config.opts, but that did not fix the problem. I wasn't too hopeful about that fixing it, since the file says it does not affect CardBus cards. Those are apparently configured by the PCI hotplug system.

So my questions are these:

How can I fix PCMCIA so that inserting a card makes it usable?

How can I configure the PCI hotplug system?

How can I change IRQ routing?

Do I have entirely the wrong idea about what is causing the trouble?
 
Old 04-23-2007, 10:45 AM   #2
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 10,890
Blog Entries: 1

Rep: Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307
Hi,

Which kernel are you using? It looks like the 2.4. The ide-scsi module is used for the cd device. You do have a cd? If you are using a 2.6 kernel the module would be ide-cd.

You should 'man hotplug'.

Can you switch to another terminal after what you call a lockup?

Last edited by onebuck; 04-23-2007 at 10:55 AM.
 
Old 04-23-2007, 01:49 PM   #3
abend
LQ Newbie
 
Registered: Apr 2007
Posts: 7

Original Poster
Rep: Reputation: 0
Which kernel are you using? It looks like the 2.4.

I am using a 2.4 kernel, the one that came on the installation CD. This laptop and its pcmcia used to work with the pcmcia-cs system, which I think was the precursor to yenta_socket. Perhaps yenta_socket is meant for 2.6 kernels?

The ide-scsi module is used for the cd device. You do have a cd? If you are using a 2.6 kernel the module would be ide-cd.

I do have a CD drive, so that's probably it.

Can you switch to another terminal after what you call a lockup?

No. The blinking cursor at the prompt stops blinking and the system does not respond to keyboard or mouse input.
 
Old 04-23-2007, 08:24 PM   #4
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 10,890
Blog Entries: 1

Rep: Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307
Quote:
Originally Posted by abend
Which kernel are you using? It looks like the 2.4.

I am using a 2.4 kernel, the one that came on the installation CD. This laptop and its pcmcia used to work with the pcmcia-cs system, which I think was the precursor to yenta_socket. Perhaps yenta_socket is meant for 2.6 kernels?

The ide-scsi module is used for the cd device. You do have a cd? If you are using a 2.6 kernel the module would be ide-cd.

I do have a CD drive, so that's probably it.

Can you switch to another terminal after what you call a lockup?

No. The blinking cursor at the prompt stops blinking and the system does not respond to keyboard or mouse input.
Hi,

First, I would use the quote function on the reply window to make things easier to read instead of the the italic.

Now, the pcmcia-cs is for the 2.4 kernel uses. The Yenta_socket was written by Linus and he still maintains it. If you want some reference for the pcmcia-cs then read the README-2.4.

BTW, what card are you inserting?

I would try a livecd like knoppix to see what is actually being recognized.
 
Old 04-24-2007, 08:58 AM   #5
abend
LQ Newbie
 
Registered: Apr 2007
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by onebuck
Hi,

Now, the pcmcia-cs is for the 2.4 kernel uses. The Yenta_socket was written by Linus and he still maintains it. If you want some reference for the pcmcia-cs then read the README-2.4.

BTW, what card are you inserting?

I would try a livecd like knoppix to see what is actually being recognized.
Since I'm using a 2.4 Kernel, I think I should try to get rid of the yenta_socket stuff and go back to good old pcmcia-cs. I'll give that a shot and reply when I've done it.

I've tried both of my network cards. One is an Orinoco Silver, the other is a Prism chipset, but isn't properly labeled. I know the Orinoco card works fine, as I used in in another computer last night.
 
Old 04-26-2007, 08:53 AM   #6
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 10,890
Blog Entries: 1

Rep: Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307
Quote:
Originally Posted by abend
Since I'm using a 2.4 Kernel, I think I should try to get rid of the yenta_socket stuff and go back to good old pcmcia-cs. I'll give that a shot and reply when I've done it.

I've tried both of my network cards. One is an Orinoco Silver, the other is a Prism chipset, but isn't properly labeled. I know the Orinoco card works fine, as I used in in another computer last night.

Hi,

You should do a 'lspci -vvv' to see what bridge you are using. The yenta_socket is being loaded to accommodate the bridge that the system detects. You should look at the '/etc/rc.d/rc.pcmcia' to get a sense of detection for the bridge.

Apparently the card(s) are functional but not able to load on the machine in question.

Have you tried a LiveCD to see what is detected?
 
Old 05-02-2007, 06:50 PM   #7
abend
LQ Newbie
 
Registered: Apr 2007
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by onebuck
Hi,

You should do a 'lspci -vvv' to see what bridge you are using. The yenta_socket is being loaded to accommodate the bridge that the system detects.
The CardBus section of the output of lspci is as follows:

Code:
00:0c.0 CardBus bridge: Ricoh Co Ltd RL5c478 (rev 03)
	Subsystem: Matsushita Electric Industrial Co., Ltd. Unknown device 8332
	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: 168
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at 10000000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=00, secondary=01, subordinate=04, sec-latency=176
	Memory window 0: 10400000-107ff000 (prefetchable)
	Memory window 1: 10800000-10bff000
	I/O window 0: 00004000-000040ff
	I/O window 1: 00004400-000044ff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+
	16-bit legacy interface ports at 0001

00:0c.1 CardBus bridge: Ricoh Co Ltd RL5c478 (rev 03)
	Subsystem: Matsushita Electric Industrial Co., Ltd. Unknown device 8332
	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: 168
	Interrupt: pin B routed to IRQ 11
	Region 0: Memory at 10001000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=00, secondary=05, subordinate=08, sec-latency=176
	Memory window 0: 10c00000-10fff000 (prefetchable)
	Memory window 1: 11000000-113ff000
	I/O window 0: 00004800-000048ff
	I/O window 1: 00004c00-00004cff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+
	16-bit legacy interface ports at 0001
I can post the rest of the file if anyone thinks it would be useful, but that's all the CardBus stuff.

This is the segment of dmsg where it complains about the IRQs.
Code:
Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus] [pm]
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Intel ISA PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
PCI: Found IRQ 9 for device 00:0c.0
IRQ routing conflict for 00:0c.0, have irq 11, want irq 9
PCI: Sharing IRQ 9 with 00:0d.0
PCI: Found IRQ 9 for device 00:0c.1
IRQ routing conflict for 00:0c.1, have irq 11, want irq 9
Yenta ISA IRQ mask 0x04b8, PCI irq 11
Socket status: 30000046
Yenta ISA IRQ mask 0x04b8, PCI irq 11
Socket status: 30000046
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0820-0x08ff: clean.
cs: IO port probe 0x0800-0x080f: clean.
cs: IO port probe 0x03e0-0x04ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x0100-0x03af: excluding 0x220-0x22f 0x378-0x37f 0x388-0x38f 0x398-0x39f
cs: IO port probe 0x0a00-0x0aff: clean.
PCI: Found IRQ 9 for device 00:0a.0
PCI: Sharing IRQ 9 with 00:07.2
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
uhci.c: USB Universal Host Controller Interface driver v1.1
PCI: Found IRQ 9 for device 00:07.2
PCI: Sharing IRQ 9 with 00:0a.0
uhci.c: USB UHCI at I/O 0xfca0, IRQ 9
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
Quote:
Originally Posted by onebuck
Have you tried a LiveCD to see what is detected?
I have not tried a livecd. I was running Fedora Core of some older vintage on it before, and using pcmcia-cs, which more or less "just worked".
 
Old 05-02-2007, 07:59 PM   #8
abend
LQ Newbie
 
Registered: Apr 2007
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by onebuck
Hi,
Have you tried a LiveCD to see what is detected?
I have now tried a DSL (Damn Small Linux) liveCD. It displays the exact same symptom, that is to say, complete hard lockup as soon as a pcmcia card is inserted. There are no beeps or anything, just a complete lock.

However, if I start the laptop with the card in it, then DSL starts successfully, and recognizes the card. When I eject the card, the system locks up again. The install of slackware acts exactly the same.

The lspci output from the livecd was the same as that from the hard drrive install.
 
Old 05-11-2007, 08:54 PM   #9
abend
LQ Newbie
 
Registered: Apr 2007
Posts: 7

Original Poster
Rep: Reputation: 0
Talking

I've fixed it.

I upgraded to the 2.6 kernel that comes on the slackware CDs by following these instructions:

http://www.linuxquestions.org/linux/...Install_disc_2

And now the PCMCIA works! I guess it was a problem with a mismatch between the kernel version and the modules.

Thanks, everyone, for your help.
 
Old 07-16-2007, 07:13 PM   #10
stan.distortion
Member
 
Registered: Sep 2005
Location: ireland
Distribution: debian with bits of everything stuck on it
Posts: 114

Rep: Reputation: 15
Good to see you got it working I had the same trouble on a few older laptops, adding 'pci=usepirqmask' (without the comments) to the kernel commands in /boot/grub/menu.1st has sorted it out for me.
In case anyone was wondering, the pcmcia slot on the cf-27 is 32 bit (ok, so its 'pccard' and not 'pcmcia' ). Any card (16 or 32 bit) will freeze the system if the port isn't correctly configured.
Cheers
 
  


Reply

Tags
freeze, insert, irq, lock, pcmcia, slackware


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
System locks up when I insert any CD/DVD on SuSe Linux 10.1 ajitup Linux - Software 4 11-15-2006 02:41 AM
System Freezes / locks up when I insert any CD/DVD on SuSe Linux 10.1 ajitup Linux - Hardware 2 11-14-2006 11:48 PM
pcmcia->insert twice to activate then remove to freeze Brain Drop Linux - Laptop and Netbook 8 08-02-2004 07:15 AM
Linux locks when I insert wireless PCMCIA card 65_289 Linux - Laptop and Netbook 1 07-25-2004 04:09 PM
need to re-insert PCMCIA card.. shadowcode Linux - Laptop and Netbook 3 09-07-2003 01:05 PM


All times are GMT -5. The time now is 07:31 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration