From: Ray Olszewski <ray@comarre.com>
To: Kevin Curtis <kevin.curtis@farsite.co.uk>, linux-newbie@vger.kernel.org
Subject: RE: Preventing signal interrupt in Kernel module code
Date: Fri, 13 Sep 2002 09:40:02 -0700 [thread overview]
Message-ID: <5.1.0.14.1.20020913092838.023090c0@celine> (raw)
In-Reply-To: <7C078C66B7752B438B88E11E5E20E72E0EF515@GENERAL.farsite.co. uk>
At 05:02 PM 9/13/02 +0100, Kevin Curtis wrote:
>Ok - I will refrain from posting technical questions here. I did also post
>it to the linux-kernel mail list too. It's just that sometimes, a question
>like mine is too trivial for them and gets ignored. However, Ray is right,
>don't let postings like mine put you off sending in your questions too.
>
>By the way, even though I'm writing Kernel modules, I still have problems
>with my Mandrake distro too. The latest being that sound has stopped
>working when I installed my network card.
Oh dear. I didn't mean to chastise you for your earlier posting. Especially
since someone else did offer a suggestion about your problem. All I meant
was what I actually said ... that your question was outside the range we
typically deal with here. Please understand that I am no one special, just
another member of the list. I wasn't trying to give people orders, just
convey a sense of the list as it has operated historically.
As to your implied question ... when I experience similar problems, I
usually find that they are pci bus problems, not Linux problems as such.
(I've had both TV-tuner cards and NICs interfere with video cards, for
example.) Observe during the early (pre-LILO or -GRUB or whatever you use)
stages of the boot process to see if your BIOS still sees both the sound
and NIC devices. If it doesn't, fiddle around ... try changing the slots of
one of the other device (or just the NIC, if your mobo has on-board sound).
On the Linux end, see if the sound hardware still shows up in the
"lspci" listing. Check /proc/interrupts and /proc/ioports for a conflict
(yes, I know Linux is supposed to share interrupts, but the reality is that
it works imperfectly at best).
That's about all I can suggest without some details -- what sound card
(what module), what NIC, and what "stopped working" means (what are you no
longer able to do that you used to be able to do?).
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA ray@comarre.com
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next parent reply other threads:[~2002-09-13 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7C078C66B7752B438B88E11E5E20E72E0EF515@GENERAL.farsite.co. uk>
2002-09-13 16:40 ` Ray Olszewski [this message]
2002-09-13 16:02 Preventing signal interrupt in Kernel module code Kevin Curtis
-- strict thread matches above, loose matches on Subject: below --
2002-09-13 15:49 Kevin Curtis
2002-09-13 17:22 ` Quinn Harris
2002-09-13 13:54 Kevin Curtis
2002-09-13 13:54 ` Kevin Curtis
2002-09-13 15:56 ` Quinn Harris
2002-09-13 18:33 ` Bill Pleasants
2002-09-13 15:39 ` Ken Boyer
2002-09-13 15:53 ` Ray Olszewski
2002-09-13 16:00 ` Ken Boyer
2002-09-13 20:06 ` Bryan Whitehead
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=5.1.0.14.1.20020913092838.023090c0@celine \
--to=ray@comarre.com \
--cc=kevin.curtis@farsite.co.uk \
--cc=linux-newbie@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.