On Sat,27.Jun.09, 11:50:01, Paul E Condon wrote:
> Since you are intending to patch the last bullet point in the release
> note, I suggest that you also recast the other bullet points where you
> suggest specific commands to type and the specific results to be
> expected.
I filed #534797, becau
On 2009-06-27_11:50:02, Andrei Popescu wrote:
> On Fri,26.Jun.09, 21:24:42, Paul E Condon wrote:
> >
> > * make sure the sound channel levels are up and unmuted (using
> > alsamixer),
> > I not sure. alsamixer display did not look familiar and it was not at all
> > clear what the
> > iconic
On Fri,26.Jun.09, 21:24:42, Paul E Condon wrote:
>
> * make sure the sound channel levels are up and unmuted (using
> alsamixer),
> I not sure. alsamixer display did not look familiar and it was not at all
> clear what the
> iconic display was indicating. Further I wasn't able to change the
I have a computer on which I did a clean new install of Lenny about a month
ago. Lots of problems and I am just now confronting fact that there is no
sound. (I got Flash working earlier today, and with that knew, for sure: no
sount)
There is some advice on possible problems in Lenny in the Releas
Hello everyone. My soundcard is a soundblaster CT3600. I can't
get it to work.
I am getting the following error when I try to load modules to use it
as follows:
spoke:/proc# modprobe sb io=0x220 irq=10 dma=1 dma16=5 mpu_io=0x330
Soundblaster audio driver Copyright (C) by Hannu Savolainen 1
I think that there is one step missing, and that is
dpkg -i . After you build the kernel,
you have to install it.
Don
--- Andrew Dixon <[EMAIL PROTECTED]> wrote:
> Kent West wrote:
> >
> > Once you exit out of the "make menuconfig" step,
> the "Debian way" of
> > compiling a kernel is next.
> >
Kent West wrote:
>
> Once you exit out of the "make menuconfig" step, the "Debian way" of
> compiling a kernel is next.
>
> "make-kpkg kernel_image" should be the only thing you have to do. It'll
> compile the kernel and modules, put everything where it needs to be,
> reconfigure lilo.conf to use
Mario Vukelic wrote:
On Tue, 2002-02-05 at 16:36, Kent West wrote:
"make-kpkg kernel_image" should be the only thing you have to do. It'll
compile the kernel and modules, put everything where it needs to be,
reconfigure lilo.conf to use the new kernel, and ask if you want to run
lilo to mak
On Tue, 2002-02-05 at 16:36, Kent West wrote:
> "make-kpkg kernel_image" should be the only thing you have to do. It'll
> compile the kernel and modules, put everything where it needs to be,
> reconfigure lilo.conf to use the new kernel, and ask if you want to run
> lilo to make the changes to
On Tue, Feb 05, 2002 at 10:33:31AM -0400, Liam Black wrote:
> I've just set up my first-ever Debian box (Potato, 2.2.19). After ironing
> out a few minor problems everything went fine. I'm now at the point where I
> want to have my soundcard working -- it's an ISA CMI8330 based. I have been
> tryin
Andrew Dixon wrote:
Liam Black wrote:
But what do I do now? There is no /usr/src/linux directory on my machine,
and I've never dealt with reconfiguring/recompiling the kernel (which seems
to be something I have to do?)
Yup, if you want sound you'll need to recompile a kernel.
Not necess
On Tue, 2002-02-05 at 16:05, Andrew Dixon wrote:
> Liam Black wrote:
>
> > But what do I do now? There is no /usr/src/linux directory on my machine,
> > and I've never dealt with reconfiguring/recompiling the kernel (which seems
> > to be something I have to do?)
>
> Yup, if you want sound you'll
Liam Black wrote:
> But what do I do now? There is no /usr/src/linux directory on my machine,
> and I've never dealt with reconfiguring/recompiling the kernel (which seems
> to be something I have to do?)
Yup, if you want sound you'll need to recompile a kernel.
>
> Is there an "easy" way to do
Hi,
I've just set up my first-ever Debian box (Potato, 2.2.19). After ironing
out a few minor problems everything went fine. I'm now at the point where I
want to have my soundcard working -- it's an ISA CMI8330 based. I have been
trying to install it, but no one source seems to have all of the
inf
> "S" == S Salman Ahmed <[EMAIL PROTECTED]> writes:
> "jsja" == john s jacobs anderson <[EMAIL PROTECTED]> writes:
jsja> Following up for the list archives: The es1371 driver in the
jsja> current kernel did not work for this card; Creative has
jsja> apparently revved the codec, or t
> "Chanop" == Chanop Silpa-Anan <[EMAIL PROTECTED]> writes:
Chanop> Once upon a time, I heard john s anderson said
>> I'm currently trying to get my SoundBlaster PCI128 card to work,
>> and I'm on my seventh kernel compile, and I'm starting to pull my
>> hair out. The damn thing won't
Once upon a time, I heard john s anderson said
> I've recently switched to Debian (from LinuxPPC (home) and RedHat(work)),
> and I'm enjoying it quite a bit. I installed from the O'Reilly disk, and
> then did an update to frozen (I think I even got it mostly correct!).
Cheers,
>
> I'm currently t
Greetings.
I've recently switched to Debian (from LinuxPPC (home) and RedHat(work)),
and I'm enjoying it quite a bit. I installed from the O'Reilly disk, and
then did an update to frozen (I think I even got it mostly correct!).
I'm currently trying to get my SoundBlaster PCI128 card to work, and
I am going crazy trying to get my sound card to be recognized!!!
I am using slink and pulled the latest kernel sources off of the 2
official
cd-roms. I used the pnpdump tool to determine the base address, IRQ's,
etc of my card (a 3 year old Ensoniq Soundscape VIVO). I put these
into a /etc/isapnp.
>Resent-Cc: recipient list not shown: ;
>X-Envelope-Sender: [EMAIL PROTECTED]
>Date: Fri, 18 Jun 1999 15:02:02 +0200
>From: Jean-Philippe Gu?rard <[EMAIL PROTECTED]>
>Content-Type: text/plain; charset=iso-8859-1
>Resent-From: debian-user@lists.debian.org
>X-Mailing-List: archive/latest/53589
>X-Lo
On Fri, Jun 18, 1999 at 11:08:45AM +0100, Frankie wrote:
> "Andrew C. Gronosky" wrote:
>
> > Hi,
> >
> > My new PC has a Creative AWE64 card and I've been pulling my hair out
> > trying to configure it. :) I am running the 2.2.1 kernel with all the
> > correct modules according to the kernel docu
"Andrew C. Gronosky" wrote:
> Hi,
>
> My new PC has a Creative AWE64 card and I've been pulling my hair out
> trying to configure it. :) I am running the 2.2.1 kernel with all the
> correct modules according to the kernel documentation. The card is PnP
> and I believe I have it configured proper
Hi,
My new PC has a Creative AWE64 card and I've been pulling my hair out
trying to configure it. :) I am running the 2.2.1 kernel with all the
correct modules according to the kernel documentation. The card is PnP
and I believe I have it configured properly with isapnp.
/lib/modules/2.2.1/misc
> debian:~/sounds/sndkit/dsp$ cat /usr/X11R6/lib/tkdesk/sound/metal.au
> >/dev/audio
> bash: /dev/audio: Cannot allocate memory
>
> I've configured for a 4K (4096) buffer. When I run dmesg, here's
>what pops up:
>
> Sound error: Couldn't allocate DMA buffer
[ ... ]
> /proc/me
Hi, folks
I have sucessfully re-built my kernel to add support for my
Soundblaster Pro card. (An interesting side-effect is that now
my backspace key works!! Go figure..) I was having trouble
getting CD's to play until I changed the permissions on /dev/cdrom
On Wed, Aug 12, 1998 at 03:33:59PM +0200, [EMAIL PROTECTED] wrote:
>
>
> On Wed, 12 Aug 1998, XRDLAB wrote:
>
> > >Didn't you read the documentation? There is no SB 16 compatible card on the
> > >market. ..
> > >
> > Yes, I read the documentation and it said that some cards might work.
>
On Wed, 12 Aug 1998, XRDLAB wrote:
> >Didn't you read the documentation? There is no SB 16 compatible card on the
> >market. ..
> >
> Yes, I read the documentation and it said that some cards might work.
> That is why I mentioned that the card "claims" to be compatible.
The compatibilit
Hello,
On Tue, 11 Aug 1998, Marcus Brinkmann wrote:
>
>> My sound card is Aztech Galaxy (claims to be compatible
>> with SoundBlaster 16, non pnp).
>
>Didn't you read the documentation? There is no SB 16 compatible card on the
>market. ..
>
Yes, I read the documentation and it said that s
Hello,
On Tue, Aug 11, 1998 at 04:51:04PM +0530, XRDLAB wrote:
> I am currently running Debian bo and wanted to compile sound support.
>
> My sound card is Aztech Galaxy (claims to be compatible
> with SoundBlaster 16, non pnp).
Didn't you read the documentation? There is no SB 16 compatible
I am currently running Debian bo and wanted to compile sound support.
My sound card is Aztech Galaxy (claims to be compatible
with SoundBlaster 16, non pnp). The card works fine under dos with the
following settings:
SB 16io=0x220, irq=10, dma=1
MPU-401 io=0x330, irq=2
In
On Sun, 19 Jul 1998, Ian Keith Setford wrote:
> Yo-
>
> > I can't get my sound to work. Everything that uses sound says it
> can't
> > open the sound device. Bplay gave me the best lead with this:
> > bplay: /dev/dsp: Device not configured
> >
> > My question is, how do I configure /dev/dsp?
Yo-
> I can't get my sound to work. Everything that uses sound says it
can't
> open the sound device. Bplay gave me the best lead with this:
> bplay: /dev/dsp: Device not configured
>
> My question is, how do I configure /dev/dsp? MAKEDEV doesn't appear to do
> anything.
Do you have /dev/dsp s
On Sun, 19 Jul 1998, Robert Henry Rati wrote:
> bplay: /dev/dsp: Device not configured
>
> My question is, how do I configure /dev/dsp? MAKEDEV doesn't appear to do
> anything.
you need to compile sound support into your kernel, when yu do that build
in the support for /dev/dsp .
make sure you k
I can't get my sound to work. Everything that uses sound says it can't
open the sound device. Bplay gave me the best lead with this:
bplay: /dev/dsp: Device not configured
My question is, how do I configure /dev/dsp? MAKEDEV doesn't appear to do
anything.
|-
34 matches
Mail list logo
