From: Alexander Rau <al.rau@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: ericvb@debian.org
Subject: Re: 2.6.0-test1 fails at insmoding orinoco_cs
Date: Mon, 21 Jul 2003 14:40:58 +0200 [thread overview]
Message-ID: <3F1BDF5A.8010209@gmx.de> (raw)
Had the same problems. Check if you enabled ISA support in your kernel
config. Solved my problems. Otherwise check out the pcmcia-cs docs at
pcmcia.sf.net. There's a description of configuration parameters in the
troubleshooting section of the user-howto, especially on irq and io mem
problems...
Regards, Al
> I just gave a try to 2.6.0-test1, all is fine except there's an IRQ
> conflict occuring when modprobing my wireless card's driver:
>
> Jul 19 20:53:37 femto kernel: Linux Kernel Card Services 3.1.22
> Jul 19 20:53:37 femto kernel: options: [pci] [cardbus] [pm]
> Jul 19 20:53:37 femto kernel: PCI: Found IRQ 11 for device 0000:00:0b.0
> Jul 19 20:53:37 femto kernel: Yenta IRQ list 06b0, PCI irq11
> Jul 19 20:53:37 femto kernel: Socket status: 30000411
> Jul 19 20:53:37 femto kernel: PCI: Found IRQ 11 for device 0000:00:0b.1
> Jul 19 20:53:37 femto kernel: Yenta IRQ list 06b0, PCI irq11
> Jul 19 20:53:37 femto kernel: Socket status: 30000087
> Jul 19 20:53:38 femto kernel: cs: memory probe 0x0c0000-0x0fffff:
> excluding 0xc0000-0xcbfff 0xf0000-0xfffff
> Jul 19 20:53:38 femto kernel: orinoco_cs: RequestIRQ: Resource in use
>
> It's the same driver I used with 2.4.21 and it worked fine. Is this a
> bug ? I'm not a kernel guru... If you need help to debug, lemme know.
>
> Please CC me on reply.
next reply other threads:[~2003-07-21 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 12:40 Alexander Rau [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-19 19:57 2.6.0-test1 fails at insmoding orinoco_cs Eric Van Buggenhaut
2003-07-19 20:07 ` Sean Neakums
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=3F1BDF5A.8010209@gmx.de \
--to=al.rau@gmx.de \
--cc=ericvb@debian.org \
--cc=linux-kernel@vger.kernel.org \
/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