on Tue, 22 Jun 2004 02:44:12PM -0400, Chris Metzler insinuated: > On Tue, 22 Jun 2004 13:56:46 -0400 > Nori Heikkinen <[EMAIL PROTECTED]> wrote: > > > > hey all, > > > > after a reboot, my sound has disappeared. music123 tells me > > > > Error: Cannot open device oss. > > > > so i look to see if I've got the apporpriate modules in my kernel > > (which I should have; this never _used_to be a problem!), and, as far > > as I can tell, I don't. I only have: > > > > Module Size Used by Not tainted > > serial 42436 0 (autoclean) > > vfat 9548 0 (unused) > > fat 29848 0 [vfat] > > > > I need at least "sound" and the module for my soundcard, yes? > > If you're running OSS (which it looks like you are),
looks like I am, yeah. How would I tell for sure?
> you need soundcore, sound, and es1371 (and maybe ac97_codec, dunno,
> depends on your card).
okay, great.
> If you're running ALSA, you need soundcore + the relevant ALSA
> modules. soundcore is common to both OSS and ALSA.
now, this is the weird part -- i can't find soundcore, at least not
for my kernel ... see below.
> > es1371
> > (which is what I think I need for my Ensoniq) is in /etc/modules, but
> > it's not getting loaded; there's nothing i can see in dmesg,
> > /var/log/messages, or /var/log/syslog that's relevant.
>
> Create a file in /etc/default called "bootlogd". Edit
> /etc/default/bootlogd so that it says:
>
> # Run bootlogd at startup ?
> BOOTLOGD_ENABLE=Yes
>
> You will then get files in /var/log with names like boot, boot.0,
> etc.; these will contain logs of what the /etc/init.d scripts
> do during the boot process. The actions of those scripts aren't
> normally logged in dmesg.
aHA! this is super useful; thanks. i'll do this as soon as I'm home.
> > So i try to modprobe it in by hand, and get the following output:
> >
> > /lib/modules/2.4.20+nori-orange/kernel/drivers/sound/es1371.o:
> > init_module: No such device Hint: insmod errors can be caused by
> > incorrect module parameters, including invalid IO or IRQ parameters.
> > You may find more information in syslog or the output from dmesg
> > /lib/modules/2.4.20+nori-orange/kernel/drivers/sound/es1371.o: insmod
> > /lib/modules/2.4.20+nori-orange/kernel/drivers/sound/es1371.o
> > failed/lib/modules/2.4.20+nori-orange/kernel/drivers/sound/es1371.o:
> > insmod es1371 failed
> >
> > No such device? What device? I have all the /dev/dsps:
> >
> > crw-rw---- 1 root audio 14, 3 Jun 22 00:53 /dev/dsp
> > crw-rw---- 1 root audio 14, 3 Apr 14 2001 /dev/dsp0
> > crw-rw---- 1 root audio 14, 19 Jun 22 00:53 /dev/dsp1
> > crw-rw---- 1 root audio 14, 35 Jun 22 00:53 /dev/dsp2
> > crw-rw---- 1 root audio 14, 51 Jun 22 00:53 /dev/dsp3
>
> Try modprobing soundcore first, then sound, *then* es1371. Yes,
> modprobe should take care of those dependencies; but you might learn
> something from any messages that occur earlier, dunno.
hm. well, as mentioned above, i can't find it. a `locate es1371 |
grep `uname -r`` returns:
/lib/modules/2.4.20+nori-orange/kernel/drivers/sound/es1371.o
/lib/modules/2.4.20+nori-orange_15652/kernel/drivers/sound/es1371.o
(yes, i rolled this one myself)
but, the same thing for "soundcore" returns nothing. in fact, the
only soundcore modules i have are under different kernels:
/lib/modules/2.4.18-386_199/kernel/drivers/sound/soundcore.o
/lib/modules/2.4.4/kernel/drivers/sound/soundcore.o
there's a "sound_core" under a bunch of directories in
/usr/src/kernel-source-2.4.20, but nothing else similar.
Does this mean that somehow, in the building of my kernel (which, I
should add, I've been using for at least a year without any problem),
I left out the crucial module "soundcore", and will now need to go
back and reroll it (or just grab a kernel package) with it in?
> What does lspci -vv show for your soundcard?
00:0f.0 Multimedia audio controller: Ensoniq: Unknown device 0371 (rev 09)
Subsystem: Ensoniq: Unknown device 0371
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 32 (3000ns min, 32000ns max)
Interrupt: pin A routed to IRQ 12
Region 0: I/O ports at e400 [size=64]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
i'm not sure how relevant any of that is to this except for telling me
what kind of module I want to look for ... what else should one get
out of it?
thanks a ton,
</nori>
--
.~. nori @ sccs.swarthmore.edu
/V\ http://www.sccs.swarthmore.edu/~nori
// \\ @ maenad.net
/( )\ www.maenad.net/jnl
^`~'^
++ Sponsor me as I run my SECOND marathon for AIDS: ++
++ http://www.aidsmarathon.com/participant.asp?runner=DC-2844 ++
pgpQ7ItMECZXf.pgp
Description: PGP signature
