Re: [Cooker] [alsa] driver error
On Fri, 2003-04-04 at 13:07, B Lauber wrote: > > > >>The snd-via82xx module causes my system to hard lock at boot time. If > >I > > > >>switch to the oss-equivalent sound driver ( via82cxxx_audio ), my > >system > > > >>boots just fine. > > > >> > > > >>BTW, My sound card is a VT82C686 [Apollo Super AC97/Audio]. > > > >> > > > >>If anyone has any idea why this driver would cause my system to hard > >lock, > > > >>I would be very thankful for the input. I would like to use the alsa > > > >>drivers because they appear to be designed with software suspend in > >mind > > > >>(at least, that's the way it appears from parsing the suspend > >scripts). > > > >> > > > >>_ > > > >>MSN 8 with e-mail virus protection service: 2 months FREE* > > > >>http://join.msn.com/?page=features/virus > > > >> > > > >> > > > > > > > > > > > > > > > > > > > > > > > >I just wanted to give an update on the status of this problem. > >Apparently, > > > >the driver is configured wrongly during installation by drakx. As I > >stated > > > >above, I instead installed the oss equivalent driver and was able to > > > >successfully get through the system install. If I go back later and > >change > > > >the driver back to the alsa driver using draksound, then the driver is > > > >reconfigured perfectly. Thus, I now have sound via alsa. > > > > > > > >So for me, this is no longer a problem; for new users, the drakx > >installer > > > >needs to be corrected so that this driver is correctly configured (it > >would > > > >be discouraging to Linux newbies if their system hardlocked on the > >first > > > >boot). > > > > > > > >_ > > > > > > > > > > > > > > > > > > > > > > > > Now I have one more quick update and a question: > > > I have been able to get the alsa driver to successfully suspend and > >recover > > > if I set the following flags in /etc/sysconfig/suspend: > > > > > > RESTORE_SOUND="yes" > > > SOUND_MODULES="sb uart401 sound soundcore maestro cs4281 > > > > > > If RESTORE_SOUND="no" , then only the left sound channel recovers from a > > > suspend (even then, this channel sounds like it has experienced an > >upward > > > pitch shift). The only problem with setting RESTORE_SOUND="yes" is that > >it > > > causes the gnome Control Volume applet to die when I reenter xfree86. > >Since > > > this is sorta annoying, I'd like to be able to just get rid of the > >applet > > > and instead configure some laptop function keys to control my volume. > >Does > > > anyone know how I would go about doing this? > > > >On my laptop the same "system" of volume control works as in the manual > >for me it's fn-f5 and then the left and right arrow keys. Have you > >tried to do it this way... IOW the way the manual says? > > > > > > > > _ > > > > > > > > > > > > > > > > > That's how my system is supposed to work, but those buttons are not > automatically configured under Linux. I saw some documentation about > configuring the function keys when I was a Linux newbie, but I haven't been > able to relocate it. > Try this link. http://134.76.25.165/~woelz/linux/kbd/tastatur.html found it via linux-laptop.net aka linux-on-laptops.com James
Re: [Cooker] [alsa] driver error
From: Thierry Vignaud <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [Cooker] [alsa] driver error Date: Fri, 04 Apr 2003 11:24:55 +0200 "B Lauber" <[EMAIL PROTECTED]> writes: > I just wanted to give an update on the status of this problem. > Apparently, the driver is configured wrongly during installation by > drakx. As I stated above, I instead installed the oss equivalent > driver and was able to successfully get through the system install. > If I go back later and change the driver back to the alsa driver > using draksound, then the driver is reconfigured perfectly. Thus, I > now have sound via alsa. could you diff the config file before/after your changes ? I don't think I can at this time because it would require me to reinstall mdk9.1 . I'll see what I can do, though. _ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
Re: [Cooker] [alsa] driver error
From: James Sparenberg <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: Cooker List <[EMAIL PROTECTED]> Subject: Re: [Cooker] [alsa] driver error Date: 03 Apr 2003 00:02:08 -0800 On Thu, 2003-04-03 at 16:08, B Lauber wrote: > >From: "B Lauber" <[EMAIL PROTECTED]> > >Reply-To: [EMAIL PROTECTED] > >To: [EMAIL PROTECTED] > >Subject: Re: [Cooker] [alsa] driver error > >Date: Thu, 03 Apr 2003 17:50:34 -0500 > > > > > > > > > > > > > > > > > >>From: "B Lauber" <[EMAIL PROTECTED]> > >>Reply-To: [EMAIL PROTECTED] > >>To: [EMAIL PROTECTED] > >>Subject: [Cooker] [alsa] driver error > >>Date: Thu, 03 Apr 2003 17:04:55 -0500 > >> > >>The snd-via82xx module causes my system to hard lock at boot time. If I > >>switch to the oss-equivalent sound driver ( via82cxxx_audio ), my system > >>boots just fine. > >> > >>BTW, My sound card is a VT82C686 [Apollo Super AC97/Audio]. > >> > >>If anyone has any idea why this driver would cause my system to hard lock, > >>I would be very thankful for the input. I would like to use the alsa > >>drivers because they appear to be designed with software suspend in mind > >>(at least, that's the way it appears from parsing the suspend scripts). > >> > >>_ > >>MSN 8 with e-mail virus protection service: 2 months FREE* > >>http://join.msn.com/?page=features/virus > >> > >> > > > > > > > > > > > >I just wanted to give an update on the status of this problem. Apparently, > >the driver is configured wrongly during installation by drakx. As I stated > >above, I instead installed the oss equivalent driver and was able to > >successfully get through the system install. If I go back later and change > >the driver back to the alsa driver using draksound, then the driver is > >reconfigured perfectly. Thus, I now have sound via alsa. > > > >So for me, this is no longer a problem; for new users, the drakx installer > >needs to be corrected so that this driver is correctly configured (it would > >be discouraging to Linux newbies if their system hardlocked on the first > >boot). > > > >_ > > > > > > > > > > Now I have one more quick update and a question: > I have been able to get the alsa driver to successfully suspend and recover > if I set the following flags in /etc/sysconfig/suspend: > > RESTORE_SOUND="yes" > SOUND_MODULES="sb uart401 sound soundcore maestro cs4281 > > If RESTORE_SOUND="no" , then only the left sound channel recovers from a > suspend (even then, this channel sounds like it has experienced an upward > pitch shift). The only problem with setting RESTORE_SOUND="yes" is that it > causes the gnome Control Volume applet to die when I reenter xfree86. Since > this is sorta annoying, I'd like to be able to just get rid of the applet > and instead configure some laptop function keys to control my volume. Does > anyone know how I would go about doing this? On my laptop the same "system" of volume control works as in the manual for me it's fn-f5 and then the left and right arrow keys. Have you tried to do it this way... IOW the way the manual says? > > _ > > > That's how my system is supposed to work, but those buttons are not automatically configured under Linux. I saw some documentation about configuring the function keys when I was a Linux newbie, but I haven't been able to relocate it. _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
Re: [Cooker] [alsa] driver error
"B Lauber" <[EMAIL PROTECTED]> writes: > I just wanted to give an update on the status of this problem. > Apparently, the driver is configured wrongly during installation by > drakx. As I stated above, I instead installed the oss equivalent > driver and was able to successfully get through the system install. > If I go back later and change the driver back to the alsa driver > using draksound, then the driver is reconfigured perfectly. Thus, I > now have sound via alsa. could you diff the config file before/after your changes ?
Re: [Cooker] [alsa] driver error
On Thu, 2003-04-03 at 16:08, B Lauber wrote: > >From: "B Lauber" <[EMAIL PROTECTED]> > >Reply-To: [EMAIL PROTECTED] > >To: [EMAIL PROTECTED] > >Subject: Re: [Cooker] [alsa] driver error > >Date: Thu, 03 Apr 2003 17:50:34 -0500 > > > > > > > > > > > > > > > > > >>From: "B Lauber" <[EMAIL PROTECTED]> > >>Reply-To: [EMAIL PROTECTED] > >>To: [EMAIL PROTECTED] > >>Subject: [Cooker] [alsa] driver error > >>Date: Thu, 03 Apr 2003 17:04:55 -0500 > >> > >>The snd-via82xx module causes my system to hard lock at boot time. If I > >>switch to the oss-equivalent sound driver ( via82cxxx_audio ), my system > >>boots just fine. > >> > >>BTW, My sound card is a VT82C686 [Apollo Super AC97/Audio]. > >> > >>If anyone has any idea why this driver would cause my system to hard lock, > >>I would be very thankful for the input. I would like to use the alsa > >>drivers because they appear to be designed with software suspend in mind > >>(at least, that's the way it appears from parsing the suspend scripts). > >> > >>_ > >>MSN 8 with e-mail virus protection service: 2 months FREE* > >>http://join.msn.com/?page=features/virus > >> > >> > > > > > > > > > > > >I just wanted to give an update on the status of this problem. Apparently, > >the driver is configured wrongly during installation by drakx. As I stated > >above, I instead installed the oss equivalent driver and was able to > >successfully get through the system install. If I go back later and change > >the driver back to the alsa driver using draksound, then the driver is > >reconfigured perfectly. Thus, I now have sound via alsa. > > > >So for me, this is no longer a problem; for new users, the drakx installer > >needs to be corrected so that this driver is correctly configured (it would > >be discouraging to Linux newbies if their system hardlocked on the first > >boot). > > > >_ > > > > > > > > > > Now I have one more quick update and a question: > I have been able to get the alsa driver to successfully suspend and recover > if I set the following flags in /etc/sysconfig/suspend: > > RESTORE_SOUND="yes" > SOUND_MODULES="sb uart401 sound soundcore maestro cs4281 > > If RESTORE_SOUND="no" , then only the left sound channel recovers from a > suspend (even then, this channel sounds like it has experienced an upward > pitch shift). The only problem with setting RESTORE_SOUND="yes" is that it > causes the gnome Control Volume applet to die when I reenter xfree86. Since > this is sorta annoying, I'd like to be able to just get rid of the applet > and instead configure some laptop function keys to control my volume. Does > anyone know how I would go about doing this? On my laptop the same "system" of volume control works as in the manual for me it's fn-f5 and then the left and right arrow keys. Have you tried to do it this way... IOW the way the manual says? > > _ > > >
Re: [Cooker] [alsa] driver error
From: "B Lauber" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [Cooker] [alsa] driver error Date: Thu, 03 Apr 2003 17:50:34 -0500 From: "B Lauber" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [Cooker] [alsa] driver error Date: Thu, 03 Apr 2003 17:04:55 -0500 The snd-via82xx module causes my system to hard lock at boot time. If I switch to the oss-equivalent sound driver ( via82cxxx_audio ), my system boots just fine. BTW, My sound card is a VT82C686 [Apollo Super AC97/Audio]. If anyone has any idea why this driver would cause my system to hard lock, I would be very thankful for the input. I would like to use the alsa drivers because they appear to be designed with software suspend in mind (at least, that's the way it appears from parsing the suspend scripts). _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus I just wanted to give an update on the status of this problem. Apparently, the driver is configured wrongly during installation by drakx. As I stated above, I instead installed the oss equivalent driver and was able to successfully get through the system install. If I go back later and change the driver back to the alsa driver using draksound, then the driver is reconfigured perfectly. Thus, I now have sound via alsa. So for me, this is no longer a problem; for new users, the drakx installer needs to be corrected so that this driver is correctly configured (it would be discouraging to Linux newbies if their system hardlocked on the first boot). _ Now I have one more quick update and a question: I have been able to get the alsa driver to successfully suspend and recover if I set the following flags in /etc/sysconfig/suspend: RESTORE_SOUND="yes" SOUND_MODULES="sb uart401 sound soundcore maestro cs4281 If RESTORE_SOUND="no" , then only the left sound channel recovers from a suspend (even then, this channel sounds like it has experienced an upward pitch shift). The only problem with setting RESTORE_SOUND="yes" is that it causes the gnome Control Volume applet to die when I reenter xfree86. Since this is sorta annoying, I'd like to be able to just get rid of the applet and instead configure some laptop function keys to control my volume. Does anyone know how I would go about doing this? _
Re: [Cooker] [alsa] driver error
From: "B Lauber" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [Cooker] [alsa] driver error Date: Thu, 03 Apr 2003 17:04:55 -0500 The snd-via82xx module causes my system to hard lock at boot time. If I switch to the oss-equivalent sound driver ( via82cxxx_audio ), my system boots just fine. BTW, My sound card is a VT82C686 [Apollo Super AC97/Audio]. If anyone has any idea why this driver would cause my system to hard lock, I would be very thankful for the input. I would like to use the alsa drivers because they appear to be designed with software suspend in mind (at least, that's the way it appears from parsing the suspend scripts). _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus I just wanted to give an update on the status of this problem. Apparently, the driver is configured wrongly during installation by drakx. As I stated above, I instead installed the oss equivalent driver and was able to successfully get through the system install. If I go back later and change the driver back to the alsa driver using draksound, then the driver is reconfigured perfectly. Thus, I now have sound via alsa. So for me, this is no longer a problem; for new users, the drakx installer needs to be corrected so that this driver is correctly configured (it would be discouraging to Linux newbies if their system hardlocked on the first boot). _
[Cooker] [alsa] driver error
The snd-via82xx module causes my system to hard lock at boot time. If I switch to the oss-equivalent sound driver ( via82cxxx_audio ), my system boots just fine. BTW, My sound card is a VT82C686 [Apollo Super AC97/Audio]. If anyone has any idea why this driver would cause my system to hard lock, I would be very thankful for the input. I would like to use the alsa drivers because they appear to be designed with software suspend in mind (at least, that's the way it appears from parsing the suspend scripts). _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus
