You are not logged in.
Here is the information about my device,
output from "lspci | grep -i aud > audinfo"
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
I recently upgraded to kernel version 2.6.28.1-1 and then today 2.6.28.2-1 and in both versions sound is not working, it was working as prior to my 2.6.28.1-1 upgrade, My computer is a HP mini 1000.
I am wondering what I have to do, lsmod shows that the module snd_hda-intel is loaded,
output from "lsmod | grep -i snd > sndinfo"
snd_pcsp 11048 0
snd_seq_oss 31872 0
snd_seq_midi_event 8192 1 snd_seq_oss
snd_seq 49968 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 8204 2 snd_seq_oss,snd_seq
snd_hda_intel 412852 0
snd_hwdep 9092 1 snd_hda_intel
snd_pcm_oss 40192 0
snd_pcm 70020 3 snd_pcsp,snd_hda_intel,snd_pcm_oss
snd_timer 21384 2 snd_seq,snd_pcm
snd_page_alloc 10120 2 snd_hda_intel,snd_pcm
snd_mixer_oss 16512 1 snd_pcm_oss
snd 50852 10 snd_pcsp,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 8160 1 snd
I was thinking maybe I have to compile a module in or go digging around the kernel, But having semi-recently moved to Arch linux from Gentoo linux I have no idea howto do this in Arch, although I am unsure as to wheither or not I actualy have to.
I appologise if I have left anything out and/or made some dumb mistake.
And yes, all my channels in alsamixer are unmuted
Thanks again,
Ducky,
[SOLVED]
Solved by using kernel 2.6.29-3 and details can be found in this thread:
http://bbs.archlinux.org/viewtopic.php?pid=532903
Last edited by suicideducky (2009-04-14 22:54:00)
Offline
Just to confirm, I've got the exact same problem with my 82801G, as well, it's not working since the 2.6.28.1-1 kernel.
Offline
I think snd_hda_intel is not assigned any number, which could explain no sound issue. Have you tried alsaconf? http://wiki.archlinux.org/index.php/ALSA
Here is the output of my lsmod:
snd_pcsp 11964 0
snd_seq_oss 34560 0
snd_seq_midi_event 8320 1 snd_seq_oss
snd_seq 57312 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 8276 2 snd_seq_oss,snd_seq
snd_hda_intel 529460 1
snd_hwdep 9608 1 snd_hda_intel
snd_pcm_oss 44416 0
snd_pcm 81608 3 snd_pcsp,snd_hda_intel,snd_pcm_oss
snd_timer 23632 2 snd_seq,snd_pcm
snd_page_alloc 10768 2 snd_hda_intel,snd_pcm
snd_mixer_oss 17856 1 snd_pcm_oss
snd 64072 12 snd_pcsp,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 8544 1 snd
Last edited by ahcaliskan (2009-01-28 13:17:39)
Offline
ahcaliskan: I've checked the link (http://wiki.archlinux.org/index.php/ALSA) but didn't find anything obvious. Everything seems normal except I hear no sound.
In my case, snd_hda_intel does have a number assigned (though I've got no clue what the number means and "man lsmod" isn't too much of a help). Im not sure but suicideducky might be using a 64 bit version of the kernel (which is what I'm using as well), could it be the case that those modules behave correctly only on 32 bit kernel versions?
This: http://rafb.net/p/efUVQq32.html is some more info about my HW which I've obtained using the aadebug script mentioned on the wiki page.
Offline
Try removing "model=3stack" or replace 3stack with "auto" from /etc/modprobe.d/sound!
If that doesn't work, I believe that it's a bug, please file a bug report.
Last edited by ahcaliskan (2009-01-28 16:02:16)
Offline
OK, silly me, I've removed all the "option snd-hda-intel *" lines from /etc/modprobe.conf, rebooted and I can hear sound now.
Thanks ahcaliskan. Hope this will help suicideducky too.
Offline
Well I glad to hear that it worked out for you
Last edited by ahcaliskan (2009-01-28 16:03:58)
Offline
Glad to hear yours is working
Im using a 32 bit kernel, processor is an intel atom.
All the lines in /etc/modprobe.d/sound are alias commnad (I assume created by alsaconf).
The only lines present in modprobe.conf are comments.
Sound still not working
I also tried adding !snd_pscp or whatever to the module listing in rc.conf it is as mentioned in the news article, but made no difference.
Ducky.
Offline
do you have a working codec? Try
cat /proc/asound/card0/codec#0 | grep Codec
Also, could you do a aadebug and post it here?
http://alsa.opensrc.org/index.php/Aadebug
Last edited by ahcaliskan (2009-01-29 13:49:58)
Offline
I ran cat /proc/asound/card0/codec#0 | grep -i codec > output,txt, and here is the output:
Codec: IDT 92HD75B2X5
and the output from the aadebug script you asked me to run is found here:
http://pastebin.com/m50074789
Thank again,
Ducky.
Offline
It appears to be that your sound card for now has limited support by alsa, which doesn't seem to recognize your model. So it's quite interesting that it worked for you after all.
http://forums.opensuse.org/hardware/lap … sound.html
https://help.ubuntu.com/community/HdaIntelSoundHowto
However, ubuntu and suse people have fixed no sound issue, so it should work with right alsa driver:
https://bugzilla.novell.com/show_bug.cgi?id=467381
Have you tried to load snd-hda-intel driver with specific model option in /etc/modprobe.d/sound? If not, try this line:
options snd-hda-intel model=ref
and then reboot
here is my /etc/modprobe.d/sound file:
alias snd-card-0 snd-hda-intel
options snd-hda-intel model=6stack-dig enable=1 index=0
alias sound-slot-0 snd-hda-intel
You can find more info about snd-hda-intel driver configuration:
http://www.mjmwired.net/kernel/Document … on.txt#739
Last edited by ahcaliskan (2009-01-30 13:18:34)
Offline
It seems I have same problem here. But instead of fighting with new alsa compilation I've downgraded with my kernel with:
sudo pacman -U kernel26-2.6.27.10-1-x86_64.pkg.tar.gz
Sound works fine again but I'm not sure if it's ok to wait someone to fix this
Note: Because I am using NVIDIA drivers, I had to re-install it after downgrade.
Offline
Ok, I couldn't resist myself and done some reseach, and have a working sound with new kernel yuppie
Here is the solution I've found:
*First try to find out which codec you're using with:
head -n 1 /proc/asound/card0/codec*
*My output was like:
==> /proc/asound/card0/codec#0 <==
Codec: IDT 92HD71B7X
==> /proc/asound/card0/codec#2 <==
Codec: Generic 10de ID 6
*So (I guess) my codec was "92HD71B7X" then try to find your model using your codec in the "module snd-hda-intel" part of this documentation
http://www.mjmwired.net/kernel/Document … ration.txt
*Bad thing about it, It's not up-to-date. I couldn't find an updated version of this document and unfortunetly my codec was not on that list (maybe you can find yours) but I've googled "92HD71B7X" and (in one of the suse forms) I found out that my probabilites are;
STAC92HD71B*
============
ref Reference board
dell-m4-1 Dell desktops
dell-m4-2 Dell desktops
dell-m4-3 Dell desktops
hp-m4 HP dv laptops
*I'm using a HP HDX16, so I've chosen hp-m4 and updated my /etc/modprobe.conf like this;
options snd-pcsp index=2
options snd-hda-intel model=hp-m4 enable_msi=1
*Unmuted channels with alsamixer and SOLVED for me, everything works;
*I hope this helps you too, guys. Sorry for the format of this message, I'm new and don't know how to add "Code" tags
Offline
Hey all, sorry for the beyond late reply >.<
Been really busy, so my output is:
[chris@myhost ~]$ head -n 1 /proc/asound/card0/codec#0
Codec: IDT 92HD75B2X5
There is not listing for a second codec, also within the card0 directory only the following appears:
codec#0
id
oss_mixer
pcm0c
pcm0p
pcm1p
and im currently running kernel version 2.6.28.4-1
I keep upgrading hoping in vain it will "fix itself", but alas it does not.
As far as I can tell, that document you linked me to does not mention my specific card, unless I have also lost the ability to read
Any help I can get is much apprechiated...
I'm running the alsa upgrade script that I found by following ahcaliskan's links, lets hope it works xP
Interesting fault though IMO, especially because HP are releasing this laptop with linux as one of the options, unless it has a different sound card then they surely must have a solution as they are trying to market it as not only a netbook but a multimedia platform. I may try get in contact with their tech support and see what I can digg up.
Thanks again,
Chris,
Offline
Ok, so the script did not work, "configuration error" It appears this is due to it being unable to find the path to the kernel headers, I can retry this later, but I just noticed at boot it says:
::restoring alsa levels
hardware not recognised "HDA-intel" blah blah hardware information
Hardware initialized using guess message
many fail messages
Offline
Why not try to compile it by yourself, that is, fetch the PKGBUILD for alsa-libs and alsa-utils and compile them, while compiling the alsa driver for your current kernel. Good luck, and I'll try my best to help you solve this sound issue. Please, follow the ubuntu users self-help install procedures:
Re: Audio Issue (hp mini note 1000) (STAC92xx chipset)
Well, since there is not much input, here is the solution that I worked out myselfdownload and compile:
alsa-driver-1.0.18.tar.bz2with ./configure --with-cards=hda-intel --with-kernel=/usr/src/linux-headers-$(uname -r) && make && make install
then:
alsa-lib-1.0.18.tar.bz2
alsa-utils-1.0.18.tar.bz2with simpe ./configure && make && make install
Make sure that
/etc/modprobe.d/alsa-base
Has line:
options snd-hda-intel model=refFire up alsamixer and make sure the PCM, Master, Front etc are turned up.
Offline
I looked at those instructions, and thought it be easier to try the automated script first, but now that we are here...
The alsa-utils and alsa-lib packages have just gone to version 1.0.19-1 in pacman and it prompted to install them, but I will download and compile later if necessary, although from the instructions it has no additional options passed to it so this may not be needed.
But about alsa-drivers, this is included in the kernel yes? how would one go about compiling this?
Thanks again, Chris.
Offline
the driver is included in the kernel, however v1.0.19 will be included in next release of the linux kernel, ie 2.6.29. What you could do is to patch the current kernel with the newest version of alsa driver, and compile the kernel through ABS. Read this post, there is a link to compile instructions:
http://bbs.archlinux.org/viewtopic.php?id=63987
Offline
the driver is included in the kernel, however v1.0.19 will be included in next release of the linux kernel, ie 2.6.29. What you could do is to patch the current kernel with the newest version of alsa driver, and compile the kernel through ABS. Read this post, there is a link to compile instructions:
http://bbs.archlinux.org/viewtopic.php?id=63987
Hey, so looking at that, sorry for all the noob questions and all, but do I use the arch supplied kernel or fetch one from kernel.org?
And what version of alsa drivers do I need to grab? I presume 1.0.19?
Sorry for my continous questioning, just with the kernel and all, its still one of those parts of the system which I am somewhat reluctant to play with. I have compiled a kernel before, in Gentoo, but this was after using the same laptop for like 3 years + so I knew the hardware and had a rescure disk on standby, as my new baby does not have a cd drive I am somewhat more carefull.
Thanks again, so much,
Chris.
Offline
Does 2.6.29 actually fix the problem?
Offline
Don't worry, ask as many questions you like, that's how people learn new stuff
1. You can download the the latest kernel and build it with your own PKGBUILD or use an example found on wiki:
http://wiki.archlinux.org/index.php/Ker … n_with_ABS
2. Or you can use the official PKGBUILD via abs.
Install abs:
pacman -Sy abs
Specify abs to fetch only the linux kernel:
abs core/kernel26
Copy the kernel26 directory from /var/abs/core/kernel26 to your home directory. And then use makepkg to build your kernel. Further reference:
http://wiki.archlinux.org/index.php/ABS
It's important to know that if you build from abs, you'll have change the PKGBUILD, in order to patch the kernel that is being automatically downloaded and compiled. You need to instruct makepkg through PKGBUILD to include the new alsa driver. If you extract the kernel you downloaded, and know where to copy the new alsa files, you'll be able to add some lines to the PKGBUILD before it compiles the kernel.
3. Another option you have is to build the alsa module without compiling the entire kernel. I mean you have the kernel source installed, so all you need to do is ./configure, make and make install in the alsa-driver directory. Download the latest alsa driver and read the INSTALL file for further instructions.
Yea, the new version of alsa is 1.0.19, which will be officially included in the next kernel release.
Last edited by ahcaliskan (2009-02-18 11:35:59)
Offline
ok, I took 3) as it seemed like the "best" (easiest) method.
Done, although still no sound >.<
I tried both ./configure and ./configure --with-cards=hda-intel
and then make and make install, install went fine.
Still no sound,
Alsa tried alsaconf (via sudo)
made sure all channels are unmuted.
Still no sound
Offline
I believe it's something with the archlinux system files. Why not try booting with a livecd to compare it with your system, and see if the sound card works that way. You could use the lastest opensuse, fedora, or ubuntu to check out what kind driver is being used, and what the configuration is like, and which sound card codec is being used. In this way you could solve the mysterious no sound issue.
Offline
Hi. I've managed to get my hands on a Compaq Mini 700, which I believe is mostly identical to the HP Mini 1000, but I also can't get a peep of sound out of it under Arch. Under Ubuntu 8.10, sound is scattered and broken, it sounds like only one in 10 sounds play. Windows, bizarrely, has no sound if the last linux OS booted was Arch, but has perfectly working sound if the last linux booted was Ubuntu 8.10.
I've tried recompiling the current arch kernel with alsa 1.0.19 built-in, but it fails complaining that values are undefined. I suspect the built-in alsa 1.0.19 requires the kernel 2.6.29 source, since in the missing values are defined in linux/input.h for 2.6.29 Release Candidates.
I've not yet tried compiling alsa outside the kernel. At a guess you'll need to disable the built-in alsa in order for your compiled alsa to work?
Offline
yes, it makes sense that you disable the built-in alsa driver source, but shouldn't the new alsa driver replace the old one when you install it after a kernel kompilation?
Offline