From: Dax Kelson <dax@gurulabs.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: linux-kernel@vger.kernel.org, linux-thinkpad@linux-thinkpad.org
Subject: Re: pcmcia on the T42p
Date: Mon, 12 Jul 2004 15:39:29 -0600 [thread overview]
Message-ID: <1089668369.3848.25.camel@mentorng.gurulabs.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0407102320180.1145@t42p>
On Sun, 2004-07-11 at 00:27, Rasmus Lerdorf wrote:
> You mentioned you couldn't get your T42 to see any pcmcia events with a
> Cisco Aironet 350 card. I just tried it on mine and it worked fine. I
> didn't boot with it and plugged it in and it came right up. cardctl eject
> and re-inserted it about 10 times and each time it came back up fine.
More details and resolution.
When I tried Debian stable (with a 2.4 kernel), everything worked great
including audible "beeps" when I inserted/removed PCMCIA cards.
I upgraded to Debian testing and then unstable with the 2.6.7 kernel and
PCMCIA devices would only work if inserted prior to booting. This
matched my Fedora Core v2 experience with the latest errata kernel, or
with 2.6.7-mm.
With Debian testing/unstable using the Debian stable 2.4 kernel
everything was peachy.
I found that loading the BIOS default setting that made everything work
(minus the audible beeps). The default BIOS settings has a screen where
all IRQs are *forced* to be IRQ 11, and sure enough, cat
/proc/interrupts showed everything on 11. I had changed it to "Auto"
instead of "11" and cat /proc/interrupts showed everything spread
around. Everything seemed to work great, except PCMCIA.
Resetting my BIOS back to defaults and now PCMCIA hotplug is working.
It seems that it *should* work with interrupts not all clumped up on
IRQ 11 (and indeed, Windows does work with that config), but for now
at least, my PCMCIA slots are working.
Dax Kelson
next parent reply other threads:[~2004-07-12 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0407102320180.1145@t42p>
2004-07-12 21:39 ` Dax Kelson [this message]
2004-07-12 21:45 ` Rasmus Lerdorf
2004-07-12 23:08 ` [ltp] " Dax Kelson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1089668369.3848.25.camel@mentorng.gurulabs.com \
--to=dax@gurulabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-thinkpad@linux-thinkpad.org \
--cc=rasmus@lerdorf.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®