Re: sndconfig problems: sound only works until reboot
--- Donald Spoon <[EMAIL PROTECTED]> wrote: > Joris Huizer wrote: > > Hello everybody, > > > > I don't know wether this is important so to be > sure I > > send this. > > In an old email I found somebody suggesting lspci; > > Here is the output: > > > > 00:00.0 Host bridge: OPTi Inc. 82C701 [FireStar > Plus] > > (rev 32) > > 00:01.0 ISA bridge: OPTi Inc. 82C700 (rev 31) > > 00:0a.0 CardBus bridge: Texas Instruments PCI1131 > (rev > > 01) > > 00:0a.1 CardBus bridge: Texas Instruments PCI1131 > (rev > > 01) > > 00:12.0 VGA compatible controller: Neomagic > > Corporation NM2160 [MagicGraph 128XD] (rev 01) > > 00:13.0 USB Controller: OPTi Inc. 82C861 (rev 10) > > 00:14.0 IDE interface: OPTi Inc. 82C825 > [Firebridge 2] > > (rev 30) > > > > Now, I thind this output a bit confusing: Not a > word > > about ESS 1869, so does this mean this laptop > doesn't > > have that card?? I saw at a few pages this card is > > normally used on Compaq Pressario 1245 - but why > isn't > > it showing up?? Or is it named differently > somehow? > > > > Can this output help anyone help me what the > sndconfig > > does to make sound work - temporarily :-( ? > > It tells me that the sound chip ISN'T hooked > directly to the PCI bus. > It is probably sitting off the ISA bus, and probably > ISN'T Plug & Play. > > More helpful to me is your origianl post saying you > got it working with > the SoundBlaster drivers via Sndconfig, but the > settings disappear when > you re-boot. I suspect what is happening is the > proper modules & > settings are being inserted into memory via > modprobe, but the file > changes needed to re-load these modules on the next > re-boot are NOT > being made. > > I have not used Sndconfig here recently, but as I > recall it first > tested the system with the requested modules & > settings, THEN wrote the > proper changes to /etc/modutils/sndconfig file if > they worked. I am not > sure what it did after that, but once this file is > written, it "should" > have run "update-modules" to re-write the > /etc/modules.conf file with > the new settings. This is the file that is read at > every bootup to > insert the desired modules. You shouldn't edit the > /etc/modules.conf > file directly, but let it be re-written by > "update-modules". > > I suggest you take a look and see if the > "/etc/modutils/sndconfig" file > is present on your system. It "should" be there as > a result of your > previous incantation of Sndconfig. If it is there, > just run the command > "update-modules" as root, and try a re-boot. That > should make it work. > If it isn't there, you should re-run sndconfig and > make sure you > "save" the changes. Check /etc/modutils/sndconfig > to make sure it is > there and jump into the above routine. > Well I see you are up to date on sndconfig allright :-) Indeed, sndconfig writes a /etc/modutils/sndconfig; It *forgets* to run update-modules but that's just a small problem. I did more searches, including just the name sndconfig - and I found a doc which discribes how sndconfig works at http://www.linuxheadquarters.com/howto/basic/sndconfig.shtml However, some things don't happen: it doesn't seem to do anything with /etc/isapnp.conf, and the sample midi isn't played either. > Finally, it is possible that Sndconfig is not doing > what it is supposed > to do. It could be "broken" (have you checked the > buglists?) or > something else is interfering with it. I noticed in > previous posts that > you had experimented with ALSA. ALSA will work, but > I have found it to > be a bit more difficult to setup. IF you have any > ALSA stuff still on > your system, it could easily be interfering with the > OSS sound setup > used by sndconfig. I would suggest sticking with > one or the other. IF > you want to use sndconfig, remove all the ALSA > packages. IF sndconfig > isn't writing the file mentioned above, you could > always try inserting > the needed modules with the "modconf" program. Once > you know which ones > are needed, then using modconf will insure they get > inserted properly > and will be re-loaded upon the next reboot. > I might have a look at possible buglists in a few; Yeah at first I was told I should use ALSA but later on I saw sndconfig being mentioned in a page on my laptop so I thought let's give it a try; Later on I did a new kernel compilation without ALSA so alsa shouldn't be in the way. Anyway, I removed all programs which had to do with ALSA after your post. > BTW, this is just an "educated guess". I don't have > that particular > sound chipset here... > > > > > BTW, I put a question on a forum but after one > > response (and my answer) they got silent - is this > an > > unusual problem or something ? > > Well actually this is not true anymore - it was just silent for a few days. You may have a look at http://www.linuxforums.org/viewtopic.php?t=2635&sid=8219c5269c90c513957ed26d78e43fa2 for the disscussion. (Many of the facts I mentioned here are mentioned th
Re: sndconfig problems: sound only works until reboot
Joris Huizer wrote: Hello everybody, I don't know wether this is important so to be sure I send this. In an old email I found somebody suggesting lspci; Here is the output: 00:00.0 Host bridge: OPTi Inc. 82C701 [FireStar Plus] (rev 32) 00:01.0 ISA bridge: OPTi Inc. 82C700 (rev 31) 00:0a.0 CardBus bridge: Texas Instruments PCI1131 (rev 01) 00:0a.1 CardBus bridge: Texas Instruments PCI1131 (rev 01) 00:12.0 VGA compatible controller: Neomagic Corporation NM2160 [MagicGraph 128XD] (rev 01) 00:13.0 USB Controller: OPTi Inc. 82C861 (rev 10) 00:14.0 IDE interface: OPTi Inc. 82C825 [Firebridge 2] (rev 30) Now, I thind this output a bit confusing: Not a word about ESS 1869, so does this mean this laptop doesn't have that card?? I saw at a few pages this card is normally used on Compaq Pressario 1245 - but why isn't it showing up?? Or is it named differently somehow? Can this output help anyone help me what the sndconfig does to make sound work - temporarily :-( ? It tells me that the sound chip ISN'T hooked directly to the PCI bus. It is probably sitting off the ISA bus, and probably ISN'T Plug & Play. More helpful to me is your origianl post saying you got it working with the SoundBlaster drivers via Sndconfig, but the settings disappear when you re-boot. I suspect what is happening is the proper modules & settings are being inserted into memory via modprobe, but the file changes needed to re-load these modules on the next re-boot are NOT being made. I have not used Sndconfig here recently, but as I recall it first tested the system with the requested modules & settings, THEN wrote the proper changes to /etc/modutils/sndconfig file if they worked. I am not sure what it did after that, but once this file is written, it "should" have run "update-modules" to re-write the /etc/modules.conf file with the new settings. This is the file that is read at every bootup to insert the desired modules. You shouldn't edit the /etc/modules.conf file directly, but let it be re-written by "update-modules". I suggest you take a look and see if the "/etc/modutils/sndconfig" file is present on your system. It "should" be there as a result of your previous incantation of Sndconfig. If it is there, just run the command "update-modules" as root, and try a re-boot. That should make it work. If it isn't there, you should re-run sndconfig and make sure you "save" the changes. Check /etc/modutils/sndconfig to make sure it is there and jump into the above routine. Finally, it is possible that Sndconfig is not doing what it is supposed to do. It could be "broken" (have you checked the buglists?) or something else is interfering with it. I noticed in previous posts that you had experimented with ALSA. ALSA will work, but I have found it to be a bit more difficult to setup. IF you have any ALSA stuff still on your system, it could easily be interfering with the OSS sound setup used by sndconfig. I would suggest sticking with one or the other. IF you want to use sndconfig, remove all the ALSA packages. IF sndconfig isn't writing the file mentioned above, you could always try inserting the needed modules with the "modconf" program. Once you know which ones are needed, then using modconf will insure they get inserted properly and will be re-loaded upon the next reboot. BTW, this is just an "educated guess". I don't have that particular sound chipset here... BTW, I put a question on a forum but after one response (and my answer) they got silent - is this an unusual problem or something ? I went to the Debian-User Archives and searched on your name in order to review the original post on this subject. I notice you have over 30 posts to Debian-User on a variety of subjects... most with LOTS of answers! I think you should be able to answer your question with a little thinking. People DO help... when they think they have something to contribute... I suspect not too many people have run into your particular "problem" on this one. Personally, I feel a bit uncomfortable "guessing" at a solution to your problem since I don't have your equipment here, but I thought I would add the above "generalities" for whatever they are worth. If you think about it, lists like this one NEVER solved a "problem"... all they do is point you in the proper direction for YOU to solve it! After all you are the one at the keyboard and with the hardware... Cheers, -Don Spoon- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sndconfig problems: sound only works until reboot
Hello everybody, I don't know wether this is important so to be sure I send this. In an old email I found somebody suggesting lspci; Here is the output: 00:00.0 Host bridge: OPTi Inc. 82C701 [FireStar Plus] (rev 32) 00:01.0 ISA bridge: OPTi Inc. 82C700 (rev 31) 00:0a.0 CardBus bridge: Texas Instruments PCI1131 (rev 01) 00:0a.1 CardBus bridge: Texas Instruments PCI1131 (rev 01) 00:12.0 VGA compatible controller: Neomagic Corporation NM2160 [MagicGraph 128XD] (rev 01) 00:13.0 USB Controller: OPTi Inc. 82C861 (rev 10) 00:14.0 IDE interface: OPTi Inc. 82C825 [Firebridge 2] (rev 30) Now, I thind this output a bit confusing: Not a word about ESS 1869, so does this mean this laptop doesn't have that card?? I saw at a few pages this card is normally used on Compaq Pressario 1245 - but why isn't it showing up?? Or is it named differently somehow? Can this output help anyone help me what the sndconfig does to make sound work - temporarily :-( ? BTW, I put a question on a forum but after one response (and my answer) they got silent - is this an unusual problem or something ? Thanks for any help ! Joris __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sndconfig problems: sound only works until reboot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 28 May 2003 10:27 am, Joris Huizer wrote: > Well, I couldn't really find the interesting part - > the link to the article about the other laptop is a > broken; > > I think the problem is that sndconfig uses modules > which are normally not active (temporarily activating > them or something) - I allready found it uses a module > called 'opl3' which was not active. > > I now have got the following sound modules installed: > opl3, sb, sb_lib, sound, soundcore, uart401. > > I attached the /etc/modules.conf - I hope you can tell > me what I am missing - I think it must be a module - > because, what else could be the problem after a > (re)boot ?? > > I can't find something usefull on google, except that > other people have had problems with sndconfig - no > real solutions :-( > > Thank you for your help, > > Joris When you run sndconfig are you root? It may be a permissions thing, accessing sound as a user you may have to be in the 'audio' group. - -- Greg Madden Debian GNU/Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+1UCGk7rtxKWZzGsRAuaeAKCuogzPYdggyfdHMWHXsuvcLvGiVgCfWtgK HP3RymNeeITB4v/R4Tao5M8= =CZAP -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sndconfig problems: sound only works until reboot
Joris Huizer <[EMAIL PROTECTED]> writes: > I think the problem is that sndconfig uses modules > which are normally not active (temporarily activating > them or something) - I allready found it uses a module > called 'opl3' which was not active. > > I now have got the following sound modules installed: > opl3, sb, sb_lib, sound, soundcore, uart401. > > I attached the /etc/modules.conf - I hope you can tell > me what I am missing - I think it must be a module - > because, what else could be the problem after a > (re)boot ?? I think to make module XYZ loaded at boot time, you want to add the line XYZ to /etc/modules. For me, having a module-enabled kernel, plus adding the line sb in /etc/modules was enough for my sound card (Creative Labs SB AWE32) to be activated at boot time. -- Benjamin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sndconfig problems: sound only works until reboot
Well, I couldn't really find the interesting part - the link to the article about the other laptop is a broken; I think the problem is that sndconfig uses modules which are normally not active (temporarily activating them or something) - I allready found it uses a module called 'opl3' which was not active. I now have got the following sound modules installed: opl3, sb, sb_lib, sound, soundcore, uart401. I attached the /etc/modules.conf - I hope you can tell me what I am missing - I think it must be a module - because, what else could be the problem after a (re)boot ?? I can't find something usefull on google, except that other people have had problems with sndconfig - no real solutions :-( Thank you for your help, Joris --- Antonio Rodriguez <[EMAIL PROTECTED]> wrote: > Debian Planet has some info that may help you. Check > the comments and links > http://debianplanet.com/node.php?id=949#comment > > - Original Message - > From: "Joris Huizer" <[EMAIL PROTECTED]> > To: "debian user" <[EMAIL PROTECTED]> > Sent: Wednesday, May 28, 2003 3:36 AM > Subject: sndconfig problems: sound only works until > reboot > > > > Hello everybody, > > > > I have this problem: > > I'm installing & configuring Debian on an Compaq > > Presario 1245 - the last part is sound. I was told > > this computer has a ESS 1869 sound card. > > > > I searched on the web and found a few pages > mentioning > > sndconfig. I gave it a try and got sound working > using > > the Soundblaster config; > > > > The problem is, for some reason sound is NOT > working > > when the computer is booted again. The only way I > > found to get it working again is, commenting out > > again, rebooting (otherwise sndconfig gives an > error > > about /dev/audio which isn't telling me nothing > except > > that somethings goes wrong) and running sndconfig > > again. > > > > Can anybody tell me what I should do to make the > sound > > work allways ? > > > > Thanks very much > > > > Joris > > > > __ > > Do you Yahoo!? > > Yahoo! Calendar - Free online calendar with sync > to Outlook(TM). > > http://calendar.yahoo.com > > > > > > -- > > To UNSUBSCRIBE, email to > [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > > > > -- > To UNSUBSCRIBE, email to > [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com modules.conf Description: modules.conf
Re: sndconfig problems: sound only works until reboot
Debian Planet has some info that may help you. Check the comments and links http://debianplanet.com/node.php?id=949#comment - Original Message - From: "Joris Huizer" <[EMAIL PROTECTED]> To: "debian user" <[EMAIL PROTECTED]> Sent: Wednesday, May 28, 2003 3:36 AM Subject: sndconfig problems: sound only works until reboot > Hello everybody, > > I have this problem: > I'm installing & configuring Debian on an Compaq > Presario 1245 - the last part is sound. I was told > this computer has a ESS 1869 sound card. > > I searched on the web and found a few pages mentioning > sndconfig. I gave it a try and got sound working using > the Soundblaster config; > > The problem is, for some reason sound is NOT working > when the computer is booted again. The only way I > found to get it working again is, commenting out > again, rebooting (otherwise sndconfig gives an error > about /dev/audio which isn't telling me nothing except > that somethings goes wrong) and running sndconfig > again. > > Can anybody tell me what I should do to make the sound > work allways ? > > Thanks very much > > Joris > > __ > Do you Yahoo!? > Yahoo! Calendar - Free online calendar with sync to Outlook(TM). > http://calendar.yahoo.com > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
sndconfig problems: sound only works until reboot
Hello everybody, I have this problem: I'm installing & configuring Debian on an Compaq Presario 1245 - the last part is sound. I was told this computer has a ESS 1869 sound card. I searched on the web and found a few pages mentioning sndconfig. I gave it a try and got sound working using the Soundblaster config; The problem is, for some reason sound is NOT working when the computer is booted again. The only way I found to get it working again is, commenting out again, rebooting (otherwise sndconfig gives an error about /dev/audio which isn't telling me nothing except that somethings goes wrong) and running sndconfig again. Can anybody tell me what I should do to make the sound work allways ? Thanks very much Joris __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
