Thread: [Alsa-user] hda-intel codec not being detected on ICH9 chipset
Brought to you by:
perex
Menu
▾
▴
alsa-user
|
From: Peter W. <al...@we...> - 2008-05-20 11:11:20
|
First can I say if I should post this question somewhere else, please accept my apologies and let me know where! I am running ubuntu 8.04 on an Intel DQ35MP motherboard which has built-in ICH9 (ALC268 I believe) HD audio chipset. The kernel is 2.6.24-17-server When I first installed the desktop version of Ubuntu (acually it was 7.10) the audio worked. I'm not sure exactly at which point it stopped working but it might have been when I re-installed with -server version. I have trawled the web and tried many things but I just cannot get the hda-intel driver to see the codec on my motherboard. alsa-info.sh captured details are at http://pastebin.ca/1021799 I have tried uninstalling and re-installing alsa using apt-get purge and apt-get install I have tried building and installing the packagae from realtek (but that's only alsa-project's latest stable build any way I think) I have downloaded built and installed the hot daily build from alsa-project.org <http://alsa-project.org> and still no luck. Currently running 1.0.16 built on 20080516: ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/alsa-driver-hg20080516.tar.bz2 <ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/alsa-driver-hg20080516.tar.bz2> Additional info (Might already be in info capture) From demsg: [ 40.254047] ALSA /build/buildd/linux-ubuntu -modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: hda-intel: no codecs found! [ 40.254089] ACPI: PCI interrupt for device 0000:00:1b.0 disabled From lspci -v 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02) Subsystem: Intel Corporation Unknown device 0013 Flags: fast devsel, IRQ 23 Memory at 922a0000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Capabilities: [70] Express Unknown type IRQ 0 I have also tried using varous MODEL= options to loading the module (5stack, 3stack, acer) I have not yet tried doing anything with the debug option because I don't know how to use it. Any help appreciated. Let me know if you need more information. Thanks, Peter |
|
From: Nigel H. <cav...@al...> - 2008-05-20 14:25:22
|
On Tuesday 20 May 2008 13:11, Peter Westley wrote: > First can I say if I should post this question somewhere else, please > accept my apologies and let me know where! > > I am running ubuntu 8.04 on an Intel DQ35MP motherboard which has > built-in ICH9 (ALC268 I believe) HD audio chipset. The kernel is > 2.6.24-17-server > > When I first installed the desktop version of Ubuntu (acually it was > 7.10) the audio worked. I'm not sure exactly at which point it stopped > working but it might have been when I re-installed with -server version. > > I have trawled the web and tried many things but I just cannot get the > hda-intel driver to see the codec on my motherboard. > > alsa-info.sh captured details are at http://pastebin.ca/1021799 > > I have tried uninstalling and re-installing alsa using apt-get purge and > apt-get install > I have tried building and installing the packagae from realtek (but > that's only alsa-project's latest stable build any way I think) > I have downloaded built and installed the hot daily build from > alsa-project.org <http://alsa-project.org> and still no luck. > > Currently running 1.0.16 built on 20080516: > ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/alsa-driver-hg20080516 >.tar.bz2 > <ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/alsa-driver-hg2008051 >6.tar.bz2> > > Additional info (Might already be in info capture) > > From demsg: > [ 40.254047] ALSA /build/buildd/linux-ubuntu > -modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa-driver/pci/hda/ >../../alsa-kernel/pci/hda/hda_intel.c:1892: hda-intel: no codecs found! > [ 40.254089] ACPI: PCI interrupt for device 0000:00:1b.0 disabled > > From lspci -v > 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio > Controller (rev 02) > Subsystem: Intel Corporation Unknown device 0013 > Flags: fast devsel, IRQ 23 > Memory at 922a0000 (64-bit, non-prefetchable) [size=16K] > Capabilities: [50] Power Management version 2 > Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ > Queue=0/0 Enable- > Capabilities: [70] Express Unknown type IRQ 0 > > I have also tried using varous MODEL= options to loading the module > (5stack, 3stack, acer) > I have not yet tried doing anything with the debug option because I > don't know how to use it. > > Any help appreciated. > Let me know if you need more information. > > Thanks, > Peter Hi Peter. Upon reading your post, I thought there might be some conflict going as to which soundcard was set as card0, as you have both snd-hda-intel, and a TV card with a sound component. At least your lspci indicates it. My Hauppauge Win TV express card has snd-bt87x, which is one of those "abnormal" drivers that try to grab card0, and which need to have the following line set in /etc/modules.d/alsa-base (see below), otherwise you can get conflicts where both soundcards are trying to grab card0, and sometimes no cards appear in /proc/asound/cards, although lsmod shows the modules to be loaded options snd-bt87x index=2. I thought this may be the case with your problem, and a bit of googling shows aoptions cx88-alsa index=2 (all these dodgy drivers are indexed as 2), in someones /etc/modprobe.d/alsa-base. It doesn't show in your options list on the pastebin file, but that may be because it doesn't start with "snd". Do you have that one there? I also read that someone had add snd-hda-intel to /etc/modules to get sound to work. Not sure if that was for Hardy Heron though. Did you roll your own server kernel? Nigel. |
|
From: stan <ghj...@co...> - 2008-05-20 18:27:33
|
Peter Westley wrote: > First can I say if I should post this question somewhere else, please > accept my apologies and let me know where! > > I am running ubuntu 8.04 on an Intel DQ35MP motherboard which has > built-in ICH9 (ALC268 I believe) HD audio chipset. The kernel is > 2.6.24-17-server > > When I first installed the desktop version of Ubuntu (acually it was > 7.10) the audio worked. I'm not sure exactly at which point it stopped > working but it might have been when I re-installed with -server version. > > I have trawled the web and tried many things but I just cannot get the > hda-intel driver to see the codec on my motherboard. > > alsa-info.sh captured details are at http://pastebin.ca/1021799 > > I have tried uninstalling and re-installing alsa using apt-get purge and > apt-get install > I have tried building and installing the packagae from realtek (but > that's only alsa-project's latest stable build any way I think) > I have downloaded built and installed the hot daily build from > alsa-project.org <http://alsa-project.org> and still no luck. > > Currently running 1.0.16 built on 20080516: > ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/alsa-driver-hg20080516.tar.bz2 > <ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/alsa-driver-hg20080516.tar.bz2> > > Additional info (Might already be in info capture) > > From demsg: > [ 40.254047] ALSA /build/buildd/linux-ubuntu > -modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: > hda-intel: no codecs found! > [ 40.254089] ACPI: PCI interrupt for device 0000:00:1b.0 disabled > > From lspci -v > 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio > Controller (rev 02) > Subsystem: Intel Corporation Unknown device 0013 > Flags: fast devsel, IRQ 23 > Memory at 922a0000 (64-bit, non-prefetchable) [size=16K] > Capabilities: [50] Power Management version 2 > Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ > Queue=0/0 Enable- > Capabilities: [70] Express Unknown type IRQ 0 > > I have also tried using varous MODEL= options to loading the module > (5stack, 3stack, acer) > I have not yet tried doing anything with the debug option because I > don't know how to use it. > > Any help appreciated. > Let me know if you need more information. > > Thanks, > Peter > > You seem to have covered the bases. Your OS is recognizing the card, but alsa isn't. Are you sure it is looking at the right cards directory? The official alsa one is in /usr/share/alsa but different distributions put the files in different places. It might still be looking at the old file. I'm not sure where that would be on Ubuntu, on redhat clones in /etc/alsa. There are a lot of problems with hda-intel (at least on this list), not because of the chip, but because everyone seems to use it differently. It is possible your configuration hasn't been implemented yet. You could ask on alsa-devel. |
|
From: Peter W. <al...@we...> - 2008-05-21 10:33:40
|
Stan, Thanks for the suggestions. I looked in /etc/alsa but there's only a file alsa-source.conf and I can't locate any other places where a card directory might be. /usr/share/alsa is where they all seem to be. Peter On Wed, May 21, 2008 at 4:27 AM, stan <ghj...@co...> wrote: > Peter Westley wrote: > >> First can I say if I should post this question somewhere else, please >> accept my apologies and let me know where! >> >> I am running ubuntu 8.04 on an Intel DQ35MP motherboard which has built-in >> ICH9 (ALC268 I believe) HD audio chipset. The kernel is 2.6.24-17-server >> >> When I first installed the desktop version of Ubuntu (acually it was 7.10) >> the audio worked. I'm not sure exactly at which point it stopped working but >> it might have been when I re-installed with -server version. >> >> I have trawled the web and tried many things but I just cannot get the >> hda-intel driver to see the codec on my motherboard. >> >> alsa-info.sh captured details are at http://pastebin.ca/1021799 >> >> I have tried uninstalling and re-installing alsa using apt-get purge and >> apt-get install >> I have tried building and installing the packagae from realtek (but that's >> only alsa-project's latest stable build any way I think) >> I have downloaded built and installed the hot daily build from >> alsa-project.org <http://alsa-project.org> and still no luck. >> >> Currently running 1.0.16 built on 20080516: >> ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/alsa-driver-hg20080516.tar.bz2< >> ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/alsa-driver-hg20080516.tar.bz2 >> > >> >> Additional info (Might already be in info capture) >> >> From demsg: >> [ 40.254047] ALSA /build/buildd/linux-ubuntu >> -modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: >> hda-intel: no codecs found! >> [ 40.254089] ACPI: PCI interrupt for device 0000:00:1b.0 disabled >> >> From lspci -v >> 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio >> Controller (rev 02) >> Subsystem: Intel Corporation Unknown device 0013 >> Flags: fast devsel, IRQ 23 >> Memory at 922a0000 (64-bit, non-prefetchable) [size=16K] >> Capabilities: [50] Power Management version 2 >> Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ >> Queue=0/0 Enable- >> Capabilities: [70] Express Unknown type IRQ 0 >> >> I have also tried using varous MODEL= options to loading the module >> (5stack, 3stack, acer) >> I have not yet tried doing anything with the debug option because I don't >> know how to use it. >> >> Any help appreciated. >> Let me know if you need more information. >> >> Thanks, >> Peter >> >> >> > You seem to have covered the bases. Your OS is recognizing the card, but > alsa isn't. Are you sure it is looking at the right cards directory? The > official alsa one is in /usr/share/alsa but different distributions put the > files in different places. It might still be looking at the old file. I'm > not sure where that would be on Ubuntu, on redhat clones in /etc/alsa. > > There are a lot of problems with hda-intel (at least on this list), not > because of the chip, but because everyone seems to use it differently. It > is possible your configuration hasn't been implemented yet. You could ask > on alsa-devel. > |
|
From: stan <ghj...@co...> - 2008-05-21 15:32:57
|
Peter Westley wrote: > Stan, > > Thanks for the suggestions. I looked in /etc/alsa but there's only a > file alsa-source.conf and I can't locate any other places where a card > directory might be. /usr/share/alsa is where they all seem to be. > > Peter > -modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: hda-intel: no codecs found! It was this line that made me think alsa wasn't finding the cards file or you had a codec that wasn't implemented yet. Given your response above, it seems the codec isn't implemented. I would ask on the alsa-devel list about your incarnation of hda-intel and motherboard and see if anyone can give you insight. |
|
From: Nigel H. <cav...@al...> - 2008-05-21 19:16:20
|
On Wednesday 21 May 2008 12:35, you wrote: > Update: > > I removed the DVB-T card from the system and rebooted - same problem. > System sees the card but the ALSA system doesn't recognise the codec > > <sigh> still looking. > > Peter Hi Peter. First of all it would be fair to say that there are horrible problems with hda intel based cards, as they are setup differently on the mobos of PC's/Laptops, depending on which machine you have. Laptops are the worst, as your only alternative if you can't get the onboard hda intel card to produce sounds, is to buy a USB, or pcmcia card. At least with a PC, and aspare PCI slot you can buy a cheap, known Alsa supported card, and get the sounds working. That said, you had sounds working when you had your Gutsy Gibbon installed, so at least you know the sounds worked with the hda intel card. You say that your not sure if the sounds stopped after installing the server version of Ubuntu GG, or after you'd installed HH 8.04. I spent a bit of time at the Ubuntu site looking at the server version, and the kernel. It did say the server kernel was somewhat different, but didn't say too much about the differences. I don't know if there is some specific reason that you need the server kernel, but if not it may be worth installing the generic one, and seeing if the sounds work ok with it. I'm a bit lost. Alsaconf is now deprecated, and no longer exists on GG. You used to be able to run that command as root, and it would search for soundcards, and if found set them up. I can't find anything on GG to reconfigure the soundcard. All that running "asoundconf list " (no double quotes)shows is soundcards that are already configured. There are a couple of things you could try to perhaps identify the problem. First open konsole/terminal, and enter the following text. sudo tail -f /var/log/messages This should capture any problems when running the following stuff. Now open another instance of konsole/terminal, and run the following command. sudo /etc/init.d/alsa-utils stop Followed by /etc/init.d/alsa-utils start Any messages on the konsole running tail -f? Also check out cat /proc/asound/cards, to see if any cards have appeared. if so we may be getting somewhere, but if not try the next suggestion, as below. Leaving the konsole running tail -f open, on the other konsole do. rmmod snd-hda-intel This may need to be run as. modprobe -r snd-hda-intel, if the rmmod command fails. Now run. modprobe snd-hda-intel Check again any output from the other konsole running tail -f, and also run. cat /proc/asound/cards, which may show detected cards. Whatever output you get on the konsole/terminal that is running tail -f /var/log/messages, please post it to myself, and to the alsa-user list. Personally, and if you have a spare PCI slot, I'd have a look on E-bay for an Audigy2 soundblaster card (emu10k1), which is the one I have. I think they can be picked up quite cheaply, and I know that this card works. Just a suggestion. Nigel. > > On Wed, May 21, 2008 at 7:38 PM, Peter Westley <al...@we...> wrote: > > Nigel, > > > > Thanks for the suggestions. > > > > I now have both : > > options snd-bt87x index=2 > > options cx88-alsa index=2 > > > > in the /etc/modprobe.d/alsa-base file but that hasn't helped. > > > > What is the difference between 2 and -2? Other modules have -2. > > > > I have tried these changes remotely but I will try removing the TV card > > altogether tonight and see if that makes any difference. At least if it > > does work I'll know that it's some sort of conflict. > > > > I don't roll my own kernel - I'm not that clever! > > > > Thanks again, > > Peter |
|
From: Peter W. <al...@we...> - 2008-05-22 22:27:30
|
Nigel, Thanks again for putting so much time into my problem! See comments inline. On Thu, May 22, 2008 at 5:15 AM, Nigel Henry <cav...@al...> wrote: > On Wednesday 21 May 2008 12:35, you wrote: > > Update: > > > > I removed the DVB-T card from the system and rebooted - same problem. > > System sees the card but the ALSA system doesn't recognise the codec > > > > <sigh> still looking. > > > > Peter > > Hi Peter. First of all it would be fair to say that there are horrible > problems with hda intel based cards, as they are setup differently on the > mobos of PC's/Laptops, depending on which machine you have. Laptops are the > worst, as your only alternative if you can't get the onboard hda intel card > to produce sounds, is to buy a USB, or pcmcia card. At least with a PC, and > aspare PCI slot you can buy a cheap, known Alsa supported card, and get the > sounds working. > > That said, you had sounds working when you had your Gutsy Gibbon installed, > so > at least you know the sounds worked with the hda intel card. > > You say that your not sure if the sounds stopped after installing the > server > version of Ubuntu GG, or after you'd installed HH 8.04. I spent a bit of > time > at the Ubuntu site looking at the server version, and the kernel. It did > say > the server kernel was somewhat different, but didn't say too much about the > differences. I don't know if there is some specific reason that you need > the > server kernel, but if not it may be worth installing the generic one, and > seeing if the sounds work ok with it. > > I'm a bit lost. Alsaconf is now deprecated, and no longer exists on GG. You > used to be able to run that command as root, and it would search for > soundcards, and if found set them up. I can't find anything on GG to > reconfigure the soundcard. All that running "asoundconf list " (no double > quotes)shows is soundcards that are already configured. > > There are a couple of things you could try to perhaps identify the problem. > > First open konsole/terminal, and enter the following text. > sudo tail -f /var/log/messages > This should capture any problems when running the following stuff. > > Now open another instance of konsole/terminal, and run the following > command. > sudo /etc/init.d/alsa-utils stop > Followed by /etc/init.d/alsa-utils start > Any messages on the konsole running tail -f? I get: $ sudo /etc/init.d/alsa-utils stop * Shutting down ALSA... * warning: 'alsactl store' failed with error message 'alsactl: save_state:1497: No soundcards found...'... [fail] Which is to be expected I guess... Then: $ sudo /etc/init.d/alsa-utils start * Setting up ALSA... [ OK ] and in /var/log/messgaes: May 22 23:04:38 snoopy kernel: [97942.954373] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23 May 22 23:04:39 snoopy kernel: [97943.034189] ACPI: PCI interrupt for device 0000:00:1b.0 disabled Which is similar to what goes in dmesg when the system boots: >From demsg: [ 40.254047] ALSA /build/buildd/linux-ubuntu -modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa -driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: hda-intel: no codecs found! [ 40.254089] ACPI: PCI interrupt for device 0000:00:1b.0 disabled > Also check out cat /proc/asound/cards, to see if any cards have appeared. > if > so we may be getting somewhere, but if not try the next suggestion, as > below. Nothing appeared Leaving the konsole running tail -f open, on the other konsole do. > rmmod snd-hda-intel > This may need to be run as. > modprobe -r snd-hda-intel, if the rmmod command fails. > > Now run. > modprobe snd-hda-intel > > Check again any output from the other konsole running tail -f, and also > run. > cat /proc/asound/cards, which may show detected cards. Nothing from those commands in /var/log/messages Whatever output you get on the konsole/terminal that is running tail > -f /var/log/messages, please post it to myself, and to the alsa-user list. > > Personally, and if you have a spare PCI slot, I'd have a look on E-bay for > an > Audigy2 soundblaster card (emu10k1), which is the one I have. I think they > can be picked up quite cheaply, and I know that this card works. Just a > suggestion. That's exactly what I would have done ages ago but sadly my stupid motherboard has only one PCI slot and that has the DVB-T card in it so sadly not an option. I will post to the alsa-dev group and see what they have to say. Peter > > Nigel. > > > > > On Wed, May 21, 2008 at 7:38 PM, Peter Westley <al...@we...> > wrote: > > > Nigel, > > > > > > Thanks for the suggestions. > > > > > > I now have both : > > > options snd-bt87x index=2 > > > options cx88-alsa index=2 > > > > > > in the /etc/modprobe.d/alsa-base file but that hasn't helped. > > > > > > What is the difference between 2 and -2? Other modules have -2. > > > > > > I have tried these changes remotely but I will try removing the TV card > > > altogether tonight and see if that makes any difference. At least if it > > > does work I'll know that it's some sort of conflict. > > > > > > I don't roll my own kernel - I'm not that clever! > > > > > > Thanks again, > > > Peter > |
|
From: Nigel H. <cav...@al...> - 2008-05-22 23:01:44
|
On Friday 23 May 2008 00:27, Peter Westley wrote: > Nigel, > > Thanks again for putting so much time into my problem! See comments inline. > > On Thu, May 22, 2008 at 5:15 AM, Nigel Henry <cav...@al...> > > wrote: > > On Wednesday 21 May 2008 12:35, you wrote: > > > Update: > > > > > > I removed the DVB-T card from the system and rebooted - same problem. > > > System sees the card but the ALSA system doesn't recognise the codec > > > > > > <sigh> still looking. > > > > > > Peter > > > > Hi Peter. First of all it would be fair to say that there are horrible > > problems with hda intel based cards, as they are setup differently on the > > mobos of PC's/Laptops, depending on which machine you have. Laptops are > > the worst, as your only alternative if you can't get the onboard hda > > intel card to produce sounds, is to buy a USB, or pcmcia card. At least > > with a PC, and aspare PCI slot you can buy a cheap, known Alsa supported > > card, and get the sounds working. > > > > That said, you had sounds working when you had your Gutsy Gibbon > > installed, so > > at least you know the sounds worked with the hda intel card. > > > > You say that your not sure if the sounds stopped after installing the > > server > > version of Ubuntu GG, or after you'd installed HH 8.04. I spent a bit of > > time > > at the Ubuntu site looking at the server version, and the kernel. It did > > say > > the server kernel was somewhat different, but didn't say too much about > > the differences. I don't know if there is some specific reason that you > > need the > > server kernel, but if not it may be worth installing the generic one, and > > seeing if the sounds work ok with it. > > > > I'm a bit lost. Alsaconf is now deprecated, and no longer exists on GG. > > You used to be able to run that command as root, and it would search for > > soundcards, and if found set them up. I can't find anything on GG to > > reconfigure the soundcard. All that running "asoundconf list " (no double > > quotes)shows is soundcards that are already configured. > > > > There are a couple of things you could try to perhaps identify the > > problem. > > > > First open konsole/terminal, and enter the following text. > > sudo tail -f /var/log/messages > > This should capture any problems when running the following stuff. > > > > Now open another instance of konsole/terminal, and run the following > > command. > > sudo /etc/init.d/alsa-utils stop > > Followed by /etc/init.d/alsa-utils start > > Any messages on the konsole running tail -f? > > I get: > $ sudo /etc/init.d/alsa-utils stop > * Shutting down > ALSA... * warning: > 'alsactl store' failed with error message 'alsactl: save_state:1497: No > soundcards found...'... [fail] > > Which is to be expected I guess... > > Then: > $ sudo /etc/init.d/alsa-utils start > * Setting up ALSA... [ > OK ] > > and in /var/log/messgaes: > May 22 23:04:38 snoopy kernel: [97942.954373] ACPI: PCI Interrupt > 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23 > May 22 23:04:39 snoopy kernel: [97943.034189] ACPI: PCI interrupt for > device 0000:00:1b.0 disabled > > Which is similar to what goes in dmesg when the system boots: > >From demsg: > > [ 40.254047] ALSA /build/buildd/linux-ubuntu > -modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa > -driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: > hda-intel: no codecs found! > [ 40.254089] ACPI: PCI interrupt for device 0000:00:1b.0 disabled > > > Also check out cat /proc/asound/cards, to see if any cards have appeared. > > if > > so we may be getting somewhere, but if not try the next suggestion, as > > below. > > Nothing appeared > > Leaving the konsole running tail -f open, on the other konsole do. > > > rmmod snd-hda-intel > > This may need to be run as. > > modprobe -r snd-hda-intel, if the rmmod command fails. > > > > Now run. > > modprobe snd-hda-intel > > > > Check again any output from the other konsole running tail -f, and also > > run. > > cat /proc/asound/cards, which may show detected cards. > > Nothing from those commands in /var/log/messages > > Whatever output you get on the konsole/terminal that is running tail > > > -f /var/log/messages, please post it to myself, and to the alsa-user > > list. > > > > Personally, and if you have a spare PCI slot, I'd have a look on E-bay > > for an > > Audigy2 soundblaster card (emu10k1), which is the one I have. I think > > they can be picked up quite cheaply, and I know that this card works. > > Just a suggestion. > > That's exactly what I would have done ages ago but sadly my stupid > motherboard has only one PCI slot and that has the DVB-T card in it so > sadly not an option. > > I will post to the alsa-dev group and see what they have to say. > > Peter Hi Peter. Sorry none of my suggestions produced any positive results. As regards your mobo with only one PCI slot. That has to be quite pathetic. You used to be able to get mobo's with 5 PCI slots, and I've been hunting for a new atx mobo, to put in a case that I've had for some time. I have found an atx one with 3 PCI slots, and a couple pf PCI express ones, and am waiting for it to arrive (Asus M2N-X Plus). Not too expensive 52.50 euros. It too may have a dodgy onboard soundcard. It will be interesting to see if the sound works when it arrives. Yes, do post to the alsa-development list. I hope someone there can help you to get the sounds back up and running. Nigel. |
|
From: Peter W. <al...@we...> - 2008-05-23 01:24:17
|
On Fri, May 23, 2008 at 9:01 AM, Nigel Henry <cav...@al...> wrote: > On Friday 23 May 2008 00:27, Peter Westley wrote: > > Nigel, > > > > Thanks again for putting so much time into my problem! See comments > inline. > > > > On Thu, May 22, 2008 at 5:15 AM, Nigel Henry < > cav...@al...> > > > > wrote: > > > On Wednesday 21 May 2008 12:35, you wrote: > > > > Update: > > > > > > > > I removed the DVB-T card from the system and rebooted - same problem. > > > > System sees the card but the ALSA system doesn't recognise the codec > > > > > > > > <sigh> still looking. > > > > > > > > Peter > > > > > > Hi Peter. First of all it would be fair to say that there are horrible > > > problems with hda intel based cards, as they are setup differently on > the > > > mobos of PC's/Laptops, depending on which machine you have. Laptops are > > > the worst, as your only alternative if you can't get the onboard hda > > > intel card to produce sounds, is to buy a USB, or pcmcia card. At least > > > with a PC, and aspare PCI slot you can buy a cheap, known Alsa > supported > > > card, and get the sounds working. > > > > > > That said, you had sounds working when you had your Gutsy Gibbon > > > installed, so > > > at least you know the sounds worked with the hda intel card. > > > > > > You say that your not sure if the sounds stopped after installing the > > > server > > > version of Ubuntu GG, or after you'd installed HH 8.04. I spent a bit > of > > > time > > > at the Ubuntu site looking at the server version, and the kernel. It > did > > > say > > > the server kernel was somewhat different, but didn't say too much about > > > the differences. I don't know if there is some specific reason that you > > > need the > > > server kernel, but if not it may be worth installing the generic one, > and > > > seeing if the sounds work ok with it. > > > > > > I'm a bit lost. Alsaconf is now deprecated, and no longer exists on GG. > > > You used to be able to run that command as root, and it would search > for > > > soundcards, and if found set them up. I can't find anything on GG to > > > reconfigure the soundcard. All that running "asoundconf list " (no > double > > > quotes)shows is soundcards that are already configured. > > > > > > There are a couple of things you could try to perhaps identify the > > > problem. > > > > > > First open konsole/terminal, and enter the following text. > > > sudo tail -f /var/log/messages > > > This should capture any problems when running the following stuff. > > > > > > Now open another instance of konsole/terminal, and run the following > > > command. > > > sudo /etc/init.d/alsa-utils stop > > > Followed by /etc/init.d/alsa-utils start > > > Any messages on the konsole running tail -f? > > > > I get: > > $ sudo /etc/init.d/alsa-utils stop > > * Shutting down > > ALSA... * > warning: > > 'alsactl store' failed with error message 'alsactl: save_state:1497: No > > soundcards found...'... > [fail] > > > > Which is to be expected I guess... > > > > Then: > > $ sudo /etc/init.d/alsa-utils start > > * Setting up ALSA... > [ > > OK ] > > > > and in /var/log/messgaes: > > May 22 23:04:38 snoopy kernel: [97942.954373] ACPI: PCI Interrupt > > 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23 > > May 22 23:04:39 snoopy kernel: [97943.034189] ACPI: PCI interrupt for > > device 0000:00:1b.0 disabled > > > > Which is similar to what goes in dmesg when the system boots: > > >From demsg: > > > > [ 40.254047] ALSA /build/buildd/linux-ubuntu > > -modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa > > -driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: > > hda-intel: no codecs found! > > [ 40.254089] ACPI: PCI interrupt for device 0000:00:1b.0 disabled > > > > > Also check out cat /proc/asound/cards, to see if any cards have > appeared. > > > if > > > so we may be getting somewhere, but if not try the next suggestion, as > > > below. > > > > Nothing appeared > > > > Leaving the konsole running tail -f open, on the other konsole do. > > > > > rmmod snd-hda-intel > > > This may need to be run as. > > > modprobe -r snd-hda-intel, if the rmmod command fails. > > > > > > Now run. > > > modprobe snd-hda-intel > > > > > > Check again any output from the other konsole running tail -f, and also > > > run. > > > cat /proc/asound/cards, which may show detected cards. > > > > Nothing from those commands in /var/log/messages > > > > Whatever output you get on the konsole/terminal that is running tail > > > > > -f /var/log/messages, please post it to myself, and to the alsa-user > > > list. > > > > > > Personally, and if you have a spare PCI slot, I'd have a look on E-bay > > > for an > > > Audigy2 soundblaster card (emu10k1), which is the one I have. I think > > > they can be picked up quite cheaply, and I know that this card works. > > > Just a suggestion. > > > > That's exactly what I would have done ages ago but sadly my stupid > > motherboard has only one PCI slot and that has the DVB-T card in it so > > sadly not an option. > > > > I will post to the alsa-dev group and see what they have to say. > > > > Peter > > Hi Peter. Sorry none of my suggestions produced any positive results. > > As regards your mobo with only one PCI slot. That has to be quite pathetic. > You used to be able to get mobo's with 5 PCI slots, and I've been hunting > for > a new atx mobo, to put in a case that I've had for some time. I have found > an > atx one with 3 PCI slots, and a couple pf PCI express ones, and am waiting > for it to arrive (Asus M2N-X Plus). Not too expensive 52.50 euros. It too > may > have a dodgy onboard soundcard. It will be interesting to see if the sound > works when it arrives. > > Yes, do post to the alsa-development list. I hope someone there can help > you > to get the sounds back up and running. > > Nigel. > > Nigel, The mobo was was my own stupid fault - I bought it in a hurry and didn't research properly! It does have two PCIe slots but there's precious little in PCIe that Linux seems to support at all yet. I will probably go the mobo replacement path eventually (then my 15yo son can have this one - he's been bugging me for one for ages!) I am going to try one more thing and that is to install a fresh Ubuntu desktop onto an external drive and just check that the sound comes up there... Peter |
|
From: Tobin D. <td...@ds...> - 2008-05-23 17:05:17
|
Before you go off and get rid of your board, there are a number of things to look at first. According to an earlier post, it looked as though the audio may have been disabled in bios. Another possibility is that it worked before because the driver didn't even know about the codec (let alone the board). When I looked at the tip source, the only motherboard that matched the subdevice id for your system was a 945 (ICH7/Sigmatel 9221). Based on that, and the the way my board currently works (DP35DP - very similar), I am starting to think that it may be a problem with Ubuntu's alsa drivers (wouldn't be a first time, believe me). First thing to try, as suggested elsewhere, try removing your tuner card temporarily. If audio comes up, then we have found the conflict. If not, try "acpi=off". Lastly, you can try downloading a daily snapshot from ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/ and building it with "./configure --with-cards=hda-intel --with-debug=detect". Once you build and install it, type "lsmod|fgrep snd|awk '{print $1}'|xargs rmmod" to remove all sound modules, type "dmesg -c" to clear the dmesg log, then "modprobe snd_hda_intel" to load the new modules. If you still don't get audio, type dmesg to see the latest output and email that info here. Tobin On Fri, 2008-05-23 at 11:24 +1000, Peter Westley wrote: > > > On Fri, May 23, 2008 at 9:01 AM, Nigel Henry > <cav...@al...> wrote: > > > On Friday 23 May 2008 00:27, Peter Westley wrote: > > Nigel, > > > > Thanks again for putting so much time into my problem! See > comments inline. > > > > On Thu, May 22, 2008 at 5:15 AM, Nigel Henry > <cav...@al...> > > > > wrote: > > > On Wednesday 21 May 2008 12:35, you wrote: > > > > Update: > > > > > > > > I removed the DVB-T card from the system and rebooted - > same problem. > > > > System sees the card but the ALSA system doesn't > recognise the codec > > > > > > > > <sigh> still looking. > > > > > > > > Peter > > > > > > Hi Peter. First of all it would be fair to say that there > are horrible > > > problems with hda intel based cards, as they are setup > differently on the > > > mobos of PC's/Laptops, depending on which machine you > have. Laptops are > > > the worst, as your only alternative if you can't get the > onboard hda > > > intel card to produce sounds, is to buy a USB, or pcmcia > card. At least > > > with a PC, and aspare PCI slot you can buy a cheap, known > Alsa supported > > > card, and get the sounds working. > > > > > > That said, you had sounds working when you had your Gutsy > Gibbon > > > installed, so > > > at least you know the sounds worked with the hda intel > card. > > > > > > You say that your not sure if the sounds stopped after > installing the > > > server > > > version of Ubuntu GG, or after you'd installed HH 8.04. I > spent a bit of > > > time > > > at the Ubuntu site looking at the server version, and the > kernel. It did > > > say > > > the server kernel was somewhat different, but didn't say > too much about > > > the differences. I don't know if there is some specific > reason that you > > > need the > > > server kernel, but if not it may be worth installing the > generic one, and > > > seeing if the sounds work ok with it. > > > > > > I'm a bit lost. Alsaconf is now deprecated, and no longer > exists on GG. > > > You used to be able to run that command as root, and it > would search for > > > soundcards, and if found set them up. I can't find > anything on GG to > > > reconfigure the soundcard. All that running "asoundconf > list " (no double > > > quotes)shows is soundcards that are already configured. > > > > > > There are a couple of things you could try to perhaps > identify the > > > problem. > > > > > > First open konsole/terminal, and enter the following text. > > > sudo tail -f /var/log/messages > > > This should capture any problems when running the > following stuff. > > > > > > Now open another instance of konsole/terminal, and run the > following > > > command. > > > sudo /etc/init.d/alsa-utils stop > > > Followed by /etc/init.d/alsa-utils start > > > Any messages on the konsole running tail -f? > > > > I get: > > $ sudo /etc/init.d/alsa-utils stop > > * Shutting down > > ALSA... > * warning: > > 'alsactl store' failed with error message 'alsactl: > save_state:1497: No > > soundcards found...'... > [fail] > > > > Which is to be expected I guess... > > > > Then: > > $ sudo /etc/init.d/alsa-utils start > > * Setting up ALSA... > [ > > OK ] > > > > and in /var/log/messgaes: > > May 22 23:04:38 snoopy kernel: [97942.954373] ACPI: PCI > Interrupt > > 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23 > > May 22 23:04:39 snoopy kernel: [97943.034189] ACPI: PCI > interrupt for > > device 0000:00:1b.0 disabled > > > > Which is similar to what goes in dmesg when the system > boots: > > >From demsg: > > > > [ 40.254047] ALSA /build/buildd/linux-ubuntu > > -modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa > > -driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: > > hda-intel: no codecs found! > > [ 40.254089] ACPI: PCI interrupt for device 0000:00:1b.0 > disabled > > > > > Also check out cat /proc/asound/cards, to see if any cards > have appeared. > > > if > > > so we may be getting somewhere, but if not try the next > suggestion, as > > > below. > > > > Nothing appeared > > > > Leaving the konsole running tail -f open, on the other > konsole do. > > > > > rmmod snd-hda-intel > > > This may need to be run as. > > > modprobe -r snd-hda-intel, if the rmmod command fails. > > > > > > Now run. > > > modprobe snd-hda-intel > > > > > > Check again any output from the other konsole running tail > -f, and also > > > run. > > > cat /proc/asound/cards, which may show detected cards. > > > > Nothing from those commands in /var/log/messages > > > > Whatever output you get on the konsole/terminal that is > running tail > > > > > -f /var/log/messages, please post it to myself, and to the > alsa-user > > > list. > > > > > > Personally, and if you have a spare PCI slot, I'd have a > look on E-bay > > > for an > > > Audigy2 soundblaster card (emu10k1), which is the one I > have. I think > > > they can be picked up quite cheaply, and I know that this > card works. > > > Just a suggestion. > > > > That's exactly what I would have done ages ago but sadly my > stupid > > motherboard has only one PCI slot and that has the DVB-T > card in it so > > sadly not an option. > > > > I will post to the alsa-dev group and see what they have to > say. > > > > Peter > > > > Hi Peter. Sorry none of my suggestions produced any positive > results. > > As regards your mobo with only one PCI slot. That has to be > quite pathetic. > You used to be able to get mobo's with 5 PCI slots, and I've > been hunting for > a new atx mobo, to put in a case that I've had for some time. > I have found an > atx one with 3 PCI slots, and a couple pf PCI express ones, > and am waiting > for it to arrive (Asus M2N-X Plus). Not too expensive 52.50 > euros. It too may > have a dodgy onboard soundcard. It will be interesting to see > if the sound > works when it arrives. > > Yes, do post to the alsa-development list. I hope someone > there can help you > to get the sounds back up and running. > > Nigel. > > > > Nigel, > > The mobo was was my own stupid fault - I bought it in a hurry and > didn't research properly! It does have two PCIe slots but there's > precious little in PCIe that Linux seems to support at all yet. > > I will probably go the mobo replacement path eventually (then my 15yo > son can have this one - he's been bugging me for one for ages!) > > I am going to try one more thing and that is to install a fresh Ubuntu > desktop onto an external drive and just check that the sound comes up > there... > > Peter > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ Alsa-user mailing list Als...@li... https://lists.sourceforge.net/lists/listinfo/alsa-user |
|
From: Peter W. <al...@we...> - 2008-05-25 04:18:03
|
Tobin, On Sat, May 24, 2008 at 3:05 AM, Tobin Davis <td...@ds...> wrote: > Before you go off and get rid of your board, there are a number of things > to look at first. According to an earlier post, it looked as though the > audio may have been disabled in bios. > Checked that - all OK. Another possibility is that it worked before because the driver didn't > even know about the codec (let alone the board). When I looked at the tip > source, the only motherboard that matched the subdevice id for your system > was a 945 (ICH7/Sigmatel 9221). Based on that, and the the way my board > currently works (DP35DP - very similar), I am starting to think that it may > be a problem with Ubuntu's alsa drivers (wouldn't be a first time, believe > me). > I've tried building an Ubuntu 8.04 from scratch but that doesn't work. I'll also try it with the 7.10 desktop I think I originally had it working with. Haven't done that yet so can't report on it... standby for an update on that. > First thing to try, as suggested elsewhere, try removing your tuner card > temporarily. If audio comes up, then we have found the conflict. > Yes did that, same result. If not, try "acpi=off". > Also this, no luck > Lastly, you can try downloading a daily snapshot from > ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/ and building it with > "./configure --with-cards=hda-intel --with-debug=detect". Once you build > and install it, type "lsmod|fgrep snd|awk '{print $1}'|xargs rmmod" to > remove all sound modules, type "dmesg -c" to clear the dmesg log, then > "modprobe snd_hda_intel" to load the new modules. If you still don't get > audio, type dmesg to see the latest output and email that info here. > OK built 20080524 from the above site (actually from ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/ because there's a 'README' there that says it's moved...) Used: ./configure --with-cards=hda-intel --with-debug=detect make sudo make install Then removed all the 'snd' modules with rmmod (couldn't use your above command - it required reverse dependency removal of the modules so I just did it manually - anyone written a script or is there an option to rmmod that ignores dependencies?) and finally dmesg -c modprobe snd-hda-intel No go. Log contents folow ************************* dmesg: [14834.424775] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23 [14834.424799] PCI: Setting latency timer of device 0000:00:1b.0 to 64 [14834.495425] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: hda-intel: no codecs found! [14834.495477] ACPI: PCI interrupt for device 0000:00:1b.0 disabled ************************* tail /var/log/messages : May 25 13:59:40 snoopy kernel: [14834.424775] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23 May 25 13:59:40 snoopy kernel: [14834.495477] ACPI: PCI interrupt for device 0000:00:1b.0 disabled Also tail /var/log/syslog is a little more telling (maybe!): May 25 13:57:49 snoopy NetworkManager: <debug> [1211687869.615123] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/computer_oss_sequencer_0'). May 25 13:57:49 snoopy NetworkManager: <debug> [1211687869.618245] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/computer_oss_sequencer'). May 25 13:58:36 snoopy NetworkManager: <debug> [1211687916.647991] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/computer_alsa_sequencer'). May 25 13:58:50 snoopy NetworkManager: <debug> [1211687930.303908] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/computer_alsa_timer'). May 25 13:59:40 snoopy NetworkManager: <debug> [1211687980.458993] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/computer_alsa_timer'). May 25 13:59:40 snoopy NetworkManager: <debug> [1211687980.470466] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/computer_alsa_sequencer'). May 25 13:59:40 snoopy kernel: [14834.424775] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23 May 25 13:59:40 snoopy kernel: [14834.424799] PCI: Setting latency timer of device 0000:00:1b.0 to 64 May 25 13:59:40 snoopy NetworkManager: <debug> [1211687980.486231] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/computer_oss_sequencer'). May 25 13:59:40 snoopy NetworkManager: <debug> [1211687980.495521] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/computer_oss_sequencer_0'). May 25 13:59:40 snoopy kernel: [14834.495425] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: hda-intel: no codecs found! May 25 13:59:40 snoopy kernel: [14834.495477] ACPI: PCI interrupt for device 0000:00:1b.0 disabled Curious to know why the hal is getting involved... So that's where we are... Peter > > > Tobin > > > On Fri, 2008-05-23 at 11:24 +1000, Peter Westley wrote: > > > On Fri, May 23, 2008 at 9:01 AM, Nigel Henry <cav...@al...> > wrote: > > > On Friday 23 May 2008 00:27, Peter Westley wrote: > > Nigel, > > > > Thanks again for putting so much time into my problem! See comments > inline. > > > > On Thu, May 22, 2008 at 5:15 AM, Nigel Henry < > cav...@al...> > > > > wrote: > > > On Wednesday 21 May 2008 12:35, you wrote: > > > > Update: > > > > > > > > I removed the DVB-T card from the system and rebooted - same problem. > > > > System sees the card but the ALSA system doesn't recognise the codec > > > > > > > > <sigh> still looking. > > > > > > > > Peter > > > > > > Hi Peter. First of all it would be fair to say that there are horrible > > > problems with hda intel based cards, as they are setup differently on > the > > > mobos of PC's/Laptops, depending on which machine you have. Laptops are > > > the worst, as your only alternative if you can't get the onboard hda > > > intel card to produce sounds, is to buy a USB, or pcmcia card. At least > > > with a PC, and aspare PCI slot you can buy a cheap, known Alsa > supported > > > card, and get the sounds working. > > > > > > That said, you had sounds working when you had your Gutsy Gibbon > > > installed, so > > > at least you know the sounds worked with the hda intel card. > > > > > > You say that your not sure if the sounds stopped after installing the > > > server > > > version of Ubuntu GG, or after you'd installed HH 8.04. I spent a bit > of > > > time > > > at the Ubuntu site looking at the server version, and the kernel. It > did > > > say > > > the server kernel was somewhat different, but didn't say too much about > > > the differences. I don't know if there is some specific reason that you > > > need the > > > server kernel, but if not it may be worth installing the generic one, > and > > > seeing if the sounds work ok with it. > > > > > > I'm a bit lost. Alsaconf is now deprecated, and no longer exists on GG. > > > You used to be able to run that command as root, and it would search > for > > > soundcards, and if found set them up. I can't find anything on GG to > > > reconfigure the soundcard. All that running "asoundconf list " (no > double > > > quotes)shows is soundcards that are already configured. > > > > > > There are a couple of things you could try to perhaps identify the > > > problem. > > > > > > First open konsole/terminal, and enter the following text. > > > sudo tail -f /var/log/messages > > > This should capture any problems when running the following stuff. > > > > > > Now open another instance of konsole/terminal, and run the following > > > command. > > > sudo /etc/init.d/alsa-utils stop > > > Followed by /etc/init.d/alsa-utils start > > > Any messages on the konsole running tail -f? > > > > I get: > > $ sudo /etc/init.d/alsa-utils stop > > * Shutting down > > ALSA... * > warning: > > 'alsactl store' failed with error message 'alsactl: save_state:1497: No > > soundcards found...'... > [fail] > > > > Which is to be expected I guess... > > > > Then: > > $ sudo /etc/init.d/alsa-utils start > > * Setting up ALSA... > [ > > OK ] > > > > and in /var/log/messgaes: > > May 22 23:04:38 snoopy kernel: [97942.954373] ACPI: PCI Interrupt > > 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23 > > May 22 23:04:39 snoopy kernel: [97943.034189] ACPI: PCI interrupt for > > device 0000:00:1b.0 disabled > > > > Which is similar to what goes in dmesg when the system boots: > > >From demsg: > > > > [ 40.254047] ALSA /build/buildd/linux-ubuntu > > -modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa > > -driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: > > hda-intel: no codecs found! > > [ 40.254089] ACPI: PCI interrupt for device 0000:00:1b.0 disabled > > > > > Also check out cat /proc/asound/cards, to see if any cards have > appeared. > > > if > > > so we may be getting somewhere, but if not try the next suggestion, as > > > below. > > > > Nothing appeared > > > > Leaving the konsole running tail -f open, on the other konsole do. > > > > > rmmod snd-hda-intel > > > This may need to be run as. > > > modprobe -r snd-hda-intel, if the rmmod command fails. > > > > > > Now run. > > > modprobe snd-hda-intel > > > > > > Check again any output from the other konsole running tail -f, and also > > > run. > > > cat /proc/asound/cards, which may show detected cards. > > > > Nothing from those commands in /var/log/messages > > > > Whatever output you get on the konsole/terminal that is running tail > > > > > -f /var/log/messages, please post it to myself, and to the alsa-user > > > list. > > > > > > Personally, and if you have a spare PCI slot, I'd have a look on E-bay > > > for an > > > Audigy2 soundblaster card (emu10k1), which is the one I have. I think > > > they can be picked up quite cheaply, and I know that this card works. > > > Just a suggestion. > > > > That's exactly what I would have done ages ago but sadly my stupid > > motherboard has only one PCI slot and that has the DVB-T card in it so > > sadly not an option. > > > > I will post to the alsa-dev group and see what they have to say. > > > > Peter > > > Hi Peter. Sorry none of my suggestions produced any positive results. > > As regards your mobo with only one PCI slot. That has to be quite pathetic. > You used to be able to get mobo's with 5 PCI slots, and I've been hunting > for > a new atx mobo, to put in a case that I've had for some time. I have found > an > atx one with 3 PCI slots, and a couple pf PCI express ones, and am waiting > for it to arrive (Asus M2N-X Plus). Not too expensive 52.50 euros. It too > may > have a dodgy onboard soundcard. It will be interesting to see if the sound > works when it arrives. > > Yes, do post to the alsa-development list. I hope someone there can help > you > to get the sounds back up and running. > > Nigel. > > > Nigel, > > The mobo was was my own stupid fault - I bought it in a hurry and didn't > research properly! It does have two PCIe slots but there's precious little > in PCIe that Linux seems to support at all yet. > > I will probably go the mobo replacement path eventually (then my 15yo son > can have this one - he's been bugging me for one for ages!) > > I am going to try one more thing and that is to install a fresh Ubuntu > desktop onto an external drive and just check that the sound comes up > there... > > Peter > > -------------------------------------------------------------------------This SF.net email is sponsored by: MicrosoftDefy all challenges. Microsoft(R) Visual Studio 2008.http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________ Alsa-user mailing list Als...@li... https://lists.sourceforge.net/lists/listinfo/alsa-user > > > |
|
From: Sergei S. <ste...@li...> - 2008-05-23 08:26:01
|
On Fri, 23 May 2008 11:24:23 +1000 "Peter Westley" <al...@we...> wrote: > Nigel, > > The mobo was was my own stupid fault - I bought it in a hurry and didn't > research properly! It does have two PCIe slots but there's precious little > in PCIe that Linux seems to support at all yet. > > I will probably go the mobo replacement path eventually (then my 15yo son > can have this one - he's been bugging me for one for ages!) FWIW, there are still motherboards with 4 PCI slots, but the motherboards are for AMD (AM2 socket), not Intel. The maker is Gigabyte. Regards, Sergei. |
|
From: Peter W. <al...@we...> - 2008-05-23 11:50:00
|
Sergei, Thanks for that pointer - I'm not married to either AMD or Intel so I might take a look - thanks! Peter On Fri, May 23, 2008 at 6:24 PM, Sergei Steshenko <ste...@li...> wrote: > On Fri, 23 May 2008 11:24:23 +1000 > "Peter Westley" <al...@we...> wrote: > > > > Nigel, > > > > The mobo was was my own stupid fault - I bought it in a hurry and didn't > > research properly! It does have two PCIe slots but there's precious > little > > in PCIe that Linux seems to support at all yet. > > > > I will probably go the mobo replacement path eventually (then my 15yo son > > can have this one - he's been bugging me for one for ages!) > > FWIW, there are still motherboards with 4 PCI slots, but the motherboards > are > for AMD (AM2 socket), not Intel. > > The maker is Gigabyte. > > Regards, > Sergei. > |
|
From: Sergei S. <ste...@li...> - 2008-05-23 14:34:46
|
On Fri, 23 May 2008 21:50:05 +1000 "Peter Westley" <al...@we...> wrote: > Sergei, > > Thanks for that pointer - I'm not married to either AMD or Intel so I might > take a look - thanks! > > Peter > > On Fri, May 23, 2008 at 6:24 PM, Sergei Steshenko <ste...@li...> > wrote: > > > On Fri, 23 May 2008 11:24:23 +1000 > > "Peter Westley" <al...@we...> wrote: > > > > > > > Nigel, > > > > > > The mobo was was my own stupid fault - I bought it in a hurry and didn't > > > research properly! It does have two PCIe slots but there's precious > > little > > > in PCIe that Linux seems to support at all yet. > > > > > > I will probably go the mobo replacement path eventually (then my 15yo son > > > can have this one - he's been bugging me for one for ages!) > > > > FWIW, there are still motherboards with 4 PCI slots, but the motherboards > > are > > for AMD (AM2 socket), not Intel. > > > > The maker is Gigabyte. > > > > Regards, > > Sergei. > > I have such a MB - it's ALC883-based (the MB is no more in production), and the sound works - at least, as stereo. I think the newer ones are also ALC883-based. Regards, Sergei. |
|
From: Nigel H. <cav...@al...> - 2008-05-23 15:41:23
|
On Friday 23 May 2008 16:34, Sergei Steshenko wrote: > On Fri, 23 May 2008 21:50:05 +1000 > > "Peter Westley" <al...@we...> wrote: > > Sergei, > > > > Thanks for that pointer - I'm not married to either AMD or Intel so I > > might take a look - thanks! > > > > Peter > > > > On Fri, May 23, 2008 at 6:24 PM, Sergei Steshenko > > <ste...@li...> > > > > wrote: > > > On Fri, 23 May 2008 11:24:23 +1000 > > > > > > "Peter Westley" <al...@we...> wrote: > > > > Nigel, > > > > > > > > The mobo was was my own stupid fault - I bought it in a hurry and > > > > didn't research properly! It does have two PCIe slots but there's > > > > precious > > > > > > little > > > > > > > in PCIe that Linux seems to support at all yet. > > > > > > > > I will probably go the mobo replacement path eventually (then my 15yo > > > > son can have this one - he's been bugging me for one for ages!) > > > > > > FWIW, there are still motherboards with 4 PCI slots, but the > > > motherboards are > > > for AMD (AM2 socket), not Intel. > > > > > > The maker is Gigabyte. > > > > > > Regards, > > > Sergei. > > I have such a MB - it's ALC883-based (the MB is no more in production), and > the sound works - at least, as stereo. > > I think the newer ones are also ALC883-based. > > Regards, > Sergei. Regarding something else Peter could try, that I saw on the list today, was appending the Grub kernel line, at boot up, and add acpi=off. That appears to have got someones sound working with an hda intel card. I must admit that I'm clutching at straws in the help I'm offering, but it may be worth a try. Although saying that, he had sounds working with this card, when he had the earlier version of Ubuntu (Gutsy Gibbon) installed, and admittadly this was the desktop version. He then installed the server version of Gutsy Gibbon, but can't remember if he had sounds after that. I could find very little about the differences between the server kernel, and the generic one on the Ubuntu site. He next installed the latest server version Of Ubuntu (Hardy Heron), which has no sound, and that is where we stand at the moment. It has to be said that hda intel cards present a whole can of worms, that the user has to try and deal with to try and get sounds working. The Alsa devs are doing there best patching, and patching this card with so many variations, but at times you sort of think that this is a losing battle. According to the mobo I'm waiting to receive (Asus M2N-X Plus), it has HDA sound (ALC662), which is likely to be a bundle of fun compared to my Audigy2 soundblaster (emu10k1) on one machine, and Ensoniq (ens1371) on the other machine. At least the mobo has 3 PCI slots, so I can pick up a cheap, well supported soundcard, so that if the El Crapo hda intel doesn't work, at least I'll have sounds. Sorry. I think I've ranted on enough. Nigel. |
|
From: Sergei S. <ste...@li...> - 2008-05-23 15:53:11
|
On Fri, 23 May 2008 17:41:10 +0200 Nigel Henry <cav...@al...> wrote: > The Alsa devs > are doing there best patching, and patching this card with so many > variations, but at times you sort of think that this is a losing battle. > It is - some reverse engineering using Windows and/or Macs needs to be done. I mean, rather some automated reverse engineering - maybe it is possible to extract connectivity info from Windows and/or Mac driver. As I wrote many times, an ndiswrapper-like solution would be nice to have too. Regards, Sergei. |
|
From: stan <ghj...@co...> - 2008-05-25 23:39:40
|
Peter Westley wrote: > Tobin, > > On Sat, May 24, 2008 at 3:05 AM, Tobin Davis <td...@ds... > <mailto:td...@ds...>> wrote: > > Before you go off and get rid of your board, there are a number of > things to look at first. According to an earlier post, it looked > as though the audio may have been disabled in bios. > > > Checked that - all OK. > > Another possibility is that it worked before because the driver > didn't even know about the codec (let alone the board). When I > looked at the tip source, the only motherboard that matched the > subdevice id for your system was a 945 (ICH7/Sigmatel 9221). > Based on that, and the the way my board currently works (DP35DP - > very similar), I am starting to think that it may be a problem > with Ubuntu's alsa drivers (wouldn't be a first time, believe me). > > > I've tried building an Ubuntu 8.04 from scratch but that doesn't > work. I'll also try it with the 7.10 desktop I think I originally had > it working with. Haven't done that yet so can't report on it... > standby for an update on that. > > > First thing to try, as suggested elsewhere, try removing your > tuner card temporarily. If audio comes up, then we have found the > conflict. > > > Yes did that, same result. > > If not, try "acpi=off". > > > Also this, no luck > > > Lastly, you can try downloading a daily snapshot from > ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/ and building > it with "./configure --with-cards=hda-intel --with-debug=detect". > Once you build and install it, type "lsmod|fgrep snd|awk '{print > $1}'|xargs rmmod" to remove all sound modules, type "dmesg -c" to > clear the dmesg log, then "modprobe snd_hda_intel" to load the new > modules. If you still don't get audio, type dmesg to see the > latest output and email that info here. > > > OK built 20080524 from the above site (actually from > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/ because > there's a 'README' there that says it's moved...) > > Used: > ./configure --with-cards=hda-intel --with-debug=detect > make > sudo make install > > Then removed all the 'snd' modules with rmmod (couldn't use your above > command - it required reverse dependency removal of the modules so I > just did it manually - anyone written a script or is there an option > to rmmod that ignores dependencies?) > > and finally > > dmesg -c > modprobe snd-hda-intel > > No go. > [snip] > Curious to know why the hal is getting involved... > So that's where we are... > Peter You might want to look at the thread "ICH8 HDA not detected after upgrade from Ubuntu 7.10 to 8.04". He has the identical problem and his dmesg clearly shows that the probe of the soundcard is failing. |
|
From: Peter W. <al...@we...> - 2008-05-25 23:56:31
|
On Mon, May 26, 2008 at 9:39 AM, stan <ghj...@co...> wrote: > Peter Westley wrote: > >> Tobin, >> >> >> On Sat, May 24, 2008 at 3:05 AM, Tobin Davis <td...@ds...<mailto: >> td...@ds...>> wrote: >> >> Before you go off and get rid of your board, there are a number of >> things to look at first. According to an earlier post, it looked >> as though the audio may have been disabled in bios. >> >> >> Checked that - all OK. >> >> Another possibility is that it worked before because the driver >> didn't even know about the codec (let alone the board). When I >> looked at the tip source, the only motherboard that matched the >> subdevice id for your system was a 945 (ICH7/Sigmatel 9221). Based >> on that, and the the way my board currently works (DP35DP - >> very similar), I am starting to think that it may be a problem >> with Ubuntu's alsa drivers (wouldn't be a first time, believe me). >> >> >> I've tried building an Ubuntu 8.04 from scratch but that doesn't work. >> I'll also try it with the 7.10 desktop I think I originally had it working >> with. Haven't done that yet so can't report on it... standby for an update >> on that. >> >> First thing to try, as suggested elsewhere, try removing your >> tuner card temporarily. If audio comes up, then we have found the >> conflict. >> >> Yes did that, same result. >> >> If not, try "acpi=off". >> >> Also this, no luck >> >> Lastly, you can try downloading a daily snapshot from >> ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/ and building >> it with "./configure --with-cards=hda-intel --with-debug=detect". >> Once you build and install it, type "lsmod|fgrep snd|awk '{print >> $1}'|xargs rmmod" to remove all sound modules, type "dmesg -c" to >> clear the dmesg log, then "modprobe snd_hda_intel" to load the new >> modules. If you still don't get audio, type dmesg to see the >> latest output and email that info here. >> >> OK built 20080524 from the above site (actually from >> ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/ because >> there's a 'README' there that says it's moved...) >> >> Used: >> ./configure --with-cards=hda-intel --with-debug=detect >> make >> sudo make install >> >> Then removed all the 'snd' modules with rmmod (couldn't use your above >> command - it required reverse dependency removal of the modules so I just >> did it manually - anyone written a script or is there an option to rmmod >> that ignores dependencies?) >> >> and finally >> >> dmesg -c >> modprobe snd-hda-intel >> >> No go. >> >> [snip] > >> Curious to know why the hal is getting involved... >> So that's where we are... >> Peter >> > You might want to look at the thread "ICH8 HDA not detected after upgrade > from Ubuntu 7.10 to 8.04". He has the identical problem and his dmesg > clearly shows that the probe of the soundcard is failing. > > Stan, Thanks, yes I saw that and wondered the same thing. In fact his problem is a little different - in his dmesg log, he gets: 1. [ 42.872651] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21 2. [ 42.872657] PCI: Unable to reserve mem region #1:4000@febf8000 for device 0000:00:1b.0 3. [ 42.872661] ACPI: PCI interrupt for device 0000:00:1b.0 disabled 4. [ 42.872668] HDA Intel: probe of 0000:00:1b.0 failed with error -16 compared to mine: 1. [ 40.254047] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892:hda-intel: no codecs found! 2. [ 40.254089] ACPI: PCI interrupt for device 0000:00:1b.0 disabled So in his case there's what looks like a conflict, rather than in mine, just the codec is not detected. The end result is the same. I did try installing a fresh 7.10 and 7.04 Ubuntu and now I'm beginning to doubt my recollection that the sound ever worked - it didn't on either of those installs.... Peter |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X