public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: Ryan Underwood <nemesis-lists@icequake.net>,
	acpi-devel@lists.sourceforge.net,
	tlinux-users@linux.toshiba-dme.co.jp
Subject: [tlinux-users:06884] Re: [ACPI] Portege 7010CT CPU speed
Date: Mon, 18 Apr 2005 13:31:07 -0500	[thread overview]
Message-ID: <20050418183107.GA27407@dbz.icequake.net> (raw)
In-Reply-To: <20050415131757.GD2298@poupinou.org>


On Fri, Apr 15, 2005 at 03:17:57PM +0200, Bruno Ducrot wrote:
> 
> You hit the (in)famous 'toshiba return bug'.  That should be fixed with
> recent version of ACPI-CA (read: may not work with 2.6.11, but should
> work with upcomming 2.6.12).

I cloned linux-2.6 BK of 2.6.12-rc2, and then pulled ACPI 26-latest into
it.  Recompiled with stock Debian configuration.  The following problems
have been fixed for the 7010CT and were previously broken:

- CPU speed is now 300MHz instead of 150MHz
- ACPI IRQ routing is now working (pci=noacpi not necessary)
- hotplug picks up internal sound on the 'isapnp' bus as it should from
  the ACPI-PNP info.  Unfortunately opl3sa2 is blacklisted in default
  hotplug configuration; I haven't seen yet if it successfully loads the
  driver.

Unfortunately kernel 2.6.12-rc2 seems to have some bugs - for instance
unloading opl3sa2 module hangs the system entirely.  Furthermore, there
is an e100 ethernet which is enabled when the docking station is
connected at boot (hotplugging docking station does not work as with
windows).  This works initially, but after some time the transceiver
seems to stop responding.  Attempting to unload the driver first fails
and then oopses.  I'm not sure if this is the defective docking station
or a linux bug.  I only get to interact with this system once per month
or so, so it is hard to check.

Anyway, the ACPI problems seem to have been solved, so I'd like to see
the fix(es) into the main kernel soon.  Thanks!

-- 
Ryan Underwood, <nemesis@icequake.net>

      reply	other threads:[~2005-04-18 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12  3:59 Portege 7010CT CPU speed Ryan Underwood
     [not found] ` <20050412035916.GB7304-eRi7t0xs5gloIlNlpBNreQ@public.gmane.org>
2005-04-15 13:17   ` Bruno Ducrot
2005-04-18 18:31     ` Ryan Underwood [this message]

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=20050418183107.GA27407@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=ducrot@poupinou.org \
    --cc=tlinux-users@linux.toshiba-dme.co.jp \
    /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