public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrizio Bassi <patrizio.bassi@gmail.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Ard van Breemen <ard@kwaak.net>, linux-kernel@vger.kernel.org
Subject: Re: [BUG 2579] linux 2.6.* sound problems
Date: Wed, 23 Nov 2005 21:05:31 +0100	[thread overview]
Message-ID: <4384CB8B.6040409@gmail.com> (raw)
In-Reply-To: <1132775178.10453.14.camel@mindpipe>

Lee Revell ha scritto:

>On Wed, 2005-11-23 at 17:22 +0100, Ard van Breemen wrote:
>  
>
>>On Tue, Nov 01, 2005 at 10:54:55AM +0100, Patrizio Bassi wrote:
>>    
>>
>>>i played a bit with bios, but no luck.
>>>considering that in my windows copy i have no problems, i'm sure it's
>>>linux 2.6
>>>
>>>update: can't use linux 2.4, i have nptl only and acpi problems too.
>>>i'll play with timers and latency
>>>      
>>>
>>One more suggestion:
>>try running distributed-net or something else that uses 100% cpu.
>>I also have "bad sound" from on-board audio (hp nx9110 notebook
>>and some elcheap asus motherboard). Usually it is a bad or cheap
>>motherboard design.
>>If using your CPU 100% fixes or mostly diminishes your audio
>>distortion, you can be 100% sure that the audio part has a very
>>bad design (no separate voltage controllers or good power supply
>>filters, and no separate power supply circuit, and of course a
>>good deal of crosstalk between analog lines and "digital" lines).
>>
>>    
>>
>
>Please try to isolate whether the PCI latency timer change OR the change
>from HZ=250 to HZ=100 fixed the problem.
>
>Lee
>
>
>  
>
it seems both.
now i'm using 1000hz with 0x40 latency.
i still get some noises but lower than before (lat = 0x20).

however i saw you marked it closed as hardware problem, i'm sure it isn't.

it' a linux 2.6 problem for me, as 2.4 and windows works perfectly. stop :)
a windows copy, running under vmware on linux 2.6, seems to work good too.

  reply	other threads:[~2005-11-23 20:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53L1x-6dC-13@gated-at.bofh.it>
     [not found] ` <53L1x-6dC-11@gated-at.bofh.it>
2005-10-31 16:59   ` [BUG 2579] linux 2.6.* sound problems Patrizio Bassi
     [not found] ` <53LkE-6QU-5@gated-at.bofh.it>
     [not found]   ` <53LkW-6QU-49@gated-at.bofh.it>
     [not found]     ` <53LEq-7gr-7@gated-at.bofh.it>
2005-10-31 19:44       ` Patrizio Bassi
2005-10-31 23:12         ` Ondrej Zary
     [not found]         ` <4366A49F.3000101@rainbow-software.org>
2005-11-01  9:54           ` Patrizio Bassi
2005-11-23 16:22             ` Ard van Breemen
2005-11-23 19:46               ` Lee Revell
2005-11-23 20:05                 ` Patrizio Bassi [this message]
2005-11-23 20:22                   ` Lee Revell
2005-11-23 20:31                     ` Patrizio Bassi
     [not found] <53JVy-4yi-19@gated-at.bofh.it>
2005-10-31 16:43 ` Bodo Eggert
     [not found] ` <53Kyw-5Bt-53@gated-at.bofh.it>
     [not found]   ` <53L26-6dC-75@gated-at.bofh.it>
2005-10-31 16:59     ` Patrizio Bassi
2005-10-31 17:04   ` Patrizio Bassi
2005-10-31 17:27     ` Ray Lee
     [not found] ` <53Lus-73L-39@gated-at.bofh.it>
2005-10-31 19:38   ` Patrizio Bassi
2005-10-31 15:30 Patrizio Bassi
2005-10-31 16:13 ` Ray Lee
2005-10-31 16:40   ` Mike Fowler
2005-10-31 17:15 ` Lee Revell
2005-10-31 22:10 ` Tomasz Torcz
2005-11-02 11:20   ` Takashi Iwai
2005-11-02 11:36     ` Patrizio Bassi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4384CB8B.6040409@gmail.com \
    --to=patrizio.bassi@gmail.com \
    --cc=ard@kwaak.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox