From tjk at annapolislinux.org Fri Jan 1 09:58:49 2010 From: tjk at annapolislinux.org (Theodore Knab) Date: Fri, 1 Jan 2010 09:58:49 -0500 Subject: [Lugstuff] Next Meeting: Jan 4 2010 7PM Message-ID: <20100101145848.GA25163@annapolislinux.org> Happy new year. The next LUG meeting is January 4th 2010 at 7PM. Directions to the meeting can be found here: http://annapolislinux.org/?page_id=23 -- Ted Knab Stevensville, MD USA From dfbleil at toad.net Mon Jan 11 10:29:00 2010 From: dfbleil at toad.net (David F Bleil) Date: Mon, 11 Jan 2010 10:29:00 -0500 Subject: [Lugstuff] Need a local source for SCSI-2 cable for external scanner. Message-ID: <201001111029.00884.dfbleil@toad.net> I am setting up a Linux system for a friend and the box has an Adapteck SCSI card to connect to a Microtec-3 scanner. This scanner origionally used an Apple SCSI card in the system which just died. The end on the existing cable does not connect to the SCSI-2 connector on the new box. I am looking for places where I can buy a replacement cable with the correct ends, preferably locally in the Annapolis area. Failing that, I would like recomendations for a reliable, not overly expensive source to order from. -- David F. Bleil Catboat sailor from Crofton SUSE Linux 11.1 This penguin can fly! From bgraw3 at mac.com Mon Jan 11 11:37:31 2010 From: bgraw3 at mac.com (Bob Graw III) Date: Mon, 11 Jan 2010 11:37:31 -0500 Subject: [Lugstuff] Need a local source for SCSI-2 cable for external scanner. In-Reply-To: <201001111029.00884.dfbleil@toad.net> References: <201001111029.00884.dfbleil@toad.net> Message-ID: <5F3EC936-C654-4EB5-8F14-DC69BA31DF7A@mac.com> i cannot remember the last time i hooked up an external device. i used to use scsi all the time for hard drives, tape drives, cd-roms, scanners, etc. i probably have a cable in a box in my basement. but, there are so many combinations. is the scanner a big, old centronics type? or, is it a smaller scsi-2? there are 50-pin, 68-pin, etc. then there were really small, high density configurations, too. if the cable was attached to an apple, it probably had a 25-pin that's the same as a parallel cable. the question is what connector do you have on the PC side and what connector is on the scanner side? you can use the following to identify what kinds of connectors you need: http://www.pcguide.com/ref/hdd/if/scsi/cables.htm i've ordered lots of cables from the following company. they don't seem to have as many scsi cables as the used to, though... http://www.cyberguys.com/product-listings/?categoryid=145 bob graw 410-703-3455 On Jan 11, 2010, at 10:29 AM, David F Bleil wrote: > I am setting up a Linux system for a friend and the box has an > Adapteck SCSI > card to connect to a Microtec-3 scanner. This scanner origionally > used an > Apple SCSI card in the system which just died. The end on the > existing cable > does not connect to the SCSI-2 connector on the new box. I am > looking for > places where I can buy a replacement cable with the correct ends, > preferably > locally in the Annapolis area. Failing that, I would like > recomendations for > a reliable, not overly expensive source to order from. > > -- > > 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 From tjk at annapolislinux.org Thu Jan 14 07:41:06 2010 From: tjk at annapolislinux.org (Theodore Knab) Date: Thu, 14 Jan 2010 07:41:06 -0500 Subject: [Lugstuff] myth tv box: low power with RAID 1 Message-ID: <20100114124105.GA1556@annapolislinux.org> Hi, I started the path of making a MythTV box for home. I was wondering if anyone could make any recommendations for both a low power machines and low power consuming hard drives. I am looking for something that will only consume 100W or less and holds 1 terrabyte or more of data in a RAID 1. It also needs to have one slot to hold my TV card. So, far I have only purchased this Linux only TV card: http://www.mythtv.org/wiki/PcHDTV_HD-5500 -- Ted Knab Stevensville, MD USA From kaori.hinata at gmail.com Thu Jan 14 09:19:30 2010 From: kaori.hinata at gmail.com (Thomas Gallen) Date: Thu, 14 Jan 2010 09:19:30 -0500 Subject: [Lugstuff] myth tv box: low power with RAID 1 In-Reply-To: <20100114124105.GA1556@annapolislinux.org> References: <20100114124105.GA1556@annapolislinux.org> Message-ID: <079E4437-06D1-4ED4-B2E5-517CE37FF229@gmail.com> I think one of the various Intel Atom (perhaps an ION as well) based motherboards along with a few Western Digital Caviar Green drives would fit that bill nicely. I've been wanting to built such a system as well. I believe there are also some good cases available that will fit exactly two drives and use very little space otherwise. You'd have to check motherboard compatibility though. Check: http://www.mini-itx.com/store/?c=2 (for motherboards) You can check some Tom's Hardware reviews and specs for the Caviar Green power usage. Unfortunately I don't have those links on hand (at work). Thomas On Jan 14, 2010, at 7:41 AM, Theodore Knab wrote: > Hi, > > I started the path of making a MythTV box for home. > > I was wondering if anyone could make any recommendations for both a low power > machines and low power consuming hard drives. > > I am looking for something that will only consume 100W > or less and holds 1 terrabyte or more of data in a RAID 1. > It also needs to have one slot to hold my TV card. > > So, far I have only purchased this Linux only TV card: > http://www.mythtv.org/wiki/PcHDTV_HD-5500 > > -- > Ted Knab > Stevensville, MD USA > > _______________________________________________ > Lugstuff mailing list > Lugstuff at annapolislinux.org > http://list.annapolislinux.org/cgi-bin/mailman/listinfo/lugstuff From dfbleil at toad.net Fri Jan 15 08:15:10 2010 From: dfbleil at toad.net (David F Bleil) Date: Fri, 15 Jan 2010 08:15:10 -0500 Subject: [Lugstuff] sound driver conundrum Message-ID: <201001150815.10874.dfbleil@toad.net> Sound was working fine in Open Suse 10.3. Sound chip is an onboard AC97 audio controller and the kernel driver is snd_via82xx Upgrading to Suse 11.1 killed the sound. Attempting to configure the sound is Yast produces the error message that the kernel can not load the module because of incorrect parameters. Running alsaconfig as root does not change this. Knoppix finds and uses the sound chip so the issue is with Suse 11.1. Questions are - How do I find and set the parameters so that the kernel will load the Suse sound module? or How do I find what sound driver the Knoppix is using and make that driver available to suse? -- David F. Bleil Catboat sailor from Crofton SUSE Linux 11.1 This penguin can fly! From tjk at annapolislinux.org Fri Jan 15 08:47:37 2010 From: tjk at annapolislinux.org (Theodore Knab) Date: Fri, 15 Jan 2010 08:47:37 -0500 Subject: [Lugstuff] sound driver conundrum In-Reply-To: <201001150815.10874.dfbleil@toad.net> References: <201001150815.10874.dfbleil@toad.net> Message-ID: <20100115134736.GA20166@annapolislinux.org> The AC97 chip is pretty generic. Maybe your kernel got upgraded but the kernel modules did not get rebuilt. Can you load the old kernel and see if does the same thing ? You should be able to run this as root to see if something is missing: + /sbin/depmod -a Depmod will 'generate module dependancies and map files' according to man page. This command will prope all the modules. If there are errors they will get displayed. On 15/01/10 08:15 -0500, David F Bleil wrote: > Sound was working fine in Open Suse 10.3. Sound chip is an onboard AC97 audio > controller and the kernel driver is snd_via82xx > > Upgrading to Suse 11.1 killed the sound. Attempting to configure the sound is > Yast produces the error message that the kernel can not load the module > because of incorrect parameters. > > Running alsaconfig as root does not change this. > > Knoppix finds and uses the sound chip so the issue is with Suse 11.1. > > Questions are - How do I find and set the parameters so that the kernel will > load the Suse sound module? > or > How do I find what sound driver the Knoppix is using and make that driver > available to suse? > > -- > > 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 From dfbleil at toad.net Fri Jan 15 20:50:27 2010 From: dfbleil at toad.net (David F Bleil) Date: Fri, 15 Jan 2010 20:50:27 -0500 Subject: [Lugstuff] sound driver conundrum In-Reply-To: <20100115134736.GA20166@annapolislinux.org> References: <201001150815.10874.dfbleil@toad.net> <20100115134736.GA20166@annapolislinux.org> Message-ID: <201001152050.27869.dfbleil@toad.net> On Friday 15 January 2010 08:47:37 am Theodore Knab wrote: > You should be able to run this as root to see if something is missing: > + /sbin/depmod -a Is the "+" part of the command? Running the command without the + there is a pause and nothing is returned to stdout. Is the output directed to stderror? running the command /sbin.lspci | grep -i audio produces the message " no modules" If the sound module has indeed been totally clobbered is there a way to put it back -- short of doing a clean install? I guess this weekend is total data backup time. -- David F. Bleil Catboat sailor from Crofton SUSE Linux 11.1 This penguin can fly! From tjk at annapolislinux.org Mon Jan 18 09:52:44 2010 From: tjk at annapolislinux.org (Theodore Knab) Date: Mon, 18 Jan 2010 09:52:44 -0500 Subject: [Lugstuff] sound driver conundrum In-Reply-To: <201001152050.27869.dfbleil@toad.net> References: <201001150815.10874.dfbleil@toad.net> <20100115134736.GA20166@annapolislinux.org> <201001152050.27869.dfbleil@toad.net> Message-ID: <20100118145241.GA9934@annapolislinux.org> The '+' is not part of the command. You might be able to reinstall the kernel after you get things backed up and get sound to work. I would try reinstalling the kernel first. On 15/01/10 20:50 -0500, David F Bleil wrote: > On Friday 15 January 2010 08:47:37 am Theodore Knab wrote: > > You should be able to run this as root to see if something is missing: > > + /sbin/depmod -a > > Is the "+" part of the command? Running the command without the + there is a > pause and nothing is returned to stdout. Is the output directed to stderror? > > running the command /sbin.lspci | grep -i audio produces the message " no > modules" > > If the sound module has indeed been totally clobbered is there a way to put it > back -- short of doing a clean install? I guess this weekend is total data > backup time. > > -- > > 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 From dfbleil at toad.net Tue Jan 19 18:56:08 2010 From: dfbleil at toad.net (David F Bleil) Date: Tue, 19 Jan 2010 18:56:08 -0500 Subject: [Lugstuff] sound driver conundrum In-Reply-To: <20100118145241.GA9934@annapolislinux.org> References: <201001150815.10874.dfbleil@toad.net> <201001152050.27869.dfbleil@toad.net> <20100118145241.GA9934@annapolislinux.org> Message-ID: <201001191856.08306.dfbleil@toad.net> On Monday 18 January 2010 09:52:44 am Theodore Knab wrote: > You might be able to reinstall the kernel after you get things backed up > and get sound to work. I would try reinstalling the kernel first. 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? -- David F. Bleil Catboat sailor from Crofton SUSE Linux 11.1 This penguin can fly! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.annapolislinux.org/pipermail/lugstuff/attachments/20100119/f6a01e98/attachment.html From dfbleil at toad.net Tue Jan 19 20:05:52 2010 From: dfbleil at toad.net (David F Bleil) Date: Tue, 19 Jan 2010 20:05:52 -0500 Subject: [Lugstuff] It only gets more interesting -read confusing. In-Reply-To: <20100118145241.GA9934@annapolislinux.org> References: <201001150815.10874.dfbleil@toad.net> <201001152050.27869.dfbleil@toad.net> <20100118145241.GA9934@annapolislinux.org> Message-ID: <201001192005.52698.dfbleil@toad.net> 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! From aaron.nye at gmail.com Wed Jan 20 13:25:56 2010 From: aaron.nye at gmail.com (Aaron Nye) Date: Wed, 20 Jan 2010 13:25:56 -0500 Subject: [Lugstuff] Sound issues Message-ID: 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 From kaori.hinata at gmail.com Wed Jan 20 13:46:08 2010 From: kaori.hinata at gmail.com (Thomas Gallen) Date: Wed, 20 Jan 2010 13:46:08 -0500 Subject: [Lugstuff] Sound issues In-Reply-To: References: Message-ID: 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 From dfbleil at toad.net Wed Jan 20 16:02:11 2010 From: dfbleil at toad.net (David F Bleil) Date: Wed, 20 Jan 2010 16:02:11 -0500 Subject: [Lugstuff] Thank you for your responses - still seeking a solution Message-ID: <201001201602.11582.dfbleil@toad.net> 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! From kaori.hinata at gmail.com Wed Jan 20 16:10:16 2010 From: kaori.hinata at gmail.com (Thomas Gallen) Date: Wed, 20 Jan 2010 16:10:16 -0500 Subject: [Lugstuff] Thank you for your responses - still seeking a solution In-Reply-To: <201001201602.11582.dfbleil@toad.net> References: <201001201602.11582.dfbleil@toad.net> Message-ID: <94BF3823-1C19-49C9-8CD7-2A579AB861DD@gmail.com> 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 From tjk at annapolislinux.org Wed Jan 20 21:44:32 2010 From: tjk at annapolislinux.org (Theodore Knab) Date: Wed, 20 Jan 2010 21:44:32 -0500 Subject: [Lugstuff] It only gets more interesting -read confusing. In-Reply-To: <201001192005.52698.dfbleil@toad.net> References: <201001150815.10874.dfbleil@toad.net> <201001152050.27869.dfbleil@toad.net> <20100118145241.GA9934@annapolislinux.org> <201001192005.52698.dfbleil@toad.net> Message-ID: <20100121024432.GA15401@annapolislinux.org> 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 From mtanen at mavenspire.com Thu Jan 21 13:27:45 2010 From: mtanen at mavenspire.com (Tanenhaus Michael) Date: Thu, 21 Jan 2010 13:27:45 -0500 Subject: [Lugstuff] Lugstuff Digest, Vol 18, Issue 8 In-Reply-To: References: Message-ID: <4B5856510200004A0009293A@mail.mavenspire.net> Doesnt that version of OpenSUSE use PulseAudio and not alsa? >>> From: To: 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 Subject: [Lugstuff] Sound issues To: lugstuff at annapolislinux.org Message-ID: 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 Subject: Re: [Lugstuff] Sound issues To: Aaron Nye Cc: lugstuff at annapolislinux.org Message-ID: 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 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 Subject: Re: [Lugstuff] Thank you for your responses - still seeking a solution To: David F Bleil 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 Subject: Re: [Lugstuff] It only gets more interesting -read confusing. To: David F Bleil 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://list.annapolislinux.org/pipermail/lugstuff/attachments/20100121/feda7dea/attachment.htm From jtanen at mavenspire.com Thu Jan 21 17:04:07 2010 From: jtanen at mavenspire.com (Tanenhaus Jessica) Date: Thu, 21 Jan 2010 17:04:07 -0500 Subject: [Lugstuff] Lugstuff Digest, Vol 18, Issue 8 In-Reply-To: <4B5856510200004A0009293A@mail.mavenspire.net> References: <4B5856510200004A0009293A@mail.mavenspire.net> Message-ID: <4B588907020000410000F9C4@mail.mavenspire.net> It does, and I had several nightmares with sound before disabling PulseAudio altogether. The problems described don't sound quite like what was happening to me (although I have tried to repress the memories, so maybe I'm just remembering incorrectly) but it may be worth a shot to go through and get rid of PulseAudio to see if that fixes the problem. Or go through and reinstall it, but I will state that several reinstalls never fixed the PA problems for me. >>> On 1/21/2010 at 01:27 PM, in message <4B5856510200004A0009293A at mail.mavenspire.net>, "Tanenhaus Michael" wrote: Doesnt that version of OpenSUSE use PulseAudio and not alsa? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.annapolislinux.org/pipermail/lugstuff/attachments/20100121/fd2e0642/attachment.htm From kaori.hinata at gmail.com Thu Jan 21 14:21:49 2010 From: kaori.hinata at gmail.com (Thomas Gallen) Date: Thu, 21 Jan 2010 14:21:49 -0500 Subject: [Lugstuff] Lugstuff Digest, Vol 18, Issue 8 In-Reply-To: <4B5856510200004A0009293A@mail.mavenspire.net> References: <4B5856510200004A0009293A@mail.mavenspire.net> Message-ID: What do you mean "use PulseAudio and not alsa"? PulseAudio takes input natively from applications that support PulseAudio or using an alsa plugin which redirects audio from applications that only support alsa output to PulseAudio then outputs to an alsa device. In the normal use case that I believe we have below, it's not possible to use PulseAudio and not alsa. Though, if you meant to say "use PulseAudio and not alsa directly", I admit I still don't understand whose issue you are referring to (David or Aaron's)? Could you elaborate? Thanks, Thomas (P.S. Please correct me if I'm wrong.) On Jan 21, 2010, at 1:27 PM, Tanenhaus Michael wrote: > Doesnt that version of OpenSUSE use PulseAudio and not alsa? > > > >>> > From: > To: > 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 > Subject: [Lugstuff] Sound issues > To: lugstuff at annapolislinux.org > Message-ID: > > 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 > Subject: Re: [Lugstuff] Sound issues > To: Aaron Nye > Cc: lugstuff at annapolislinux.org > Message-ID: > 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 > 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 > Subject: Re: [Lugstuff] Thank you for your responses - still seeking a > solution > To: David F Bleil > 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 > Subject: Re: [Lugstuff] It only gets more interesting -read confusing. > To: David F Bleil > 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 > *************************************** > _______________________________________________ > Lugstuff mailing list > Lugstuff at annapolislinux.org > http://list.annapolislinux.org/cgi-bin/mailman/listinfo/lugstuff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.annapolislinux.org/pipermail/lugstuff/attachments/20100121/b133300d/attachment-0001.htm From dfbleil at toad.net Sat Jan 23 20:58:59 2010 From: dfbleil at toad.net (David F Bleil) Date: Sat, 23 Jan 2010 20:58:59 -0500 Subject: [Lugstuff] Thank you all! There is sound! Message-ID: <201001232059.06638.dfbleil@toad.net> Thank you to all who made suggestions and comments. The key seems to have been the understanding that PulseAudio and ALSA talk to each other, or at least supposed to.?? ?After fumbling around with the driver I got from the chip manufacturer site I got to an error I could understand. ?The compiler was complaining about a field called CFLAGS, and said the source should be changed to EXTRA_CFLAGS. ?I googled that and found an entry explaining that someone had installed the 1.0.19 version of the driver and it fixed everything with a link to the ALSA site. ?I went there and got their latest source along with all the related utilities and libraries for 1.0.22! ??Finally, everything worked, no more error message about snd-via82xx. Once again Linux has proved to be a learning experience whether I wanted it or not. However there is help when needed and that is what makes this a community. David Bleil Catboat Sailor from Crofton Suse Linux 11.1 This penguin can fly! From kaori.hinata at gmail.com Sat Jan 23 21:23:26 2010 From: kaori.hinata at gmail.com (Thomas Gallen) Date: Sat, 23 Jan 2010 21:23:26 -0500 Subject: [Lugstuff] Thank you all! There is sound! Message-ID: <20100124022325.GD3435@localhost.lan.merumeru.mobi> Glad to hear it. Having a vague idea of how each gear fits into one big machine always helps out when error messages do not and in the case of Linux, the gears of this big machine have labels if you can find them. ;) Thomas (P.S. If the people who read the Digest version of these threads could edit their subject lines appropriately as mentioned in the digest itself: "When replying, please edit your Subject line so it is more specific..." ...then we won't have threads split up like this one. Thanks.) On Sat, Jan 23, 2010 at 08:58:59PM -0500, David F Bleil wrote: > Thank you to all who made suggestions and comments. The key seems to have been > the understanding that PulseAudio and ALSA talk to each other, or at least > supposed to.?? > > ?After fumbling around with the driver I got from the chip manufacturer site I > got to an error I could understand. ?The compiler was complaining about a > field called CFLAGS, and said the source should be changed to EXTRA_CFLAGS. ?I > googled that and found an entry explaining that someone had installed the > 1.0.19 version of the driver and it fixed everything with a link to the ALSA > site. ?I went there and got their latest source along with all the related > utilities and libraries for 1.0.22! ??Finally, everything worked, no more > error message about snd-via82xx. > > Once again Linux has proved to be a learning experience whether I wanted it or > not. However there is help when needed and that is what makes this a > community. > > David 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 From tjk at annapolislinux.org Thu Jan 28 07:28:44 2010 From: tjk at annapolislinux.org (Theodore Knab) Date: Thu, 28 Jan 2010 07:28:44 -0500 Subject: [Lugstuff] Next LUG Monday Feb 1: Scribus Presentation 7PM Message-ID: <20100128122844.GA29365@annapolislinux.org> Hi this month we have presentation on Scribus scheduled. Presenter: David Bleil Application: Scribus Desktop publishing http://www.scribus.net/ Directions to the meeting can be found here: http://annapolislinux.org/?page_id=23 -- Ted Knab Stevensville, MD USA From james.raymond.duncan at verizon.net Thu Jan 28 08:06:32 2010 From: james.raymond.duncan at verizon.net (James Duncan) Date: Thu, 28 Jan 2010 08:06:32 -0500 Subject: [Lugstuff] Next LUG Monday Feb 1: Scribus Presentation 7PM In-Reply-To: <20100128122844.GA29365@annapolislinux.org> References: <20100128122844.GA29365@annapolislinux.org> Message-ID: <000601caa01a$b75c6500$26152f00$@raymond.duncan@verizon.net> "Next meeting is Feb 1 2010" is listed on the website. Is that accurate? I thought meetings were on the First Monday which I believe is Feb 4. Have the meeting days changed? James Duncan email: james.raymond.duncan at verizon.net > -----Original Message----- > From: lugstuff-bounces at annapolislinux.org [mailto:lugstuff- > bounces at annapolislinux.org] On Behalf Of Theodore Knab > Sent: Thursday, January 28, 2010 7:29 AM > To: lugstuff at annapolislinux.org > Subject: [Lugstuff] Next LUG Monday Feb 1: Scribus Presentation 7PM > > Hi this month we have presentation on Scribus scheduled. > > Presenter: David Bleil > Application: Scribus Desktop publishing http://www.scribus.net/ > > Directions to the meeting can be found here: > http://annapolislinux.org/?page_id=23 > > -- > Ted Knab > Stevensville, MD USA > > _______________________________________________ > Lugstuff mailing list > Lugstuff at annapolislinux.org > http://list.annapolislinux.org/cgi-bin/mailman/listinfo/lugstuff From james.raymond.duncan at verizon.net Thu Jan 28 08:09:07 2010 From: james.raymond.duncan at verizon.net (James Duncan) Date: Thu, 28 Jan 2010 08:09:07 -0500 Subject: [Lugstuff] Next LUG Monday Feb 1: Scribus Presentation 7PM References: <20100128122844.GA29365@annapolislinux.org> Message-ID: <000701caa01b$1390d360$3ab27a20$@raymond.duncan@verizon.net> Please disregard the previous message. I was looking at calendar on my mobile phone and was still looking at January. First Monday in Feb is Feb 1. Sorry for the spam. Need to not try to dash off email before heading out in the morning. James Duncan email: james.raymond.duncan at verizon.net > -----Original Message----- > From: James Duncan [mailto:james.raymond.duncan at verizon.net] > Sent: Thursday, January 28, 2010 8:07 AM > To: 'Theodore Knab' > Cc: 'lugstuff at annapolislinux.org' > Subject: RE: [Lugstuff] Next LUG Monday Feb 1: Scribus Presentation 7PM > > "Next meeting is Feb 1 2010" is listed on the website. Is that > accurate? I thought meetings were on the First Monday which I believe > is Feb 4. Have the meeting days changed? > > James Duncan > email: james.raymond.duncan at verizon.net > > > -----Original Message----- > > From: lugstuff-bounces at annapolislinux.org [mailto:lugstuff- > > bounces at annapolislinux.org] On Behalf Of Theodore Knab > > Sent: Thursday, January 28, 2010 7:29 AM > > To: lugstuff at annapolislinux.org > > Subject: [Lugstuff] Next LUG Monday Feb 1: Scribus Presentation 7PM > > > > Hi this month we have presentation on Scribus scheduled. > > > > Presenter: David Bleil > > Application: Scribus Desktop publishing http://www.scribus.net/ > > > > Directions to the meeting can be found here: > > http://annapolislinux.org/?page_id=23 > > > > -- > > Ted Knab > > Stevensville, MD USA > > > > _______________________________________________ > > Lugstuff mailing list > > Lugstuff at annapolislinux.org > > http://list.annapolislinux.org/cgi-bin/mailman/listinfo/lugstuff