Re: [newbie] InteractiveBastille killed my sound!
On Mon, 16 Jul 2001 00:57, civileme wrote: On Sunday 15 July 2001 03:54, Sridhar Dhanapalan wrote: On Sun, 15 Jul 2001 05:17, civileme wrote: On Saturday 14 July 2001 09:03, Sridhar Dhanapalan wrote: Hey everyone, I ran InteractiveBastille and configured my system security settings. After I rebooted and returned to GNOME, I found that my sound no longer works. The Esound daemon (ESD) is running, but nothing comes out of my speakers. My mixer settings are fine, and sound still works perfectly in KDE, which uses the ARTS sound server. I can also run console apps like mpg123 with no trouble. What could be wrong? Perhaps I accidentally blocked a port that Esound needs? Or the arts _server_ Yes indeed. Civileme Thanks for the response. I'm sorry, Civileme, but I don't quite understand what you mean here (Or the arts _server_). I don't have ARTS running at all when I'm using GNOME (I checked with a ps aux). When I run GNOME, it loads esd -nobeeps -as 30 to initialise sound. Even though this is loaded, sound doesn't work. If I go to the GNOME Control Centre sound settings, it turns off sound. I have tried turning it back on again both via the Control Centre and by directly editing the file /home/user/.gnome/sound/system (changing false statements to true). As Tom Brinkman suggested, I have tried executing (as root) chmod 666 /dev/dsp* /dev/audio* /dev/mixer* /dev/midi* /dev/sequencer*. Now when I try to run esd manually (after killing other instances of it) I will get the startup beeps (as they are called when I type esd --help) that indicate that it is working (I didn't get them before), but sound in GNOME still doesn't work (e.g. XMMS complains when I try to play an MP3). Thanks for any help. OK that could be gmix... go to another desktop and use the mixer settings from it, then return to GNOME and keep hands off the gmix. I logged off GNOME and loaded IceWM. When I ran gmix it appeared with my preset mixer settings. I changed things a bit (just in case) and then logged off. GNOME was still soundless upon my return. I tried going to KDE and doing the same as I did in IceWM -- no luck. I even tried changing the volume with aumix from the console then logging into GNOME. Nothing. GNOME uses CORBA and that means sockets, so it is conceivable that the Bastille firewall is blocking something internally. You would need to check the rules and make sure that things with origin at 127.0.0.1 are never blocked. (the internet routers will not relay such an address, so you are still safe from exploits.) I checked my firewall rules and I noticed that lo (local loopback) was running as a trusted interface. There is nothing blocking either lo or 127.0.0.1 (or any of its aliases). I then fully disabled my firewall (so that it wouldn't start at bootup) and rebooted. GNOME was the same: no sound. Loading esd on different ports didn't help either (I didn't think it would, but I'm getting desperate here :-) ). By the looks of it, the problem is with a different component of Bastille -- not the firewall. I am quite certain that it is *something* (I just don't know what) in Bastille, since this is the second time I've had this problem (a MandrakeFreq install fixed it the first time). In case you're wondering (I forgot to mention before), I am using Bastille Linux 1.2.0 from http://www.bastille-linux.org on Mandrake 8.0 (upgraded to Freq2). Any more ideas to help an increasingly desperate user? Cheers :-) -- Sridhar Dhanapalan. There are two major products that come from Berkeley: LSD and UNIX. We don't believe this to be a coincidence. -- Jeremy S. Anderson
Re: [newbie] InteractiveBastille killed my sound!
On Tue, 17 Jul 2001 20:54, etharp wrote: this might be beating a dead horse, but is the mixer set to a reasonable level? I have the same sound card, and while it appeared everything was getting setup, the vol. was so low that ! could not hear sound. I kept failing sndconfig since i could not here the sounds. That was one of the first things I checked. The mixer levels are fine. The problem is that sound works beautifully in everything except the GNOME/Sawfish environment itself. By this I mean that Sawfish sounds (e.g. when a window closes) and GNOME sounds (e.g. sounds associated to the panel) do not work. Esound is running as always. If I run another app, like Downloader for X, aviplay (part of avifile) or Xmovie, I can get sound as usual. Some other apps, like XMMS, don't work in GNOME. Sound works perfectly in KDE, including programmes that didn't work in GNOME like XMMS. As I said before, this is the second time this has happened, both times occurring after I configured my system with InteractiveBastille (version 1.2.0). I managed to fix things the first time with a Freq2 install. The firewall component is not the cause, AFAIK. I checked the rules, and there is nothing blocking ports locally. I then fully disabled the firewall, yet the problem persists. I am beginning to think I should just reinstall. I am loathe to do this: it is such a WinDOS solution. I would also lose the extra security provided by InteractiveBastille. I would rather see this problem fixed. That way when somebody else has a similar problem we'll already know the answer. IMHO, this looks like a nasty bug in Bastille that should be fixed, not forgotten about. On Monday 16 July 2001 22:19, Sridhar Dhanapalan wrote: On Tue, 17 Jul 2001 08:00, civileme wrote: BIG SNIP Here's my complete lsmod output: [root@YAMA Data]# lsmod Module Size Used by vmnet 14720 3 vmmon 16880 0 (unused) sb 7136 0 sb_lib 33120 0 [sb] uart401 6224 0 [sb_lib] sound 54256 0 [sb_lib uart401] soundcore 3504 5 [sb_lib sound] af_packet 11280 1 (autoclean) 8139too11696 1 (autoclean) nls_iso8859-1 2848 2 (autoclean) nls_cp850 3584 2 (autoclean) vfat9040 2 (autoclean) fat30720 0 (autoclean) [vfat] supermount 32496 6 (autoclean) ide-scsi7568 0 reiserfs 165760 1 sd_mod 11048 0 (unused) scsi_mod 86036 2 [ide-scsi sd_mod] I see at least 5 entries related to sound -- is that normal? When I type service alsa status I get Sound loaded. The same output occurs when I type service sound status. In the services section of Drakconf (the X version), I noticed that alsa is stopped but set to load on boot, and sound is both running and configured to load on startup. While in GNOME I can get sound in programmes like Downloader for X (nt), xmovie and aviplay (part of avifile, an avi movie player). This is without esound or arts loaded. XMMS refuses to work, though.] OK that sounds like the alsa drivers worked and then the oss drivers got loaded on top. The behavior with XMMS is typical of that. Try stopping alsa at boot (i. e. telling it not to start), and see what happens. I figured you would ask this (since I have read your other responses to sound problems on the list), so as soon as I fired off my above message I went to DrakConf and disabled the alsa service from loading at boot, leaving sound as the only sound-related service that loads at boot. After a reboot, there was no change :-( And if that produces an improvement chkconfig --del alsa and dhange etc/modules.conf to alias the sb driver from oss. Civileme And he backup plan is pnpdump isapnp.conf sndconfig Sndconfig was the first thing I tried when the problem arose. Just in case, I did the pnpdump and tried sndconfig again -- still no luck. Here's the pnpdump output (i.e. the contents of isapnp.conf): # $Id: pnpdump_main.c,v 1.25 2001/01/06 20:45:58 fox Exp $ # Release isapnptools-1.24 # # This is free software, see the sources for details. # This software has NO WARRANTY, use at your OWN RISK # # For details of the output file format, see isapnp.conf(5) # # For latest information and FAQ on isapnp and pnpdump see: # http://www.roestock.demon.co.uk/isapnptools/ # # Compiler flags: -DREALTIME -DHAVE_PROC -DENABLE_PCI -DHAVE_SCHED_SETSCHEDULER -DHAVE_NANOSLEEP -DWANT_TO_VALIDATE # # Trying port address 0273 # Board 1 has serial identifier 8a 03 c3 2a 46 e4 00 8c 0e # (DEBUG) (READPORT 0x0273)
Re: [newbie] InteractiveBastille killed my sound!
this might be beating a dead horse, but is the mixer set to a reasonable level? I have the same sound card, and while it appeared everything was getting setup, the vol. was so low that ! could not hear sound. I kept failing sndconfig since i could not here the sounds. On Monday 16 July 2001 22:19, Sridhar Dhanapalan wrote: On Tue, 17 Jul 2001 08:00, civileme wrote: BIG SNIP Here's my complete lsmod output: [root@YAMA Data]# lsmod Module Size Used by vmnet 14720 3 vmmon 16880 0 (unused) sb 7136 0 sb_lib 33120 0 [sb] uart401 6224 0 [sb_lib] sound 54256 0 [sb_lib uart401] soundcore 3504 5 [sb_lib sound] af_packet 11280 1 (autoclean) 8139too11696 1 (autoclean) nls_iso8859-1 2848 2 (autoclean) nls_cp850 3584 2 (autoclean) vfat9040 2 (autoclean) fat30720 0 (autoclean) [vfat] supermount 32496 6 (autoclean) ide-scsi7568 0 reiserfs 165760 1 sd_mod 11048 0 (unused) scsi_mod 86036 2 [ide-scsi sd_mod] I see at least 5 entries related to sound -- is that normal? When I type service alsa status I get Sound loaded. The same output occurs when I type service sound status. In the services section of Drakconf (the X version), I noticed that alsa is stopped but set to load on boot, and sound is both running and configured to load on startup. While in GNOME I can get sound in programmes like Downloader for X (nt), xmovie and aviplay (part of avifile, an avi movie player). This is without esound or arts loaded. XMMS refuses to work, though.] OK that sounds like the alsa drivers worked and then the oss drivers got loaded on top. The behavior with XMMS is typical of that. Try stopping alsa at boot (i. e. telling it not to start), and see what happens. I figured you would ask this (since I have read your other responses to sound problems on the list), so as soon as I fired off my above message I went to DrakConf and disabled the alsa service from loading at boot, leaving sound as the only sound-related service that loads at boot. After a reboot, there was no change :-( And if that produces an improvement chkconfig --del alsa and dhange etc/modules.conf to alias the sb driver from oss. Civileme And he backup plan is pnpdump isapnp.conf sndconfig Sndconfig was the first thing I tried when the problem arose. Just in case, I did the pnpdump and tried sndconfig again -- still no luck. Here's the pnpdump output (i.e. the contents of isapnp.conf): # $Id: pnpdump_main.c,v 1.25 2001/01/06 20:45:58 fox Exp $ # Release isapnptools-1.24 # # This is free software, see the sources for details. # This software has NO WARRANTY, use at your OWN RISK # # For details of the output file format, see isapnp.conf(5) # # For latest information and FAQ on isapnp and pnpdump see: # http://www.roestock.demon.co.uk/isapnptools/ # # Compiler flags: -DREALTIME -DHAVE_PROC -DENABLE_PCI -DHAVE_SCHED_SETSCHEDULER -DHAVE_NANOSLEEP -DWANT_TO_VALIDATE # # Trying port address 0273 # Board 1 has serial identifier 8a 03 c3 2a 46 e4 00 8c 0e # (DEBUG) (READPORT 0x0273) (ISOLATE PRESERVE) (IDENTIFY *) (VERBOSITY 2) (CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING # Card 1: (serial identifier 8a 03 c3 2a 46 e4 00 8c 0e) # Vendor Id CTL00e4, Serial Number 63121990, checksum 0x8A. # Version 1.0, Vendor version 1.0 # ANSI string --Creative SB AWE64 PnP-- # Vendor defined tag: 73 02 45 20 # # Logical device id CTL0045 # Device supports vendor reserved register @ 0x3a # Device supports vendor reserved register @ 0x3b # Device supports vendor reserved register @ 0x3d # Device supports vendor reserved register @ 0x3e # Device supports vendor reserved register @ 0x3f # # Edit the entries below to uncomment out the configuration required. # Note that only the first value of any range is given, this may be changed if required # Don't forget to uncomment the activate (ACT Y) when happy (CONFIGURE CTL00e4/63121990 (LD 0 # ANSI string --Audio-- # Multiple choice time, choose one only ! # Start dependent functions: priority preferred # IRQ 5. # High true, edge sensitive interrupt (by default) # (INT 0 (IRQ 5 (MODE +E))) # First DMA channel 1. # 8 bit DMA only # Logical device is a bus master # DMA may execute in count by byte mode # DMA may not execute in count by word mode # DMA channel speed in compatible mode # (DMA 0 (CHANNEL 1)) # Next DMA channel 5. # 16 bit DMA only #
Re: [newbie] InteractiveBastille killed my sound!
On Tue, 17 Jul 2001 08:00, civileme wrote: BIG SNIP Here's my complete lsmod output: [root@YAMA Data]# lsmod Module Size Used by vmnet 14720 3 vmmon 16880 0 (unused) sb 7136 0 sb_lib 33120 0 [sb] uart401 6224 0 [sb_lib] sound 54256 0 [sb_lib uart401] soundcore 3504 5 [sb_lib sound] af_packet 11280 1 (autoclean) 8139too11696 1 (autoclean) nls_iso8859-1 2848 2 (autoclean) nls_cp850 3584 2 (autoclean) vfat9040 2 (autoclean) fat30720 0 (autoclean) [vfat] supermount 32496 6 (autoclean) ide-scsi7568 0 reiserfs 165760 1 sd_mod 11048 0 (unused) scsi_mod 86036 2 [ide-scsi sd_mod] I see at least 5 entries related to sound -- is that normal? When I type service alsa status I get Sound loaded. The same output occurs when I type service sound status. In the services section of Drakconf (the X version), I noticed that alsa is stopped but set to load on boot, and sound is both running and configured to load on startup. While in GNOME I can get sound in programmes like Downloader for X (nt), xmovie and aviplay (part of avifile, an avi movie player). This is without esound or arts loaded. XMMS refuses to work, though.] OK that sounds like the alsa drivers worked and then the oss drivers got loaded on top. The behavior with XMMS is typical of that. Try stopping alsa at boot (i. e. telling it not to start), and see what happens. I figured you would ask this (since I have read your other responses to sound problems on the list), so as soon as I fired off my above message I went to DrakConf and disabled the alsa service from loading at boot, leaving sound as the only sound-related service that loads at boot. After a reboot, there was no change :-( And if that produces an improvement chkconfig --del alsa and dhange etc/modules.conf to alias the sb driver from oss. Civileme And he backup plan is pnpdump isapnp.conf sndconfig Sndconfig was the first thing I tried when the problem arose. Just in case, I did the pnpdump and tried sndconfig again -- still no luck. Here's the pnpdump output (i.e. the contents of isapnp.conf): # $Id: pnpdump_main.c,v 1.25 2001/01/06 20:45:58 fox Exp $ # Release isapnptools-1.24 # # This is free software, see the sources for details. # This software has NO WARRANTY, use at your OWN RISK # # For details of the output file format, see isapnp.conf(5) # # For latest information and FAQ on isapnp and pnpdump see: # http://www.roestock.demon.co.uk/isapnptools/ # # Compiler flags: -DREALTIME -DHAVE_PROC -DENABLE_PCI -DHAVE_SCHED_SETSCHEDULER -DHAVE_NANOSLEEP -DWANT_TO_VALIDATE # # Trying port address 0273 # Board 1 has serial identifier 8a 03 c3 2a 46 e4 00 8c 0e # (DEBUG) (READPORT 0x0273) (ISOLATE PRESERVE) (IDENTIFY *) (VERBOSITY 2) (CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING # Card 1: (serial identifier 8a 03 c3 2a 46 e4 00 8c 0e) # Vendor Id CTL00e4, Serial Number 63121990, checksum 0x8A. # Version 1.0, Vendor version 1.0 # ANSI string --Creative SB AWE64 PnP-- # Vendor defined tag: 73 02 45 20 # # Logical device id CTL0045 # Device supports vendor reserved register @ 0x3a # Device supports vendor reserved register @ 0x3b # Device supports vendor reserved register @ 0x3d # Device supports vendor reserved register @ 0x3e # Device supports vendor reserved register @ 0x3f # # Edit the entries below to uncomment out the configuration required. # Note that only the first value of any range is given, this may be changed if required # Don't forget to uncomment the activate (ACT Y) when happy (CONFIGURE CTL00e4/63121990 (LD 0 # ANSI string --Audio-- # Multiple choice time, choose one only ! # Start dependent functions: priority preferred # IRQ 5. # High true, edge sensitive interrupt (by default) # (INT 0 (IRQ 5 (MODE +E))) # First DMA channel 1. # 8 bit DMA only # Logical device is a bus master # DMA may execute in count by byte mode # DMA may not execute in count by word mode # DMA channel speed in compatible mode # (DMA 0 (CHANNEL 1)) # Next DMA channel 5. # 16 bit DMA only # Logical device is not a bus master # DMA may not execute in count by byte mode # DMA may execute in count by word mode # DMA channel speed in compatible mode # (DMA 1 (CHANNEL 5)) # Logical device decodes 16 bit IO address lines # Minimum IO base address 0x0220 # Maximum IO base address 0x0220 # IO base alignment 1 bytes #
Re: [newbie] InteractiveBastille killed my sound!
On Saturday 14 July 2001 04:03 am, Sridhar Dhanapalan wrote: I ran InteractiveBastille and configured my system security settings. After I rebooted and returned to GNOME, I found that my sound no longer works. The Esound daemon (ESD) is running, but nothing comes out of my speakers. My mixer settings are fine, and sound still works perfectly in KDE, which uses the ARTS sound server. I can also run console apps like mpg123 with no trouble. What could be wrong? Perhaps I accidentally blocked a port that Esound needs? I don't really think this is the fix, but it couldn't hurt. as root run: chmod 666 /dev/dsp* /dev/audio* /dev/mixer* /dev/midi* /dev/sequencer* -- Tom Brinkman [EMAIL PROTECTED] Galveston Bay
