From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Daniel Würfel" <daniel.wuerfel@gmx.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-acpi@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
bugme-daemon@bugzilla.kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: [Bugme-new] [Bug 9155] New: No fan control with ATI Radeon display support on HP nx6125.
Date: Sun, 14 Oct 2007 21:55:08 +0200 [thread overview]
Message-ID: <200710142155.09345.rjw@sisk.pl> (raw)
In-Reply-To: <1192371504.6265.46.camel@localhost>
On Sunday, 14 October 2007 16:18, Daniel Würfel wrote:
> Am Sonntag, den 14.10.2007, 16:02 +0200 schrieb Rafael J. Wysocki:
> > On Sunday, 14 October 2007 09:26, Daniel Würfel wrote:
> > > Hi there,
> > >
> > > at first great respect for your fast answers.
> > > I don't think, that the binary ati driver is the problem, because:
> > > 1. with switched of "ati radeon display support" in the kernel, the fan
> > > control works correctly (and i still using the ati-driver)
> >
> > How do you know, however, that the "ati radeon display support" in the kernel
> > does not interfere with the ATI driver in a destructive way?
>
> I think, but im not sure, that the ati driver is loaded, if X was
> started. But at this moment X was not started.
Well, the kernel module part is probably loaded earlier.
> > > 2. the fan starts spinning at the boot screen even if the radeon display
> > > driver was loaded (and the ati driver is not just loaded yet).
> >
> > I'm not sure what you mean exactly. Can you clarify, please?dann
>
> Well, i see it looks a little bit confused what i wrote. What i mean is,
> that the fan at this time starts to rotate, when the "radeon display
> support" is loaded at boot time.
I see.
Can you please check:
- What happens if you don't use the ATI driver at all (please unload its kernel
module before loading the kernel's radeon one)?
- Does the loading of the radeon module trigger the fan automatically?
- What happens if the fan module is not loaded at that time?
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-10-14 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9155-10286@http.bugzilla.kernel.org/>
2007-10-13 17:53 ` [Bugme-new] [Bug 9155] New: No fan control with ATI Radeon display support on HP nx6125 Andrew Morton
[not found] ` <20071013105315.accef6aa.akpm@linux-foundation.org>
2007-10-13 18:30 ` Rafael J. Wysocki
2007-10-14 7:26 ` Daniel Würfel
2007-10-14 14:02 ` Rafael J. Wysocki
2007-10-14 14:18 ` Daniel Würfel
2007-10-14 19:55 ` Rafael J. Wysocki [this message]
2007-10-15 17:12 ` Daniel Würfel
2007-10-15 20:32 ` Rafael J. Wysocki
2007-10-15 20:57 ` Benjamin Herrenschmidt
2007-10-15 21:17 ` Rafael J. Wysocki
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=200710142155.09345.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=daniel.wuerfel@gmx.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).