Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

[Josh Myer]

You're probably just hearing electrical noise from the memory buss; try
moving the 128 stick to the slot you put the 64 in (if you can) and run
that way -- you'll probably hear it there too.

I get something similiar to this with my SB Live (!... damn marketroids) on
a BP6 with 192MB as well. In my case, it's not during DSP use per se, but
during memory activity. Try dragging a window around in X and listen for
buzzing.

My guess is that JA's console player doesn't move around as much memory as
the gnome one (imagine that), therefore produces less memory noise.
--
/jbm, but you can call me Josh. Really, you can.
       "car. snow. slippery. wheee. 
        dead josh. car slipped on ice."
 -- Manda explaining my purchase of kitty litter

On Wed, 17 Jan 2001 17:25:51 J . A . Magallon wrote:
> 
> On 2001.01.18 Joel Franco Guzmán wrote:
> > 1. 128M memory OK, but with 192M the sound card generate a noise while
> > use the DSP.
> .. 
> > the problem: The sound card generates a toc.. toc.. toc .. toc...while
> > playing a sound using the DSP of the soundcard. Two "tocs"/sec
> > aproxiumadetely.
> > 
> > 
.
> I have noticed something similar. If I start gqmpeg from the command line
> in
> a terminal (rxvt), sounds fine. If I start it from the icon in the gnome
> panel, it makes that 'toc toc' noise you describe. ????
> (I know it sounds strange, but real...)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

[Joel Franco Guzmán]

No se si entiendes español (por causa del .ch) pero lo escribo en mi
pesimo ingles.

Bug Report
----------
1. 128M memory OK, but with 192M the sound card generate a noise while
use the DSP.
2. i got the problem when I just put more 64M memory to the my machine.
With 128M the problem is not present, but with 192M it is. The only
difference is the memory quantity, or in other words, the additional slot
occupied by the new memory card.

i've got the two dmesg, with 128M and with 192M.
With the kernel 2.2.18 don't problem.

the problem: The sound card generates a toc.. toc.. toc .. toc...while
playing a sound using the DSP of the soundcard. Two "tocs"/sec
aproxiumadetely.

i think that be a irq problem.

3. es1371, sound card, kernel 2.4
4. Linux version 2.4.1-pre8 (root@thor.gds-corp.com) (gcc version 2.95.3
19991030 (prerelease)) #2 Wed Jan 17 19:44:31 BRST 2001
   Tested too with the 2.4.0 official kernel.
5. No Oops.
6.
7.Hardware
   - Pentium III 600Mhz Coppermine 133Mhz FSB, mounted with SLOTA
(or
slot 1) to socket 770 adaptor.
   - ASUS P299 (Chipset i440ZX). Note: the i440ZX don't support officially
the coppermine processor at 133Mhz FSB.
   - 100Mhz memory modules. 2 modules in the 2 slots provided by the
motherboard. One of 128M and the other 64M.
   - Sound card creative. es1391 chipset.
  7.1

Linux thor.gds-corp.com 2.4.1-pre8 #2 Wed Jan 17 19:44:31 BRST 2001
i686 unknownKernel modules         2.3.21
Gnu C                  2.95.3
Gnu Make               3.79.1
Binutils               2.10.0.24
Linux C Library        2.1.3
Dynamic linker         ldd (GNU libc) 2.1.3
Procps                 2.0.7
Mount                  2.10o
Net-tools              1.57
Console-tools          0.2.3
Sh-utils               2.0
cat: /proc/modules: No such file or directory
Modules Loaded

7.2

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 8
model name	: Pentium III (Coppermine)
stepping	: 3
cpu MHz		: 598.483
cache size	: 256 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov
pat pse36 mmx fxsr sse
bogomips	: 1192.75

7.3 static kernel compiled.
7.4 [joel@thor linux]$ cat /proc/ioports
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0376-0376 : ide1
03c0-03df : vga+
  03c0-03df : matrox
03f6-03f6 : ide0
03f8-03ff : serial(auto)
0cf8-0cff : PCI conf1
b800-b87f : 3Com Corporation 3c905B 100BaseTX [Cyclone]
  b800-b87f : eth0
d000-d03f : Ensoniq ES1371 [AudioPCI-97]
  d000-d03f : es1371
d400-d41f : Intel Corporation 82371AB PIIX4 USB
  d400-d41f : usb-uhci
d800-d80f : Intel Corporation 82371AB PIIX4 IDE
  d800-d807 : ide0
  d808-d80f : ide1
e400-e43f : Intel Corporation 82371AB PIIX4 ACPI
e800-e81f : Intel Corporation 82371AB PIIX4 ACPI

[joel@thor linux]$ cat /proc/iomem
00000000-0009efff : System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-0bffcfff : System RAM
  00100000-00265055 : Kernel code
  00265056-002dd703 : Kernel data
e1000000-e100007f : 3Com Corporation 3c905B 100BaseTX [Cyclone]
e1800000-e2dfffff : PCI Bus #01
  e1800000-e1ffffff : Matrox Graphics, Inc. MGA G200 AGP
  e2000000-e2003fff : Matrox Graphics, Inc. MGA G200 AGP
    e2000000-e2003fff : matroxfb MMIO
e2f00000-e3ffffff : PCI Bus #01
  e3000000-e3ffffff : Matrox Graphics, Inc. MGA G200 AGP
    e3000000-e3ffffff : matroxfb FB
e4000000-e7ffffff : Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge

7.5
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge
(rev 03)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR-
	Latency: 64
	Region 0: Memory at e4000000 (32-bit, prefetchable) [size=64M]
	Capabilities: [a0] AGP version 1.0
		Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2
		Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>

00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge
(rev 03) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
	I/O behind bridge: 0000e000-0000dfff
	Memory behind bridge: e1800000-e2dfffff
	Prefetchable memory behind bridge: e2f00000-e3ffffff
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B+

00:04.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 0

00:04.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
(prog-if 80 [Master])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 32
	Region 4: I/O ports at d800 [size=16]

00:04.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
(prog-if 00 [UHCI])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 32
	Interrupt: pin D routed to IRQ 5
[root@thor linux]# lspci -vvv
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge
(rev 03)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR-
	Latency: 64
	Region 0: Memory at e4000000 (32-bit, prefetchable) [size=64M]
	Capabilities: [a0] AGP version 1.0
		Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2
		Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>

00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge
(rev 03) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
	I/O behind bridge: 0000e000-0000dfff
	Memory behind bridge: e1800000-e2dfffff
	Prefetchable memory behind bridge: e2f00000-e3ffffff
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B+

00:04.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 0

00:04.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
(prog-if 80 [Master])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 32
	Region 4: I/O ports at d800 [size=16]

00:04.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
(prog-if 00 [UHCI])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 32
	Interrupt: pin D routed to IRQ 5
	Region 4: I/O ports at d400 [size=32]

00:04.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

00:0a.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 06)
	Subsystem: Ensoniq Creative Sound Blaster AudioPCI64V, AudioPCI128
	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 d000 [size=64]
	Capabilities: [dc] Power Management version 1
		Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA
PME(D0+,D1-,D2+,D3hot+,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0b.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone]
(rev 30)
	Subsystem: 3Com Corporation 3C905B Fast Etherlink XL 10/100
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (2500ns min, 2500ns max), cache line size 08
	Interrupt: pin A routed to IRQ 10
	Region 0: I/O ports at b800 [size=128]
	Region 1: Memory at e1000000 (32-bit, non-prefetchable) [size=128]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: [dc] Power Management version 1
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1+,D2+,D3hot+,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200 AGP (rev
03) (prog-if 00 [VGA])
	Subsystem: Matrox Graphics, Inc. Millennium G200 AGP
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 64 (4000ns min, 8000ns max), cache line size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at e3000000 (32-bit, prefetchable) [size=16M]
	Region 1: Memory at e2000000 (32-bit, non-prefetchable) [size=16K]
	Region 2: Memory at e1800000 (32-bit, non-prefetchable) [size=8M]
	Expansion ROM at e2ff0000 [disabled] [size=64K]
	Capabilities: [dc] Power Management version 1
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [f0] AGP version 1.0
		Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2
		Command: RQ=31 SBA+ AGP+ 64bit- FW- Rate=x2

7.6

[root@thor linux]# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: HP       Model: CD-Writer+ 8200  Rev: 1.0f
  Type:   CD-ROM                           ANSI SCSI revision: 02


-- 
    Joel Franco Guzmán
GDS - Global Dynamic Systems
   joelfranco@bigfoot.com
ICQ 19354050 | (16) 270-6867



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

[J . A . Magallon]

On 2001.01.18 Joel Franco Guzmán wrote:
> 1. 128M memory OK, but with 192M the sound card generate a noise while
> use the DSP.
.. 
> the problem: The sound card generates a toc.. toc.. toc .. toc...while
> playing a sound using the DSP of the soundcard. Two "tocs"/sec
> aproxiumadetely.
> 
> 
> Linux thor.gds-corp.com 2.4.1-pre8 #2 Wed Jan 17 19:44:31 BRST 2001
> i686 unknownKernel modules         2.3.21

Don't know if it is related, but you should upgrade your modutils up to
2.4, even 2.4.1 is yet available.

I have noticed something similar. If I start gqmpeg from the command line in
a terminal (rxvt), sounds fine. If I start it from the icon in the gnome
panel, it makes that 'toc toc' noise you describe. ????
(I know it sounds strange, but real...)

How do you launch your sound test ? (btw, which do you use to play sound ?) 

-- 
J.A. Magallon                                                      $> cd pub
mailto:jamagallon@able.es                                          $> more beer

Linux werewolf 2.4.0-ac9 #2 SMP Sun Jan 14 01:46:07 CET 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

[Stefan Ring]

On Wed, 17 Jan 2001, Joel Franco Guzmán wrote:

> With 128M the problem is not present, but with 192M it is. The only
> difference is the memory quantity, or in other words, the additional slot
> occupied by the new memory card.

>    - ASUS P299 (Chipset i440ZX). Note: the i440ZX don't support officially
> the coppermine processor at 133Mhz FSB.

I know that increasing the number of DIMMs on your board will require
speedier RAMs on ASUS boards with some sort of an i440 chipset. This may
well be the case for just about every other MB, it's only that I don't
know specifically about these other boards.

133MHz is damn fast, and you need really good RAMs to keep up to that.
In fact, most of the cheap modules sold as "PC133" can't cope with it,
and you just got PC100. That's asking for trouble! As you add more
modules, it gets even more critical.

Do extensive testing before actually using such a system. The best testing
that I know of is compiling large source trees with 2.2.x (I don't know
about 2.4.x -- I DO know that 2.0.x won't turn up problems as easily
because the buffer cache grows out of bounds) for hours and hours (10h
minimum, 48h or more desirable). Make sure that there is enough "free"
memory at all time (not cached, but really "free"). Also make sure that
the temperature inside your computer is slightly higher than in actual use
to put maximum stress on the RAMs.

You may be able to get away by just increasing the SDRAM timings if you
are running 2-2-2.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

[J . A . Magallon]

On 2001.01.17 Josh Myer wrote:
> 
> My guess is that JA's console player doesn't move around as much memory as
> the gnome one (imagine that), therefore produces less memory noise.

No, that is the problem. It is just the same player, just launched from
the command line (also opens his gnome window, doees not fall back to a
terminal look) or pushing a button... That is what I don't understand.

-- 
J.A. Magallon                                                      $> cd pub
mailto:jamagallon@able.es                                          $> more beer

Linux werewolf 2.4.0-ac9 #2 SMP Sun Jan 14 01:46:07 CET 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

[Joel Franco Guzmán]

On Wed, 17 Jan 2001, Josh Myer wrote:

> You're probably just hearing electrical noise from the memory buss; try
> moving the 128 stick to the slot you put the 64 in (if you can) and run
> that way -- you'll probably hear it there too.

i've exchanged the two memory slot, and the problem is still alive.

>
> I get something similiar to this with my SB Live (!... damn marketroids) on
> a BP6 with 192MB as well. In my case, it's not during DSP use per se, but
> during memory activity. Try dragging a window around in X and listen for
> buzzing.

When i drag a window around in X, the noise don't change. It's a rate
constant and not influencied by the windows movement.

Thank You Josh.

>
> My guess is that JA's console player doesn't move around as much memory as
> the gnome one (imagine that), therefore produces less memory noise.
> --
> /jbm, but you can call me Josh. Really, you can.
>        "car. snow. slippery. wheee.
>         dead josh. car slipped on ice."
>  -- Manda explaining my purchase of kitty litter
>
> On Wed, 17 Jan 2001 17:25:51 J . A . Magallon wrote:
> >
> > On 2001.01.18 Joel Franco Guzmán wrote:
> > > 1. 128M memory OK, but with 192M the sound card generate a noise while
> > > use the DSP.
> > ..
> > > the problem: The sound card generates a toc.. toc.. toc .. toc...while
> > > playing a sound using the DSP of the soundcard. Two "tocs"/sec
> > > aproxiumadetely.
> > >
> > >
> .
> > I have noticed something similar. If I start gqmpeg from the command line
> > in
> > a terminal (rxvt), sounds fine. If I start it from the icon in the gnome
> > panel, it makes that 'toc toc' noise you describe. ????
> > (I know it sounds strange, but real...)
>

-- 
    Joel Franco Guzmán
GDS - Global Dynamic Systems
   joelfranco@bigfoot.com
ICQ 19354050 | (16) 270-6867

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

[Mike Dresser]

Sorry if this has been asked of you before, but what happens if you put just
the 64 meg module in?

> Bug Report
> ----------
> 1. 128M memory OK, but with 192M the sound card generate a noise while
> use the DSP.
> 2. i got the problem when I just put more 64M memory to the my machine.
> With 128M the problem is not present, but with 192M it is. The only
> difference is the memory quantity, or in other words, the additional slot
> occupied by the new memory card.

My instinct is the pc100 ram being run at 133.  Sometimes you get away with
it(my pre-ratings, but supposed to be pc66 - hyundai ram runs at 100 just
fine, but won't go any higher), and maybe your new 64 megger can't do it.

Mike Dresser


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

[Joel Franco Guzmán]

On Thu, 18 Jan 2001, Mike Dresser wrote:

> Sorry if this has been asked of you before, but what happens if you put just
> the 64 meg module in?

Ok. i've not analised that possibility. I've tested that just now.
But, the system work perfect. Without the sound card problem.
I've exchanged the modules. FAIL.
The memory sets in the BIOS is 3-3-3-10.
The 64M and the 128M is PC100.
Another more one thing. I think that be a software problem, because with
the kernel 2.2.18 it's not happening.

thank you, Mike.
>
> > Bug Report
> > ----------
> > 1. 128M memory OK, but with 192M the sound card generate a noise while
> > use the DSP.
> > 2. i got the problem when I just put more 64M memory to the my machine.
> > With 128M the problem is not present, but with 192M it is. The only
> > difference is the memory quantity, or in other words, the additional slot
> > occupied by the new memory card.
>
> My instinct is the pc100 ram being run at 133.  Sometimes you get away with
> it(my pre-ratings, but supposed to be pc66 - hyundai ram runs at 100 just
> fine, but won't go any higher), and maybe your new 64 megger can't do it.
>
> Mike Dresser
>

-- 
    Joel Franco Guzmán
GDS - Global Dynamic Systems
   joelfranco@bigfoot.com
ICQ 19354050 | (16) 270-6867

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

[Joel Franco Guzmán]

On Thu, 18 Jan 2001, Stefan Ring wrote:

> On Wed, 17 Jan 2001, Joel Franco Guzmán wrote:
>
> > With 128M the problem is not present, but with 192M it is. The only
> > difference is the memory quantity, or in other words, the additional slot
> > occupied by the new memory card.
>
> >    - ASUS P299 (Chipset i440ZX). Note: the i440ZX don't support officially
> > the coppermine processor at 133Mhz FSB.
>
> I know that increasing the number of DIMMs on your board will require
> speedier RAMs on ASUS boards with some sort of an i440 chipset. This may
> well be the case for just about every other MB, it's only that I don't
> know specifically about these other boards.

This means that a modules will work at more high MHZ?

>
> 133MHz is damn fast, and you need really good RAMs to keep up to that.
> In fact, most of the cheap modules sold as "PC133" can't cope with it,
> and you just got PC100. That's asking for trouble! As you add more
> modules, it gets even more critical.

OK. the 2 modules are PC100.
But why the system works with the 2.2.18 kernel perfectly?
It's by this, that i think that the problem is in new kernel.

>
> Do extensive testing before actually using such a system. The best testing
> that I know of is compiling large source trees with 2.2.x (I don't know
> about 2.4.x -- I DO know that 2.0.x won't turn up problems as easily
> because the buffer cache grows out of bounds) for hours and hours (10h
> minimum, 48h or more desirable). Make sure that there is enough "free"
> memory at all time (not cached, but really "free"). Also make sure that
> the temperature inside your computer is slightly higher than in actual use
> to put maximum stress on the RAMs.
>
> You may be able to get away by just increasing the SDRAM timings if you
> are running 2-2-2.

I use 3-3-3 to have security that i'm not forcing the memory modules.
with 2-2-2 i've troubles.

thank you.


>

-- 
    Joel Franco Guzmán
GDS - Global Dynamic Systems
   joelfranco@bigfoot.com
ICQ 19354050 | (16) 270-6867

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

[Stefan Ring]

> > I know that increasing the number of DIMMs on your board will require
> > speedier RAMs on ASUS boards with some sort of an i440 chipset. This may
> > well be the case for just about every other MB, it's only that I don't
> > know specifically about these other boards.
> 
> This means that a modules will work at more high MHZ?

I said that you need faster (better) RAMs for the same bus speed when you
put more modules in. I could also say that you might have to lower the bus
speed so your RAMs keep up.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

[Mike Galbraith]

On Thu, 18 Jan 2001, Stefan Ring wrote:

> > > I know that increasing the number of DIMMs on your board will require
> > > speedier RAMs on ASUS boards with some sort of an i440 chipset. This may
> > > well be the case for just about every other MB, it's only that I don't
> > > know specifically about these other boards.
> > 
> > This means that a modules will work at more high MHZ?
> 
> I said that you need faster (better) RAMs for the same bus speed when you
> put more modules in. I could also say that you might have to lower the bus
> speed so your RAMs keep up.

Any mb where this statement is true is useless crap.  (or the ram you're
attempting to hanging onto it's healthy memory bus is useless crap.. one
of the two;)

	-Mike

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble

[Gregory McLean]

On Wed, 17 Jan 2001, Joel Franco Guzmán wrote:

[snip]
>
> the problem: The sound card generates a toc.. toc.. toc .. toc...while
> playing a sound using the DSP of the soundcard. Two "tocs"/sec
> aproxiumadetely.
>
Just for giggles, turn down the LINE-IN volume (or mute it) See if the
noise goes away.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/