public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda@ilport.com.ua>
To: Florian Hars <florian@hars.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.12.4: Continuous Sound from internal speaker from boot to shutdown
Date: Mon, 15 Aug 2005 10:18:39 +0300	[thread overview]
Message-ID: <200508151018.39232.vda@ilport.com.ua> (raw)
In-Reply-To: <43002D8A.70701@hars.de>

On Monday 15 August 2005 08:52, Florian Hars wrote:
> I have an NForce4 board with an Athlon 64 and use the 2.6.8 kernel from
> the inofficial debian AMD64 port, and everything works, except that the
> proprietary nvidia driver for my geforce card  complains about "Your
> Linux kernel has problems in its implementation of the change_page_attr
> kernel interface" and recommends an upgrade to 2.6.11 or later. Now
> 2.6.11 is out of the question as it does not support lseek(2)
> (archives.neohapsis.com/archives/postfix/2005-01/1205.html), so I tried
> 2.6.12.4 instead. I used the sources from kernel.org and used the
> default for all new options. On boot I get a contionuous sound from the
> internal speaker from a moment shortly after all filesystems are
> mounted. There seems to be no error message related to the sound. In

Sounds like ( ;] ) it's a userspace program or a loaded module.
boot with init=/bin/sh and then reproduce normal boot manually entering
relevant commands (you need to be familiar with boot process - i.e.
you need to know what commands are executed by system while it boots)
until you find out what is it.

> addition, I get a lot of spurious warnings like
> 
> pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS

Output of lspci? lspci -n?
--
vda


  reply	other threads:[~2005-08-15  7:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15  5:52 2.6.12.4: Continuous Sound from internal speaker from boot to shutdown Florian Hars
2005-08-15  7:18 ` Denis Vlasenko [this message]
2005-08-18  7:28   ` Florian Hars

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=200508151018.39232.vda@ilport.com.ua \
    --to=vda@ilport.com.ua \
    --cc=florian@hars.de \
    --cc=linux-kernel@vger.kernel.org \
    /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