Re: [gentoo-user] alsa problems on kernel 2.6.0-test8
On Tue, 4 Nov 2003 13:18:56 -0700 Collins Richey [EMAIL PROTECTED] wrote: On Tue, 04 Nov 2003 14:17:31 -0500 brett holcomb [EMAIL PROTECTED] wrote: Do you get any error messages in any logs? Here, alsa has worked like a champ. I build it (and rebuild if I do another kernel). After that I copy my saved alsa file to /etc/modules.d and do the modules-update. Works fine. Small note. This is 2.6 kernel. There is nothing to rebuild after generating a kernel. alsa is now a part of the kernel tree. Finally found a decent workaround on forums. alsasound does not work for some (all?) sound cards unless the specific module (ens1371 in my case) is preloaded. Adding ens1371 to /etc/modules.autoload is the answer. I did not find a reported bug, so I opened bugzilla #32880. -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
[gentoo-user] alsa problems on kernel 2.6.0-test8
I have finally gotten alsa to work for my SoundBlaster PCI 64 (ens1371), but it's still a bit hokey. I've seen a few reports but no real answers on forum. Maybe someone knows the answer. Bugzilla is down, so I can't search there at present. 1. You should be able to compile the 2.6 alsa modules as built in, but this does not work. The kernel reports that the soundcard is not working. 2. Alsa compiled as modules does work with a little tinkering. a. If I add alsasound to the boot level scripts as recommended, sound does not work. Devfsd does not build the /dev/dsp ... entries. b. If I add alsasound to the default level scripts as recommended, same results as for a. A few extra dependancy complaints, since alsasound is design for executing at boot time. c. After either of these approaches, if I issue /etc/init.d/alsasound stop and then /etc/init.d/alsasound start, sound works. So, what I do for now is to add the following to /etc/conf.d/local.start /etc/init.d/alsasound start /etc/init.d/alsasound stop /etc/init.d/alsasound start Messy (lots of dependancy errors) , but it works. Does anyone have a clue how to fix this POS? -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problems on kernel 2.6.0-test8
Do you get any error messages in any logs? Here, alsa has worked like a champ. I build it (and rebuild if I do another kernel). After that I copy my saved alsa file to /etc/modules.d and do the modules-update. Works fine. On Tue, 4 Nov 2003 11:09:38 -0700 Collins Richey [EMAIL PROTECTED] wrote: I have finally gotten alsa to work for my SoundBlaster PCI 64 (ens1371), but it's still a bit hokey. I've seen a few reports but no real answers on forum. Maybe someone knows the answer. Bugzilla is down, so I can't search there at present. 1. You should be able to compile the 2.6 alsa modules as built in, but this does not work. The kernel reports that the soundcard is not working. 2. Alsa compiled as modules does work with a little tinkering. a. If I add alsasound to the boot level scripts as recommended, sound does not work. Devfsd does not build the /dev/dsp ... entries. b. If I add alsasound to the default level scripts as recommended, same results as for a. A few extra dependancy complaints, since alsasound is design for executing at boot time. c. After either of these approaches, if I issue /etc/init.d/alsasound stop and then /etc/init.d/alsasound start, sound works. So, what I do for now is to add the following to /etc/conf.d/local.start /etc/init.d/alsasound start /etc/init.d/alsasound stop /etc/init.d/alsasound start Messy (lots of dependancy errors) , but it works. Does anyone have a clue how to fix this POS? -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problems on kernel 2.6.0-test8
On Tue, 04 Nov 2003 14:17:31 -0500 brett holcomb [EMAIL PROTECTED] wrote: Do you get any error messages in any logs? Here, alsa has worked like a champ. I build it (and rebuild if I do another kernel). After that I copy my saved alsa file to /etc/modules.d and do the modules-update. Works fine. Small note. This is 2.6 kernel. There is nothing to rebuild after generating a kernel. alsa is now a part of the kernel tree. -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problems on kernel 2.6.0-test8
Ahha - I'm on 2.4.x series. When 2.6,7, or whatever is stable then I'll go for that! On Tuesday 04 November 2003 15:18, you wrote: On Tue, 04 Nov 2003 14:17:31 -0500 brett holcomb [EMAIL PROTECTED] wrote: Do you get any error messages in any logs? Here, alsa has worked like a champ. I build it (and rebuild if I do another kernel). After that I copy my saved alsa file to /etc/modules.d and do the modules-update. Works fine. Small note. This is 2.6 kernel. There is nothing to rebuild after generating a kernel. alsa is now a part of the kernel tree. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problems on kernel 2.6.0-test8
On Tue, 4 Nov 2003 18:26:18 -0500 Brett I. Holcomb [EMAIL PROTECTED] wrote: Ahha - I'm on 2.4.x series. When 2.6,7, or whatever is stable then I'll go for that! On Tuesday 04 November 2003 15:18, you wrote: On Tue, 04 Nov 2003 14:17:31 -0500 brett holcomb [EMAIL PROTECTED] wrote: Do you get any error messages in any logs? Here, alsa has worked like a champ. I build it (and rebuild if I do another kernel). After that I copy my saved alsa file to /etc/modules.d and do the modules-update. Works fine. Small note. This is 2.6 kernel. There is nothing to rebuild after generating a kernel. alsa is now a part of the kernel tree. Unless you have a very unusual configuration, it's rock solid now. I've been on board since 2.5.x (now 2.6.0_test8) without any glitches - several months. I'm sure this is in part due to the fact that I use plain ole ext3 instead of the more adventuresome filesystems grin. Even nvidia has updated their modules. 2.6 is a lot more stable at this point than 2.4 was in its early stages. Getting alsa support to work for my ens1371 has been the only problem, and that is nothing new - never worked on for me on 2.4. Now at least I have a workable (if clumsy) solution. Prior to this on 2.4 and 2.6 I could only get the OSS support for ens1371 to work. -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problems on kernel 2.6.0-test8
Has Linus released it G. I guess sometime I'll delve into but I get the idea it's still in development. Right now I need to run and don't have time to mess with it - maybe later on. On Tuesday 04 November 2003 19:16, you wrote: On Tue, 4 Nov 2003 18:26:18 -0500 Brett I. Holcomb [EMAIL PROTECTED] wrote: Ahha - I'm on 2.4.x series. When 2.6,7, or whatever is stable then I'll go for that! generating a kernel. alsa is now a part of the kernel tree. Unless you have a very unusual configuration, it's rock solid now. I've been on board since 2.5.x (now 2.6.0_test8) without any glitches - several months. I'm sure this is in part due to the fact that I use plain ole ext3 instead of the more adventuresome filesystems grin. Even nvidia has updated their modules. 2.6 is a lot more stable at this point than 2.4 was in its early stages. Getting alsa support to work for my ens1371 has been the only problem, and that is nothing new - never worked on for me on 2.4. Now at least I have a workable (if clumsy) solution. Prior to this on 2.4 and 2.6 I could only get the OSS support for ens1371 to work. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problems on kernel 2.6.0-test8
On Tue, 4 Nov 2003 19:26:15 -0500 Brett I. Holcomb [EMAIL PROTECTED] wrote: Has Linus released it G. I guess sometime I'll delve into but I get the idea it's still in development. Right now I need to run and don't have time to mess with it - maybe later on. Yeah, he releases it every few weeks grin. -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problems on kernel 2.6.0-test8
Collins Richey wrote: I have finally gotten alsa to work for my SoundBlaster PCI 64 (ens1371), but it's still a bit hokey. I've seen a few reports but no real answers on forum. Maybe someone knows the answer. Bugzilla is down, so I can't search there at present. 1. You should be able to compile the 2.6 alsa modules as built in, but this does not work. The kernel reports that the soundcard is not working. 2. Alsa compiled as modules does work with a little tinkering. a. If I add alsasound to the boot level scripts as recommended, sound does not work. Devfsd does not build the /dev/dsp ... entries. b. If I add alsasound to the default level scripts as recommended, same results as for a. A few extra dependancy complaints, since alsasound is design for executing at boot time. c. After either of these approaches, if I issue /etc/init.d/alsasound stop and then /etc/init.d/alsasound start, sound works. So, what I do for now is to add the following to /etc/conf.d/local.start Do not do this. Only do: $ rc-update add alsasound boot /etc/init.d/alsasound start /etc/init.d/alsasound stop /etc/init.d/alsasound start Messy (lots of dependancy errors) , but it works. Does anyone have a clue how to fix this POS? Steps to get ALSA to work in 2.6 kernel. (1) Enable all ALSA related options in kernel. (2) Boot off newly compiled kernel. (3) Unmute channels (I use gkrellm-volume plugin to do this) Look here for screenshot of gkrellm-volume control if you like. http://dhruba.codewordt.co.uk/images/gkv.png (left-centre) There is no compelling need to emerge anything alsa-related at all. The only problem is saving your volume levels on shutdown and restoring them on startup and that can be done using: $ alsactl store (put this in /etc/conf.d/local.stop) $ alsactl restore (put this in /etc/conf.d/local.start) Then you are sorted. I myself prefer not to emerge anything alsa related as there is no need and that way your system does not get the dreaded libasound.la library against which many packages begin to compile and depend upon. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problems on kernel 2.6.0-test8
Well I'll wait then G. On Tuesday 04 November 2003 19:50, you wrote: On Tue, 4 Nov 2003 19:26:15 -0500 Brett I. Holcomb [EMAIL PROTECTED] wrote: Has Linus released it G. I guess sometime I'll delve into but I get the idea it's still in development. Right now I need to run and don't have time to mess with it - maybe later on. Yeah, he releases it every few weeks grin. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problems on kernel 2.6.0-test8
On Wed, 05 Nov 2003 03:34:50 + Dhruba Bandopadhyay [EMAIL PROTECTED] wrote: Collins Richey wrote: I have finally gotten alsa to work for my SoundBlaster PCI 64 (ens1371), but it's still a bit hokey. I've seen a few reports but no real answers on forum. Maybe someone knows the answer. Bugzilla is down, so I can't search there at present. 1. You should be able to compile the 2.6 alsa modules as built in, but this does not work. The kernel reports that the soundcard is not working. 2. Alsa compiled as modules does work with a little tinkering. a. If I add alsasound to the boot level scripts as recommended, sound does not work. Devfsd does not build the /dev/dsp ... entries. b. If I add alsasound to the default level scripts as recommended, same results as for a. A few extra dependancy complaints, since alsasound is design for executing at boot time. c. After either of these approaches, if I issue /etc/init.d/alsasound stop and then /etc/init.d/alsasound start, sound works. So, what I do for now is to add the following to /etc/conf.d/local.start Do not do this. Only do: $ rc-update add alsasound boot You didn't read my report closely enough! THIS DOES NOT WORK. If I add alsasound to the boot runlevel then reboot, alsasound starts but the sound card IS NOT WORKING. Read that line again. After doing only this much, devfsd has not generated the /dev/dsp etc. entries, so I can't unmute the sound card! I have to stop alsasound and start it again for the sound card to work. All the apropriate modules are loaded the first time, but the soundcard DOES NOT WORK and /dev/dsp ... are not generated until I stop and start alsasound again. /etc/init.d/alsasound start /etc/init.d/alsasound stop /etc/init.d/alsasound start Messy (lots of dependancy errors) , but it works. Does anyone have a clue how to fix this POS? Steps to get ALSA to work in 2.6 kernel. (1) Enable all ALSA related options in kernel. (2) Boot off newly compiled kernel. All this has been done, except that I haven't compiled the PCI modules for sound cards that I do not have. (3) Unmute channels (I use gkrellm-volume plugin to do this) See above. THIS DOES NOT WORK without stopping and starting alsasound again. Look here for screenshot of gkrellm-volume control if you like. http://dhruba.codewordt.co.uk/images/gkv.png (left-centre) There is no compelling need to emerge anything alsa-related at all. The only problem is saving your volume levels on shutdown and restoring them on startup and that can be done using: I haven't emerged anything alsa-related. $ alsactl store (put this in /etc/conf.d/local.stop) $ alsactl restore (put this in /etc/conf.d/local.start) This doesn't work either. Then you are sorted. Unfortunately not. -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
