From: Takashi Iwai <tiwai@suse•de>
To: piotr@hosowicz•com
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Randy Dunlap <randy.dunlap@oracle•com>,
tj@kernel•org, linux-next@vger•kernel.org
Subject: Re: Intel sound proke in today;s next
Date: Mon, 26 Jul 2010 19:24:27 +0200 [thread overview]
Message-ID: <s5hr5iq9mwk.wl%tiwai@suse.de> (raw)
In-Reply-To: <4C4DBE72.7070900@example.com>
At Mon, 26 Jul 2010 18:57:22 +0200,
Piotr Hosowicz wrote:
>
> On 26.07.2010 09:29, Takashi Iwai wrote:
> > At Sun, 25 Jul 2010 17:56:50 +0200,
> > Piotr Hosowicz wrote:
> >>
> >> On 25.07.2010 17:27, Takashi Iwai wrote:
> >>> At Sat, 24 Jul 2010 11:59:00 +1000,
> >>> Stephen Rothwell wrote:
> >>>>
> >>>> [Just cc'ing the sound tree contact]
> >>>>
> >>>> On Fri, 23 Jul 2010 20:24:36 +0200 Piotr Hosowicz<piotr@hosowicz•com> wrote:
> >>>>>
> >>>>> Hello,
> >>>>>
> >>>>> I just downloaded today's next and built it, then booted. Sound is not
> >>>>> working, my card is:
> >>>>>
> >>>>> 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio
> >>>>> Controller
> >>>>>
> >>>>> I am now booted with latest git kernel and cannot provide more info
> >>>>> here, I rebooted with that kernel because I am going to sleep and I like
> >>>>> to listen to music by night. If more details is necessary I could boot
> >>>>> that next tommorow, but tell me what you need.
> >>>
> >>> Make sure that your mixer setup is correct with a new kernel.
> >>> Usually alsactl restores the right mixer values, though.
> >>>
> >>> At best, run alsa-info.sh (with --no-upload option) on both kernels to
> >>> compare. Also you can try to pull only sound git tree instead of
> >>> linux-kernel to identify whether it's a problem in the sound tree or
> >>> somewhere else. Anyway, see Documentation/sound/alsa/HD-Audio.txt for
> >>> some details.
> >>
> >> I do not see such script, alsa-info.sh.
> >
> > The location of the script is found in the document mentioned above.
> >
> >> I dont know how to pull only the
> >> sound tree.
> >
> > The sound git tree URL is found in the document mentioned above.
> > Just do git-pull onto your cloned Linus tree.
>
> I don't knmow how to pull _onto_ existing files. git says that it is not
> a repo and refuses to download files, I thought that first I have to
> make git clone, but I was happy that it's not like that.
First clone, then pull onto it,
% git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
% cd linux-2.6
% git pull git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
Anyway, if your codec is either IDT or STAC codec, try the latest sound
git or wait for tomorrow's linux-next tree. A fix regarding the volume
was committed today.
Takashi
next prev parent reply other threads:[~2010-07-26 17:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 6:49 linux-next: Tree for July 23 Stephen Rothwell
2010-07-23 16:08 ` linux-next: Tree for July 23 (fscache) Randy Dunlap
2010-07-23 18:24 ` Intel sound proke in today;s next Piotr Hosowicz
2010-07-23 18:27 ` Piotr Hosowicz
2010-07-24 1:59 ` Stephen Rothwell
2010-07-25 15:27 ` Takashi Iwai
2010-07-25 15:56 ` Piotr Hosowicz
2010-07-26 7:29 ` Takashi Iwai
2010-07-26 16:57 ` Piotr Hosowicz
2010-07-26 17:24 ` Takashi Iwai [this message]
2010-07-26 17:33 ` Piotr Hosowicz
2010-07-26 18:00 ` Takashi Iwai
2010-07-26 18:30 ` Piotr Hosowicz
2010-07-26 19:03 ` Piotr Hosowicz
2010-07-26 20:17 ` Takashi Iwai
2010-07-26 20:54 ` Piotr Hosowicz
2010-07-27 5:41 ` Takashi Iwai
2010-07-24 9:14 ` [PATCH wq#for-next] fscache: fix build on !CONFIG_SYSCTL Tejun Heo
2010-07-25 22:18 ` Randy Dunlap
2010-07-23 16:41 ` [PATCH -next] compal-laptop: depends on POWER_SUPPLY Randy Dunlap
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=s5hr5iq9mwk.wl%tiwai@suse.de \
--to=tiwai@suse$(echo .)de \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=piotr@hosowicz$(echo .)com \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tj@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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