Tuesday June 28, 2005
Casper Dik's WeblogCasper Dik's Weblog First Installment (of frkit) I've teased people before about the nifty hacks I've been doing for my Ferrari 3400 laptop. The hacks I did and the tool I wrote to make the distribution easier were so well liked that there was this "meme" propagating that whenever we got even cooler laptops, I should get the first one. And so it happened, I literally got the first Ferrari 4000 shipped to Sun. Now, this is a whole different beast than the Ferrari 3400 and I haven't yet gotten quite to the same comfort level yet. I've long promised to make all of the neat stuff available, but legalities are the difficult part of such a venture. But now with OpenSolaris and a supported license scheme (plus management buy-in), I now feel comfortable to release the stuff which I wrote or was derived from source now available under the CDDL) The first installment includes my single CPU "PowerNow!(tm)" driver and my battery driver and utility. What the heck, let's throw in the mdb scripts which enable the additional keys on the Acer keyboards (mail, www, P1, P2, audio control). Some of these appear standard controls and may work for internet keyboards as well. The tar.gz files all come with an install script which will take care of all the details of the installation; the battery driver requires ACPICA; that is only included in Solaris Nevada (11) build 14 and later. I'll see what I can do about the GNOME battery utility we've done as well; oh, sorry for the somewhat lacking documentation. Update: I've added acpipowertool, a small graphic battery meter by Matt Simmons, and fixed some installation issues for root user's without "nm" in $PATH. Update2: (2005/7/31) Ive upgraded powernow so it works for more systems and to better integrate powernowadm with SMF; apcidrv is also updated to do a little bit more of thermal zone handling. acpidrv only works for Solaris express build 14 and later; powernow should work with Solaris 10 GA also.
Update3: frkit is for some time now available as runnable script at www.opensolaris.org in the (2005-06-28 08:26:54.0) Permalink Comments [19]
Trackback URL: http://blogs.sun.com/casper/entry/first_installment
Post a Comment: |
Calendar
RSS Feeds
All /General /OpenSolaris /Solaris SearchLinks
NavigationReferersToday's Page Hits: 234 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Posted by Jimmy Laptop on June 28, 2005 at 06:23 PM MEST #
Posted by Casper Dik on June 28, 2005 at 09:31 PM MEST #
Posted by Charles Meeks on June 29, 2005 at 03:35 PM MEST #
Posted by W. Wayne Liauh on June 29, 2005 at 09:01 PM MEST #
I think we all know how Solaris/x86 was first 'serverized' (no laptop support, later no desktop support) and then really abandoned. We're recovering from four or five years of wanton neglect and such recovery takes time. We made great strides in Solaris 10, the first release with substantial x86 specific optimizations and features and full fledged amd64 support.
The power management stuff I threw over the fence is a stop-gap; without it I find that the AMD64 laptops are too hot to handle and battery life sucks too.
We have people working on the various ACPI power, states including suspend to RAM which would probably happen automatically when you close the lid.
Another important laptop feature is wifi; I think we're fairly close to releasing those prototypes as well.
Posted by Casper Dik on June 29, 2005 at 09:11 PM MEST #
Posted by W. Wayne Liauh on June 30, 2005 at 01:40 AM MEST #
Posted by Darren Moffat on July 19, 2005 at 12:21 AM MEST #
Posted by W. Wayne Liauh on July 28, 2005 at 07:34 PM MEST #
Posted by Martin Cerveny on September 05, 2005 at 07:04 PM MEST #
Posted by Joe Gainey on September 16, 2005 at 09:45 PM MEST #
Posted by Douglas Atique on September 21, 2005 at 06:23 PM MEST #
Posted by Casper Dik on September 22, 2005 at 12:10 PM MEST #
I am very interested in knowing what goes on under the hood with ACPI. I already know there is some kind of microcode in some specific memory locations that is specific to my hardware and there is an interpreter for this code that is provided by the OS, and that when a hardware event triggers an event handler must be registered somehow in the OS (in Solaris case, some functions inside acpidrv module) so that it can take proper action. But what happens behind the scenes with prtconf? Why does it say there is no driver attached? Does it have something to do with the minor device number you create on /dev?
prtconf -v still says acpi device has no driver attached. Here it is (just the part that talks about acpi):
acpi (driver not attached)
Hardware properties:
name='acpi-namespace' type=string items=1
value='\_SB_.ADP1'
name='model' type=string items=1
value='ACPI AC Device'
name='compatible' type=string items=1
value='ACPI0003'
Posted by Douglas Atique on September 26, 2005 at 04:20 PM MEST #
Posted by Douglas Atique on October 10, 2005 at 01:07 AM MEST #
Posted by Douglas Atique on October 11, 2005 at 06:29 PM MEST #
And the atheros driver was promptly recognized in my Toshiba Satellite A45-S2501 notebook
Thanks, Casper!
Posted by Douglas Atique on October 12, 2005 at 05:52 AM MEST #
Posted by Masaki Hasegawa on January 26, 2006 at 08:18 AM MET #
Posted by Dan on December 06, 2006 at 10:47 PM MET #
Hi!! I hass ben used, from a very long time, the frkit (before destroy my acer 5050, literally, with a electric shock in a openSolaris presentation), and it's a great job, but now I have a hp pavilion dv2625, the keyboard hack work only for volumen control. I did like to know how you discover the key codes from ferrary, to do something similar with my hp laptop. Thanks and excuse my bad english. Regards from Chile!
Posted by Raul Ortega on May 26, 2008 at 08:07 PM MEST #