Re: ALSA problems sarge 2.4.25 (trying 2.6.3 compile
Well
I will try this, however this is the bin package, and I don't think it
is loading alsa modules?
As well, in alsaconfig what does the following do
Configuring snd-ens1370 .
Do you want to mod /etc/modprobe.d/sound?
I answered yes
and I am still getting
Starting ALSA (version 1.0.2c): ens1370.
Restoring ALSA mixer settings ... failed:
You may want to run 'alsactl restore' manually to view any
errors.
Setting default volume
Well I am trying another recompile on the kernel now
* Ralph Crongeyer (ralph@crongeyer.com) wrote:
> Run dpkg-reconfigure alsa-base. And then only select the sound card module you
> want. Then run run alsaconf again.
>
> Ralph
>
> On Tuesday 13 April 2004 08:13 am, lebbatdot@cogeco.ca wrote:
> > problems)
> > Reply-To:
> > In-Reply-To: <[🔎] 20040406131912.GA7756@lebbalot>
> >
> > Well as I have stated I downloaded the 2.6.3 kernel, both bin and
> > source. The bin worked fine and came up no problem. The sound did not
> > work however.
> > I had read somewhere to compile ALSA in with the kernel, so off we went.
> > I am now having trouble getting the root partition to load, suspecting
> > this was ext3 not built in I made sure it was, same problem, any ideas
> > anyone?
> >
> > Back to the ALSA problem, but looking at the bin kernel fro 2.6.3 as it
> > loads . The sound blaster card seems to be recognized by the kernel
> >
> > snip
> > es1370: version v0.38 time 23:28:15 Feb 20 2004
> > es1370: found adapter at io 0x5000 irq 9
> > es1370: features: joystick on, line in, mic impedance 0
> >
> >
> > And when I run alsaconf, it claims to have configured the es1370
> > from dmesg
> >
> > snip
> > Following card(s) are found on your system. .
> > ens1370 Ensoniq
> > ES1370 [AudioPCI] (rev01)
> > snip
> >
> > snip
> > Running update-modules...
> > Loading driver...
> > Starting ALSA (version 1.0.2c): cs46xx ens1370 ens1370.
> > Restoring ALSA mixer settings ... failed:
> > You may want to run 'alsactl restore' manually to view any
> > errors.
> > Setting default volumes...
> > snip
> >
> > So it thinks the cs drivers are still there?
> >
> >
> >
> >
> >
> > When I then run the aadebug it cannot find any sound cards
> >
> > what files do I need to clean out?
> > Anyother places to lok in the logs?
> >
> > Thanks
> > Brian
> >
> > * lebbatdot@cogeco.ca (lebbatdot@cogeco.ca) wrote:
> > > ALl
> > > I have been trying to get ALSA working on my admitadly old IBM 300PL for
> > > the last while. Extensive Googling and several kernel recompiles later
> > > I think I am in reverse!
> > > I am running sarge kernel version 2.4.25
> > > Here is the output of aadebug from the ALSA website
> > >
> > > sarge:~# ./aadebug
> > > ALSA Audio Debug v0.0.7 - Tue Apr 6 09:40:04 EDT 2004
> > > http://alsa.opensrc.org/?aadebug
> > >
> > > Kernel ----------------------------------------------------
> > > Linux sarge 2.4.25alsa3 #1 Mon Apr 5 22:57:41 EDT 2004 i586 GNU/Linux
> > >
> > > Loaded Modules --------------------------------------------
> > > snd 34276 0
> > >
> > > Modules Conf ----------------------------------------------
> > > alias char-major-116 snd
> > > alias char-major-14 soundcore
> > > options snd major=116 cards_limit=4
> > > alias sound-service-0-0 snd-mixer-oss
> > > alias sound-service-0-1 snd-seq-oss
> > > alias sound-service-0-3 snd-pcm-oss
> > > alias sound-service-0-8 snd-seq-oss
> > > alias sound-service-0-12 snd-pcm-oss
> > > alias /dev/dsp* snd-pcm-oss
> > > alias snd-card-0 snd-cs46xx
> > > alias snd-card-1 snd-ens1370
> > > alias snd-slot-0 snd-card-0
> > > alias sound-slot-0 snd-slot-0
> > > alias snd-slot-1 snd-card-1
> > > alias sound-slot-1 snd-slot-1
> > >
> > > Proc Asound -----------------------------------------------
> > > Advanced Linux Sound Architecture Driver Version 1.0.3.
> > > Compiled on Apr 6 2004 for kernel 2.4.25alsa3 with versioned symbols.
> > > --- no soundcards ---
> > > cat: /proc/asound/hwdep: No such file or directory
> > > cat: /proc/asound/pcm: No such file or directory
> > >
> > > Dev Snd ---------------------------------------------------
> > > controlC0 hwC1D2 midiC0D0 midiC1D2 midiC2D4 midiC3D6 pcmC0D3p
> > > pcmC1D0p pcmC1D5p pcmC2D2p pcmC2D7p pcmC3D4p
> > > controlC1 hwC1D3 midiC0D1 midiC1D3 midiC2D5 midiC3D7 pcmC0D4c
> > > pcmC1D1c pcmC1D6c pcmC2D3c pcmC3D0c pcmC3D5c
> > > controlC2 hwC2D0 midiC0D2 midiC1D4 midiC2D6 pcmC0D0 pcmC0D4p
> > > pcmC1D1p pcmC1D6p pcmC2D3p pcmC3D0p pcmC3D5p
> > > controlC3 hwC2D1 midiC0D3 midiC1D5 midiC2D7 pcmC0D0c pcmC0D5c
> > > pcmC1D2c pcmC1D7c pcmC2D4c pcmC3D1c pcmC3D6c
> > > hwC0D0 hwC2D2 midiC0D4 midiC1D6 midiC3D0 pcmC0D0p pcmC0D5p
> > > pcmC1D2p pcmC1D7p pcmC2D4p pcmC3D1p pcmC3D6p
> > > hwC0D1 hwC2D3 midiC0D5 midiC1D7 midiC3D1 pcmC0D1c pcmC0D6c
> > > pcmC1D3c pcmC2D0c pcmC2D5c pcmC3D2c pcmC3D7c
> > > hwC0D2 hwC3D0 midiC0D6 midiC2D0 midiC3D2 pcmC0D1p pcmC0D6p
> > > pcmC1D3p pcmC2D0p pcmC2D5p pcmC3D2p pcmC3D7p
> > > hwC0D3 hwC3D1 midiC0D7 midiC2D1 midiC3D3 pcmC0D2c pcmC0D7c
> > > pcmC1D4c pcmC2D1c pcmC2D6c pcmC3D3c seq
> > > hwC1D0 hwC3D2 midiC1D0 midiC2D2 midiC3D4 pcmC0D2p pcmC0D7p
> > > pcmC1D4p pcmC2D1p pcmC2D6p pcmC3D3p timer
> > > hwC1D1 hwC3D3 midiC1D1 midiC2D3 midiC3D5 pcmC0D3c pcmC1D0c
> > > pcmC1D5c pcmC2D2c pcmC2D7c pcmC3D4c
> > >
> > > CPU -------------------------------------------------------
> > > model name : Pentium MMX
> > > cpu MHz : 199.435
> > >
> > > RAM -------------------------------------------------------
> > > MemTotal: 62080 kB
> > > SwapTotal: 243892 kB
> > >
> > > Hardware --------------------------------------------------
> > > 00:00.0 Host bridge: Intel Corp. 430HX - 82439HX TXC [Triton II] (rev
> > > 03)
> > > 00:0d.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] (rev 01)
> > >
> > >
> > >
> > > A little histoy
> > >
> > > I tried to get the onboard CS chip working, the kernel recognised it and
> > > all seemed well, but no sound.
> > >
> > > I then installed a cheap soundblaster card
> > >
> > > now when I try a dpkg -i on the alsa deb I get
> > >
> > > sarge:/usr/src# dpkg -D2000 -i
> > > alsa-modules-2.4.25alsa3_1.0.3-1+custom3_i386.deb
> > > (Reading database ... 37622 files and directories currently installed.)
> > > Preparing to replace alsa-modules-2.4.25alsa3 1.0.3-1+custom3 (using
> > > alsa-modules-2.4.25alsa3_1.0.3-1+custom3_i386.deb) ...
> > > Unpacking replacement alsa-modules-2.4.25alsa3 ...
> > > D002000: process_archive info this pkg
> > > D002000: process_archive info this pkg
> > > D002000: process_archive info this pkg
> > > D002000: process_archive info this pkg
> > > Setting up alsa-modules-2.4.25alsa3 (1.0.3-1+custom3) ...
> > > Configuration file for ALSA 1.0 exists.
> > > Attempting to start.
> > >
> > > Storing ALSA mixer settings ... failed
> > > Shutting down ALSA (version 1.0.3): done.
> > > Starting ALSA (version 1.0.3): cs46xx-failed ens1370-failed failed
> > >
> > > Note the lack of information?
> > >
> > > The log traces are similarily not very verbose
> > >
> > > ANy ideas on what to try next?
> > >
> > >
> > > Help appreciated
> > >
> > > Brian
> > >
> > >
> > > --
> > > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> > > with a subject of "unsubscribe". Trouble? Contact
> > > listmaster@lists.debian.org
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: