Hmmmmm. I've never encountered a sblive, they are pci pnp right? Can I see the output of uname -a, /proc/pci and /proc/sound /proc/devices output? I don't see anything out of the ordinary in these files.
--mike On 08 Aug 2001 12:16:37 -0400, Steve Gran wrote: > > On Wed, 08 Aug 2001 11:01:32 Michael Heldebrant wrote: > > What type of soundcard do you have? > > please also show /proc/modules /proc/interrupts /proc/dma and > > /etc/modules.conf > > > > I have a soundblaster live card, which has up to now worked just fine. The > support for it is compiled directly into the kernel, as is I think just > about everything else. Here's the output: > /proc/modules: > <blank> > > /proc/interrupts: > CPU0 > 0: 4744298 XT-PIC timer > 1: 9160 XT-PIC keyboard > 2: 0 XT-PIC cascade > 4: 54317 XT-PIC serial > 5: 0 XT-PIC usb-uhci, usb-uhci > 10: 184236 XT-PIC eth0 > 11: 34 XT-PIC aic7xxx > 12: 81717 XT-PIC EMU10K1 > 14: 63283 XT-PIC ide0 > 15: 332 XT-PIC ide1 > NMI: 0 > > /proc/dma: > 4: cascade > > /etc/modules.conf: > > ### This file is automatically generated by update-modules > # > # Please do not edit this file directly. If you want to change or add > # anything please take a look at the files in /etc/modutils and read > # the manpage for update-modules. > # > ### update-modules: start processing /etc/modutils/0keep > # DO NOT MODIFY THIS FILE! > # This file is not marked as conffile to make sure if you upgrade modutils > # it will be restored in case some modifications have been made. > # > # The keep command is necessary to prevent insmod and friends from ignoring > # the builtin defaults of a path-statement is encountered. Until all other > # packages use the new `add path'-statement this keep-statement is > essential > # to keep your system working > keep > > ### update-modules: end processing /etc/modutils/0keep > > ### update-modules: start processing /etc/modutils/actions > # Special actions that are needed for some modules > > # The BTTV module does not load the tuner module automatically, > # so do that in here > post-install bttv insmod tuner > post-remove bttv rmmod tuner > > > ### update-modules: end processing /etc/modutils/actions > > ### update-modules: start processing /etc/modutils/aliases > # Aliases to tell insmod/modprobe which modules to use > > # Uncomment the network protocols you don't want loaded: > # alias net-pf-1 off # Unix > # alias net-pf-2 off # IPv4 > # alias net-pf-3 off # Amateur Radio AX.25 > # alias net-pf-4 off # IPX > # alias net-pf-5 off # DDP / appletalk > # alias net-pf-6 off # Amateur Radio NET/ROM > # alias net-pf-9 off # X.25 > # alias net-pf-10 off # IPv6 > # alias net-pf-11 off # ROSE / Amateur Radio X.25 PLP > # alias net-pf-19 off # Acorn Econet > > alias char-major-10-175 agpgart > alias char-major-10-200 tun > alias char-major-81 bttv > alias char-major-108 ppp_generic > alias /dev/ppp ppp_generic > alias tty-ldisc-3 ppp_async > alias tty-ldisc-14 ppp_synctty > alias ppp-compress-21 bsd_comp > alias ppp-compress-24 ppp_deflate > alias ppp-compress-26 ppp_deflate > > # Crypto modules (see http://www.kerneli.org/) > alias loop-xfer-gen-0 loop_gen > alias loop-xfer-3 loop_fish2 > alias loop-xfer-gen-10 loop_gen > alias cipher-2 des > alias cipher-3 fish2 > alias cipher-4 blowfish > alias cipher-6 idea > alias cipher-7 serp6f > alias cipher-8 mars6 > alias cipher-11 rc62 > alias cipher-15 dfc2 > alias cipher-16 rijndael > alias cipher-17 rc5 > > > ### update-modules: end processing /etc/modutils/aliases > > ### update-modules: start processing /etc/modutils/paths > # This file contains a list of paths that modprobe should scan, > # beside the once that are compiled into the modutils tools > # themselves. > > > ### update-modules: end processing /etc/modutils/paths > > ### update-modules: start processing /etc/modutils/ppp > alias /dev/ppp ppp_generic > alias char-major-108 ppp_generic > alias tty-ldisc-3 ppp_async > alias tty-ldisc-14 ppp_synctty > alias ppp-compress-21 bsd_comp > alias ppp-compress-24 ppp_deflate > alias ppp-compress-26 ppp_deflate > > ### update-modules: end processing /etc/modutils/ppp > > ### update-modules: start processing /etc/modutils/setserial > # > # This is what I wanted to do, but logger is in /usr/bin, which isn't > loaded > # when the module is first loaded into the kernel at boot time! > # > #post-install serial /etc/init.d/setserial start | logger -p daemon.info -t > "setserial-module reload" > #pre-remove serial /etc/init.d/setserial stop | logger -p daemon.info -t > "setserial-module uload" > post-install serial /etc/init.d/setserial modload > /dev/null 2> /dev/null > pre-remove serial /etc/init.d/setserial modsave > /dev/null 2> /dev/null > > ### update-modules: end processing /etc/modutils/setserial > > ### update-modules: start processing /etc/modutils/arch/i386 > alias parport_lowlevel parport_pc > alias char-major-10-144 nvram > alias binfmt-0064 binfmt_aout > alias char-major-10-135 rtc > > ### update-modules: end processing /etc/modutils/arch/i386 > > Thanks again, sorry for the length of everything. > > Steve > > > --mike > > On 07 Aug 2001 22:50:26 -0400, Steve Gran wrote: > > > > > > On Tue, 07 Aug 2001 21:29:22 Eric G. Miller wrote: > > > > On Tue, Aug 07, 2001 at 06:58:41PM -0400, Steve Gran wrote: > > > > > Hello all, > > > > > I've just experienced my first ever system crashes. They were all > > > > within > > > > > the last several days (after an upgrade that included an upgrade of > > > > XMMS), > > > > > and they all happened shortly after opening XMMS. There were only > > > > three > > > > > total, and it's not consistent, but XMMS & X are the only > > consistent > > > > > factors. I saw that someone else was having some problems with > > system > > > > > hangs, and so I regenerated my /etc/X11/XF86Config-4 on the off > > chance > > > > that > > > > > that was it, but it continued. Anybody else having any problems > > with > > > > this? > > > > > I took a look at the bug reports, and saw some related problems, > > but > > > > > nothing that seemed to be this bad - I'm getting total lockups (no > > > > keyboard > > > > > response, even). > > > > > I'm not sure how to troubleshoot - I've looked through the various > > > > logfiles > > > > > in /var/, and it doesn't look like there are any obvious error > > > > messages, > > > > > although I'm kind of a newbie at this. Any responses or > > suggestions > > > > would > > > > > be appreciated. I've only been running Debian for about six > > months, > > > > but > > > > > thisa is the first hang, and (although it was in a sick way nice to > > > > know > > > > > that nothing is perfect) fairly upsetting. In the meantime, I'm > > not > > > > using > > > > > XMMS, to see if my box will hang whithout it. > > > > > Thanks in advance, > > > > > Steve > > > > > > > > Since you say there is nothing in the logs, is doesn't sound like the > > > > kernel crashed. Perhaps just X got frozen? Ctrl-Alt-Backspace is > > > > usually set to kill X. > > > > > > > > Helps if you give info about the type of system and kernel version. > > > > > > > > > > > > Sorry about that - I realized I forgot to put all that information in > > after > > > I sent it off. I'm running Woody on a 2.4.7 kernel. The box is built > > > around a P III chip, with an assortment of hard drives, cd drives, > > SCSI, > > > USB, and so forth. Relevant version numbers: > > > xserver-common 4.0.3-4 > > > xserver-xfree86 4.0.3-4 > > > libesd0 0.2.22-6 > > > libc6 2.2.3-5 > > > xmms 1.2.5-1.1 > > > Not sure if you'll need anything else. Ctrl-Alt-Backspace would > > ordinarily > > > work just fine, but the keyboard is also locked out - nothing works. > > > > > > Thanks again, > > > Steve > > > > > > > > > -- > > > 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] > > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
