[Lugstuff] Lugstuff Digest, Vol 18, Issue 8
Tanenhaus Michael
mtanen at mavenspire.com
Thu Jan 21 13:27:45 EST 2010
Doesnt that version of OpenSUSE use PulseAudio and not alsa?
>>>
From: <lugstuff-request at annapolislinux.org>
To:<lugstuff at annapolislinux.org>
Date: 1/21/2010 12:00 PM
Subject: Lugstuff Digest, Vol 18, Issue 8
Send Lugstuff mailing list submissions to
lugstuff at annapolislinux.org
To subscribe or unsubscribe via the World Wide Web, visit
http://list.annapolislinux.org/cgi-bin/mailman/listinfo/lugstuff
or, via email, send a message with subject or body 'help' to
lugstuff-request at annapolislinux.org
You can reach the person managing the list at
lugstuff-owner at annapolislinux.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Lugstuff digest..."
Today's Topics:
1. Sound issues (Aaron Nye)
2. Re: Sound issues (Thomas Gallen)
3. Thank you for your responses - still seeking a solution
(David F Bleil)
4. Re: Thank you for your responses - still seeking asolution
(Thomas Gallen)
5. Re: It only gets more interesting -read confusing. (Theodore Knab)
----------------------------------------------------------------------
Message: 1
Date: Wed, 20 Jan 2010 13:25:56 -0500
From: Aaron Nye <aaron.nye at gmail.com>
Subject: [Lugstuff] Sound issues
To: lugstuff at annapolislinux.org
Message-ID:
<eb90d3ee1001201025p4b51a06ene3771e5773adbe3f at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi... FNG here.
I've had a sound issue since kernel 2.6.24 (in Ubuntu and Slackware).
My main system uses an Intel HDA, and since updating past .24, Pulse
will run away for no discernible reason, sometimes when no sound app
is running. I know when it does with a quick glance at the system
monitor. One of my cores will be maxed out. A quick kill -9 fixes
it, but it is a pain. I have it down to about twice a day now by
fiddling with driver settings, but I wonder what the team did to these
most recent kernels that caused it.
I missed the beginning of this thread, but I'll go back and see if I
maybe able to offer any insight (though, it isn't likely).
<--snip-->
>
> I have never attempted to ?install just a kernel other than by means of the distro installer on the dvd and I am reluctant to attempt to do so for fear that I might end with an unbootable system. What I would really would like to understand ?is how the kernel modulse interact with the kernel and how the module could be modified to pass the proper parameters to the kernel so that it would load and function. When I use Yast to set up the sound driver I get a message that the kernel could not load the sound module because something in the module is incorrect.
>
> Knoppix recognizes and uses the sound chip automatically so I know it can be done. I have reinstalled the alsa tool kit and alsa files. Yast no longer claims that they are not found but instead that the module can not be loaded by the kernel. What information does the sound module have to pass to the kernel for it to be loaded and how can that be modified?
>
<--snip-->
> On Monday 18 January 2010 09:52:44 am Theodore Knab wrote:
>> I would try reinstalling the kernel first.
>
> running ? uname -r ? ?I get 2.6.27.42-0.1-pae
> I used to have ? ? ? ? ? ? ? ? 2.6.27.42-0.1-default
>
> I presume that the kernel I have now is an updated (patched) one. How would I
> make sure that I am installing the correct kernel? I think the "default"
> kernel is the one which came on the installation dvd.
>
--
Aaron Nye
aaron.nye at gmail.com
http://theakkadian.com
m. 443-791-9580
f. 443-308-0124
-----------------------------
"There are two kinds of people, those who want to be left alone and
those who won't leave them alone."
-- Doreen Hannes
------------------------------
Message: 2
Date: Wed, 20 Jan 2010 13:46:08 -0500
From: Thomas Gallen <kaori.hinata at gmail.com>
Subject: Re: [Lugstuff] Sound issues
To: Aaron Nye <aaron.nye at gmail.com>
Cc: lugstuff at annapolislinux.org
Message-ID: <D2C074B1-A809-4804-89E5-AF2AB0A9F559 at gmail.com>
Content-Type: text/plain; charset=us-ascii
Hiya,
There have been a few bugs submitted to the bug trackers for Ubuntu and Fedora that sound like the issue you're describing (I've included them below). By any chance would you be able to check the output of the "dmesg" command or the last few lines of the file "/var/log/messages" the next time pulseaudio dies and post the results here to the mailing list if you find anything talking about pulseaudio? You'll find some examples of what the messages might look like at the links below.
https://bugzilla.redhat.com/show_bug.cgi?id=485734
https://bugs.launchpad.net/ubuntu/+source/linux-rt/+bug/481619
Thanks,
Thomas
On Jan 20, 2010, at 1:25 PM, Aaron Nye wrote:
> Hi... FNG here.
>
> I've had a sound issue since kernel 2.6.24 (in Ubuntu and Slackware).
> My main system uses an Intel HDA, and since updating past .24, Pulse
> will run away for no discernible reason, sometimes when no sound app
> is running. I know when it does with a quick glance at the system
> monitor. One of my cores will be maxed out. A quick kill -9 fixes
> it, but it is a pain. I have it down to about twice a day now by
> fiddling with driver settings, but I wonder what the team did to these
> most recent kernels that caused it.
>
> I missed the beginning of this thread, but I'll go back and see if I
> maybe able to offer any insight (though, it isn't likely).
>
> <--snip-->
>>
>> I have never attempted to install just a kernel other than by means of the distro installer on the dvd and I am reluctant to attempt to do so for fear that I might end with an unbootable system. What I would really would like to understand is how the kernel modulse interact with the kernel and how the module could be modified to pass the proper parameters to the kernel so that it would load and function. When I use Yast to set up the sound driver I get a message that the kernel could not load the sound module because something in the module is incorrect.
>>
>> Knoppix recognizes and uses the sound chip automatically so I know it can be done. I have reinstalled the alsa tool kit and alsa files. Yast no longer claims that they are not found but instead that the module can not be loaded by the kernel. What information does the sound module have to pass to the kernel for it to be loaded and how can that be modified?
>>
>
> <--snip-->
>
>> On Monday 18 January 2010 09:52:44 am Theodore Knab wrote:
>>> I would try reinstalling the kernel first.
>>
>> running uname -r I get 2.6.27.42-0.1-pae
>> I used to have 2.6.27.42-0.1-default
>>
>> I presume that the kernel I have now is an updated (patched) one. How would I
>> make sure that I am installing the correct kernel? I think the "default"
>> kernel is the one which came on the installation dvd.
>>
>
> --
> Aaron Nye
> aaron.nye at gmail.com
> http://theakkadian.com
> m. 443-791-9580
> f. 443-308-0124
>
> -----------------------------
>
> "There are two kinds of people, those who want to be left alone and
> those who won't leave them alone."
>
> -- Doreen Hannes
> _______________________________________________
> Lugstuff mailing list
> Lugstuff at annapolislinux.org
> http://list.annapolislinux.org/cgi-bin/mailman/listinfo/lugstuff
------------------------------
Message: 3
Date: Wed, 20 Jan 2010 16:02:11 -0500
From: David F Bleil <dfbleil at toad.net>
Subject: [Lugstuff] Thank you for your responses - still seeking a
solution
To: lugstuff at annapolislinux.org
Message-ID: <201001201602.11582.dfbleil at toad.net>
Content-Type: text/plain; charset="us-ascii"
Background of problem-
OS = open Suse 11.1 Kernel 2.6.27.42-0.1-pae Kernel sound driver
snd_via82xx
Hardware Info reports Model VIA VT8233/A/8235/8237 AC97 Audio controller
IO Port Active:yes Length: 256 Mode:rw Start:56320
IRQ Count 8941 Enabled:yes IRQ: 22
Subvender ASRock incorporated
Attempting to configure the sound with Yast2 the error message is "The kernel
module snd_via82xx could not be loaded. This can be caused by incorrect
module parameters, including invalid IO or IRQ parameters."
Sound was working perfectly on this hardware with this driver under open
Suse10.3. Sound still works perfectly when Knoppix (kernel 2.6.19 ) is
booted.
What I have done-
I have attempted to run alsaconfig without success.
I have attempted to look for information in /bin/dmesg using vim but the
output is not readable to me.
I have downloaded and installed the most recent alsa-driver-1.0.xx from
www.alsa-project.org. This may have been a mistake. It did not fix anything.
I would like to find out how to 1. identify the proper IO and IRQ parameters
for this sound chip and 2 modify the sound module so that the proper
parameters are used.
--
David F. Bleil
Catboat sailor from Crofton
SUSE Linux 11.1
This penguin can fly!
------------------------------
Message: 4
Date: Wed, 20 Jan 2010 16:10:16 -0500
From: Thomas Gallen <kaori.hinata at gmail.com>
Subject: Re: [Lugstuff] Thank you for your responses - still seeking a
solution
To: David F Bleil <dfbleil at toad.net>
Cc: lugstuff at annapolislinux.org
Message-ID: <94BF3823-1C19-49C9-8CD7-2A579AB861DD at gmail.com>
Content-Type: text/plain; charset=us-ascii
Ahh, sorry about the confusion. /bin/dmesg is a program not a log file. To run it, you type "dmesg" (without the quotes) in a terminal window and press enter. If your distribution prevents normal users from running the dmesg program then you will have to type "sudo dmesg" (without the quotes) then input your password when asked (the one you use to log in to your computer) in order to run it.
Another option you have if you want to find out what's going on is to try to load the module then use "sudo less /var/log/messages" to look at the system log for messages regarding the loading of your sound card module. Once the file loads, use page down to go to the bottom of this file (the newest entries are at the bottom). If you find anything that looks like an error, go ahead an post it to the list. You can then quit "less" by pressing the "q" key.
Hope that helps clear that up,
Thomas
On Jan 20, 2010, at 4:02 PM, David F Bleil wrote:
> Background of problem-
>
> OS = open Suse 11.1 Kernel 2.6.27.42-0.1-pae Kernel sound driver
> snd_via82xx
> Hardware Info reports Model VIA VT8233/A/8235/8237 AC97 Audio controller
> IO Port Active:yes Length: 256 Mode:rw Start:56320
> IRQ Count 8941 Enabled:yes IRQ: 22
> Subvender ASRock incorporated
>
> Attempting to configure the sound with Yast2 the error message is "The kernel
> module snd_via82xx could not be loaded. This can be caused by incorrect
> module parameters, including invalid IO or IRQ parameters."
>
> Sound was working perfectly on this hardware with this driver under open
> Suse10.3. Sound still works perfectly when Knoppix (kernel 2.6.19 ) is
> booted.
>
> What I have done-
> I have attempted to run alsaconfig without success.
>
> I have attempted to look for information in /bin/dmesg using vim but the
> output is not readable to me.
>
> I have downloaded and installed the most recent alsa-driver-1.0.xx from
> www.alsa-project.org. This may have been a mistake. It did not fix anything.
>
> I would like to find out how to 1. identify the proper IO and IRQ parameters
> for this sound chip and 2 modify the sound module so that the proper
> parameters are used.
>
> --
>
> David F. Bleil
> Catboat sailor from Crofton
>
> SUSE Linux 11.1
> This penguin can fly!
> _______________________________________________
> Lugstuff mailing list
> Lugstuff at annapolislinux.org
> http://list.annapolislinux.org/cgi-bin/mailman/listinfo/lugstuff
------------------------------
Message: 5
Date: Wed, 20 Jan 2010 21:44:32 -0500
From: Theodore Knab <tjk at annapolislinux.org>
Subject: Re: [Lugstuff] It only gets more interesting -read confusing.
To: David F Bleil <dfbleil at toad.net>
Cc: lugstuff at annapolislinux.org
Message-ID: <20100121024432.GA15401 at annapolislinux.org>
Content-Type: text/plain; charset=us-ascii
If SUSE is using grub as a boot loader, you should be able to load the
old kernel if it exists.
Here are the commands:
1.
cd /boot/grub/
Look at the menu1st file.
2.
less menu.lst
Verify the Kernels in the list if there are more than one are on the
hard drive. They should be in /boot unless SUSE calls them something
else.
After verifying that you have the kernel on the list, you can change the 'default' paramater to a
different number. For example, my menu.1st reads:
## default num
# Set the default entry to the entry number NUM. Numbering starts from
# 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default
# entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved'
# or your
# array will desync and will not let you boot your system.
default 0
This should get your sound back.
Once you modify the /boot/grub/menu.1st file restart and the new kernel
should come up.
If it does not, throw in a Knoppix CD and change the file back to the
way it was. Then reboot.
On 19/01/10 20:05 -0500, David F Bleil wrote:
> On Monday 18 January 2010 09:52:44 am Theodore Knab wrote:
> > I would try reinstalling the kernel first.
>
> running uname -r I get 2.6.27.42-0.1-pae
> I used to have 2.6.27.42-0.1-default
>
> I presume that the kernel I have now is an updated (patched) one. How would I
> make sure that I am installing the correct kernel? I think the "default"
> kernel is the one which came on the installation dvd.
>
> --
>
> David F. Bleil
> Catboat sailor from Crofton
>
> SUSE Linux 11.1
> This penguin can fly!
> _______________________________________________
> Lugstuff mailing list
> Lugstuff at annapolislinux.org
> http://list.annapolislinux.org/cgi-bin/mailman/listinfo/lugstuff
--
Ted Knab
Stevensville, MD USA
------------------------------
_______________________________________________
Lugstuff mailing list
Lugstuff at annapolislinux.org
http://list.annapolislinux.org/cgi-bin/mailman/listinfo/lugstuff
End of Lugstuff Digest, Vol 18, Issue 8
***************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://annapolislinux.org/pipermail/lugstuff/attachments/20100121/feda7dea/attachment.html>
More information about the Lugstuff
mailing list