From: mike <mike-rSZvBvsYROxg9hUCZPvPmw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: smartbattery swsusp and acpi-sbs
Date: Tue, 18 Jan 2005 20:09:08 +0700 [thread overview]
Message-ID: <20051182098.998032@p4> (raw)
In-Reply-To: <20050118081428.909488835A-MRDXTZLjjMs+bN4EscsFoaQD96bmaF075NbjCUgZEJk@public.gmane.org>
i'm having success with the above features. Currently I'm-a-runnin 2.6.10 with support for swsusp. I have the smartbattery(i2c-dev) and I'm using Mr. Townsend's i2c-acpi-ec which I think he said is slightly modified from someone who's name escapes me sorry. I'm also using acpi-sbs.. My machine is an ACER 3200Xci which is just like the "ferrari" 3200 but I live in ASIA so maybe it's slightly different.
I am also able to suspend using swsusp core (2.1.5.12). But I must remove all the i2c modules or we get a nasy! Before I didn't remove the modules and swsusp failed to resume (it suspend okay) but I think i2c-core module was causing the a problem. Now using Mr. Townsend's stuffs, it suspends and resumes just dandy. it looks like i2c core functionality is fine after re-inserting the modules. Thanks heaps by the way I was so bummed about this smart battery issue..
Now 3 error messages:
when removing the i2c-dev modules I get the following:
"i2c-dev does not have a release() function, be careful"
"i2c-adaptor does not have a release() function, be careful"
"Kernel: losing some ticks... checking if CPU frequency changed"
I notice this message happens every 30 seconds which corresponds to the setting I have for gkrellm to poll the /proc attery dir I remember seeing someone mention that i2c reads are very slow and causes the entire system to lock up.. well I rekon this is happening to me.. Is "losing ticks" a bad thing?
Finally an observation:
Upon engaging the battery and subsequently charging again, I notice the battery light comes on and off (in my case it the LED goes from "off not lit" state to "orange" charge state roughly every 62 seconds ( I was hoping it would be 30 seconds) but no such luck. This seems to be reported by other people as well.
Okay thanks again for this, its a killer ap dude
mikel
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
parent reply other threads:[~2005-01-18 13:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20050118081428.909488835A-MRDXTZLjjMs+bN4EscsFoaQD96bmaF075NbjCUgZEJk@public.gmane.org>]
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=20051182098.998032@p4 \
--to=mike-rszvbvsyroxg9huczpvpmw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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