From: Colleen Josephson <cjoseph@mit.edu>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] Re: LiveCD: Unpacking Firmware
Date: Sun, 27 Mar 2011 20:00:39 -0400 [thread overview]
Message-ID: <AANLkTimVu0HMvQepWyU-hAUULEeu1FXD7n8ToLVnakHC@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik23XC6LG_1LeKO+jCEoHBDKj0+XEnqWdj1+jNP@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
Update: it seems hotplug/coldplug is the culprit.
If I disable everything, there is no hum. If I re-enable coldplug
(COLDPLUG="yes"), then the hum re-appear.
What about coldplug could be causing problems? Where should I go from here
to solve this problem?
On Sun, Mar 27, 2011 at 6:31 PM, Colleen Josephson <cjoseph@mit.edu> wrote:
> I had a question related to the amd64 minimal livecd.
>
> What exactly is happening at the "Unpacking firmware" stage of the boot
> process?
> Is there a way to find out exactly what firmware is being loaded? Or a way
> to boot without loading the firmware?
>
> Why? It is a somewhat strange reason. I am having issues with a
> high-pitched hum coming from the audio jacks (occurs on both MB sound and a
> creative sound card)
> I have a very nice sound system (a sound board, studio monitors...I am an
> audio hobbyist), and no other system has these problems, so I am relatively
> sure that it is not the speakers/cables.
>
> I have been booting from the liveCD, and I have pinpointed the point at
> which the hum starts to something near the *Unpacking firmware stage.
> I realize this is somewhat esoteric, but it renders my system almost
> useless, and would greatly appreciate any input.
>
> I did interactive mode. The interactive mode only prompts for some of the
> items. Among the items it does not prompt for is the firmware unpacking. It
> just goes and does it.
>
> --
> Colleen Josephson
> Dept. of Electrical Engineering and Computer Science
> Massachusetts Institute of Technology
> Class of 2013
>
--
Colleen Josephson
Dept. of Electrical Engineering and Computer Science
Massachusetts Institute of Technology
Class of 2013
[-- Attachment #2: Type: text/html, Size: 2086 bytes --]
next prev parent reply other threads:[~2011-03-28 0:01 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 ` Colleen Josephson [this message]
2011-03-28 0:13 ` [gentoo-catalyst] " 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
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=AANLkTimVu0HMvQepWyU-hAUULEeu1FXD7n8ToLVnakHC@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