FSC Esprimo Mobile V5505 - info, partly working

Hi !

I got a new FSC Esprimo Mobile V5505 (full system info attached).

Sound-buttons are working, WLAN partly (?). Brightness doesn't work here.

Attachements:
* Full lspci -vv -nn

If any other data is needed -> please ping !

Sincerely yours

Jan-Simon Möller

[email protected]

-------------------------------------------------------

Here is the output of dmidecode:

legolas:~ # dmidecode

# dmidecode 2.9
SMBIOS 2.4 present.
43 structures occupying 1553 bytes.
Table at 0x7F6DF000.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Phoenix Technologies LTD
Version: R01-A0T
Release Date: 09/11/2007
Address: 0xE6290
Runtime Size: 105840 bytes
ROM Size: 1024 kB
Characteristics:
ISA is supported
PCI is supported
PC Card (PCMCIA) is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
ACPI is supported
USB legacy is supported
AGP is supported
BIOS boot specification is supported Targeted content distribution is supported

Handle 0x0001, DMI type 1, 27 bytes System Information
Manufacturer: FUJITSU SIEMENS Product Name: ESPRIMO Mobile V5505
Version: 20
Wake-up Type: Power Switch SKU Number: Not Specified
Family: Not Specified

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: FUJITSU SIEMENS Product Name: ESPRIMO Mobile V5505
Version: Not Applicable
Serial Number: 914V0Z1003G73103DDDKS0B

Handle 0x0003, DMI type 3, 17 bytes Chassis Information
Manufacturer: FUJITSU SIEMENS
Type: Notebook
Lock: Not Present
Version: A2040
Asset Tag: No Asset Tag Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x00001234

Handle 0x0004, DMI type 4, 35 bytes Processor Information
Socket Designation: U2E1
Type: Central Processor
Family: Other
Manufacturer: Intel
ID: FA 06 00 00 FF FB EB BF
Version: CPU Version
Voltage: 3.3 V
External Clock: Unknown Max Speed: 4096 MHz Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: ZIF Socket
L1 Cache Handle: 0x0005 L2 Cache Handle: 0x0006 L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified

Handle 0x0005, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1 Cache
Configuration: Enabled, Socketed, Level 1 Operational Mode: Write Back
Location: Internal
Installed Size: 64 KB
Maximum Size: 64 KB
Supported SRAM Types:
Burst
Pipeline Burst Asynchronous
Installed SRAM Type: Asynchronous
Speed: Unknown
Error Correction Type: Unknown System Type: Unknown
Associativity: Unknown

Handle 0x0006, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2 Cache
Configuration: Enabled, Socketed, Level 2 Operational Mode: Write Back
Location: Internal
Installed Size: 4096 KB
Maximum Size: 4096 KB
Supported SRAM Types:
Burst
Pipeline Burst Asynchronous
Installed SRAM Type: Burst
Speed: Unknown
Error Correction Type: Unknown System Type: Unknown
Associativity: Unknown

Handle 0x0007, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J19
Internal Connector Type: 9 Pin Dual Inline (pin 10 cut) External Reference Designator: COM 1
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible

Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1 Internal Connector Type: None External Reference Designator: Keyboard External Connector Type: Circular DIN-8 male Port Type: Keyboard Port

Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1 Internal Connector Type: None External Reference Designator: PS/2 Mouse External Connector Type: Circular DIN-8 male Port Type: Mouse Port

Handle 0x000A, DMI type 9, 13 bytes System Slot Information
Designation: PCI Slot J8B3
Type: 32-bit PCI Current Usage: Available
Length: Long
ID: 3
Characteristics:
5.0 V is provided 3.3 V is provided

Handle 0x000B, DMI type 9, 13 bytes System Slot Information
Designation: PCI Slot S9B1
Type: 32-bit PCI Current Usage: Unknown
Length: Long
ID: 0
Characteristics:
5.0 V is provided 3.3 V is provided

Handle 0x000C, DMI type 9, 13 bytes System Slot Information
Designation: PEG Slot J6B2
Type: 32-bit PCI Express Current Usage: Available
Length: Long
ID: 6
Characteristics:
5.0 V is provided 3.3 V is provided

Handle 0x000D, DMI type 9, 13 bytes System Slot Information
Designation: PCI Express Slot J6B1
Type: 32-bit PCI Express Current Usage: In Use
Length: Long
ID: 7
Characteristics:
5.0 V is provided 3.3 V is provided

Handle 0x000E, DMI type 9, 13 bytes System Slot Information
Designation: PCI Express Slot J6D1
Type: 32-bit PCI Express Current Usage: Available
Length: Long
ID: 8
Characteristics:
5.0 V is provided 3.3 V is provided

Handle 0x000F, DMI type 9, 13 bytes System Slot Information
Designation: PCI Express Slot J8B4
Type: 32-bit PCI Express Current Usage: In Use
Length: Long
ID: 9
Characteristics:
5.0 V is provided 3.3 V is provided

Handle 0x0010, DMI type 9, 13 bytes System Slot Information
Designation: PCI Express Slot J8D1
Type: 32-bit PCI Express Current Usage: Available
Length: Long
ID: 10
Characteristics:
5.0 V is provided 3.3 V is provided

Handle 0x0011, DMI type 9, 13 bytes System Slot Information
Designation: PCI Express Slot J7B1
Type: 32-bit PCI Express Current Usage: Unknown
Length: Long
ID: 0
Characteristics:
5.0 V is provided 3.3 V is provided

Handle 0x0012, DMI type 10, 6 bytes On Board Device Information
Type: Sound
Status: Disabled
Description: HD-Audio

Handle 0x0013, DMI type 11, 5 bytes OEM Strings
String 1: This is the Intel Crestline String 2: Chipset CRB Platform

Handle 0x0014, DMI type 12, 5 bytes
System Configuration Options
Option 1: Jumper settings can be described here.

Handle 0x0015, DMI type 15, 29 bytes
System Event Log
Area Length: 16 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: General-purpose non-volatile data functions Access Address: 0x0000
Status: Valid, Not Full
Change Token: 0x00000001
Header Format: Type 1
Supported Log Type Descriptors: 3
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: Single-bit ECC memory error
Data Format 2: Multiple-event
Descriptor 3: Multi-bit ECC memory error
Data Format 3: Multiple-event

Handle 0x0016, DMI type 16, 15 bytes Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None Maximum Capacity: 4 GB
Error Information Handle: Not Provided Number Of Devices: 2

Handle 0x0017, DMI type 17, 27 bytes Memory Device
Array Handle: 0x0016
Error Information Handle: No Error Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: SODIMM
Set: 1
Locator: M1
Bank Locator: Bank 0
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz (1.5 ns)
Manufacturer: Mfg 0
Serial Number: 1234-B0 Asset Tag: Not Specified Part Number: SODIMM000

Handle 0x0018, DMI type 17, 27 bytes Memory Device
Array Handle: 0x0016
Error Information Handle: No Error Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: SODIMM
Set: 1
Locator: M2
Bank Locator: Bank 1
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz (1.5 ns)
Manufacturer: Mfg 1
Serial Number: 1234-B1 Asset Tag: Not Specified Part Number: SODIMM001

Handle 0x0019, DMI type 19, 15 bytes Memory Array Mapped Address

        Starting Address: 0x00000000000
        Ending Address: 0x0007FFFFFFF
        Range Size: 2 GB
        Physical Array Handle: 0x0016
        Partition Width: 0

Handle 0x001A, DMI type 20, 19 bytes Memory Device Mapped Address
Starting Address: 0x00000000000 Ending Address: 0x0003FFFFFFF Range Size: 1 GB
Physical Device Handle: 0x0017 Memory Array Mapped Address Handle: 0x0019 Partition Row Position: Unknown Interleave Position: Unknown Interleaved Data Depth: Unknown

Handle 0x001B, DMI type 20, 19 bytes Memory Device Mapped Address
Starting Address: 0x00040000000 Ending Address: 0x0007FFFFFFF Range Size: 1 GB
Physical Device Handle: 0x0018 Memory Array Mapped Address Handle: 0x0019 Partition Row Position: Unknown Interleave Position: Unknown Interleaved Data Depth: Unknown

Handle 0x001C, DMI type 22, 26 bytes Portable Battery
Location: main
Manufacturer: Foxlink Manufacture Date: Panasonic Serial Number: e00513301B32B21030742 Name:
Chemistry: Lithium Ion
Design Capacity: 48840 mWh Design Voltage: 11100 mV
SBDS Version: 00
Maximum Error: Unknown OEM-specific Information: 0x00000000

Handle 0x001D, DMI type 23, 13 bytes System Reset
Status: Enabled
Watchdog Timer: Present
Boot Option: Do Not Reboot Boot Option On Limit: Do Not Reboot Reset Count: Unknown
Reset Limit: Unknown
Timer Interval: Unknown
Timeout: Unknown

Handle 0x001E, DMI type 24, 5 bytes Hardware Security
Power-On Password Status: Disabled Keyboard Password Status: Unknown Administrator Password Status: Disabled Front Panel Reset Status: Unknown

Handle 0x001F, DMI type 25, 9 bytes
System Power Controls
Next Scheduled Power-on: 12-31 23:59:59

Handle 0x0020, DMI type 26, 20 bytes Voltage Probe
Description: Voltage Probe
Location: Processor
Status: OK
Maximum Value: Unknown Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown OEM-specific Information: 0x00000000

Handle 0x0021, DMI type 27, 12 bytes Cooling Device

        Temperature Probe Handle: 0x0022
        Type: Fan
        Status: OK
        OEM-specific Information: 0x00000000

Handle 0x0022, DMI type 28, 20 bytes Temperature Probe
Description: Temperature Probe
Location: Processor
Status: OK
Maximum Value: Unknown Minimum Value Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown OEM-specific Information: 0x00000000

Handle 0x0023, DMI type 29, 20 bytes Electrical Current Probe
Description: Electrical Current Probe
Location: Processor
Status: OK
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000

Handle 0x0024, DMI type 30, 6 bytes Out-of-band Remote Access
Manufacturer Name: Intel Inbound Connection: Enabled Outbound Connection: Disabled

Handle 0x0025, DMI type 32, 20 bytes System Boot Information
Status: <OUT OF SPEC>

Handle 0x0026, DMI type 129, 10 bytes OEM-specific Type

        Header and Data:
                81 0A 26 00 01 01 02 01 01 02
        Strings:
                Intel_ASF
                Intel_ASF_001

Handle 0x0027, DMI type 136, 6 bytes OEM-specific Type
Header and Data:
88 06 27 00 FF FF

Handle 0x0028, DMI type 150, 14 bytes OEM-specific Type
Header and Data:
96 0E 28 00 01 01 00 00 00 00 00 00 00 00
Strings:
ABSOLUTE(PHOENIX) CLM

Handle 0x0029, DMI type 200, 7 bytes OEM-specific Type

        Header and Data:
                C8 07 29 00 01 02 03
        Strings:
                17C0

                0001

Handle 0x002A, DMI type 127, 4 bytes End Of Table

Jan-Simon,
Thanks for the dmidecode output.

Did the console dmesg ask you to send it because
of OSI(Linux)?

Do you notice any functional difference when booting with

"acpi_osi=Linux" (default for 2.6.22 and earlier)
vs.
"acpi_osi=!Linux" (default for 2.6.23 and later)

Also, please send me the output from acpidump.

thanks,
-Len

ps
If you don't have acpidump, you can get it from pmtools here:
http://www.lesswatts.org/projects/acpi/utilities.php
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Sorry for the late reply !

Am Samstag 19 Januar 2008 05:29:49 schrieb Len Brown:

Didn't notice any difference.
acpidump here:

http://bugzilla.kernel.org/show_bug.cgi?id=9939

Thanks!
Jan-Simon
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

thanks for the acpidump in http://bugzilla.kernel.org/show_bug.cgi?id=9939

This BIOS makes heavy use of TRAP's into SMM, Windows version-specific hooks, and WMI -- all bad news for Linux.

But OSI(Linux) itself is a NOP on this box, since LINX is set and never referenced, per below.

-Len

       Method (_INI, 0, NotSerialized)
        {
            If (DTSE)
            {
                TRAP (0x47)
            }

            Store (0x07D0, OSYS)
            If (CondRefOf (_OSI, Local0))
            {
                If (_OSI ("Linux"))
                {
                    Store (0x01, LINX)
                }

                If (_OSI ("Windows 2001"))
                {
                    Store (0x07D1, OSYS)
                }

                If (_OSI ("Windows 2001 SP1"))
                {
                    Store (0x07D1, OSYS)
                }

                If (_OSI ("Windows 2001 SP2"))
                {
                    Store (0x07D2, OSYS)
                }

                If (_OSI ("Windows 2006"))
                {
                    Store (0x07D6, OSYS)
                }
            }

            If (LAnd (MPEN, LEqual (OSYS, 0x07D1)))
            {
                TRAP (0x3D)
            }

            TRAP (0x2B)
            TRAP (0x32)
        }
    }
...
    OperationRegion (GNVS, SystemMemory, 0x7F6DEDBC, 0x0100)
    Field (GNVS, AnyAcc, Lock, Preserve)
    {
        OSYS,   16,
        SMIF,   8,
        PRM0,   8,
        PRM1,   8,
        SCIF,   8,
        PRM2,   8,
        PRM3,   8,
        LCKF,   8,
        PRM4,   8,
        PRM5,   8,
        P80D,   32,
        LIDS,   8,
        PWRS,   8,
        DBGS,   8,
        LINX,   8,

-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

LINX is not a variable, but a field in SystemMemory region. Thus it could be accessed from SMM or EC firmware without us knowing that. IMHO it is too brave to call it NOP.

Regards,
Alex.

-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

True, and some other BIOS have had it as a field as well.

However, I'm comfortable taking this risk because:
1. we've never noticed any difference with the field set.
2. there is approximately 0 chance that this vendor is writing Linux-aware EC or SMM code.
3. we want to stamp out the use of OSI(Linux), not encourage it,
so erring on the conservative side is to turn it off and be quiet by default.

thanks,
-Len
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Am Dienstag 12 Februar 2008 21:00:25 schrieb Len Brown:
[...]

Its a Phoenix BIOS btw.

For the WMI: Could acer_wmi be extended for this as Alex suggested ? Another FSC model is listed in their hw-db.

Atm this is fine for me - being able to adjust the brightness in "some" way. But this is not good for user/newbie xyz. How should he know the kernel-cmdline.

Sidenote:
I don't like this BIOS - there are just no features in it. I'm also struggling with vmx being disabled by the bios - and no menu to enable it.

TRAP 0x3D is the Windows WMI code then ?

I wonder what these two are ;)

best regards
Jan-Simon

yes, but rather than extending acer_wmi, it would probably be more appropriate to fork it into fsc_wmi...

I saw your comments in bugzilla 9939.
One possibility is that we could add a DMI entry that automatically does acpi_osi="!Windows 2006" for you.

only "Windows 2001 SP1" -- so it must be a pretty targeted SMM entry point...

There is no way to tell. The code (that I didn't show) is littered with TRAPs...

cheers,
-Len

-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Am Mittwoch, 13. Februar 2008 05:16:19 schrieb Len Brown:
[...]

Sure ...

For me its ok to use the option. BUT if there's no better way atm then for user "Jony smith" its better to do that automagically.

Best regards
Jan-SImon