speedstep-smi module on Omnibook 6000 (2.6.0-test8)

Hi,

Perhaps someone can help me in my quest to get speedstep working on my Omnibook 6000. It contains the 440BX/ZX/DX/MX chipset, so I assumed it would work with the speedstep-smi module included with Linux. No, it doesn't. This is the output I get when inserting the module:

speedstep-smi: signature:0x00008680, command:0x0000e6f5, event:0x00000000, perf_level:0x47534943.

Is there anything I can do, probes, utilities or anything, to help someone determine how to get this working?

Thanks in advance,
Please cc me on replies,
John.

PS. there is a module with support called speedstep-piix4 here:
http://www.poupinou.org/cpufreq/speedstep-piix4.html

Your bios do not support GSIC call, so there is really bad luck that others bios call are ok.
You can try to force with
modprobe speedstep-smi smi_cmd=0x82 smi_port=0xb2
but I doubt that will work (but who knows?).

Yes, I know. I was told it is in cpufreq CVS, btw. What say speedstep-detect?

Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

Hi Bruno,

Thanks for the help. I tried to force the module in as you said, and it loads successfully, but this is what I get:

speedstep-smi: signature:0x00008680, command:0x0000e6f5, event:0x00000000, perf_level:0x47534943.
speedstep-smi: could not detect low and high frequencies by SMI call.
cpufreq: change failed
speedstep-smi: could not detect two different speeds -- aborting.

Where can I find speedstep-detect?

John.

Sorry for the premature reply,

Here's the output of speedstep-detect under power:

dmi_scan: return:
DMI 2.3 present.
36 structures occupying 1161 bytes.
DMI table at 0x000EFC80.
BIOS Vendor: Phoenix Technologies Ltd.
BIOS Version: EA.M1.82
BIOS Release: 05/23/2002
System Vendor: Hewlett-Packard
Product Name: HP OmniBook PC
Version: HP OmniBook 6000 EA
Board Vendor: Hewlett-Packard
Board Name: HP OmniBook PC
Board Version: 6000EA
Trying Intel's int15 GSIC:
BIOS DO NOT support GSIC call. Dumping registers anyway:
eax = 0x00008680
ebx = 0x00000000
ecx = 0x00000000
edx = 0x47534943
probing chipsets: Found PIIX4
pmbase at 0x8000
Dumping PM IO register for this southbridge:
PMCNTRL (0x8004): 0x1400

(0x8006):         0x0000
GPEN (0x800e):    0x0001
PCNTRL (0x8010):  0x00001a08
(0x8016):         0x0000
DEVSTS (0x801c):  0x00000000
GLBLEN (0x8020):  0x0400
(0x8022):         0x00000000
GLBCTL (0x8028):  0x06013d05
DEVCTL (0x802c):  0x02000000
GPIs: (0x8030):   0x260003
(0x8033):         0x00
GPOs: (0x8034):   0x00e02150
(0x8038):         0x03 0x00 0x26 0x00 0x50 0x21 0xe0 0x00 

                                      ..28..24..20..16..12...8...4...0
        GPOs: (0x8034):   0x00e02150  00000000111000000010000101010000

And here's the diff for the battery:

26c26
< PCNTRL (0x8010): 0x00001a08
---

29c29
< GLBLEN (0x8020): 0x0400
---

35,36c35,36
< GPOs: (0x8034): 0x00e02150
< (0x8038): 0x03 0x00 0x26 0x00 0x50 0x21 0xe0 0x00
---

< GPOs: (0x8034): 0x00e02150 00000000111000000010000101010000
---

Thanks for everything,
John.

You may try with
modprobe speedstep-piix4 gpo_hilo=0x30
but you need a kernel version 2.6.0-test5 (if im correct) because the cvs is not updated (sorry), or with a recent 2.4 kernel and cvs.

Cheers,

Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.