From: Colleen Josephson <cjoseph@mit.edu>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] LiveCD: Unpacking Firmware
Date: Mon, 28 Mar 2011 13:25:49 -0400 [thread overview]
Message-ID: <AANLkTi=FV0FRuVQq4w9iKcF2Q_uVRjvNbd4_W5JhfCKw@mail.gmail.com> (raw)
In-Reply-To: <20110328171005.5341.qmail@stuge.se>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
When drivers load in the system (I guess you have hardware drivers
> built as modules, as opposed to built-in to the kernel?) they will
> start exercising their respective hardware devices.
>
Actually, I've been troubleshooting from the livecd. I guess one of the
modules it loads causes this.
> It could be something simpler as well, some signals that are simply
> being coupled onto analog output.
>
> To say any more you need to find which driver is causing this. Mike's
> advice is the start; find out which drivers coldplugging loads, then
> e.g. load one at a time manually. At some point you should get the
> noise. Then dive deeper into that particular driver case.
>
OK, how do I find out which drivers coldplugging loads?
--
Colleen Josephson
Dept. of Electrical Engineering and Computer Science
Massachusetts Institute of Technology
Class of 2013
[-- Attachment #2: Type: text/html, Size: 1262 bytes --]
next prev parent reply other threads:[~2011-03-28 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 22:31 [gentoo-catalyst] LiveCD: Unpacking Firmware Colleen Josephson
2011-03-28 0:00 ` [gentoo-catalyst] " Colleen Josephson
2011-03-28 0:13 ` Mike Frysinger
2011-03-28 13:40 ` [gentoo-catalyst] " Peter Stuge
2011-03-28 16:17 ` Colleen Josephson
2011-03-28 17:05 ` Mike Frysinger
2011-03-28 17:10 ` Peter Stuge
2011-03-28 17:25 ` Colleen Josephson [this message]
2011-03-28 17:38 ` Mike Frysinger
2011-05-02 19:18 ` [gentoo-catalyst] unsubscribe Guy Harrison
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='AANLkTi=FV0FRuVQq4w9iKcF2Q_uVRjvNbd4_W5JhfCKw@mail.gmail.com' \
--to=cjoseph@mit.edu \
--cc=gentoo-catalyst@lists.gentoo.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