dmidecode output from Benq notebook

dmidecode output from Benq notebook

[Dmitry A. Marin]

[-- Attachment #1: Type: text/plain, Size: 139 bytes --]

Hello. I had seen a string "Please send dmidecode to
linux-acpi@vger.kernel.org" in dmesg output and decided to
sent you this information.

[-- Attachment #2: benq-joybook-s31.txt --]
[-- Type: text/plain, Size: 8887 bytes --]

# dmidecode 2.8
SMBIOS 2.4 present.
34 structures occupying 1112 bytes.
Table at 0x000DF810.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: Phoenix Technologies LTD
	Version: 1.08  
	Release Date: 09/12/06
	Address: 0xE8B70
	Runtime Size: 95376 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
		Smart battery is supported
		BIOS boot specification is supported

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: BenQ
	Product Name: Joybook S31
	Version:                                   
	Serial Number: 9H00P11R0364406335DHT300
	UUID: 806F3074-BE64-0010-B773-00163691CDB5
	Wake-up Type: Power Switch
	SKU Number: Not Specified
	Family: Not Specified

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
	Manufacturer: BenQ
	Product Name: Joybook S31
	Version: Rev 1.0
	Serial Number:                                 

Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
	Manufacturer: BenQ
	Type: Notebook
	Lock: Not Present
	Version:                                 
	Serial Number:                                 
	Asset Tag:                                 
	Boot-up State: Unknown
	Power Supply State: Unknown
	Thermal State: Unknown
	Security Status: Unknown
	OEM Information: 0x00001234

Handle 0x0004, DMI type 4, 35 bytes
Processor Information
	Socket Designation: U2E1
	Type: Central Processor
	Family: Unknown
	Manufacturer: Intel
	ID: F6 06 00 00 FF FB EB BF
	Version:   
	Voltage: 3.3 V
	External Clock: 100 MHz
	Max Speed: 1600 MHz
	Current Speed: 1600 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: 16 KB
	Maximum Size: 16 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: External
	Installed Size: 2048 KB
	Maximum Size: 512 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: J23
	Internal Connector Type: 25 Pin Dual Inline (pin 26 cut)
	External Reference Designator: Parallel
	External Connector Type: DB-25 female
	Port Type: Parallel Port ECP/EPP

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

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

Handle 0x000B, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI Slot J11
	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 10, 6 bytes
On Board Device Information
	Type: Sound
	Status: Disabled
	Description: HD-Audio

Handle 0x000D, DMI type 11, 5 bytes
OEM Strings
	String 1:  
	String 2:  
	String 3:  
	String 4:  
	String 5:  

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

Handle 0x000F, 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 0x0010, DMI type 16, 15 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 3 GB
	Error Information Handle: Not Provided
	Number Of Devices: 2

Handle 0x0011, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x0010
	Error Information Handle: No Error
	Total Width: 32 bits
	Data Width: 32 bits
	Size: 1024 MB
	Form Factor: SODIMM
	Set: 1
	Locator: M1
	Bank Locator: Bank 0
	Type: DDR2
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x0012, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x0010
	Error Information Handle: No Error
	Total Width: 32 bits
	Data Width: 32 bits
	Size: 1024 MB
	Form Factor: SODIMM
	Set: 1
	Locator: M2
	Bank Locator: Bank 1
	Type: DDR2
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x0013, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 2 GB
	Physical Array Handle: 0x0010
	Partition Width: 0

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

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

Handle 0x0016, 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 0x0017, 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 0x0018, DMI type 25, 9 bytes
	System Power Controls
	Next Scheduled Power-on: 12-31 23:59:59

Handle 0x0019, 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 0x001A, DMI type 27, 12 bytes
Cooling Device
	Temperature Probe Handle: 0x001B
	Type: Fan
	Status: OK
	OEM-specific Information: 0x00000000

Handle 0x001B, 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 0x001C, 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 0x001D, DMI type 30, 6 bytes
Out-of-band Remote Access
	Manufacturer Name: Intel
	Inbound Connection: Enabled
	Outbound Connection: Disabled

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

Handle 0x001F, DMI type 129, 16 bytes
OEM-specific Type
	Header and Data:
		81 10 1F 00 01 01 02 01 00 00 00 01 00 00 08 01
	Strings:
		Intel_ASF_001
		Intel_ASF_001

Handle 0x0020, DMI type 136, 8 bytes
OEM-specific Type
	Header and Data:
		88 08 20 00 FF FF 00 00
	Strings:
		..!

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

Re: dmidecode output from Benq notebook

[Len Brown]

On Sunday 15 July 2007 06:40, Dmitry A. Marin wrote:
> System Information
>         Manufacturer: BenQ
>         Product Name: Joybook S31

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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: dmidecode output from Benq notebook

[Len Brown]

On Saturday 19 January 2008 02:54, Dmitry A. Marin wrote:
> Hello! The output of acpidumop is attached. I working with
> 2.6.24-4 kernel now (Ubuntu Hardy (testing)), but if it
> important I can try 2.6.23 as it exist in distribution.
> It seems, that I worked with 2.6.18 5-6 month ago and tried
> some options for booting with another acpi-table (?) and
> don't seen any differnce. Hibirnate and sleep worked well.
> 
> On Fri, 18 Jan 2008 18:56:30 -0500
>  Len Brown <lenb@kernel.org> wrote:
> > On Sunday 15 July 2007 06:40, Dmitry A. Marin wrote:
> > > System Information
> > >         Manufacturer: BenQ
> > >         Product Name: Joybook S31
> > 
> > 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 for the acpidump.

OSI(Linux) has no effect on the AML of this machine,
as OSYS is over-written.  So I'll just kill the warning
on this box by adding it to the NOP DMI list.

thanks,
-Len

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

                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)
                }
            }

Re: dmidecode output from Benq notebook

[Theodore Tso]

On Sun, Jan 20, 2008 at 02:08:40PM -0500, Len Brown wrote:
> 
> OSI(Linux) has no effect on the AML of this machine,
> as OSYS is over-written.  So I'll just kill the warning
> on this box by adding it to the NOP DMI list.

The one thing I worry about is if you aren't including the BIOS
version in the DMI list, you could end up in a situation where one
version of the BIOS treats OSI(Linux) as a no-op, but a newer or an
older version of the BIOS actually does something with it....

BIOS writers can be sneaky that way.  :-)


      	      	     	  	   		  - Ted

Re: dmidecode output from Benq notebook

[Len Brown]

On Monday 21 January 2008 02:51, Theodore Tso wrote:
> On Sun, Jan 20, 2008 at 02:08:40PM -0500, Len Brown wrote:
> > 
> > OSI(Linux) has no effect on the AML of this machine,
> > as OSYS is over-written.  So I'll just kill the warning
> > on this box by adding it to the NOP DMI list.
> 
> The one thing I worry about is if you aren't including the BIOS
> version in the DMI list, you could end up in a situation where one
> version of the BIOS treats OSI(Linux) as a no-op, but a newer or an
> older version of the BIOS actually does something with it....
> 
> BIOS writers can be sneaky that way.  :-)

I'm not worried.

Vendors that want to make a BIOS change to actually benefit Linux
will actually boot Linux on their machine, and will notice
that OSI(Linux) has no effect in 2.6.23 and later.

The object here is simply to identify systems which have already
shipped (say they were tested against Linux-2.6.22 or earlier)
that really do require OSI(Linux).

The reason we put in a BenQ DMI entry was simply to prevent
spamming dmesg with requests for DMI info and test results
that we already have.  I have zero interest in spamming users
of every version of the platform's BIOS to confirm that
they are all the same.  Indeed, I'd be more inclined to
wildcard the DMI entries more by deleting some of the
platforms and ignoring entire Vendors w/ a single entry --
as the vendors tend to do the same thing on every product.

thanks,
-Len

Re: dmidecode output from Benq notebook

[Theodore Tso]

On Mon, Jan 21, 2008 at 06:22:42PM -0500, Len Brown wrote:
> > The one thing I worry about is if you aren't including the BIOS
> > version in the DMI list, you could end up in a situation where one
> > version of the BIOS treats OSI(Linux) as a no-op, but a newer or an
> > older version of the BIOS actually does something with it....
> > 
> > BIOS writers can be sneaky that way.  :-)
> 
> I'm not worried.
> 
> Vendors that want to make a BIOS change to actually benefit Linux
> will actually boot Linux on their machine, and will notice
> that OSI(Linux) has no effect in 2.6.23 and later.

You're giving the vendors far too much credit.  It's very likely that
vendors will only test their BIOS on one distro kernel, probably of
their distro partner.  So they may not notice that OSI(Linux) has no
effect in 2.6.23 and later until it's too late (i.e., after they've
stopped doing active firmware development on that BIOS series).
Hence, it's critical to get the distro kernel people involved, and
have them issue errata kernels that matches the upstream behaviour,
and/or get whoever has back-channel connections into HP, Dell, Lenovo,
etc., involved in talking with the firmware development folks.
Otherwise, we can *NOT* guarantee that the right thing will happen ---
in fact it's fairly likely it won't!

				- Ted

Re: dmidecode output from Benq notebook

[Len Brown]

On Tuesday 22 January 2008 10:29, Theodore Tso wrote:
> On Mon, Jan 21, 2008 at 06:22:42PM -0500, Len Brown wrote:
> > > The one thing I worry about is if you aren't including the BIOS
> > > version in the DMI list, you could end up in a situation where one
> > > version of the BIOS treats OSI(Linux) as a no-op, but a newer or an
> > > older version of the BIOS actually does something with it....
> > > 
> > > BIOS writers can be sneaky that way.  :-)
> > 
> > I'm not worried.
> > 
> > Vendors that want to make a BIOS change to actually benefit Linux
> > will actually boot Linux on their machine, and will notice
> > that OSI(Linux) has no effect in 2.6.23 and later.
> 
> You're giving the vendors far too much credit.  It's very likely that
> vendors will only test their BIOS on one distro kernel, probably of
> their distro partner.  So they may not notice that OSI(Linux) has no
> effect in 2.6.23 and later until it's too late (i.e., after they've
> stopped doing active firmware development on that BIOS series).

I agree it is likely that the laptop vendors would be focused
only on the snapshot of the Linux distro pre-installed on their SKU.

If the customer customer stays with the installed Linux
that was validated, then everybody is happy.

If the vendor supplies an upgrade for a .22 or earlier kernel
to a .23 or later kernel, or if the user takes the initiative
and does so with an upstream kernel, then any OSI(Linux) hook
will stop working, and they'll get a new dmesg warning asking them
to try acpi_osi=Linux.

If they don't read their dmesg, they'll call the vendor
and ask why their mute button stopped working after the ugprade.

> Hence, it's critical to get the distro kernel people involved, and
> have them issue errata kernels that matches the upstream behaviour,
> and/or get whoever has back-channel connections into HP, Dell, Lenovo,
> etc., involved in talking with the firmware development folks.
> Otherwise, we can *NOT* guarantee that the right thing will happen ---
> in fact it's fairly likely it won't!

We know for sure that we have to worry about Lenovo,
and I'd keep my eye on what Dell and HP do, since they also
dabble in Linux.

Everybody else seems to be invoking OSI(Linux) either
by habit, or by accident.

-Len