Skip to contentSkip to conversation

Pentium III Coppermine and 440BX/ZX/DX

DISCUSSION Jesper Anderson 2 participants 5 messages Feb 17, 2004

lore
Share & tools
lore
#0 lore raw

I have a Gateway Solo 3450 laptop, which is a PIII 750 MHz with a PIIX4 chipset. I'm trying to get both ACPI and cpufreq to work on it, with very little luck so far. The ACPI is its own kettel of fish, I suspect the BIOS might be rather broken (but then, which isn't?), but I was hoping the cpufreq issue could at least be somewhat easy to solve.

Unfortunately I'm a bit unclear on just what I need to do to get cpufreq running on this system. I tried modprobing speedstep-smi (from kernel 2.6.2 with mm1), and it gives no errors - but neither does it give me anything to go on in /sys or /proc. speedstep-ich doesn't load at all. I tried the patch posted previously on the mailing list (that removes a few bits of the PIII check), but that didn't make any difference.

I'm a bit at a loss as to where to go from here. speedstep-detect doesn't show any different output on battery or AC power, can that be a problem?

Output of speedstep-detect is attached.

Thanks in advance,

Jesper

# ./speedstep-detect
dmi_scan: return:
DMI present.
31 structures occupying 1004 bytes.
DMI table at 0x000D3010.
BIOS Vendor: Gateway
BIOS Version: 28.06.04
BIOS Release: 03/14/2002
System Vendor: Gateway
Product Name: Solo3450
Version: Rev 1.0
Board Vendor: Gateway
Board Name: Solo3450
Board Version: Rev 1.0
Trying Intel's int15 GSIC:
BIOS support GSIC call:
        signature: GSIC
        command port = 0x00b2
        command =      0x0080
        event port =   0x000000b3
        flags =        0x07d00100
probing chipsets: Found PIIX4
  pmbase at 0x8000
Dumping PM IO register for this southbridge:
PMCNTRL (0x8004): 0x1401
(0x8006):         0x0000
GPEN (0x800e):    0x0e00
PCNTRL (0x8010):  0x00003a0c
(0x8016):         0x0000
DEVSTS (0x801c):  0x00000000
GLBLEN (0x8020):  0x0400
(0x8022):         0x00000000
GLBCTL (0x8028):  0x06010305
DEVCTL (0x802c):  0x01200000
GPIs: (0x8030):   0x3fe343
(0x8033):         0x00
GPOs: (0x8034):   0x6c3fb7d1
(0x8038):         0x43 0xe3 0x3f 0x00 0xd1 0xb7 0x3f 0x6c 

You need to boot on AC and battery and see if GPOs change. Then, see if one bit change in between, you have then to note the number of this bit. This will be the gpo_hilo= number kernel option for enabling the speedstep-piix4 module under Linux.

                                      ..28..24..20..16..12...8...4...0
        GPOs: (0x8034):   0x6c3fb7d1  01101100001111111011011111010001
#1 lore raw
Quoted 39 lines · Jesper Anderson

I have a Gateway Solo 3450 laptop, which is a PIII 750 MHz with a PIIX4 chipset. I'm trying to get both ACPI and cpufreq to work on it, with very little luck so far. The ACPI is its own kettel of fish, I suspect the BIOS might be rather broken (but then, which isn't?), but I was hoping the cpufreq issue could at least be somewhat easy to solve.

Unfortunately I'm a bit unclear on just what I need to do to get cpufreq running on this system. I tried modprobing speedstep-smi (from kernel 2.6.2 with mm1), and it gives no errors - but neither does it give me anything to go on in /sys or /proc. speedstep-ich doesn't load at all. I tried the patch posted previously on the mailing list (that removes a few bits of the PIII check), but that didn't make any difference.

I'm a bit at a loss as to where to go from here. speedstep-detect doesn't show any different output on battery or AC power, can that be a problem?

Output of speedstep-detect is attached.

Thanks in advance,

Jesper

# ./speedstep-detect
dmi_scan: return:
DMI present.
31 structures occupying 1004 bytes.
DMI table at 0x000D3010.
BIOS Vendor: Gateway
BIOS Version: 28.06.04
BIOS Release: 03/14/2002
System Vendor: Gateway
Product Name: Solo3450
Version: Rev 1.0
Board Vendor: Gateway
Board Name: Solo3450
Quoted 8 lines
Board Version: Rev 1.0
Trying Intel's int15 GSIC:
BIOS support GSIC call:
        signature: GSIC
        command port = 0x00b2
        command =      0x0080
        event port =   0x000000b3
        flags =        0x07d00100

There is good chance that it work, but I think that you need to pass the smi_cmd=0x82 to speedstep-smi:

modprobe speedstep-smi smi_cmd=0x82

Cheers,

Signature · 4 lines
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.
#2 lore raw
Quoted 5 lines · Bruno Ducrot

There is good chance that it work, but I think that you need to pass the smi_cmd=0x82 to speedstep-smi:

modprobe speedstep-smi smi_cmd=0x82

Thanks. Hmm. I tried that, and the exact same thing happened; ie. nothing. I looked manually for the cpufreq interface in /sys and /proc, and couldn't find anything. cpufreqd 1.1.1 can't find it either.

Jesper

#3 lore raw
In reply to Bruno Ducrot
Quoted 5 lines · Bruno Ducrot

There is good chance that it work, but I think that you need to pass the smi_cmd=0x82 to speedstep-smi:

modprobe speedstep-smi smi_cmd=0x82

Ok, I played around a bit, rebooted, messed about - and suddenly this worked. Well, sort of. I now have an interface to read information, however, there's no way to set the CPU frequency; I can't find a write interface?

# ls /sys/devices/system/cpu/cpu0/cpufreq/
cpuinfo_max_freq             scaling_driver    scaling_min_freq
cpuinfo_min_freq             scaling_governor
scaling_available_governors  scaling_max_freq

No scaling_setspeed interface to be found ...

This is with kernel 2.6.2 mm1. Anything else I can try. or anything I missed here?

Thanks very much for the help so far, looks like this might end up working!

Jesper

#4 lore raw
Quoted 11 lines · Jesper Anderson
Quoted 5 lines · Bruno Ducrot

There is good chance that it work, but I think that you need to pass the smi_cmd=0x82 to speedstep-smi:

modprobe speedstep-smi smi_cmd=0x82

Ok, I played around a bit, rebooted, messed about - and suddenly this worked. Well, sort of. I now have an interface to read information, however, there's no way to set the CPU frequency; I can't find a write interface?

Now I feel pretty stupid. In my playing around trying to get this to work, I had among other things turned the userspace governor off, and forgot to turn it back on. Turning it back on fixed everything, we can add the Gateway Solo 3450 to the success stories using speedstep-smi with smi_cmd=0x82 added as an argument.

Now, if I can only get the ACPI interface to see the battery, I'd be a lot happier ... but that's a different problem.

Thank you very much for the help!

Jesper