[gentoo-user] My Continuing ALSA Woes

[gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

I still cannot get my sound card to work!  Here is the evidence I've
been able to collect:

camille linux # lspci -v | grep -i audio
0000:00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) High Definition Audio Controller (rev 03)


I've added it to my /etc/make.conf:

camille linux # cat /etc/make.conf | grep 'ALSA_CARDS'
ALSA_CARDS="intel8x0"


Support for the snd-hda-intel (my card) has been compiled into the
kernel:

camille linux # cat /usr/src/linux/.config | grep 'HDA'
CONFIG_SND_HDA_INTEL=m

I rebuilt the kernel.

I've added the card infomation to /etc/modules.d/alsa:

# Alsa 0.9.X kernel modules' configuration file.
#
$Header: /var/cvsroot/gentoo-x86/media-sound/alsa-utils/files/alsa-modules.conf-rc,v 1.4 2004/11/16 01:31:22 eradicator Exp $

# ALSA portion
alias char-major-116 snd
# OSS/Free portion
alias char-major-14 soundcore

##
## IMPORTANT:
## You need to customise this section for your specific sound card(s)
## and then run `update-modules' command.
## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
##
##  ALSA portion
## alias snd-card-0 snd-interwave
alias snd-card-0 snd-hda-intel
## alias snd-card-1 snd-ens1371
##  OSS/Free portion
## alias sound-slot-0 snd-card-0
## alias sound-slot-1 snd-card-1
##

# OSS/Free portion - card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
##  OSS/Free portion - card #2
## alias sound-service-1-0 snd-mixer-oss
## alias sound-service-1-3 snd-pcm-oss
## alias sound-service-1-12 snd-pcm-oss

alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss

# Set this to the correct number of cards.
options snd cards_limit=1

And run modules-update:

camille linux # modules-update
camille linux #

I rebooted the computer.  

I attempted to start /etc/init.d/alsasound:

camille ~ # /etc/init.d/alsasound start
 * Loading ALSA modules ...
 *   Loading: snd-card-0 ...
WARNING: Error inserting snd_hda_codec
(/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-codec.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_hda_intel
(/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-intel.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
[ !! ] *   Loading: snd-seq-oss ...
[ ok ] *   Loading: snd-pcm-oss ...
[ ok ] * ERROR: Failed to load necessary drivers
[ ok ] * Restoring Mixer Levels ...
 * No mixer config in /etc/asound.state, you have to unmute your card!
[ ok ]

I checked dmesg:

camille ~ # dmesg | grep 'snd_hda_codec'
snd_hda_codec: disagrees about version of symbol snd_ctl_add
snd_hda_codec: Unknown symbol snd_ctl_add
snd_hda_codec: disagrees about version of symbol snd_card_proc_new
snd_hda_codec: Unknown symbol snd_card_proc_new
snd_hda_codec: disagrees about version of symbol snd_ctl_find_id
snd_hda_codec: Unknown symbol snd_ctl_find_id
snd_hda_codec: disagrees about version of symbol snd_ctl_new1
snd_hda_codec: Unknown symbol snd_ctl_new1
snd_hda_codec: disagrees about version of symbol snd_component_add
snd_hda_codec: Unknown symbol snd_component_add
snd_hda_codec: disagrees about version of symbol snd_ctl_elem_read
snd_hda_codec: Unknown symbol snd_ctl_elem_read
snd_hda_codec: disagrees about version of symbol snd_ctl_elem_write
snd_hda_codec: Unknown symbol snd_ctl_elem_write
snd_hda_codec: disagrees about version of symbol snd_device_new
snd_hda_codec: Unknown symbol snd_device_new
snd_hda_codec: disagrees about version of symbol
snd_pcm_hw_constraint_step
snd_hda_codec: Unknown symbol snd_pcm_hw_constraint_step
snd_hda_intel: Unknown symbol snd_hda_codec_new
snd_hda_codec: disagrees about version of symbol snd_ctl_add
snd_hda_codec: Unknown symbol snd_ctl_add
snd_hda_codec: disagrees about version of symbol snd_card_proc_new
snd_hda_codec: Unknown symbol snd_card_proc_new
snd_hda_codec: disagrees about version of symbol snd_ctl_find_id
snd_hda_codec: Unknown symbol snd_ctl_find_id
snd_hda_codec: disagrees about version of symbol snd_ctl_new1
snd_hda_codec: Unknown symbol snd_ctl_new1
snd_hda_codec: disagrees about version of symbol snd_component_add
snd_hda_codec: Unknown symbol snd_component_add
snd_hda_codec: disagrees about version of symbol snd_ctl_elem_read
snd_hda_codec: Unknown symbol snd_ctl_elem_read
snd_hda_codec: disagrees about version of symbol snd_ctl_elem_write
snd_hda_codec: Unknown symbol snd_ctl_elem_write
snd_hda_codec: disagrees about version of symbol snd_device_new
snd_hda_codec: Unknown symbol snd_device_new
snd_hda_codec: disagrees about version of symbol
snd_pcm_hw_constraint_step
snd_hda_codec: Unknown symbol snd_pcm_hw_constraint_step
snd_hda_intel: Unknown symbol snd_hda_codec_new
snd_hda_codec: disagrees about version of symbol snd_ctl_add
snd_hda_codec: Unknown symbol snd_ctl_add
snd_hda_codec: disagrees about version of symbol snd_card_proc_new
snd_hda_codec: Unknown symbol snd_card_proc_new
snd_hda_codec: disagrees about version of symbol snd_ctl_find_id
snd_hda_codec: Unknown symbol snd_ctl_find_id
snd_hda_codec: disagrees about version of symbol snd_ctl_new1
snd_hda_codec: Unknown symbol snd_ctl_new1
snd_hda_codec: disagrees about version of symbol snd_component_add
snd_hda_codec: Unknown symbol snd_component_add
snd_hda_codec: disagrees about version of symbol snd_ctl_elem_read
snd_hda_codec: Unknown symbol snd_ctl_elem_read
snd_hda_codec: disagrees about version of symbol snd_ctl_elem_write
snd_hda_codec: Unknown symbol snd_ctl_elem_write
snd_hda_codec: disagrees about version of symbol snd_device_new
snd_hda_codec: Unknown symbol snd_device_new
snd_hda_codec: disagrees about version of symbol
snd_pcm_hw_constraint_step
snd_hda_codec: Unknown symbol snd_pcm_hw_constraint_step
snd_hda_intel: Unknown symbol snd_hda_codec_new
camille ~ #

I'm at a loss as for what to do next.  Can anyone help me with this?
-Michael Sullivan-



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mike Williams]

On Wednesday 19 October 2005 19:03, Michael Sullivan wrote:
> I'm at a loss as for what to do next.  Can anyone help me with this?

Do a clean re-compile of the kernel with anything that might possible be 
related to your sound card as modules, especially the mixer and sequencer 
stuff. Doing this as a clean compile is important, the symbol version stuff 
has possible come about from having things compiled at different times.

Put /etc/modules.d/alsa back as it was, remove the ALSA_CARDS variable from 
make.conf (it's used by the alsa-driver package, so unnecessary for kernel 
compiled drivers), and reboot.

The alsasound init script, and associated tools, are clever, and don't 
actually need to be told what card you have (in "simple" circumstances).

-- 
Mike Williams

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Kevin Hanson]

Mike Williams wrote:

>On Wednesday 19 October 2005 19:03, Michael Sullivan wrote:
>  
>
>>I'm at a loss as for what to do next.  Can anyone help me with this?
>>    
>>
>
>Do a clean re-compile of the kernel with anything that might possible be 
>related to your sound card as modules, especially the mixer and sequencer 
>stuff. Doing this as a clean compile is important, the symbol version stuff 
>has possible come about from having things compiled at different times.
>
>Put /etc/modules.d/alsa back as it was, remove the ALSA_CARDS variable from 
>make.conf (it's used by the alsa-driver package, so unnecessary for kernel 
>compiled drivers), and reboot.
>
>The alsasound init script, and associated tools, are clever, and don't 
>actually need to be told what card you have (in "simple" circumstances).
>
>  
>
I noticed the OP is using a 2.6.13 kernel.  I have had problems using 
modules with this kernel where they worked in a 2.6.12 kernel.  For 
example, I could not get agp/dri working when compiled as modules.  Once 
I compiled them in the kernel itself, it worked.

So, when I couldn't get alsa modules to load after upgrading to 2.6.13 
kernel, I tried the above trick.  That did it for me.  When alsa was 
compiled in kernel, not as modules nor with the alsa-driver ebuild, 
sound started working.

I think there is something that changed in 2.6.13 that has affected 
modules.  I haven't researched anymore as my work-around has me happy 
for now.

hth,
kevin
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Sascha Lucas]

> I've added it to my /etc/make.conf:
>
> camille linux # cat /etc/make.conf | grep 'ALSA_CARDS'
> ALSA_CARDS="intel8x0"

You must chose to use in kernel driver or the external provided by 
sound/alsa-driver. See http://www.gentoo.org/doc/en/alsa-guide.xml.

ALSA_CARDS="intel8x0" indicates you want sound/alsa-driver. But your grep 
in kernel .config indicates the kernel driver.

Read the URL above and skip the part about "Using the ALSA Driver 
package" in section 2.

Sascha.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Wed, 2005-10-19 at 20:40 +0200, Sascha Lucas wrote:
> > I've added it to my /etc/make.conf:
> >
> > camille linux # cat /etc/make.conf | grep 'ALSA_CARDS'
> > ALSA_CARDS="intel8x0"
> 
> You must chose to use in kernel driver or the external provided by 
> sound/alsa-driver. See http://www.gentoo.org/doc/en/alsa-guide.xml.
> 
> ALSA_CARDS="intel8x0" indicates you want sound/alsa-driver. But your grep 
> in kernel .config indicates the kernel driver.
> 
> Read the URL above and skip the part about "Using the ALSA Driver 
> package" in section 2.
> 
> Sascha.
> 

>From the Gentoo ALSA Guide (link above):

Note:  If you activated ALSA in your kernel and did not compile ALSA as
modules, please proceed to the ALSA Initscript section. The rest of you
need to configure ALSA. This is made very easy by the existence of the
alsaconf tool provided by alsa-utils.

I compiled support for my card as a module.  Does this still apply?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Rob]

Michael Sullivan wrote:
> On Wed, 2005-10-19 at 20:40 +0200, Sascha Lucas wrote:
> 
>>>I've added it to my /etc/make.conf:
>>>
>>>camille linux # cat /etc/make.conf | grep 'ALSA_CARDS'
>>>ALSA_CARDS="intel8x0"
>>
>>You must chose to use in kernel driver or the external provided by 
>>sound/alsa-driver. See http://www.gentoo.org/doc/en/alsa-guide.xml.
>>
>>ALSA_CARDS="intel8x0" indicates you want sound/alsa-driver. But your grep 
>>in kernel .config indicates the kernel driver.
>>
>>Read the URL above and skip the part about "Using the ALSA Driver 
>>package" in section 2.
>>
>>Sascha.
>>
> 
> 
>>From the Gentoo ALSA Guide (link above):
> 
> Note:  If you activated ALSA in your kernel and did not compile ALSA as
> modules, please proceed to the ALSA Initscript section. The rest of you
> need to configure ALSA. This is made very easy by the existence of the
> alsaconf tool provided by alsa-utils.
> 
> I compiled support for my card as a module.  Does this still apply?
> 
I recently had to set up ALSA and had some problems.  Some of it I
thought was due to the documentation.  You have to read each paragraph
over a couple of times to actually realize what you have to do next.  I
have set up ALSA before, the instructions were clearer, and I got it the
first time.  Maybe my reading and following instructions skills are not
too good.  Too many things going on at once here.

Anyway, if I have time, perhaps I will try to rearrange the document to
be clearer, and see if anyone thinks it is better.

IMHO, I think each type of install should be presented from start to
finish, without mixing up all of the steps and then relying on the
document to tell you where you go next in the document.

Rob.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Nick Rout]

On Thursday 20 October 2005 07:03, Michael Sullivan wrote:
> camille linux # cat /etc/make.conf | grep 'ALSA_CARDS'
> ALSA_CARDS="intel8x0"
>
>
> Support for the snd-hda-intel (my card) has been compiled into the
> kernel:
>
> camille linux # cat /usr/src/linux/.config | grep 'HDA'
> CONFIG_SND_HDA_INTEL=m
>
> I rebuilt the kernel.



Why have ALSA_CARDDS set to intel8x0 whn your card is hda_intel?

Have you run alsaconfig like I told you last time?

I suggest you have probably not re-compiled your kernel properly from the 
output you gave. Have you enabled all the other kernel features that 
snd-hda-intel requires?
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Thu, 2005-10-20 at 07:49 +1300, Nick Rout wrote:
> On Thursday 20 October 2005 07:03, Michael Sullivan wrote:
> > camille linux # cat /etc/make.conf | grep 'ALSA_CARDS'
> > ALSA_CARDS="intel8x0"
> >
> >
> > Support for the snd-hda-intel (my card) has been compiled into the
> > kernel:
> >
> > camille linux # cat /usr/src/linux/.config | grep 'HDA'
> > CONFIG_SND_HDA_INTEL=m
> >
> > I rebuilt the kernel.
> 
> 
> 
> Why have ALSA_CARDDS set to intel8x0 whn your card is hda_intel?
> 
> Have you run alsaconfig like I told you last time?
> 
> I suggest you have probably not re-compiled your kernel properly from the 
> output you gave. Have you enabled all the other kernel features that 
> snd-hda-intel requires?

What other kernel features does it require?  In menuconfig I checked
everything in the sound category that wasn't marked as experimental...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Nick Rout]

> > 
> > I suggest you have probably not re-compiled your kernel properly from the 
> > output you gave. Have you enabled all the other kernel features that 
> > snd-hda-intel requires?
> 
> What other kernel features does it require?  In menuconfig I checked
> everything in the sound category that wasn't marked as experimental...

I don't know, I do not have one of those cards and the driver was new to
the kernel in 2.6.12 IIRC. However you were getting symbol errors so
either you left something out, or the kernel needs to be compiled
cleanly. I suspect the latter.

Back up .config, make mrproper, restore .config, make menuconfig and
exit, choosing yes to save kernel config.

then make the kernel in the usual manner.




-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Thu, 2005-10-20 at 10:29 +1300, Nick Rout wrote:
> > > 
> > > I suggest you have probably not re-compiled your kernel properly from the 
> > > output you gave. Have you enabled all the other kernel features that 
> > > snd-hda-intel requires?
> > 
> > What other kernel features does it require?  In menuconfig I checked
> > everything in the sound category that wasn't marked as experimental...
> 
> I don't know, I do not have one of those cards and the driver was new to
> the kernel in 2.6.12 IIRC. However you were getting symbol errors so
> either you left something out, or the kernel needs to be compiled
> cleanly. I suspect the latter.
> 
> Back up .config, make mrproper, restore .config, make menuconfig and
> exit, choosing yes to save kernel config.
> 
> then make the kernel in the usual manner.
> 
> 
> 
> 
> -- 
> Nick Rout <nick@rout.co.nz>

Can this be done with genkernel?  I've always used genkernel in the
past.  All attempts at building and installing kernels manually have
failed.  I've spent most of the afternoon and evening today trying to
build the 2.6.13-gentoo-r3 kernel manually.  I've followed the kernel
section in the handbook and I'm pretty sure I've got it set up correctly
in grub, but I always get a kernel panic when I try to use it.  I think
it's because there is not initial root disk file.  I'd rather use
genkernel if I can...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Nick Rout]

On Wed, 19 Oct 2005 22:21:15 -0500
Michael Sullivan wrote:

> > 
> > Back up .config, make mrproper, restore .config, make menuconfig and
> > exit, choosing yes to save kernel config.
> > 
> > then make the kernel in the usual manner.
> 
> Can this be done with genkernel?  I've always used genkernel in the
> past.  All attempts at building and installing kernels manually have
> failed.  I've spent most of the afternoon and evening today trying to
> build the 2.6.13-gentoo-r3 kernel manually.  I've followed the kernel
> section in the handbook and I'm pretty sure I've got it set up correctly
> in grub, but I always get a kernel panic when I try to use it.  I think
> it's because there is not initial root disk file.  I'd rather use
> genkernel if I can...

Not a genkernel expert, 

The aim of my post was to ensure you had a completely clean kernel tree. but theres no reason why you cannot completely clean out your kernel
tree with make mrproper then run genkernel.

-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Thu, 2005-10-20 at 16:41 +1300, Nick Rout wrote:
> On Wed, 19 Oct 2005 22:21:15 -0500
> Michael Sullivan wrote:
> 
> > > 
> > > Back up .config, make mrproper, restore .config, make menuconfig and
> > > exit, choosing yes to save kernel config.
> > > 
> > > then make the kernel in the usual manner.
> > 
> > Can this be done with genkernel?  I've always used genkernel in the
> > past.  All attempts at building and installing kernels manually have
> > failed.  I've spent most of the afternoon and evening today trying to
> > build the 2.6.13-gentoo-r3 kernel manually.  I've followed the kernel
> > section in the handbook and I'm pretty sure I've got it set up correctly
> > in grub, but I always get a kernel panic when I try to use it.  I think
> > it's because there is not initial root disk file.  I'd rather use
> > genkernel if I can...
> 
> Not a genkernel expert, 
> 
> The aim of my post was to ensure you had a completely clean kernel tree. but theres no reason why you cannot completely clean out your kernel
> tree with make mrproper then run genkernel.
> 
> -- 
> Nick Rout <nick@rout.co.nz>
> 

I moved my .config to another location, ran 'make mrproper',
moved .config back and ran the genkernel script and then rebooted and
it's still giving me the error when I try to modprobe snd-hda-intel:

camille ~ # modprobe snd-hda-intel
WARNING: Error inserting snd_hda_codec
(/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-codec.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_hda_intel
(/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-intel.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

What's next?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/20/05, Michael Sullivan <michael@espersunited.com> wrote:

>
> I moved my .config to another location, ran 'make mrproper',
> moved .config back and ran the genkernel script and then rebooted and
> it's still giving me the error when I try to modprobe snd-hda-intel:
>
> camille ~ # modprobe snd-hda-intel
> WARNING: Error inserting snd_hda_codec
> (/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-codec.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> FATAL: Error inserting snd_hda_intel
> (/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-intel.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
>
> What's next?
>

Michael,
   I have not followed this thread in depth. Sorry if I cover old
ground. Please give me a bit of info:

uname -a
ls -al /usr/src
lspci
lsmod
cat /etc/modules.d/alsa

   Basically I'm concerned that the hardware you have and the modules
you are trying to load aren't matching up.

   As an FYI only, I've never managed to boot a completely working
kernel I created with genkernel. It just didn't work for me. I know
you're a bit worried about building a kernel by hand, but long term
it's really a good thing to learn.

   I'm around today and can help out.

Cheers,
Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Thu, 2005-10-20 at 06:11 -0700, Mark Knecht wrote:
> On 10/20/05, Michael Sullivan <michael@espersunited.com> wrote:
> 
> >
> > I moved my .config to another location, ran 'make mrproper',
> > moved .config back and ran the genkernel script and then rebooted and
> > it's still giving me the error when I try to modprobe snd-hda-intel:
> >
> > camille ~ # modprobe snd-hda-intel
> > WARNING: Error inserting snd_hda_codec
> > (/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-codec.ko):
> > Unknown symbol in module, or unknown parameter (see dmesg)
> > FATAL: Error inserting snd_hda_intel
> > (/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-intel.ko):
> > Unknown symbol in module, or unknown parameter (see dmesg)
> >
> > What's next?
> >
> 
> Michael,
>    I have not followed this thread in depth. Sorry if I cover old
> ground. Please give me a bit of info:
> 
> uname -a
> ls -al /usr/src
> lspci
> lsmod
> cat /etc/modules.d/alsa
> 
>    Basically I'm concerned that the hardware you have and the modules
> you are trying to load aren't matching up.
> 
>    As an FYI only, I've never managed to boot a completely working
> kernel I created with genkernel. It just didn't work for me. I know
> you're a bit worried about building a kernel by hand, but long term
> it's really a good thing to learn.
> 
>    I'm around today and can help out.
> 
> Cheers,
> Mark
> 

camille ~ # uname -a
Linux camille 2.6.13-gentoo-r3 #1 SMP Thu Oct 20 08:22:11 CDT 2005 i686
Intel(R) Celeron(R) CPU 2.66GHz GenuineIntel GNU/Linux
camille ~ # ls -al /usr/src
total 12
drwxr-xr-x   3 root root 4096 Oct 19 15:42 .
drwxr-xr-x  18 root root 4096 Oct 19 18:27 ..
-rw-r--r--   1 root root    0 Oct 18 19:11 .keep
lrwxrwxrwx   1 root root   22 Oct 18 12:27 linux ->
linux-2.6.13-gentoo-r3
drwxr-xr-x  19 root root 4096 Oct 20 08:35 linux-2.6.13-gentoo-r3
camille ~ # lspci
0000:00:00.0 Host bridge: Intel Corporation 915G/P/GV/GL/PL/910GL
Processor to I/O Controller
0000:00:02.0 VGA compatible controller: Intel Corporation
82915G/GV/910GL Express Chipset Family Graphics Controller
0000:00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) High Definition Audio Controller (rev 03)
0000:00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) PCI Express Port 1 (rev 03)
0000:00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) PCI Express Port 2 (rev 03)
0000:00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) PCI Express Port 3 (rev 03)
0000:00:1c.3 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) PCI Express Port 4 (rev 03)
0000:00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) USB UHCI #1 (rev 03)
0000:00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) USB UHCI #2 (rev 03)
0000:00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) USB UHCI #3 (rev 03)
0000:00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) USB UHCI #4 (rev 03)
0000:00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) USB2 EHCI Controller (rev 03)
0000:00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3)
0000:00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC
Interface Bridge (rev 03)
0000:00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) IDE Controller (rev 03)
0000:00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W)
SATA Controller (rev 03)
0000:00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) SMBus Controller (rev 03)
0000:05:00.0 Multimedia video controller: Internext Compression Inc
iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
0000:05:01.0 Communication controller: U.S. Robotics: Unknown device
2f00 (rev 01)
0000:05:08.0 Ethernet controller: Intel Corporation 82562ET/EZ/GT/GZ -
PRO/100 VE (LOM) Ethernet Controller (rev 01)
camille ~ # lsmod
Module                  Size  Used by
nfs                    76252  2
ipv6                  187584  8
nfsd                   75944  9
lockd                  45384  3 nfs,nfsd
sunrpc                 98788  14 nfs,nfsd,lockd
parport_pc             27908  0
parport                22184  1 parport_pc
floppy                 45236  0
rtc                     8808  0
snd_pcm                52932  0
snd_timer              15764  1 snd_pcm
snd                    31748  2 snd_pcm,snd_timer
snd_page_alloc          5460  1 snd_pcm
evdev                   6496  0
e100                   26128  0
mii                     2800  1 e100
dm_mirror              15412  0
dm_mod                 37788  1 dm_mirror
ata_piix                6196  2
ahci                    8212  0
sata_qstor              6388  0
sata_vsc                5204  0
sata_uli                4496  0
sata_sis                4368  0
sata_sx4                9844  0
sata_nv                 5908  0
sata_via                5524  0
sata_svw                4788  0
sata_sil                6036  0
sata_promise            7252  0
libata                 27892  12
ata_piix,ahci,sata_qstor,sata_vsc,sata_uli,sata_sis,sata_sx4,sata_nv,sata_via,sata_svw,sata_sil,sata_promise
sbp2                   17112  0
ohci1394               26372  0
ieee1394               59000  2 sbp2,ohci1394
sl811_hcd               9360  0
ohci_hcd               15252  0
uhci_hcd               25152  0
usb_storage            44320  0
usbhid                 26272  0
ehci_hcd               23000  0
usbcore                77116  7
sl811_hcd,ohci_hcd,uhci_hcd,usb_storage,usbhid,ehci_hcd
camille ~ #

camille ~ # cat /etc/modules.d/alsa
# Alsa 0.9.X kernel modules' configuration file.
#
$Header: /var/cvsroot/gentoo-x86/media-sound/alsa-utils/files/alsa-modules.conf-rc,v 1.4 2004/11/16 01:31:22 eradicator Exp $

# ALSA portion
alias char-major-116 snd
# OSS/Free portion
alias char-major-14 soundcore

##
## IMPORTANT:
## You need to customise this section for your specific sound card(s)
## and then run `update-modules' command.
## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
##
##  ALSA portion
## alias snd-card-0 snd-interwave
alias snd-card-0 snd-hda-intel
## alias snd-card-1 snd-ens1371
##  OSS/Free portion
## alias sound-slot-0 snd-card-0
## alias sound-slot-1 snd-card-1
##

# OSS/Free portion - card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
##  OSS/Free portion - card #2
## alias sound-service-1-0 snd-mixer-oss
## alias sound-service-1-3 snd-pcm-oss
## alias sound-service-1-12 snd-pcm-oss

alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss

# Set this to the correct number of cards.
options snd cards_limit=1
camille ~ #

I hope you can help.  Thank you for trying...
-Michael Sullivan-

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/20/05, Michael Sullivan <michael@espersunited.com> wrote:
> On Thu, 2005-10-20 at 06:11 -0700, Mark Knecht wrote:
> > On 10/20/05, Michael Sullivan <michael@espersunited.com> wrote:
> >
> > >
> > > I moved my .config to another location, ran 'make mrproper',
> > > moved .config back and ran the genkernel script and then rebooted and
> > > it's still giving me the error when I try to modprobe snd-hda-intel:
> > >
> > > camille ~ # modprobe snd-hda-intel
> > > WARNING: Error inserting snd_hda_codec
> > > (/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-codec.ko):
> > > Unknown symbol in module, or unknown parameter (see dmesg)
> > > FATAL: Error inserting snd_hda_intel
> > > (/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-intel.ko):
> > > Unknown symbol in module, or unknown parameter (see dmesg)
> > >
> > > What's next?
> > >
> >
> > Michael,
> >    I have not followed this thread in depth. Sorry if I cover old
> > ground. Please give me a bit of info:
> >
> > uname -a
> > ls -al /usr/src
> > lspci
> > lsmod
> > cat /etc/modules.d/alsa
> >
> >    Basically I'm concerned that the hardware you have and the modules
> > you are trying to load aren't matching up.
> >
> >    As an FYI only, I've never managed to boot a completely working
> > kernel I created with genkernel. It just didn't work for me. I know
> > you're a bit worried about building a kernel by hand, but long term
> > it's really a good thing to learn.
> >
> >    I'm around today and can help out.
> >
> > Cheers,
> > Mark
> >
>
> camille ~ # uname -a
> Linux camille 2.6.13-gentoo-r3 #1 SMP Thu Oct 20 08:22:11 CDT 2005 i686
> Intel(R) Celeron(R) CPU 2.66GHz GenuineIntel GNU/Linux

Possibly an SMP issue? Is this a dual Celeron system? Is there such a
thing as a Hper Threading Celeron?



> camille ~ # ls -al /usr/src


> lrwxrwxrwx   1 root root   22 Oct 18 12:27 linux ->
> linux-2.6.13-gentoo-r3
> drwxr-xr-x  19 root root 4096 Oct 20 08:35 linux-2.6.13-gentoo-r3

This is your only kernel. OK.


> camille ~ # lspci

> 0000:00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> Family) High Definition Audio Controller (rev 03)


> camille ~ # lsmod
> Module                  Size  Used by
<SNIP>
> snd_pcm                52932  0
> snd_timer              15764  1 snd_pcm
> snd                    31748  2 snd_pcm,snd_timer
> snd_page_alloc          5460  1 snd_pcm
<SNIP>

Clearly nothing close to enough stuff is loaded as modules. Either you
built it into the kernel or the modules weren't loaded. It's probably
the latter since it doesn't find your card.



> camille ~ # cat /etc/modules.d/alsa
> # Alsa 0.9.X kernel modules' configuration file.
> #
> $Header: /var/cvsroot/gentoo-x86/media-sound/alsa-utils/files/alsa-modules.conf-rc,v 1.4 2004/11/16 01:31:22 eradicator Exp $
>
> # ALSA portion
> alias char-major-116 snd
> # OSS/Free portion
> alias char-major-14 soundcore
>
> ##
> ## IMPORTANT:
> ## You need to customise this section for your specific sound card(s)
> ## and then run `update-modules' command.
> ## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
> ##
> ##  ALSA portion
> ## alias snd-card-0 snd-interwave
> alias snd-card-0 snd-hda-intel
> ## alias snd-card-1 snd-ens1371
> ##  OSS/Free portion
> ## alias sound-slot-0 snd-card-0
> ## alias sound-slot-1 snd-card-1
> ##
>
> # OSS/Free portion - card #1
> alias sound-service-0-0 snd-mixer-oss
> alias sound-service-0-1 snd-seq-oss
> alias sound-service-0-3 snd-pcm-oss
> alias sound-service-0-8 snd-seq-oss
> alias sound-service-0-12 snd-pcm-oss
> ##  OSS/Free portion - card #2
> ## alias sound-service-1-0 snd-mixer-oss
> ## alias sound-service-1-3 snd-pcm-oss
> ## alias sound-service-1-12 snd-pcm-oss
>
> alias /dev/mixer snd-mixer-oss
> alias /dev/dsp snd-pcm-oss
> alias /dev/midi snd-seq-oss
>
> # Set this to the correct number of cards.
> options snd cards_limit=1
> camille ~ #
>

This looks pretty reasonable.

Please provide the following info:

cat /proc/asound/version

slocate snd- | grep modules

cat /usr/src/linux/.config | grep SND

cat /etc/modprobe.conf

Good luck,
Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Thu, 2005-10-20 at 07:24 -0700, Mark Knecht wrote:
> On 10/20/05, Michael Sullivan <michael@espersunited.com> wrote:
> > On Thu, 2005-10-20 at 06:11 -0700, Mark Knecht wrote:
> > > On 10/20/05, Michael Sullivan <michael@espersunited.com> wrote:
> > >
> > > >
> > > > I moved my .config to another location, ran 'make mrproper',
> > > > moved .config back and ran the genkernel script and then rebooted and
> > > > it's still giving me the error when I try to modprobe snd-hda-intel:
> > > >
> > > > camille ~ # modprobe snd-hda-intel
> > > > WARNING: Error inserting snd_hda_codec
> > > > (/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-codec.ko):
> > > > Unknown symbol in module, or unknown parameter (see dmesg)
> > > > FATAL: Error inserting snd_hda_intel
> > > > (/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-intel.ko):
> > > > Unknown symbol in module, or unknown parameter (see dmesg)
> > > >
> > > > What's next?
> > > >
> > >
> > > Michael,
> > >    I have not followed this thread in depth. Sorry if I cover old
> > > ground. Please give me a bit of info:
> > >
> > > uname -a
> > > ls -al /usr/src
> > > lspci
> > > lsmod
> > > cat /etc/modules.d/alsa
> > >
> > >    Basically I'm concerned that the hardware you have and the modules
> > > you are trying to load aren't matching up.
> > >
> > >    As an FYI only, I've never managed to boot a completely working
> > > kernel I created with genkernel. It just didn't work for me. I know
> > > you're a bit worried about building a kernel by hand, but long term
> > > it's really a good thing to learn.
> > >
> > >    I'm around today and can help out.
> > >
> > > Cheers,
> > > Mark
> > >
> >
> > camille ~ # uname -a
> > Linux camille 2.6.13-gentoo-r3 #1 SMP Thu Oct 20 08:22:11 CDT 2005 i686
> > Intel(R) Celeron(R) CPU 2.66GHz GenuineIntel GNU/Linux
> 
> Possibly an SMP issue? Is this a dual Celeron system? Is there such a
> thing as a Hper Threading Celeron?

I don't know anything about SMP.
> 
> 
> > camille ~ # ls -al /usr/src
> 
> 
> > lrwxrwxrwx   1 root root   22 Oct 18 12:27 linux ->
> > linux-2.6.13-gentoo-r3
> > drwxr-xr-x  19 root root 4096 Oct 20 08:35 linux-2.6.13-gentoo-r3
> 
> This is your only kernel. OK.
> 
> 
> > camille ~ # lspci
> 
> > 0000:00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> > Family) High Definition Audio Controller (rev 03)
> 
> 
> > camille ~ # lsmod
> > Module                  Size  Used by
> <SNIP>
> > snd_pcm                52932  0
> > snd_timer              15764  1 snd_pcm
> > snd                    31748  2 snd_pcm,snd_timer
> > snd_page_alloc          5460  1 snd_pcm
> <SNIP>
> 
> Clearly nothing close to enough stuff is loaded as modules. Either you
> built it into the kernel or the modules weren't loaded. It's probably
> the latter since it doesn't find your card.
> 

I compiled support for the sound card as a module.

> 
> > camille ~ # cat /etc/modules.d/alsa
> > # Alsa 0.9.X kernel modules' configuration file.
> > #
> > $Header: /var/cvsroot/gentoo-x86/media-sound/alsa-utils/files/alsa-modules.conf-rc,v 1.4 2004/11/16 01:31:22 eradicator Exp $
> >
> > # ALSA portion
> > alias char-major-116 snd
> > # OSS/Free portion
> > alias char-major-14 soundcore
> >
> > ##
> > ## IMPORTANT:
> > ## You need to customise this section for your specific sound card(s)
> > ## and then run `update-modules' command.
> > ## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
> > ##
> > ##  ALSA portion
> > ## alias snd-card-0 snd-interwave
> > alias snd-card-0 snd-hda-intel
> > ## alias snd-card-1 snd-ens1371
> > ##  OSS/Free portion
> > ## alias sound-slot-0 snd-card-0
> > ## alias sound-slot-1 snd-card-1
> > ##
> >
> > # OSS/Free portion - card #1
> > alias sound-service-0-0 snd-mixer-oss
> > alias sound-service-0-1 snd-seq-oss
> > alias sound-service-0-3 snd-pcm-oss
> > alias sound-service-0-8 snd-seq-oss
> > alias sound-service-0-12 snd-pcm-oss
> > ##  OSS/Free portion - card #2
> > ## alias sound-service-1-0 snd-mixer-oss
> > ## alias sound-service-1-3 snd-pcm-oss
> > ## alias sound-service-1-12 snd-pcm-oss
> >
> > alias /dev/mixer snd-mixer-oss
> > alias /dev/dsp snd-pcm-oss
> > alias /dev/midi snd-seq-oss
> >
> > # Set this to the correct number of cards.
> > options snd cards_limit=1
> > camille ~ #
> >
> 
> This looks pretty reasonable.
> 
> Please provide the following info:
> 
camille ~ # cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.9b.
Compiled on Oct 19 2005 for kernel 2.6.13-gentoo-r3 (SMP).


> 
> slocate snd- | grep modules
> 
camille ~ # slocate snd- | grep modules
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/oss/snd-mixer-oss.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/oss/snd-pcm-oss.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/seq/oss/snd-seq-oss.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/seq/snd-seq-device.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/seq/snd-seq-dummy.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/seq/snd-seq-midi-event.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/seq/snd-seq-midi.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/seq/snd-seq-virmidi.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/seq/snd-seq.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/snd-page-alloc.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/snd-pcm.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/snd-rawmidi.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/core/snd-timer.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/drivers/snd-virmidi.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-codec.ko
/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-page-alloc.ko
/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-pcm.ko
/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-rtctimer.ko
/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-timer.ko
/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/oss/snd-mixer-oss.ko
/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/oss/snd-pcm-oss.ko
/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq-device.ko
/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq-midi-event.ko
/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq.ko
/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/oss/snd-seq-oss.ko
/lib/modules/2.6.13-gentoo-r3/alsa-driver/pci/snd-intel8x0.ko
/lib/modules/2.6.13-gentoo-r3/alsa-driver/pci/ac97/snd-ac97-codec.ko
camille ~ #


> cat /usr/src/linux/.config | grep SND
> 


> camille ~ # cat /usr/src/linux/.config | grep SND
> CONFIG_SND=m
> CONFIG_SND_TIMER=m
> CONFIG_SND_PCM=m
> CONFIG_SND_RAWMIDI=m
> CONFIG_SND_SEQUENCER=m
> CONFIG_SND_SEQ_DUMMY=m
> CONFIG_SND_OSSEMUL=y
> CONFIG_SND_MIXER_OSS=m
> CONFIG_SND_PCM_OSS=m
> CONFIG_SND_SEQUENCER_OSS=y
> # CONFIG_SND_RTCTIMER is not set
> # CONFIG_SND_VERBOSE_PRINTK is not set
> # CONFIG_SND_DEBUG is not set
> # CONFIG_SND_DUMMY is not set
> CONFIG_SND_VIRMIDI=m
> # CONFIG_SND_MTPAV is not set
> # CONFIG_SND_SERIAL_U16550 is not set
> # CONFIG_SND_MPU401 is not set
> # CONFIG_SND_AD1816A is not set
> # CONFIG_SND_AD1848 is not set
> # CONFIG_SND_CS4231 is not set
> # CONFIG_SND_CS4232 is not set
> # CONFIG_SND_CS4236 is not set
> # CONFIG_SND_ES968 is not set
> # CONFIG_SND_ES1688 is not set
> # CONFIG_SND_ES18XX is not set
> # CONFIG_SND_GUSCLASSIC is not set
> # CONFIG_SND_GUSEXTREME is not set
> # CONFIG_SND_GUSMAX is not set
> # CONFIG_SND_INTERWAVE is not set
> # CONFIG_SND_INTERWAVE_STB is not set
> # CONFIG_SND_OPTI92X_AD1848 is not set
> # CONFIG_SND_OPTI92X_CS4231 is not set
> # CONFIG_SND_OPTI93X is not set
> # CONFIG_SND_SB8 is not set
> # CONFIG_SND_SB16 is not set
> # CONFIG_SND_SBAWE is not set
> # CONFIG_SND_WAVEFRONT is not set
> # CONFIG_SND_ALS100 is not set
> # CONFIG_SND_AZT2320 is not set
> # CONFIG_SND_CMI8330 is not set
> # CONFIG_SND_DT019X is not set
> # CONFIG_SND_OPL3SA2 is not set
> # CONFIG_SND_SGALAXY is not set
> # CONFIG_SND_SSCAPE is not set
> # CONFIG_SND_ALI5451 is not set
> # CONFIG_SND_ATIIXP is not set
> # CONFIG_SND_ATIIXP_MODEM is not set
> # CONFIG_SND_AU8810 is not set
> # CONFIG_SND_AU8820 is not set
> # CONFIG_SND_AU8830 is not set
> # CONFIG_SND_AZT3328 is not set
> # CONFIG_SND_BT87X is not set
> # CONFIG_SND_CS46XX is not set
> # CONFIG_SND_CS4281 is not set
> # CONFIG_SND_EMU10K1 is not set
> # CONFIG_SND_EMU10K1X is not set
> # CONFIG_SND_CA0106 is not set
> # CONFIG_SND_KORG1212 is not set
> # CONFIG_SND_MIXART is not set
> # CONFIG_SND_NM256 is not set
> # CONFIG_SND_RME32 is not set
> # CONFIG_SND_RME96 is not set
> # CONFIG_SND_RME9652 is not set
> # CONFIG_SND_HDSP is not set
> # CONFIG_SND_HDSPM is not set
> # CONFIG_SND_TRIDENT is not set
> # CONFIG_SND_YMFPCI is not set
> # CONFIG_SND_ALS4000 is not set
> # CONFIG_SND_CMIPCI is not set
> # CONFIG_SND_ENS1370 is not set
> # CONFIG_SND_ENS1371 is not set
> # CONFIG_SND_ES1938 is not set
> # CONFIG_SND_ES1968 is not set
> # CONFIG_SND_MAESTRO3 is not set
> # CONFIG_SND_FM801 is not set
> # CONFIG_SND_ICE1712 is not set
> # CONFIG_SND_ICE1724 is not set
> # CONFIG_SND_INTEL8X0 is not set
> # CONFIG_SND_INTEL8X0M is not set
> # CONFIG_SND_SONICVIBES is not set
> # CONFIG_SND_VIA82XX is not set
> # CONFIG_SND_VIA82XX_MODEM is not set
> # CONFIG_SND_VX222 is not set
> CONFIG_SND_HDA_INTEL=m
> # CONFIG_SND_USB_AUDIO is not set
> # CONFIG_SND_USB_USX2Y is not set
> # CONFIG_SND_VXPOCKET is not set
> # CONFIG_SND_PDAUDIOCF is not set
> 
> cat /etc/modprobe.conf

camille ~ # cat /etc/modprobe.conf
### This file is automatically generated by modules-update
#
# Please do not edit this file directly. If you want to change or add
# anything please take a look at /etc/modules.conf and read
# the manpage for modules-update.
#
alias binfmt-204 binfmt_aout
alias binfmt-263 binfmt_aout
alias binfmt-264 binfmt_aout
alias binfmt-267 binfmt_aout
alias binfmt-387 binfmt_aout
alias binfmt-332 iBCS
alias binfmt--310 binfmt_java
alias block-major-1-* rd
alias block-major-2-* floppy
alias block-major-3-* ide-probe-mod
alias block-major-7-* loop
alias block-major-8-* sd_mod
alias block-major-9-* md
alias block-major-11-* sr_mod
alias block-major-13-* xd
alias block-major-15-* cdu31a
alias block-major-16-* gscd
alias block-major-17-* optcd
alias block-major-18-* sjcd
alias block-major-20-* mcdx
alias block-major-22-* ide-probe-mod
alias block-major-23-* mcd
alias block-major-24-* sonycd535
alias block-major-25-* sbpcd
alias block-major-26-* sbpcd
alias block-major-27-* sbpcd
alias block-major-29-* aztcd
alias block-major-32-* cm206
alias block-major-33-* ide-probe-mod
alias block-major-34-* ide-probe-mod
alias block-major-37-* ide-tape
alias block-major-44-* ftl
alias block-major-46-* pcd
alias block-major-47-* pf
alias block-major-56-* ide-probe-mod
alias block-major-57-* ide-probe-mod
alias block-major-58-* lvm-mod
alias block-major-88-* ide-probe-mod
alias block-major-89-* ide-probe-mod
alias block-major-90-* ide-probe-mod
alias block-major-91-* ide-probe-mod
alias block-major-93-* nftl
alias block-major-113-* viocd
alias char-major-4-* serial
alias char-major-5-* serial
alias char-major-6-* lp
alias char-major-9-* st
alias char-major-10-0 busmouse
alias char-major-10-2 msbusmouse
alias char-major-10-3 atixlmouse
alias char-major-10-130 wdt
alias char-major-10-131 wdt
alias char-major-10-135 rtc
alias char-major-10-139 openprom
alias char-major-10-144 nvram
alias char-major-10-157 applicom
alias char-major-10-175 agpgart
alias char-major-10-184 microcode
alias char-major-10-200 tun
alias char-major-10-250 hci_vhci
alias char-major-13-* input
alias char-major-13-0 joydev
alias char-major-13-32 mousedev
alias char-major-14-* soundcore
alias char-major-19-* cyclades
alias char-major-20-* cyclades
alias char-major-21-* sg
alias char-major-22-* pcxx
alias char-major-23-* pcxx
alias char-major-27-* zftape
alias char-major-34-* scc
alias char-major-35-* tclmidi
alias char-major-36-* netlink
alias char-major-37-* ide-tape
alias char-major-48-* riscom8
alias char-major-49-* riscom8
alias char-major-57-* esp
alias char-major-58-* esp
alias char-major-63-* kdebug
alias char-major-90-* mtdchar
alias char-major-96-* pt
alias char-major-97-* pg
alias char-major-99-* ppdev
alias char-major-107-* 3dfx
alias char-major-108-* ppp_generic
alias char-major-109-* lvm-mod
alias char-major-161-* ircomm-tty
alias char-major-171-* raw1394
alias char-major-195-* NVdriver
alias char-major-200-* vxspec
alias char-major-206-* osst
alias char-major-216-* rfcomm
alias dos msdos
alias dummy0 dummy
alias dummy1 dummy
alias iso9660 isofs
alias md-personality-1 linear
alias md-personality-2 raid0
alias md-personality-3 raid1
alias md-personality-4 raid5
alias md-personality-7 multipath
alias net-pf-1 unix
alias net-pf-2 ipv4
alias net-pf-4 ipx
alias net-pf-5 appletalk
alias net-pf-15 af_key
alias net-pf-17 af_packet
alias net-pf-31 bluez
alias netalias-2 ip_alias
alias irlan0 irlan
alias irda-dongle-0 tekram
alias irda-dongle-1 esi
alias irda-dongle-2 actisys
alias irda-dongle-3 actisys
alias irda-dongle-4 girbil
alias irda-dongle-5 litelink
alias irda-dongle-6 airport
alias irda-dongle-7 old_belkin
alias bt-proto-0 l2cap
alias bt-proto-2 sco
alias bt-proto-3 rfcomm
alias bt-proto-4 bnep
alias plip0 plip
alias plip1 plip
alias tunl0 ipip
alias cipcb0 cipcb
alias cipcb1 cipcb
alias cipcb2 cipcb
alias cipcb3 cipcb
alias ppp0 ppp
alias ppp1 ppp
alias slip0 slip
alias slip1 slip
alias tty-ldisc-1 slip
alias tty-ldisc-3 ppp_async
alias tty-ldisc-11 irtty
alias tty-ldisc-14 ppp_synctty
alias tty-ldisc-15 hci_uart
alias ppp-compress-18 ppp_mppe
alias ppp-compress-21 bsd_comp
alias ppp-compress-24 ppp_deflate
alias ppp-compress-26 ppp_deflate
alias parport_lowlevel parport_pc
alias usbdevfs usbcore
alias xfrm-type-2-50 esp4
alias xfrm-type-2-51 ah4
alias xfrm-type-2-108 ipcomp
alias xfrm-type-10-50 esp6
alias xfrm-type-10-51 ah6
alias xfrm-type-10-108 ipcomp6
alias cipher_null crypto_null
alias digest_null crypto_null
alias compress_null crypto_null
alias sha384 sha512
alias char-major-81-* bttv
alias /dev/ppp ppp_generic
alias loop-xfer-gen-0 loop_gen
alias loop-xfer-3 loop_fish2
alias loop-xfer-gen-10 loop_gen
alias cipher-2 des
alias cipher-3 fish2
alias cipher-4 blowfish
alias cipher-6 idea
alias cipher-7 serp6f
alias cipher-8 mars6
alias cipher-11 rc62
alias cipher-15 dfc2
alias cipher-16 rijndael
alias cipher-17 rc5
alias char-major-89-* i2c-dev
alias /dev/nvidiactl NVdriver
alias char-major-116-* snd
alias snd-card-0 snd-hda-intel
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss
alias binfmt-0064 binfmt_aout
options sb io=0x220 irq=7 dma=1 dma16=5 mpu_io=0x330
options snd cards_limit=1
install /dev/svga /sbin/modprobe svgalib_helper; /bin/true
install binfmt-0000 /bin/true
install char-major-10 /bin/true
install char-major-10-1 /bin/true
install dummy0 /sbin/modprobe -o dummy0 --ignore-install dummy
install dummy1 /sbin/modprobe -o dummy1 --ignore-install dummy
install eth0 /bin/true
install net-pf-10 /bin/true
install net-pf-19 /bin/true
install net-pf-3 /bin/true
install net-pf-6 /bin/true
install scsi_hostadapter /bin/true
camille ~ #


> Good luck,
> Mark


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/20/05, Michael Sullivan <michael@espersunited.com> wrote:
> On Thu, 2005-10-20 at 07:24 -0700, Mark Knecht wrote:

> > >
> > > camille ~ # uname -a
> > > Linux camille 2.6.13-gentoo-r3 #1 SMP Thu Oct 20 08:22:11 CDT 2005 i686
> > > Intel(R) Celeron(R) CPU 2.66GHz GenuineIntel GNU/Linux
> >
> > Possibly an SMP issue? Is this a dual Celeron system? Is there such a
> > thing as a Hper Threading Celeron?
>
> I don't know anything about SMP.

It's multi-processor stuff. It's been known in the past to cause
problems for certain sound chips, at least when the drivers forst come
out. Please disable it.

su -
cd /usr/src/linux
make menuconfig

Under 'Processor Type and Features' turn off SMP.

Then possibly stay in make menuconfig, or do by hand, for sound
adjustment recommendations below.

> >
> >
> > > camille ~ # lspci
> >
> > > 0000:00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> > > Family) High Definition Audio Controller (rev 03)
> >
> >
> > > camille ~ # lsmod
> > > Module                  Size  Used by
> > <SNIP>
> > > snd_pcm                52932  0
> > > snd_timer              15764  1 snd_pcm
> > > snd                    31748  2 snd_pcm,snd_timer
> > > snd_page_alloc          5460  1 snd_pcm
> > <SNIP>
> >
> > Clearly nothing close to enough stuff is loaded as modules. Either you
> > built it into the kernel or the modules weren't loaded. It's probably
> > the latter since it doesn't find your card.
> >
>
> I compiled support for the sound card as a module.
>
> >
<SNIP>
> >
> > Please provide the following info:
> >
> camille ~ # cat /proc/asound/version
> Advanced Linux Sound Architecture Driver Version 1.0.9b.
> Compiled on Oct 19 2005 for kernel 2.6.13-gentoo-r3 (SMP).
>
>

> > cat /usr/src/linux/.config | grep SND
> >
>
>
> > camille ~ # cat /usr/src/linux/.config | grep SND
> > CONFIG_SND=m
> > CONFIG_SND_TIMER=m
> > CONFIG_SND_PCM=m
> > CONFIG_SND_RAWMIDI=m
> > CONFIG_SND_SEQUENCER=m
> > CONFIG_SND_SEQ_DUMMY=m
> > CONFIG_SND_OSSEMUL=y
> > CONFIG_SND_MIXER_OSS=m
> > CONFIG_SND_PCM_OSS=m
> > CONFIG_SND_SEQUENCER_OSS=y
> > # CONFIG_SND_RTCTIMER is not set
> > # CONFIG_SND_VERBOSE_PRINTK is not set
> > # CONFIG_SND_DEBUG is not set
> > # CONFIG_SND_DUMMY is not set
> > CONFIG_SND_VIRMIDI=m
> > # CONFIG_SND_MTPAV is not set
> > # CONFIG_SND_SERIAL_U16550 is not set
> > # CONFIG_SND_MPU401 is not set

<SNIP>

> > # CONFIG_SND_VX222 is not set
> > CONFIG_SND_HDA_INTEL=m
> > # CONFIG_SND_USB_AUDIO is not set
> > # CONFIG_SND_USB_USX2Y is not set
> > # CONFIG_SND_VXPOCKET is not set
> > # CONFIG_SND_PDAUDIOCF is not set


I will recommend that you make adjustments to the above settings. You
can edit the .config file by hand or use make menuconfig. Here are the
settings I would recommend. NOTE: Do NOT change the later sections
that choose the card. Only change the first part that changes the Alsa
system itself:

mark@lightning ~ $ cat /usr/src/linux-2.6.13-gentoo-r3/.config | grep SND
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_MPU401_UART=m
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
CONFIG_SND_RME9652=m
CONFIG_SND_HDSP=m
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
CONFIG_SND_ICE1712=m
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_HDA_INTEL is not set
CONFIG_SND_USB_AUDIO=m
# CONFIG_SND_USB_USX2Y is not set
mark@lightning ~ $


After that is done you will need to recomiple the kernel.

cd /usr/src/linux
make && make modules_install
mount /boot
cp arch/i386/boot/bzImage /boot/bzImage-2.6.13-gentoo-r3

Adjust /boot/grub/grub.conf if required, reboot and test.

If lsmod doesn't show more modules then please do the following

/etc/init.d/alsasound stop

rmmod any remaining sound modules

/etc/init.d/alsasound start

and return the Alsa part of dmesg.

NOTE: Holly may be very correct about needing i2c.

Good luck,
Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

> su -
> cd /usr/src/linux
> make menuconfig
> 
> Under 'Processor Type and Features' turn off SMP.
> 
> Then possibly stay in make menuconfig, or do by hand, for sound
> adjustment recommendations below.
> 
> > >
> > >
> > > > camille ~ # lspci
> > >
> > > > 0000:00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> > > > Family) High Definition Audio Controller (rev 03)
> > >
> > >
> > > > camille ~ # lsmod
> > > > Module                  Size  Used by
> > > <SNIP>
> > > > snd_pcm                52932  0
> > > > snd_timer              15764  1 snd_pcm
> > > > snd                    31748  2 snd_pcm,snd_timer
> > > > snd_page_alloc          5460  1 snd_pcm
> > > <SNIP>
> > >
> > > Clearly nothing close to enough stuff is loaded as modules. Either you
> > > built it into the kernel or the modules weren't loaded. It's probably
> > > the latter since it doesn't find your card.
> > >
> >
> > I compiled support for the sound card as a module.
> >
> > >
> <SNIP>
> > >
> > > Please provide the following info:
> > >
> > camille ~ # cat /proc/asound/version
> > Advanced Linux Sound Architecture Driver Version 1.0.9b.
> > Compiled on Oct 19 2005 for kernel 2.6.13-gentoo-r3 (SMP).
> >
> >
> 
> > > cat /usr/src/linux/.config | grep SND
> > >
> >
> >
> > > camille ~ # cat /usr/src/linux/.config | grep SND
> > > CONFIG_SND=m
> > > CONFIG_SND_TIMER=m
> > > CONFIG_SND_PCM=m
> > > CONFIG_SND_RAWMIDI=m
> > > CONFIG_SND_SEQUENCER=m
> > > CONFIG_SND_SEQ_DUMMY=m
> > > CONFIG_SND_OSSEMUL=y
> > > CONFIG_SND_MIXER_OSS=m
> > > CONFIG_SND_PCM_OSS=m
> > > CONFIG_SND_SEQUENCER_OSS=y
> > > # CONFIG_SND_RTCTIMER is not set
> > > # CONFIG_SND_VERBOSE_PRINTK is not set
> > > # CONFIG_SND_DEBUG is not set
> > > # CONFIG_SND_DUMMY is not set
> > > CONFIG_SND_VIRMIDI=m
> > > # CONFIG_SND_MTPAV is not set
> > > # CONFIG_SND_SERIAL_U16550 is not set
> > > # CONFIG_SND_MPU401 is not set
> 
> <SNIP>
> 
> > > # CONFIG_SND_VX222 is not set
> > > CONFIG_SND_HDA_INTEL=m
> > > # CONFIG_SND_USB_AUDIO is not set
> > > # CONFIG_SND_USB_USX2Y is not set
> > > # CONFIG_SND_VXPOCKET is not set
> > > # CONFIG_SND_PDAUDIOCF is not set
> 
> 
> I will recommend that you make adjustments to the above settings. You
> can edit the .config file by hand or use make menuconfig. Here are the
> settings I would recommend. NOTE: Do NOT change the later sections
> that choose the card. Only change the first part that changes the Alsa
> system itself:
> 
> mark@lightning ~ $ cat /usr/src/linux-2.6.13-gentoo-r3/.config | grep SND
> CONFIG_SND=m
> CONFIG_SND_TIMER=m
> CONFIG_SND_PCM=m
> CONFIG_SND_HWDEP=m
> CONFIG_SND_RAWMIDI=m
> CONFIG_SND_SEQUENCER=m
> # CONFIG_SND_SEQ_DUMMY is not set
> CONFIG_SND_OSSEMUL=y
> CONFIG_SND_MIXER_OSS=m
> CONFIG_SND_PCM_OSS=m
> CONFIG_SND_SEQUENCER_OSS=y
> # CONFIG_SND_RTCTIMER is not set
> # CONFIG_SND_VERBOSE_PRINTK is not set
> # CONFIG_SND_DEBUG is not set
> CONFIG_SND_MPU401_UART=m
> # CONFIG_SND_DUMMY is not set
> # CONFIG_SND_VIRMIDI is not set
> # CONFIG_SND_MTPAV is not set
> # CONFIG_SND_SERIAL_U16550 is not set
> # CONFIG_SND_MPU401 is not set
> CONFIG_SND_AC97_CODEC=m
> # CONFIG_SND_ALI5451 is not set
> # CONFIG_SND_ATIIXP is not set
> # CONFIG_SND_ATIIXP_MODEM is not set
> # CONFIG_SND_AU8810 is not set
> # CONFIG_SND_AU8820 is not set
> # CONFIG_SND_AU8830 is not set
> # CONFIG_SND_AZT3328 is not set
> # CONFIG_SND_BT87X is not set
> # CONFIG_SND_CS46XX is not set
> # CONFIG_SND_CS4281 is not set
> # CONFIG_SND_EMU10K1 is not set
> # CONFIG_SND_EMU10K1X is not set
> # CONFIG_SND_CA0106 is not set
> # CONFIG_SND_KORG1212 is not set
> # CONFIG_SND_MIXART is not set
> # CONFIG_SND_NM256 is not set
> # CONFIG_SND_RME32 is not set
> # CONFIG_SND_RME96 is not set
> CONFIG_SND_RME9652=m
> CONFIG_SND_HDSP=m
> # CONFIG_SND_HDSPM is not set
> # CONFIG_SND_TRIDENT is not set
> # CONFIG_SND_YMFPCI is not set
> # CONFIG_SND_ALS4000 is not set
> # CONFIG_SND_CMIPCI is not set
> # CONFIG_SND_ENS1370 is not set
> # CONFIG_SND_ENS1371 is not set
> # CONFIG_SND_ES1938 is not set
> # CONFIG_SND_ES1968 is not set
> # CONFIG_SND_MAESTRO3 is not set
> # CONFIG_SND_FM801 is not set
> CONFIG_SND_ICE1712=m
> # CONFIG_SND_ICE1724 is not set
> CONFIG_SND_INTEL8X0=m
> # CONFIG_SND_INTEL8X0M is not set
> # CONFIG_SND_SONICVIBES is not set
> # CONFIG_SND_VIA82XX is not set
> # CONFIG_SND_VIA82XX_MODEM is not set
> # CONFIG_SND_VX222 is not set
> # CONFIG_SND_HDA_INTEL is not set
> CONFIG_SND_USB_AUDIO=m
> # CONFIG_SND_USB_USX2Y is not set
> mark@lightning ~ $
> 
> 
> After that is done you will need to recomiple the kernel.
> 
> cd /usr/src/linux
> make && make modules_install
> mount /boot
> cp arch/i386/boot/bzImage /boot/bzImage-2.6.13-gentoo-r3
> 
> Adjust /boot/grub/grub.conf if required, reboot and test.
> 
> If lsmod doesn't show more modules then please do the following
> 
> /etc/init.d/alsasound stop
> 
> rmmod any remaining sound modules
> 
> /etc/init.d/alsasound start
> 
> and return the Alsa part of dmesg.
> 
> NOTE: Holly may be very correct about needing i2c.
> 
> Good luck,
> Mark

I think I've done everything you said to, but it still doesn't work.
Here's my kernel config:

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.13-gentoo-r3
# Fri Oct 21 10:09:36 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_EMBEDDED=y
# CONFIG_KALLSYMS is not set
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
CONFIG_M486=y
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=4
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_F00F_BUG=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_ALIGNMENT_16=y
# CONFIG_HPET_TIMER is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
# CONFIG_REGPARM is not set
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_PHYSICAL_START=0x100000
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_SLEEP_PROC_SLEEP is not set
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_ASUS=m
CONFIG_ACPI_IBM=m
CONFIG_ACPI_TOSHIBA=m
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_X86_PM_TIMER is not set
CONFIG_ACPI_CONTAINER=m

#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=m
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
CONFIG_APM_DO_ENABLE=y
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_RTC_IS_GMT is not set
# CONFIG_APM_ALLOW_INTS is not set
CONFIG_APM_REAL_MODE_POWER_OFF=y

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=m
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=m
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_POWERNOW_K6=m
CONFIG_X86_POWERNOW_K7=m
CONFIG_X86_POWERNOW_K7_ACPI=y
CONFIG_X86_POWERNOW_K8=m
CONFIG_X86_POWERNOW_K8_ACPI=y
CONFIG_X86_GX_SUSPMOD=m
CONFIG_X86_SPEEDSTEP_CENTRINO=m
# CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI is not set
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
CONFIG_X86_SPEEDSTEP_ICH=m
CONFIG_X86_SPEEDSTEP_SMI=m
CONFIG_X86_P4_CLOCKMOD=m
CONFIG_X86_CPUFREQ_NFORCE2=m
CONFIG_X86_LONGRUN=m
CONFIG_X86_LONGHAUL=m

#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
CONFIG_X86_SPEEDSTEP_LIB=m
# CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
# CONFIG_PCI_LEGACY_PROC is not set
# CONFIG_PCI_NAMES is not set
# CONFIG_PCI_DEBUG is not set
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
CONFIG_EISA=y
CONFIG_EISA_VLB_PRIMING=y
CONFIG_EISA_PCI_EISA=y
CONFIG_EISA_VIRTUAL_ROOT=y
# CONFIG_EISA_NAMES is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCCARD (PCMCIA/CardBus) support
#
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=m
CONFIG_PD6729=m
CONFIG_I82092=m
CONFIG_I82365=m
CONFIG_TCIC=m
CONFIG_PCMCIA_PROBE=y
CONFIG_PCCARD_NONSTATIC=m

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_IP_TCPDIAG=y
# CONFIG_IP_TCPDIAG_IPV6 is not set
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_BIC=y
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_INET6_TUNNEL=m
CONFIG_IPV6_TUNNEL=m
# CONFIG_NETFILTER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
CONFIG_VLAN_8021Q=m
# CONFIG_DECNET is not set
CONFIG_LLC=y
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
# CONFIG_BT_CMTP is not set
CONFIG_BT_HIDP=m

#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_BCSP_TXCRC=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_PC_SUPERIO=y
CONFIG_PARPORT_PC_PCMCIA=m
CONFIG_PARPORT_NOT_PC=y
# CONFIG_PARPORT_GSC is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_ISAPNP=y
# CONFIG_PNPBIOS is not set
CONFIG_PNPACPI=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
CONFIG_BLK_DEV_XD=m
CONFIG_PARIDE=m
CONFIG_PARIDE_PARPORT=m

#
# Parallel IDE high-level drivers
#
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m

#
# Parallel IDE protocol modules
#
CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=m
CONFIG_PARIDE_BPCK6=m
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
CONFIG_PARIDE_EPATC8=y
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRIQ=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
CONFIG_CISS_SCSI_TAPE=y
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_UMEM=m
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_SX8=m
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=8192
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_LBD=y
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
CONFIG_IOSCHED_DEADLINE=y
# CONFIG_IOSCHED_CFQ is not set
CONFIG_ATA_OVER_ETH=m

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECS=m
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=m
# CONFIG_BLK_DEV_IDESCSI is not set
CONFIG_IDE_TASK_IOCTL=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_CMD640_ENHANCED=y
CONFIG_BLK_DEV_IDEPNP=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
CONFIG_BLK_DEV_OPTI621=y
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_AEC62XX=y
CONFIG_BLK_DEV_ALI15X3=y
# CONFIG_WDC_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
CONFIG_BLK_DEV_ATIIXP=y
CONFIG_BLK_DEV_CMD64X=y
CONFIG_BLK_DEV_TRIFLEX=y
CONFIG_BLK_DEV_CY82C693=y
CONFIG_BLK_DEV_CS5520=y
CONFIG_BLK_DEV_CS5530=y
CONFIG_BLK_DEV_HPT34X=y
# CONFIG_HPT34X_AUTODMA is not set
CONFIG_BLK_DEV_HPT366=y
CONFIG_BLK_DEV_SC1200=y
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_IT821X is not set
CONFIG_BLK_DEV_NS87415=y
CONFIG_BLK_DEV_PDC202XX_OLD=y
# CONFIG_PDC202XX_BURST is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
CONFIG_PDC202XX_FORCE=y
CONFIG_BLK_DEV_SVWKS=y
CONFIG_BLK_DEV_SIIMAGE=m
CONFIG_BLK_DEV_SIS5513=y
CONFIG_BLK_DEV_SLC90E66=y
CONFIG_BLK_DEV_TRM290=y
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_ARM is not set
CONFIG_IDE_CHIPSETS=y

#
# Note: most of these also require special kernel boot parameters
#
CONFIG_BLK_DEV_4DRIVES=y
CONFIG_BLK_DEV_ALI14XX=y
CONFIG_BLK_DEV_DTC2278=y
CONFIG_BLK_DEV_HT6560B=y
CONFIG_BLK_DEV_QD65XX=y
CONFIG_BLK_DEV_UMC8672=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_IVB=y
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_ISCSI_ATTRS=m

#
# SCSI low-level drivers
#
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_7000FASST=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AHA152X=m
CONFIG_SCSI_AHA1542=m
CONFIG_SCSI_AHA1740=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=32
CONFIG_AIC7XXX_RESET_DELAY_MS=5000
CONFIG_AIC7XXX_PROBE_EISA_VL=y
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_AIC7XXX_OLD is not set
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=5000
# CONFIG_AIC79XX_ENABLE_RD_STRM is not set
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
CONFIG_SCSI_DPT_I2O=m
CONFIG_SCSI_IN2000=m
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
# CONFIG_MEGARAID_LEGACY is not set
CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_AHCI=m
CONFIG_SCSI_SATA_SVW=m
CONFIG_SCSI_ATA_PIIX=m
CONFIG_SCSI_SATA_NV=m
CONFIG_SCSI_SATA_PROMISE=m
CONFIG_SCSI_SATA_QSTOR=m
CONFIG_SCSI_SATA_SX4=m
CONFIG_SCSI_SATA_SIL=m
CONFIG_SCSI_SATA_SIS=m
CONFIG_SCSI_SATA_ULI=m
CONFIG_SCSI_SATA_VIA=m
CONFIG_SCSI_SATA_VITESSE=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
CONFIG_SCSI_DMX3191D=m
CONFIG_SCSI_DTC3280=m
CONFIG_SCSI_EATA=m
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
CONFIG_SCSI_EATA_LINKED_COMMANDS=y
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
CONFIG_SCSI_INIA100=m
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
CONFIG_SCSI_NCR53C406A=m
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
# CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set
CONFIG_SCSI_IPR=m
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
CONFIG_SCSI_PAS16=m
CONFIG_SCSI_PSI240I=m
CONFIG_SCSI_QLOGIC_FAS=m
CONFIG_SCSI_QLOGIC_FC=m
# CONFIG_SCSI_QLOGIC_FC_FIRMWARE is not set
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLOGIC_1280_1040=y
CONFIG_SCSI_QLA2XXX=y
CONFIG_SCSI_QLA21XX=m
CONFIG_SCSI_QLA22XX=m
CONFIG_SCSI_QLA2300=m
CONFIG_SCSI_QLA2322=m
CONFIG_SCSI_QLA6312=m
# CONFIG_SCSI_QLA24XX is not set
# CONFIG_SCSI_LPFC is not set
CONFIG_SCSI_SIM710=m
CONFIG_53C700_IO_MAPPED=y
CONFIG_SCSI_SYM53C416=m
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_T128=m
CONFIG_SCSI_U14_34F=m
CONFIG_SCSI_U14_34F_TAGGED_QUEUE=y
CONFIG_SCSI_U14_34F_LINKED_COMMANDS=y
CONFIG_SCSI_U14_34F_MAX_TAGS=8
CONFIG_SCSI_ULTRASTOR=m
CONFIG_SCSI_NSP32=m
# CONFIG_SCSI_DEBUG is not set

#
# PCMCIA SCSI adapter support
#
CONFIG_PCMCIA_AHA152X=m
CONFIG_PCMCIA_FDOMAIN=m
CONFIG_PCMCIA_NINJA_SCSI=m
CONFIG_PCMCIA_QLOGIC=m
CONFIG_PCMCIA_SYM53C500=m

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID5=m
CONFIG_MD_RAID6=m
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=m
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
CONFIG_DM_MULTIPATH_EMC=m
CONFIG_BLK_DEV_DM_BBR=m

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set

#
# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=m

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set
CONFIG_IEEE1394_EXTRA_CONFIG_ROMS=y
CONFIG_IEEE1394_CONFIG_ROM_IP1394=y
# CONFIG_IEEE1394_EXPORT_FULL_API is not set

#
# Device Drivers
#
# CONFIG_IEEE1394_PCILYNX is not set
CONFIG_IEEE1394_OHCI1394=m

#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
CONFIG_IEEE1394_ETH1394=m
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_CMP=m
# CONFIG_IEEE1394_AMDTP is not set

#
# I2O device support
#
CONFIG_I2O=m
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_CONFIG=m
CONFIG_I2O_CONFIG_OLD_IOCTL=y
# CONFIG_I2O_BUS is not set
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m

#
# Network device support
#
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
CONFIG_NET_SB1000=m

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_EL1=m
CONFIG_EL2=m
CONFIG_ELPLUS=m
CONFIG_EL16=m
CONFIG_EL3=m
CONFIG_3C515=m
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
CONFIG_LANCE=m
CONFIG_NET_VENDOR_SMC=y
CONFIG_WD80x3=m
CONFIG_ULTRA=m
CONFIG_ULTRA32=m
CONFIG_SMC9194=m
CONFIG_NET_VENDOR_RACAL=y
# CONFIG_NI5010 is not set
CONFIG_NI52=m
CONFIG_NI65=m

#
# Tulip family network device support
#
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_TULIP=m
CONFIG_TULIP_MWI=y
CONFIG_TULIP_MMIO=y
CONFIG_TULIP_NAPI=y
CONFIG_TULIP_NAPI_HW_MITIGATION=y
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
CONFIG_PCMCIA_XIRCOM=m
# CONFIG_PCMCIA_XIRTULIP is not set
CONFIG_AT1700=m
CONFIG_DEPCA=m
CONFIG_HP100=m
CONFIG_NET_ISA=y
CONFIG_E2100=m
CONFIG_EWRK3=m
CONFIG_EEXPRESS=m
CONFIG_EEXPRESS_PRO=m
CONFIG_HPLAN_PLUS=m
CONFIG_HPLAN=m
CONFIG_LP486E=m
CONFIG_ETH16I=m
CONFIG_NE2000=m
CONFIG_ZNET=m
CONFIG_SEEQ8005=m
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
CONFIG_AMD8111_ETH=m
# CONFIG_AMD8111E_NAPI is not set
CONFIG_ADAPTEC_STARFIRE=m
# CONFIG_ADAPTEC_STARFIRE_NAPI is not set
CONFIG_AC3200=m
CONFIG_APRICOT=m
CONFIG_B44=m
CONFIG_FORCEDETH=m
CONFIG_CS89x0=m
CONFIG_DGRS=m
# CONFIG_EEPRO100 is not set
CONFIG_E100=m
CONFIG_LNE390=m
CONFIG_FEALNX=m
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_NE3210=m
CONFIG_ES3210=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
CONFIG_8139TOO_TUNE_TWISTER=y
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_SIS900=m
CONFIG_EPIC100=m
CONFIG_SUNDANCE=m
CONFIG_SUNDANCE_MMIO=y
CONFIG_TLAN=m
CONFIG_VIA_RHINE=m
CONFIG_VIA_RHINE_MMIO=y
CONFIG_NET_POCKET=y
CONFIG_ATP=m
CONFIG_DE600=m
CONFIG_DE620=m

#
# Ethernet (1000 Mbit)
#
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
CONFIG_DL2K=m
CONFIG_E1000=m
# CONFIG_E1000_NAPI is not set
CONFIG_NS83820=m
CONFIG_HAMACHI=m
CONFIG_YELLOWFIN=m
CONFIG_R8169=m
# CONFIG_R8169_NAPI is not set
CONFIG_R8169_VLAN=y
CONFIG_SKGE=m
# CONFIG_SK98LIN is not set
CONFIG_VIA_VELOCITY=m
CONFIG_TIGON3=m
# CONFIG_BNX2 is not set

#
# Ethernet (10000 Mbit)
#
CONFIG_IXGB=m
# CONFIG_IXGB_NAPI is not set
CONFIG_S2IO=m
# CONFIG_S2IO_NAPI is not set
# CONFIG_2BUFF_MODE is not set

#
# Token Ring devices
#
CONFIG_TR=y
CONFIG_IBMTR=m
CONFIG_IBMOL=m
CONFIG_IBMLS=m
CONFIG_3C359=m
CONFIG_TMS380TR=m
CONFIG_TMSPCI=m
CONFIG_SKISA=m
CONFIG_PROTEON=m
CONFIG_ABYSS=m
CONFIG_SMCTR=m

#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y

#
# Obsolete Wireless cards support (pre-802.11)
#
CONFIG_STRIP=m
CONFIG_ARLAN=m
CONFIG_WAVELAN=m
CONFIG_PCMCIA_WAVELAN=m
CONFIG_PCMCIA_NETWAVE=m

#
# Wireless 802.11 Frequency Hopping cards support
#
CONFIG_PCMCIA_RAYCS=m

#
# Wireless 802.11b ISA/PCI cards support
#
CONFIG_AIRO=m
CONFIG_HERMES=m
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
CONFIG_PCI_HERMES=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m

#
# Wireless 802.11b Pcmcia/Cardbus cards support
#
CONFIG_PCMCIA_HERMES=m
CONFIG_AIRO_CS=m
CONFIG_PCMCIA_ATMEL=m
CONFIG_PCMCIA_WL3501=m

#
# Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
#
CONFIG_PRISM54=m
CONFIG_NET_WIRELESS=y

#
# PCMCIA network device support
#
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=m
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_PCMCIA_PCNET=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_PCMCIA_SMC91C92=m
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_PCMCIA_AXNET=m
CONFIG_PCMCIA_IBMTR=m

#
# Wan interfaces
#
CONFIG_WAN=y
CONFIG_HOSTESS_SV11=m
CONFIG_COSA=m
CONFIG_DSCC4=m
CONFIG_DSCC4_PCISYNC=y
CONFIG_DSCC4_PCI_RST=y
CONFIG_LANMEDIA=m
CONFIG_SEALEVEL_4021=m
CONFIG_SYNCLINK_SYNCPPP=m
CONFIG_HDLC=m
CONFIG_HDLC_RAW=y
CONFIG_HDLC_RAW_ETH=y
CONFIG_HDLC_CISCO=y
CONFIG_HDLC_FR=y
CONFIG_HDLC_PPP=y

#
# X.25/LAPB support is disabled
#
CONFIG_PCI200SYN=m
CONFIG_WANXL=m
CONFIG_PC300=m
CONFIG_PC300_MLPPP=y
CONFIG_N2=m
CONFIG_C101=m
CONFIG_FARSYNC=m
CONFIG_DLCI=m
CONFIG_DLCI_COUNT=24
CONFIG_DLCI_MAX=8
CONFIG_SDLA=m
CONFIG_SBNI=m
CONFIG_SBNI_MULTILINE=y
CONFIG_FDDI=y
CONFIG_DEFXX=m
CONFIG_SKFP=m
CONFIG_HIPPI=y
CONFIG_ROADRUNNER=m
# CONFIG_ROADRUNNER_LARGE_RINGS is not set
CONFIG_PLIP=m
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPPOE=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y
CONFIG_NET_FC=y
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
CONFIG_ISDN=y

#
# Old ISDN4Linux
#
# CONFIG_ISDN_I4L is not set

#
# CAPI subsystem
#
CONFIG_ISDN_CAPI=y
# CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON is not set
CONFIG_ISDN_CAPI_MIDDLEWARE=y
CONFIG_ISDN_CAPI_CAPI20=m
CONFIG_ISDN_CAPI_CAPIFS_BOOL=y
CONFIG_ISDN_CAPI_CAPIFS=m

#
# CAPI hardware drivers
#

#
# Active AVM cards
#
CONFIG_CAPI_AVM=y
CONFIG_ISDN_DRV_AVMB1_B1ISA=m
CONFIG_ISDN_DRV_AVMB1_B1PCI=m
CONFIG_ISDN_DRV_AVMB1_B1PCIV4=y
CONFIG_ISDN_DRV_AVMB1_T1ISA=m
CONFIG_ISDN_DRV_AVMB1_B1PCMCIA=m
CONFIG_ISDN_DRV_AVMB1_AVM_CS=m
CONFIG_ISDN_DRV_AVMB1_T1PCI=m
CONFIG_ISDN_DRV_AVMB1_C4=m

#
# Active Eicon DIVA Server cards
#
CONFIG_CAPI_EICON=y
CONFIG_ISDN_DIVAS=m
CONFIG_ISDN_DIVAS_BRIPCI=y
CONFIG_ISDN_DIVAS_PRIPCI=y
CONFIG_ISDN_DIVAS_DIVACAPI=m
CONFIG_ISDN_DIVAS_USERIDI=m
CONFIG_ISDN_DIVAS_MAINT=m

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_SUNKBD=m
CONFIG_KEYBOARD_LKKBD=m
CONFIG_KEYBOARD_XTKBD=m
CONFIG_KEYBOARD_NEWTON=m
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_INPORT=m
CONFIG_MOUSE_ATIXL=y
CONFIG_MOUSE_LOGIBM=m
CONFIG_MOUSE_PC110PAD=m
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=m
CONFIG_SERIO_CT82C710=m
CONFIG_SERIO_PARKBD=m
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_ACPI=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y
# CONFIG_SERIAL_8250_FOURPORT is not set
# CONFIG_SERIAL_8250_ACCENT is not set
# CONFIG_SERIAL_8250_BOCA is not set
# CONFIG_SERIAL_8250_HUB6 is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
# CONFIG_PRINTER is not set
CONFIG_PPDEV=m
# CONFIG_TIPAR is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
CONFIG_NVRAM=m
CONFIG_RTC=m
# CONFIG_GEN_RTC is not set
CONFIG_DTLK=m
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set

#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
CONFIG_MWAVE=m
CONFIG_RAW_DRIVER=m
# CONFIG_HPET is not set
CONFIG_MAX_RAW_DEVS=256
# CONFIG_HANGCHECK_TIMER is not set

#
# TPM devices
#
# CONFIG_TCG_TPM is not set

#
# I2C support
#
CONFIG_I2C=m
# CONFIG_I2C_CHARDEV is not set

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_ELEKTOR is not set
CONFIG_I2C_I801=m
CONFIG_I2C_I810=m
CONFIG_I2C_PIIX4=m
# CONFIG_I2C_ISA is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set
# CONFIG_I2C_SENSOR is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Hardware Monitoring support
#
CONFIG_HWMON=y
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_FSCPOS is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_SOFT_CURSOR=y
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_MODE_HELPERS is not set
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_FB_VESA_STD=y
# CONFIG_FB_VESA_TNG is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
CONFIG_FB_SPLASH=y

#
# Speakup console speech
#
CONFIG_SPEAKUP=y
CONFIG_SPEAKUP_ACNTSA=y
CONFIG_SPEAKUP_ACNTPC=y
CONFIG_SPEAKUP_APOLLO=y
CONFIG_SPEAKUP_AUDPTR=y
CONFIG_SPEAKUP_BNS=y
CONFIG_SPEAKUP_DECTLK=y
CONFIG_SPEAKUP_DECEXT=y
# CONFIG_SPEAKUP_DECPC is not set
CONFIG_SPEAKUP_DTLK=y
CONFIG_SPEAKUP_KEYPC=y
CONFIG_SPEAKUP_LTLK=y
CONFIG_SPEAKUP_SFTSYN=y
CONFIG_SPEAKUP_SPKOUT=y
CONFIG_SPEAKUP_TXPRT=y

#
# Enter the 3 to 6 character keyword from the list above, or none for no
default synthesizer on boot up.
#
CONFIG_SPEAKUP_DEFAULT="none"

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# ISA devices
#
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_DT019X is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set

#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
CONFIG_SND_HDA_INTEL=m

#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set

#
# PCMCIA devices
#
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_PDAUDIOCF is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_SL811_HCD=m
# CONFIG_USB_SL811_CS is not set

#
# USB Device Class drivers
#
CONFIG_USB_AUDIO=m

#
# USB Bluetooth TTY can only be used with disabled Bluetooth subsystem
#
# CONFIG_USB_MIDI is not set
CONFIG_USB_ACM=m
# CONFIG_USB_PRINTER is not set

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be
needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
# CONFIG_USB_STORAGE_USBAT is not set
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y

#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
CONFIG_USB_AIPTEK=m
CONFIG_USB_WACOM=m
# CONFIG_USB_ACECAD is not set
CONFIG_USB_KBTAB=m
# CONFIG_USB_POWERMATE is not set
CONFIG_USB_MTOUCH=m
# CONFIG_USB_ITMTOUCH is not set
CONFIG_USB_EGALAX=m
CONFIG_USB_XPAD=m
CONFIG_USB_ATI_REMOTE=m
# CONFIG_USB_KEYSPAN_REMOTE is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m

#
# USB Host-to-Host Cables
#
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_GENESYS=y
CONFIG_USB_NET1080=y
CONFIG_USB_PL2301=y
CONFIG_USB_KC2190=y

#
# Intelligent USB Devices/Gadgets
#
# CONFIG_USB_ARMLINUX is not set
# CONFIG_USB_EPSON2888 is not set
# CONFIG_USB_ZAURUS is not set
CONFIG_USB_CDCETHER=y

#
# USB Network Adapters
#
CONFIG_USB_AX8817X=y
# CONFIG_USB_ZD1201 is not set
CONFIG_USB_MON=y

#
# USB port drivers
#
CONFIG_USB_USS720=m

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_AIRPRIME is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_CP2101 is not set
# CONFIG_USB_SERIAL_CYPRESS_M8 is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_GARMIN is not set
CONFIG_USB_SERIAL_IPW=m
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_HP4X is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_TI is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OPTION is not set
CONFIG_USB_SERIAL_OMNINET=m

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
CONFIG_USB_AUERSWALD=m
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TEST is not set

#
# USB DSL modem support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# MMC/SD Card support
#
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
CONFIG_MMC_BLOCK=m
CONFIG_MMC_WBSD=m

#
# InfiniBand support
#
CONFIG_INFINIBAND=m
# CONFIG_INFINIBAND_USER_VERBS is not set
CONFIG_INFINIBAND_MTHCA=m
# CONFIG_INFINIBAND_MTHCA_DEBUG is not set
CONFIG_INFINIBAND_IPOIB=m
# CONFIG_INFINIBAND_IPOIB_DEBUG is not set

#
# SN Devices
#

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
# CONFIG_JFS_SECURITY is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y

#
# XFS support
#
CONFIG_XFS_FS=y
CONFIG_XFS_EXPORT=y
CONFIG_XFS_RT=y
CONFIG_XFS_QUOTA=y
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
# CONFIG_QUOTA is not set
CONFIG_QUOTACTL=y
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_TMPFS_XATTR is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_SQUASHFS=y
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
# CONFIG_SQUASHFS_VMALLOC is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_LOG_BUF_SHIFT=15
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_BUGVERBOSE is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_4KSTACKS is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_TEST is not set

#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set

#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y


Here's uname -a:

camille ~ # uname -a
Linux camille 2.6.13-gentoo-r3 #1 Fri Oct 21 10:18:35 CDT 2005 i686
Intel(R) Celeron(R) CPU 2.66GHz GenuineIntel GNU/Linux

Here's lsmod (if you need it):

camille ~ # lsmod
Module                  Size  Used by
nfs                    73516  2
ipv6                  177344  8
nfsd                   74536  9
lockd                  44168  3 nfs,nfsd
sunrpc                 95556  14 nfs,nfsd,lockd
parport_pc             27140  0
parport                21160  1 parport_pc
floppy                 44180  0
rtc                     7864  0
i2c_i801                5804  0
i2c_core               10896  1 i2c_i801
evdev                   6368  0
e100                   24672  0
mii                     2688  1 e100
dm_mirror              14004  0
dm_mod                 36700  1 dm_mirror
ata_piix                6052  2
ahci                    7908  0
sata_qstor              6084  0
sata_vsc                4932  0
sata_uli                4352  0
sata_sis                4224  0
sata_sx4                9540  0
sata_nv                 5636  0
sata_via                5380  0
sata_svw                4644  0
sata_sil                5892  0
sata_promise            6948  0
libata                 27428  12
ata_piix,ahci,sata_qstor,sata_vsc,sata_uli,sata_sis,sata_sx4,sata_nv,sata_via,sata_svw,sata_sil,sata_promise
sbp2                   16648  0
ohci1394               25620  0
ieee1394               57272  2 sbp2,ohci1394
sl811_hcd               8640  0
ohci_hcd               14372  0
uhci_hcd               23984  0
usb_storage            43648  0
usbhid                 25760  0
ehci_hcd               21992  0
usbcore                74652  7
sl811_hcd,ohci_hcd,uhci_hcd,usb_storage,usbhid,ehci_hcd

I didn't see my sound modules there, so I tried to
start /etc/init.d/alsasound and got this:

 ^[[32;01m*^[[0m Loading ALSA modules ...
 ^[[32;01m*^[[0m   Loading: snd-card-0 ...
WARNING: Error inserting snd_page_alloc
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-page-alloc.ko):
Invalid module format
WARNING: Error inserting snd
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
format
WARNING: Error inserting snd_timer
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-timer.ko): Invalid
module format
WARNING: Error inserting snd_pcm
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-pcm.ko): Invalid
module format
WARNING: Error inserting snd_hda_codec
(/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-codec.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_hda_intel
(/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-intel.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
^[[A^[[84G  ^[[34;01m[ ^[[31;01m!!^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   Loading: snd-seq-oss ...
WARNING: Error inserting snd
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
format
WARNING: Error inserting snd_seq_device
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq-device.ko):
Invalid module format
WARNING: Error inserting snd_timer
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-timer.ko): Invalid
module format
WARNING: Error inserting snd_seq
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq.ko):
Invalid module format
WARNING: Error inserting snd_seq_midi_event
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq-midi-event.ko): Invalid module format
FATAL: Error inserting snd_seq_oss
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/oss/snd-seq-oss.ko): Invalid module format
^[[A^[[84G  ^[[34;01m[ ^[[31;01m!!^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   Loading: snd-pcm-oss ...
WARNING: Error inserting snd
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
format
WARNING: Error inserting snd_mixer_oss
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/oss/snd-mixer-oss.ko):
Invalid module format
WARNING: Error inserting snd_page_alloc
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-page-alloc.ko):
Invalid module format
WARNING: Error inserting snd_timer
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-timer.ko): Invalid
module format
WARNING: Error inserting snd_pcm
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-pcm.ko): Invalid
module format
FATAL: Error inserting snd_pcm_oss
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/oss/snd-pcm-oss.ko):
Invalid module format
^[[A^[[84G  ^[[34;01m[ ^[[31;01m!!^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   Loading: snd-mixer-oss ...
WARNING: Error inserting snd
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
format
FATAL: Error inserting snd_mixer_oss
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/oss/snd-mixer-oss.ko):
Invalid module format
^[[A^[[84G  ^[[34;01m[ ^[[31;01m!!^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   Loading: snd-seq-oss ...
WARNING: Error inserting snd
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
format
WARNING: Error inserting snd_seq_device
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq-device.ko):
Invalid module format
WARNING: Error inserting snd_timer
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-timer.ko): Invalid
module format
WARNING: Error inserting snd_seq
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq.ko):
Invalid module format
WARNING: Error inserting snd_seq_midi_event
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq-midi-event.ko): Invalid module format
FATAL: Error inserting snd_seq_oss
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/oss/snd-seq-oss.ko): Invalid module format
^[[A^[[84G  ^[[34;01m[ ^[[31;01m!!^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   Loading: snd-pcm-oss ...
WARNING: Error inserting snd
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
format
WARNING: Error inserting snd_mixer_oss
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/oss/snd-mixer-oss.ko):
Invalid module format
WARNING: Error inserting snd_page_alloc
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-page-alloc.ko):
Invalid module format
WARNING: Error inserting snd_timer
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-timer.ko): Invalid
module format
WARNING: Error inserting snd_pcm
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-pcm.ko): Invalid
module format
FATAL: Error inserting snd_pcm_oss
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/oss/snd-pcm-oss.ko):
Invalid module format
^[[A^[[84G  ^[[34;01m[ ^[[31;01m!!^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   Loading: snd-mixer-oss ...
WARNING: Error inserting snd
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
format
FATAL: Error inserting snd_mixer_oss
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/oss/snd-mixer-oss.ko):
Invalid module format
^[[A^[[84G  ^[[34;01m[ ^[[31;01m!!^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   Loading: snd-seq ...
WARNING: Error inserting snd
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
format
WARNING: Error inserting snd_seq_device
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq-device.ko):
Invalid module format
WARNING: Error inserting snd_timer
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-timer.ko): Invalid
module format
FATAL: Error inserting snd_seq
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq.ko):
Invalid module format
^[[A^[[84G  ^[[34;01m[ ^[[31;01m!!^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   Loading: snd-seq ...
WARNING: Error inserting snd
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
format
WARNING: Error inserting snd_seq_device
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq-device.ko):
Invalid module format
WARNING: Error inserting snd_timer
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-timer.ko): Invalid
module format
FATAL: Error inserting snd_seq
(/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/seq/snd-seq.ko):
Invalid module format
^[[A^[[84G  ^[[34;01m[ ^[[31;01m!!^[[34;01m ]^[[0m
 ^[[31;01m*^[[0m ERROR: Failed to load necessary drivers
^[[A^[[84G  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m Restoring Mixer Levels ...
 ^[[33;01m*^[[0m No mixer config in /etc/asound.state, you have to unmute
your card!
^[[A^[[84G  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/21/05, Michael Sullivan <michael@espersunited.com> wrote:
<SNIP>
> > Good luck,
> > Mark
>
> I think I've done everything you said to, but it still doesn't work.
> Here's my kernel config:

Indeed, it appears at first glance that you did.
<SNIP>
> Here's uname -a:
>
> camille ~ # uname -a
> Linux camille 2.6.13-gentoo-r3 #1 Fri Oct 21 10:18:35 CDT 2005 i686
> Intel(R) Celeron(R) CPU 2.66GHz GenuineIntel GNU/Linux

Good. No more SMP. Unfortunately, no better results either.

>
> Here's lsmod (if you need it):
>
> camille ~ # lsmod
> Module                  Size  Used by
<SNIP>
> i2c_i801                5804  0
> i2c_core               10896  1 i2c_i801

OK, i2c seems to be loaded. That's good.

<SNIP>
>
> I didn't see my sound modules there, so I tried to
> start /etc/init.d/alsasound and got this:

Yes, they weren't loaded.

>
>  ^[[32;01m*^[[0m Loading ALSA modules ...
>  ^[[32;01m*^[[0m   Loading: snd-card-0 ...
> WARNING: Error inserting snd_page_alloc
> (/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-page-alloc.ko):
> Invalid module format
> WARNING: Error inserting snd
> (/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
> format
<SNIP>

The only time I've seen anything like this is when I messed up my
linux link in the /usr/src directory. You haven't done that as you
have only a single kernel source tree. These messages imply that ALL
of alsa is messed up, not just your device driver. That see,s
completely wrong.

I cannot explain it, other than to say I'd probably do the following
if this was my box:

1) ls -al /lib/modules  and ensure that there is only
/lib/modules/2.6.13-gentoo-r3

2) rm -rf /lib/modules/2.6.13-gentoo-r3  to completely remove all the
existing modules.

3) cd /usr/src/linux

4) make clean

5) make && make modules_install

6) Copy over the new kernel, check that /lib/modules has the new
modules, then reboot and test again.

My real suspicion here is that 2.6.14-gentoo-r3 doesn't actually have
support for this card, or that the card is not well supported at all.
Using Google I get very few results for snd_intel_hda

Cheers,
Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Fri, 2005-10-21 at 11:25 -0700, Mark Knecht wrote:
> On 10/21/05, Michael Sullivan <michael@espersunited.com> wrote:
> <SNIP>
> > > Good luck,
> > > Mark
> >
> > I think I've done everything you said to, but it still doesn't work.
> > Here's my kernel config:
> 
> Indeed, it appears at first glance that you did.
> <SNIP>
> > Here's uname -a:
> >
> > camille ~ # uname -a
> > Linux camille 2.6.13-gentoo-r3 #1 Fri Oct 21 10:18:35 CDT 2005 i686
> > Intel(R) Celeron(R) CPU 2.66GHz GenuineIntel GNU/Linux
> 
> Good. No more SMP. Unfortunately, no better results either.
> 
> >
> > Here's lsmod (if you need it):
> >
> > camille ~ # lsmod
> > Module                  Size  Used by
> <SNIP>
> > i2c_i801                5804  0
> > i2c_core               10896  1 i2c_i801
> 
> OK, i2c seems to be loaded. That's good.
> 
> <SNIP>
> >
> > I didn't see my sound modules there, so I tried to
> > start /etc/init.d/alsasound and got this:
> 
> Yes, they weren't loaded.
> 
> >
> >  ^[[32;01m*^[[0m Loading ALSA modules ...
> >  ^[[32;01m*^[[0m   Loading: snd-card-0 ...
> > WARNING: Error inserting snd_page_alloc
> > (/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-page-alloc.ko):
> > Invalid module format
> > WARNING: Error inserting snd
> > (/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
> > format
> <SNIP>
> 
> The only time I've seen anything like this is when I messed up my
> linux link in the /usr/src directory. You haven't done that as you
> have only a single kernel source tree. These messages imply that ALL
> of alsa is messed up, not just your device driver. That see,s
> completely wrong.
> 
> I cannot explain it, other than to say I'd probably do the following
> if this was my box:
> 
> 1) ls -al /lib/modules  and ensure that there is only
> /lib/modules/2.6.13-gentoo-r3
> 
> 2) rm -rf /lib/modules/2.6.13-gentoo-r3  to completely remove all the
> existing modules.
> 
> 3) cd /usr/src/linux
> 
> 4) make clean
> 
> 5) make && make modules_install
> 
> 6) Copy over the new kernel, check that /lib/modules has the new
> modules, then reboot and test again.
> 
> My real suspicion here is that 2.6.14-gentoo-r3 doesn't actually have
> support for this card, or that the card is not well supported at all.
> Using Google I get very few results for snd_intel_hda
> 
> Cheers,
> Mark
> 

OK.  Now that  I've replaced the modules I can modprobe my sound card,
but not I'm back to the problem of unmuting it.  Does alsamixer keep
detailed logs anywhere, or is there a means to unmute my card that
doesn't rely on alsamixer and does keep logs?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Fri, 2005-10-21 at 14:11 -0500, Michael Sullivan wrote:
> On Fri, 2005-10-21 at 11:25 -0700, Mark Knecht wrote:
> > On 10/21/05, Michael Sullivan <michael@espersunited.com> wrote:
> > <SNIP>
> > > > Good luck,
> > > > Mark
> > >
> > > I think I've done everything you said to, but it still doesn't work.
> > > Here's my kernel config:
> > 
> > Indeed, it appears at first glance that you did.
> > <SNIP>
> > > Here's uname -a:
> > >
> > > camille ~ # uname -a
> > > Linux camille 2.6.13-gentoo-r3 #1 Fri Oct 21 10:18:35 CDT 2005 i686
> > > Intel(R) Celeron(R) CPU 2.66GHz GenuineIntel GNU/Linux
> > 
> > Good. No more SMP. Unfortunately, no better results either.
> > 
> > >
> > > Here's lsmod (if you need it):
> > >
> > > camille ~ # lsmod
> > > Module                  Size  Used by
> > <SNIP>
> > > i2c_i801                5804  0
> > > i2c_core               10896  1 i2c_i801
> > 
> > OK, i2c seems to be loaded. That's good.
> > 
> > <SNIP>
> > >
> > > I didn't see my sound modules there, so I tried to
> > > start /etc/init.d/alsasound and got this:
> > 
> > Yes, they weren't loaded.
> > 
> > >
> > >  ^[[32;01m*^[[0m Loading ALSA modules ...
> > >  ^[[32;01m*^[[0m   Loading: snd-card-0 ...
> > > WARNING: Error inserting snd_page_alloc
> > > (/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-page-alloc.ko):
> > > Invalid module format
> > > WARNING: Error inserting snd
> > > (/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
> > > format
> > <SNIP>
> > 
> > The only time I've seen anything like this is when I messed up my
> > linux link in the /usr/src directory. You haven't done that as you
> > have only a single kernel source tree. These messages imply that ALL
> > of alsa is messed up, not just your device driver. That see,s
> > completely wrong.
> > 
> > I cannot explain it, other than to say I'd probably do the following
> > if this was my box:
> > 
> > 1) ls -al /lib/modules  and ensure that there is only
> > /lib/modules/2.6.13-gentoo-r3
> > 
> > 2) rm -rf /lib/modules/2.6.13-gentoo-r3  to completely remove all the
> > existing modules.
> > 
> > 3) cd /usr/src/linux
> > 
> > 4) make clean
> > 
> > 5) make && make modules_install
> > 
> > 6) Copy over the new kernel, check that /lib/modules has the new
> > modules, then reboot and test again.
> > 
> > My real suspicion here is that 2.6.14-gentoo-r3 doesn't actually have
> > support for this card, or that the card is not well supported at all.
> > Using Google I get very few results for snd_intel_hda
> > 
> > Cheers,
> > Mark
> > 
> 
> OK.  Now that  I've replaced the modules I can modprobe my sound card,
> but not I'm back to the problem of unmuting it.  Does alsamixer keep
> detailed logs anywhere, or is there a means to unmute my card that
> doesn't rely on alsamixer and does keep logs?
> 

I forgot to mention that when I try to use alsamixer to unmute my card I
get this:

camille ~ # alsamixer

alsamixer: function snd_mixer_load failed: Invalid argument

And when I try to use amixer:

camille ~ # amixer set Master 100% unmute
amixer: Mixer default load error: Invalid argument

Any hints?


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/21/05, Michael Sullivan <michael@espersunited.com> wrote:
> On Fri, 2005-10-21 at 11:25 -0700, Mark Knecht wrote:
<SNIP>
> > I cannot explain it, other than to say I'd probably do the following
> > if this was my box:
> >
> > 1) ls -al /lib/modules  and ensure that there is only
> > /lib/modules/2.6.13-gentoo-r3
> >
> > 2) rm -rf /lib/modules/2.6.13-gentoo-r3  to completely remove all the
> > existing modules.
> >
> > 3) cd /usr/src/linux
> >
> > 4) make clean
> >
> > 5) make && make modules_install
> >
> > 6) Copy over the new kernel, check that /lib/modules has the new
> > modules, then reboot and test again.
> >
> > My real suspicion here is that 2.6.14-gentoo-r3 doesn't actually have
> > support for this card, or that the card is not well supported at all.
> > Using Google I get very few results for snd_intel_hda
> >
> > Cheers,
> > Mark
> >
>
> OK.  Now that  I've replaced the modules I can modprobe my sound card,
> but not I'm back to the problem of unmuting it.  Does alsamixer keep
> detailed logs anywhere, or is there a means to unmute my card that
> doesn't rely on alsamixer and does keep logs?
>
Michael,
   Please clarify. Are you sating that the set of actions outlined
above worked? That would be a good step forward. Congrats.

   OK, as for unmuting the card, some cards work with alsamixer. Many do not.

   Can you provide the output of lsmod. I'd very much like to see the
drivers that are loaded.

   As you have been through the ringer on this one I suggest the following:

1) rm /etc/asound.state      This gets rid of old settings and allows
you to store clean stuff.

2) Run alsamixer and let us know what it says. If alsamixer doesn't
work then you may need to run amixer at the command line to unmute
your card. I'll let you slog through the man page on that one. amixer
commands can be placed in /etc/conf.d/local.start if needed. For
instance, possibly

amixer -c 0 unmute

NOTE: This will only work if the card is listed under /proc/asound/cards.

3) If alsamixer or amixer works at all then run

alsactrl store

which will store new data that was created by alsamixer. (And Alsa I suppose...)

As for logs from Alsa they should be in dmesg or /var/log/messages.

   You could also try doing /etc/init.d/alsasound stop and then start
from the command line and looking at what happens. In fact, it might
be wise to remove it from your default profile

rc-update del alsasound default

and start it by hand after booting until you get this all workign
correctly. This may impact Gnome/KDE so I'm not sure if it's a great
idea. Just a thought.

Hope this helps,
Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Fri, 2005-10-21 at 14:59 -0700, Mark Knecht wrote:
> On 10/21/05, Michael Sullivan <michael@espersunited.com> wrote:
> > On Fri, 2005-10-21 at 11:25 -0700, Mark Knecht wrote:
> <SNIP>
> > > I cannot explain it, other than to say I'd probably do the following
> > > if this was my box:
> > >
> > > 1) ls -al /lib/modules  and ensure that there is only
> > > /lib/modules/2.6.13-gentoo-r3
> > >
> > > 2) rm -rf /lib/modules/2.6.13-gentoo-r3  to completely remove all the
> > > existing modules.
> > >
> > > 3) cd /usr/src/linux
> > >
> > > 4) make clean
> > >
> > > 5) make && make modules_install
> > >
> > > 6) Copy over the new kernel, check that /lib/modules has the new
> > > modules, then reboot and test again.
> > >
> > > My real suspicion here is that 2.6.14-gentoo-r3 doesn't actually have
> > > support for this card, or that the card is not well supported at all.
> > > Using Google I get very few results for snd_intel_hda
> > >
> > > Cheers,
> > > Mark
> > >
> >
> > OK.  Now that  I've replaced the modules I can modprobe my sound card,
> > but not I'm back to the problem of unmuting it.  Does alsamixer keep
> > detailed logs anywhere, or is there a means to unmute my card that
> > doesn't rely on alsamixer and does keep logs?
> >
> Michael,
>    Please clarify. Are you sating that the set of actions outlined
> above worked? That would be a good step forward. Congrats.

Yes.  I can modprobe the card.  
> 
>    OK, as for unmuting the card, some cards work with alsamixer. Many do not.
> 
>    Can you provide the output of lsmod. I'd very much like to see the
> drivers that are loaded.

camille ~ # lsmod
Module                  Size  Used by
snd_pcm_oss            36064  0
snd_mixer_oss          12256  1 snd_pcm_oss
snd_seq_oss            21216  0
snd_seq_midi_event      2976  1 snd_seq_oss
snd_seq                30384  4 snd_seq_oss,snd_seq_midi_event
snd_seq_device          4588  2 snd_seq_oss,snd_seq
snd_hda_intel          10496  3
snd_hda_codec          57152  1 snd_hda_intel
snd_pcm                49928  4 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer              14404  3 snd_seq,snd_pcm
snd                    28644  13
snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
snd_page_alloc          6248  2 snd_hda_intel,snd_pcm
nfs                    73516  2
ipv6                  177344  8
nfsd                   74536  9
lockd                  44168  3 nfs,nfsd
sunrpc                 95556  14 nfs,nfsd,lockd
parport_pc             27140  0
parport                21160  1 parport_pc
floppy                 44180  0
rtc                     7864  0
i2c_i801                5804  0
i2c_core               10896  1 i2c_i801
evdev                   6368  0
e100                   24672  0
mii                     2688  1 e100
dm_mirror              14004  0
dm_mod                 36700  1 dm_mirror
ata_piix                6052  2
ahci                    7908  0
sata_qstor              6084  0
sata_vsc                4932  0
sata_uli                4352  0
sata_sis                4224  0
sata_sx4                9540  0
sata_nv                 5636  0
sata_via                5380  0
sata_svw                4644  0
sata_sil                5892  0
sata_promise            6948  0
libata                 27428  12
ata_piix,ahci,sata_qstor,sata_vsc,sata_uli,sata_sis,sata_sx4,sata_nv,sata_via,sata_svw,sata_sil,sata_promise
sbp2                   16648  0
ohci1394               25620  0
ieee1394               57272  2 sbp2,ohci1394
sl811_hcd               8640  0
ohci_hcd               14372  0
uhci_hcd               23984  0
usb_storage            43648  0
usbhid                 25760  0
ehci_hcd               21992  0
usbcore                74652  7
sl811_hcd,ohci_hcd,uhci_hcd,usb_storage,usbhid,ehci_hcd

> 
>    As you have been through the ringer on this one I suggest the following:
> 
> 1) rm /etc/asound.state      This gets rid of old settings and allows
> you to store clean stuff.

/etc/asound.state didn't exist, so I couldn't delete it.
> 
> 2) Run alsamixer and let us know what it says. 

camille ~ # alsamixer

alsamixer: function snd_mixer_load failed: Invalid argument

> If alsamixer doesn't
> work then you may need to run amixer at the command line to unmute
> your card. I'll let you slog through the man page on that one. amixer
> commands can be placed in /etc/conf.d/local.start if needed. For
> instance, possibly
> 
> amixer -c 0 unmute

camille ~ # amixer -c 0 unmute
amixer: Unknown command 'unmute'...

> 
> NOTE: This will only work if the card is listed under /proc/asound/cards.

camille ~ # cat /proc/asound/cards
0 [Intel          ]: HDA-Intel - HDA Intel
                     HDA Intel at 0xffac0000 irq 11

> 
> 3) If alsamixer or amixer works at all then run
> 
> alsactrl store
> 
> which will store new data that was created by alsamixer. (And Alsa I suppose...)
> 
> As for logs from Alsa they should be in dmesg or /var/log/messages.
> 
>    You could also try doing /etc/init.d/alsasound stop and then start
> from the command line and looking at what happens. In fact, it might
> be wise to remove it from your default profile
> 
> rc-update del alsasound default
> 
> and start it by hand after booting until you get this all workign
> correctly. This may impact Gnome/KDE so I'm not sure if it's a great
> idea. Just a thought.
> 
> Hope this helps,
> Mark
> 

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Holly Bostick]

Michael Sullivan schreef:
> On Fri, 2005-10-21 at 14:59 -0700, Mark Knecht wrote:
> 
> 
>> If alsamixer doesn't work then you may need to run amixer at the 
>> command line to unmute your card. I'll let you slog through the man
>>  page on that one. amixer commands can be placed in 
>> /etc/conf.d/local.start if needed. For instance, possibly
>> 
>> amixer -c 0 unmute
> 
> 
> camille ~ # amixer -c 0 unmute amixer: Unknown command 'unmute'...

Now, really, Michael, this is a bit silly; the program obviously works,
and doesn't even fall over your card, so the card is apparently working,
but you're stumped by the lack of the 'unmute' command (which is the
very least of all the problems you could encounter at this stage)?

amixer --help
Usage: amixer <options> command

Available options:
  -h,--help       this help
  -c,--card N     select the card
  -D,--device N   select the device, default 'default'
  -d,--debug      debug mode
  -n,--nocheck    do not perform range checking
  -v,--version    print version of this program
  -q,--quiet      be quiet
  -i,--inactive   show also inactive controls
  -a,--abstract L select abstraction level (none or basic)

Available commands:
  scontrols       show all mixer simple controls
  scontents       show contents of all mixer simple controls (default
command)
  sset sID P      set contents for one mixer simple control
  sget sID        get contents for one mixer simple control
  controls        show all controls for given card
  contents        show contents of all controls for given card
  cset cID P      set control contents for one control
  cget cID        get control contents for one control

Fine, the unmute command is not listed (perhaps it's been removed), just
use 'scontrols' or 'controls' instead and see if you can unmute the card
manually!

Then follow the rest of the instructions:
> 
>> 3) If alsamixer or amixer works at all then run
>> 
>> alsactrl store
>> 
>> which will store new data that was created by alsamixer. (And Alsa 
>> I suppose...)

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 00:46 +0200, Holly Bostick wrote:
> Michael Sullivan schreef:
> > On Fri, 2005-10-21 at 14:59 -0700, Mark Knecht wrote:
> > 
> > 
> >> If alsamixer doesn't work then you may need to run amixer at the 
> >> command line to unmute your card. I'll let you slog through the man
> >>  page on that one. amixer commands can be placed in 
> >> /etc/conf.d/local.start if needed. For instance, possibly
> >> 
> >> amixer -c 0 unmute
> > 
> > 
> > camille ~ # amixer -c 0 unmute amixer: Unknown command 'unmute'...
> 
> Now, really, Michael, this is a bit silly; the program obviously works,
> and doesn't even fall over your card, so the card is apparently working,
> but you're stumped by the lack of the 'unmute' command (which is the
> very least of all the problems you could encounter at this stage)?
> 
> amixer --help
> Usage: amixer <options> command
> 
> Available options:
>   -h,--help       this help
>   -c,--card N     select the card
>   -D,--device N   select the device, default 'default'
>   -d,--debug      debug mode
>   -n,--nocheck    do not perform range checking
>   -v,--version    print version of this program
>   -q,--quiet      be quiet
>   -i,--inactive   show also inactive controls
>   -a,--abstract L select abstraction level (none or basic)
> 
> Available commands:
>   scontrols       show all mixer simple controls
>   scontents       show contents of all mixer simple controls (default
> command)
>   sset sID P      set contents for one mixer simple control
>   sget sID        get contents for one mixer simple control
>   controls        show all controls for given card
>   contents        show contents of all controls for given card
>   cset cID P      set control contents for one control
>   cget cID        get control contents for one control
> 
> Fine, the unmute command is not listed (perhaps it's been removed), just
> use 'scontrols' or 'controls' instead and see if you can unmute the card
> manually!
> 
> Then follow the rest of the instructions:
> > 
> >> 3) If alsamixer or amixer works at all then run
> >> 
> >> alsactrl store
> >> 
> >> which will store new data that was created by alsamixer. (And Alsa 
> >> I suppose...)
> 
> Holly

According to "man amixer":

INVOKING
       amixer with no arguments will display the current mixer settings
for  the
       default soundcard and device. This is a good way to see a list of
the sim-
       ple mixer controls you can use.

Yet, when I issue:

camille ~ # amixer
amixer: Mixer default load error: Invalid argument

What argument(s) does it want?  The man page doesn't even list an
example of the syntax.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Holly Bostick]

Michael Sullivan schreef:
> On Sat, 2005-10-22 at 00:46 +0200, Holly Bostick wrote:
> 
>> Michael Sullivan schreef:
>> 
>>> On Fri, 2005-10-21 at 14:59 -0700, Mark Knecht wrote:
>>> 
>>> 
>>> 
>>>> If alsamixer doesn't work then you may need to run amixer at 
>>>> the command line to unmute your card. I'll let you slog through
>>>>  the man page on that one. amixer commands can be placed in 
>>>> /etc/conf.d/local.start if needed. For instance, possibly
>>>> 
>>>> amixer -c 0 unmute
>>> 
>>> 
>>> camille ~ # amixer -c 0 unmute amixer: Unknown command 
>>> 'unmute'...
>> 
>> Now, really, Michael, this is a bit silly; the program obviously 
>> works, and doesn't even fall over your card, so the card is 
>> apparently working, but you're stumped by the lack of the 'unmute' 
>> command (which is the very least of all the problems you could 
>> encounter at this stage)?
>> 

> According to "man amixer":
> 
> INVOKING amixer with no arguments will display the current mixer 
> settings for  the default soundcard and device. This is a good way to
>  see a list of the sim- ple mixer controls you can use.
> 
> Yet, when I issue:
> 
> camille ~ # amixer amixer: Mixer default load error: Invalid argument
> 
> 
> 
> What argument(s) does it want?  The man page doesn't even list an 
> example of the syntax.
> 

amixer amixer? That actually *isn't* a valid command, the command meant
is simply

amixer

And yes, the man page does tell you the syntax:

NAME
       amixer - command-line mixer for ALSA soundcard driver

SYNOPSIS
       amixer [-c card] [cmd]

That, there, under "SYNOPSIS" is the syntax

--help also lists the syntax:

amixer --help
Usage: amixer <options> command

That would be the syntax, there under 'Usage'.

Now if I just run 'amixer' with nothing after it, I get a whole lot of
info (partial):

 amixer
Simple mixer control 'Master',0
  Capabilities: pvolume
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Front Left: Playback 25 [81%]
  Front Right: Playback 25 [81%]
Simple mixer control '3D Control - Switch',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]
Simple mixer control 'PCM',0
  Capabilities: pvolume pswitch pswitch-joined cswitch
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Front Left: Playback 16 [52%] [on] Capture [off]
  Front Right: Playback 16 [52%] [on] Capture [off]
Simple mixer control 'Synth',0
  Capabilities: pvolume pswitch pswitch-joined cswitch
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Front Left: Playback 26 [84%] [on] Capture [on]
  Front Right: Playback 26 [84%] [on] Capture [on]

Try just 'amixer' or maybe 'amixer -c 0' and see if it tells you anything.

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 01:31 +0200, Holly Bostick wrote:
> Michael Sullivan schreef:
> > On Sat, 2005-10-22 at 00:46 +0200, Holly Bostick wrote:
> > 
> >> Michael Sullivan schreef:
> >> 
> >>> On Fri, 2005-10-21 at 14:59 -0700, Mark Knecht wrote:
> >>> 
> >>> 
> >>> 
> >>>> If alsamixer doesn't work then you may need to run amixer at 
> >>>> the command line to unmute your card. I'll let you slog through
> >>>>  the man page on that one. amixer commands can be placed in 
> >>>> /etc/conf.d/local.start if needed. For instance, possibly
> >>>> 
> >>>> amixer -c 0 unmute
> >>> 
> >>> 
> >>> camille ~ # amixer -c 0 unmute amixer: Unknown command 
> >>> 'unmute'...
> >> 
> >> Now, really, Michael, this is a bit silly; the program obviously 
> >> works, and doesn't even fall over your card, so the card is 
> >> apparently working, but you're stumped by the lack of the 'unmute' 
> >> command (which is the very least of all the problems you could 
> >> encounter at this stage)?
> >> 
> 
> > According to "man amixer":
> > 
> > INVOKING amixer with no arguments will display the current mixer 
> > settings for  the default soundcard and device. This is a good way to
> >  see a list of the sim- ple mixer controls you can use.
> > 
> > Yet, when I issue:
> > 
> > camille ~ # amixer amixer: Mixer default load error: Invalid argument
> > 
> > 
> > 
> > What argument(s) does it want?  The man page doesn't even list an 
> > example of the syntax.
> > 
> 
> amixer amixer? That actually *isn't* a valid command, the command meant
> is simply
> 
> amixer
> 
> And yes, the man page does tell you the syntax:
> 
> NAME
>        amixer - command-line mixer for ALSA soundcard driver
> 
> SYNOPSIS
>        amixer [-c card] [cmd]
> 
> That, there, under "SYNOPSIS" is the syntax
> 
> --help also lists the syntax:
> 
> amixer --help
> Usage: amixer <options> command
> 
> That would be the syntax, there under 'Usage'.
> 
> Now if I just run 'amixer' with nothing after it, I get a whole lot of
> info (partial):
> 
>  amixer
> Simple mixer control 'Master',0
>   Capabilities: pvolume
>   Playback channels: Front Left - Front Right
>   Limits: Playback 0 - 31
>   Front Left: Playback 25 [81%]
>   Front Right: Playback 25 [81%]
> Simple mixer control '3D Control - Switch',0
>   Capabilities: pswitch pswitch-joined
>   Playback channels: Mono
>   Mono: Playback [off]
> Simple mixer control 'PCM',0
>   Capabilities: pvolume pswitch pswitch-joined cswitch
>   Playback channels: Front Left - Front Right
>   Capture channels: Front Left - Front Right
>   Limits: Playback 0 - 31
>   Front Left: Playback 16 [52%] [on] Capture [off]
>   Front Right: Playback 16 [52%] [on] Capture [off]
> Simple mixer control 'Synth',0
>   Capabilities: pvolume pswitch pswitch-joined cswitch
>   Playback channels: Front Left - Front Right
>   Capture channels: Front Left - Front Right
>   Limits: Playback 0 - 31
>   Front Left: Playback 26 [84%] [on] Capture [on]
>   Front Right: Playback 26 [84%] [on] Capture [on]
> 
> Try just 'amixer' or maybe 'amixer -c 0' and see if it tells you anything.
> 
> Holly

camille ~ # amixer
amixer: Mixer default load error: Invalid argument

camille ~ # amixer -c 0
amixer: Mixer hw:0 load error: Invalid argument


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Holly Bostick]

Michael Sullivan schreef:
> On Sat, 2005-10-22 at 01:31 +0200, Holly Bostick wrote:
>>
>>Try just 'amixer' or maybe 'amixer -c 0' and see if it tells you anything.
>>
>>Holly
> 
> 
> camille ~ # amixer
> amixer: Mixer default load error: Invalid argument
> 
> camille ~ # amixer -c 0
> amixer: Mixer hw:0 load error: Invalid argument

Well it looks like all your modules are there, so something else "must"
be wrong:

Have you run alsaconf with the card active/working as it is now?

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 01:44 +0200, Holly Bostick wrote:
> Michael Sullivan schreef:
> > On Sat, 2005-10-22 at 01:31 +0200, Holly Bostick wrote:
> >>
> >>Try just 'amixer' or maybe 'amixer -c 0' and see if it tells you anything.
> >>
> >>Holly
> > 
> > 
> > camille ~ # amixer
> > amixer: Mixer default load error: Invalid argument
> > 
> > camille ~ # amixer -c 0
> > amixer: Mixer hw:0 load error: Invalid argument
> 
> Well it looks like all your modules are there, so something else "must"
> be wrong:
> 
> Have you run alsaconf with the card active/working as it is now?
> 
> Holly

I just did.  Afterwards, I tried to use amixer again:

camille ~ # amixer -c 0
amixer: Mixer hw:0 load error: Invalid argument


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Holly Bostick]

Michael Sullivan schreef:
> On Sat, 2005-10-22 at 01:44 +0200, Holly Bostick wrote:
>>>
>>>camille ~ # amixer
>>>amixer: Mixer default load error: Invalid argument
>>>
>>>camille ~ # amixer -c 0
>>>amixer: Mixer hw:0 load error: Invalid argument
>>
>>Well it looks like all your modules are there, so something else "must"
>>be wrong:
>>
>>Have you run alsaconf with the card active/working as it is now?
>>
> 
> I just did.  Afterwards, I tried to use amixer again:
> 
> camille ~ # amixer -c 0
> amixer: Mixer hw:0 load error: Invalid argument

Did you stop and restart alsasound to load alsaconf's changed settings?

Did alsaconf make any complaints when run?

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 02:12 +0200, Holly Bostick wrote:
> Michael Sullivan schreef:
> > On Sat, 2005-10-22 at 01:44 +0200, Holly Bostick wrote:
> >>>
> >>>camille ~ # amixer
> >>>amixer: Mixer default load error: Invalid argument
> >>>
> >>>camille ~ # amixer -c 0
> >>>amixer: Mixer hw:0 load error: Invalid argument
> >>
> >>Well it looks like all your modules are there, so something else "must"
> >>be wrong:
> >>
> >>Have you run alsaconf with the card active/working as it is now?
> >>
> > 
> > I just did.  Afterwards, I tried to use amixer again:
> > 
> > camille ~ # amixer -c 0
> > amixer: Mixer hw:0 load error: Invalid argument
> 
> Did you stop and restart alsasound to load alsaconf's changed settings?
> 
> Did alsaconf make any complaints when run?
> 
> Holly

camille ~ # /etc/init.d/alsasound restart
 * Storing ALSA Mixer Levels ...
/usr/sbin/alsactl: get_control:149: Cannot read control info
'2,0,0,Front Playback Volume,0': Invalid argument
[ !! ] * Unloading ALSA ...
[ ok ] * Unloading ALSA modules ...
[ ok ] * Loading ALSA modules ...
 *   Loading: snd-card-0 ...
[ ok ] *   Loading: snd-seq-oss ...
[ ok ] *   Loading: snd-pcm-oss ...
[ ok ] * Restoring Mixer Levels ...
 * No mixer config in /etc/asound.state, you have to unmute your card!
[ ok ]camille ~ # amixer -c 0
amixer: Mixer hw:0 load error: Invalid argument

I think alsaconf tried to run alsamixer, which failed, but it went by
too fast for me to see...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/21/05, Michael Sullivan <michael@espersunited.com> wrote:
> On Sat, 2005-10-22 at 02:12 +0200, Holly Bostick wrote:
> > Michael Sullivan schreef:
> > > On Sat, 2005-10-22 at 01:44 +0200, Holly Bostick wrote:
> > >>>
> > >>>camille ~ # amixer
> > >>>amixer: Mixer default load error: Invalid argument
> > >>>
> > >>>camille ~ # amixer -c 0
> > >>>amixer: Mixer hw:0 load error: Invalid argument
> > >>
> > >>Well it looks like all your modules are there, so something else "must"
> > >>be wrong:
> > >>
> > >>Have you run alsaconf with the card active/working as it is now?
> > >>
> > >
> > > I just did.  Afterwards, I tried to use amixer again:
> > >
> > > camille ~ # amixer -c 0
> > > amixer: Mixer hw:0 load error: Invalid argument
> >
> > Did you stop and restart alsasound to load alsaconf's changed settings?
> >
> > Did alsaconf make any complaints when run?
> >
> > Holly
>
> camille ~ # /etc/init.d/alsasound restart
>  * Storing ALSA Mixer Levels ...
> /usr/sbin/alsactl: get_control:149: Cannot read control info
> '2,0,0,Front Playback Volume,0': Invalid argument
> [ !! ] * Unloading ALSA ...
> [ ok ] * Unloading ALSA modules ...
> [ ok ] * Loading ALSA modules ...
>  *   Loading: snd-card-0 ...
> [ ok ] *   Loading: snd-seq-oss ...
> [ ok ] *   Loading: snd-pcm-oss ...
> [ ok ] * Restoring Mixer Levels ...
>  * No mixer config in /etc/asound.state, you have to unmute your card!
> [ ok ]camille ~ # amixer -c 0
> amixer: Mixer hw:0 load error: Invalid argument
>
> I think alsaconf tried to run alsamixer, which failed, but it went by
> too fast for me to see...

I'm tellin' ya. alsamixer is jsut a gui for amixer and amixer does not
work for every Alsa supported card. You need to find out from the Alsa
folks what is the supported mixer for this card.

If you have only one sound card in your system then running

amixer

is sufficient. -c is the option to tell it card 0,1,... when you have
more than one card.

I expect form the link I posted a while back that you need
Alsa-1.10.xxx to support this device....

- Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Richard Fish]

Mark Knecht wrote:

>I'm tellin' ya. alsamixer is jsut a gui for amixer and amixer does not
>work for every Alsa supported card. You need to find out from the Alsa
>folks what is the supported mixer for this card.
>  
>

Just an FYI, I also have an intel-hda (in my laptop).  Alsamixer 
supports it just fine, except that the stupid card doesn't provide a 
"Master Volume" control, so you have to adjust the speaker volume with 
the "Front" control.  Stupid card.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/21/05, Richard Fish <bigfish@asmallpond.org> wrote:
> Mark Knecht wrote:
>
> >I'm tellin' ya. alsamixer is jsut a gui for amixer and amixer does not
> >work for every Alsa supported card. You need to find out from the Alsa
> >folks what is the supported mixer for this card.
> >
> >
>
> Just an FYI, I also have an intel-hda (in my laptop).  Alsamixer
> supports it just fine, except that the stupid card doesn't provide a
> "Master Volume" control, so you have to adjust the speaker volume with
> the "Front" control.  Stupid card.
>
> -Richard

What kernel are you running? Can you give Michael a hint as to how you
set it up?

- Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Richard Fish]

Mark Knecht wrote:

>On 10/21/05, Richard Fish <bigfish@asmallpond.org> wrote:
>  
>
>>Mark Knecht wrote:
>>
>>    
>>
>>>I'm tellin' ya. alsamixer is jsut a gui for amixer and amixer does not
>>>work for every Alsa supported card. You need to find out from the Alsa
>>>folks what is the supported mixer for this card.
>>>
>>>
>>>      
>>>
>>Just an FYI, I also have an intel-hda (in my laptop).  Alsamixer
>>supports it just fine, except that the stupid card doesn't provide a
>>"Master Volume" control, so you have to adjust the speaker volume with
>>the "Front" control.  Stupid card.
>>
>>-Richard
>>    
>>
>
>What kernel are you running? Can you give Michael a hint as to how you
>set it up?
>  
>

Kernel version is from suspend2-sources-2.6.13-r5.  I didn't have to do 
anything special for setup though..."it just worked".

I suspect you are correct that it is a driver bug and a newer version of 
the driver would help.  Michael, sorry I haven't been following this 
thread closely, but have you tried a .14-rc kernel?  I just looked at 
vanilla-sources-2.6.14-rc5, and there seems to be some significant 
changes with the newest kernel.

Anyway, some basic information about my setup follows.  I can provide 
more if desired (particularly /etc/asound.state, ~/.asoundrc, or amixer 
output).

carcharias linux # lsmod
Module                  Size  Used by
...
snd_hda_intel          15872  1
snd_hda_codec          73536  1 snd_hda_intel
snd_pcm                78600  2 snd_hda_intel,snd_hda_codec
snd_timer              22212  1 snd_pcm
snd                    43192  6 
snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
soundcore               9056  1 snd
snd_page_alloc          9800  2 snd_hda_intel,snd_pcm
...

carcharias linux # emerge -vp alsa-lib alsa-utils alsa-tools alsa-headers
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild   R   ] media-libs/alsa-lib-1.0.9  +doc -jack 0 kB
[ebuild   R   ] media-sound/alsa-utils-1.0.9a-r1  +nls 0 kB
[ebuild   R   ] media-sound/alsa-tools-1.0.9  +X 0 kB
[ebuild   R   ] media-sound/alsa-headers-1.0.9b  0 kB

carcharias linux # lspci -n
...
00:1b.0 0403: 8086:2668 (rev 04)
...

carcharias linux # lspci -vv
...
00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) High Definition Audio Controller (rev 04)
        Subsystem: ASUSTeK Computer Inc. Unknown device 10c3
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size 08
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at febf8000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [60] Message Signalled Interrupts: 64bit+ 
Queue=0/0 Enable-
                Address: 0000000000000000  Data: 0000
        Capabilities: [70] Express Unknown type IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, 
ExtTag-
                Device: Latency L0s <64ns, L1 <1us
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed unknown, Width x0, ASPM unknown, 
Port 0
                Link: Latency L0s <64ns, L1 <1us
                Link: ASPM Disabled CommClk- ExtSynch-
                Link: Speed unknown, Width x0
        Capabilities: [100] Virtual Channel
        Capabilities: [130] Unknown (5)
...

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 00:53 -0700, Richard Fish wrote:
> Mark Knecht wrote:
> 
> >On 10/21/05, Richard Fish <bigfish@asmallpond.org> wrote:
> >  
> >
> >>Mark Knecht wrote:
> >>
> >>    
> >>
> >>>I'm tellin' ya. alsamixer is jsut a gui for amixer and amixer does not
> >>>work for every Alsa supported card. You need to find out from the Alsa
> >>>folks what is the supported mixer for this card.
> >>>
> >>>
> >>>      
> >>>
> >>Just an FYI, I also have an intel-hda (in my laptop).  Alsamixer
> >>supports it just fine, except that the stupid card doesn't provide a
> >>"Master Volume" control, so you have to adjust the speaker volume with
> >>the "Front" control.  Stupid card.
> >>
> >>-Richard
> >>    
> >>
> >
> >What kernel are you running? Can you give Michael a hint as to how you
> >set it up?
> >  
> >
> 
> Kernel version is from suspend2-sources-2.6.13-r5.  I didn't have to do 
> anything special for setup though..."it just worked".
> 
> I suspect you are correct that it is a driver bug and a newer version of 
> the driver would help.  Michael, sorry I haven't been following this 
> thread closely, but have you tried a .14-rc kernel?  I just looked at 
> vanilla-sources-2.6.14-rc5, and there seems to be some significant 
> changes with the newest kernel.
> 
> Anyway, some basic information about my setup follows.  I can provide 
> more if desired (particularly /etc/asound.state, ~/.asoundrc, or amixer 
> output).
> 
> carcharias linux # lsmod
> Module                  Size  Used by
> ...
> snd_hda_intel          15872  1
> snd_hda_codec          73536  1 snd_hda_intel
> snd_pcm                78600  2 snd_hda_intel,snd_hda_codec
> snd_timer              22212  1 snd_pcm
> snd                    43192  6 
> snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
> soundcore               9056  1 snd
> snd_page_alloc          9800  2 snd_hda_intel,snd_pcm
> ...
> 
> carcharias linux # emerge -vp alsa-lib alsa-utils alsa-tools alsa-headers
> These are the packages that I would merge, in order:
> Calculating dependencies ...done!
> [ebuild   R   ] media-libs/alsa-lib-1.0.9  +doc -jack 0 kB
> [ebuild   R   ] media-sound/alsa-utils-1.0.9a-r1  +nls 0 kB
> [ebuild   R   ] media-sound/alsa-tools-1.0.9  +X 0 kB
> [ebuild   R   ] media-sound/alsa-headers-1.0.9b  0 kB
> 
> carcharias linux # lspci -n
> ...
> 00:1b.0 0403: 8086:2668 (rev 04)
> ...
> 
> carcharias linux # lspci -vv
> ...
> 00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
> Family) High Definition Audio Controller (rev 04)
>         Subsystem: ASUSTeK Computer Inc. Unknown device 10c3
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 0, Cache Line Size 08
>         Interrupt: pin A routed to IRQ 16
>         Region 0: Memory at febf8000 (64-bit, non-prefetchable) [size=16K]
>         Capabilities: [50] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA 
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>         Capabilities: [60] Message Signalled Interrupts: 64bit+ 
> Queue=0/0 Enable-
>                 Address: 0000000000000000  Data: 0000
>         Capabilities: [70] Express Unknown type IRQ 0
>                 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, 
> ExtTag-
>                 Device: Latency L0s <64ns, L1 <1us
>                 Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
>                 Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
>                 Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
>                 Link: Supported Speed unknown, Width x0, ASPM unknown, 
> Port 0
>                 Link: Latency L0s <64ns, L1 <1us
>                 Link: ASPM Disabled CommClk- ExtSynch-
>                 Link: Speed unknown, Width x0
>         Capabilities: [100] Virtual Channel
>         Capabilities: [130] Unknown (5)
> ...
> 
> -Richard
> 

I built and rebooted with the vanilla kernel  2.6.14-rc5 and
started /etc/init.d/alsasound:

camille ~ # /etc/init.d/alsasound start
 * Loading ALSA modules ...
 *   Loading: snd-card-0 ...
[ ok ] *   Loading: snd-seq-oss ...
[ ok ] *   Loading: snd-pcm-oss ...
[ ok ] * Restoring Mixer Levels ...
 * No mixer config in /etc/asound.state, you have to unmute your card!
[ ok ]

I can modprobe snd-hda-intel successfully.

Here is lsmod:

camille ~ # lsmod
Module                  Size  Used by
snd_pcm_oss            36256  0
snd_mixer_oss          12224  1 snd_pcm_oss
snd_seq_oss            21280  0
snd_seq_midi_event      2976  1 snd_seq_oss
snd_seq                30384  4 snd_seq_oss,snd_seq_midi_event
snd_seq_device          4588  2 snd_seq_oss,snd_seq
snd_hda_intel          11328  0
snd_hda_codec          58816  1 snd_hda_intel
snd_pcm                49960  3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer              14436  2 snd_seq,snd_pcm
snd                    28676  9
snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
snd_page_alloc          6312  2 snd_hda_intel,snd_pcm
nfs                    73580  2
ipv6                  178784  8
nfsd                   74504  13
lockd                  44328  3 nfs,nfsd
sunrpc                 95868  10 nfs,nfsd,lockd
parport_pc             27204  0
parport                21128  1 parport_pc
floppy                 46436  0
rtc                     7864  0
i2c_i801                5804  0
i2c_core               10928  1 i2c_i801
e100                   24608  0
mii                     2624  1 e100
dm_mirror              14036  0
dm_mod                 36860  1 dm_mirror
ata_piix                6084  2
ahci                    7844  0
sata_qstor              6052  0
sata_vsc                4932  0
sata_uli                4256  0
sata_sis                4896  0
sata_sx4                9444  0
sata_nv                 5636  0
sata_via                5412  0
sata_svw                4644  0
sata_sil                5956  0
sata_promise            6852  0
libata                 28040  12
ata_piix,ahci,sata_qstor,sata_vsc,sata_uli,sata_sis,sata_sx4,sata_nv,sata_via,sata_svw,sata_sil,sata_promise
sbp2                   16900  0
ohci1394               25556  0
ieee1394               57592  2 sbp2,ohci1394
sl811_hcd               8672  0
ohci_hcd               14404  0
uhci_hcd               23760  0
usb_storage            44064  0
usbhid                 28576  0
ehci_hcd               22408  0
usbcore                75840  7
sl811_hcd,ohci_hcd,uhci_hcd,usb_storage,usbhid,ehci_hcd


camille ~ # emerge -vp alsa-lib alsa-utils alsa-tools

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] media-libs/alsa-lib-1.0.10_rc2  +doc +jack* 0 kB
[ebuild   R   ] media-sound/alsa-utils-1.0.10_rc2  +nls 0 kB
[ebuild   R   ] media-sound/alsa-tools-1.0.8-r1  +X 0 kB


camille ~ # lspci -vv
0000:00:00.0 Host bridge: Intel Corporation 915G/P/GV/GL/PL/910GL Processor to I/O Controller
        Subsystem: Intel Corporation: Unknown device 5647
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
        Latency: 0
        Capabilities: [e0] #09 [2109]

0000:00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Express Chipset Family Graphics Controller (prog-if 00 [VGA])
        Subsystem: Intel Corporation: Unknown device 5647
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at ffa00000 (32-bit, non-prefetchable) [size=512K]
        Region 1: I/O ports at ec00 [size=8]
        Region 2: Memory at c0000000 (32-bit, prefetchable) [size=256M]
        Region 3: Memory at ffa80000 (32-bit, non-prefetchable) [size=256K]
        Capabilities: [d0] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 03)
        Subsystem: Intel Corporation: Unknown device e213
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, cache line size 10
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at ffac0000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000  Data: 0000
        Capabilities: [70] #10 [0091]

0000:00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03) (prog-if 00 [Normal decode])
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, cache line size 10
        Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
        Memory behind bridge: ff800000-ff8fffff
        Prefetchable memory behind bridge: 00000000d4300000-00000000d4300000
        BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
        Capabilities: [40] #10 [0141]
        Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
                Address: 00000000  Data: 0000
        Capabilities: [90] #0d [0000]
        Capabilities: [a0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 03) (prog-if 00 [Normal decode])
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, cache line size 10
        Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
        Memory behind bridge: ff700000-ff7fffff
        Prefetchable memory behind bridge: 00000000d4200000-00000000d4200000
        BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
        Capabilities: [40] #10 [0141]
        Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
                Address: 00000000  Data: 0000
        Capabilities: [90] #0d [0000]
        Capabilities: [a0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 03) (prog-if 00 [Normal decode])
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, cache line size 10
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
        Memory behind bridge: ff600000-ff6fffff
        Prefetchable memory behind bridge: 00000000d4100000-00000000d4100000
        BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
        Capabilities: [40] #10 [0141]
        Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
                Address: 00000000  Data: 0000
        Capabilities: [90] #0d [0000]
        Capabilities: [a0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:1c.3 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 4 (rev 03) (prog-if 00 [Normal decode])
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, cache line size 10
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: ff500000-ff5fffff
        Prefetchable memory behind bridge: 00000000d4000000-00000000d4000000
        BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
        Capabilities: [40] #10 [0141]
        Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
                Address: 00000000  Data: 0000
        Capabilities: [90] #0d [0000]
        Capabilities: [a0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation: Unknown device 5647
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin A routed to IRQ 9
        Region 4: I/O ports at c800 [size=32]

0000:00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation: Unknown device 5647
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin B routed to IRQ 10
        Region 4: I/O ports at cc00 [size=32]

0000:00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation: Unknown device 5647
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin C routed to IRQ 5
        Region 4: I/O ports at d000 [size=32]

0000:00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation: Unknown device 5647
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin D routed to IRQ 11
        Region 4: I/O ports at d400 [size=32]

0000:00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) (prog-if 20 [EHCI])
        Subsystem: Intel Corporation: Unknown device 5647
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin A routed to IRQ 9
        Region 0: Memory at ffac4000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [58] #0a [20a0]

0000:00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3) (prog-if 01 [Subtractive decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Bus: primary=00, secondary=05, subordinate=05, sec-latency=32
        I/O behind bridge: 0000b000-0000bfff
        Memory behind bridge: ff900000-ff9fffff
        Prefetchable memory behind bridge: 00000000d0000000-00000000d3f00000
        BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
        Capabilities: [50] #0d [0000]

0000:00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 03)
        Subsystem: Intel Corporation: Unknown device 5647
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0

0000:00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
        Subsystem: Intel Corporation: Unknown device 5647
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin A routed to IRQ 5
        Region 0: I/O ports at <unassigned>
        Region 1: I/O ports at <unassigned>
        Region 2: I/O ports at <unassigned>
        Region 3: I/O ports at <unassigned>
        Region 4: I/O ports at ffa0 [size=16]

0000:00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller (rev 03) (prog-if 8f [Master SecP SecO PriP PriO])
        Subsystem: Intel Corporation: Unknown device 5647
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin B routed to IRQ 10
        Region 0: I/O ports at e800 [size=8]
        Region 1: I/O ports at e400 [size=4]
        Region 2: I/O ports at e000 [size=8]
        Region 3: I/O ports at dc00 [size=4]
        Region 4: I/O ports at d800 [size=16]
        Capabilities: [70] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
        Subsystem: Intel Corporation: Unknown device 5647
        Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin B routed to IRQ 10
        Region 4: I/O ports at c400 [size=32]

0000:05:00.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
        Subsystem: Hauppauge computer works Inc.: Unknown device 4801
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (32000ns min, 2000ns max), cache line size 10
        Interrupt: pin A routed to IRQ 3
        Region 0: Memory at d0000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [44] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:05:01.0 Communication controller: U.S. Robotics: Unknown device 2f00 (rev 01)
        Subsystem: U.S. Robotics: Unknown device 0113
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at ff900000 (32-bit, non-prefetchable) [size=64K]
        Region 1: I/O ports at bc00 [size=8]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:05:08.0 Ethernet controller: Intel Corporation 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller (rev 01)
        Subsystem: Intel Corporation: Unknown device 307d
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (2000ns min, 14000ns max), cache line size 10
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at ff910000 (32-bit, non-prefetchable) [size=4K]
        Region 1: I/O ports at b800 [size=64]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=2 PME-



alsamixer and amixer still refuse to start.  When I restart /etc/init.d/alsasound it gives me an alsactl error on stopping:

camille ~ # /etc/init.d/alsasound restart
 * Storing ALSA Mixer Levels ...
/usr/sbin/alsactl: get_control:149: Cannot read control info '2,0,0,Front Playback Volume,0': Invalid argument                                                                  [ !! ] * Unloading ALSA ...                                                                [ ok ] * Unloading ALSA modules ...                                                        [ ok ] * Loading ALSA modules ...
 *   Loading: snd-card-0 ...                                                         [ ok ] *   Loading: snd-seq-oss ...                                                        [ ok ] *   Loading: snd-pcm-oss ...                                                        [ ok ] * Restoring Mixer Levels ...
 * No mixer config in /etc/asound.state, you have to unmute your card!               [ ok 

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
>
> I built and rebooted with the vanilla kernel  2.6.14-rc5 and
> started /etc/init.d/alsasound:
>
> camille ~ # /etc/init.d/alsasound start
>  * Loading ALSA modules ...
>  *   Loading: snd-card-0 ...
> [ ok ] *   Loading: snd-seq-oss ...
> [ ok ] *   Loading: snd-pcm-oss ...
> [ ok ] * Restoring Mixer Levels ...
>  * No mixer config in /etc/asound.state, you have to unmute your card!
> [ ok ]

rm /etc/asound.state and then try rerunning alsamixer? If that doesn't
work then remove it again, re-emerge the following packages, and try
again. I think you must be very close


dragonfly ~ #  emerge -pv alsa-tools alsa-utils alsa-lib alsa-headers
alsa-jack alsa-oss alsa-firmware

>
> camille ~ # emerge -vp alsa-lib alsa-utils alsa-tools
>
> These are the packages that I would merge, in order:
>
> Calculating dependencies ...done!
> [ebuild   R   ] media-libs/alsa-lib-1.0.10_rc2  +doc +jack* 0 kB
> [ebuild   R   ] media-sound/alsa-utils-1.0.10_rc2  +nls 0 kB
> [ebuild   R   ] media-sound/alsa-tools-1.0.8-r1  +X 0 kB
>
>


>
> alsamixer and amixer still refuse to start.  When I restart /etc/init.d/alsasound it gives me an alsactl error on stopping:

When the Alsa developers update the driver for a card the numbering of
the controls often changes. For this reason any time there is a major
change to the driver you often need to delete the existing
asound.state card and create a new one that matches the driver.

I think you'll get there today. (Long slog...)

- Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 07:30 -0700, Mark Knecht wrote:
> On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> >
> > I built and rebooted with the vanilla kernel  2.6.14-rc5 and
> > started /etc/init.d/alsasound:
> >
> > camille ~ # /etc/init.d/alsasound start
> >  * Loading ALSA modules ...
> >  *   Loading: snd-card-0 ...
> > [ ok ] *   Loading: snd-seq-oss ...
> > [ ok ] *   Loading: snd-pcm-oss ...
> > [ ok ] * Restoring Mixer Levels ...
> >  * No mixer config in /etc/asound.state, you have to unmute your card!
> > [ ok ]
> 
> rm /etc/asound.state and then try rerunning alsamixer? If that doesn't
> work then remove it again, re-emerge the following packages, and try
> again. I think you must be very close
> 
> 
> dragonfly ~ #  emerge -pv alsa-tools alsa-utils alsa-lib alsa-headers
> alsa-jack alsa-oss alsa-firmware
> 
> >
> > camille ~ # emerge -vp alsa-lib alsa-utils alsa-tools
> >
> > These are the packages that I would merge, in order:
> >
> > Calculating dependencies ...done!
> > [ebuild   R   ] media-libs/alsa-lib-1.0.10_rc2  +doc +jack* 0 kB
> > [ebuild   R   ] media-sound/alsa-utils-1.0.10_rc2  +nls 0 kB
> > [ebuild   R   ] media-sound/alsa-tools-1.0.8-r1  +X 0 kB
> >
> >
> 
> 
> >
> > alsamixer and amixer still refuse to start.  When I restart /etc/init.d/alsasound it gives me an alsactl error on stopping:
> 
> When the Alsa developers update the driver for a card the numbering of
> the controls often changes. For this reason any time there is a major
> change to the driver you often need to delete the existing
> asound.state card and create a new one that matches the driver.
> 
> I think you'll get there today. (Long slog...)
> 
> - Mark
> 

There is no /etc/asound.state to remove.  There never was.  I haven't
been able to generate one since I've had this computer.  

camille ~ # emerge -pv alsa-tools alsa-utils alsa-lib alsa-headers
alsa-jack alsa-oss alsa-firmware

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] media-sound/alsa-tools-1.0.9  +X 0 kB
[ebuild   R   ] media-sound/alsa-utils-1.0.10_rc2  +nls 0 kB
[ebuild   R   ] media-libs/alsa-lib-1.0.10_rc2  +doc +jack* 0 kB
[ebuild   R   ] media-sound/alsa-headers-1.0.10_rc2  0 kB
[ebuild   R   ] media-plugins/alsa-jack-1.0.10_rc1  0 kB
[ebuild   R   ] media-libs/alsa-oss-1.0.10_rc2  0 kB
[ebuild   R   ] media-sound/alsa-firmware-1.0.9  0 kB

Total size of downloads: 0 kB


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Holly Bostick]

Michael Sullivan schreef:
> camille ~ # emerge -pv alsa-tools alsa-utils alsa-lib alsa-headers 
> alsa-jack alsa-oss alsa-firmware
> 
> These are the packages that I would merge, in order:
> 
> Calculating dependencies ...done! [ebuild   R   ] 
> media-sound/alsa-tools-1.0.9  +X 0 kB [ebuild   R   ] 
> media-sound/alsa-utils-1.0.10_rc2  +nls 0 kB [ebuild   R   ] 
> media-libs/alsa-lib-1.0.10_rc2  +doc +jack* 0 kB [ebuild   R   ] 
> media-sound/alsa-headers-1.0.10_rc2  0 kB [ebuild   R   ] 
> media-plugins/alsa-jack-1.0.10_rc1  0 kB [ebuild   R   ] 
> media-libs/alsa-oss-1.0.10_rc2  0 kB [ebuild   R   ] 
> media-sound/alsa-firmware-1.0.9  0 kB



>From www.alsa-project.org:

Latest Software Releases
Package

    * Driver
    * Library
    * Lib-plugins
    * Utilities
    * Tools
    * Firmware
    * OSS Compat. Library

Stable release

    * 1.0.9b
    * 1.0.9
    * 1.0.9
    * 1.0.9a
    * 1.0.9
    * 1.0.9
    * 1.0.9

Development release

    * 1.0.10rc2
    * 1.0.10rc2
    * 1.0.10rc1
    * 1.0.10rc2
    * 1.0.10rc2
    * ---
    * 1.0.10rc2

So there is an alsa-tools devel release higher than what you've got, as
well as a firmware devel-release.

It's possible that part of the issue is the version mismatch you've got
happening (for example, the devel release of alsa-tools might well
understand how the hda-intel cards work, whereas 1.0.9 does not).

I would consider copying the alsa-firmware and alsa-tools ebuilds to
your overlay, updating them to 1.0.10rc2, and seeing if they will then
upgrade, and if so, whether that helps.

Just an idea.

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 17:04 +0200, Holly Bostick wrote:
> Michael Sullivan schreef:
> > camille ~ # emerge -pv alsa-tools alsa-utils alsa-lib alsa-headers 
> > alsa-jack alsa-oss alsa-firmware
> > 
> > These are the packages that I would merge, in order:
> > 
> > Calculating dependencies ...done! [ebuild   R   ] 
> > media-sound/alsa-tools-1.0.9  +X 0 kB [ebuild   R   ] 
> > media-sound/alsa-utils-1.0.10_rc2  +nls 0 kB [ebuild   R   ] 
> > media-libs/alsa-lib-1.0.10_rc2  +doc +jack* 0 kB [ebuild   R   ] 
> > media-sound/alsa-headers-1.0.10_rc2  0 kB [ebuild   R   ] 
> > media-plugins/alsa-jack-1.0.10_rc1  0 kB [ebuild   R   ] 
> > media-libs/alsa-oss-1.0.10_rc2  0 kB [ebuild   R   ] 
> > media-sound/alsa-firmware-1.0.9  0 kB
> 
> 
> 
> >From www.alsa-project.org:
> 
> Latest Software Releases
> Package
> 
>     * Driver
>     * Library
>     * Lib-plugins
>     * Utilities
>     * Tools
>     * Firmware
>     * OSS Compat. Library
> 
> Stable release
> 
>     * 1.0.9b
>     * 1.0.9
>     * 1.0.9
>     * 1.0.9a
>     * 1.0.9
>     * 1.0.9
>     * 1.0.9
> 
> Development release
> 
>     * 1.0.10rc2
>     * 1.0.10rc2
>     * 1.0.10rc1
>     * 1.0.10rc2
>     * 1.0.10rc2
>     * ---
>     * 1.0.10rc2
> 
> So there is an alsa-tools devel release higher than what you've got, as
> well as a firmware devel-release.
> 
> It's possible that part of the issue is the version mismatch you've got
> happening (for example, the devel release of alsa-tools might well
> understand how the hda-intel cards work, whereas 1.0.9 does not).
> 
> I would consider copying the alsa-firmware and alsa-tools ebuilds to
> your overlay, updating them to 1.0.10rc2, and seeing if they will then
> upgrade, and if so, whether that helps.
> 
> Just an idea.
> 
> Holly

Are there ebuilds for alsa-firmware-1.0.10-rc2 and
alsa-tools-1.0.10.rc2???  I looked in portage (I sync every night at
midnight) and I didn't see them...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> On Sat, 2005-10-22 at 17:04 +0200, Holly Bostick wrote:
> > Michael Sullivan schreef:
> > > camille ~ # emerge -pv alsa-tools alsa-utils alsa-lib alsa-headers
> > > alsa-jack alsa-oss alsa-firmware
> > >
> > > These are the packages that I would merge, in order:
> > >
> > > Calculating dependencies ...done! [ebuild   R   ]
> > > media-sound/alsa-tools-1.0.9  +X 0 kB [ebuild   R   ]
> > > media-sound/alsa-utils-1.0.10_rc2  +nls 0 kB [ebuild   R   ]
> > > media-libs/alsa-lib-1.0.10_rc2  +doc +jack* 0 kB [ebuild   R   ]
> > > media-sound/alsa-headers-1.0.10_rc2  0 kB [ebuild   R   ]
> > > media-plugins/alsa-jack-1.0.10_rc1  0 kB [ebuild   R   ]
> > > media-libs/alsa-oss-1.0.10_rc2  0 kB [ebuild   R   ]
> > > media-sound/alsa-firmware-1.0.9  0 kB
> >
> >
> >
> > >From www.alsa-project.org:
> >
> > Latest Software Releases
> > Package
> >
> >     * Driver
> >     * Library
> >     * Lib-plugins
> >     * Utilities
> >     * Tools
> >     * Firmware
> >     * OSS Compat. Library
> >
> > Stable release
> >
> >     * 1.0.9b
> >     * 1.0.9
> >     * 1.0.9
> >     * 1.0.9a
> >     * 1.0.9
> >     * 1.0.9
> >     * 1.0.9
> >
> > Development release
> >
> >     * 1.0.10rc2
> >     * 1.0.10rc2
> >     * 1.0.10rc1
> >     * 1.0.10rc2
> >     * 1.0.10rc2
> >     * ---
> >     * 1.0.10rc2
> >
> > So there is an alsa-tools devel release higher than what you've got, as
> > well as a firmware devel-release.
> >
> > It's possible that part of the issue is the version mismatch you've got
> > happening (for example, the devel release of alsa-tools might well
> > understand how the hda-intel cards work, whereas 1.0.9 does not).
> >
> > I would consider copying the alsa-firmware and alsa-tools ebuilds to
> > your overlay, updating them to 1.0.10rc2, and seeing if they will then
> > upgrade, and if so, whether that helps.
> >
> > Just an idea.
> >
> > Holly
>
> Are there ebuilds for alsa-firmware-1.0.10-rc2 and
> alsa-tools-1.0.10.rc2???  I looked in portage (I sync every night at
> midnight) and I didn't see them...

I believe that alsa-firmware is only supporting the HDSP devices
(Digiface and Multiface) that need to have firmware loaded into them
before they will operate. My HDSP 9652 doesn't need it since the
firmware is on the card.

I find it doubtful that this will fix your problem, but it doesn't hurt to try.

Did you do the aplay experiment?

- Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 08:27 -0700, Mark Knecht wrote:
> On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> > On Sat, 2005-10-22 at 17:04 +0200, Holly Bostick wrote:
> > > Michael Sullivan schreef:
> > > > camille ~ # emerge -pv alsa-tools alsa-utils alsa-lib alsa-headers
> > > > alsa-jack alsa-oss alsa-firmware
> > > >
> > > > These are the packages that I would merge, in order:
> > > >
> > > > Calculating dependencies ...done! [ebuild   R   ]
> > > > media-sound/alsa-tools-1.0.9  +X 0 kB [ebuild   R   ]
> > > > media-sound/alsa-utils-1.0.10_rc2  +nls 0 kB [ebuild   R   ]
> > > > media-libs/alsa-lib-1.0.10_rc2  +doc +jack* 0 kB [ebuild   R   ]
> > > > media-sound/alsa-headers-1.0.10_rc2  0 kB [ebuild   R   ]
> > > > media-plugins/alsa-jack-1.0.10_rc1  0 kB [ebuild   R   ]
> > > > media-libs/alsa-oss-1.0.10_rc2  0 kB [ebuild   R   ]
> > > > media-sound/alsa-firmware-1.0.9  0 kB
> > >
> > >
> > >
> > > >From www.alsa-project.org:
> > >
> > > Latest Software Releases
> > > Package
> > >
> > >     * Driver
> > >     * Library
> > >     * Lib-plugins
> > >     * Utilities
> > >     * Tools
> > >     * Firmware
> > >     * OSS Compat. Library
> > >
> > > Stable release
> > >
> > >     * 1.0.9b
> > >     * 1.0.9
> > >     * 1.0.9
> > >     * 1.0.9a
> > >     * 1.0.9
> > >     * 1.0.9
> > >     * 1.0.9
> > >
> > > Development release
> > >
> > >     * 1.0.10rc2
> > >     * 1.0.10rc2
> > >     * 1.0.10rc1
> > >     * 1.0.10rc2
> > >     * 1.0.10rc2
> > >     * ---
> > >     * 1.0.10rc2
> > >
> > > So there is an alsa-tools devel release higher than what you've got, as
> > > well as a firmware devel-release.
> > >
> > > It's possible that part of the issue is the version mismatch you've got
> > > happening (for example, the devel release of alsa-tools might well
> > > understand how the hda-intel cards work, whereas 1.0.9 does not).
> > >
> > > I would consider copying the alsa-firmware and alsa-tools ebuilds to
> > > your overlay, updating them to 1.0.10rc2, and seeing if they will then
> > > upgrade, and if so, whether that helps.
> > >
> > > Just an idea.
> > >
> > > Holly
> >
> > Are there ebuilds for alsa-firmware-1.0.10-rc2 and
> > alsa-tools-1.0.10.rc2???  I looked in portage (I sync every night at
> > midnight) and I didn't see them...
> 
> I believe that alsa-firmware is only supporting the HDSP devices
> (Digiface and Multiface) that need to have firmware loaded into them
> before they will operate. My HDSP 9652 doesn't need it since the
> firmware is on the card.
> 
> I find it doubtful that this will fix your problem, but it doesn't hurt to try.
> 
> Did you do the aplay experiment?

Yes.  I sent the output in a previous post.  I don't use aplay very
often, but I believe that the output it gave was the output it's
supposed to give on a working sound system, except that there was no
sound coming out of the speakers.  I checked and the speakers are turned
on and plugged into the PC and I turned the volume all the way up before
running aplay and still didn't hear the wav file.
> 
> - Mark


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:

> > > > > media-sound/alsa-firmware-1.0.9  0 kB

This is the newest firmware package BTW.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:

> Yes.  I sent the output in a previous post.  I don't use aplay very
> often, but I believe that the output it gave was the output it's
> supposed to give on a working sound system, except that there was no
> sound coming out of the speakers.  I checked and the speakers are turned
> on and plugged into the PC and I turned the volume all the way up before
> running aplay and still didn't hear the wav file.

I'm really hesitant to mention this one, but others have done it and
so have I oncce or twice. Are you sure you have the speakers plugged
into the right output from the motherboard? Normally it's the green
one in the middle.

Also, there was a time when the Intel 810 was senting output out on
some other plug on a couple of machines. Try the headphone output plug
as well as the speaker output plug.

- Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 08:51 -0700, Mark Knecht wrote:
> On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> 
> > Yes.  I sent the output in a previous post.  I don't use aplay very
> > often, but I believe that the output it gave was the output it's
> > supposed to give on a working sound system, except that there was no
> > sound coming out of the speakers.  I checked and the speakers are turned
> > on and plugged into the PC and I turned the volume all the way up before
> > running aplay and still didn't hear the wav file.
> 
> I'm really hesitant to mention this one, but others have done it and
> so have I oncce or twice. Are you sure you have the speakers plugged
> into the right output from the motherboard? Normally it's the green
> one in the middle.
> 
> Also, there was a time when the Intel 810 was senting output out on
> some other plug on a couple of machines. Try the headphone output plug
> as well as the speaker output plug.
> 
> - Mark
> 

I have my speakers plugged into the headphone jack on the front of the
case.  That's the only way I could get sound out of them in Windows XP.


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Matt Randolph]

Michael Sullivan wrote:

>On Sat, 2005-10-22 at 08:51 -0700, Mark Knecht wrote:
>  
>
>>On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
>>
>>    
>>
>>>Yes.  I sent the output in a previous post.  I don't use aplay very
>>>often, but I believe that the output it gave was the output it's
>>>supposed to give on a working sound system, except that there was no
>>>sound coming out of the speakers.  I checked and the speakers are turned
>>>on and plugged into the PC and I turned the volume all the way up before
>>>running aplay and still didn't hear the wav file.
>>>      
>>>
>>I'm really hesitant to mention this one, but others have done it and
>>so have I oncce or twice. Are you sure you have the speakers plugged
>>into the right output from the motherboard? Normally it's the green
>>one in the middle.
>>
>>Also, there was a time when the Intel 810 was senting output out on
>>some other plug on a couple of machines. Try the headphone output plug
>>as well as the speaker output plug.
>>
>>- Mark
>>
>>    
>>
>
>I have my speakers plugged into the headphone jack on the front of the
>case.  That's the only way I could get sound out of them in Windows XP.
>
>
>  
>
The headphone jack on the front of the case?  First of all, make sure 
that this is not the headphone jack on the front of the CD-ROM drive.  
If this is actually just an alternate front panel jack you should still 
try using the standard jack on the rear of the machine.  What if there 
was something wrong with the front panel lead or jacks?  If you couldn't 
get sound out of your machine under Windows through the regular 
speaker-out or line-out jacks, and you could only get sound out of this 
front panel connector, then either you have a serious hardware problem 
with the card or you installed the front panel lead improperly.  On my 
newer machines, the front panel lead connects to the appropriate pins on 
the motherboard not once, but twice.  The second connection serves as a 
jumper to enable the front panel connectors to work as well as the rear 
panel connectors.  Check your motherboard manual to be sure that you 
have things wired up correctly.  It sounds like you don't.  If 
everything IS wired up correctly and both problems still persist (the 
Windows one and the ALSA one), then I'd urge you to run out and buy a 
new card.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 15:03 -0400, Matt Randolph wrote:
> Michael Sullivan wrote:
> 
> >On Sat, 2005-10-22 at 08:51 -0700, Mark Knecht wrote:
> >  
> >
> >>On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> >>
> >>    
> >>
> >>>Yes.  I sent the output in a previous post.  I don't use aplay very
> >>>often, but I believe that the output it gave was the output it's
> >>>supposed to give on a working sound system, except that there was no
> >>>sound coming out of the speakers.  I checked and the speakers are turned
> >>>on and plugged into the PC and I turned the volume all the way up before
> >>>running aplay and still didn't hear the wav file.
> >>>      
> >>>
> >>I'm really hesitant to mention this one, but others have done it and
> >>so have I oncce or twice. Are you sure you have the speakers plugged
> >>into the right output from the motherboard? Normally it's the green
> >>one in the middle.
> >>
> >>Also, there was a time when the Intel 810 was senting output out on
> >>some other plug on a couple of machines. Try the headphone output plug
> >>as well as the speaker output plug.
> >>
> >>- Mark
> >>
> >>    
> >>
> >
> >I have my speakers plugged into the headphone jack on the front of the
> >case.  That's the only way I could get sound out of them in Windows XP.
> >
> >
> >  
> >
> The headphone jack on the front of the case?  First of all, make sure 
> that this is not the headphone jack on the front of the CD-ROM drive.

The cd-rom drive is at the top of the case.  The headphone jack my
speakers are plugged into is at the bottom of the case.
>   
> If this is actually just an alternate front panel jack you should still 
> try using the standard jack on the rear of the machine.  What if there 
> was something wrong with the front panel lead or jacks?  If you couldn't 
> get sound out of your machine under Windows through the regular 
> speaker-out or line-out jacks, and you could only get sound out of this 
> front panel connector, then either you have a serious hardware problem 
> with the card or you installed the front panel lead improperly.  

I think I just plugged the speakers into the wrong jack in the back.
Besides, it's a lot more convenient for me this way.
> On my 
> newer machines, the front panel lead connects to the appropriate pins on 
> the motherboard not once, but twice.  The second connection serves as a 
> jumper to enable the front panel connectors to work as well as the rear 
> panel connectors.  Check your motherboard manual to be sure that you 
> have things wired up correctly.  It sounds like you don't.  

I don't have a motherboard manual for this machine.  
> If 
> everything IS wired up correctly and both problems still persist (the 
> Windows one and the ALSA one), then I'd urge you to run out and buy a 
> new card.

It would cost more than I can afford to replace the card.  I would have
to pay for the new sound card, and then for someone to install it.  I
don't go inside the case anymore.  I'd rather have a working computer
(although mute in Linux) than a dead computer because I tried to fix the
hardware.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> On Sat, 2005-10-22 at 08:51 -0700, Mark Knecht wrote:
> > On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> >
> > > Yes.  I sent the output in a previous post.  I don't use aplay very
> > > often, but I believe that the output it gave was the output it's
> > > supposed to give on a working sound system, except that there was no
> > > sound coming out of the speakers.  I checked and the speakers are turned
> > > on and plugged into the PC and I turned the volume all the way up before
> > > running aplay and still didn't hear the wav file.
> >
> > I'm really hesitant to mention this one, but others have done it and
> > so have I oncce or twice. Are you sure you have the speakers plugged
> > into the right output from the motherboard? Normally it's the green
> > one in the middle.
> >
> > Also, there was a time when the Intel 810 was senting output out on
> > some other plug on a couple of machines. Try the headphone output plug
> > as well as the speaker output plug.
> >
> > - Mark
> >
>
> I have my speakers plugged into the headphone jack on the front of the
> case.  That's the only way I could get sound out of them in Windows XP.

Seems like a reasonable thing, based on the Windows results, but I am
not the least bit confident that this will work with Alsa.

Can you test again using back panel connectors? What motherboard it
this? Or what machine? Is it somethign you built or is it like a Dell
or some other prebuilt machine.

One downside to Dell machines is that htey are SO tightly tied in with
Intel that they often are very leading edge hardware. Good for
Windows, if the drivers are ready, and Dell has enough pull to make
sure they are, but not a good thing when you get to be an early Linux
adopter.

Anyway, please, please try workign with the back panel connectors and
let me know what motherboard we are talking about.

- Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 12:29 -0700, Mark Knecht wrote:
> On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> > On Sat, 2005-10-22 at 08:51 -0700, Mark Knecht wrote:
> > > On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> > >
> > > > Yes.  I sent the output in a previous post.  I don't use aplay very
> > > > often, but I believe that the output it gave was the output it's
> > > > supposed to give on a working sound system, except that there was no
> > > > sound coming out of the speakers.  I checked and the speakers are turned
> > > > on and plugged into the PC and I turned the volume all the way up before
> > > > running aplay and still didn't hear the wav file.
> > >
> > > I'm really hesitant to mention this one, but others have done it and
> > > so have I oncce or twice. Are you sure you have the speakers plugged
> > > into the right output from the motherboard? Normally it's the green
> > > one in the middle.
> > >
> > > Also, there was a time when the Intel 810 was senting output out on
> > > some other plug on a couple of machines. Try the headphone output plug
> > > as well as the speaker output plug.
> > >
> > > - Mark
> > >
> >
> > I have my speakers plugged into the headphone jack on the front of the
> > case.  That's the only way I could get sound out of them in Windows XP.
> 
> Seems like a reasonable thing, based on the Windows results, but I am
> not the least bit confident that this will work with Alsa.
> 
> Can you test again using back panel connectors? What motherboard it
> this? Or what machine? Is it somethign you built or is it like a Dell
> or some other prebuilt machine.
> 
> One downside to Dell machines is that htey are SO tightly tied in with
> Intel that they often are very leading edge hardware. Good for
> Windows, if the drivers are ready, and Dell has enough pull to make
> sure they are, but not a good thing when you get to be an early Linux
> adopter.
> 
> Anyway, please, please try workign with the back panel connectors and
> let me know what motherboard we are talking about.
> 
> - Mark
> 

OK.  I powered down the machine and tipped it and plugged my speakers
into the "Line Out" slot.  It worked in Windows.  Before I must have
plugged it into the "Line In" slot.  I booted back into Linux and
started alsasound and tried the aplay test.  No sound out of the
speakers...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 12:29 -0700, Mark Knecht wrote:
> On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> > On Sat, 2005-10-22 at 08:51 -0700, Mark Knecht wrote:
> > > On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> > >
> > > > Yes.  I sent the output in a previous post.  I don't use aplay very
> > > > often, but I believe that the output it gave was the output it's
> > > > supposed to give on a working sound system, except that there was no
> > > > sound coming out of the speakers.  I checked and the speakers are turned
> > > > on and plugged into the PC and I turned the volume all the way up before
> > > > running aplay and still didn't hear the wav file.
> > >
> > > I'm really hesitant to mention this one, but others have done it and
> > > so have I oncce or twice. Are you sure you have the speakers plugged
> > > into the right output from the motherboard? Normally it's the green
> > > one in the middle.
> > >
> > > Also, there was a time when the Intel 810 was senting output out on
> > > some other plug on a couple of machines. Try the headphone output plug
> > > as well as the speaker output plug.
> > >
> > > - Mark
> > >
> >
> > I have my speakers plugged into the headphone jack on the front of the
> > case.  That's the only way I could get sound out of them in Windows XP.
> 
> Seems like a reasonable thing, based on the Windows results, but I am
> not the least bit confident that this will work with Alsa.
> 
> Can you test again using back panel connectors? What motherboard it
> this? Or what machine? Is it somethign you built or is it like a Dell
> or some other prebuilt machine.
> 
> One downside to Dell machines is that htey are SO tightly tied in with
> Intel that they often are very leading edge hardware. Good for
> Windows, if the drivers are ready, and Dell has enough pull to make
> sure they are, but not a good thing when you get to be an early Linux
> adopter.
> 
> Anyway, please, please try workign with the back panel connectors and
> let me know what motherboard we are talking about.
> 
> - Mark
> 

BTW you asked if this was one I built or some other prebuilt machine.
It's a NobelView P4 with a few changes I requested.  The sound card was
supposed to be a Creative Labs Sound Blaster Live, but it's not.  I have
no idea what it is, but it's not an SB Live...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/22/05, Mark Knecht <markknecht@gmail.com> wrote:
> On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> > On Sat, 2005-10-22 at 17:04 +0200, Holly Bostick wrote:
> > > Michael Sullivan schreef:
> > > > camille ~ # emerge -pv alsa-tools alsa-utils alsa-lib alsa-headers
> > > > alsa-jack alsa-oss alsa-firmware
> > > >
> > > > These are the packages that I would merge, in order:
> > > >
> > > > Calculating dependencies ...done! [ebuild   R   ]
> > > > media-sound/alsa-tools-1.0.9  +X 0 kB [ebuild   R   ]
> > > > media-sound/alsa-utils-1.0.10_rc2  +nls 0 kB [ebuild   R   ]
> > > > media-libs/alsa-lib-1.0.10_rc2  +doc +jack* 0 kB [ebuild   R   ]
> > > > media-sound/alsa-headers-1.0.10_rc2  0 kB [ebuild   R   ]
> > > > media-plugins/alsa-jack-1.0.10_rc1  0 kB [ebuild   R   ]
> > > > media-libs/alsa-oss-1.0.10_rc2  0 kB [ebuild   R   ]
> > > > media-sound/alsa-firmware-1.0.9  0 kB
> > >
> > >
> > >
> > > >From www.alsa-project.org:
> > >
> > > Latest Software Releases
> > > Package
> > >
> > >     * Driver
> > >     * Library
> > >     * Lib-plugins
> > >     * Utilities
> > >     * Tools
> > >     * Firmware
> > >     * OSS Compat. Library
> > >
> > > Stable release
> > >
> > >     * 1.0.9b
> > >     * 1.0.9
> > >     * 1.0.9
> > >     * 1.0.9a
> > >     * 1.0.9
> > >     * 1.0.9
> > >     * 1.0.9
> > >
> > > Development release
> > >
> > >     * 1.0.10rc2
> > >     * 1.0.10rc2
> > >     * 1.0.10rc1
> > >     * 1.0.10rc2
> > >     * 1.0.10rc2
> > >     * ---
> > >     * 1.0.10rc2
> > >
> > > So there is an alsa-tools devel release higher than what you've got, as
> > > well as a firmware devel-release.
> > >
> > > It's possible that part of the issue is the version mismatch you've got
> > > happening (for example, the devel release of alsa-tools might well
> > > understand how the hda-intel cards work, whereas 1.0.9 does not).
> > >
> > > I would consider copying the alsa-firmware and alsa-tools ebuilds to
> > > your overlay, updating them to 1.0.10rc2, and seeing if they will then
> > > upgrade, and if so, whether that helps.
> > >
> > > Just an idea.
> > >
> > > Holly
> >
> > Are there ebuilds for alsa-firmware-1.0.10-rc2 and
> > alsa-tools-1.0.10.rc2???  I looked in portage (I sync every night at
> > midnight) and I didn't see them...
>
> I believe that alsa-firmware is only supporting the HDSP devices
> (Digiface and Multiface) that need to have firmware loaded into them
> before they will operate. My HDSP 9652 doesn't need it since the
> firmware is on the card.
>
> I find it doubtful that this will fix your problem, but it doesn't hurt to try.
>
> Did you do the aplay experiment?
>
> - Mark
>

Please spend some time looking at the Alsa bug report system. There
are a number of folks having similar problems. There are currently
25-30 bugs reported for this device. Maybe 25% of them have been for
no sound or alsamixer problems. A couple have solutions. It seems that
most are waiting attention.

If you think your problem matches one of theirs then add your info to
the bug report. If you think it's different than all the ones filed
then file a new one.

One interesting report said alsamixer failed exactly like it does for
you but he managed to get sound using ogg123. Maybe you can try that.

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1316

- Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 08:38 -0700, Mark Knecht wrote:
> On 10/22/05, Mark Knecht <markknecht@gmail.com> wrote:
> > On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> > > On Sat, 2005-10-22 at 17:04 +0200, Holly Bostick wrote:
> > > > Michael Sullivan schreef:
> > > > > camille ~ # emerge -pv alsa-tools alsa-utils alsa-lib alsa-headers
> > > > > alsa-jack alsa-oss alsa-firmware
> > > > >
> > > > > These are the packages that I would merge, in order:
> > > > >
> > > > > Calculating dependencies ...done! [ebuild   R   ]
> > > > > media-sound/alsa-tools-1.0.9  +X 0 kB [ebuild   R   ]
> > > > > media-sound/alsa-utils-1.0.10_rc2  +nls 0 kB [ebuild   R   ]
> > > > > media-libs/alsa-lib-1.0.10_rc2  +doc +jack* 0 kB [ebuild   R   ]
> > > > > media-sound/alsa-headers-1.0.10_rc2  0 kB [ebuild   R   ]
> > > > > media-plugins/alsa-jack-1.0.10_rc1  0 kB [ebuild   R   ]
> > > > > media-libs/alsa-oss-1.0.10_rc2  0 kB [ebuild   R   ]
> > > > > media-sound/alsa-firmware-1.0.9  0 kB
> > > >
> > > >
> > > >
> > > > >From www.alsa-project.org:
> > > >
> > > > Latest Software Releases
> > > > Package
> > > >
> > > >     * Driver
> > > >     * Library
> > > >     * Lib-plugins
> > > >     * Utilities
> > > >     * Tools
> > > >     * Firmware
> > > >     * OSS Compat. Library
> > > >
> > > > Stable release
> > > >
> > > >     * 1.0.9b
> > > >     * 1.0.9
> > > >     * 1.0.9
> > > >     * 1.0.9a
> > > >     * 1.0.9
> > > >     * 1.0.9
> > > >     * 1.0.9
> > > >
> > > > Development release
> > > >
> > > >     * 1.0.10rc2
> > > >     * 1.0.10rc2
> > > >     * 1.0.10rc1
> > > >     * 1.0.10rc2
> > > >     * 1.0.10rc2
> > > >     * ---
> > > >     * 1.0.10rc2
> > > >
> > > > So there is an alsa-tools devel release higher than what you've got, as
> > > > well as a firmware devel-release.
> > > >
> > > > It's possible that part of the issue is the version mismatch you've got
> > > > happening (for example, the devel release of alsa-tools might well
> > > > understand how the hda-intel cards work, whereas 1.0.9 does not).
> > > >
> > > > I would consider copying the alsa-firmware and alsa-tools ebuilds to
> > > > your overlay, updating them to 1.0.10rc2, and seeing if they will then
> > > > upgrade, and if so, whether that helps.
> > > >
> > > > Just an idea.
> > > >
> > > > Holly
> > >
> > > Are there ebuilds for alsa-firmware-1.0.10-rc2 and
> > > alsa-tools-1.0.10.rc2???  I looked in portage (I sync every night at
> > > midnight) and I didn't see them...
> >
> > I believe that alsa-firmware is only supporting the HDSP devices
> > (Digiface and Multiface) that need to have firmware loaded into them
> > before they will operate. My HDSP 9652 doesn't need it since the
> > firmware is on the card.
> >
> > I find it doubtful that this will fix your problem, but it doesn't hurt to try.
> >
> > Did you do the aplay experiment?
> >
> > - Mark
> >
> 
> Please spend some time looking at the Alsa bug report system. There
> are a number of folks having similar problems. There are currently
> 25-30 bugs reported for this device. Maybe 25% of them have been for
> no sound or alsamixer problems. A couple have solutions. It seems that
> most are waiting attention.
> 
> If you think your problem matches one of theirs then add your info to
> the bug report. If you think it's different than all the ones filed
> then file a new one.
> 
> One interesting report said alsamixer failed exactly like it does for
> you but he managed to get sound using ogg123. Maybe you can try that.
> 
> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1316
> 
> - Mark
> 

camille sounds # ogg123 KDE_Pop.ogg

Audio Device:   Advanced Linux Sound Architecture (ALSA) output

Playing: KDE_Pop.ogg
Ogg Vorbis stream: 1 channel, 44100 Hz

Done.
camille sounds # ogg123 KDE_Desktop1.wav

Audio Device:   Advanced Linux Sound Architecture (ALSA) output

Error opening KDE_Desktop1.wav using the oggvorbis module.  The file may
be corrupted.


I'll take a look at the ALSA site.  The above ogg file played (at least
the screen output said it did), but there was no sound from the
speakers.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:

> There is no /etc/asound.state to remove.  There never was.  I haven't
> been able to generate one since I've had this computer.

Yeah, with alsamixer not working for you there isn't a way to get it configured.

What happens if you just run aplay?

slocate *.wav and pick one, then aplaye somefile.wav

I wonder if the card is truly muted at this point?

On other thing. Your card is rev. 3

Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition
Audio Controller (rev 03)

Richard's card is rev 4:

 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition
Audio Controller (rev 04)

Possibly the Alsa developers haven't seen your revision and hence
somethign is a bit different? That sort of thing could easily cause a
problem if the differences are very significant. I think Richard said
his was in a laptop. I have been assumign yours is in a desktop. This
means (probably) that you are using different chipsets.

- Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 08:12 -0700, Mark Knecht wrote:
> On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> 
> > There is no /etc/asound.state to remove.  There never was.  I haven't
> > been able to generate one since I've had this computer.
> 
> Yeah, with alsamixer not working for you there isn't a way to get it configured.
> 
> What happens if you just run aplay?
> 
> slocate *.wav and pick one, then aplaye somefile.wav
> 
> I wonder if the card is truly muted at this point?

camille sounds # aplay KDE_Desktop5.wav
Playing WAVE 'KDE_Desktop5.wav' : Signed 16 bit Little Endian, Rate
22050 Hz, Mono

I turned my speakers all the way up before I issued the command, but no
sound came out.  Just the usual tiny bit of static I hear when I turn
the speaker up all the way.

Also, when I log into GNOME I get this stupid error message box saying
that no volume control was available or something like that.  Holly
Bostick said something about GNOME's included sound server might be
interfering with ALSA.  Is there a way I can check for that, and if I
find it, turn it off so it's not interfering?
> 
> On other thing. Your card is rev. 3
> 
> Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition
> Audio Controller (rev 03)
> 
> Richard's card is rev 4:
> 
>  Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition
> Audio Controller (rev 04)
> 
> Possibly the Alsa developers haven't seen your revision and hence
> somethign is a bit different? That sort of thing could easily cause a
> problem if the differences are very significant. I think Richard said
> his was in a laptop. I have been assumign yours is in a desktop. This
> means (probably) that you are using different chipsets.

Yes, mine is a desktop.
> 
> - Mark
> 

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> On Sat, 2005-10-22 at 08:12 -0700, Mark Knecht wrote:
> > On 10/22/05, Michael Sullivan <michael@espersunited.com> wrote:
> >
> > > There is no /etc/asound.state to remove.  There never was.  I haven't
> > > been able to generate one since I've had this computer.
> >
> > Yeah, with alsamixer not working for you there isn't a way to get it configured.
> >
> > What happens if you just run aplay?
> >
> > slocate *.wav and pick one, then aplaye somefile.wav
> >
> > I wonder if the card is truly muted at this point?
>
> camille sounds # aplay KDE_Desktop5.wav
> Playing WAVE 'KDE_Desktop5.wav' : Signed 16 bit Little Endian, Rate
> 22050 Hz, Mono
>
> I turned my speakers all the way up before I issued the command, but no
> sound came out.  Just the usual tiny bit of static I hear when I turn
> the speaker up all the way.
>
> Also, when I log into GNOME I get this stupid error message box saying
> that no volume control was available or something like that.  Holly
> Bostick said something about GNOME's included sound server might be
> interfering with ALSA.  Is there a way I can check for that, and if I
> find it, turn it off so it's not interfering?

ps aux and look for sound stuff. I think it's called esound or esd.
Something like that. You can kill it or probably stop it nicely using
Gnome's configuration utilities.

> >
> > On other thing. Your card is rev. 3
> >
> > Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition
> > Audio Controller (rev 03)
> >
> > Richard's card is rev 4:
> >
> >  Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition
> > Audio Controller (rev 04)
> >
> > Possibly the Alsa developers haven't seen your revision and hence
> > somethign is a bit different? That sort of thing could easily cause a
> > problem if the differences are very significant. I think Richard said
> > his was in a laptop. I have been assumign yours is in a desktop. This
> > means (probably) that you are using different chipsets.
>
> Yes, mine is a desktop.

It's a new card and support is probably touchy. I will not tell you
(right now) how long I had to wait to get support for my HDSP 9652 as
you might draw conclusions that would make you cry, and I don't think
it will happen to you. ;-) Maybe after you get yours working. ;-)

Cheers,
Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Holly Bostick]

Michael Sullivan schreef:
> On Sat, 2005-10-22 at 00:53 -0700, Richard Fish wrote:
> 
>> Mark Knecht wrote:
>> 
>> 
>>> On 10/21/05, Richard Fish <bigfish@asmallpond.org> wrote:
>>> 
>>> 
>>> 
>>>> Mark Knecht wrote:
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> I'm tellin' ya. alsamixer is jsut a gui for amixer and amixer
>>>>>  does not work for every Alsa supported card. You need to
>>>>> find out from the Alsa folks what is the supported mixer for
>>>>> this card.
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> Just an FYI, I also have an intel-hda (in my laptop). Alsamixer
>>>> supports it just fine, except that the stupid card doesn't
>>>> provide a "Master Volume" control, so you have to adjust the
>>>> speaker volume with the "Front" control.  Stupid card.
>>>> 
>>>> -Richard
>>>> 
>>>> 
>>> 
>>> What kernel are you running? Can you give Michael a hint as to 
>>> how you set it up?
>>> 
>>> 
>> 
>> Kernel version is from suspend2-sources-2.6.13-r5.  I didn't have 
>> to do anything special for setup though..."it just worked".
>> 
>> I suspect you are correct that it is a driver bug and a newer 
>> version of the driver would help.  Michael, sorry I haven't been 
>> following this thread closely, but have you tried a .14-rc kernel? 
>> I just looked at vanilla-sources-2.6.14-rc5, and there seems to be 
>> some significant changes with the newest kernel.
>> 
>> Anyway, some basic information about my setup follows.  I can 
>> provide more if desired (particularly /etc/asound.state, 
>> ~/.asoundrc, or amixer output).
>> 
>> carcharias linux # lsmod Module                  Size  Used by ...
>>  snd_hda_intel          15872  1 snd_hda_codec          73536  1 
>> snd_hda_intel snd_pcm                78600  2 
>> snd_hda_intel,snd_hda_codec snd_timer              22212  1 snd_pcm
>>  snd                    43192  6 
>> snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer soundcore 9056  1 snd
>> snd_page_alloc          9800  2 snd_hda_intel,snd_pcm ...
>> 
>> carcharias linux # emerge -vp alsa-lib alsa-utils alsa-tools 
>> alsa-headers These are the packages that I would merge, in order: 
>> Calculating dependencies ...done! [ebuild   R   ] 
>> media-libs/alsa-lib-1.0.9  +doc -jack 0 kB [ebuild   R   ] 
>> media-sound/alsa-utils-1.0.9a-r1  +nls 0 kB [ebuild   R   ] 
>> media-sound/alsa-tools-1.0.9  +X 0 kB [ebuild   R   ] 
>> media-sound/alsa-headers-1.0.9b  0 kB
>> 
>> carcharias linux # lspci -n ... 00:1b.0 0403: 8086:2668 (rev 04) 
>> ...
>> 
>> carcharias linux # lspci -vv ... 00:1b.0 Class 0403: Intel 
>> Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition 
>> Audio Controller (rev 04) Subsystem: ASUSTeK Computer Inc. Unknown 
>> device 10c3 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- 
>> VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF-
>>  FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- 
>> <PERR- Latency: 0, Cache Line Size 08 Interrupt: pin A routed to 
>> IRQ 16 Region 0: Memory at febf8000 (64-bit, non-prefetchable) 
>> [size=16K] Capabilities: [50] Power Management version 2 Flags: 
>> PMEClk- DSI- D1- D2- AuxCurrent=55mA 
>> PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 
>> DScale=0 PME- Capabilities: [60] Message Signalled Interrupts: 
>> 64bit+ Queue=0/0 Enable- Address: 0000000000000000  Data: 0000 
>> Capabilities: [70] Express Unknown type IRQ 0 Device: Supported: 
>> MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s 
>> <64ns, L1 <1us Device: Errors: Correctable- Non-Fatal- Fatal- 
>> Unsupported- Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ 
>> Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported 
>> Speed unknown, Width x0, ASPM unknown, Port 0 Link: Latency L0s 
>> <64ns, L1 <1us Link: ASPM Disabled CommClk- ExtSynch- Link: Speed 
>> unknown, Width x0 Capabilities: [100] Virtual Channel Capabilities:
>>  [130] Unknown (5) ...
>> 
>> -Richard
>> 
> 
> 
> I built and rebooted with the vanilla kernel  2.6.14-rc5 and started 
> /etc/init.d/alsasound:
> 
> camille ~ # /etc/init.d/alsasound start * Loading ALSA modules ... * 
> Loading: snd-card-0 ... [ ok ] *   Loading: snd-seq-oss ... [ ok ] * 
> Loading: snd-pcm-oss ... [ ok ] * Restoring Mixer Levels ... * No 
> mixer config in /etc/asound.state, you have to unmute your card! [ ok
>  ]

OK that works (we know you haven't unmuted your card, and we know (or
are almost sure) that running alsamixer is what creates
/etc/asound.state, so it's no surprise that it's not there.

> I can modprobe snd-hda-intel successfully.
> 
> Here is lsmod:
> 
> camille ~ # lsmod Module                  Size  Used by snd_pcm_oss 
> 36256  0 snd_mixer_oss          12224  1 snd_pcm_oss snd_seq_oss 
> 21280  0 snd_seq_midi_event      2976  1 snd_seq_oss snd_seq 30384  4
> snd_seq_oss,snd_seq_midi_event snd_seq_device          4588 2
> snd_seq_oss,snd_seq snd_hda_intel          11328  0 snd_hda_codec 
> 58816  1 snd_hda_intel snd_pcm                49960  3 
> snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer              14436 
> 2 snd_seq,snd_pcm snd                    28676  9 
> snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
>  snd_page_alloc          6312  2 snd_hda_intel,snd_pcm
<snip>

looks good

> 
> camille ~ # emerge -vp alsa-lib alsa-utils alsa-tools
> 
> These are the packages that I would merge, in order:
> 
> Calculating dependencies ...done! [ebuild   R   ] 
> media-libs/alsa-lib-1.0.10_rc2  +doc +jack* 0 kB [ebuild   R   ] 
> media-sound/alsa-utils-1.0.10_rc2  +nls 0 kB [ebuild   R   ] 
> media-sound/alsa-tools-1.0.8-r1  +X 0 kB


You could probably use alsa-oss as well, since you're using ALSA OSS
emulation; you might consider alsa-headers, and alsa-firmware, too.

> 
> 
<snip>
> 
> 0000:00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW 
> (ICH6 Family) High Definition Audio Controller (rev 03) Subsystem: 
> Intel Corporation: Unknown device e213 Control: I/O- Mem+ BusMaster+ 
> SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- 
> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
> <TAbort- <MAbort- >SERR- <PERR- Latency: 0, cache line size 10 
> Interrupt: pin A routed to IRQ 11 Region 0: Memory at ffac0000 
> (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power 
> Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA 
> PME(D0+,D1-,D2-,D3hot+,D3cold+)                Status: D0 PME-Enable-
>  DSel=0 DScale=0 PME- Capabilities: [60] Message Signalled
> Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000  Data:
> 0000 Capabilities: [70] #10 [0091]

Well, we knew the card was being detected, so that's good. I wonder if
any of this additional information needs to be set as extra parameters
for the card in one or more of the ALSA configuration files?

> 
> 
> alsamixer and amixer still refuse to start.  When I restart 
> /etc/init.d/alsasound it gives me an alsactl error on stopping:
> 
> camille ~ # /etc/init.d/alsasound restart * Storing ALSA Mixer Levels
>  ... /usr/sbin/alsactl: get_control:149: Cannot read control info 
> '2,0,0,Front Playback Volume,0': Invalid argument [ !! ] * Unloading
> ALSA ... [ ok ] * Unloading ALSA modules ... [ ok ] * Loading ALSA
> modules ... *   Loading: snd-card-0 ... [ ok ] *   Loading:
> snd-seq-oss ... [ ok ] *   Loading: snd-pcm-oss ... [ ok ] *
> Restoring Mixer Levels ... * No mixer config in /etc/asound.state,
> you have to unmute your card!               [ ok
> 
First of all, what error does *alsamixer* (not amixer) give you when you
attempt to start it.

Second of all.. I just attempted a restart of alsasound to see what
'correct' output should be, and I noticed that one instance of GKrellm2
closed (the instance that uses the 'Volume' plugin, unsurprisingly).
Which got me thinking... are you doing this under a loaded DE/WM? if so,
which one? Both GNOME and KDE have audio subsystems which kinda actively
interfere with ALSA when first installed (or rather, until you get them
synchronized). It's possible that aRTS or eds is interfering with ALSA
reading the card information, but.....

...third of all, I notice that the error you're getting just *happens*
to be in the very control that Richard says is a 'problem':

Richard Fish schreef:
> Just an FYI, I also have an intel-hda (in my laptop).  Alsamixer 
> supports it just fine, except that the stupid card doesn't provide a 
> "Master Volume" control, so you have to adjust the speaker volume
> with the "Front" control.  Stupid card.

Right, so the idea (generally) is that this card maps Master to Front,
which seems to be confusing to alsasound, which cannot read 'Front' for
some reason (possibly because it does not understand/has not been told
that Master=Front, so it's still looking for a 'Master' control that
does not exist, and is not expecting the 'Master' control output to be
labelled 'Front'?).

Richard, did you have to do anything to make ALSA understand that there
was no Master control and that Front should be used for this purpose?

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 16:42 +0200, Holly Bostick wrote:
> Michael Sullivan schreef:
> > On Sat, 2005-10-22 at 00:53 -0700, Richard Fish wrote:
> > 
> >> Mark Knecht wrote:
> >> 
> >> 
> >>> On 10/21/05, Richard Fish <bigfish@asmallpond.org> wrote:
> >>> 
> >>> 
> >>> 
> >>>> Mark Knecht wrote:
> >>>> 
> >>>> 
> >>>> 
> >>>> 
> >>>>> I'm tellin' ya. alsamixer is jsut a gui for amixer and amixer
> >>>>>  does not work for every Alsa supported card. You need to
> >>>>> find out from the Alsa folks what is the supported mixer for
> >>>>> this card.
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>> 
> >>>> Just an FYI, I also have an intel-hda (in my laptop). Alsamixer
> >>>> supports it just fine, except that the stupid card doesn't
> >>>> provide a "Master Volume" control, so you have to adjust the
> >>>> speaker volume with the "Front" control.  Stupid card.
> >>>> 
> >>>> -Richard
> >>>> 
> >>>> 
> >>> 
> >>> What kernel are you running? Can you give Michael a hint as to 
> >>> how you set it up?
> >>> 
> >>> 
> >> 
> >> Kernel version is from suspend2-sources-2.6.13-r5.  I didn't have 
> >> to do anything special for setup though..."it just worked".
> >> 
> >> I suspect you are correct that it is a driver bug and a newer 
> >> version of the driver would help.  Michael, sorry I haven't been 
> >> following this thread closely, but have you tried a .14-rc kernel? 
> >> I just looked at vanilla-sources-2.6.14-rc5, and there seems to be 
> >> some significant changes with the newest kernel.
> >> 
> >> Anyway, some basic information about my setup follows.  I can 
> >> provide more if desired (particularly /etc/asound.state, 
> >> ~/.asoundrc, or amixer output).
> >> 
> >> carcharias linux # lsmod Module                  Size  Used by ...
> >>  snd_hda_intel          15872  1 snd_hda_codec          73536  1 
> >> snd_hda_intel snd_pcm                78600  2 
> >> snd_hda_intel,snd_hda_codec snd_timer              22212  1 snd_pcm
> >>  snd                    43192  6 
> >> snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer soundcore 9056  1 snd
> >> snd_page_alloc          9800  2 snd_hda_intel,snd_pcm ...
> >> 
> >> carcharias linux # emerge -vp alsa-lib alsa-utils alsa-tools 
> >> alsa-headers These are the packages that I would merge, in order: 
> >> Calculating dependencies ...done! [ebuild   R   ] 
> >> media-libs/alsa-lib-1.0.9  +doc -jack 0 kB [ebuild   R   ] 
> >> media-sound/alsa-utils-1.0.9a-r1  +nls 0 kB [ebuild   R   ] 
> >> media-sound/alsa-tools-1.0.9  +X 0 kB [ebuild   R   ] 
> >> media-sound/alsa-headers-1.0.9b  0 kB
> >> 
> >> carcharias linux # lspci -n ... 00:1b.0 0403: 8086:2668 (rev 04) 
> >> ...
> >> 
> >> carcharias linux # lspci -vv ... 00:1b.0 Class 0403: Intel 
> >> Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition 
> >> Audio Controller (rev 04) Subsystem: ASUSTeK Computer Inc. Unknown 
> >> device 10c3 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- 
> >> VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF-
> >>  FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- 
> >> <PERR- Latency: 0, Cache Line Size 08 Interrupt: pin A routed to 
> >> IRQ 16 Region 0: Memory at febf8000 (64-bit, non-prefetchable) 
> >> [size=16K] Capabilities: [50] Power Management version 2 Flags: 
> >> PMEClk- DSI- D1- D2- AuxCurrent=55mA 
> >> PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 
> >> DScale=0 PME- Capabilities: [60] Message Signalled Interrupts: 
> >> 64bit+ Queue=0/0 Enable- Address: 0000000000000000  Data: 0000 
> >> Capabilities: [70] Express Unknown type IRQ 0 Device: Supported: 
> >> MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s 
> >> <64ns, L1 <1us Device: Errors: Correctable- Non-Fatal- Fatal- 
> >> Unsupported- Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ 
> >> Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported 
> >> Speed unknown, Width x0, ASPM unknown, Port 0 Link: Latency L0s 
> >> <64ns, L1 <1us Link: ASPM Disabled CommClk- ExtSynch- Link: Speed 
> >> unknown, Width x0 Capabilities: [100] Virtual Channel Capabilities:
> >>  [130] Unknown (5) ...
> >> 
> >> -Richard
> >> 
> > 
> > 
> > I built and rebooted with the vanilla kernel  2.6.14-rc5 and started 
> > /etc/init.d/alsasound:
> > 
> > camille ~ # /etc/init.d/alsasound start * Loading ALSA modules ... * 
> > Loading: snd-card-0 ... [ ok ] *   Loading: snd-seq-oss ... [ ok ] * 
> > Loading: snd-pcm-oss ... [ ok ] * Restoring Mixer Levels ... * No 
> > mixer config in /etc/asound.state, you have to unmute your card! [ ok
> >  ]
> 
> OK that works (we know you haven't unmuted your card, and we know (or
> are almost sure) that running alsamixer is what creates
> /etc/asound.state, so it's no surprise that it's not there.
> 
> > I can modprobe snd-hda-intel successfully.
> > 
> > Here is lsmod:
> > 
> > camille ~ # lsmod Module                  Size  Used by snd_pcm_oss 
> > 36256  0 snd_mixer_oss          12224  1 snd_pcm_oss snd_seq_oss 
> > 21280  0 snd_seq_midi_event      2976  1 snd_seq_oss snd_seq 30384  4
> > snd_seq_oss,snd_seq_midi_event snd_seq_device          4588 2
> > snd_seq_oss,snd_seq snd_hda_intel          11328  0 snd_hda_codec 
> > 58816  1 snd_hda_intel snd_pcm                49960  3 
> > snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer              14436 
> > 2 snd_seq,snd_pcm snd                    28676  9 
> > snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
> >  snd_page_alloc          6312  2 snd_hda_intel,snd_pcm
> <snip>
> 
> looks good
> 
> > 
> > camille ~ # emerge -vp alsa-lib alsa-utils alsa-tools
> > 
> > These are the packages that I would merge, in order:
> > 
> > Calculating dependencies ...done! [ebuild   R   ] 
> > media-libs/alsa-lib-1.0.10_rc2  +doc +jack* 0 kB [ebuild   R   ] 
> > media-sound/alsa-utils-1.0.10_rc2  +nls 0 kB [ebuild   R   ] 
> > media-sound/alsa-tools-1.0.8-r1  +X 0 kB
> 
> 
> You could probably use alsa-oss as well, since you're using ALSA OSS
> emulation; you might consider alsa-headers, and alsa-firmware, too.
> 
> > 
> > 
> <snip>
> > 
> > 0000:00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW 
> > (ICH6 Family) High Definition Audio Controller (rev 03) Subsystem: 
> > Intel Corporation: Unknown device e213 Control: I/O- Mem+ BusMaster+ 
> > SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- 
> > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
> > <TAbort- <MAbort- >SERR- <PERR- Latency: 0, cache line size 10 
> > Interrupt: pin A routed to IRQ 11 Region 0: Memory at ffac0000 
> > (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power 
> > Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA 
> > PME(D0+,D1-,D2-,D3hot+,D3cold+)                Status: D0 PME-Enable-
> >  DSel=0 DScale=0 PME- Capabilities: [60] Message Signalled
> > Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000  Data:
> > 0000 Capabilities: [70] #10 [0091]
> 
> Well, we knew the card was being detected, so that's good. I wonder if
> any of this additional information needs to be set as extra parameters
> for the card in one or more of the ALSA configuration files?
> 
> > 
> > 
> > alsamixer and amixer still refuse to start.  When I restart 
> > /etc/init.d/alsasound it gives me an alsactl error on stopping:
> > 
> > camille ~ # /etc/init.d/alsasound restart * Storing ALSA Mixer Levels
> >  ... /usr/sbin/alsactl: get_control:149: Cannot read control info 
> > '2,0,0,Front Playback Volume,0': Invalid argument [ !! ] * Unloading
> > ALSA ... [ ok ] * Unloading ALSA modules ... [ ok ] * Loading ALSA
> > modules ... *   Loading: snd-card-0 ... [ ok ] *   Loading:
> > snd-seq-oss ... [ ok ] *   Loading: snd-pcm-oss ... [ ok ] *
> > Restoring Mixer Levels ... * No mixer config in /etc/asound.state,
> > you have to unmute your card!               [ ok
> > 
> First of all, what error does *alsamixer* (not amixer) give you when you
> attempt to start it.

camille ~ # alsamixer

alsamixer: function snd_mixer_load failed: Invalid argument

> 
> Second of all.. I just attempted a restart of alsasound to see what
> 'correct' output should be, and I noticed that one instance of GKrellm2
> closed (the instance that uses the 'Volume' plugin, unsurprisingly).
> Which got me thinking... are you doing this under a loaded DE/WM? if so,
> which one? Both GNOME and KDE have audio subsystems which kinda actively
> interfere with ALSA when first installed (or rather, until you get them
> synchronized). It's possible that aRTS or eds is interfering with ALSA
> reading the card information, but.....

I use GNOME as my window manager.  I have eds and arts in my USE flags
though.
> 
> ...third of all, I notice that the error you're getting just *happens*
> to be in the very control that Richard says is a 'problem':
> 
> Richard Fish schreef:
> > Just an FYI, I also have an intel-hda (in my laptop).  Alsamixer 
> > supports it just fine, except that the stupid card doesn't provide a 
> > "Master Volume" control, so you have to adjust the speaker volume
> > with the "Front" control.  Stupid card.
> 
> Right, so the idea (generally) is that this card maps Master to Front,
> which seems to be confusing to alsasound, which cannot read 'Front' for
> some reason (possibly because it does not understand/has not been told
> that Master=Front, so it's still looking for a 'Master' control that
> does not exist, and is not expecting the 'Master' control output to be
> labelled 'Front'?).
> 
> Richard, did you have to do anything to make ALSA understand that there
> was no Master control and that Front should be used for this purpose?
> 
> Holly

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Richard Fish]

Holly Bostick wrote:

>Richard Fish schreef:
>  
>
>>Just an FYI, I also have an intel-hda (in my laptop).  Alsamixer 
>>supports it just fine, except that the stupid card doesn't provide a 
>>"Master Volume" control, so you have to adjust the speaker volume
>>with the "Front" control.  Stupid card.
>>    
>>
>
>Right, so the idea (generally) is that this card maps Master to Front,
>which seems to be confusing to alsasound, which cannot read 'Front' for
>some reason (possibly because it does not understand/has not been told
>that Master=Front, so it's still looking for a 'Master' control that
>does not exist, and is not expecting the 'Master' control output to be
>labelled 'Front'?).
>  
>

The alsa approach seems to be to just expose the hardware capabilities 
of the card to userspace, without any intelligence for remapping 
controls and the like.  So it would be more accurate to simply state 
that the card does not provide any master control volume, just separate 
controls for "Front", "Surround", "Center", and "LFE", in addition to 
the standard "Line", "CD", "Mic", and so on.  It expects the OS to 
provide a Master control that would adjust all of the outputs together. 

I think there is a way to do this in the .asoundrc file, but I haven't 
really investigated that yet.  On my laptop, it seems that all 4 
speakers, as well as the headphone jack, are wired to the "Front" 
control, so in reality I only need that to control the output volume.  
But I suspect if I actually used the s/pdif plug to connect to a true 
surround system, I would need to control all the outputs to adjust the 
volume.

>Richard, did you have to do anything to make ALSA understand that there
>was no Master control and that Front should be used for this purpose?
>  
>

Nope.

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Nick Rout]

On Sat, 2005-10-22 at 01:44 +0200, Holly Bostick wrote:
> Michael Sullivan schreef:
> > On Sat, 2005-10-22 at 01:31 +0200, Holly Bostick wrote:
> >>
> >>Try just 'amixer' or maybe 'amixer -c 0' and see if it tells you anything.
> >>
> >>Holly
> > 
> > 
> > camille ~ # amixer
> > amixer: Mixer default load error: Invalid argument
> > 
> > camille ~ # amixer -c 0
> > amixer: Mixer hw:0 load error: Invalid argument
> 
> Well it looks like all your modules are there, so something else "must"
> be wrong:
> 
> Have you run alsaconf with the card active/working as it is now?

Michael I have lost track of whether you are running alsa-driver or the
kernel modules? The hda-intel driver seems to be in heavy development,
so you may be better with alsa-driver, which is usually ahead of the
kernel stuff. 

Can anyone tell me how often stuff from the alsa project gets ported
across to the kernel?

googling hda-intel site:.alsa-project.org shows quite a few changelogs. 

Also which version of alsa-utils do you have installed (alsa-utils is
the home of alsamixer)

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Sat, 2005-10-22 at 12:57 +1300, Nick Rout wrote:
> On Sat, 2005-10-22 at 01:44 +0200, Holly Bostick wrote:
> > Michael Sullivan schreef:
> > > On Sat, 2005-10-22 at 01:31 +0200, Holly Bostick wrote:
> > >>
> > >>Try just 'amixer' or maybe 'amixer -c 0' and see if it tells you anything.
> > >>
> > >>Holly
> > > 
> > > 
> > > camille ~ # amixer
> > > amixer: Mixer default load error: Invalid argument
> > > 
> > > camille ~ # amixer -c 0
> > > amixer: Mixer hw:0 load error: Invalid argument
> > 
> > Well it looks like all your modules are there, so something else "must"
> > be wrong:
> > 
> > Have you run alsaconf with the card active/working as it is now?
> 
> Michael I have lost track of whether you are running alsa-driver or the
> kernel modules? The hda-intel driver seems to be in heavy development,
> so you may be better with alsa-driver, which is usually ahead of the
> kernel stuff. 

I'm using kernel modules.
> 
> Can anyone tell me how often stuff from the alsa project gets ported
> across to the kernel?
> 
> googling hda-intel site:.alsa-project.org shows quite a few changelogs. 
> 
> Also which version of alsa-utils do you have installed (alsa-utils is
> the home of alsamixer)
alsa-utils-1.0.9a
> 

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/21/05, Michael Sullivan <michael@espersunited.com> wrote:

>
> I'm using kernel modules.

Earlier Nick pointed out  that you seemed to have emerged the
alsa-drivers package. Have you done an emerge -C alsa-drivers yet?


> alsa-utils-1.0.9a

lightning ~ # emerge -pv alsa-headers alsa-tools alsa-oss
alsa-firmware alsa-lib alsa-utils alsa-jack

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] media-sound/alsa-headers-1.0.9b  0 kB
[ebuild   R   ] media-sound/alsa-tools-1.0.9  +X 0 kB
[ebuild   R   ] media-libs/alsa-oss-1.0.8-r1  0 kB
[ebuild  N    ] media-sound/alsa-firmware-1.0.8-r1  1,527 kB
[ebuild   R   ] media-libs/alsa-lib-1.0.9  -doc +jack 0 kB
[ebuild   R   ] media-sound/alsa-utils-1.0.9a-r1  +nls 0 kB
[ebuild   R   ] media-plugins/alsa-jack-1.0.9  0 kB

Total size of downloads: 1,527 kB
lightning ~ #

Everything on my system is marked ~x86 in /etc/portage/package.keywords

lightning ~ # cat /etc/portage/package.keywords | grep alsa
media-sound/alsa-headers ~x86
media-sound/alsa-jack ~x86
media-sound/alsa-lib ~x86
media-sound/alsa-oss ~x86
media-sound/alsa-tools ~x86
media-sound/alsa-utils ~x86
lightning ~ #

Cheers,
Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Fri, 2005-10-21 at 17:17 -0700, Mark Knecht wrote:
> On 10/21/05, Michael Sullivan <michael@espersunited.com> wrote:
> 
> >
> > I'm using kernel modules.
> 
> Earlier Nick pointed out  that you seemed to have emerged the
> alsa-drivers package. Have you done an emerge -C alsa-drivers yet?
> 
> 
> > alsa-utils-1.0.9a
> 
> lightning ~ # emerge -pv alsa-headers alsa-tools alsa-oss
> alsa-firmware alsa-lib alsa-utils alsa-jack
> 
> These are the packages that I would merge, in order:
> 
> Calculating dependencies ...done!
> [ebuild   R   ] media-sound/alsa-headers-1.0.9b  0 kB
> [ebuild   R   ] media-sound/alsa-tools-1.0.9  +X 0 kB
> [ebuild   R   ] media-libs/alsa-oss-1.0.8-r1  0 kB
> [ebuild  N    ] media-sound/alsa-firmware-1.0.8-r1  1,527 kB
> [ebuild   R   ] media-libs/alsa-lib-1.0.9  -doc +jack 0 kB
> [ebuild   R   ] media-sound/alsa-utils-1.0.9a-r1  +nls 0 kB
> [ebuild   R   ] media-plugins/alsa-jack-1.0.9  0 kB
> 
> Total size of downloads: 1,527 kB
> lightning ~ #
> 
> Everything on my system is marked ~x86 in /etc/portage/package.keywords
> 
> lightning ~ # cat /etc/portage/package.keywords | grep alsa
> media-sound/alsa-headers ~x86
> media-sound/alsa-jack ~x86
> media-sound/alsa-lib ~x86
> media-sound/alsa-oss ~x86
> media-sound/alsa-tools ~x86
> media-sound/alsa-utils ~x86
> lightning ~ #
> 
> Cheers,
> Mark
> 

I was told by people on this list and by the Gentoo ALSA Guide that
alsa-drivers conflicts with the kernel module drivers.  Should I emerge
it?  It's not installed now...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/21/05, Michael Sullivan <michael@espersunited.com> wrote:
> >
>
> I was told by people on this list and by the Gentoo ALSA Guide that
> alsa-drivers conflicts with the kernel module drivers.  Should I emerge
> it?  It's not installed now...

NO! Use what's in your kernel.

My mistake on the driver name. The 810 driver is intel8x0, so I
assumed the HDA driver was intel_hda. Apparently the Alsa guys did the
naming backward.

If you see the device under /proc/asound/cards then you did it right.
(And you did!)

At a minimum you should reemerge all the Alsa support stuff but use
~x86 for all of that, as per my easlier message. (in
/etc/portage/package.keywards) You need the newest Alsa stuff out
there. I doubt even this is new enough though.

- Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes [SOLVED]

[Michael Sullivan]

On Fri, 2005-10-21 at 17:53 -0700, Mark Knecht wrote:
> On 10/21/05, Michael Sullivan <michael@espersunited.com> wrote:
> > >
> >
> > I was told by people on this list and by the Gentoo ALSA Guide that
> > alsa-drivers conflicts with the kernel module drivers.  Should I emerge
> > it?  It's not installed now...
> 
> NO! Use what's in your kernel.
> 
> My mistake on the driver name. The 810 driver is intel8x0, so I
> assumed the HDA driver was intel_hda. Apparently the Alsa guys did the
> naming backward.
> 
> If you see the device under /proc/asound/cards then you did it right.
> (And you did!)
> 
> At a minimum you should reemerge all the Alsa support stuff but use
> ~x86 for all of that, as per my easlier message. (in
> /etc/portage/package.keywards) You need the newest Alsa stuff out
> there. I doubt even this is new enough though.
> 
> - Mark

I fixed my ALSA problem.  I booted off the 2005.0 LiveCD and rebuilt my
kernel with genkernel (based off the LiveCD's config), then rebooted
with the new kernel and emerged alsa-driver.  alsamixer worked fine and
I got my card unmuted.  A funny thing about it is that although sound
was playing I couldn't hear it through my speakers until I unplugged the
speakers from the back of the computer and plugged them back into the
headphone jack in the front.  Go figure...
-Michael Sullivan-

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes [SOLVED]

[Norberto Bensa]

Michael Sullivan wrote:
> A funny thing about it is that although sound
> was playing I couldn't hear it through my speakers until I unplugged the
> speakers from the back of the computer and plugged them back into the
> headphone jack in the front.  Go figure...

Some motherboards (based on via chipset) have a jumper setting which disable 
(disables?) the rear audio ports. The following is from a MSI K8MM-V 
motherboard:

"If you do not want to connect to the front audio header, pins 5 & 6, 9 & 10 
have to be jumpered in order to have signal output directed to the rear audio 
ports. Otherwise, the Line-Out connector on the back panel will not 
function."


I recommend to check your motherboard's manual.

> -Michael Sullivan-

-- 
Norberto Bensa
4544-9692
Ciudad de Buenos Aires, Argentina
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes [SOLVED]

[Mark Knecht]

On 10/29/05, Michael Sullivan <michael@espersunited.com> wrote:
> On Fri, 2005-10-21 at 17:53 -0700, Mark Knecht wrote:
> > On 10/21/05, Michael Sullivan <michael@espersunited.com> wrote:
> > > >
> > >
> > > I was told by people on this list and by the Gentoo ALSA Guide that
> > > alsa-drivers conflicts with the kernel module drivers.  Should I emerge
> > > it?  It's not installed now...
> >
> > NO! Use what's in your kernel.
> >
> > My mistake on the driver name. The 810 driver is intel8x0, so I
> > assumed the HDA driver was intel_hda. Apparently the Alsa guys did the
> > naming backward.
> >
> > If you see the device under /proc/asound/cards then you did it right.
> > (And you did!)
> >
> > At a minimum you should reemerge all the Alsa support stuff but use
> > ~x86 for all of that, as per my easlier message. (in
> > /etc/portage/package.keywards) You need the newest Alsa stuff out
> > there. I doubt even this is new enough though.
> >
> > - Mark
>
> I fixed my ALSA problem.  I booted off the 2005.0 LiveCD and rebuilt my
> kernel with genkernel (based off the LiveCD's config), then rebooted
> with the new kernel and emerged alsa-driver.  alsamixer worked fine and
> I got my card unmuted.  A funny thing about it is that although sound
> was playing I couldn't hear it through my speakers until I unplugged the
> speakers from the back of the computer and plugged them back into the
> headphone jack in the front.  Go figure...
> -Michael Sullivan-
>

Hey, cool. Persistence pays off. Congrats!

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes [SOLVED]

[Jerry McBride]

> I fixed my ALSA problem. 

YEAH!!!!!!!


-- 

******************************************************************************
                     Registered Linux User Number 185956
              FSF Associate Member number 2340 since 05/20/2004
             Join me in chat at #linux-users on irc.freenode.net
    Buy an Xbox for $149.00, run linux on it and Microsoft loses $150.00!
     5:23pm  up 41 days,  7:48,  3 users,  load average: 2.95, 3.04, 3.01
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/21/05, Holly Bostick <motub@planet.nl> wrote:

>
> Well it looks like all your modules are there, so something else "must"
> be wrong:
>
> Have you run alsaconf with the card active/working as it is now?
>
> Holly

But I think what alsaconf does is discoiver cards and write stuff to
modprobe.conf. I don't think that's appropriate right now. I have
barely used amixer as I mostly work with the HDSP which is supported
by a different application. I think what's required here would be for
Michael to dig into amixer a bit more and see what he can figure out
about his device.

As far as I can tell so far we have managed to get his drivers loaded.
the snd-intel-hda is loaded. It shows up as card 0 and has an
interrupt. This is immensley better than when I started readign this
thread earlier today. Everyone helped. That's cool.

However, and this is a really ugly part about Alsa, there is no single
way to control all these cards. Michael will need to learn amixer or
figure out what other application supports this card, as hdspmixer
does for my HDSP cards. Maybe there is some other app we don't know
about.

Going to this page:

https://bugtrack.alsa-project.org/alsa-bug/view_all_bug_page.php

choosing ALSA-driver at the top right and snd_intel_hda in the search
area shows one major issue right now:

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1380

It starts:

<QUOTE>
 Hello.

I am getting very scratchy audio in my Intel HDA card besides the
sound is very low.

lspci output is:

0000:00:1b.0 0403: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family)
High Definition Audio Controller (rev 03)
</QUOTE>


One interesting comment:

<QUOTE>
First, try ALSA CVS or ALSA 1.0.10-rc1. There have been many bugs
fixed since 1.0.9-rc2.

Then, if it still doesn't work, to verify that it's not a modutils
bug, explicitly do:
rmmod snd-intel-hda
modprobe snd-intel-hda position_fix=0

Then test the sound and repeat with position_fix=1, 2, and 3.
</QUOTE>

So possibly 2.6.13-gentoo-r3 may not support this card very well, as I
suggested earlier. It's a new card.

I think that Micheal could probably work this issue through the Alsa
bug reporting feature, or by going to alsa-devel and looking for some
help there. I am about 200% certain he will be asked to update to the
most recent versions of Alsa which will require patching the kernel or
at least building stuff outside of portage. He may or may not want to
do that.

- Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Fri, 2005-10-21 at 17:13 -0700, Mark Knecht wrote:
> On 10/21/05, Holly Bostick <motub@planet.nl> wrote:
> 
> >
> > Well it looks like all your modules are there, so something else "must"
> > be wrong:
> >
> > Have you run alsaconf with the card active/working as it is now?
> >
> > Holly
> 
> But I think what alsaconf does is discoiver cards and write stuff to
> modprobe.conf. I don't think that's appropriate right now. I have
> barely used amixer as I mostly work with the HDSP which is supported
> by a different application. I think what's required here would be for
> Michael to dig into amixer a bit more and see what he can figure out
> about his device.
> 
> As far as I can tell so far we have managed to get his drivers loaded.
> the snd-intel-hda is loaded. It shows up as card 0 and has an
> interrupt. This is immensley better than when I started readign this
> thread earlier today. Everyone helped. That's cool.
> 
> However, and this is a really ugly part about Alsa, there is no single
> way to control all these cards. Michael will need to learn amixer or
> figure out what other application supports this card, as hdspmixer
> does for my HDSP cards. Maybe there is some other app we don't know
> about.
> 
> Going to this page:
> 
> https://bugtrack.alsa-project.org/alsa-bug/view_all_bug_page.php
> 
> choosing ALSA-driver at the top right and snd_intel_hda in the search
> area shows one major issue right now:
> 
> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1380
> 
> It starts:
> 
> <QUOTE>
>  Hello.
> 
> I am getting very scratchy audio in my Intel HDA card besides the
> sound is very low.
> 
> lspci output is:
> 
> 0000:00:1b.0 0403: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family)
> High Definition Audio Controller (rev 03)
> </QUOTE>
> 
> 
> One interesting comment:
> 
> <QUOTE>
> First, try ALSA CVS or ALSA 1.0.10-rc1. There have been many bugs
> fixed since 1.0.9-rc2.
> 
> Then, if it still doesn't work, to verify that it's not a modutils
> bug, explicitly do:
> rmmod snd-intel-hda
> modprobe snd-intel-hda position_fix=0
> 
> Then test the sound and repeat with position_fix=1, 2, and 3.
> </QUOTE>
> 
> So possibly 2.6.13-gentoo-r3 may not support this card very well, as I
> suggested earlier. It's a new card.
> 
> I think that Micheal could probably work this issue through the Alsa
> bug reporting feature, or by going to alsa-devel and looking for some
> help there. I am about 200% certain he will be asked to update to the
> most recent versions of Alsa which will require patching the kernel or
> at least building stuff outside of portage. He may or may not want to
> do that.
> 
> - Mark
> 

I tried those things you listed, issuing a "amixer -c 0" after each one.
None of them worked.  Also, I'm not sure if it's important, but I cannot
successfully modprobe snd-intel-hda.  I CAN successfully modprobe
snd-hda-intel...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Richard Fish]

Michael Sullivan wrote:

>I tried those things you listed, issuing a "amixer -c 0" after each one.
>None of them worked.  Also, I'm not sure if it's important, but I cannot
>successfully modprobe snd-intel-hda.  I CAN successfully modprobe
>snd-hda-intel...
>
>  
>

Not important at all...the module file is snd-hda-intel.ko, and is named 
(from lsmod) snd_hda_intel.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Richard Fish]

Michael Sullivan wrote:

>I tried those things you listed, issuing a "amixer -c 0" after each one.
>None of them worked.  Also, I'm not sure if it's important, but I cannot
>successfully modprobe snd-intel-hda.  I CAN successfully modprobe
>snd-hda-intel...
>
>  
>

Not important at all...the module file is snd-hda-intel.ko, and is named 
(from lsmod) snd_hda_intel.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Nick Rout]

On Saturday 22 October 2005 13:13, Mark Knecht wrote:

[big snip]
>
> So possibly 2.6.13-gentoo-r3 may not support this card very well, as I
> suggested earlier. It's a new card.

Thats the feeling I'm getting too, new card, newish driver, lots changelog, 
probably better to use the latest alsa-driver possible.

>
> I think that Micheal could probably work this issue through the Alsa
> bug reporting feature, or by going to alsa-devel and looking for some
> help there. I am about 200% certain he will be asked to update to the
> most recent versions of Alsa which will require patching the kernel or
> at least building stuff outside of portage. He may or may not want to
> do that.
>
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/21/05, Nick Rout <nick@rout.co.nz> wrote:
> On Saturday 22 October 2005 13:13, Mark Knecht wrote:
>
> [big snip]
> >
> > So possibly 2.6.13-gentoo-r3 may not support this card very well, as I
> > suggested earlier. It's a new card.
>
> Thats the feeling I'm getting too, new card, newish driver, lots changelog,
> probably better to use the latest alsa-driver possible.

Yeah. I'm using a very new kernel - release candidate 5 fdor 2.6.15.
I'm not sure that Alsa in even this kernel is new enough for what
Michael needs, but the file has been going through big changes:

lightning ~ # ls -la /usr/src/linux-2.6.13-gentoo-r3/sound/pci/hda/hda_intel.c
-rw-r--r--  1 root root 38904 Oct  6 10:53
/usr/src/linux-2.6.13-gentoo-r3/sound/pci/hda/hda_intel.c
lightning ~ # ls -la /usr/src/linux-2.6.14-rc5-rt3/sound/pci/hda/hda_intel.c
-rw-r--r--  1 root root 43117 Oct 21 08:59
/usr/src/linux-2.6.14-rc5-rt3/sound/pci/hda/hda_intel.c
lightning ~ #

Cheers,
Mark


>
> >
> > I think that Micheal could probably work this issue through the Alsa
> > bug reporting feature, or by going to alsa-devel and looking for some
> > help there. I am about 200% certain he will be asked to update to the
> > most recent versions of Alsa which will require patching the kernel or
> > at least building stuff outside of portage. He may or may not want to
> > do that.
> >
> --
> gentoo-user@gentoo.org mailing list
>
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Fri, 2005-10-21 at 18:00 -0700, Mark Knecht wrote:
> On 10/21/05, Nick Rout <nick@rout.co.nz> wrote:
> > On Saturday 22 October 2005 13:13, Mark Knecht wrote:
> >
> > [big snip]
> > >
> > > So possibly 2.6.13-gentoo-r3 may not support this card very well, as I
> > > suggested earlier. It's a new card.
> >
> > Thats the feeling I'm getting too, new card, newish driver, lots changelog,
> > probably better to use the latest alsa-driver possible.
> 
> Yeah. I'm using a very new kernel - release candidate 5 fdor 2.6.15.
> I'm not sure that Alsa in even this kernel is new enough for what
> Michael needs, but the file has been going through big changes:
> 
> lightning ~ # ls -la /usr/src/linux-2.6.13-gentoo-r3/sound/pci/hda/hda_intel.c
> -rw-r--r--  1 root root 38904 Oct  6 10:53
> /usr/src/linux-2.6.13-gentoo-r3/sound/pci/hda/hda_intel.c
> lightning ~ # ls -la /usr/src/linux-2.6.14-rc5-rt3/sound/pci/hda/hda_intel.c
> -rw-r--r--  1 root root 43117 Oct 21 08:59
> /usr/src/linux-2.6.14-rc5-rt3/sound/pci/hda/hda_intel.c
> lightning ~ #
> 
> Cheers,
> Mark
> 
> 
> >
> > >
> > > I think that Micheal could probably work this issue through the Alsa
> > > bug reporting feature, or by going to alsa-devel and looking for some
> > > help there. I am about 200% certain he will be asked to update to the
> > > most recent versions of Alsa which will require patching the kernel or
> > > at least building stuff outside of portage. He may or may not want to
> > > do that.
> > >
> > --
> > gentoo-user@gentoo.org mailing list
> >
> >
> 

I put all the alsa stuff I had currently installed
in /etc/portage/package.unmask and /etc/portage/package.keywords and
upgraded alsa-headers, alsa-lib, and alsa-utils, but amixer still
fails...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Nick Rout]

On Sat, October 22, 2005 7:25 am, Mark Knecht said:
> On 10/21/05, Michael Sullivan <michael@espersunited.com> wrote:
> <SNIP>
>> > Good luck,
>> > Mark
>>
>> I think I've done everything you said to, but it still doesn't work.
>> Here's my kernel config:
>
> Indeed, it appears at first glance that you did.
> <SNIP>
>> Here's uname -a:
>>
>> camille ~ # uname -a
>> Linux camille 2.6.13-gentoo-r3 #1 Fri Oct 21 10:18:35 CDT 2005 i686
>> Intel(R) Celeron(R) CPU 2.66GHz GenuineIntel GNU/Linux
>
> Good. No more SMP. Unfortunately, no better results either.
>
>>
>> Here's lsmod (if you need it):
>>
>> camille ~ # lsmod
>> Module                  Size  Used by
> <SNIP>
>> i2c_i801                5804  0
>> i2c_core               10896  1 i2c_i801
>
> OK, i2c seems to be loaded. That's good.
>
> <SNIP>
>>
>> I didn't see my sound modules there, so I tried to
>> start /etc/init.d/alsasound and got this:
>
> Yes, they weren't loaded.
>
>>
>>  ^[[32;01m*^[[0m Loading ALSA modules ...
>>  ^[[32;01m*^[[0m   Loading: snd-card-0 ...
>> WARNING: Error inserting snd_page_alloc
>> (/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd-page-alloc.ko):
>> Invalid module format
>> WARNING: Error inserting snd
>> (/lib/modules/2.6.13-gentoo-r3/alsa-driver/acore/snd.ko): Invalid module
>> format

****************************** see below

> <SNIP>
>
> The only time I've seen anything like this is when I messed up my
> linux link in the /usr/src directory. You haven't done that as you
> have only a single kernel source tree. These messages imply that ALL
> of alsa is messed up, not just your device driver. That see,s
> completely wrong.
>
> I cannot explain it, other than to say I'd probably do the following
> if this was my box:
>
> 1) ls -al /lib/modules  and ensure that there is only
> /lib/modules/2.6.13-gentoo-r3
>
> 2) rm -rf /lib/modules/2.6.13-gentoo-r3  to completely remove all the
> existing modules.
>
> 3) cd /usr/src/linux
>
> 4) make clean
>
> 5) make && make modules_install
>
> 6) Copy over the new kernel, check that /lib/modules has the new
> modules, then reboot and test again.
>
> My real suspicion here is that 2.6.14-gentoo-r3 doesn't actually have
> support for this card, or that the card is not well supported at all.
> Using Google I get very few results for snd_intel_hda

It entered the vanilla kernel at 2.6.12

The last set of error messages that Michael showed show errors arising
from alsa-driver drivers. He can't have the kernel alsa drivers and the
alsa-driver package installed at the same time. (acyually this is shown
above, marked *** by me)

>
> Cheers,
> Mark
>
> --
> gentoo-user@gentoo.org mailing list
>
>


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Holly Bostick]

Michael Sullivan schreef:
> On Thu, 2005-10-20 at 06:11 -0700, Mark Knecht wrote:
> 
>> Please give me a bit of info:
>> 
>> lspci
>> 
>> Basically I'm concerned that the hardware you have and the modules 
>> you are trying to load aren't matching up.
> 

Here is the kernel help for the snd_hda_intel driver:

 Say Y here to include support for Intel "High Definition
  x Audio" (Azalia) motherboard devices.
  x

  x To compile this driver as a module, choose M here: the module
  x will be called snd-hda-intel.
  x
  x Symbol: SND_HDA_INTEL [=n]
  x Prompt: Intel HD Audio
  x   Defined at sound/pci/Kconfig:530
  x   Depends on: !M68K && SOUND!=n && PCI && SND
  x   Location:
  x     -> Device Drivers
  x       -> Sound
  x         -> Advanced Linux Sound Architecture
  x           -> Advanced Linux Sound Architecture (SND [=m])
  x             -> PCI devices
  x   Selects: SND_PCM

As I see it, there is no further selection needed to get this detected,
but are we certain that this driver (which does not really specify which
revisions/versions of the motherboard chipset resources are in fact
supported) works with this exact device:

> 0000:00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW
> (ICH6 Family) High Definition Audio Controller (rev 03)

?

Perhaps there is undocumented support not built, I went to Device
Drivers=>I2C support, and found this:

CONFIG_I2C_I801:
x
  x If you say yes to this option, support will be included for the Intel
  x 801 family of mainboard I2C interfaces.  Specifically, the following
  x versions of the chipset are supported:
  x   82801AA
  x   82801AB
  x   82801BA
  x   82801CA/CAM
  x   82801DB
  x   82801EB/ER (ICH5/ICH5R)
  x   6300ESB
  x   ICH6
  x   ICH7
  x   ESB2
  x
  x This driver can also be built as a module.  If so, the module
  x will be called i2c-i801.

  x

  x Symbol: I2C_I801 [=m]
  x Prompt: Intel 82801 (ICH)
  x   Defined at drivers/i2c/busses/Kconfig:110
  x   Depends on: I2C && PCI
  x   Location:
  x     -> Device Drivers
  x       -> I2C support
  x         -> I2C support (I2C [=y])
  x           -> I2C Hardware Bus support
  x
  x

It seems quite possible that this advanced board might need I2c support
statically compiled before the various components can properly
communicate with each other and the kernel.

Hope this helps.
Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Thu, 2005-10-20 at 16:36 +0200, Holly Bostick wrote:
> Michael Sullivan schreef:
> > On Thu, 2005-10-20 at 06:11 -0700, Mark Knecht wrote:
> > 
> >> Please give me a bit of info:
> >> 
> >> lspci
> >> 
> >> Basically I'm concerned that the hardware you have and the modules 
> >> you are trying to load aren't matching up.
> > 
> 
> Here is the kernel help for the snd_hda_intel driver:
> 
>  Say Y here to include support for Intel "High Definition
>   x Audio" (Azalia) motherboard devices.
>   x
> 
>   x To compile this driver as a module, choose M here: the module
>   x will be called snd-hda-intel.
>   x
>   x Symbol: SND_HDA_INTEL [=n]
>   x Prompt: Intel HD Audio
>   x   Defined at sound/pci/Kconfig:530
>   x   Depends on: !M68K && SOUND!=n && PCI && SND
>   x   Location:
>   x     -> Device Drivers
>   x       -> Sound
>   x         -> Advanced Linux Sound Architecture
>   x           -> Advanced Linux Sound Architecture (SND [=m])
>   x             -> PCI devices
>   x   Selects: SND_PCM
> 
> As I see it, there is no further selection needed to get this detected,
> but are we certain that this driver (which does not really specify which
> revisions/versions of the motherboard chipset resources are in fact
> supported) works with this exact device:
> 
> > 0000:00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW
> > (ICH6 Family) High Definition Audio Controller (rev 03)
> 
> ?
> 
> Perhaps there is undocumented support not built, I went to Device
> Drivers=>I2C support, and found this:
> 
> CONFIG_I2C_I801:
> x
>   x If you say yes to this option, support will be included for the Intel
>   x 801 family of mainboard I2C interfaces.  Specifically, the following
>   x versions of the chipset are supported:
>   x   82801AA
>   x   82801AB
>   x   82801BA
>   x   82801CA/CAM
>   x   82801DB
>   x   82801EB/ER (ICH5/ICH5R)
>   x   6300ESB
>   x   ICH6
>   x   ICH7
>   x   ESB2
>   x
>   x This driver can also be built as a module.  If so, the module
>   x will be called i2c-i801.
> 
>   x
> 
>   x Symbol: I2C_I801 [=m]
>   x Prompt: Intel 82801 (ICH)
>   x   Defined at drivers/i2c/busses/Kconfig:110
>   x   Depends on: I2C && PCI
>   x   Location:
>   x     -> Device Drivers
>   x       -> I2C support
>   x         -> I2C support (I2C [=y])
>   x           -> I2C Hardware Bus support
>   x
>   x
> 
> It seems quite possible that this advanced board might need I2c support
> statically compiled before the various components can properly
> communicate with each other and the kernel.
> 
> Hope this helps.
> Holly

I recompiled the kernel removing the SMP and adding what you listed
above.  You didn't say what part of I2C Hardware Bus support I should
add, so I checked everything that said Intel on the Hardware Bus support
submenu.  It still doesn't detect my snd-hda-intel...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Nick Rout]

On Thu, 20 Oct 2005 07:59:36 -0500
Michael Sullivan wrote:

> camille ~ # modprobe snd-hda-intel
> WARNING: Error inserting snd_hda_codec
> (/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-codec.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> FATAL: Error inserting snd_hda_intel
> (/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-intel.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> 
> What's next?

What do you mean "what next". It tells you in two places "see dmesg"


-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Fri, 2005-10-21 at 09:11 +1300, Nick Rout wrote:
> On Thu, 20 Oct 2005 07:59:36 -0500
> Michael Sullivan wrote:
> 
> > camille ~ # modprobe snd-hda-intel
> > WARNING: Error inserting snd_hda_codec
> > (/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-codec.ko):
> > Unknown symbol in module, or unknown parameter (see dmesg)
> > FATAL: Error inserting snd_hda_intel
> > (/lib/modules/2.6.13-gentoo-r3/kernel/sound/pci/hda/snd-hda-intel.ko):
> > Unknown symbol in module, or unknown parameter (see dmesg)
> > 
> > What's next?
> 
> What do you mean "what next". It tells you in two places "see dmesg"

I looked at dmesg; It made no sense to me.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Sascha Lucas]

On Wed, 19 Oct 2005, Michael Sullivan wrote:

> Can this be done with genkernel?  I've always used genkernel in the
> past.  All attempts at building and installing kernels manually have

yes you can use genkenel. I also use it. And it's wrong that genkernel is 
only for wimps :-). It's also for the lazy (saves you typing some 
commands).

You may run following commands, just a try:

# mv /etc/kernels/* /tmp
# genkernel --menuconfig kernel

In the menuconfig enable your sound-card as module if not allready:

Symbol: SND_HDA_INTEL [=m] 
Location:
   -> Device Drivers
      -> Sound
         -> Advanced Linux Sound Architecture
            -> Advanced Linux Sound Architecture (SND [=m])
               -> PCI devices

after this you have a fresh kernel in /boot. Make shure you have a line in 
your grub.conf like this:

title=GNU/Linux (2.6.13-gentoo-r3)
   root (hd0,1)
   kernel /boot/kernel-genkernel-x86-2.6.13-gentoo-r3 root=/dev/hda2

please adopt the root () statment, the root= paramter and the kernel 
version to your needs.

If not allready merge the gentoolkit:

# emerge gentoolkit

then look for alsa packages:

# equery list alsa*

It's ok to have installed media-libs/alsa-lib media-sound/alsa-utils 
and media-sound/alsa-headers. Make shure to remove sound/alsa-driver.

# emerge -C sound/alsa-driver

Configure /etc/modules.d/alsa. You just have to edit one line in this 
file. To get the orginal version type:

# cp /usr/portage/media-sound/alsa-utils/files/alsa-modules.conf-rc /etc/modules.d/alsa

Then set the line to look like this: alias snd-card-0 snd-hda-intel

Finaly run:

# modules-update

Thats all. Cross your fingers and reboot.

Sascha.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Thu, 2005-10-20 at 10:38 +0200, Sascha Lucas wrote:
> On Wed, 19 Oct 2005, Michael Sullivan wrote:
> 
> > Can this be done with genkernel?  I've always used genkernel in the
> > past.  All attempts at building and installing kernels manually have
> 
> yes you can use genkenel. I also use it. And it's wrong that genkernel is 
> only for wimps :-). It's also for the lazy (saves you typing some 
> commands).
> 
> You may run following commands, just a try:
> 
> # mv /etc/kernels/* /tmp
> # genkernel --menuconfig kernel
> 
> In the menuconfig enable your sound-card as module if not allready:
> 
> Symbol: SND_HDA_INTEL [=m] 
> Location:
>    -> Device Drivers
>       -> Sound
>          -> Advanced Linux Sound Architecture
>             -> Advanced Linux Sound Architecture (SND [=m])
>                -> PCI devices
> 
> after this you have a fresh kernel in /boot. Make shure you have a line in 
> your grub.conf like this:
> 
> title=GNU/Linux (2.6.13-gentoo-r3)
>    root (hd0,1)
>    kernel /boot/kernel-genkernel-x86-2.6.13-gentoo-r3 root=/dev/hda2
> 
> please adopt the root () statment, the root= paramter and the kernel 
> version to your needs.
> 
> If not allready merge the gentoolkit:
> 
> # emerge gentoolkit
> 
> then look for alsa packages:
> 
> # equery list alsa*
> 
> It's ok to have installed media-libs/alsa-lib media-sound/alsa-utils 
> and media-sound/alsa-headers. Make shure to remove sound/alsa-driver.
> 
> # emerge -C sound/alsa-driver
> 
> Configure /etc/modules.d/alsa. You just have to edit one line in this 
> file. To get the orginal version type:
> 
> # cp /usr/portage/media-sound/alsa-utils/files/alsa-modules.conf-rc /etc/modules.d/alsa
> 
> Then set the line to look like this: alias snd-card-0 snd-hda-intel
> 
> Finaly run:
> 
> # modules-update
> 
> Thats all. Cross your fingers and reboot.
> 
> Sascha.
> 

It didn't go.  I did everything you said, but when I booted with the new
kernel it gave me a kernel panic.  It said something about not being
able to find the root fs.  Should there be an initrd line?  Also, I
saved the output of the genkernel script.  I mv'd the files
from /etc/kernel to /tmp, but I still saw this line in the genkernel
output:

* Linux Kernel 2.6.13-gentoo-r3 for x86...
* kernel: >> Running mrproper...
* config: Using config from /usr/share/genkernel/x86/kernel-config-2.6
*         Previous config backed up to .config.bak
*         >> Running oldconfig...

Should this be happening?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Sascha Lucas]

On Thu, 20 Oct 2005, Michael Sullivan wrote:

> kernel it gave me a kernel panic.  It said something about not being
> able to find the root fs.  Should there be an initrd line?  Also, I

you only need an initrd if you have some special hardware. Do you? I.E. 
sata controler (intel ICH6), SCSI, or some special things with your root 
filesystem like lvm, md...

> saved the output of the genkernel script.  I mv'd the files
> from /etc/kernel to /tmp, but I still saw this line in the genkernel
> output:
>
> * Linux Kernel 2.6.13-gentoo-r3 for x86...
> * kernel: >> Running mrproper...
> * config: Using config from /usr/share/genkernel/x86/kernel-config-2.6
> *         Previous config backed up to .config.bak
> *         >> Running oldconfig...
>
> Should this be happening?

thats fine. this lines told you, that a generic kernel-config (like on 
livecd) is used.

The first thing is to make your kernel booting. This is not a hard thing, 
if you have no special setup. The siplest case is that your root=/dev/hdxx 
in grub.conf is wrong. Type "mount" and see what device is mounted for 
"/boot". If you have none for "/boot" look for "/". Then use this device 
in the root= parameter.

Sascha.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Sascha Lucas]

> If you have none for "/boot" look for "/". Then use this device in the root= 
> parameter.

sorry pleas only look for / not for /boot

S.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Michael Sullivan]

On Thu, 2005-10-20 at 17:13 +0200, Sascha Lucas wrote:
> On Thu, 20 Oct 2005, Michael Sullivan wrote:
> 
> > kernel it gave me a kernel panic.  It said something about not being
> > able to find the root fs.  Should there be an initrd line?  Also, I
> 
> you only need an initrd if you have some special hardware. Do you? I.E. 
> sata controler (intel ICH6), SCSI, or some special things with your root 
> filesystem like lvm, md...
> 
> > saved the output of the genkernel script.  I mv'd the files
> > from /etc/kernel to /tmp, but I still saw this line in the genkernel
> > output:
> >
> > * Linux Kernel 2.6.13-gentoo-r3 for x86...
> > * kernel: >> Running mrproper...
> > * config: Using config from /usr/share/genkernel/x86/kernel-config-2.6
> > *         Previous config backed up to .config.bak
> > *         >> Running oldconfig...
> >
> > Should this be happening?
> 
> thats fine. this lines told you, that a generic kernel-config (like on 
> livecd) is used.
> 
> The first thing is to make your kernel booting. This is not a hard thing, 
> if you have no special setup. The siplest case is that your root=/dev/hdxx 
> in grub.conf is wrong. Type "mount" and see what device is mounted for 
> "/boot". If you have none for "/boot" look for "/". Then use this device 
> in the root= parameter.
> 
> Sascha.

Then why does Linux not continue to boot when I specify a kernel in
grub.conf without an initrd?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Holly Bostick]

Michael Sullivan schreef:
> On Thu, 2005-10-20 at 17:13 +0200, Sascha Lucas wrote:

>> you only need an initrd if you have some special hardware. Do you?
>> I.E. sata controler (intel ICH6), SCSI, or some special things with
>> your root filesystem like lvm, md...
> 
> Then why does Linux not continue to boot when I specify a kernel in 
> grub.conf without an initrd?

Because you still need one specified in grub.conf? Genkernel makes one
by default, so it must be specified in grub.conf. If you build a kernel
by hand, you most likely don't have an initrd (unless you're using one
for gensplash), so it need not be specified (unless needed for gensplash).

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/20/05, Michael Sullivan <michael@espersunited.com> wrote:
>
> Then why does Linux not continue to boot when I specify a kernel in
> grub.conf without an initrd?

I don't use initrd's at all. I doubt you need one for your machine.
Set it up like this:

title  Gentoo 2.6.13-gentoo-r3
root (hd0,0)
kernel (hd0,0)/boot/bzImage-2.6.13-gentoo-r3 root=/dev/sda3

NOTE: This assumes a separate /boot partition as per the standard
Gentoo install docs.

- Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mike Williams]

On Thursday 20 October 2005 16:44, Mark Knecht wrote:
> I don't use initrd's at all. I doubt you need one for your machine.

If the default kernel config genkernel supplies doesn't compile all the 
appropriate drivers in, he'll need to use the initrd/initramfs generated.
It's fairly obvious Michael does need to, unless he can reconfigure the kernel 
to suit his needs more specifically.

-- 
Mike Williams
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mark Knecht]

On 10/20/05, Mike Williams <mike@gaima.co.uk> wrote:
> On Thursday 20 October 2005 16:44, Mark Knecht wrote:
> > I don't use initrd's at all. I doubt you need one for your machine.
>
> If the default kernel config genkernel supplies doesn't compile all the
> appropriate drivers in, he'll need to use the initrd/initramfs generated.
> It's fairly obvious Michael does need to, unless he can reconfigure the kernel
> to suit his needs more specifically.
>

OK, right. I only meant that I haven't seen anything in his specific
hardware that makes me think he *has* to have one. Unless I missed
something, which happens every day, it's a pretty standard, if modern,
PC. It should be possible to build everything into the kernel so no
initrd is required, if he wants to do it that way.

I know he's nervous about building kernels. He'll be much better off
if he gets past that. (My opinion only.)

- Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mike Williams]

On Thursday 20 October 2005 17:53, Mark Knecht wrote:
> OK, right. I only meant that I haven't seen anything in his specific
> hardware that makes me think he *has* to have one. Unless I missed
> something, which happens every day, it's a pretty standard, if modern,
> PC. It should be possible to build everything into the kernel so no
> initrd is required, if he wants to do it that way.

I can't remember what hardware he has :o)
Sascha appears to though, and spotted the problem.

> I know he's nervous about building kernels. He'll be much better off
> if he gets past that. (My opinion only.)

Oh aye, one of the testing guys here is jumping in at the deep end, and asking 
me lots of questions. He'll learn eventually, and be better off for it.

-- 
Mike Williams
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Sascha Lucas]

> Then why does Linux not continue to boot when I specify a kernel in
> grub.conf without an initrd?

The answer is: you have a sata controler. Output from your lsmmod:

ata_piix                6196  2

Make a kernel with this controler enabled:

Symbol: SCSI_ATA_PIIX [=n]
  Prompt: Intel PIIX/ICH SATA support
    Defined at drivers/scsi/Kconfig:452
    Depends on: SCSI!=n && SCSI_SATA && PCI
    Location:
      -> Device Drivers
        -> SCSI device support
          -> SCSI device support (SCSI [=y])
            -> SCSI low-level drivers
              -> Serial ATA (SATA) support (SCSI_SATA [=n])

Compile this into kernel not as module.

Sascha.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] My Continuing ALSA Woes

[Mike Williams]

On Thursday 20 October 2005 16:25, Michael Sullivan wrote:
> Then why does Linux not continue to boot when I specify a kernel in
> grub.conf without an initrd?

The default genkernel kernel config is designed to use the initrd/initramfs it 
configures.
You could be brave, and use the --bootloader=grub option to genkernel too. 
Backup and remove your current grub.conf first, and make absolutely sure 
there is only one line in your fstab that contains the phrase 
"[:space:]/[:space:]", it's a bug I've notice that I should submit to 
bugzilla. If it works, you'll automatically have a properly configured 
grub.conf, that can also be automatically updated by genkernel for any new 
kernels!

-- 
Mike Williams
-- 
gentoo-user@gentoo.org mailing list