Howto Fix Your Buggy DSDT.

I can't say that I'm surprised at your 'tech support' experiences. I've never used SuSE support, probably because I've heard about experiences similar to yours. I have used the aforementioned mailing lists though with good success. It seems that some SuSE developers hang out on those lists and are usually quite responsive. I do agree though that much of the time we help each other over these problems with good results as well.

As promised, here are my fixes for DSDT on Sager NP4750 laptop/ Suse 9.3 x86-64 in format error/warning followed by the code I used:
(Note: you will have to align the code with the code in original DSDT.)

dsdt.dsl 226: Method(\_WAK,1,notserialized)
Warning 2026 Reserved Method must return a Value (_WAK)

Method (\_WAK, 1, NotSerialized)
{
Store (Zero, \_SB.PCI0.PIB.USBW)
Store (One, \_SB.PCI0.PIB.PWBS)
If (LEqual (Arg0, 0x01))
{
Store (Zero, \_SB.PCI0.VLNK)
Store (Zero, \_SB.PCI0.VCLK)
}

Store (0x81, \_SB.BCMD)
Store (Zero, \_SB.SMIC)
Return(Package(0x02){0x00, 0x00})

}



dsdt.dsl 2592 Field (Rom,AnyAcc,Lock, Preserve Precxx)
Error 1048 Host operation Region requires ByteAcc

OperationRegion (RAM, EmbeddedControl, 0x00, 0xFF)
Field (RAM, ByteAcc, Lock, Preserve)



dsdt.dsl 3486 Method (_PSR,0,Not Serialized)
Warning 2019 Not all control Paths return a value (_PSR)

dsdt.dsl 3486 Method (_PSR,0,Not Serialized)
Warning 2026 Not all control Paths return a value (_PSR)

Method (_PSR, 0, NotSerialized)
{
If (\_SB.PCI0.PIB.EC.ECOK)
{
Return (One)
}
Else {
Return (Zero)
}

Note: This one took some reading of the acpi spec, as I could not find an example anywhere. This has to do with the AC controller and reports wether or not AC is plugged in or not. Basically it returns a "1" if AC is online or a "0" if it is 0ff-line. this was trial & error, but this compiled W/O error. I'm open to suggestions as I'm no expert.


Lastly,"I might add that when I fixed these and recompiled; there was no end-of-file marker either."

Name (_TC1, 0x02)
Name (_TC2, 0x05)
Name (_TSP, 0x00)
}
}
}
}

Note: The second symbol from the bottom, I moved right 2 spaces; then added the last symbol; then did a return.
Edit: The edit didn't come thru on the post; the bottom symbol is on left most margin & they stairstep up & to the right to the last "Name", sorrry about that.

Whoot: no errors : no warnings.

Have Fun

Here's my DSDT fix on my Nforce3-250GB desktop system running Suse 9.3 32-bits:

My 1st attempt:
linux:/usr/sbin # ./iasl -tc /home/jim/NFdsdt.dsl

Intel ACPI Component Architecture
ASL Optimizing Compiler / AML Disassembler version 20050309 [Mar 19 2005]
Copyright © 2000 - 2005 Intel Corporation
Supports ACPI Specification Revision 3.0

/home/jim/NFdsdt.dsl 343: Method (\_WAK, 1, NotSerialized)
Warning 2026 - ^ Reserved method must return a value (_WAK)

/home/jim/NFdsdt.dsl 2605: Name (_HID, "_NVRAIDBUS")
Error 1068 - String must be entirely alphanumeric ^ (_NVRAIDBUS)

ASL Input: /home/jim/NFdsdt.dsl - 5780 lines, 167644 bytes, 2215 keywords
Compilation complete. 1 Errors, 1 Warnings, 0 Remarks, 565 Optimizations
linux:/usr/sbin #


The fix for (\_WAK) line 343 is the same as the post immediaately above.

The fix for line 2605 simply consisted of removing "_" from (_NVRAIDBUS) to (NVRAIDBUS)

Simple, so you think!

Upon recompile I got these errors:
DSDT.DSL 248 Notify (\_SB.LID,0X02)
Error 1022 Object does not exist (_SB.LID)

DSDT.DSL 2710 Notify (\_SB.LID,0X80)
Error 1022 Object does not exist (_SB.LID)

dsdt.dsl 3578 Return (DACO)
Error 1021 Object not Accessible from this Scope (DACO)

I could not find any google references to these errors. Had to do some "find" & "find next"; then analyze the situation.
for example, "find DACO" resulted in this entry being the only one in the entire table; There was no place for the system to return the value of DACO to. I simply removed the block of code.
ditto with _SB.LID.

Uon recompile, I get:

linux:/usr/sbin # ./iasl -tc /home/jim/NFdsdt.dsl

Intel ACPI Component Architecture
ASL Optimizing Compiler / AML Disassembler version 20050309 [Mar 19 2005]
Copyright © 2000 - 2005 Intel Corporation
Supports ACPI Specification Revision 3.0

ASL Input: /home/jim/NFdsdt.dsl - 5781 lines, 167685 bytes, 2216 keywords
AML Output: DSDT.aml - 19095 bytes 900 named objects 1316 executable opcodes

Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 567 Optimizations
linux:/usr/sbin #


Whoot -- Let's test our work.

OK, let's test our new DSDT:

DSDT.aml was our goal and it will be found in /usr/sbin.
As root, copy it to /etc/DSDT.aml.
Edit /etc/sysconfig/kernel and adapt the path to /etc/DSDT.aml.

# The file name of a binary ACPI Differentiated System Description Table
# (DSDT). This table is appended to the initial ram disk (initrd) that
# the mkinitrd script creates. If the kernel finds that its initrd
# contains a DSDT, this table replaces the DSDT of the bios. If the file
# specified in ACPI_DSDT is not found or ACPI_DSDT is empty/not specified,
# no DSDT will be appended to the initrd.
# Example path /etc/acpi/dsdt
#
ACPI_DSDT=/etc/DSDT.aml

now run "mkinitrd"; this will cause initrd to look for your new DSDT at boot.

You are done.
Let's reboot & hope we made some good guesses.

Examine dmesg again; hese's what I got:
Freeing initrd memory: 1477k freed
ACPI: Looking for DSDT in initramfs... found /DSDT.aml ... successfully read 19095 bytes from /DSDT.aml
ACPI: Using customized DSDT
ACPI-0293: *** Info: Table [DSDT] replaced by host OS
ACPI: setting ELCR to 0200 (from 0820)

Plus, my system boots one h-ll of a lot faster as it's not having to do all those work-arounds that you see in /var/log.

Now I'm down to only this problem:
ACPI-0283: *** Warning: Error evaluating _PSS
powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.00.09e)
ACPI-0283: *** Warning: Error evaluating _PSS
powernow-k8: BIOS error - no PSB
powernow: This module only works with AMD K7 CPUs

So what's the score?
I have a better system -- boots faster; boots cleaner; more functions work .
Clearly I have to explore "BIOS error - no PSB"
I'm open to suggestions!

Have fun

SnakeDriver, I researched that "BIOS error - no PSB". It is due to not having cool 'n' quiet enabled in BIOS. In my case, my present BIOS does not seem to support it, so I am off to find an updated one.

Harryc,

First thing I did was get the latest Epox 8KDA3+ BIOS. I too believe that it does not have a bios trigger for turning on "cool& Quite". I'm sure, however that there was an earlier version that did. Question is: with all the fixes in the bios series, do I really need to go backwards. You can bet that I'm gonna look at it! If I'm gonna go BIOS swapping, I may just see if I can put a BIOS SAVIOR in this machine -- works wonders!

Thanks

BIOS Saviors are great. I could not find one for this board though. I have a stack of older ones around here somewhere. I was able to enable cool 'n' quiet on this machine. Now I am getting a different error(or is it a warning I can ignore), and my temps seem to be down.

powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.00.09e)
ACPI-0283: *** Warning: Error evaluating _PSS
powernow-k8: 0 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV)
powernow-k8: 1 : fid 0xa (1800 MHz), vid 0x8 (1350 mV)

Interesting....it's a 2.0ghz CPU.

harryc@linux:~> cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 31
model name : AMD Athlon™ 64 Processor 3200+
stepping : 0
cpu MHz : 1004.788
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 pni syscall nx mmxext fxsr_opt lm 3dnowext 3dnow
bogomips : 1990.65


Now I have to figure out if it's ramping up and down correctly.

Awesome, it ramps right up when I run glxgears -

harryc@linux:~> cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 31
model name : AMD Athlon™ 64 Processor 3200+
stepping : 0
cpu MHz : 2009.576
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 pni syscall nx mmxext fxsr_opt lm 3dnowext 3dnow
bogomips : 3981.31

Update - FID/VID and Min and Intermediate P-State verified for this processor -

Part# = ADA3200DIK4BI

Min P-State = 1000Mhz p/AMD Processor Power and Thermal Spec Sheet

Intermediate P-State = 1800Mhz p/AMD Processor Power and Thermal Spec Sheet

http://www.amd.com/us-en/assets/content_ty..._docs/30430.pdf

So, I am good to go. Thanks again SnakeDriver.

Harryc -- congrats!
What is your mobo? Did you do a bios upgrade? Which one? Did you do a Suse reinstall? Tell us the details.

I had to go back to 5/14/04 (bios kda34514) ( = about 6 BIOSes back) to get cool'n'quite switch in bios. Suse 9.3 would not boot past usb scan although it was loading cpufreq. Suse 9.2 would load with everything but I think my cpu voltage control was so unstable that it would freeze after 5-10 min. I'm back to latest bios & no cool'n'quite.

Alas......
I'll just suffer barrelling along @ 110% & fan making me loose my hearing!

ACPI-0283: *** Warning: Error evaluating _PSS
powernow-k8: 0 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV)
powernow-k8: 1 : fid 0xa (1800 MHz), vid 0x8 (1350 mV)

look in /var/log/messages

looks like it did the procedure but didn't find all the values. I would think it should start @ 800MHz, with 6-8 steps to 2000MHZ.