At 02:11 PM 4/7/2005 -0500, James Miller wrote:
I'll start the testing responses to this, your most recent, posting, and
move to your previous posting after this one. I wanted to ask about udev
before running the tests in your previous post on the assumption that its
presence might change someth
On Thu, 7 Apr 2005, James Miller wrote:
module line in /etc/modules. I do have the option of swapping Soundman (3)
and Soundblaster (5) IRQ's, I suppose, to see if that makes any difference.
Haven't tried that yet.
Just tried it (made Soundman IRQ 5 and Soundblaster 3 and edited
/etc/modules acc
On Thu, 7 Apr 2005 [EMAIL PROTECTED] wrote:
On Wed, 6 Apr 2005, James Miller wrote:
if that relieves any potential IRQ 3 conflict. Possible IRQ's for the card
are: 2, 3, 5, 7, 10, 11, 12, 15 for "Soundman" and 2, 3, 5, and 7 for
"Sound blaster."
i think you can use interrupt 5 or 9 if there's a w
On Wed, 6 Apr 2005, James Miller wrote:
On Thu, 7 Apr 2005 [EMAIL PROTECTED] wrote:
Can you post your /proc/interrupts here ?
[EMAIL PROTECTED]:~$ cat /proc/interrupts
CPU0
0: 25759543 XT-PIC timer
1: 23960 XT-PIC i8042
2: 0 XT-PIC cascade
I'll start the testing responses to this, your most recent, posting, and
move to your previous posting after this one. I wanted to ask about udev
before running the tests in your previous post on the assumption that its
presence might change something fundamental in testing procedures. The
test
At 12:31 PM 4/7/2005 -0500, James Miller wrote:
[...]
Anyway, I'll try what you've suggested. But one aspect needs some further
comment and clarification, namely:
2. Create the device entries if they are not present. (I was a bit
surprised that they are not present, but if they are not, you are
On Thu, 7 Apr 2005, Ray Olszewski wrote:
bit more systematic than what you've been doing. (I'm seeing some gaps in
your testing, and I can't tell if you really are skipping steps or just being
terse in your reports to us.)
I'd call what I'm doing semi-controlled, semi-informed flailing. I know
s
At 09:09 AM 4/7/2005 -0500, James Miller wrote:
On Wed, 6 Apr 2005, James Miller wrote:
range) or to disable ttyS1 (COM 2 as the BIOS sees it, I believe) and see
if that relieves any potential IRQ 3 conflict.
I tried disabling COM 2 in the BIOS (set it to "off" there). When I look
at dmesg output
On Wed, 6 Apr 2005, James Miller wrote:
range) or to disable ttyS1 (COM 2 as the BIOS sees it, I believe) and see if
that relieves any potential IRQ 3 conflict.
I tried disabling COM 2 in the BIOS (set it to "off" there). When I look
at dmesg output, it does, indeed, appear to be off and is not g
On Wed, 6 Apr 2005, Ray Olszewski wrote:
One thing you don't mention trying is using a different audio device. I
suggest you try directing output to /dev/audio1 or /dev/dsp1 and see if that
improves the result. I don't know how to do that with mp3blaster; with mpg123
you would do
mpg123
On Thu, 7 Apr 2005 [EMAIL PROTECTED] wrote:
Can you post your /proc/interrupts here ?
[EMAIL PROTECTED]:~$ cat /proc/interrupts
CPU0
0: 25759543 XT-PIC timer
1: 23960 XT-PIC i8042
2: 0 XT-PIC cascade
3: 5223 XT-PIC PAS
At 04:13 PM 4/6/2005 -0500, James Miller wrote:
[...]
With sb_irq=XXX (and so forth) in the same line as pas2, I do not get
these sorts of error messages. Just a clean:
Pro Audio Spectrum driver Copyright (C) by Hannu Savolainen 1993-1996
But sound still works very poorly. Very scratchy when I pl
On Wed, 6 Apr 2005, James Miller wrote:
On Thu, 7 Apr 2005 [EMAIL PROTECTED] wrote:
On Wed, 6 Apr 2005, James Miller wrote:
Not totally, no. cat /pro/interrupts shows only PAS16 assigned to IRQ 3.
But dmesg output has ttyS1 using IRQ 3. It's a bit confusing to me. I
assigned it IRQ 3 because prev
On Thu, 7 Apr 2005 [EMAIL PROTECTED] wrote:
On Wed, 6 Apr 2005, James Miller wrote:
Not totally, no. cat /pro/interrupts shows only PAS16 assigned to IRQ 3.
But dmesg output has ttyS1 using IRQ 3. It's a bit confusing to me. I
assigned it IRQ 3 because previously, when checking cat /proc/interrup
On Wed, 6 Apr 2005, James Miller wrote:
On Thu, 7 Apr 2005 [EMAIL PROTECTED] wrote:
On Wed, 6 Apr 2005, James Miller wrote:
Are you sure your soundcard is not sharing interrupts with other device ?
Not totally, no. cat /pro/interrupts shows only PAS16 assigned to IRQ 3. But
dmesg output has ttyS1
On Thu, 7 Apr 2005 [EMAIL PROTECTED] wrote:
On Wed, 6 Apr 2005, James Miller wrote:
Are you sure your soundcard is not sharing interrupts with other device ?
Not totally, no. cat /pro/interrupts shows only PAS16 assigned to IRQ 3.
But dmesg output has ttyS1 using IRQ 3. It's a bit confusing to me.
On Wed, 6 Apr 2005, James Miller wrote:
On Wed, 6 Apr 2005, Ray Olszewski wrote:
With sb_irq=XXX (and so forth) in the same line as pas2, I do not get these
sorts of error messages. Just a clean:
Pro Audio Spectrum driver Copyright (C) by Hannu Savolainen 1993-1996
But sound still works very poor
On Wed, 6 Apr 2005, Ray Olszewski wrote:
At 01:38 PM 4/6/2005 -0500, James Miller wrote:
> pas2 io=0x388 irq=3 dma=5
sb io=0x230 irq=5 dma=1
You are pretty much doing what I meant to be suggesting. You do need to adapt
this stuf to /etc/modules, not to grub.
Note though that the LILO parameters a
At 01:38 PM 4/6/2005 -0500, James Miller wrote:
[...]
You might want to check that you are using the right parameters (the doc
file that comes with kernel source offers sort of an example, in the form
of a LILO append line to use with compiled-in sound, and it indicates the
need to specify two d
Thanks for your response Ray. I've been able to get a little closer to
normal sound by following your advice. But it's not fully functional yet:
using mp3blaster I can get pretty much continuous sound playing
mp3's/ogg's. Pretty much meaning it is continuous and normal (maybe a bit
of scratchin
At 10:10 AM 4/6/2005 -0500, James Miller wrote:
I'm having some perplexing sound problems on my Debian unstable system and
would like to ask for help, clarifications and sympathy :)
I can at least offer the last. Getting sound right ... particularly with
offbeat hardware ... can be a real pain. I
I'm having some perplexing sound problems on my Debian unstable system and
would like to ask for help, clarifications and sympathy :)
The system is a Dell Optiplex GX1 that's been somewhat modified (BIOS
update, Powerleap processor, maxed out for RAM, extra hard drives, new
power supply). It's
22 matches
Mail list logo
